just to add, i just tried a backup on the VM using the script without any specific config file. the script gives no errors but still only backs up data.vmx and the first data.vmdk. data_01.vmdk is still missing. I just cant understan why everything else is working apart from this one file
FYI The iscsi volume which holds the VM is 2TB in size and has about 233GB free.
You mentioned your have a 2TB iSCSI volume and that it has 233GB free? Did you mean 233GB used? Since the VM you're trying to backup is 800GB? Looking at the log, the script only found 1 VMDK ... it might be due to the name of the VMDK, that's the only thing that I can see that maybe off OR that the this data disk is a physical RDM or configured as an Independent disk
Hi Ian, thanks for your quick reply,
sorry just to be clear, the destination volume which we are using to store the backup is 2TB and has nothing on it. the volume currently holding the live vm is also 2tb and has about 233GB free.
>>Looking at the log, the script only found 1 VMDK
for testing perposes i set the vm config file to only backup the problematic disk ie pmbdata_1.vmdk. with a defualt of "all" it backs up pmbdata.vmdk and not pmbdata_1.vmdk, although the log says both have been backed up OK.
Edit: here's the output from a dry run when using default "all" disks to be backed up (it seems to find both disks OK):
As far as i can tell there's nothing different between this disk and any others. both disk 1 and disk 2 are not set to "indedpendant" in the actual VM's settings in vsphere.
Can you run the backup with debugging option enabled and backup all VMDK's and provide me with the log?
I had a few follow-up questions:
1) Are you backing up to a VMFS datastore?
2) If so, what is the blocksize configured for the source and destination VMFS datastore?
3) What are the size of your VMDKs that are not backing up?
Hi Ian, your right it was the blocksize of the data store, unfortunatly i have tested the backup on one of our live datastores and it is eating all space up, is there a way to halt the back up!
If you need to halt the backup, just ctrl+C and the backup will stop. You'll need to do some post-clean up by removing the snapshot that exists. If you have this kicked off a cronjob, then you'll need to search for the process and kill it.