Start a Conversation

Unsolved

This post is more than 5 years old

989

July 30th, 2015 10:00

Sporadic VSS issues on Exchange 2010 backup

This backup runs successfully 90% of the time.  every month and a half or so the server requires a reboot to eliminate a VSS issue.  The writers all look healthy, etc.  My manager is tired of restarting the server.  This is part of a DAG, the other server in the DAG is not experiencing this issue.   

Any ideas are appreciated.


Thanks,

Lee


APPLICATIONS:\Microsoft Exchange 2010: Backup of [APPLICATIONS:\Microsoft Exchange 2010] failed g snap_wait.. 07/29/15 08:36:10.129509 [nsr/save/nsrsnap.c 1764] Calling parse_fs_logs_and_prefix.. 86745:nsrsnap_vss_save:Version information for C:\Program Files\Legato\nsr\bin\nsrsnap_vss_save.exe: Original file name: nsrsnap_vss_save.exe Version: 3.0.0.282 Comments: NetWorker Module for Microsoft (x64) 50423:nsrsnap_vss_save:nsrsnap_vss_save: Unknown Application Information parameter: NSR_SAVE_FROM_SAVEGRP_NSRSNAP, may not be supported 50423:nsrsnap_vss_save:nsrsnap_vss_save: Unknown Application Information parameter: device interface, may not be supported 50423:nsrsnap_vss_save:nsrsnap_vss_save: Unknown Application Information parameter: NSR_SAVE_FROM_SAVEGRP_NSRSNAP, may not be supported 50411:nsrsnap_vss_save:nsrsnap_vss_save: Data mover host name not specified. Assuming local host: 0nh1c2p11.fairpoint.com 89201:nsrsnap_vss_save:nsrsnap_vss_save: Backup is level INCR. Set GLR compatibility to NOT_ELIGIBLE. 80271:nsrsnap_vss_save:NMM .. Valid snapshot policy. Group: "NH_Exchange2010" Snapshot Policy: "RolloverOnly" Snapshots Per Day: "1" Retain: "0" Backup Snapshots: "All" Level: "incr". NMM ... Using client name 0NH1C2P11, the version of the Exchange server is Exchange 2010. 96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfully initialized. Required for Exchange 2010 or Exchange 2013. 47363:nsrsnap_vss_save: nsrpsd service is running on 0NH1C2P11.fairpoint.com. 37959:nsrsnap_vss_save:The group or resource is not in the correct state to perform the requested operation. . 63335:nsrsnap_vss_save:NMM backup failed to complete successfully. Internal error. 68151 1438173368 2 0 0 17720 12924 0 0nh1c2p11.fairpoint.com nsrsnap_vss_save NSR warning 39 nsrsnap_vss_save: Exiting with failure. 0

73 Posts

August 3rd, 2015 15:00

One thing I've run into before is if the DAG is having issues than the Networker backups will not work.  For example DAG with 2 servers, call it DAG1 and DAG2.  I'm backing up DAG1.  DAG2 goes down because log drive fills up.  Networker backup fails on DAG1.  Backup works again when Exchange issues are resolved on DAG2.  In my experience it doesn't mater if its federated or not both exchange servers need to be working.

I would start by looking at Windows event viewer and Exchange.  It could be a Networker issue but I think its more likely to be an Exchange issue.

No Events found!

Top