Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

(c)XSIBackup is optimized to work on RHEL familiy of Linux: RHEL, CentOS, Rocky Linux, Alma Linux, Fedora, etc...
Debian has some serious drawbacks:

1/ They have deprecated some classic system calls that (c)ESXi does still use:
[url]https://33hops.com/xsibackup-dc-full-manual-home.html#enable-vsyscall[/url]
That was more than one year ago, thay may have disabled some additional ones.

2/ They enable the iNotify service by default which slows down the FS.

Debian is optimized for security, whereas RHEL is optmized for speed. You can use Debian, but you will have to go through enabling vsyscall and disabling unneded services that may interfere with your backups.

Contact support if you are a registered user and can't get it to work.

Please, post the full job and output when you need some support.

Don't use an SD card to install (c)ESXi. It is discouraged by (c)VMWare:
[url]https://kb.vmware.com/s/article/85685[/url]

You are trying to create a backup repository in [b]/vmfs/volumes[/b], which is a non existent path, therefore the error you are receiving.
Use some subfolder in a datastore, per instance:

/vmfs/volume/backup-ds/repo01

You are not even allowed to create the repo in the root of a datastore which is one level up.

/vmfs/volume/backup-ds/

The path above would also be an illegal target for (c)XSIBackup. Do use some subfolder in a real datastore.

There is some problem with that NFS4 mount.

In branch 6 there use to exist multiple problems around NFS4, in your case it's probably not well mounted, maybe some permission issue or bad configuration parameter.

In any case we would plainly remove the NFS4 volume and reconnect using NFS3. NFS4 (wich includes multipathing) is great to host VMs, in case you are forced somehow to use NFS, cause VMFS is way, way better for the task. NFS4 is totally useless at the time to use one of this volumes to store backups though.

You can't take advantage of multipathing when transferring huge -flat.vmdk files because one single file will never be split across multiple NICs.

Please, provide the FULL backup command and the FULL output. There is vital information in both to help us at the time to offer you some feedback.
If you omit  the job, we don't know what you are trying to accomplish or how.
If you omit the output, we know nothing about your environment: XSIBackup and ESXi versions, local and remote file systems, previous errors, VM names, paths, etc..., etc...

Yes, in the event that you want to experiment with not yet tested scenarios and not very recommendable file systems you could run ©XSIBackup-App in ©VMWare Workstation and attach an NTFS disk, but:

Why would you want to do so when the appliance has been designed to run in ©ESXi and to use XFS or ext 3/4 file systems?

You can't restore to a remote server, you can restore from a remote server though.
Still you are missing the username part in your restore job.

Your best approach is to install (c)XSIBackup 1.6.0.7 alone in the server you want to restore to and pull the backup from there.

xsibackup --restore root@a.b.c.d:22:/mnt/warehouse/20230307114112/Linux-test /vmfs/volumes/datastore1/Linux-production

You can also add your restore target server as a backup host and use the local mount point [b]/mnt/XSI/srvs/192.168.0.5/vmfs/volumes/datastore1/Linux-production[/b] to restore directly. Still be warned that depending on your latency to the target server the second approach may be too slow. In this case use the pull approach instead.

Your REGEXP pattern is being rejected. Why are you using double parentheses?
Check this post: [url=https://www.educative.io/answers/how-to-write-regular-expressions-in-c]How to write regular expressions[/url]

Use something like this:

--exclude="[^/vmfs/volumes/datastorekubedata/kubevols*.]"

Split your logic into different jobs to achieve your goal.
Consider scripting some logic to bring the VM out of the cluster while the backup is taking place.
You may also find useful the "l" option in the [url=https://33hops.com/xsibackup-dc-full-manual-home.html#options]--options argument[/url]

First production ready release will be ready by the end of March 2023

If you renewed then just contact support and ask for the MAC to be freed, so that you can upgrade the software.

We have created an appliance: ©XSIBackup-App that allows to backup any ©ESXi server between 5.1 and 8.0
It allows centralized management of jobs in different ©ESXi servers.

There is a beta version available for download, we have already tested it up to some point with excellent results.

Download from here:
[url]https://33hops.com/xsibackup-2-what-is-new.html[/url]

It lacks a GUI by now, thus you would need to use it from the command line.
Needless to say what we have published by now is a Beta version, use cautiously.

We are preparing ©XSIBackup 2.0 which will be compatible with ©ESXi 8.0.
A beta version will be available in some days.