You are not logged in.
Pages: 1
Thanks for the quick response and the helpful tutorial to rename the disk. I've done that for one VM and will see how the replica job runs now. Btw, I definitely see your point about not naming disks uniquely for one VM even if they are on different datastores, unfortunately that was the configuration when I inherited this setup. :-/
I have a VM that I'm trying to do a replica backup for as part of the following saved job:
/vmfs/volumes/629ebcf6-d370a7b0-0955-d4ae529b7524/XSI/XSIBackup-DC/xsibackup \
--replica=cbt \
"VMs(RUNNING)" \
"root@192.168.1.100:remotehost:22:/vmfs/volumes/Data01/Backups/Replicas/$(( $(date +%j) % 2 ))" \
>> /vmfs/volumes/629ebcf6-d370a7b0-0955-d4ae529b7524/XSI/XSIBackup-DC/var/log/xsibackup.log 2>&1
Mostly everything is working fine, but my issue is that one of the VMs has two hard disks configured, and only the first one is getting backed up - the other is getting excluded/skipped. From the xsibackup.log file:
2/30 VM1-flat.vmdk (CBT 1 full) 50.00 GB ESC[90m|ESC[0m Done 0.00%
ESC[90m-------------------------------------------------------------------------------------------------------------ESC[0m
^M 3/30 VM1.vmdk 755.00 B ESC[90m|ESC[0m Done 30.83%
ESC[90m-------------------------------------------------------------------------------------------------------------ESC[0m
<snip>
ESC[90m-------------------------------------------------------------------------------------------------------------ESC[0m
^M 26/30 VM1-flat.vmdk (CBT 1 full) 80.00 GB ESC[90m|ESC[0m Done 30.84%
ESC[90m-------------------------------------------------------------------------------------------------------------ESC[0m
^M 27/30 VM1-ctk.vmdk [skipped excluded]
ESC[90m-------------------------------------------------------------------------------------------------------------ESC[0m
^M 28/30 VM1-000002-delta.vmdk [skipped excluded]
ESC[90m-------------------------------------------------------------------------------------------------------------ESC[0m
^M 29/30 VM1-000002.vmdk [skipped excluded]
ESC[90m-------------------------------------------------------------------------------------------------------------ESC[0m
^M 30/30 VM1-000002-ctk.vmdk [skipped excluded]
ESC[90m-------------------------------------------------------------------------------------------------------------ESC[0m
^MTotal size: 130.00 GB ESC[90m|ESC[0m Done 100.00%
ESC[90m-------------------------------------------------------------------------------------------------------------ESC[0m
I have confirmed that the scsi0:2.ctkEnabled TRUE setting is in the config file and it shows up in the vSphere config page as well.
The vmdk files are stored in different datastores, but their file names are the same - I'm guessing that is what is confusing the XSIBackup software.
Is this a bug that can be fixed, or do I need to manually rename one of the vmdk files? I have several VMs like this so I would really prefer to avoid the latter if at all possible.
Pages: 1