Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm on VMware ESXI 5.0.0 Update 1 and wanted to use the ghettoVCB script for backuping my VMs.

The dryrun went perfectly fine:

2012-10-24 11:47:46 -- info: ###### Final status: OK, only a dryrun. ######

But when I try to do an actual backup, I get the following message for every VM on my host:

2012-10-24 11:48:43 -- info: Initiate backup for Willert-Tools
2012-10-24 11:48:43 -- info: Creating Snapshot "ghettoVCB-snapshot-2012-10-24" for Willert-Tools

2012-10-24 11:48:47 -- info: ERROR: error in backing up of "/vmfs/volumes/datastore1/Willert-Tools/Willert-Tools_1.vmdk" for Willert-Tools

2012-10-24 11:48:47 -- info: ERROR: error in backing up of "/vmfs/volumes/datastore1/Willert-Tools/Willert-Tools.vmdk" for Willert-Tools
2012-10-24 11:48:50 -- info: Removing snapshot from Willert-Tools ...
2012-10-24 11:48:50 -- info: Compressing VM backup "/vmfs/volumes/Cluster-Backup/Willert-Tools/Willert-Tools-2012-10-24_11-48-31.gz"...
2012-10-24 11:48:50 -- info: Successfully compressed backup for Willert-Tools!

2012-10-24 11:48:50 -- info: Backup Duration: 7 Seconds
2012-10-24 11:48:50 -- info: ERROR: Unable to backup Willert-Tools due to error in VMDK backup!

What am I doing wrong? As I didn’t want to paste every configuration snippet from my configuration, please ask if you need more specific information.

The backup is supposed to be saved to a NFS share which is correctly mounted on my ESXi host.

Thanks for your help :-).

share|improve this question

1 Answer 1

the most I can suggest by seeing the output is:

1) Are you sure the path to your NFS mount or datastore is correct in the ghettoVCB configs? Double check all NFS configs for ghettoVCB.

And...

2) Is your NFS share accepting anonymous access and granting read/write permissions?

Judging by the output, the script was able to create the snapshot but then 5 seconds later it said it could not back up the VMDK. My guess is this is a permissions issue on NFS mount. That, or lack of free space.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.