Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

XSIBackup makes use of the snapshot options available in the ESXi system, it does not decide anything in regards to how big the snapshots will be, with the exception of the [b]includememory[/b] option: [url=https://33hops.com/xsibackup-help-man-page.html#snapshot](c)XSIBackup snapshots[/url]. Thus, the size of the snapshot will depend on your VM config and how you use your data.

The way snapshots are managed by [b]XSIBackup[/b] depends on the type of backup you are performing, please, provide some minimum information to get a concrete response. If you are performing an Rsync backup, XSIBackup will preserve the snapshots on the remote end. Some people might find it extremely useful to keep the snapshots on the backed up VM, you can consolidate them by deleting the snapshots.

We have updated the information here:

[url=https://33hops.com/xsibackup-pro-borgbackup-support.html]Deprecated (c)XSIBackup Borg support[/url]

Regarding Borg backups, depending on the Linux/ Unix distro you use, you may need to exchange keys manually to enable passwordless communication, although with CentOS, RHEL, Fedora and FreeBSD you can use the [b]--link-srv[/b] command to achieve this goal.

It might work with other OSs too, if they pledge to [b]init.d[/b] or [b]systemd[/b] standards. Key exchange will work with almost any OS that has OpenSSH installed, the weakest point is service restart, but you can fix that with a full reboot.

You don't have to, have you run the command ./xsibackup [b]--install-cron[/b]?
Please, read the docs, it's all there:

[url=https://33hops.com/xsibackup-cron-how-to.html]XSIBackup Cron How to[/url]

You even have an explanatory video, step by step in Youtube:

[url=https://www.youtube.com/watch?v=hv2JPdVjglA&t=53s]Youtube video[/url]

### Forum admin 2017-08-02 ###

1 - XSITools is a dedupication tool, you can't use it to backup to an inline already deduplicated FS like LessFS. Well, you can do whatever you want, but it's useless, you want get any benefit and it will soon clogg your hardware.

2 - XSITools stores chunks of data in repositories, you can't turn on a VM backed up in an XSITools repository, you must first restore it to a regular datastore.

### Support ###

You will get better results if you use XSITools on a NAS device with a regular FS like EXT4, EXT3 or XFS, as their limits are far beyond VMFSs, in any case VMFS should offer you margin enough to accumulate some Tb of data.

Have you used the restore command to restore the VM from the XSITools repository?, or you are trying to switch it on directly from the repo?.

For this type of personalized support requests, please contact Support if you are a Pro user, we'll be glad to help you. The forum should be used for more general topics.

You have different approaches to solve this situation:

- [url=https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-0591F865-91B5-4311-ABA6-84FBA5AAFB59.html]Create Affinity Rules[/url] to prevent VMs from migrating while being backed up

- Disable the vMotion VMkernel interface

This URL covers the topic in detail:
[url=https://www.yellow-bricks.com/2017/01/17/disable-drs-single-host-cluster/]Disable DRS[/url]

Disabling the vMotion interface before the backup job and enabling it again once it finishes is probably something to take on account.

[b]The nitty gritty details:[/b]

To disable DRS for Virtual Machine Kernel port:

- List IPv4/6 ports: esxcli network ip interface ipv4/6 get

Once we have the port names, we can enable/disable them as needed.

vim-cmd hostsvc/vmotion/vnic_set [vnic] 
vim-cmd hostsvc/vmotion/vnic_set vmk0
Disabling vMotion Port:
vim-cmd hostsvc/vmotion/vnic_unset [vnic]
vim-cmd hostsvc/vmotion/vnic_unset vmk0

I really don't know what was happening to you, but it has to be some sort of missunderstanding, or something you asume works in a different way. There are thousands of XSIBackup users, we launch cron jobs every day, and although some people have had trouble with hanged crond services, nobody ever reported this issue.

Remove the [b]root@[/b] and try again. If you get the error, that means that the receiving party does not allow implicit authentication. If that's the case, editing the OpenSSH config file might do it.

In any case you're the only user with this problem, so whatever the problem is has to be related to the config on your destination server. Please provide all the details to ask for further help. We still don't know what your backup server is at 192.168.0.115: ESXi?

Paste your full log so that we have all the relevant information.

I don't see any line in the SMTP conversation confirming delivery, like:

235 2.7.0 Authentication successful
250 2.1.0 Ok
250 2.1.5 Ok
354 End data with <CR><LF>.<CR><LF>
250 2.0.0 Ok: queued as 81409211B7
221 2.0.0 Bye

Port 25 is generally reserved for inter-SMTP communication, maybe that's your problem. Try using 587 instead or use a different server.

We had already taken this feature request into account for future releases, but it will be added to the Pro version only. It will most probably come out this summer with [b]XSIBACKUP-PRO 10[/b]