Forum ©XSIBackup: ©VMWare ©ESXi Backup Software
MenuYou are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: General matters » PID management issue » 2019-10-01 06:06:16
Reading the code of xsibackup script (lines 382 to 475, XSIBackup-PRO 11.2.10) makes me believe that cron job will run if:
1) --exec=yes argument is provided
OR
2) --time=... argument is provided
The latter is not used with ESXi cron, IIRC; therefore, --exec=yes argument is mandatory for ESXi cron jobs.
The bug mentioned in the OP could be fixed in line 398: s/remote/cron/
Right?
#2 Re: General matters » PID management issue » 2019-09-30 12:41:14
admin wrote:
It does for us, please re-check.
Double re-checked. I cannot even provide you a job log file, as it is created, but remains empty.
#3 Re: General matters » Chain of remote backup jobs » 2019-09-30 12:32:34
admin wrote:
Backup Ids must be 000-999 numeric strings
Yes, they are. "EEE" and "SSS" are just substitutions for generality.
In my case --on-error="backupId->102" and --on-success="backupId->102".
#4 Re: General matters » PID management issue » 2019-09-30 09:33:54
admin wrote:
Yes, that is the issue, you should not use the --exec=yes argument (we didn't see it at first glance). It is reserved for internal use of the program and it is an indicator that the command was launched remotely. You won't see it in the manual, maybe in some older post where we explained how to launch from an external cron.
Tested on XSIBackup-PRO 11.2.10
It does not work as cron job without --exec=yes argument.
#5 General matters » Chain of remote backup jobs » 2019-09-27 15:23:45
- hebasto
- Replies: 2
When a remote job, with specified --host, has --on-error="backupId->EEE" and/or --on-success="backupId->SSS" options and is executed via cron, a remote host searches for "EEE" and/or "SSS" backup jobs (without effect).
Such behavior seems a bit awkward. Maybe do not pass --on-error and/or --on-success to a remote host?
#6 Re: General matters » PID management issue » 2019-09-26 19:47:17
Thank you for clarification.
#7 Re: General matters » PID management issue » 2019-09-25 19:43:10
Could the relevant code be here (at around line 390):
if [ -z $from ] && [ "$launched" == "cron" ]
then
rsyncbusy=0
if [ $( ps | grep xsibackup-rsync | wc -l ) -gt 0 ]
then
rsyncbusy=1
fi
if [ "$exec" = "yes" ]
then
if [ "$rsyncbusy" -eq "1" ]
then
writeout "ERROR: there are some ongoing rsync process/es loaded into memory. Clean them manually \
if no backup job is running now -> \e[1mkill -9 $( ps -c | grep rsync | awk '{print $1}')\033[0m"
exit 0
fi
righttime=1
echo "$$ remote" >> "${PWD}/xsibackup-pid"
...?
#8 Re: General matters » PID management issue » 2019-09-25 10:31:23
[root@esxi02:~] cat /vmfs/volumes/backup/xsi-dir/jobs/111
"/vmfs/volumes/backup/xsi-dir/xsibackup" \
--description="ONCE: Mirror Abso to esxi01:DS-2" \
--backup-id="111" \
--backup-prog="onediff:l" \
--backup-point="10.0.0.51:22:/vmfs/volumes/datastore2" \
--backup-type="custom" \
--backup-vms="Abso" \
--backup-how="warm" \
--shutdown-wait="30" \
--mail-to="hebasto@fastmail.fm" \
--use-smtp="1" \
--img-list="none|none|none|none|none|none" \
--exec=yes > \
"/vmfs/volumes/backup/xsi-dir/var/logs/$(date '+%Y%m%d%H%M')-111.log" \
2>&1#9 General matters » PID management issue » 2019-09-25 09:23:00
- hebasto
- Replies: 10
From VMWare Backup - XSIBackup: pid management:
XSIBackup process types:
• cron: this type is launched from the xsibackup-cron file without any user intervention.
• remote: if backup job is launched from a different host, this type is registered in the xsibackup-pid file.
But I've got a "remote" process type instead of a "cron" one for a backup job launched from the same (local) host:
[root@esxi02:~] head /vmfs/volumes/backup/xsi-dir/var/logs/201909250905-111.log
2019-09-25T09:05:03| ###############################################################################
2019-09-25T09:05:03| XSIBACKUP-PRO 11.2.10: new execution request
2019-09-25T09:05:03| ###############################################################################
2019-09-25T09:05:03|
2019-09-25T09:05:04| NOTICE: (c) XSIBackup kills any user launched jobs, make sure you don't overlap manual jobs
---------------------------------------------------------------------------------------------------------------------------------
XSIBackup PID: 118123 esxi02.pci.net.ua
Wed, 25 Sep 2019 09:05:03 +0000 IPv4: 10.0.0.110/255.255.0.0
VMware ESXi 6.0.0 build-2809209 (c) Rsync 3.1.0 as opt. dependency
---------------------------------------------------------------------------------------------------------------------------------[root@esxi02:~] cat /vmfs/volumes/backup/xsi-dir/xsibackup-pid
118123 remote#10 © XSITools » Remote --check-xsitoolsrepo » 2019-09-16 15:37:11
- hebasto
- Replies: 0
Is it possible to launch --check-xsitoolsrepo on remote host using --host=... option?
#11 General matters » Compatible Borg version » 2019-09-14 13:10:09
- hebasto
- Replies: 1
Trying to restore a VM:
/vmfs/volumes/backup/xsi-dir/xsibackup --restore-vms=10.0.0.200:22:/esxiI get an error:
###############################################################################
#
# (c) XSIBACKUP-PRO 11.2.10 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com
#
###################################################################################
--------------------------------------------------------------------------------------------------------------------------------------------------------------
RESTORE VIRTUAL MACHINES:
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Detected OpenSSH server at 10.0.0.200:22 and folder at "/esxi"
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Checking the type of backup...
--------------------------------------------------------------------------------------------------------------------------------------------------------------
That looks like a Borg repository
Could not find a compatible Borg version at 10.0.0.200:22
--------------------------------------------------------------------------------------------------------------------------------------------------------------
KilledThe actual Borg version at 10.0.0.200 host is
$ borg -V
borg 1.1.5Which Borg version is compatible with XSIBACKUP-PRO 11.2.10 ?
#12 Re: © XSITools » XSITools fails to create backup repo » 2019-09-14 12:19:35
admin wrote:
This issue has been solved today, version 11.2.9 is already available to all Pro users.
It works with empty blocks as expected. Thanks.
#13 General matters » Doing warm backup does not report about VM start » 2019-08-20 07:59:27
- hebasto
- Replies: 1
Email report does not contain VM start time:
Done warm backup (id: 101) using onediff (no compression)
Mirroring following VMs to 10.0.0.51:22:/vmfs/volumes/datastore1...
(Id)VM Name State Size (Gb) Stop Copy Start Time (min:sec) Speed (mb/s)
(6) AEOD-eLib ON 216.48/ 329.80 OK (Shutdown) OK - 33:59 108/ 165
Complete backup elapsed time: 34 min
The ESXi configuration was saved to 10.0.0.51:22:/vmfs/volumes/datastore1
#14 Re: © XSITools » XSITools fails to create backup repo » 2019-08-20 05:37:33
admin wrote:
So XSIBackup will rebuild the VM without issue.
Unfortunately, this is not the case. Restoring from a backup repo fails as well.
Let me remind that it seems XSITools does not write full copy to the repo at all (while creating the repo).
#15 © XSITools » XSITools fails to create backup repo » 2019-08-15 05:12:21
- hebasto
- Replies: 7
Using XSIBackup-PRO 11.2.8
vmware -v
VMware ESXi 6.0.0 build-2809209/vmfs/volumes/datastore1/xsi-dir/xsibackup --backup-prog=xsitools:z --check-repo=yes --backup-point="/vmfs/volumes/datastore2/xsitools-repo-local" --backup-type="custom" --backup-vms="Abso_XSIBAK" --override=xsibakfilterSome excerpts from the output:
Backup program is: xsitools
-------------------------------------------------------------------------------------------------------------------------------------------
--backup-point created at /vmfs/volumes/datastore2/xsitools-repo-local (filesystem: VMFS-5)
-------------------------------------------------------------------------------------------------------------------------------------------
WARNING: the </vmfs/volumes/datastore2/xsitools-repo-local> dir is not an XSITOOLS repo, it will be initialized
-------------------------------------------------------------------------------------------------------------------------------------------
...
VMs to backup:
-------------------------------------------------------------------------------------------------------------------------------------------
6 Abso_XSIBAK [datastore1] Abso/Abso.vmx windows7Server64Guest vmx-11
-------------------------------------------------------------------------------------------------------------------------------------------
Calculating sizes...
-------------------------------------------------------------------------------------------------------------------------------------------
Needed room: 71 Gb.
Sparse size: 278 Gb.
Available room: 285 Gb.
-------------------------------------------------------------------------------------------------------------------------------------------
[Abso_XSIBAK] Starting backup (size is 73540M on 284706M file)
-------------------------------------------------------------------------------------------------------------------------------------------
XSIBackup will backup your VMs while they are running, so that users can continue to use the VM
while the backup is taking place. You can also run --backup-how=cold|warm
-------------------------------------------------------------------------------------------------------------------------------------------
Hot backup selected for VM: [Abso_XSIBAK], the VM is off though
-------------------------------------------------------------------------------------------------------------------------------------------
[Abso_XSIBAK] info: boot partition is MBR
-------------------------------------------------------------------------------------------------------------------------------------------
[Abso_XSIBAK] info: Win64 OS (windows7Server64) detected on MBR, applying Windows algorithm
-------------------------------------------------------------------------------------------------------------------------------------------
Removing snapshots, please wait...
-------------------------------------------------------------------------------------------------------------------------------------------
Syncronizing config files
-------------------------------------------------------------------------------------------------------------------------------------------
Backing up virtual disks...
-------------------------------------------------------------------------------------------------------------------------------------------
DISK=/vmfs/volumes/datastore1/Abso/Abso.vmdk
DISK=/vmfs/volumes/datastore1/Abso/Abso_1.vmdk
-------------------------------------------------------------------------------------------------------------------------------------------
(c) XSIDiff 1.1.1.4 licensed:
A full file copy will be performed, no meta-data available
Reading from file /vmfs/volumes/datastore1/Abso/Abso.vmdk
Writing to file /vmfs/volumes/datastore2/xsitools-repo-local/20190814123307/Abso_XSIBAK/Abso.vmdk
Set input file offset to 0 bytes
100.00% done
Time taken: 1 seconds
Speed 1.00 mb/s
Overall speed 0.00 mb/s
-------------------------------------------------------------------------------------------------------------------------------------------
Blocksize is 52428800 bytes
-------------------------------------------------------------------------------------------------------------------------------------------
Compression has been set
-------------------------------------------------------------------------------------------------------------------------------------------
Backing up via XSITools
-------------------------------------------------------------------------------------------------------------------------------------------
File name: Abso-flat.vmdk, File size: 191158550528
Block size: 52428800, Block count: 3647
Disk usage: 74902929408
-------------------------------------------------------------------------------------------------------------------------------------------
3647/3647 blocks | Processed 100%
Previous block count: 0
Current block count: 1476
-------------------------------------------------------------------------------------------------------------------------------------------
Time taken: 2832 seconds
Avg speed: 64 mb/s
-------------------------------------------------------------------------------------------------------------------------------------------
(c) XSIDiff 1.1.1.4 licensed:
A full file copy will be performed, no meta-data available
Reading from file /vmfs/volumes/datastore1/Abso/Abso_1.vmdk
Writing to file /vmfs/volumes/datastore2/xsitools-repo-local/20190814123307/Abso_XSIBAK/Abso_1.vmdk
Set input file offset to 0 bytes
100.00% done
Time taken: 1 seconds
Speed 1.00 mb/s
Overall speed 0.00 mb/s
-------------------------------------------------------------------------------------------------------------------------------------------
Blocksize is 52428800 bytes
-------------------------------------------------------------------------------------------------------------------------------------------
Compression has been set
-------------------------------------------------------------------------------------------------------------------------------------------
Backing up via XSITools
-------------------------------------------------------------------------------------------------------------------------------------------
File name: Abso_1-flat.vmdk, File size: 107377328128
Block size: 52428800, Block count: 2049
Disk usage: 2209349632
-------------------------------------------------------------------------------------------------------------------------------------------
2049/2049 blocks | Processed 100%
Previous block count: 1476
Current block count: 1550
-------------------------------------------------------------------------------------------------------------------------------------------
Time taken: 311 seconds
Avg speed: 329 mb/s
-------------------------------------------------------------------------------------------------------------------------------------------
</vmfs/volumes/datastore2/xsitools-repo-local/20190814123307/Abso_XSIBAK> is an (c)XSITools repo VM directory
-------------------------------------------------------------------------------------------------------------------------------------------
Checking XSITools Repo:
-------------------------------------------------------------------------------------------------------------------------------------------
XSIBackup will only check the VM folder: /vmfs/volumes/datastore2/xsitools-repo-local/20190814123307/Abso_XSIBAK
This are the deduplicated data files to check:
-------------------------------------------------------------------------------------------------------------------------------------------
/vmfs/volumes/datastore2/xsitools-repo-local/20190814123307/Abso_XSIBAK/Abso-flat.vmdk
/vmfs/volumes/datastore2/xsitools-repo-local/20190814123307/Abso_XSIBAK/Abso_1-flat.vmdk
-------------------------------------------------------------------------------------------------------------------------------------------
1551/1551 blocks | Processed 100%
1 bad blocks detected
49886561f8e26ed5e2ae549897a28aaab44881bd
Block 49886561f8e26ed5e2ae549897a28aaab44881bd is missing
-------------------------------------------------------------------------------------------------------------------------------------------
The ESXi configuration was saved to "/vmfs/volumes/datastore2/xsitools-repo-local/20190814123307"
-------------------------------------------------------------------------------------------------------------------------------------------
Errors detected in backup, check logs
-------------------------------------------------------------------------------------------------------------------------------------------The error "Block ... is missing" appears every time I try to backup VM with XSITools.
Also note that disk space has not decreased by 71 GB, as one might expect.
What am I doing wrong?
Pages: 1