I am again hit with the problem of backing up two virtual machines with the same error in my previous post Problem With Virtual Machine Backup–Part 2 of 2 but with a different cause.
The same error message shown up in vCenter.
Create virtual machine snapshot
Cannot create a quiesced snapshot because
the create snapshot operation exceeded the
time limit for holding off I/O in the frozen
virtual machine.
Checking the hostd.log, I found the following error message.
[2011-12-23 03:20:23.108 FF99EE80 verbose 'vm:/vmfs/volumes/4a880abd-883fb168-b09f-12feb0cabb11/deServer01/deServer01.vmx' opID=b30b905e-c] Tools version status: ok
[2011-12-23 03:20:23.108 FF99EE80 verbose 'vm:/vmfs/volumes/4a880abd-883fb168-b09f-12feb0cabb11/deServer01/deServer01.vmx' opID=b30b905e-c] VMware Tools are current in guest: true
[2011-12-23 03:20:25.114 FF99EE80 verbose 'vm:/vmfs/volumes/4a880abd-883fb168-b09f-12feb0cabb11/deServer01/deServer01.vmx' opID=b30b905e-c] Quiesced snapshot backup agent event: (vim.vm.BackupEventInfo) {
dynamicType = <unset>,
eventType = "requestorError",
code = 3,
message = "The system cannot find the path specified.",
}
[2011-12-23 03:20:25.114 FF99EE80 error 'vm:/vmfs/volumes/4a880abd-883fb168-b09f-12feb0cabb11/deServer01/deServer01.vmx' opID=b30b905e-c] Quiesced snapshot backup agent error: The system cannot find the path specified. (3)
[2011-12-23 03:20:25.115 FF99EE80 verbose 'vm:/vmfs/volumes/4a880abd-883fb168-b09f-12feb0cabb11/deServer01/deServer01.vmx' opID=b30b905e-c] Tools version status: ok
[2011-12-23 03:20:25.115 FF99EE80 verbose 'vm:/vmfs/volumes/4a880abd-883fb168-b09f-12feb0cabb11/deServer01/deServer01.vmx' opID=b30b905e-c] VMware Tools are current in guest: true
[2011-12-23 03:20:25.115 FF99EE80 verbose 'vm:/vmfs/volumes/4a880abd-883fb168-b09f-12feb0cabb11/deServer01/deServer01.vmx' opID=b30b905e-c] Quiesced snapshot backup agent event: (vim.vm.BackupEventInfo) {
dynamicType = <unset>,
eventType = "requestorError",
code = 3,
message = "Error when enabling the sync provider.",
}
The resolution for this cause was simple. I did a repair on the VMware Tool installation and it solved the issue. Just completed the backup for the two virtual machines.
No comments:
Post a Comment