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

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#1 General matters » Xsibackup job will not terminate itself » 2019-06-13 17:55:22

drluong
Replies: 1

I set jobs to run in chain. When fail or success, it is suppose launch another job, but the existing job never terminate itself, making it impossible for the next job to run. I have to manually kill all Xsi job in order to run the next job. Here is the error print out:

-rw-r--r--    1 root     root       1698354 Jun 12 21:03 xsibackup-192.168.20.242.log
[root@QALab01:/vmfs/volumes/5cba66ef-fc7d1e2c-48f7-002590c81022/xsi-dir/var/logs] tail -f xsibackup.
log
2019-06-13T04:53:45|  --use-smtp=2 \
2019-06-13T04:53:45|  --mail-to=rluong@jupiter.com \
2019-06-13T04:53:45|  --backup-id=24202 \
2019-06-13T04:53:45|  --description="backup to nas1 for cloud upload" \
2019-06-13T04:53:45|  --exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"
---------------------------------------------------------------------------------------------------------------------------------
2019-06-13T04:53:52|  ERROR: there are some ongoing rsync process/es loaded into memory. Clean them manually \
2019-06-13T04:53:52|            if no backup job is running now -> kill -9 4205476
2019-06-13T04:53:52|  4205598
2019-06-13T04:53:52|  4249595
ERROR: there are some ongoing rsync process/es loaded into memory. Clean them manually

Here is the job running before that error:
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=OneDiff \
--snapshot=doquiesce \
--backup-point=192.168.20.242:22:"/vmfs/volumes/datastore1" \
--backup-type=Running \
--backup-how=Hot \
--use-smtp=2 \
--mail-to=rluong@jupiter.com \
--backup-id=242 \
--description="replicate 19216820242" \
--on-success="backupId->24202" \
--on-error="backupId->24202" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"

This is the job that suppose to run and got the error:
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=XSITools:z \
--host=192.168.20.242:22 \
--override=xsibakfilter \
--backup-point=/vmfs/volumes/datastorenas1/qalab-vm \
--backup-type=All \
--backup-how=Hot \
--del-dirs=+21d \
--use-smtp=2 \
--mail-to=rluong@jupiter.com \
--backup-id=24202 \
--description="backup to nas1 for cloud upload" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"

This happen every time. Any idea in fixing the problem?

Raymond

#2 Re: © OneDiff » Onediff does not register vm the first time » 2019-05-08 17:10:09

In that case, I link my backup together. After running Onediff, I linked Xsitool backup right after it. If the vm is not register, will Xsitool detect the vms to backup?

Thanks

#3 © OneDiff » Onediff does not register vm the first time » 2019-05-08 00:22:24

drluong
Replies: 3

I run onediff on a couple of different vm
The first time onediff finish, the vm is not register. The log said I have to register it manually but the 2nd time I run onediff, it auto register the vm.
I had been using xsibackup for years, but this newest version is the first time I experience this.
I register the software and got change the ket to license.key and put it under xsi-dir folder.
here is my job
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=OneDiff \
--host=10.1.0.198:22 \
--snapshot=doquiesce \
--backup-point=10.1.0.197:22:"/vmfs/volumes/datastore1" \
--backup-type=Running \
--backup-how=Hot \
--use-smtp=2 \
--mail-to=rluong@jupiter.com \
--backup-id=001 \
--description="" \
--on-success="backupId->401" \
--on-error="backupId->401" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"

What am I doing wrong? I would like onediff to register the vm on first run.

Thanks

Board footer