You are not logged in.
We didn't mean that using different versions at the same time on the same repo is a good idea, just that it will work.
If you prune the repo use always the latest version and if you have enough space, rotate the repositories instead of pruning them.
And of course, don't use some older version when you have a newer one available.
You can use the same repo, but use v. 1.4.1.1, it contains some fixes with regards to 1.4.0.0
If you are using some Lenovo build, switch to some VMWare official one, we don't support manufacturer builds, as they contain arbitrary changes with regards to VMWare's official build.
The restore routine does not truncate the virtual disks -flat.vmdk files to their nominal size when restoring them.
When some virtual disk has some closing footer, even if it's just one byte, the last block is backed up as "none zero" and the restore process completes without any issue. Nonetheless, when the virtual disk file has some empty area extending until the end of the file, the restore process just stops at the last non empty block and the restored VM can't be used.
The fix will be contained in version 1.4.1.1, contact us if you can't wait until we release it.
You are mixing [b](c)XSIBackup-DC[/b] and [b](c)XSIBackup-Pro[/b] arguments, they are different programs. To use [b](c)XSIBackup-DC[/b], please read its manual.
[url=https://33hops.com/xsibackup-dc-full-manual-home.html](c)XSIBackup-DC man page[/url]
As explained above, OpenSSH changed recommended formats. We cannot force mailmasters to use new standards if they don't want to. You may in any case convert the key to the older format to try to fit outdated SMTP servers. Simplest thing to do is obviously just use a different SMTP, we support GMail, Yahoo, Hotmail, etc...
a/ We have reorganized arguments and flags to make them be easier to use and resulting jobs more compact.
b/ [b]--on-error[/b] & [b]--on-sucess[/b] were just ways to make users believe they had some easier control on things, also a way to tighten Pro's behaviour up. You could acomplish the same with regular bash control output codes. (c)XSIBackup is a binary, you don't need added arguments to control execution, just create compounded jobs by concatenating jobs in extended bash files, like: [b]job1 && job2 || error[/b]
c/ [b][url=https://33hops.com/xsibackup-dc-full-manual-home.html#rotate]--rotate[/url][/b].
d/ No, you must install (c)XSIBackup-DC to the remote end. In case of Linux servers just copying the main binary [b]xsibackup[/b] to /bin is enough.
e/ Nesting ESXi is not a good idea in production. VMWare does not support nesting, we can't support something that the OS manufacturer does not support, the software still runs, that warning is displayed though.
f/ You should not use external editors to edit job files, you can easily convert the job files to whatever format you want to.
[b](c)XSIBackup-DC[/b] runs in ESXi and in Linux x86_64. You could run it in a VM, but that would only allow you to backup local files in the guest OS.
To backup VMs you must run [b](c)XSIBackup-DC[/b] in the ESXi hypervisor.
[b]writeout[/b] is a function in the [b]src/functions[/b] file. You have whether misplaced that file or not asigned permissions as explained in the README.txt file.
Contact support and we will install the software for you.
Nobody else has reported download corruption problems since years ago. Check that your ISP is offering quality bandwidth and routes.
The issue has been solved, you may try again.
Ops, sorry, we thought that you had replaced the original IP. We'll check the user area download script, maybe something is failing at the time to set the IP. You can just download and install manually, it's even easier than using the script. Read the README.txt file.
We don't publish e-mail addresses in forums, please check the welcome e-mail or send us a contact form.
We did a correction to our previous post, there was a typo. The key that you have to paste in the [b]authorized_keys[/b] file is the public key: [b]xsibackup_id_rsa.pub[/b]
BTW, what do you mean by V7?
[b]unzip: invalid zip magic 0A0D0A0D[/b] is clearly denoting a corrupt .zip file. Download again from a device you know to work well. We have checked the downloadable file in the server and it's fine.
If you still have problems, download and install manually just like [b]sirjamie[/b] did.
That line is O.K., contact support if you need asistance
We followed your issue in VMWare Communities too. We really can't grasp, with the information that you have provided so far, why was this VM failing to be backed up, we have the feeling that it had something to do with the snapshot system, maybe some old snapshot info remained in some config file like .vmsd
We have answered to your post in VMWare Communities with some general advices to help narrow this kind of issues down.
[url=https://communities.vmware.com/t5/Backup-Recovery-Discussions/ERROR-CLDELSN3-details-lon-d-squid-error-cannot-delete-snapshot/td-p/2296933/page/2?start=30]VMWare Communities snapshot issue thread[/url]
We haven't tested [b](c)XSIBackup-NAS[/b] with [b](c)ESXi 7.0[/b], please use some older version. That doesn't mean it can't work, but most probably default OpenSSH configuration is preventing [b](c)ESXi 7.0[/b] from being able to authenticate by public key.
We don't understand what you mean by "[b]ssh does work though on the commandline[/b]", the example you are posing is misleading.
You can't login to [b](c)XSIBackup-NAS[/b] using the (c)XSIBackup-DC RSA key; by running
ssh root@134.28.70.59You are using the default (c)ESXi host key. To use [b](c)XSIBackup-DC[/b]'s RSA key run the code below from the installation dir:
ssh -i xsibackup_id_rsa root@134.28.70.59[b]Update:[/b]
Apart from that, you can easily exchange the key manually, just paste the [b]xsibackup_id_rsa.pub[/b] to its own line in the [b]authorized_keys[/b] file at [b](c)XSIBackup-NAS[/b], it is located in the [b]/root/.ssh/[/b] dir
Use the [b][url=https://33hops.com/xsibackup-dc-full-manual-home.html#add-key]--add-key[/url][/b] action from the command line instead of using the GUI.
The complete message above should be:
You can only link to Linux and (c)VMWare (c)ESXi hosts
Response was: some textCould you provide the response text?: that's where the information is contained.
You need to pass a directory which is the root of a repository for [b][url=https://33hops.com/xsibackup-vmware-esxi-backup.html](c)XSIBackup-DC[/url][/b] to be able to run the [b]--info[/b] argument on some repository.
Please, read the manual, it contains examples and the explanation for each argument.
[url=https://33hops.com/xsibackup-dc-full-manual-home.html](c)XSIBackup-DC man page[/url]
We can't reproduce your issue, our tests of the install routine shows no errors regarding any missing [b]writeout[/b] function.
Nonetheless the [b]writeout[/b] function is all over the software, if it was missing you couldn't run anything.
[root@esxi1:/tmp] ./install
------------------------------
-> XSIBackup Installation <-
------------------------------
This will install XSIBackup to the desired directory
It is recommended that you use the root user for the
installation process, to avoid problems derived from
the lack of privileges.
Just provide the base path, the installation process
will create the XSIBackup-Pro root folder under it.
Where do you want to install XSIBackup to? (/scratch/XSI):
-----------------------------------------------------
XSIBackup will be installed to the following directory:
-----------------------------------------------------
Install dir: /scratch/XSI/XSIBackup-Pro
-----------------------------------------------------
Confirm that you want to install to the directory above (yes/no): yes
-----------------------------------------------------
Backing up configuration files directory...
-----------------------------------------------------
Backing up backup jobs...
-----------------------------------------------------
Backing up logs...
-----------------------------------------------------
Archive: /scratch/XSI/XSIBackup-Pro/XSIBACKUP-PRO.zip
creating: src/
inflating: src/api
inflating: src/cron-init
inflating: src/functions
inflating: src/instcron
inflating: src/mapblocks
inflating: src/onediff
creating: src/pro/
inflating: src/pro/borg
inflating: src/pro/certify
inflating: src/pro/custimgs
inflating: src/pro/esxbackup
inflating: src/pro/events
inflating: src/pro/host
creating: src/pro/menu/
inflating: src/pro/menu/common
inflating: src/pro/menu/config
inflating: src/pro/menu/crond
creating: src/pro/menu/help/
inflating: src/pro/menu/help/addLink.hlp
inflating: src/pro/menu/help/backupHow.hlp
inflating: src/pro/menu/help/backupPoint.hlp
inflating: src/pro/menu/help/backupProg.hlp
inflating: src/pro/menu/help/backupType.hlp
inflating: src/pro/menu/help/backupVMs.hlp
inflating: src/pro/menu/help/crondMain.hlp
inflating: src/pro/menu/help/editJobs.hlp
inflating: src/pro/menu/help/excludeDisks.hlp
inflating: src/pro/menu/help/jobsMain.hlp
inflating: src/pro/menu/help/listLinked.hlp
inflating: src/pro/menu/help/progOptions.hlp
inflating: src/pro/menu/help/regexpVMs.hlp
inflating: src/pro/menu/help/remotePoint.hlp
inflating: src/pro/menu/help/runJobs.hlp
inflating: src/pro/menu/help/schedJobs.hlp
inflating: src/pro/menu/help/setHost.hlp
inflating: src/pro/menu/help/watchJobs.hlp
inflating: src/pro/menu/help/xsiopts.hlp
inflating: src/pro/menu/jobs
inflating: src/pro/menu/link
inflating: src/pro/menu/main
inflating: src/pro/menu/restore
inflating: src/pro/menu/smtp
inflating: src/pro/menu/tools
inflating: src/pro/onediff
inflating: src/pro/onediffcert
inflating: src/pro/restore
inflating: src/pro/smartinfo
inflating: src/pro/vmsregexp
inflating: src/pro/xsitoolschk
inflating: src/pro/xsitprune
inflating: src/sendmail
inflating: src/version
inflating: src/xsitools
inflating: EULA
inflating: xsibackup
creating: bin/
inflating: bin/dd
inflating: bin/dialog
inflating: bin/lzop
inflating: bin/pv
inflating: bin/xsibackup-rsync
inflating: bin/xsidiff
creating: conf/
inflating: conf/dialogrc
inflating: conf/err-imsgs
inflating: conf/smtpsrvs
inflating: conf/xsiopts
-----------------------------------------------------
Applying permissions to files...
-----------------------------------------------------
The software has been installed and permissions were applied
-----------------------------------------------------
Restoring configuration files...
-----------------------------------------------------
Restoring backup jobs...
-----------------------------------------------------
Restoring logs...
-----------------------------------------------------
Do you want to execute (c)XSIBackup now (yes/no): yes
-----------------------------------------------------
###########################################################################
# XSIBACKUP-PRO: END-USER LICENSE AGREEMENT #
###########################################################################
LAST UPDATED: 2018-02-08 (ISO FORMAT YYYY-MM-DD)
PLEASE READ THIS END-USER LICENSE AGREEMENT CAREFULLY BEFORE ACCEPTING IT,
DOWNLOADING OR USING XSIBACKUP-PRO ("APPLICATION"). BY ACCEPTING THE LICENSE
AGREEMENT, DOWNLOADING OR USING THE APPLICATION, YOU ARE AGREEING TO BE BOUND
BY THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS
OF THIS AGREEMENT, DO NOT CLICK ON THE "I AGREE" BUTTON AND DO NOT DOWNLOAD
OR USE XSIBACKUP-PRO.
LICENSE
33HOPS, SISTEMAS DE INFORMACION Y REDES, S.L. GRANTS YOU A REVOCABLE,
NON-EXCLUSIVE, NON-TRANSFERABLE, LIMITED LICENSE TO DOWNLOAD, INSTALL AND USE
XSIBACKUP-PRO SOLELY FOR YOUR PERSONAL, COMMERCIAL OR NONCOMMERCIAL PURPOSES
STRICTLY IN ACCORDANCE WITH THE TERMS OF THIS AGREEMENT.
RESTRICTIONS:
A) YOU AGREE NOT TO, AND YOU WILL NOT PERMIT OTHERS TO: LICENSE, SELL, RENT,
LEASE, DISTRIBUTE, TRANSMIT, OUTSOURCE, DISCLOSE OR OTHERWISE COMMERCIALLY
EXPLOIT XSIBACKUP-PRO OR MAKE XSIBACKUP-PRO AVAILABLE TO ANY THIRD PARTY.
B) YOU ARE ALLOWED TO MODIFY THE SOURCECODE TO TWEAK THE APPLICATION BEHAVIOUR
TO YOUR NEEDS, WITH THE EXCEPTION OF THE EULA AND LICENSE FILES AND ANY CODE
THAT MAY PRINT ON SCREEN. MODIFYING THE CODE TO REMOVE LIMITATIONS OF ANY FREE
OR TRIAL VERSION IS EXPRESSLY FORBIDDEN TOO.
C) YOU CAN USE XSIBACKUP-PRO TO GIVE SERVICE TO YOUR CUSTOMERS, JUST AS LONG
AS THIS SERVICE IS GIVEN EXCLUSIVELY UNDER YOUR OWN FACILITIES AND IS INSTALLED
ON DEVICES OF YOUR EXCLUSIVE PROPERTY.
D) XSIBACKUP-PRO HAS BEEN DESIGNED TO READ DATA FROM ONE PRIMARY LOCATION AND
WRITE THIS SAME DATA TO A SECONDARY LOCATION. THE APPLICATION DOES NOT MODIFY
THE CONTENTS OF THE DATA ON THE PRIMARY LOCATION. THUS THE APPLICATION CREATORS
SHALL NEVER BE RESPONSIBLE FOR ANY PRIMARY DATA LOSS AND YOU IMPLICITLY RECOGNIZE
YOUR RESPONSABILITY TO VERIFY THAT THE SECONDARY DATA HAS BEEN CORRECLTY WRITTEN
INTO THE DESIRED SECONDARY LOCATION.
E) 33HOPS, SISTEMAS DE INFORMACION Y REDES, S.L. WILL NOT ATTEND REQUESTS
REPORTING BUGS ON COPIES OF THE APPLICATION WHICH MD5 HASH IS NOT EXACTLY THE
SAME AS THE ORIGINALLY TRANSMITED UPON THE PURCHASE.
F) ANY SUPPORT REQUESTED FOR A COPY OF THE APPLICATION WICH MD5 CHECKSUM IS NOT
EXACTLY THE SAME AS THE ORIGINAL WILL BE CONSIDERED A SERVICE REQUEST AND WILL
BE SUBJECT TO CHARGE ACCORDING TO THE LAST PUBLISHED TARIFFS.
G) YOU ARE ALLOWED TO USE XSIBACKUP-PRO TO BACKUP UP TO 20 DIFFERENT HOSTS
BELONGING TO A SINGLE ORGANIZATION, IDENTIFIED BY A SINGLE TAX ID NUMBER, FROM
A SINGLE CRONTAB. IF YOU INSTALL THE CRONTAB TO ADDITIONAL SERVERS, YOU MUST BUY
ADDITIONAL LICENSES. THERE IS NOT ANY LIMITATION IN THE NUMBER OF GUESTS YOU MAY
BACKUP UP PER HOST,
MODIFICATIONS:
33HOPS, SISTEMAS DE INFORMACION Y REDES, S.L. RESERVES THE RIGHT TO MODIFY,
SUSPEND OR DISCONTINUE, TEMPORARILY OR PERMANENTLY, XSIBACKUP-PRO OR ANY SERVICE
TO WHICH IT CONNECTS, WITH OR WITHOUT NOTICE AND WITHOUT LIABILITY TO YOU.
TERM AND TERMINATION:
THIS AGREEMENT SHALL REMAIN IN EFFECT UNTIL TERMINATED BY YOU OR 33HOPS, SISTEMAS
DE INFORMACION Y REDES, S.L.
THIS AGREEMENT WILL TERMINATE IMMEDIATELY, WITHOUT PRIOR NOTICE FROM 33HOPS,
SISTEMAS DE INFORMACION Y REDES, S.L., IN THE EVENT THAT YOU FAIL TO COMPLY WITH
ANY PROVISION OF THIS AGREEMENT. YOU MAY ALSO TERMINATE THIS AGREEMENT BY DELETING
XSIBACKUP-PRO AND ALL COPIES THEREOF FROM THE DEVICES IT MIGHT BE INSTALLED TO.
UPON TERMINATION OF THIS AGREEMENT, YOU SHALL CEASE ALL USE OF XSIBACKUP-PRO AND
DELETE ALL COPIES OF XSIBACKUP-PRO FROM YOUR MOBILE DEVICE OR FROM YOUR DESKTOP.
SEVERABILITY:
IF ANY PROVISION OF THIS AGREEMENT IS HELD TO BE UNENFORCEABLE OR INVALID, SUCH
PROVISION WILL BE CHANGED AND INTERPRETED TO ACCOMPLISH THE OBJECTIVES OF SUCH
PROVISION TO THE GREATEST EXTENT POSSIBLE UNDER APPLICABLE LAW AND THE REMAINING
PROVISIONS WILL CONTINUE IN FULL FORCE AND EFFECT.
AMENDMENTS TO THIS AGREEMENT:
33HOPS, SISTEMAS DE INFORMACION Y REDES, S.L. RESERVES THE RIGHT, AT ITS SOLE
DISCRETION, TO MODIFY OR REPLACE THIS AGREEMENT AT ANY TIME.
CONTACT INFORMATION:
IF YOU HAVE ANY QUESTIONS ABOUT THIS AGREEMENT, PLEASE CONTACT US AT 33HOPS.COM
-------------------------------------------------------------------------------
I ACCEPT THE LICENSE AGREEMENT (yes/no) yes
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
You can start now using XSIBACKUP-PRO 11.2.19This is a particular question, please contact support to find out.
We don't know what's going on, just what you are telling us.
[b]writeout[/b] is a function that should be accessible, that error is not normal and should not be overlooked, as it's telling you something is wrong indeed.
Installing (c)XSIBackup is extremely easy, you just need to make sure you remove everything to avoid mixing files, then install again.
Yes, ESXi OS is not persistent. In any case a quick reinstall would solve it if it went beyond what a reboot can fix.
Could be some bug, we'll check that.
Well, the cron is indeed working. We really don't know how you have come to receive that message, it's something about permissions though. It looks line the lack of permissions is afecting something in the installation dir, run this:
cd /scratch/XSI/XSIBackup-Free/
chmod 0700 /scratch/XSI/XSIBackup-Free/xsibackup
chmod -R 0700 /scratch/XSI/XSIBackup-Free/bin