Hello everyone;
Please excuse any lack of detail as this is the first time I'm posting. I've been scouring the internet for days now trying to find any detail that could help me troubleshoot the issue. I am new to the ESXi and ghettoVCB script world.
My intention is to run several tasks on a schedule. Each type of backup (Quarterly, Monthly, Weekly, Daily and Multiple) runs at a specified time. Got the scheduling part working just fine.
I'm hoping by resolving this one urgent backup that I should be able to resolve the reset.
The following is the command I'm running:
vmconfig-DataSet1-multiple contains:
# Multiple Backups - 6 rotation count
#
VM_BACKUP_VOLUME=/vmfs/volumes/Vault2-DataSet1/URANUS/Multiple
DISK_BACKUP_FORMAT=thin
VM_BACKUP_ROTATION_COUNT=6
POWER_VM_DOWN_BEFORE_BACKUP=0
ENABLE_HARD_POWER_OFF=0
ITER_TO_WAIT_SHUTDOWN=4
POWER_DOWN_TIMEOUT=5
SNAPSHOT_TIMEOUT=15
ENABLE_COMPRESSION=0
VM_SNAPSHOT_MEMORY=0
VM_SNAPSHOT_QUIESCE=0
VMDK_FILES_TO_BACKUP=
vmlist-Multiple contains 1 server listed:
# List all VMs that are backed up multiple times daily
HEAT
The log shows that the backup was successful - however it was not. The backup size is expected to be about 8gb. However, when looking at the output folder, only the following files are there:
HEAT.vmx
STATUS.ok
Question now is - where are the vmdk files that should be present?
The output (-d debug) can be found here: http://pastebin.com/hMGphTL3
So here's what else I've observed:
When running the script, the snapshot takes only a few seconds to create and then delete. I'm seeing this happen on vSphere's Rencent Tasks list (screenshot attached).
If I create a snapshot manually - it takes much longer to create and delete a snapshot. The difference here is 4 seconds using the script and 6 minutes creating a snapshot manually.
So my presumption is that it's not actually creating the snapshot, although vSphere is saying one is being created. So why is this the case?
Please help.
ADDENDUM:
If I run the following:
./ghettoVCB.sh -m HEAT
The backup is successful.