You are not logged in.
Thank you for the feedback!
If you are talking about XSIBACKUP-FREE, you can just copy the files to any other host. There isn't really any installation process apart from copying the files and asigning execute permissions.
You do have random and very nasty errors on copy. It's nothing with XSIBackup, the errors are returned by [b]vmkfstools[/b], which is a more than well tested tool, so, I would start by facing the truth, specially if it's a production machine.
You don't offer much information, being a 4 x 4tb RAID is generic information. If your device is a NAS and it has an OS you have all the tools that your NAS's OS may offer you to check the FS it may use, but it doesn't seem to be a filesystem related problem at all. It could be something as simple as a cable, a failing switch or a driver issue.
I would use one of your 4 tb. disks as a directly attached datastore, that way you would have a B plan.
It should not be necessary, but the ESXi cron daemon is "so basic", that any minimum error may hang it or even duplicate it into memory. Be careful and give it a try without a restart, just leave it as your last resource.
I think you should pose that question in the VMWare ESXi Community Forum, it is a general ESXi/ vCenter question.
You do need SSH Access to the host to use XSIBackup
Thank you for your feedback, we'll take your comments into account.
Hello Rado, your problem is very simple: XSIBackup cannot contact smtp.gmail.com on port 465 because something is blocking the connection. You can believe us or not, determining the cause why this is happening is something you'll have to find.
We are sorry that you are stuck with it, but asking the same again won't modify the answer.
On top of that, only the root user would have the appropiate set of permissions needed to add a key to the remote system or restart services, thus using a regular user would only be possible to copy data, just that.
You cannot espeficy a username in the [b]--backup-point[/b] argument by now.
Compatibility with other *NIX systems has been introduced only in the latest versions of XSIBackup and support by now is limited to the implicit user you are logged in at the ESXi system, that due to the nature of ESXi can only be [b]root[/b] or another user with almost the same set of permissions.
A workaround by now would be creating a user with the needed permissions to execute XSIBackup successfully (as commented above only a user with a full set of permissions could work), and then run XSIBackup under that user's security context. XSIBackup would then use that user to authenticate against the remote system.