Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

That is an old video.
No, you are not doing it right it is much simpler than that.
[url]https://33hops.com/xsibackup-composing-esxi-backup-jobs.html[/url]

The above link comes out first when looking for "XSIBackup configure job" in Google
Run the job on screen to make sure it works, then just append [b]--save-job=001[/b] ([url=https://33hops.com/xsibackup-help-man-page.html#savejob]--save-job[/url])

The job will be saved as <install-dir>/etc/jobs/001

Then add the schedule to the [b]<installation-dir>/conf/root-crontab[/b] file

0 2 * * * /vmfs/volumes/datastore11/xsi-dir/jobs/001

Once you have saved the above run: ./xsibackup --update-cron=root

You are doubling figures in your cron schedule, that is not neccesary and may lead to errors. On the other side the syntax you are using for the weekday is probably too complicated for ESXi (0-6/2)

Use some simpler cron syntax, ESXi cron service IS NOT a full featured Linux cron service, it is a cut down version running from Busybox.

0-6 is equivalent to an asterisk (*) for the weekday thus you don't need anything in the weekday column.

Thank you for your positive feedback.
Are you sure you are running Pro version?
Are you sure you are running the jobs you have posted and not other jobs?
Be carefull if you edit the job files externally not to change line delimiters, i.e.: \n by \r\n, or spaces by some other Unicode character. This may happen without you noticing.
Be careful not to cut&paste directly from Word documents or web pages, similar character substitution may take place.

Jobs are placed in <install-dir>/etc/jobs/...
Appending arguments to --run-backup is useless

You can also run some job interactively by doing something like:
(That way you will be sure that you are running the job you want)

/scratch/XSI/XSIBackup-Pro/etc/jobs/001 &
tail -f /scratch/XSI/XSIBackup-Pro/var/logs/xsibackup.log

And over all, --on-success and --on-error are just artifacts that in the end cross the river to get water, so that people feel there is some argument to chain jobs. You may just concatenate jobs as you would do with any Linux subprocess.

Run job 001 and then job 002, no matter what happens with job 001:

/scratch/XSI/XSIBackup-Pro/etc/jobs/001 ; /scratch/XSI/XSIBackup-Pro/etc/jobs/002

Or...

/scratch/XSI/XSIBackup-Pro/etc/jobs/001
/scratch/XSI/XSIBackup-Pro/etc/jobs/002

Run job 001 and if successfull run job 002:

/scratch/XSI/XSIBackup-Pro/etc/jobs/001 && /scratch/XSI/XSIBackup-Pro/etc/jobs/002

Run job 001 and if it does not succeed don't run 002 but run job 003:

/scratch/XSI/XSIBackup-Pro/etc/jobs/001 && /scratch/XSI/XSIBackup-Pro/etc/jobs/002 || /scratch/XSI/XSIBackup-Pro/etc/jobs/003

Etc...

This way of invoking the cron has been deprecated years ago:

--time="Mon 02:00|Wed 02:00|Fri 02:00|Sun 02:00"

To use the cron:

- Install it: ./xsibackup --install-cron
- Add your schedules to the root crontab at: <installation-dir>[b]/conf/root-crontab[/b]
- Update the ESXi crontab: ./xsibackup --update-cron

If you have upgraded to [b](c)XSIBackup-Pro 11.2.15[/b] or above, that is not the right license key. New license keys begin by the MAC address, thus it should be something like:

a417f35a8bc5_...

In that case you should regenerate a new license key, the old ones can be deleted once you have set the new ones up.
Please, read the change log before upgrading your software.

[url=https://33hops.com/xsibackup-change-log.html](c)XSIBackup Classic Change log[/url]

We don't guarantee some value added features like that on Free version.

Just like you need to know how to use some tool before actually using it, i.e. a wrench, you need to know what deduplication is before using it.
[url=https://en.wikipedia.org/wiki/Data_deduplication]Deduplication on Wikipedia[/url]

Apart from that, Free version does not allow to restore deduplicated backups, thus, if you just want to perform simple backups, do not use --backup-prog=Xsitools:z, but --backup-prog=Vmkfstools instead.

Great!. The best fail at the simplest tasks ;-) we know that by experience.

If you run the command as a user, the log is redirected to STDOUT, that is, your active TTY. When you save a job the output is redirected to the general log at <install root>/var/logs/xsibackup.log

The simplest solution is to use a different SMTP server. If you still want to dedicate time to solve that, read this post.

[url=https://33hops.com/forum/viewtopic.php?id=543]Post on key format issues[/url]

In (c)ESXi 7.0.0 only plain backups made by using [b]--backup-prog=vmkfstools[/b] are supported by (c)XSIBackup-Free.

This is due to (c)VMWare having made some drastic changes in the way ESXi behaves. New [b](c)ESXi 7.0.0[/b] blocks read access to all files, including the -flat.vmdk files all the time, even when a snapshot has been taken. These changes lead to all backup methods other than [b]--backup-prog=vmkfstools[/b] being useless.

On addition, we haven't announced compatibility with ESXi 7 so far. (c)XSIBackup-DC will indeed be compatible with ESXi 7.0 from version 1.3.0.0

Are your .vmdk disks named in capital letters fro some reason?, we have never seen this, but in ESXi they are always named lower case.
That is most probably the culprit of all your issues.