Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

You are right. That was not only a way to suggest to make the cli syntax more readable, but also a call to split code.

Instead of a monolithic "xsibackup" binary, a master, light binary "xsibackup", o shorter "xsi" with real commands implemented in ad hoc binaries.

Not a new idea at all. Just to make life easier to developers and new users.

For instance:

xsi repo unlock --root=/vmfs/volumes/nfs03/replica --force

would run "bin/xsi-repo" binary with command "unlock" and "--root=/vmfs/volumes/nfs03/replica --force" options.

Download link warns registered users to download XSIDirector from their user page, but I can't find such link as a logged-in user.

I found the [b].locked[/b] file. Thanks.

In the meantime

./xsibackup --check=full /vmfs/volumes/san03/vm42

finished, wrote that all replicated files are OK, but then it wrote [b]Segmentation fault[/b] again and terminated:

SIGTERM (11) condition was trapped: check logs for more details

Cleaning up...

Segmentation fault

Logs contain no more error info than what is written to the terminal.

I double checked permissions, but they seem OK.

Replication target path is on a VMFS datastore connected to a multipathed iSCSI target.

Talking of usability and readability - maybe for xsi 2.0 or even xsi 3.0 - what about a redesigned command line with object-action pattern in mind?

xsi help

xsi host backup --file=/vmfs/volumes/nfs03/vmhost021-esxi-cfg-20210511.tgz

xsi vm backup --repo=/vmfs/volumes/nfs03/backup

xsi vm replica --repo=/vmfs/volumes/nfs03/replica --names=server01,server02,server03 --quiesce

xsi repo check --root=/vmfs/volumes/nfs03/backup

xsi repo repair --root=/vmfs/volumes/nfs03/backup

xsi repo unlock --root=/vmfs/volumes/nfs03/replica --force

xsi config add-key

xsi config export --file=/vmfs/volumes/nfs03/xsibackup-cfg-20210511.zip

et cetera.

Sorry, I meant provide a new action to [b]xsibackup[/b] to "fire and forget" a job interactively.

Maybe, **--queue** is not the right name. What about **--run**?

xsibackup --run 000

[b]xsibackup[/b] should run in background and detach from the terminal.

I created the [b]cfgbak[/b] directory and, after last run of xsibackup, at least one replication job created the compressed archive with ESXi configuration data.