Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

You need to manually re-add the independent disk to the .vmx file. Our software prepares the VM to be switched on, it cannot asume it will find a disk it could not backup.

It's a lot easier than that, use [b]--backup-type=running[/b] or [b]--backup-type=all[/b]
Please, read the Man Page before asking for help.
[url=https://33hops.com/xsibackup-help-man-page.html](c)XSIBackup Classic Man Page[/url]

[b]Random Thoughts[/b] kindly pointed you to that document up in this thread.
A Google search by "xsibackup 11 crontab" returns the same URL

Isn't that exactly what's explained here?: [url=https://33hops.com/xsibackup-free-11-things-that-have-changed.html](c)XSIBackup Classic: changes in version 11.0.0[/url]

Thank you for the feedback, you have that information in the first page of the manual:
[url]https://33hops.com/xsibackup-pro-gui-manual.html#1[/url]

Don't worry much, only the wisest entangle in apparently stupid problems. This doesn't explain why your rules were not being added, it doesn't matter what port the remote server uses, the rule must be added to the ESXi firewall.

Please, note that you have left this in in your rule:

 <port>587</port>

To get out of that prompt, which is the bash continuation, type [b]Ctrl+d[/b]
You are pasting some unknown character, type the command manually to make sure that you are entering the right characters.

You must first add the rule

<service id='9999'>
    <id>SMTPout-587</id>
    <rule id='0000'>
        <direction>outbound</direction>
        <protocol>tcp</protocol>
        <porttype>dst</porttype>
        <port>587</port>
    </rule>
    <enabled>true</enabled>
    <required>false</required>
</service>

To the rules file at [b]/etc/vmware/firewall/service.xml[/b]
Once you have done so

esxcli network firewall ruleset set --ruleset-id="SMTPout-587”--enabled=true

Your cron is working, your job files are being called by the cron. You are just one step away. You are missing something, but we can't find it for you.

This is a problem restricted to sending e-mails, so let’s concentrate in this issue and leave everything else apart.
Issue this command:

./xsibackup --check-smtp=some@email.com --use-smtp=2

And let us know if you get the same result, I bet you will.
This looks like an ESXi bug in some build when calling Firewall operations from the command line or a broken firewall more than an XSIBackup issue.
Try adding the firewall command manually at the end of the /etc/vmware/firewall/service.xml file…

<service id='9999'>
    <id>SMTPout-587</id>
    <rule id='0000'>
        <direction>outbound</direction>
        <protocol>tcp</protocol>
        <porttype>dst</porttype>
        <port>587</port>
    </rule>
    <enabled>true</enabled>
    <required>false</required>
</service>

And see what is ESXi’s response when issuing this command

esxcli network firewall ruleset set --ruleset-id="SMTPout-587”--enabled=true

Please, keep in mind that the root crontab permission set is 0600. You need to change it to be able to edit the file with vi.

Depending on the crond implementation, and that can change from one ESXi version to the next, the cron daemon might not execute your crontab if permissions are not 0600.

As you previously had to change them to edit the file, we are asuming you are setting them back to 0600

That is a widely open question with no precise answer.

Mounting your Synology NAS as NFS3 or iSCSI is a trivial task, once you do it your volume will be available as a datastore and you'll be able to backup your VMs there via any of the XSIBackup [b]--backup-prog[/b] programs, except those which are exclusively to be used over IP (Rsync).

Nevertheless, what you stated is "I tested XSITools over IP" which means that you directly tried to backup to your Synology NAS by connecting over IP to the SSH port, which as previously stated is not supported. XSIBackup may be used to backup over IP to other ESXi boxes (version and HW compatible) or to Linux servers, being our distro family of choice RHEL, Fedora, CentOS that is where we certify Linux features.

We don't state that XSITools will work on a Synology OS.