This post is more than 5 years old
16 Posts
0
5099
Exchange consistency check failure after disk space issue
Exchange consistency check failure after disk space issue
Hi, we’ve recently had an issue with disk space on our Exchange 2010 server which was promptly resolved. However, since the space issue our Networker Exchange backups (v2.5.1_NMM2.3_drop11c.Build.36) have been failing with the following error:
savegrp: suppressed 10 lines of verbose output
NMM .. Error encountered performing snapshot import: PS .. Error starting snapshot import: Error during Exchange consistency check. See RM logs for details
64034:nsrsnap_vss_save:NMM .. Error during import of snapshot: PS .. Error starting snapshot import: Error during Exchange consistency check. See RM logs for details
.
63372:nsrsnap_vss_save:NMM .. Registration of snapshot set failed -- PS .. Error starting snapshot import: Error during Exchange consistency check. See RM logs for details
77175:nsrsnap_vss_save:NMM .. completed commit replica with status of false.
63335:nsrsnap_vss_save:NMM backup failed to complete successfully.
Internal error.
68151 1332086690 2 0 0 11180 12928 0 mailserver nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0
run for this backup. NSR_EXCH_CHECK value is set to YES.
mailserver APPLICATIONS:\Microsoft Exchange 2010:
Attached is the converted nmm log which shows the last good backup, following a series of bad backups.
Any assistance would be greatly appriciated.
AlanJH1
16 Posts
0
March 19th, 2012 19:00
Thanks for your help Ahmed and Mustafa.
My colleague was able to get it working by performing these troubleshooting tasks:
End nsrsnap_vss_save.exe process
Stop all networker and replication services
Elevate command prompt
Type diskshadow
Type list shadows all
If shadows exist type delete shadows all
Delete log folder under c:\prog files\legato\nsr
Delete mount point d:\mount_dir
Start all networker and the replication service that has an automatic startup type
NWadmin1
89 Posts
1
March 18th, 2012 23:00
Hi Alan,
Check the NSR_ALT_PATH directory and make sure it is clean before the backup is run. Or delete it:
Note: If the file system path specified for NSR_ALT_PATH in Exchange client does not exist, it is automatically created in
NMM.
Also, do the usual checks to see that Exchange and the writers are happy and there aren’t left over snapshots hanging around.
Thanks,
Mustafa
Bebo2k
544 Posts
1
March 18th, 2012 23:00
Hi AlanJH,
Please check the status of the Databases and the replication , Make sure that all Databases are in healthy status.
Also how the backup is going if you specify the NSR_EXCH_CHECK=No , the backup works correctly , Just to double check that the issue mainly with the Exchange consistecny check.
Waiting your updates.
Thanks,
Ahmed Bahaa