HashBackup has been actively developed since its initial release in June 2009. Over that time there has been a release every few weeks on average. There are ongoing backups of production servers from 2010 with over 3000 daily backups.
HashBackup is being used for large production backups, often to handle offsite backup requirements to supplement an existing onsite backup. The largest reported single backup is 53M files / 121TB at a college research site. The initial backup took 25 days, used 8GB of RAM, and created 57TB of backup data managed by a 17GB database, with 22TB eliminated by dedup. Other large reported backups are 26M files / 18TB at a research lab, 25M files / 1.5TB for a large imap server, 23M files / 34TB for a data archive, and 27TB of 1.5TB VM image backups using less than 1TB of backup space after dedup.
Is there an online bug list?
Bug lists often provide a comfortable home to bugs for many months or
years. But most customers would prefer that bugs are squashed rather
than taking up residence on a bug list, so HashBackup works a
different way: when a bug is reported, it’s fixed, released to the
preview area, and a reply is sent asking the customer to do an
hb upgrade -p to get the preview release. If it’s a difficult bug, and
most aren’t, an update may be sent directly to a customer asking them
to verify that the problem is fixed before doing a release.
Bug reports and correcting bugs take priority over new development, so not having a bug list also acts as a self-regulating mechanism to balance new development and reliability.
If you have any questions, suggestions, or concerns you’d like to discuss, send an email! It’s always helpful to get feedback about HashBackup.