Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

[b]no peer certificate available[/b]
Why are you using TLS if your server does not support it.

You have some orphan VMs that are raising errors (Skipping invalid VM '34'), they could also interfere with the snapshot process.
First of all, please keep your inventory in a usable status and try again.

First of all, just in case you didn't see our post above:

[b]WE DO NOT OFFER SUPPORT FOR THIS SCRIPT AND OTHER THIRD PARTY TOOLS[/b]

XSIBackup users can exchange ideas and code of their own in this forum up to some point that we decide.
Please do not take those upper letters as a shout, but as some official statement from part of 33hops.com: you use third party code at your own risk.

Please read the rest of the post to, at least, have our opinion in regards to purging XSITools repositories.

The "luxury" XSITools offers is measured in compression ratio. If you have a 2.9T disk and pretend to backup a 1.5T disk into it and keep two repositories, then you have some arithmetic problem. Knowing a disk's content on advance necessarily implies reading the disk, so you answered your own question. It would not take twice as much, but at least some 50% more.

What do you mean by "will be switched off"?.
Is the e-mail server actually stopped to make the backup?
A local path means nothing in ESXi, it could be pointing to an NFS or iSCSI device over a network. We asked you to post the output of [b]df -h[/b] command but you didn't do it. We cannot help you if you don't provide the information we ask for.

As stated, XSIBackup is as fast as your hardware is. If you run the above backup job in a quiet server and you get 27 mb/s, then that means that's what your hardware can offer.

Well, it didn't take 24 h. it took 15 h. 20 mins. aproximately which is about 27 mb./s, not a record speed, but if the server is under load while the backup is taking place, then it's not a big surprise.

Backing up 1,5 tb of data on a production server is not a trivial task, you should consider dedicating some hardware resources to the backup process to improve those figures, like using a dedicated NIC connected to a dedicated NAS, all with Intel NICs and professional switch or direct cable. Needless to say when you handle that amount of data 10 gb NICs are something to think about.

Yes, the --date-dir argument allows to do so. Currently it is only available in the Pro version.
[url]https://33hops.com/xsibackup-help-man-page.html#datedir[/url]

Any server supporting SSH is O.K.

The e-mail report, as well as the output contain any errors that might have been raised during the backup job.

We started offering very basic Borg compatibility while we developed our own propietary deduplication system [b](c)XSITools[/b], which has been designed from scratch to deduplicate VMs and since v. 11.1.4 is capable of deduplicating over IP to any file system accessible over SSH.

When we say "very basic" we mean that all virtual disk data is sent tarred (.tar packaged) -as is- from the ESXi server to the Borg host, as there's no possibility to run Borg directly in the ESXi context.

On the other side, being Borg a general purpose tool, it uses a small block size that ends up clogging the Borg server after some hundreds of gigabytes have been added. If you have a powerful Borg server, you may be able to handle some terabytes of data, but the increase in hunger for resources is unavoidable.

In any case, your problem consists in Borg binary not being present in the path of the remote Borg system.

sh: borg: command not found

Which does not mean that you won't hit some other further problem if using Borg 1.1.5, anyhow by now your issue is just that.

Why should you change to 6.5?, we never suggested that. You seem to be having some problems determining the cause of your hardware slugishness.

You are not telling us where are you backing up to, it does not matter if your hardware has many CPUs or a lot of RAM, if you use a cheap switch to connect to some NAS datastore that will make the difference and make any server feature useless.

It looks like XSIBackup is not even able to manage the job error file, so you get no errors in the subject. We published a thorough procedure [b][https://33hops.com/forum/viewtopic.php?pid=1431#p1431]for you to follow[/url][/b]

Please follow it blindly and paste both the backup job and the output in case you need some help.

Be careful not to schedule any cron job until you have tested your backup job manually, and use a valid cron syntax.

XSIBackup is a mature project, many people use it and [b]--backup-prog=Vmkfstools[/b] is the simplest type of backup. Nobody else seems to have this problem. In your case it could be due to some other process being holding the target .vmdk file, but for that to happen you must be overlapping jobs or accessing that file some other way.

Follow this procedure:

- Make sure your host is correctly configured, remove any eventual ghost VMs (deleted from disk but not unregistered) and any dead storage too.
- Connect via SCP and backup your install folder (xsi-dir).
- Remove XSIBackup from your system: [url]https://33hops.com/xsibackup-uninstall-procedure.html[/url]
- Kill any eventual remaining zombie processes in memory

OLDIFS=$IFS;IFS=";";for job in $(ps -c | grep xsi | awk '{print $1}' | \
sed -e ':a;N;$!ba;s/\n/;/g');do kill -9 $job 2>/dev/null;done;IFS=$OLDIFS

- Install from scratch using the User Area ( [url]https://33hops.com/user-login.html[/url] ) installation script, read the output carefully and install to the default location. You need datastore [b]/vmfs/volumes/datastore1[/b] present to be able to perform a default installation.
- Add an SMTP server using the GUI. To invoke the GUI just call [b]xsibackup[/b] file with no arguments (./xsibackup)
- Run this simple backup job.

./xsibackup --backup-prog=Vmkfstools --backup-type=running --backup-point=/vmfs/volumes/backup_ds \
--use-smtp=1 --mail-to=your@email.com

- Once you know it's working add it to the jobs/ folder by appending --save-job to the job string and pressing enter.

./xsibackup --backup-prog=Vmkfstools --backup-type=running --backup-point=/vmfs/volumes/backup_ds \
--use-smtp=1 --mail-to=your@email.com --save-job

Replace by your own --backup-point and e-mail address. In case you still have problems, paste the full output and the backup job so that we have some more information.