Hi,
I have written a custom shell script to run nightly to snapshot a machine and scp them to a DR ESX box. It works fine for 2 out of the 3 VMss. On the 3rd machine i get this error:
Starting Backup ...
Current working directory: /root
Error: Other error encountered: Snapshot creation failed: Custom pre-freeze script failed.
An error occurred, cleaning up...
Export failed. Nothing to transfer to remote host.
Backup Finished.
Both source and destination machines are ESX3.5. All guest machines are Windows 2003 server with a default install of the VMWare tools. I have not 'customised' the pre-freeze scripts (i couldn't even find them - i even created a blank one in C:\windows\system32\)
What is strange is that i can take a snapshot through the VI3 Client and it works fine.
Has anyone see this error before???????
Thanks in advance
Craig.
Craig -
First, if you are using VCB, re-install VMware Tools and select "Complete" instead of typical. This will add the driver needed to quiesce I/O.
pre-freeze.bat will be located in C:\windows or c:\winnt. Check to see if something exists there. If so, just rename it in case something else is using the script.
You can add a "-L 6" to the vcbmounter command to get a verbose log and post it here.
Dave
I think this error is also seen when the vcbmounter fails to quisce the guest OS before creating a snapshot...
Try to add "-Q 0" to your vcbmounter command...
/Rubeck
Craig -
First, if you are using VCB, re-install VMware Tools and select "Complete" instead of typical. This will add the driver needed to quiesce I/O.
pre-freeze.bat will be located in C:\windows or c:\winnt. Check to see if something exists there. If so, just rename it in case something else is using the script.
You can add a "-L 6" to the vcbmounter command to get a verbose log and post it here.
Dave
Hi,
Sorry for the late reply, Last weekend we were able to do a "Complete" install of the vmware tools and a couple of restarts of the server and it all looks fine now.
Thanks for your assistance
Craig.
PS: adding the -L 6 didn't show any additional information about the error, but was quite informative of what it was doing
Nice to hear it was fixed. That's the life of an IT person. Gotta wait for the window for a reboot....
Dave