Solved!
Go to Solution3897
0
Posted December 10th, 2011 08:00
* euexmp03 APPLICATIONS:\Microsoft Exchange 2010\EUT2B: Backup of [APPLICATIONS:\Microsoft Exchange 2010\EUT2B] failed Operation unit failed with error 'Traditional save returned error. saverc :-1'.Possible cause: 1)Unsupported file system or 2)write-protected disc or 3)No space on disc or 4)Drive not found NMM .. Error backing up one or more of the file system savesets: NMM .. Operation unit failed with error Traditional save returned error. saverc :-1. 64038:nsrsnap_vss_save:NMM .. Error creating NetWorker backup of snapshot: NMM .. Operation unit failed with error Traditional save returned error. saverc :-1. 63372:nsrsnap_vss_save:NMM .. Registration of snapshot set failed -- NMM .. Operation unit failed with error Traditional save returned error. saverc :-1 76960:nsrsnap_vss_save:NMM .. error caught calling RM to commit the replica. 49931:nsrsnap_vss_save:RM .. 027114 ERROR:Exchange Replication Service is stable. The error is VSS_E_WRITERERROR_RETRYABLE. The code is: 0x800423f3. Check the application event log for more information. 49931:nsrsnap_vss_save:RM .. 024168 ERROR:The VSS shadow copy for Exchange Replication Service was not successful because of an error that occurred earlier. 83394:nsrsnap_vss_save:NMM .. cluster failover or application role change after a replica created may have caused snapshot creation failure, try to restart the backup. 63335:nsrsnap_vss_save:NMM backup failed to complete successfully. Internal error.
3897
0
Posted December 12th, 2011 02:00
Hello,
This error message usually indicates a time out.
Can you please check the following?:
Group configuration:
1.- Inactivity Timeout has to be set to "0"
2.- Client retries has to be set to "0"
Also before running the backup please run the following command on the client:
vssadmin list writers
All writers should be in status [1] Stable. Otherwise I would suggest you to reboot the box.
If all these settings are ok then I would suggest you to set the TCP/IP best practices:
DWROD entries with Decimal values
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpWindowSize=256000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\GlobalMaxTcpWindowSize=16777216
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveInterval=1000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime=1800000
These registry entries have to be created in client and server, and need a reboot of the machines.
Thank you.
Carlos.
3897
0
Posted December 12th, 2011 19:00
Hi Carlos
we do get VSS errors ocassionally but thought that is more towards OS issue since when backup tries to use VSS it goes down...
As for the group settings, by default, they are not zero? Any reason to change to 0? Only VSS groups or all in general?
And the TCP/IP settings, how are they related to VSS? Are these EMC recommendations?
Just to clarify for better understanding... you have been giving many valuable tips....keep up the good work!
3897
0
Posted December 15th, 2011 17:00
thanks carlos..wish i could assign points to you.....
3897
0
Posted December 20th, 2011 21:00
Hi Thierry,
So is the problem solved now?
Thank you.
Carlos.
3897
0
Posted November 6th, 2012 22:00
No worries.. I`ve marked Carlos's answer as a "correct answer" and he got the points now
Thanks so much Carlos
Mustafa
36115_carloscor
217 Posts
3897
0
Posted December 13th, 2011 02:00
Hi Thierry,
The default inactivity timeout setting in the groups are 30 (minutes) and the reason behind setting it to "0" (no limit) is basically to allow the VSS operations (snapshot creation/mount/consistency check) to take the required time, so the group doesn't get timed out if the VSS operations take long time.
The reason behind the TCP/IP settings are in fact Microsoft changes, as described in the following articles:
http://technet.microsoft.com/en-us/library/cc957546.aspx
http://technet.microsoft.com/en-us/library/cc938219.aspx
http://technet.microsoft.com/en-us/library/cc957548.aspx
http://technet.microsoft.com/en-us/library/cc957549.aspx
These settings keep the TCP/IP connections open, so doesn't time out, and the connections is kept alive to allow NetWorker server and clients to send data when required without any problem.
Let us know if you need any further information.
Thank you.
Carlos.