There exist new features in ©VMWare ©ESXi 8.0 that hinder the possibility to run software not certified by ©VMWare. Nonetheless there exist some workarounds that allow to run newer ©XSIBackup editions without any restriction. This applies also to running any other software able to run in ©ESXi 8.0. The post below will offer you the clues. use with caution. Run ©XSIBackup in ©VMWare ©ESXi 8.0 ©XSIBackup 1.7.0.0 is now compatible with ©ESXi 8.0 Download ©VMWare ©ESXi 8.0 backup compatible version
There exist new features in ©VMWare ©ESXi 8.0 that hinder the possibility to run software not certified by ©VMWare. Nonetheless there exist some workarounds that allow to run newer ©XSIBackup editions without any restriction. This applies also to running any other software able to run in ©ESXi 8.0. The post below will offer you the clues. use with caution. Run ©XSIBackup in ©VMWare ©ESXi 8.0
You can use ©XSIBackup-DC to backup ©ESXi 5.1 to 7.0 Or ©XSIBackup-App appliance to backup VMs in ©ESXi 5.1 to 8.0 from a centralized multiserver console. Both of the above allow to backup VMs up to 100 GB to local storage for free wthout any time limit and offer full functionality during the trial period. The trial period is hardcoded in the binary. We release new versions every few days. ©XSIBackup-Classic was deprecated years ago due to changes in the ©ESXi hypervisor. It will work with ©ESXi...
You can use ©XSIBackup-DC to[ backup ©ESXi 5.1 to 7.0](https://https://33hops.com/xsibackup-vmware-esxi-backup.html) Or ©XSIBackup-App appliance to backup VMs in ©ESXi 5.1 to 8.0 from a centralized multiserver console. Both of the above allow to backup VMs up to 100 GB to local storage for free wthout any time limit and offer full functionality during the trial period. The trial period is hardcoded in the binary. We release new versions every few days. ©XSIBackup-Classic was deprecated years ago...
You can use ©XSIBackup-DC to backup ©ESXi 5.1 to 7.0 Or ©XSIBackup-App appliance to backup VMs in ©ESXi 5.1 to 8.0 from a centralized multiserver console. Both of the above allow to backup VMs up to 100 GB to local storage for free wthout any time limit and offer full functionality during the trial period. The trial period is hardcoded in the binary. We release new versions every few days. ©XSIBackup-Classic was deprecated years ago due to changes in the ©ESXi hypervisor. It will work with ©ESXi...
You can use ©XSIBackup-DC to backup ©ESXi 5.1 to 7.0 Or ©XSIBackup-App appliance to backup VMs in ©ESXi 5.1 to 8.0 from a centralized multiserver console. https://33hops.com/xsibackup-app-detailed-installation-instructions.html Both of the above allow to backup VMs up to 100 GB to local storage for free wthout any time limit and offer full functionality during the trial period. The trial period is hardcoded in the binary. We release new versions every few days. ©XSIBackup-Classic was deprecated years...
You can use ©XSIBackup-DC to backup ©ESXi 5.1 to 7.0 https://33hops.com/xsibackup-vmware-esxi-backup.html Or ©XSIBackup-App appliance to backup VMs in ©ESXi 5.1 to 8.0 from a centralized multiserver console. https://33hops.com/xsibackup-app-detailed-installation-instructions.html Both of the above allow to backup VMs up to 100 GB to local storage for free wthout any time limit and offer full functionality during the trial period. The trial period is hardcoded in the binary. We release new versions...
Hello, I would like to ask whether the Classic version will support ESXi 7.0 or not? Thank you.
Leave your questions on (c)XSIBackup-Classic in this forum if you will
Please contact us through our forum at https://33hops.com/forum/ (c)XSIBackup: VMWare ESXi Backup
Please contact us through our forum at https://33hops.com/forum/ (c)XSIBackup: VMWare ESXi Backup
Please contact us through our forum at https://33hops.com/forum/ (c)XSIBackup: VMWare ESXi Backup
Please contact us through our forum at https://33hops.com/forum/ (c)XSIBackup: VMWare ESXi Backup
Please contact us through our forum at https://33hops.com/forum/ (c)XSIBackup: VMWare ESXi Backup
We have created this post to help troubleshoot the ESXi cron service: https://33hops.com/xsibackup-cron-troubleshooting.html Please contact us through our forum at https://33hops.com/forum/ (c)XSIBackup: VMWare ESXi Backup
Please contact us through our forum at https://33hops.com/forum/ (c)XSIBackup: VMWare ESXi Backup
Sorry about the delay. Please contact us through our forum at https://33hops.com/forum/ (c)XSIBackup: VMWare ESXi Backup
Please, use the forum at our website: https://33hops.com/forum/ (c)XSIBackup: (c)VMWare (c)ESXi Backup
I am afraid we didn't receive it, please, send it again. (c)XSIBackup: (c)VMWare (c)ESXi Backup
O.K., I guess you mean 6.0 Update 2, it could be equivalent to 6.0.2 somwhow, but VMWare does not use that naming. That version is tested and XSIBackup works well in it. Send us a form: https://33hops.com/formulario-de-contacto.asp so that we can send you the software via e-mail. There may be some sort of curruption in the copy you are using. Did you edit it in any text editor? (c)XSIBackup: (c)VMWare (c)ESXi Backup
Sorry about the delay. Please contact us through our forum at https://33hops.com/forum/ Todownload the latest versions visit: https://33hops.com/xsibackup-vmware-esxi-backup.html
Hello, Thanks for your work on making this product freely available. I've got a box running ESXi 6.7.0 and want to know if that version is supported? Thanks.
im issue is now fixed
Hi, In my, EXSI SSH [root@localhost:/vmfs/volumes/5c38e7c0-9554d197-eb7f-000c29a098f9/xsi-dir] /vmfs/volumes/datastore1/xsi-dir/xsibackup or EXSI SSH [root@localhost:/vmfs/volumes/5c38e7c0-9554d197-eb7f-000c29a098f9/xsi-dir]./xsibackup Why i always get this error 1. /vmfs/volumes/datastore1/xsi-dir/xsibackup: line 1: arithmetic syntax error I install fresh version xsibackup 11.0.1 from main site, still same issue. I have read this artical https://33hops.com/xsibackup-tutorial-1.html in that artical...
Before to execute the commands bellow: (xsi-dir)# ./xsi-backup --install-cron (xsi-dir)# ./xsi-backup --link-srv=192.168.10.XX My job file 001: "/vmfs/volumes/datastore1/xsi-dir/xsibackup" \ --backup-prog=Rsync \ --backup-point="192.168.10.XX:22:/vmfs/volumes/datastore1/backup:D" \ --backup-how=Hot \ --backup-type=custom \ --backup-vms="WIN_SERVER" \ --certify-backup=yes \ --use-smtp=1 \ --time="Mon 22:00|Tue 22:00|Wed 22:00|Thu 22:00|Fri 22:00|Sat 12:00|Sun 12:00" \ --backup-id=001 \ --mail-to=<email>@gmail.com...
Home
Crontab
Crontab
We have created this post to help troubleshoot the ESXi cron service: https://33hops.com/xsibackup-cron-troubleshooting.html
Please, leave your doubts, feature requests and questions at https://33hops.com/forum/ This forum is closed
have ran through the check lists and the cron is running the trouble shooting looks good i can run the following line and back up the server stright away as i wanted it to but i put this line in the xsibackup-cron file and does not run , does not error and the cron job log does not show anything any ideas /vmfs/volumes/5a3787d3-5cf19bfe-095a-0024817e5a65/xsi-dir/xsibackup --time="Thu 12:20" --del-dirs=-d5 --backup-point=/vmfs/volumes/primary/backups --backup-type=custom --date-dir=yes --backup-vms="gavtestwin10"...
have ran through the check lists and the cron is running the trouble shooting looks good i can run the following line and back up the server stright away as i wanted it to but i put this line in the xsibackup-cron file and does not run , does not error and the cron job log does not show anything any ideas /vmfs/volumes/5a3787d3-5cf19bfe-095a-0024817e5a65/xsi-dir/xsibackup --time="Thu 12:20" --del-dirs=-d5time --backup-point=/vmfs/volumes/primary/backups --backup-type=custom --date-dir=yes --backup-vms="gavtestwin10"...
Please, from now on, leave your comments, questions, feature requests, etc.. at https://33hops.com/forum/
Please, from now on, leave your comments, questions, feature requests, etc.. at https://33hops.com/forum/
Please, from now on, leave your comments, questions, feature requests, etc.. at https://33hops.com/forum/
Hi, Had a look at the board and didn't see this issue so posting here hoping someone might be able to help. I get the following detailed below, It says it can't find but then finds the rsync binary - rsync is 100% installed on the remote host The CLI command I used was: ./xsibackup --backup-point="172.31.0.40:22:/export/galileo/ESXi/" --backup-prog=rsync \ --backup-how=hot --backup-type=custom --date-dir=yes --backup-vms="sflowpro" --mail-from="borg@xxxxxxxxx.org.uk” \ —mail-to="phil@xxxxxxxx.org.uk"...
Hi, Had a look at the board and didn't see this issue so posting here hoping someone might be able to help. I get the following detailed below, It says it can't find but then finds the rsync binary - rsync is 100% installed on the remote host The CLI command I used was: ./xsibackup --backup-point="172.31.0.40:22:/export/galileo/ESXi/" --backup-prog=rsync \ --backup-how=hot --backup-type=custom --date-dir=yes --backup-vms="sflowpro" --mail-from="borg@xxxxxxxxx.org.uk” \ —mail-to="phil@xxxxxxxx.org.uk"...
Hi, Had a look at the board and didn't see this issue so posting here hoping someone might be able to help. I get the following detailed below, It says it can't find but then finds the rsync binary - rsync is 100% installed on the remote host The CLI command I used was: ./xsibackup --backup-point="172.31.0.40:22:/export/galileo/ESXi/" --backup-prog=rsync \ --backup-how=hot --backup-type=custom --date-dir=yes --backup-vms="sflowpro" --mail-from="borg@qcontinuum.org.uk” \ —mail-to="phil@qcontinuum.org.uk"...
Good afternoon everyone! A few days ago I'm having trouble with the scheduled cron jobs. On several servers I have received the message below: Destination disk format: VMFS thin-provisioned Cloning disk '/vmfs/volumes/infra/compras-ti/compras-ti-000001.vmdk'... Clone: 100% done. 2017-09-13T03:36:57| Excerpt --------------------------------------------------------------------------------------------------------------------------------- 2017-09-13T03:36:57| Hot backup selected for VM: [cofre], will...
hi all, when xsi backup runs, it makes the disk thin and doesnt keep it as thick provisioned is there anyway to do this? many thanks, rob
XSIBackup tunnels Rsync data through OpenSSH. Different ESXi builds might contain different OpenSSH versions. That message seems to be just a warning, but it does in fact bring the tunnel down. It is a bug in OpenSSH_7.3 https://marc.info/?l=openssh-unix-dev&m=147309628200704&w=2 Run this: /usr/lib/vmware/openssh/bin/ssh -V To determine your OpenSSH version and downgrade or upgrade your system, depending on if VMWare fixes this soon or not. VMWare is a great enterprise and has brought out great software...
Please, post to https://33hops.com/forum/, this forum is closed now.
I have looked, but I cannot seem to find anything which resolves this issue. Probably just missing it, if so, sorry. But, I have been following the video tutorials (great by the way) to get XSIBackup going, and all appears OK, but I get no emails. This is the report which it produces within the PuTTY terminal (I have edited some specifics where that might be sensitive, otherwsie it is just a cut and paste) ... 2017-05-03T13:11:59| Opening port 587 for SMTPout-587 service... sh: 0: unknown operand...
Please, from now on, leave your comments, questions, feature requests, etc.. at https://33hops.com/forum/
That's excellent and solves the problem for me.
No, just go ahead and let XSIBackup mark the EULA as read. As you skipped it in the installation phase, just make sure now that the file is writable: # chmod 0700 EULA From the install dir
No, just go ahead and let XSIBackup mark the EULA as read.
That is the idea, using a resource that is visible to all servers. In any case, remember that we kept XSIBackup a script in sake of flexibility, so you can use something like: xsidefaultpath: /vmfs/volumes/HD1-$(hostname -f 2>/dev/null) To have an automatic custom path per server. If you move the xsidefaultpath down in the header of the script, we have done that already on our part, you can use the previously assigned vars, like: xsidefaultpath: /vmfs/volumes/HD1-$HOSTNAME or xsidefaultpath: /vm...
I have not. If I missed that part in the installation documentation, I apologize. There is a "EULA" file in the installation directory already. Do I need to do something to it to make this work? Thanks! Matt
Hi Daniel. I wouldn't be opposed to having that uniformity. That said, the naming convention for the drives allows us to see what we have at a glance and how the drives are configured. Further, in vSphere, you can't replicate drive names across multiple servers - each, apparently, must be unique. If I only need to deal with the drama for the initial install, I can live with that. My single concern is what happens when I run the script to do a backup and the default path is different per server. I'll...
Thank you for sharing. When you want to deploy to a number of servers, you need to pre-stablish a deployment plan backboned by some sort of uniformity. I'll explain my self: the xsidefaultpath should be shared by all subsidiary servers, so that XSIBackup replicates itself to the same path. We'll think about switching that fixed variable into an argument, so that you could set it by backup job, instead of being a fixed XSIBackup envirnoment variable. Nevertheless, forcing to have a fixed set of rules...
Thank you for sharing. When you want to deploy to a number of servers, you need to pre-stablish a deployment plan backboned by some sort of uniformity. I'll explain my self: the xsidefaultpath should be shared by all subsidiary servers, so that XSIBackup replicates itself to the same path. We'll think about switching that fixed variable into an argument, so that you could set it by backup job, instead of being a fixed XSIBackup envirnoment variable. Nevertheless, forcing to have a fixed set of rules...
Thank you for sharing. When you want to deploy to a number of servers, you need to pre-stablish a deployment plan backboned by some sort of uniformity. I'll explain my self: the xsidefaultpath should be shared by all subsidiary servers, so that XSIBackup replicates itself to the same path. We'll think about switching that fixed variable into an argument, so that you could set it by backup job, instead of being a fixed XSIBackup envirnoment variable. Nevertheless, forcing to have a fixed set of rules...
Thank you for sharing. When you want to deploy to a number of servers, you need to pre-stablish a deployment plan backboned by some sort of uniformity. I'll explain my self: the xsidefaultpath should be shared by all subsidiary servers, so that XSIBackup replicates itself to the same path. We'll think about switching that fixed variable into an argument, so that you could set it by backup job, instead of being a fixed XSIBackup envirnoment variable. Nevertheless, forcing to have a fixed set of rules...
Path issues when using --host command I've moved this subject here from private email so the conversation might be more useful to more people - I'd be surprised if I'm the only guy that's run into this and it is worth documenting. Long and short of it: I've got 10 physical VMWare servers running vSphere under v5.5. Each server has 2 hard drives. 192.168.10.6 is the master, so-to-speak and is where I've installed XSIBackup Pro. I'll insert the remainder of the email conversation now, to bring the...
Path issues when using --host command I've moved this subject here from private email so the conversation might be more useful to more people - I'd be surprised if I'm the only guy that's run into this and it is worth documenting. Long and short of it: I've got 10 physical VMWare servers running vSphere under v5.5. Each server has 2 hard drives. 192.168.10.6 is the master, so-to-speak and is where I've installed XSIBackup Pro. I'll insert the remainder of the email conversation now, to bring the...
Just tell XSIBackup to copy the VMs you want it to copy: --backup-type=custom --backup-vms="CENTOS#2,WIN7#1" Please, read the man page at: https://33hops.com/xsibackup-help-man-page.html
Just tell XSIBackup to copy the VMs you want it to copy: --backup-type=custom --backup-vms="CENTOS#2,WIN7#1" Please, read the man page at: https://33hops.com/xsibackup-help-man-page.html
Have you copied the EULA file to the installation dir?
Have you copied the EULA file to the installtion dir?
Disk exclusions working very well, but i need do a backup all runing vm without some vmachines. Please add a vm exclusions to --backup-vms option. Example: We have 3 vm runing DEBIAN#1 CENTOS#2 WIN7#1 In my opininion command syntax might look like this: --backup-type=running --backup-vms="!DEBIAN#1, CENTOS#2!CENTOS#2.vmdk;CENTOS#2_1.vmdk" Desired result: backup contain: CENTOS#2 (without excluded disks), WIN7#1
When running version 9.0.1, it asks me every time to accept the EULA. Of course, I'm accepting it but it gives the following error immediately after hitting "y" to accept: sed: EULA: No such file or directory I'm assuming it is supposed to create/touch a file somewhere to indicate the EULA has been accepted for future runs of the tool but I don't know where it is looking for this file or why it isn't being created. Things work fine otherwise and the backup tool does run and function properly. Any...
If the device refuses to be queried, all I can tell is contact the manufacturer or try to find more specific information. I do not know that particular piece of hardware, nor what driver you are using for ESXi.
I get: Error getting Smart Parameters: CANNOT open device The problem seems to be the LSI MegaRAID SAS3108 PCIe 3.0 Controller. Maybe should be possible to get the values with megacli/storcli/smartctl? Thanks a lot.
I get: Error getting Smart Parameters: CANNOT open device The problem seems to be the LSI MegaRAID SAS3108 PCIe 3.0 Controller. Maybe should possible to get the values with megacli/storcli/smartctl? Thanks a lot.
ok. thank you. Also today at night cron job works ok. Maybe i had problem in cron....
The fact that in the first log that you published, XSIBackup was not able to grab...
hm. this night job cron working ok. I'm confused. (((
No there are no any vCenter, only ESXi with web ui. DRS no used, only nfs
No there are no any vCenter, only ESXi with web ui. DRS no used only nfs
It seems pretty clear that the VM was not there when the crontab called XSIBackup...
It seems pretty clear that the VM was not there when the crontab called XSIBackup...
"test" and "sdh_prod_test" are same VMs i cut name when copy to post (think that...
The only VM that showed up in your initial post is called "test" not "sdh_prod_t...
Please, post the cron, the manual backup job and any relevant information that helps...
Install Xsibackup 9.0.1 free, on ESXi 6 U2 Works fine, but in one moment it start...
Install Xsibackup 9.0.1 free, on ESXi 6 U2 Works fine, but in one moment it start...
Install Xsibackup 9.0.1 free, on ESXi 6 U2 Works fine, but in one moment it start...