©XSIBackup-Free: Free Backup Software for ©VMWare ©ESXi

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#1 2020-01-31 16:56:41

magicker
Member
Registered: 2019-06-08
Posts: 13

Reports sucess after failed transfer

Hi there,
We are nearly at the end of our testing phase and generally speaking everything is working as we would expect.

However, we had an incident this morning. The email reported that everything had completed however, a quick manual inspection of the copy showed a few discrepancies in file sizes.  At least 3 of the *flat* files had only partially copied and those vms were not bootable.

---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:32|  [vps2013tvbeds] Starting backup (size is 86123M on 92160M file)
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:32|  XSIBackup will backup your VMs while they are running, so that users can continue to use the VM
2020-01-31T11:04:32|  while the backup is taking place. You can also run --backup-how=cold|warm
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:32|  Hot backup selected for VM: [vps2013tvbeds], will not be switched off
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:33|  [vps2013tvbeds] info: boot partition is MBR
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:33|  Removing snapshots, please wait...
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:35|  Syncronizing config files
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:37|  [vps2013tvbeds] info: created dir to host VM backup
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:39|  [vps2013tvbeds] info: VMX file succesfully queued
2020-01-31T11:04:39|  [vps2013tvbeds] info: VMSD file succesfully queued
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:40|  [vps2013tvbeds] info: VMXF file succesfully queued
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:40|  [vps2013tvbeds] info: NVRAM file succesfully queued
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:04:40|  [vps2013tvbeds] info: VMWare Tools detected, taking snapshot QUIESCED(false)...
2020-01-31T11:04:40|  [vps2013tvbeds] info: set argument --snapshot=doquiesce to quiesce your VMs
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:05:33|  Backing up virtual disks...
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:05:33|  DISK=/vmfs/volumes/datastore2/vps2013tvbeds/vps2013tvbeds-000001-sesparse.vmdk
2020-01-31T11:05:33|  DISK=/vmfs/volumes/datastore2/vps2013tvbeds/vps2013tvbeds-000001.vmdk
2020-01-31T11:05:33|  DISK=/vmfs/volumes/datastore2/vps2013tvbeds/vps2013tvbeds-Snapshot2.vmsn
2020-01-31T11:05:33|  DISK=/vmfs/volumes/datastore2/vps2013tvbeds/vps2013tvbeds.vmdk
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:05:34|  Disk [/vmfs/volumes/datastore2/vps2013tvbeds/vps2013tvbeds-000001-sesparse.vmdk] excluded
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:05:34|  Disk [/vmfs/volumes/datastore2/vps2013tvbeds/vps2013tvbeds-000001.vmdk] excluded
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:05:35|  Rsync file transfer (1st)
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:05:35|  From: /vmfs/volumes/datastore2/vps2013tvbeds/vps2013tvbeds-Snapshot2.vmsn
2020-01-31T11:05:35|  To: /vmfs/volumes/datastore2/10000/20200131080805/vps2013tvbeds/vps2013tvbeds-Snapshot2.vmsn
---------------------------------------------------------------------------------------------------------------------------------
sending incremental file list
vps2013tvbeds-Snapshot2.vmsn
^M         28,656 100%    0.00kB/s    0:00:00  ^M         28,656 100%    0.00kB/s    0:00:00 (xfr#1, to-chk=0/1)

sent 28,762 bytes  received 35 bytes  19,198.00 bytes/sec
total size is 28,656  speedup is 1.00
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:05:37|  Rsync file transfer (1st)
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:05:37|  From: /vmfs/volumes/datastore2/vps2013tvbeds/vps2013tvbeds.vmdk
2020-01-31T11:05:37|  To: /vmfs/volumes/datastore2/10000/20200131080805/vps2013tvbeds/vps2013tvbeds.vmdk
---------------------------------------------------------------------------------------------------------------------------------
sending incremental file list
vps2013tvbeds.vmdk
^M            557 100%    0.00kB/s    0:00:00  ^M            557 100%    0.00kB/s    0:00:00 (xfr#1, to-chk=0/1)

sent 653 bytes  received 35 bytes  1,376.00 bytes/sec
total size is 557  speedup is 0.81
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:05:38|  Info: transfering file | /vmfs/volumes/datastore2/vps2013tvbeds/vps2013tvbeds-flat.vmdk
---------------------------------------------------------------------------------------------------------------------------------
Writing to file /vmfs/volumes/datastore2/10000/20200131080805/vps2013tvbeds/vps2013tvbeds-flat.vmdk

Time taken: 1757 seconds
Speed 49.02 mb/s
Overall speed 52.45 mb/s
---------------------------------------------------------------------------------------------------------------------------------
2020-01-31T11:34:58|  Excluded disks removed from backup .vmx file

How do I go about troubleshooting this?

job:

"/vmfs/volumes/datastore1/XSIBackup-Pro/xsibackup" \
--backup-prog=XSIDiff \
--date-dir=yes \
--backup-point=xxx.xxx.xxx.xxx:22:"/vmfs/volumes/datastore2/10000" \
--backup-type=Custom \
--backup-vms="REGEXP(^v.*)" \
--backup-how=Hot \
--remote-xsipath=/vmfs/volumes/datastore1/XSIBackup-Pro \
--del-dirs=+2d \
--use-smtp=1 \
--mail-to=xxxxx@gmail.com \
--subject="10000" \
--backup-id=001 \
--description="full" \
--exec=yes >> "/vmfs/volumes/datastore1/XSIBackup-Pro/var/logs/xsibackup.log"

Offline

#2 2020-02-03 14:15:00

magicker
Member
Registered: 2019-06-08
Posts: 13

Re: Reports sucess after failed transfer

we are using XSIDiff  ?

(not sure if you answer was meant to be directed at me)

Offline

#3 2020-02-03 18:42:57

admin
Administrator
Registered: 2017-04-21
Posts: 2,057

Re: Reports sucess after failed transfer

Opss!, sorry we messed up.

(c)XSIDiff uses a syncronous loop, it depends on a reliable TCP/IP stack, it's not good over unstable connections. In any case the fact that you see less used space in the target -flat.vmdk does not necessarily mean that you lost data, as XSIDiff is zero aware, it can punch some zeros and produce a sparse disk which contains less data than the original but is still an exact copy and even produces the same checksum result.

Contact support to provide as much details as possible on this issue and use Rsync instead if you are copying data over some network that you can't trust.

Offline

Board footer