Guides - Manage Backups
Fully managed cloud database clusters built on top of Linode’s trusted and reliable platform.
As part of our ongoing commitment to innovation and better serving our customers, we have made the strategic decision to pause the sale of our Managed Database offering for all customers who do not have an active database deployed. We recognize the need for a product that offers higher performance and the capacity to handle more complex workloads.
If you have an existing database already deployed, you will continue to be able to deploy, provision, and manage the service exactly as you do today, and we’ll fully support your Managed Database workloads until our next-generation database solution is available. For future news and announcements related to Managed Databases, please sign up using the form on our product page.
Each Managed Database includes daily backups of your data, taken on a 24 hour cadence. Up to 7 backups are stored for each database cluster, which provides you with a restore point for each day in the last week. This guide walks you through viewing and restoring from these managed backups.
View Managed Backups
Log in to the Cloud Manager and select Databases from the left navigation menu.
Select your Managed Database from the list. This opens the detail page for that database cluster.
Navigate to the Backups tab. A list of your available backups are displayed, organized by the date they were created.
Restore Managed Backups
View the available backups by following the View Managed Backups instructions.
Locate the backup you wish to restore and click the corresponding Restore link. A confirmation dialog appears.
Enter the name of the database cluster in the Database Label field and click the Restore Database button. This deletes all the data currently stored on the database and restores the data from the selected backup. The restore process takes a few moments, the length of which depends on the amount of data. You can monitor the progress by viewing the listing page for all your database clusters.
Alternative Backup Methods
To fully protect your data, your backup strategy should include additional backup solutions. While managed backups provide several quick recovery points, you may wish to retain backups for longer periods of time, store backups offsite, or only backup certain databases or tables. In these cases, you can use built-in DBMS tools or other third-party solutions.
The following is a list of command-line tools included with each DBMS. These tools can all be used to create manual backups or to automate backups through cron jobs or other tools.
MySQL
The mysqldump utility captures logical backups of MySQL databases and is included as part of the MySQL software. The following command exports a database called Example within the MySQL Managed Database cluster and saves it as an .sql file. Replace the host and database name with your own values. See
Connect to a MySQL Managed Database guide for instructions on viewing the connection details (including the username, password, host, and port).
mysqldump -h lin-1111-1111-mysql-primary.servers.linodedb.net -u linroot -p --single-transaction --set-gtid-purged=OFF Example > backup-$(date +%F-%H.%M.%S).sqlFor more instructions, see Backing Up MySQL Databases Using mysqldump.
PostgreSQL
pg_dump, included with PostgreSQL, captures logical backups of PostgreSQL databases. The following command exports the database called Example within the given PostgreSQL Managed Database cluster and saves it as a file. Replace the host and database name with your own values. See Connect to a PostgreSQL Managed Database guide for instructions on viewing the connection details (including the username, password, host, and port).
pg_dump -Fd --host lin-1111-1111-pgsql-primary.servers.linodedb.net --dbname Example --quote-all-identifiers --verbose --lock-wait-timeout=480000 --no-unlogged-table-data --serializable-deferrable --jobs=1 --username linpostgres --file database.backupFor more information, review the Backing Up a PostgreSQL Database (Database Dump) guide.
This page was originally published on