Backups are copies or archives of data used for recovery after the loss, deletion, or corruption of a database or filesystem. Developers can create backups in a number of ways, including manual implementation, cloud hosting services, or backup programs (such as Bacula).
For more resources about backups, please visit:
A complete list of our backup-related tutorials, questions, and other educational resources can be found on our backups tag page.
If you’ve got a NAS (network attached storage) device at home, you know how great they are.
These mini-computers full of hard drives live on your home network, ready and waiting to store and share all of your music, photos, and other media. You can grant access to yourself, your friends, your family, or everyone on the planet using any number of different apps!
While NAS devices themselves are extremely fault-tolerant, that doesn’t mean that they could survive . . . a flood. Or a fire. A Godzilla foot would definitely destroy all your data.
That’s why you should back up your NAS regularly. Synology has made this easy by providing powerful backup tools in their line of NAS devices.
Today we’ll look at setting up Synology’s Hyper Backup app, and we’ll be using it to back up the contents of our Synology device to DreamHost’s DreamObjects cloud storage service.
You’ll first need to create a private “bucket” on DreamObjects — this where your data will live. Doing this is quick and easy, and at the end of the process, you’ll have three things: a public key, a secret key, and a bucket name.
Secure Cloud Storage Hosting
DreamObjects is an inexpensive object storage service great for hosting files, storing backups, and Web app development.
The process to create a bucket on the DreamObjects control panel is pretty straightforward, but if you need a little hand-holding, our knowledge base has got you covered: DreamHost Knowledge Base: What is DreamObjects?
Once you’ve got your bucket created, log in to your Synology device’s web interface, also known as DSM.
Click over to the Package Center, navigate to the “Hyper Backup” app, and click to Install/Open it.
If you’ve just installed Hyper Backup, navigate to your list of installed apps where you’ll see that it now sits proudly under a spotlight, awaiting your click.
Launch Hyper Backup.
The first thing you’ll be asked is which where you’d like your backups to live. Navigate to “S3 Storage.”
Why S3? Simple! DreamObjects is compatible with S3’s API, meaning that just about any app written for AWS S3 will work flawlessly with DreamObjects.
Select “Custom Server URL” for your S3 Server. Your server address should be “objects-us-east1.dream.io” and your signature version can be v4. Once you provide your access key (public key) and secret key, all of your available DreamObjects buckets will populate the dropdown list. Select the one that you want to use (you might only have one.) The “Directory” will be a directory that lives at the top level of your bucket, and you can name it whatever you like.
Now you’ll need to tell Hyper Backup which directories to include in this backup task.
If you want to back up the settings and data from any of Synology’s own applications, you can do that as well on the next screen.
You’ll now need to give this backup task a name so that you’ll be able to quickly identify it in the future. You’ll also need to choose how often you’d like the backup to run.
Finally, you’ll need to determine your rotation settings. This is important. If you allow your backups to run every week, for example, you’ll end up with 52 backups by the end of the year, and you’ll end up paying for all 52 of them. That’s probably not what you want.
What you select on this screen is up to you, but here’s the official word from Synology on how their Rotation Settings work.
If all goes as planned, you should now see a screen like this:
Whatever data you’ve selected from your NAS is now being backed up to DreamObjects! You can now kick back and never worry about having to retrieve it until you have to!
If all goes well, you’ll see this:
If you ever have a need to restore your data, just launch Hyper Backup and click this little fella to get started:
Alternately, you can use Synology’s standalone utility, Hyper Backup Explorer to retrieve individual files buried within your backups as well.
Backups automated with tools like Hyper Backup and DreamObjects can be key to ensuring the security of your data in a world full of ransomware, random hardware failures, and natural disasters. Be prepared!
Use promo code DOCS10 for $10 credit on a new account.
The Linode Backup Service is a subscription service add-on that automatically performs daily, weekly, and biweekly backups of your Linode. It’s affordable, easy to use, and provides peace of mind. This guide explains how to enable and schedule your backups, make a manual backup snapshot, restore from a backup, and disable the Backup Service.
Pricing is per Linode and varies depending upon your Linode’s plan:
Backups Hourly Rate
High Memory Plans
Backups Hourly Rate
Enable the Backup Service
Use the Linode Cloud Manager to enable the Backup Service on a Linode. Here’s how:
Log in to the Linode Cloud Manager.
From the Linodes page, select the Linode you want to back up.
Click the Backups tab.
Click Enable Backups.
The Linode Backup Service is now enabled for the selected Linode.
Auto Enroll New Linodes in the Backup Service
You can automatically enroll all new Linodes in the Backup Service. To do so, click the Account link in the sidebar, then select the Global Settings tab.
In the Backup Auto Enrollment panel, click on the switch to enable backups on all new Linodes.
Enabling this setting does not retroactively enroll any previously created Linodes in the Backup Service.
You’ll manage your backups with a simple web interface in the Linode Cloud Manager. There’s no software to install, and there are no commands to run. Just log in to the Linode Cloud Manager, navigate to the Linodes page by clicking on the link in the sidebar, select a Linode, and then click the Backups tab. The backups interface is shown below.
A list of available backups. Listed in this view are the date created, the label, how long the backup took to be created, the disks imaged, and the size of the resulting image.
Manually create a backup by taking a manual snapshot. For more information, see the Take a Manual Snapshot section.
Configure backup schedule settings. For more information, see the Schedule Backups section.
Cancel backups. After cancelling your backups you will have to wait 24 hours before you can re-enable them again.
How Linode Backups Work
Backups are stored on a separate system in the same data center as your Linode. The space required to store the backups is not subtracted from your storage space. You can store four backups of your Linode, three of which are automatically generated and rotated:
Daily backup: Automatically initiated daily within the backup window you select. Less than 24 hours old.
Current week’s backup: Automatically initiated weekly within the backup window, on the day you select. Less than 7 days old.
Last week’s backup: Automatically initiated weekly within the backup window, on the day you select. Between 8 and 14 days old.
Manual Snapshot: A user-initiated snapshot that stays the same until another snapshot is initiated.
The daily and weekly backups are automatically erased when a new backup is performed. The Linode Backup Service does not keep automated backups older than 8 – 14 days.
You can configure when automatic backups are initiated. Here’s how:
From the Linodes page, select the Linode.
Click the Backups tab.
Under Settings, select a time interval from the Time of Day menu. The Linode Backup Service will generate all backups between these hours.
Select a day from the Day of Week menu. This is the day whose backup will be promoted to the weekly slot. The back up will be performed within the time period you specified in step 3.
Click Save Changes.
The Linode Backup Service will backup your Linode according to the schedule you specified.
Take a Manual Snapshot
You can make a manual backup of your Linode by taking a snapshot. Here’s how:
From the Linodes page, select the Linode.
Click the Backups tab.
Under Manual Snapshot, give your snapshot a name and click Take Snapshot.
Taking a new snapshot will overwrite a previously saved snapshot.
The Linode Backup Service initiates the manual snapshot. Creating the manual snapshot can take several minutes, depending on the size of your Linode and the amount of data you have stored on it. Other Linode Cloud Manager jobs for this Linode will not run until the snapshot job has been completed.
Restore from a Backup
This section shows how to restore a backup to a new Linode, or to an existing Linode.
Restoring a backup will create a new configuration profile and a new set of disks on your Linode. The restore process does not restore single files or directories automatically. Restoring particular files can be done by completing a normal restore, copying the files off of the new disks, and then removing the disks afterward.
The size of the disk(s) created by the restore process will only be slightly larger than the total size of the files restored. This means that the disk(s) created will be ‘full’.
Some applications, like databases, need some amount of free unused space inside the disk in order to run. As a result, you may want to increase your disk(s) size after the restore process is completed.
To restore a backup to a different data center, first restore to a Linode in the same data center, creating a new one if necessary. Once the restore is complete, use the Clone tab to copy the disk(s) to a Linode in a different data center.
Restore to a New Linode
This section covers how to restore a backup to a new Linode that does not have any disks deployed to it. The new Linode will be located in the same data center. If you instead wish to restore your backup to an existing Linode, see the next section.
From the Linodes page, select the Linode whose backups you intend to restore, and then click on the Backups tab. Select the more options ellipsis next to the backup you would like to restore, and click Deploy New Linode.
You will be taken to the Create New Linode screen. The Create from Backup tab will already be selected for you, as will the fields corresponding to the Linode and backup that you are restoring from. Choose a Linode plan, enter a label for the new Linode, select any other options you prefer, and click Create. The new Linode will be created with the same password and SSH keys (if any) as the original.
The backup disks and configuration profiles will be restored to the Linode you selected. Watch the notifications area for updates on the process. Restoring from a backup can take several minutes depending on the size of your Linode and the amount of data you have stored on it.
Restore to an Existing Linode
You can restore a backup to any Linode located in the same data center, even if the target does not have the Backup Service enabled. To restore a backup to an existing Linode, you will need to make sure that you have enough storage space that is not currently assigned to disk images.
If you are attempting to restore a disk to the same Linode the backup was created from, the restoration process will not delete the original disk for you. Manually delete the original disk to make room for the backup, if desired.
From the Linodes page, select the Linode whose backups you intend to restore, and then click on the Backups tab. Observe the size of the backup you would like to restore, which is visible in the Space Required column. You will need at least this amount of unallocated disk space on the target Linode to complete the restore.
Select the more options ellipsis next to the backup you would like to restore, and click Restore to Existing Linode.
A menu will open with the Linodes that you can restore to. Select a Linode and click Restore.
You will be notified if you do not have enough space on your Linode to restore your backup. Optionally, you can choose to overwrite the Linode you are restoring to.
If the amount of unallocated space available is greater than the size of the backup, you can proceed with restoring. If the amount of unallocated space is less than the size of the backup, you can stop the restoration workflow, resize your existing disks on the target Linode to make room for it, and then come back to the restore page after the disk resize operation has finished.
In some cases, you will not be able to shrink your disks enough to fit the restored backup. As an alternative, you can change your Linode’s plan to a higher tier that offers more disk space.
From the Restore to Existing Linode menu, click Restore.
Your backup will begin restoring to your Linode, and you can monitor its progress in the notifications area. Note that the time it takes to restore your backup will vary depending upon the restore size, and the number of files being restored.
Boot from a Backup
After the backup has been restored, the disks and configuration profiles will be available to the destination Linode you selected. Select the restored configuration profile and reboot your Linode to start up from the restored disks:
From the Linodes page, select the Linode that you restored the backup to. Navigate to the Settings tab and open the Advanced Configurations panel.
Select the more options ellipsis next to the configuration profile that was restored and select Boot This Config.
The Linode will start from the backup disks. Monitor the notifications area for progress.
Cancel the Backup Service
You can cancel the Backup Service at any time. From your Linode’s details page, choose the Backups tab and click the Cancel Backups link at the bottom of the page. Cancelling the service will remove your saved backups from the Linode platform.
There are some limitations to what the Linode Backup Service can back up. Here are some things you should be aware of:
The Backup Service must be able to mount your disks. If you’ve created partitions, configured full disk encryption, or made other changes that prevent us from mounting the disk as a filesystem, you will likely not be able to use the Linode Backup Service. The backup system operates at the file level, not at the block level.
Because the Backup Service is file-based, the number of files stored on disk will impact both the time it takes for backups and restores to complete, and your ability to successfully take and restore backups. Customers who need to permanently store a large number of files may want to archive bundles of smaller files into a single file, or consider other backup services.
The percentage of customers who may run into this limitation is low. If you are not sure if this limitation applies to you, please contact Linode Support.
Backups taken of ext4 or ext3 filesystems will be restored as ext4. Backups taken of other mountable filesystem types will have their contents restored using ext4.
Files that have been modified but have the same size and modify time will not be considered “changed” during a subsequent backup. ACLs and extended attributes are not tracked.
The Backup Service uses a snapshot of your disks to take consistent backups while your Linode is running. This method is very reliable, but can fail to properly back up the data files for database services like MySQL. If the snapshot occurs during a transaction, the database’s files may be backed up in an unclean state. We recommend scheduling routine dumps of your database to a file on the filesystem. The resulting file will then be backed up, allowing you to restore the contents of the database if you need to restore from a backup.
Find answers, ask questions, and help others.
The Linode Classic Manager
This guide is published under a CC BY-ND 4.0 license.