Registered users
Linkedin Twitter Facebook Google+
Close

In order to improve user's experience and to enable some functionalities by tracking the user accross the website, this website uses its own cookies and from third parties, like Google Analytics and other similar activity tracking software. Read the Privacy Policy
33HOPS, IT Consultants
33HOPS ::: Proveedores de Soluciones Informáticas :: Madrid :+34 91 663 6085Avda. Castilla la Mancha, 95 - local posterior - 28700 S.S. de los Reyes - MADRID33HOPS, Sistemas de Informacion y Redes, S.L.Info

XSIBackup Datacenter.

Change log

  1. 1.1.0.0
    • Improvements: additional file buffering is performed on the server side so that the update of virtual disks and hash tables is turned into an atomic operation, that is, an inode re-assignment. This makes --replicas a lot more resilient, as any file transfer that is interrupted will be re-taken from a 0 offset This guarantees file and hashmap consistency.
    • Improvements: .vmdk files are checked against its stored hashes before starting a --replica job. When some change is detected the hash tables for all disks are rebuilt to match the underlying data. This allows to switch on the --replica VMs without having to delete the replicated folder and start from scratch, and: what is more important, you don't have to remind to keep --replica consistency by hand.

      Since this version (1.1.0.0) the server installation will require the xsilib binary, thus you should get used to install the full package in the server side as well as in the client.
    • Improvements: reinforced error handling in --prune action
  2. 1.0.1.4
    • We have refined the way remote files are synchronized during a replica. Some tasks like keeping its size (truncating) and simple cheksums are now performed from the server role and do not depend on Linux components
  3. 1.0.1.3
    • Bug fixes: VM configuration files would not be truncated when their size is reduced from one backup cycle to the next, i.e.: .vmsd files may present this behaviour. This would only happen with some config files, would not affect disk files.

      All users interested in the --replica feature should upgrade to this version. And remember, replicating is not backing up. The --backup feature is much more robust by its own nature and can overcome almost any circumstance, replicating depends on a stable enough connection.

      GENERAL INFO WHEN UPGRADING: (c)XSIBackup-DC is even easier to upgrade and maintain than (c)XSIBackup-Pro, as it is constituted by a main binary (xsibackup) and just an additional library xsilib which performs some additional tasks just in ESXi (you don't need it in Linux). So all you need to do is overwrite the main binary. We have performed only one upgrade on the accompanying library xsilib in the last months, in any case you can overwrite it too, just in case.
  4. 1.0.1.2
    • Improvements: block files are transferred to a buffer, tested then renamed with test. This adds an additional layer of tests ensuring block map integrity and retaking partial replicas is now more resilient.
    • Improvements: license is now only checked when using the --backup or --replica actions, rest of actions including server role are free.
    • Improvements: as you should know, modifying a replica will corrupt the replica data. You must leave replicas alone until you need them. Once you switch a replicated VM on, you can't continue to replicate to it.

      Now you can --check replicas too, not only backups. Checking a replica ensures that the data is the same as the original without the need to switch the VM on.

      If you still want to switch the replica VM on and continue to replicate to it, there are ways to circumvent this inconvenience, like creating a snapshot on the replica from a stopped state, switching the replica on and discarding the snapshot when you are done.

      ATTENTION: please be aware that discarding a snapshot is not the same as deleting it. In virtualization language deleting a snapshot is integrating it with the base disks and that would also break your replica.
    • Bug fixes: SSH subprocess wasn't conveniently killed in some circumstances
    • Bug fixes: Some keys send different signals to the main process if you hit them while the program is running in user mode. We try to control everything going on, but some signals can't just be discarded, so be careful not to strike keys randomly while running jobs in user mode ;-)
  5. 1.0.1.1 -- All (c)XSIBackup-DC users should upgrade to this version, specially if using pruning --
    • Data chunks sent over the SSH tunnel are counted and a simple application level checksum mechanism is set on top of the TCP layer and SSH tunnel signalling.
  6. 1.0.1.0 -- All (c)XSIBackup-DC users should upgrade to this version, speciall if using pruning --
    • Bug fixes: we have fixed some bugs in the --check and --info actions that would make them slow finding .map files in big repositories with small block sizes.
    • Bug fix: pruning is a delicate process, running out of space in the /tmp dir could lead to data loss. We have moved the main tmp dir used for pruning to the installation root in ESXi. Recommended location is /scratch/xsi, default size is 4GB, more than enough to handle multi-TB multi restore point repositories. You may move /scratch to a bigger volume in case you need more room. Read this post to delve into pruning details.
    • Improvement: --prune module has been completely reprogrammed to be faster. It was enough to prune 10MB block sizes and above, but would take long and require tweaking in the OS to prune big 1MB repositories. Read this post to delve into pruning details.
    • Improvement: fprintf() function has been replaced by fwrite() in some parts where recursiveness would make fwrite() be faster than fprintf() this improves performance a bit.
  7. 1.0.0.8
    • Fixed: issue with --update-cron command in ESXi 6.7.0 U3
    • Fixed: minor bugs
  8. 1.0.0.7
    • Fixed: since --compression option was set as default, only editing the etc/xsibackup.conf file would allow to disable compression. Now it can be set through the --compression=[0|1|true|false|yes|no] option again.
    • Improvement: default block size for backups has been changed to 1M in alignment with the ESXi block size. 10M, 20M and 50M are still available to use. Please, note that although 1M block size is a must to backup over IP and it is indeed faster when used over SSH/IP, you might get better speed results with bigger block sizes when backing up to a local datastore. Enabling jumbo frames can be of great help too at the time to increase throughput.

      Bigger block sizes allow also to use VMFS volumes as the target of deduplicated repositories. VMFS 5.0 declared to be able to host around 132,000 inodes which is a very limited number to host lots of tiny chunks of data, nonetheless VMWare says that VMFS 6.0 is able to host millions of files, which is more than enough for (c)XSIBackup-DC to be able to host many terabytes of data even at 1M block size.

      In any case, being able to use NFS to backup to underlying XFS or EXT4 file systems makes VMFS not that interesting or needed for your backups.
  9. 1.0.0.6
    • Improvement: the xsibackup.pid file has been moved to /tmp/xsibackup.pid so that using any Linux distro as an IP target is eased in regards to permissions required when compared to the /var/run folder previously holding that file
    • Improvement: we have added extended debug information to some critical error messages to help narrow down NFS connectivity/ permission issues
    • Fixed: small bug when there are no blocks to prune this fact was previously informed as an error
  10. 1.0.0.5
    • Added: clean-up of var/spool/mail and var/log/prog directories on load. Latest e-mail templates and progress information available in these directories will remain available in between backup cycles for you to inspect. Until this version they would accumulate in those dirs requiring manual clean-up
  11. 1.0.0.4
    • Fixed: e-mail subject would not inform of errors during the backup process. They were informed in the e-mail body though.
    • Fixed: partial error count per VM was not logged properly.
  12. 1.0.0.3
    • Added: accepting EULA on first run is now mandatory.
    • Fixed: minor bugs
  13. 1.0.0.2
    • Fixed: the xsibackup.log was wiped on every new execution, now new output is appended.
    • Fixed: progress info would stuff the xsibackup.log file with every progress update in a new line, resulting in a lot of useless information being logged.
  14. 1.0.0.1
    • Improvement: request.key file is not generated unless a real command is run. We changed this behaviour as some users might prefer to install their license first. To generate a request.key file just run: ./xsibackup --request-key
  15. 1.0.0.0
    • Bug fixes: final release
  16. 0.9.8.2
    • Compatible with Synology devices as a native binary. Requires to configure root access to the Synology appliance.
    • The --link-srv action will work out of the box for user root. All other users different than root store their configuration files at custom paths in Synology NAS devices, thus by now you need to perform the key exchange manually.
  17. 0.9.8.1
    • Small bug fixes and output texts retouch
  18. 0.9.8.0
    • Unified log subsystem for client and server.
    • Improved --check routine with more accurate progress and some bugs fixed. Before this version it would report small files as K.O. due to being smaller than the block size, which was a gross bug.
  19. 0.9.7.2
    • Accumulated time added to the output and the e-mail report.
  20. 0.9.7.1
    • Last errors data added to the e-mail report footer. It can handle up to 8KB of errors, beyond that point you must consult the error.log file.
  21. 0.9.7.0
    • Rotating data can now be achieved from an IP client, before the --rotate option was only available in local backups.
  22. 0.9.6.2
    • Bug fix: signal handling in the IP server side would send a 13 signal to the client when triggering jobs from the cron, which would in turn record it in the log. It caused no additionalissues, apart from overpopulating the xsibackup.log file.
  23. 0.9.6.1
    • The way to use ciphers has been improved and normalized. (c)XSIBackup-DC will pick the ciphers defined in the ssh_ciphers variable inside the etc/xsibackup.conf file. You may supersede the default list of ciphers by using the --ssh-ciphers argument in the command line. By doing so the default list of ciphers is replaced by your own custom one.

      To set a custom list of ciphers, you need to find out which ciphers are available in your OpenSSH build in order to not get a cipher negotiation error. It is arguable whether OpenSSH should simply ignore an unknown cipher, but the truth is that you must be careful as a single mismatch will cause an error.

      You may also use the --options=L switch, which is equivalent to set a light encryption deprecated list of ciphers or "Less Secure Ciphers" like:
      --ssh-ciphers=arcfour,blowfish-cbc,aes128-ctr
  24. 0.9.6.0
    • --backup-how argument is introduced. It works the same way as in the Classic XSIBackup edition, it can take one of 3 values: hot (default), cold and warm.
    • etc/xsibackup.conf file is now functional, allowing the user to tweak some general scope variables
  25. 0.9.5.3
    • Trial Version notice appeared on every execution even if the server had been just restarted. This was a bug, the Trial Version limits have been restored.
  26. 0.9.5.2
    • Improved progress information, now offering simultaneous per file and global percentages in real time
    • Fixed bug in open port detection prior to performing action, non standard ports could not be used in over IP transfers
  27. 0.9.5.1
    • Support for ALL and RUNNING has been added in the virtual machine selection syntax, i.e: "VMs(ALL)" and "VMs(RUNNING)"
    • Automatic removal of backup snapshot when the backup process is aborted by a Ctrl+C condition
  28. 0.9.5.0
    • We have redesigned PID management to make it more usable and avoid loops
  29. 0.9.4.6
    • Bug fixes mainly
  30. 0.9.4.2
    • HTML report may pick templates from the /var/html folder. Templates must be named 000 to 999 and placed in this folder as: 000.html, 001.html, 002.html and so on.

      You can design whatever HTML layout you wish and then include the <!-- PLACEHOLDER REPORT --> comment in its own line. You may then invoke the template by using the option --html-template=NNN
  31. 0.9.4.1
    • Extended HTML report functionality, fall back options and SMTP servers panel at /etc/smtpsrvs.conf.
  32. 0.9.4.0
    • Basic HTML report functionality.
  33. 0.9.3.9
    • Fixed the "Permanently added 'a.b.c.d' (RSA) to the list of known hosts" error on reboot.
  34. 0.9.3.8
    • Added --exclude argument. Allows to exclude disks by parsing a REGEXP pattern. If you want to exclude multiple disks use the --or-- operator in your REGEXP
    • Added --update-cron=[user] action. Inserts the user crontab contents into its corresponding ESXi user crontab
    • Added --install-cron=[user] action. Adds the user crontab to the ESXi /etc/rc.local.d/local.sh file, so that crontabs are persistent across reboots
    • Added --uninstall-cron=[user] action. Removes the user's crontab from the /etc/rc.local.d/local.sh. You still must comment or remove the cron lines and --update-cron=[user] to completely disable cron jobs for that user
  35. 0.9.3.7
    • --check=full action redesigned.
This page was las modified on 2019-12-10



Website Map
Resources & help
Index of Docs
33HOPS Forum

Fill in to download
The download link will be sent to your e-mail.
Name
Lastname
E-mail


            Read our Privacy Policy