You are not logged in.
Pages: 1
I have upgraded to the latest XSIBACKUP-PRO version on Srv2, and by the looks of it, when it connected to Srv1 to run the command, it updated the files on Srv1 too, however I cannot restart Srv1. To me it just looks like a replacement of files, is a reboot really necessary?
It shows XSIBACKUP-PRO version 10.2.1 in the log now, but unfortunately the problem remains.
Thanks for the help so far
Yes, it has been renamed to license.key and placed in the xsi-dir.
In the output from the log it also says: "XSIDiff 1.0.5 licensed:" - doesnt that mean it detects it?
Hi,
We just started using xsibackup-pro, but have issues with the size limitations still there after activation. We have used the request.key to get a license.key and uploaded license.key to the xsi dir. The logs shows XSIDiff 1.0.5 licensed as well.
xsibackup-cron-x.x.x.x.log:
2018-01-05T20:02:17| Info: transfering file [ /vmfs/volumes/5a33de03-789b222b-fa1d-78e7d18d8d88/vmname/vmname-flat.vmdk ]
2018-01-05T20:02:17| Info: first Rsync transfer is assumed by XSIDiff, as it is faster and will preserve VMFS data sparseness
XSIDiff 1.0.5 licensed:
File#1 size 107374182400 bytes
*** This is a trial version limited to 10485760000 bytes, parsing 107374182400 ***
Exiting...
This is the command being run from xsibackup-cron:
"/vmfs/volumes/datastore/xsi-dir/xsibackup" --time="Fri 20:00" --backup-point="x.x.x.x:22:/vmfs/volumes/datastore/backup" --backup-type=custom --backup-vms="vmname" --host=x.x.x.x --backup-prog=rsync:z --date-dir=yes --smtp-auth=none --mail-from=servername@domain.com --mail-to=mail@company.com --smtp-srv=x.x.x.x --smtp-port=25 --smtp-usr=any --smtp-pwd=any
Some additional information:
Srv1: runs VM's, have xsibackup-pro installed and licensed
Srv2: have xsibackup-pro installed and licensed. xsibackup-cron runs from this host, but connects to srv1 to run the above command.
How do we get rid of the size limitations?
Pages: 1