This post is more than 5 years old
2 Posts
0
2646
NMM Backup Sharepoint
GoodMorning to all ,
when i try new backup with nmm i recived these error:
SYSTEM COMPONENTS:\: NSRSNAPCK::success
SYSTEM COMPONENTS:\: Backup of [SYSTEM COMPONENTS:\] failed
_recycle_interval: 86400;
snap_id_list_1: NetWorker Module for Microsoft Applications,
Microsoft Volume Shadow Copy Service;
snap_sessionid: 1373356648;
NMM .. Starting Backup. This operation may take a long time depending on the size of the data requested.
82296:nsrsnap_vss_save:NMM .. Operation unit failed with error 'Failed to create snapset. Reason: Not enough space'.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 Failed to create snapset. Reason: Not enough space.
64038:nsrsnap_vss_save:NMM .. Error creating NetWorker backup of snapshot: NMM .. Operation unit failed with error Failed to create snapset. Reason: Not enough space.
63372:nsrsnap_vss_save:NMM .. Registration of snapshot set failed -- NMM .. Operation unit failed with error Failed to create snapset. Reason: Not enough space
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 1373359645 2 0 0 7060 8296 0 iso9999app138.iso.itcgr.net nsrsnap_vss_save NSR warning 39 nsrsnap_vss_save: Exiting with failure. 0
but in the client the space is enoug....
CarlosRojas
1.7K Posts
0
July 10th, 2013 07:00
This is usually a timeout.
Do as follows:
1.- Group Inactivity Timeout is set to "0" in the Exchange client configuration in NMC.
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 (DWORD 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=600000
On Solaris:
#ndd -get /dev/tcp tcp_keepalive_interval
7200000
#ndd -set /dev/tcp tcp_keepalive_interval 3360000
Thank you,
Carlos
TimQuan
1.2K Posts
1
July 9th, 2013 19:00
“Operation unit failed with error Failed to create snapset. Reason: Not enough space” indicates there is not enough disk space on the disk drive. Please verify whether there is enough disk space on all drives of the backup client to create snapshot. If not, remove/move some files on the drive to free up enough disk spaces.
If all local drives have enough space, you can open the properties of every drive on the client and click the Settings button on the Shadow Copies tab, check “Located on this volume”. Are they all local drives? If it is a shared drive/network drive/external drive, please verify whether that drive has enough disk space.
TimQuan
1.2K Posts
0
July 9th, 2013 19:00
Just find you are backing up sharepoint 2010, sharepoint backup needs space for staging. Resolution:https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000U9S
You can log on your powerlink account to see above article.
CarlosRojas
1.7K Posts
0
July 10th, 2013 02:00
Hi,
The messages obviously indicates that there is not enough space to create the shadow.
You would need to check the available free space in the drives.
Also you can check in the Disk Manager, how the shadows are configured.
You can either set a limit so the snapshot doesn't go above the max fee space on the drive, or you can just have a dedicated drive to place the snapshots, and then change the settings in shadow copies so that the snapshot is created in the dedicated drive.
Thank you,
Carlos
B4FQqUoIrW12094
60 Posts
0
July 10th, 2013 02:00
Check the status of VSS writers
vssadmin list writers
make sure no writers are failed/ not stabe
Clean up any dead VSS snapshots. Some defect systems accumulate hundreds of VSS snapshots that persist in the system and cause Windows to become unresponsive.
vssadmin delete shadows /all
Check vssadmin list shadowstorage
This will show you how much storage you have on your system.
check the size of Maximum Shadow Copy Storage space:
increase the same if it required
MorrisDileo
2 Posts
0
July 10th, 2013 07:00
Many thanks to all for the answers,
i have checked the vss and the shadows copy limit and in this moment the error is these:
SYSTEM COMPONENTS:\: Backup of [SYSTEM COMPONENTS:\] failed
NSR_CONNECTING_DIRS: No;
NSR_DATA_MOVER: iso9999app138.iso.itcgr.net;
NSR_GROUP: Test - Sharepoint;
NSR_PARENT_JOBID: 618295;
NSR_PS_DEBUG_ID: 1373462200;
NSR_SERVER: iso9999srv11.iso.itcgr.net;
NSR_SNAP_DELETE_ON_CLEANUP: 1;
NSR_SNAP_TYPE: vss;
NSR_STRICT_SYNC: 0, 0;
optype: conventional;
snap_id_list_1: NetWorker Module for Microsoft Applications,
Microsoft Volume Shadow Copy Service;
snap_sessionid: 1373462201;
NMM .. Starting Backup. This operation may take a long time depending on the size of the data requested.
82296: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
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
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 1373465087 2 0 0 1656 8960 0 iso9999app138.iso.itcgr.net nsrsnap_vss_save NSR warning 39 nsrsnap_vss_save: Exiting with failure. 0