Activity for 33HOPS
-
33HOPS modified a wiki page
File layout
-
File layout
-
Linux free block level deduplication backup solution
-
Linux free block level deduplication backup solution
-
Linux free block level deduplication backup solution
-
Linux free block level deduplication backup solution
-
Linux free block level deduplication backup solution
-
Linux free block level deduplication backup solution
-
Linux free block level deduplication backup solution
-
Some ©ESXi versions reset cbt after a hard reboot. This forces to reset the CBT configuration to prevent loosing data or corrupting your backups. We have added some logic to handle this kind of situation. Download latest ©XSIBackup version here.
-
Some ©ESXi versions (still to determine) produce broken -ctk.vmdk files after a hard reboot. This forces to reset the CBT configuration to prevent loosing data or corrupting your backups. We have added a mechanism to detect this bug and produce full backups based on our delta algorithm along with an error and a notice to reset CBT. We have confirmed this to happen in ©ESXi 6.7.0. It only happens when you reboot the server with VMs on, without previously switching them off. Even when you switch them...
-
Some ©ESXi versions (still to determine) produce broken -ctk.vmdk files after a hard reboot. This forces to reset the CBT configuration to prevent loosing data or corrupting your backups. We have added a mechanism to detect this bug and produce full backups based on our delta algorithm along with an error and a notice to reset CBT. We have confirmed this to happen in ©ESXi 6.7.0. It only happens when you reboot the server with VMs on, without previously switching them off. Even when you switch them...
-
Some ©ESXi versions (still to determine) produce broken -ctk.vmdk files after a hard reboot. This forces to reset the CBT configuration to prevent loosing data or corrupting your backups. We have added a mechanism to detect this bug and produce full backups based on our delta algorithm along with an error and a notice to reset CBT. We have confirmed this to happen in ©ESXi 6.7.0. It only happens when you reboot the server with VMs on, without previously switching them off. Even when you switch them...
-
Some ©ESXi versions (still to determine) produce broken -ctk.vmdk files after a hard reboot. This forces to reset the CBT configuration to prevent loosing data or corrupting your backups. We have added a mechanism to detect this bug and produce full backups based on our delta algorithm along with an error and a notice to reset CBT. We have confirmed this to happen in ©ESXi 6.7.0. It only happens when you reboot the server with VMs on, without previously switching them off in a controlled manner,...
-
Some ©ESXi versions (still to determine) produce broken -ctk.vmdk files after a hard reboot. This forces to reset the CBT configuration to prevent loosing data or corrupting your backups. We have added a mechanism to detect this bug and produce full backups based on our delta algorithm along with an error and a notice to reset CBT. Download latest ©XSIBackup version here.
-
©XSIBackup-App: on network latency and throughput.
-
©XSIBackup-App: on network latency and throughput.
-
We have just posted a working copy of the xsibackup-update.sh file which wasn't working as expected. We are sorry about the inconvenience. This time of the year we don't have as many resources as the rest of the season and not being a critical issue we postponed the fix until today. Please follow the ©XSIBackup-App Change Log for more detailed information on the new features and fixes:
-
We have just posted a working copy of the xsibackup-update.sh file which wasn't working as expected. We are sorry about the inconvenience. This time of the year we don't have as many resources as the rest of the year and not being a critical issue we postponed the fix until today. Please follow the ©XSIBackup-App Change Log for more detailed information on the new features and fixes:
-
If some remote replica dir is deleted partially, per instance, if you delete some -flat.vmdk file but you don't delete the .map directory containing the data definitions, subsquent jobs running on the same remote dir will result in data loss, as the client will believe the files defined by the .blocklog files inside the .map dir do exist. Some versions of ©ESXi do just that when you remove some VM from disk. The whole VM folder is not removed as it should happen and an indetermined number of files...
-
If some remote replica dir is deleted partially, per instance, if you delete some -flat.vmdk file but you don't delete the .map directory containing the data definitions, subsquent jobs running on the same remote dir will result in data loss, as the client will believe the files defined by the .blocklog files inside the .map dir is correct. Some versions of ©ESXi do just that when you remove some VM from disk. The whole VM folder is not removed as it should happen and an indetermined number of files...
-
When this happens only one of the two hosts is allowed to register. This was due to a lacking space character and is fixed in version 1.0.0.10. See change log for all changes: ©XSIBackup-App Change Log
-
This issue was solved in v. 2.0.0.5
-
When you backup some VM that is running in the same server as the backup server, being the latter a virtual machine and you are using the very same NIC to get the source data and to push it to the backup server, the final checksum collects garbage and fails, even though the backup completes consistently.
-
When you backup some VM that is running in the same server as the backup server, being the latter a virtual machine and you are using the very same NIC to get the source data and to push it to the backup server, the final checksum collects garbage and fails, even though the backup completes consistently.
-
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...
-
You need to install the OpenWRT package "kmod-nf-nathelper-extra" to be able to traverse the router with a VPN to reach a guest in the LAN network. https://forum.openwrt.org/t/new-openwrt-blocks-lan-to-wan-vpn-connections/89847/3
-
©XSIBackup-App: on network latency and throughput.
-
You need to install the OpenWRT package "kmod-nf-nathelper-extra" to be able to traverse the router with a VPN to a guest in the LAN network. https://forum.openwrt.org/t/new-openwrt-blocks-lan-to-wan-vpn-connections/89847/3
-
Please, read this post to have a clear idea on how ESXi networking behaves, in special WAN transfers and also how low end hardware affects data transmission. VMWare ESXi throughput limitations
-
Use OpenSSH tunneling feature to reach any host in a remote network through an SSH connection.
-
Leave your questions on (c)XSIBackup-Classic in this forum if you will
-
Leave your questions about this appliance here. Don't forget to read the post describing its usage here: https://33hops.com/vmware-esxi-nat-with-custom-firewall.html If you believe there's something that can be improved or explained better post your comments here too.
-
Leave your questions about this appliance here.
-
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
-
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
-
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/
-
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.
-
Please, from now on, leave your comments, questions, feature requests, etc.. at https://33hops.com/forum/
-
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...
-
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...
-
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?
-
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.
-
The fact that in the first log that you published, XSIBackup was not able to grab...
-
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...
-
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...
-
Try to do one thing, first of all, let's filter out the cdrom/s by adding this piece...
-
Don't worry, that can happen... Just one thing, do use user friendly datastore names,...
-
Don't worry, that can happen... Just one thing, do use user friendly datastore names,...
-
Don't worry, that can happen... Just one thing, do use user friendly datastore names,...
1 >