Backups
Last updated
Was this helpful?
Last updated
Was this helpful?
A backup is a copy of your database. You can restore the state of the database as it existed at the time of the backup.
Backups are used for disaster recovery. When you create a backup it is wise to copy the backup to a different host. If you lose access to the host that houses your database, you restore the database from a backup on another host.
Backups have additional uses. Taking a backup of a database is often the easiest way to get a copy of the database. You can use this copy for development, testing, or analytics.
Dolt does not support any of the except the mysqldump method. Dolt can create a dump using the or mysqldump connected to the running Dolt server.
Dolt supports different methods of backup that leverage Dolt's git-style features.
Dolt databases contain the entire history of the database, meaning Dolt has backups built in to the running server. To restore to a previous point on a running server, you checkout the database at the commit you would like to restore to.
To replicate your database off host so you can restore if you lose the host, Dolt supports two different concepts: remotes and backups.
Using a for backup allows you to back up all committed changes. You add a remote using the . Then you push a branch to a remote using the or .
Dolt has an additional backup functionality beyond remotes. Using dolt backup backs up uncommitted changes as well. Backups are accessed via the or .
Interestingly, you can trigger backups from your application using the dolt_backup() procedure. If you hit a weird edge case you can create a backup of the state of your database for debugging.