Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

If you need help, please first help yourself and help us to help you. You are being extremely imprecise. XSIBackup does not "say" anything, instead it prints information to the terminal or to a log file.

If you want to refer to some event happening in your system, cut&paste the output that illustrates the fenomenon you want to describe, so that we all know what is the exact event we are discussing.

XSIBackup printing out some message stating that the remote host does not exist has nothing to do with linking servers via a public key, so you are most probably making a wrong assumption and basing all your request for help in that assumption.

If XSIBackup states that the remote host does not exist, then it means it can't reach it, thus you are most probably facing a firewall issue instead of a key exchange one. It's easy to note what's going on by taking a look at the output, as XSIBackup is extremely verbose.

Please read the Man Page before posting to this forum:
[url]https://33hops.com/xsibackup-help-man-page.html#backuproom[/url]

To learn about the differences between different backup programs read this post:
[url]https://33hops.com/xsibackup-using-backup-programs.html[/url]

We are subject to experincing issues, just like any other human being. Should you some time hit one of those: contact support in case of being a pro user, or post to the appropiate section in this forum in case of being a Free version user.

When you cut&paste some script, you must take into account that character substitution can occur depending on your page code. Paste to some plain text editor before actually executing it.

There is indeed an [b]Smtp sec:[/b] field in the GUI, please, take a closer look.

ESXi Cron daemon can get picky, follow [b][url=https://33hops.com/xsibackup-cron-troubleshooting.html]this cron troubleshooting guide[/url][/b]

XSIBackup does not allow parenthesis or any other especial character in VM names and/or paths. Use letters numbers spaces, underscores or hyphens. Fix this and it'll work.

That will mainly depend on the GLibc version, it should work. Just give it a try, we can't test all Linux distros, so we stick to RHEL, Fedora, CentOS as our Linux reference family. Nevertheless, you just have to install and activate NFS3 in your Ubuntu box, mount it in an ESXi server and point your backups there. You can even use a nested ESXi server appliance.

[url]https://www.virtuallyghetto.com/2018/04/nested-esxi-6-7-virtual-appliance-updates.html[/url]

If, for some reason, the quick Trivial Check or a full checksum check of the subsequent backups after the first one fail, OneDiff will reset the chain to perform a full backup, in order to start with a valid seed. So the log that we need to assess you is the second run in the OneDiff cycle.

Just one changed bit in a hash check will end up in a different checksum. Most of the times checksum check failures are due to some read, or write error in some part of your virtual disk, which in turn corresponds to some physical sector in the underlying physical media.

This does not mean that the resulting VM is unusable, in fact, most of the times you can switch it on and use it. An XSIBackup full checksum check is unfeasible if the disks are a bit worned out.

Yes, you can delete all those or just start with a default firewall template, whatever you find easier to accomplish.
We have reinforced checks to prevent ghost rules from being added, we never had such case though, if fact there already existed checks around this.

You seem to have passed some SMTP configuration without a port, that generated partial FW rules which were not being detected, so every time you tried, a new one was being generated.

The message is clear:

Error MKROOM01: cannot make 162G of room, only 130G can be made available

Only folders matching the [b]YYYYMMDDhhmmss[/b] mask are considered for deletion, this is clearly stated in the posts covering this topic.

You are ignoring some fundamental information being returned by (c)XSIBackup:

Int value is not found
Firewall rule SMTPout-465 added...
Invalid Ruleset Id.
Int value is not found

XSIBackup is not being able to open the 465 port in the ESXi firewall.

chmod 644 /etc/vmware/firewall/service.xml
vi /etc/vmware/firewall/service.xml

Check at the end of the file whether there's any garbage or half written rute and delete it.
You can of course always manually add the rule via the vSphere client
Or, overwrite the [b]/etc/vmware/firewall/service.xml[/b] file with some default one from other server.

We asked whether the remote ESXi system is a manufacturer build or an official ESXi build as we don't support manufacturer builds, they aren't official VMWare releases and frequently contain arbitrary changes. You should always use official VMWare builds.

This doesn't mean that our software will not work with those manufacturer builds, but that it might cause you issues like the one you are having, that would not be caused by an official VMWare controlled build.

Dell's are not among the worst manufacturer releases that we know and we also know of XSIBackup users that use DELL builds, but believe us when we warn about manufacturer builds in general. They are most of the times just commercial traps for ESXi users.

[b]Solution[/b]

Your remote system is denying access through the exchanged public key, so:
Login into the remote system and edit the following file:

/etc/ssh/sshd_config

The above is the configuration file for the SSHD service on your remote host.
The line

PermitRootLogin yes

Controls whether root login is permitted or not. Set it to [b]yes[/b].
Check the following line:

PubkeyAuthentication yes

Set the [b]PubkeyAuthentication [/b] key to [b]yes[/b]

Once you have made those changes parse the configuration file from the command line to see if its syntax is O.K.

/usr/lib/vmware/openssh/bin/sshd -t

The above is general SSH configuration. Your hardware manufacturer's build might have been manipulated not to allow some SSH functions.