Unsolved
This post is more than 5 years old
7 Posts
0
562
May 1st, 2019 09:00
84505:nsrvadp_save: Error while creating mutex, error code : 5
Hello everyone. I have a backup that continues to fail it's scheduled backup, but if I run it manually it will work fine. The error log I get is:
--- Unsuccessful Save Sets ---
* TOLSQL02:*FULL* suppressed 2003 bytes of output.
* TOLSQL02:*FULL* Trying to connect to the VM using VM name 'TOLSQL02'.
* TOLSQL02:*FULL* Performing a File level incremental over image level backup.
* TOLSQL02:*FULL* Creating a quiesced snapshot for 'TOLSQL02'.
* TOLSQL02:*FULL* 04/30/19 17:31:33.304379 Creating snapshot for 'vm-186' ...
* TOLSQL02:*FULL* 04/30/19 17:31:33.351253 Task is 0% complete
* TOLSQL02:*FULL* 04/30/19 17:31:49.023683 Task is 50% complete
* TOLSQL02:*FULL* 04/30/19 17:32:03.336656 Task is 50% complete
* TOLSQL02:*FULL* 04/30/19 17:32:03.477283 Task is -1% complete
* TOLSQL02:*FULL* The snapshot was created successfully for VM 'TOLSQL02'.
* TOLSQL02:*FULL* Downloading VM configuration for TOLSQL02.
* TOLSQL02:*FULL* Configuration downloaded successfully for VM 'TOLSQL02'.
* TOLSQL02:*FULL*
* TOLSQL02:*FULL* Following are the details of the client TOLSQL02:
* TOLSQL02:*FULL* VirtualCenter : 10.180.20.182
* TOLSQL02:*FULL* ESX Server : tolesx1.pngaming.com
* TOLSQL02:*FULL* DataCenter Name : Toledo
* TOLSQL02:*FULL* ConfigDatastore Name : VMware_LUN_36
* TOLSQL02:*FULL* Resourcepool Name : /
* TOLSQL02:*FULL*
* TOLSQL02:*FULL* Following is the disk information of the client TOLSQL02:
* TOLSQL02:*FULL* Disk 1 Label : Hard disk 1
* TOLSQL02:*FULL* Disk 1 Size : 80.0 GB
* TOLSQL02:*FULL* Disk 1 Datastore name : VMware_LUN_36
* TOLSQL02:*FULL* Disk 2 Label : Hard disk 2
* TOLSQL02:*FULL* Disk 2 Size : 200.0 GB
* TOLSQL02:*FULL* Disk 2 Datastore name : VMware_LUN_36
* TOLSQL02:*FULL* Total Number of Disks : 2
* TOLSQL02:*FULL*
* TOLSQL02:*FULL* Obtained the virtual disks for the VM.
* TOLSQL02:*FULL* Change block tracking is disabled for VM: TOLSQL02
* TOLSQL02:*FULL* 84505:nsrvadp_save: Error while creating mutex, error code : 5.
* TOLSQL02:*FULL* 80430:nsrvadp_save: Could not mount the VM as a file system. Exiting.
* TOLSQL02:*FULL* Cleaningup VADP mount operation.
* TOLSQL02:*FULL* 04/30/19 17:32:07.368041 Deleting snapshot for 'snapshot-10599' ...
* TOLSQL02:*FULL* 04/30/19 17:32:07.399289 Task is 0% complete
* TOLSQL02:*FULL* 04/30/19 17:32:07.430539 Task is 0% complete
* TOLSQL02:*FULL* 04/30/19 17:32:07.743057 Task is 2% complete
* TOLSQL02:*FULL* 04/30/19 17:32:07.946188 Task is 7% complete
* TOLSQL02:*FULL* 04/30/19 17:32:08.149317 Task is 43% complete
* TOLSQL02:*FULL* 04/30/19 17:32:08.508705 Task is 57% complete
* TOLSQL02:*FULL* 04/30/19 17:32:08.711842 Task is 78% complete
* TOLSQL02:*FULL* 04/30/19 17:32:08.914972 Task is 100% complete
* TOLSQL02:*FULL* 04/30/19 17:32:09.368164 Task is 100% complete
* TOLSQL02:*FULL* 04/30/19 17:32:09.368164 Task is -1% complete
* TOLSQL02:*FULL* Snapshot for VM TOLSQL02 is deleted.
* TOLSQL02:*FULL* Temporary directory 'c:\mnt\TOLSQL02' for VADP deleted.
crazyrov
4 Operator
•
1.3K Posts
1
May 5th, 2019 23:00
S0URSH0ES
7 Posts
0
May 9th, 2019 06:00
Permission issues? That's interesting because I've also seen permission errors when I try to fiddle with the backup settings. The strange thing is this started happening all of a sudden; the permissions on the server didn't change. I will look more into the permissions though, thank you.
I know we are on an old version of Networker. We were supposed to get upgraded this year, but it got cut out of the budget. Thank you again for your reply.