#1 2020-09-27 00:50:55

newmember
Member
Registered: 2018-10-15
Posts: 34

DC and PRO configs

Overall doing backups has lots of options and scenarios to cover and its tough, thanks for giving it a go, its great.


Few questions:

a.
why not follow the same format at PRO, example the "--backup-type=" and :"--backup-point"??
b.
Does DC support "--on-success=" serial backup jobs?
c.
I couldn't set rotation in DC like "--del-dirs=" from PRO
d.
Does DC copy the exec files to the remote host like PRO did?  If yes, then which folder does CD try to copy the exec files too on the remote host?  PRO uses ""/vmfs/volumes/datastore1/xsi-dir/xsibackup" \"
e.
What is with not supporting nested?
-----------------------------------------------------------------------------------------------------------
/!\ Running XSIBackup-DC in a nested host is not supported
-----------------------------------------------------------------------------------------------------------
f.
In general I think that the job files should be yml format, it would help to when using editors to edit the code and submit the code to git repos.





DC:
/scratch/XSI/XSIBackup-DC/xsibackup \
--backup \
"VMs(RUNNING)" \
"root@10.240.100.38:22:/vmfs/volumes/xsi-backup" \
--backup-how="hot " \
--description="esxi_038 " \
--mail-to="cw@ns.com " \
--subject="esxi_038 " \
>> /scratch/XSI/XSIBackup-DC/var/log/xsibackup.log 2>&1



PRO:
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=OneDiff \
--backup-point=/vmfs/volumes/xsi-backup \
--backup-type=Running \
--backup-how=Hot \
--del-dirs=+2d \
--use-smtp=2 \
--mail-to=cw@ns.com \
--backup-id=038 \
--description="038oneDiff" \
--on-success="backupId->039" \
--on-error="backupId->039" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"

Offline

#2 2020-09-27 12:43:59

admin
Administrator
Registered: 2017-04-21
Posts: 1,385

Re: DC and PRO configs

a/ We have reorganized arguments and flags to make them be easier to use and resulting jobs more compact.
b/ --on-error & --on-sucess were just ways to make users believe they had some easier control on things, also a way to tighten Pro's behaviour up. You could acomplish the same with regular bash control output codes. (c)XSIBackup is a binary, you don't need added arguments to control execution, just create compounded jobs by concatenating jobs in extended bash files, like: job1 && job2 || error
c/ --rotate.
d/ No, you must install (c)XSIBackup-DC to the remote end. In case of Linux servers just copying the main binary xsibackup to /bin is enough.
e/ Nesting ESXi is not a good idea in production. VMWare does not support nesting, we can't support something that the OS manufacturer does not support, the software still runs, that warning is displayed though.
f/ You should not use external editors to edit job files, you can easily convert the job files to whatever format you want to.

Offline

Board footer