Unsolved
This post is more than 5 years old
1 Rookie
•
77 Posts
0
7339
April 13th, 2012 08:00
Nmm fails with error 'Traditional save returned error. saverc :-1'
Hi,
I've setup a NMM backup for sharepoint and , starting from yesterday, I receive an error like this ( nmm.raw file ):
82296 13/04/2012 16:42:28 5 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save NMM .. 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
63911 13/04/2012 16:42:28 1 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save 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 13/04/2012 16:42:28 5 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save NMM .. Error creating NetWorker backup of snapshot: NMM .. Operation unit failed with error Traditional save returned error. saverc :-1.
63372 13/04/2012 16:42:38 5 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save NMM .. Registration of snapshot set failed -- NMM .. Operation unit failed with error Traditional save returned error. saverc :-1
77175 13/04/2012 16:42:38 1 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save NMM .. completed commit replica with status of false.
63335 13/04/2012 16:42:38 5 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save NMM backup failed to complete successfully.
50404 13/04/2012 16:42:38 0 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save nsrsnap_vss_save: createInstanceBackup() failed
0 13/04/2012 16:42:38 2 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save nsrsnap_vss_save: APPLICATIONS:\SqlServerWriter: failed
63309 13/04/2012 16:42:38 1 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save NMM .. bye bye.
At the end of the backup with "vssadmin list shadows" I don't see any snapshot present on the system, and the state of all the writers, expecially SQLServerWriter is
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {3c478ca8-b4e8-40b4-bc20-fd669a248218}
State: [1] Stable
Last error: No error
The backup does not fails immediately, but after a long time ...
4360 13/04/2012 14:55:27 1 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save NMM .. Starting Backup. This operation may take a long time depending on the size of the data requested.
82296 13/04/2012 16:42:28 5 0 0 5704 2232 0 aittor16sqcc010 nsrsnap_vss_save NMM .. 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
Can you help me about the reason of the failure?
Thanks
PierPa
Daniea3
123 Posts
0
April 13th, 2012 08:00
Hi Pierpa,
Just found 2 possible cause for the above error,
1. Make sure the System time on the server and client are synchronized
2. http://solutions.emc.com/EMCSolutionView.asp?id=esg108383&usertype=C (Even though it talks about exchange, the error looks generic)
Regards,
Arun
CarlosRojas
1.7K Posts
0
April 14th, 2012 22:00
Hello PierPa,
That error message is usually a timeout.
You have to ensure that:
1.- Group Inactivity Timeout is set to "0"
2.- Add the TCP/IP settings as described in the article above, and if it still fails I would suggest to add the following values in Client and Server:
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=600000
On Solaris:
#ndd -get /dev/tcp tcp_keepalive_interval
7200000
#ndd -set /dev/tcp tcp_keepalive_interval 3360000
Thank you.
Carlos.
pfrassino
1 Rookie
•
77 Posts
0
April 17th, 2012 07:00
Hi,
I've used the suggestion but no changes. In the meantime, I saw that, since the backup is using a DDBoost device, I received errors in the daemon.log file for the client, like:
84029 16/04/2012 20:53:45 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=797731513
84029 16/04/2012 20:54:30 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=780954342
84029 16/04/2012 20:59:29 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=764177425
84034 16/04/2012 20:59:33 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=764177425
84029 16/04/2012 20:59:37 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=730623001
84029 16/04/2012 20:59:39 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=713845787
84034 16/04/2012 20:59:41 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=730623001
84034 16/04/2012 20:59:42 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=713845787
84029 16/04/2012 20:59:43 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=697068575
84034 16/04/2012 20:59:46 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=697068575
84029 16/04/2012 21:02:35 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=646737099
84029 16/04/2012 21:02:40 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=629959888
84034 16/04/2012 21:02:41 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=646737099
84034 16/04/2012 21:02:43 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=629959888
84029 16/04/2012 21:02:45 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=613182677
84034 16/04/2012 21:02:49 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=613182677
84029 16/04/2012 21:02:56 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=596405471
84034 16/04/2012 21:02:59 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=596405471
84029 16/04/2012 21:03:00 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=529296612
84029 16/04/2012 21:03:01 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=512519397
84034 16/04/2012 21:03:04 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=529296612
84034 16/04/2012 21:03:05 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=512519397
84030 16/04/2012 21:10:45 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_PRECOMMIT for ssid=797731513, size=61370910276
84029 16/04/2012 21:35:20 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=378303608
84034 16/04/2012 21:35:23 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=378303608
84029 16/04/2012 21:39:05 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd DIRECT_FILE_SAVE: Data Domain device=rd=aittor16sqcc010:DDBOOSTFGA_AITTOR16SQCC010 returning path for ssid=327972184
84034 16/04/2012 21:39:08 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Falling back to traditional backup for ssid=327972184
0 16/04/2012 22:36:41 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd 04/16/12 22:36:41 nsrmmd #1: active file /xittor06vhcp020/FGA_AITTOR16SQCC010/active/c71d5a25-00000006-2e8c6ae6-4f8c6ae6-00d32500-5c7125b3 (size = 291558359040) was not renamed for ssid = 780954342 over zero size save set file (/xittor06vhcp020/FGA_AITTOR16SQCC010/44/97/c71d5a25-00000006-2e8c6ae6-4f8c6ae6-00d32500-5c7125b3), size does not match the data size (290796380160) written
84031 16/04/2012 22:36:41 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Failed to rename client direct file for ssid=780954342
0 16/04/2012 22:36:42 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd 04/16/12 22:36:42 nsrmmd #1: active file /xittor06vhcp020/FGA_AITTOR16SQCC010/active/c71d5a25-00000006-2e8c6ae6-4f8c6ae6-00d32500-5c7125b3 (size = 291558359040) was not renamed for ssid = 780954342 over zero size save set file (/xittor06vhcp020/FGA_AITTOR16SQCC010/44/97/c71d5a25-00000006-2e8c6ae6-4f8c6ae6-00d32500-5c7125b3), size does not match the data size (290796380160) written
84031 16/04/2012 22:36:42 2 0 0 3352 3208 0 aittor16sqcc010 nsrmmd Failed to rename client direct file for ssid=780954342
Therefore I changed the backup from SAN to LAN, from DDBOOST to VLS and the backups work fin now ( at least , last 3 backup runs were correct ).
But no daemon,log error explanation...
PierPa
Bebo2k
544 Posts
0
April 17th, 2012 15:00
Hi PierPa,
Firstly lets check that your environment is supported for NMM integration with DDboost, The NMM Data Domain integration requires the following software:
Integration requirements:
- NetWorker server 7.6 SP1 or later
- NetWorker storage node 7.6 SP1 or later
- NetWorker client 7.6 SP1 or later
- Data Domain Appliance with Data Domain OS version supported by NetWorker client installed on NMM 2.3 host
- Data Domain OS 4.8 or later for DD Boost functionality
Supported operating systems:
The supported operating systems are as follows:
- Windows 2003 (x86, x64)
- Windows 2003 R2 (x86, x64)
- Windows 2008 SP2 (x86, x64)
- Windows 2008 R2 (x64)
Data Domain Boost on NMM support the following Microsoft applications VSS based backups:
- Exchange Server 2010 (x64)
- SharePoint Server 2010
- SQL Server 2008 R2 (x64)
Where in you case you are backing up SQL server, so is it SQL 2008 R2 or not ?
Note that NMM with DDBoost does not support SQL Server 2005 or SQL Server 2008
Thanks,
Ahmed Bahaa
Bebo2k
544 Posts
0
April 17th, 2012 16:00
Hi PierPa,
For the configuration, make sure that on the NMM client resource in NMC , you have the following configured:
In the Application Information field, the following parameters is set:
• NSR_DIRECT_ACCESS= Yes/No/Default
where:
– Yes is for DISK_ONLY, which means that the data travels directly to Data Domain appliance.
– No is for STORAGE_NODE, which means data travels to the Data Domainappliance through the NetWorker storage node.
– Default is for undefined, which means that NMM ignores this parameter and NetWorker decides about the media type based on client configuration.
• NSR_DEVICE_INTERFACE= DATA_DOMAIN
where, DATA_DOMAIN enables NetWorker for Data Domain based backups.
IMPORTANT Note:
Do not select the Data Domain option when configuring the client resource. Backup fails if the Data Domain option is selected.
Also, In Global (2 of 2) tab of the client configuration, Provide the remote storage node name where the DD device is configured. This should be the first or only entry.
Hope this helps you. Waiting your updates.
Thanks,
Ahmed Bahaa
CarlosRojas
1.7K Posts
0
April 17th, 2012 22:00
Hi PierPa,
Is the DD correctly licensed to use DDBoost?
Have you applied the changes suggested by Ahmed?
NMM 2.3 should work perfectly with DDBoost if the implementation has been done correctly.
Thank you.
Carlos
RashidMahamood
1 Rookie
•
18 Posts
0
January 5th, 2015 04:00
Hi All,
I have issue with Microsoft HYPER-V , Hyper-Visor backup.
I have two physical server , PCHV01 and PCHV02. This physical servers are not clustered and running windows server 2012 R2 operating system.
PCHV01 has three virtual machine, SharePointFEV01, SQLV01, and SharepointAPPV01.
PCHV02 has two virtual machine, SharePointFEV02, SQLV02
SQLV01 and SQLV02 is clustered and running SQL cluster on it.
I have created Networker Backup Group with two physical server , for Hypervisor backup.
Networker is able to take hyper-visor the backup without SQLV01 and SQLV02. But if i included the all VMs the backup is failing after snap shot requested.
The error in system event log is, volume shadow copy is not working fine.
I have restarted VSS , but it failed.
and i tried following things,
net stop "System Event Notification"
net stop "COM+ Event System"
net stop "Microsoft Software Shadow Copy Provider "
net stop "Volume Shadow Copy"
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
if i entered vssadmin list writers after this, i can see that, system writer and sqlwriter is working fine on SQLV01 and SQLV02.
But if i manually start backup from NMC, the system writer will be failed,with state [8].
I restarted the server several times, the system writer will be ready state without error after every restart. But once backup started from NMC, and if you checked the vssadmin list writers. The system writer will be failed state.
Please let me know the reason. I tried most of the Microsoft and EMC article to bring up the system writer up and running.
But i failed.
Please help on this.
CarlosRojas
1.7K Posts
0
January 5th, 2015 05:00
Hello RashidABC
2 thigs:
1.- I think you should open a new thread
2.- I think we are mixing SQL and Hyper-V backups
Can you please create a new thread and be specific as of what the issue is related to?
In he meantime, have you set all fields in the advance tab of the group configuration to "0"?
Thank you,
Carlos