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

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


Forum menu Menu

You are not logged in.

Pages: 1

#1 Re: General matters » Success/Error scripts not running » 2019-01-03 07:23:50

mikei

Hmm, must be something on my install then...

But if you're going to deprecate the execprog modifier anyway, then I will go the route of putting the script inside a jobfile - I tested this yesterday and that way it works as intended without a problem. Thanks for pointing me in this direction.

#2 Re: General matters » Success/Error scripts not running » 2018-12-31 16:11:04

mikei

Thanks for your feedback - I'll try the script inside a job file tomorrow.

One thing I just noticed is that running the backup job with a --on-success/--on-error script defined wipes the scriptfile - that is, it becomes an empty file - I'm not sure how I missed that.

So I'm wondering: since re-editing the backup job in the gui gives the string "execprog-" instead of the script (note the missing ">"), could it be that when executing the script, xsibackup does not fully remove the "execprog->" placeholder from the --on-success/--on-error content, thus the command becomes 

>/vmfs/volumes/local-ssd/scripts/success.sh

(leaving the ">" at the begining of the command string) - effectively overwriting/wiping the script file place instead of executing it?

So, a related question - should I contact 33hops directly regarding this possible bug (via the contact form?) or do they frequent these forums too?

In the meantime, happy new your to everyone,
Mike

#3 General matters » Success/Error scripts not running » 2018-12-31 06:25:59

mikei
Replies: 6

I'm trying to get success/error scripts to work with backup jobs defined from the GUI, and I can't seem to get them to work... Maybe I'm misunderstanding how this should work?

When creating/modifying a backup job I can enter the path to the success/error script in the GUI, and the GUI seems to find the script (because when I let the path point to a non-existing script it complains that it can't find the file). However, on running the backup job, I get the message "Tip: no chained backups scheduled, set --on-success and/or --on-error arguments to chain a backup", and neither the success nor the error script is run.

Then, when I re-edit the job, both the success/error paths now show "execprog-" in both fields, not the path to the script files entered previously.

Here is the configuration of the job:

"/vmfs/volumes/local-ssd/xsi-dir/xsibackup" \
--backup-prog=Vmkfstools \
--snapshot=includememory,doquiesce \
--backup-point=/vmfs/volumes/NFS-Backup/esxi/script_test/xsibackup_export \
--backup-type=Custom \
--backup-vms="vm1" \
--backup-how=Hot \
--backup-id=004 \
--description="Script Test" \
--del-dirs=+14d \
--on-success="execprog->/vmfs/volumes/local-ssd/scripts/success.sh" \
--on-error="execprog->/vmfs/volumes/local-ssd/scripts/error.sh" \
--exec=yes >> "/vmfs/volumes/local-ssd/xsi-dir/var/logs/xsibackup.log"

Both the success.sh and error.sh files exist and are executable, running them from the commandline works fine.

Is there any way to get the scripts to work?

Thanks, Mike

Edit: forgot to add: I'm running xsibackup Pro 11.2.0

Pages: 1

Board footer