XSIBackup-App Activity
Backup and replicate Linux files, databases and ©VMWare ©ESXi VMs
Brought to you by:
danjgf
Activity for XSIBackup-App
-
XSIBackup-App updated /README.txt
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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...
-
-
1 >