Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

No, you can't ignore errors, you are missing files, it looks like you have mixed XSIBackup-Free and XSIBackup-Pro files on the other one.
You can install to one server and from there backup up to 19 additional ones, you don't need to install to each individual server apart from the license not allowing it.

Please, [b][url=https://33hops.com/xsibackup-uninstall-procedure.html]remove XSIBackup[/url][/b] from both servers and install to one of them, then link the master server to the secondary one.

./xsibackup --link-srv=1.2.3.4:22

And lauch backups in the second server by using the [b]--host[/b] argument. The GUI also allows to create remote jobs.

Nonetheless you seem to have some sort of misconception on how snapshots work. You said "it still took a snapshot of the disk". Snapshots can't be controlled on a per disk basis, a snapshot will indeed affect all disks in a VM, excluding the disk at the backup job level is a different thing and has nothing to do with wether the snapshot is taken or not for that particular disk.

Use some REGEXP that mathes the full disk path, not just the file name.

OpenSSH is throwing a clear error: [b]Permission denied (publickey,keyboard-interactive)[/b]
You may believe to have linked both servers but you have not.

Now the next questions are:

- What is the other host?: OS, version...
- Is the other OpenSSH version compatible in KEX and cipher algorithms?.

Your ESXi system is 5.1, if the remote counterpart is too distant in main version number you would need to analyze what ciphers and KEX algorithms are in use in every system, just to determine whether setting some value manually can overcome your issue.

Make sure the [b]xsibackup_id_rsa[/b] key is present at the remote server's authorized_keys file and run the below command from the [b](c)XSIBackup-Pro[/b] installation root.

ssh -vvv -i xsibackup_id_rsa root@x.x.x.x "echo HI"

It will show a verbose log that you can use to determine what the issue is.

[b](c)XSIBackup-Pro[/b] uses SSH to transfer data, it is as compatible for remote transfers as your systems at play are. If you get into complicated situations that require analyzing the SSH conversation and finding workarounds you depend on your own knowledge of general purpose Linux tools such as OpenSSH.

If you are trying to copy data from ESXi 5.1 to some new Linux distro or ESXi version, you will be hitting some cipher incompatibility issue. The easiest way to workaround the issue is to use some older Linux or ESXi version as the target that is indeed compatible with your current set of cipehrs and KEX. Or even easier, use some shared datastore that you can mount on both ESXi/ Linux hosts via NFS3.

Should you need some additional help, we can provide it as an additional consultancy service.

You can't just copy data from one server to another, you need to be athenticated.
To do so, link both servers by means of the [b]--link-srv[/b] argument.

./xsibackup --link-srv=1.2.3.4:22

Or using the GUI: [url=https://33hops.com/xsibackup-pro-gui-manual_1.html#2]Exchange RSA keys thrugh the (c)XSIBackup-Pro Classic GUI[/url]

You also have an spurious unneded slash in your job.

The message is indeed delivered, the issue is on your SMTP server.

The source in the xsibackup file, you need some minimum Bash coding skills to do that.
If that's not the case, just inspect the VM .vmx file to find out why the program complains about those missing disks

For some reason the GUI was abruptly terminated and left its lock file (.guilock) there, just remove it manually.
From the install dir.

# rm -rf .guilock

This will rarely happen, as the GUI will trap Linux signalling, like Ctrl+C and still delete the lock file on exit.

We fixed that link.

I'm afraid it won't. It's not something we decided, but VMWare. ESXi 7 blocks all files for reading, thus we needed to develop an alternative solution that reads data from the SCSI disk.

[url=https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-7-0-0-build-15843807-flat-vmdk-files-are-read-locked/m-p/518670](c)ESXi 7.0 - Flat files locked when snapshot is taken[/url]

If you read the above post, please just pay attention to continuum, the other specialist didn't grasp what we were talking about.

All editions will be ported to use DC technology soon.

Something unexpected in your VM layout. Check what disks are attached to the VM and whether all of them are present.
Remember Free version is not compatible with ESXi 7

1.4.0.0 was released, please feel free to offer feedback on it