Backups are made every day and saved for 7 days. We also save 1 backup per week for 3 weeks. This means you will have 4 weeks worth of backups.
Backups are rotated daily after the creation of a new backup. This implies that the backups that are older than 4 weeks will be automagically removed. To save storage costs, we do not keep additional backups older than 4 weeks, so please do not wait too long before requesting a backup.
Attaching a snapshot to your Hypernode
On Amazon (AWS) and Combell OpenStack we use snapshots to create backups. A snapshot is a saved state of the /data device at a given moment in time. We can use this to create a static copy of that given state in time and transform this to a virtual device which we can attach to your Hypernode. Once attached, this device is mounted under /data/backup and you can easily restore your files by copying them from this file system. To restore database and file backups, see this article.
By using the following command you attach the latest available snapshot to your node:
The backup snapshot is automagically detached/unmounted overnight, before the backups are made. There is a second MySQL instance running so you’ll lose some resources while it is attached. Please contact Support if you want the snapshot detached earlier, to save on resources.
Requesting older backups
If you need a less recent backup (older than one day), you need to contact Support. Please note we charge a fee for this:
|SLA Basic||SLA Standard|
|Most recent Hypernode Backup (AWS/Openstack)||Free||Free|
|Most recent Hypernode Backup (DigitalOcean)||Free||Free|
|Older Hypernode Backups||€ 100,- (ex VAT)||Free|
Managing backups yourself
If want to be able to restore yourself any time you want without contacting firstname.lastname@example.org first, you may choose to manage backups yourself.
This does not imply that we do not have any backups available, as we use the same backups for disaster recovery as well. In case of emergency, you can always request a backup by contacting email@example.com
If you choose to create your own backups, we recommend using Tarsnap. This very robust third party backup service is known for it’s excellent security, their very strong compression and their low prices.
For more information about how to manage your own backups, have a look at our article about creating backups using Tarsnap.
Using hard-links for backup retention
Our backup mechanism is not very good in managing hard-links. They will not be ignored in the backup, but at restore time, every hardlink is restored as a real file, causing the restore to take up much more disk space.
This can result in lots of extra files when downloading a restore, effectively taking up much more space needed for the same data after a restore.
We recommend to avoid hard-links in your content at all times.
We make use of 2 backup mechanisms: One for the Hypernodes running on Amazon (AWS) and Combell OpenStack, and another mechanism for backups on DigitalOcean.
Read more about restoring backups on Hypernode in our restore backups article.