You are not logged in.
Pages: 1
Hello,
I have an issue with a backup of a VM with multiple Snapshots.
Backup process gets stuck at some point with the output as follows:
(c) XSIDiff 1.1.1.4 licensed:
A full file copy will be performed, no meta-data available
Reading from file /vmfs/volumes/nas-01-SSD/vm1/vm1-000007-sesparse.vmdk
Writing to file /vmfs/volumes/backup01/xsiBackup/201812-xsitools/20181206191512/vm1/vm1-000007-sesparse.vmdk
Set input file offset to 0 bytes
100.00% done
Time taken: 19 seconds
Speed 228.16 mb/s
Overall speed 228.11 mb/s
---------------------------------------------------------------------------------------------------------------------------------
Should I expect to have the backup completed after some time ?
The job cmd is:
./xsibackup \
--backup-point="/vmfs/volumes/backup01/xsiBackup/$( date +%Y%m )-xsitools" \
--backup-prog=xsitools:z \
--backup-vms="vm1" \
--backup-type=Custom \
--test-mode=false \
--exec=yes > backlup.log
In the VMware VMs folder there a among other VM files the following files:
-rw------- 1 root root 559.2M Dec 4 08:43 vm1-000001-sesparse.vmdk
-rw------- 1 root root 382 Dec 4 08:43 vm1-000001.vmdk
-rw------- 1 root root 802.2M Dec 4 08:43 vm1-000002-sesparse.vmdk
-rw------- 1 root root 389 Dec 4 08:43 vm1-000002.vmdk
-rw------- 1 root root 401.2M Dec 4 08:43 vm1-000003-sesparse.vmdk
-rw------- 1 root root 389 Dec 4 08:43 vm1-000003.vmdk
-rw------- 1 root root 1.0G Dec 4 08:43 vm1-000004-sesparse.vmdk
-rw------- 1 root root 389 Dec 4 08:43 vm1-000004.vmdk
-rw------- 1 root root 382.0M Dec 4 08:43 vm1-000005-sesparse.vmdk
-rw------- 1 root root 389 Dec 4 08:43 vm1-000005.vmdk
-rw------- 1 root root 1017.0M Dec 4 08:43 vm1-000006-sesparse.vmdk
-rw------- 1 root root 389 Dec 4 08:43 vm1-000006.vmdk
-rw------- 1 root root 4.2G Dec 6 19:47 vm1-000007-sesparse.vmdk
-rw------- 1 root root 389 Dec 6 19:47 vm1-000007.vmdk
-rw------- 1 root root 446.3M Dec 6 21:30 vm1-000008-sesparse.vmdk
-rw------- 1 root root 362 Dec 6 20:50 vm1-000008.vmdk
The last one seems to be still updated (at least the timestamp changes) but the size not.
Any comments ?
Offline
Well, that piece of log your pasted shows /vmfs/volumes/nas-01-SSD/vm1/vm1-000007-sesparse.vmdk was copied, we don't know anything beyond that.
If you keep a chain of snapshots that long, you will start to penalize performance on any operation, specially at the time to delete the backup snapshot. We don't know what you mean by stuck or "some time", these are all relative terms. The process should end sometime somehow: with success or with an error. Paste more concrete information if you want a more detailed answer.
Offline
Pages: 1