We have a SharePoint farm with 2 Nodes, one WFE and one SQL Server to host the Databases.
Networker Server version is 184.108.40.206 Build 1109 and NMM clients 8.2.3.
The Backup complete on the save sets regarding the Databases, except "APPLICATION: Microsoft Office SharePoint Services". The Jobs status is running and there is not any save session active.
We left the job to run for 12 hours without any progress until we force stop it. If we set "Inactivity timeout" on the Group the backup fail with error "82867:nsrsnap_vss_save:Stopping an instance of NMM save with process Id=36408 on host: <Hostname>. There is another instance of NMM save program is already running" after the inactivity timeout reached.
Same error occurred even if we stop the previous nsrsnap_vss_save process.
Can you restart networker services on client side and run full backup and let us know results.
Yes we have try restart the services, nothing changed. We have double check the permission on SQL server and reregister the VSS writer. the job stay idle on "APPLICATION: Microsoft Office SharePoint Services" save set.
Test the file system backups, but for all nodes in the Sharepoint farm. Just backup one file from each node is sufficient, and backup to the same pool and storage node. If this fails, then this needs to be resolved before testing NMM backups.
Next, consider updating the n/w software and the NMM software, and make sure that each client in the Sharepoint farm is using the same versions. You can find the latest cumulative hotfixes at:
For each sharepoint node, use NMM's config_checker tool, and resolve any issues that it reports.
To troubleshoot the Sharepoint backup , you can look at the NMM log files. This is located in each Sharepoint node, in the nsr\applogs directory. for example:
C:\Program Files\EMC NetWorker\nsr\applogs\nmm.raw
Also look at the daemon.raw too...
C:\Program Files\EMC NetWorker\nsr\logs\daemon.raw
To read the .RAW file, please render (convert) to readable format using:
nsr_render_log nmm.raw > nmm.log 2>&1
Remember to do these steps for each Sharepoint node.
same problem , NW 220.127.116.11 (both server and client) + NMM 18.104.22.168
First backup hang for 19 hours , then we stopped it.
I had this same issue. We upgraded to 22.214.171.124 though 126.96.36.199 is out and I would recommend upgrading. We also had to do this to properly support DDOS 6.x