This document explains how to create and restore data backups with Vitess. Vitess uses backups for two purposes:
Vitess stores data backups on a Backup Storage service, which is a pluggable interface.
Currently, we have plugins for:
Before you can back up or restore a tablet, you need to ensure that the tablet is aware of the Backup Storage system that you are using. To do so, use the following command-line flags when starting a vttablet that has access to the location where you are storing backups.
||Specifies the implementation of the Backup Storage interface to
Current plugin options available are:
||If set, the contents of every file to backup is sent to a hook. The
hook receives the data for each file on stdin. It should echo the
transformed data to stdout. Anything the hook prints to stderr will
be printed in the vttablet logs.
Hooks should be located in the
The hook receives a
||This flag controls if the backups are compressed by the Vitess code.
By default it is set to true. Use
||Indicates that, when started with an empty MySQL instance, the tablet should restore the most recent backup from the specified storage plugin.|
Note that for the Google Cloud Storage plugin, we currently only support Application Default Credentials. It means that access to Cloud Storage is automatically granted by virtue of the fact that you're already running within Google Compute Engine or Container Engine.
For this to work, the GCE instances must have been created with
the scope that
grants read-write access to Cloud Storage. When using Container Engine, you can
do this for all the instances it creates by adding
--scopes storage-rw to the
gcloud container clusters create command as shown in the Vitess on Kubernetes
Run the following vtctl command to create a backup:
vtctl Backup <tablet-alias>
In response to this command, the designated tablet performs the following sequence of actions:
Switches its type to
BACKUP. After this step, the tablet is no
longer used by vtgate to serve any query.
Stops replication, get the current replication position (to be saved in the backup along with the data).
Shuts down its mysqld process.
Copies the necessary files to the Backup Storage implementation that was specified when the tablet was started. Note if this fails, we still keep going, so the tablet is not left in an unstable state because of a storage failure.
Restarts replication (with the right semi-sync flags corresponding to its original type, if applicable).
Switches its type back to its original type. After this, it will most likely be behind on replication, and not used by vtgate for serving until it catches up.
When a tablet starts, Vitess checks the value of the
-restore_from_backup command-line flag to determine whether
to restore a backup to that tablet.
As noted in the Prerequisites section, the flag is generally enabled all of the time for all of the tablets in a shard. If Vitess cannot find a backup in the Backup Storage system, it just starts the vttablet as a new tablet.
vttablet ... -backup_storage_implementation=file \ -file_backup_storage_root=/nfs/XXX \ -restore_from_backup
vtctl provides two commands for managing backups:
ListBackups displays the existing backups for a keyspace/shard in chronological order.
vtctl ListBackups <keyspace/shard>
RemoveBackup deletes a specified backup for a keyspace/shard.
RemoveBackup <keyspace/shard> <backup name>
Bootstrapping a new tablet is almost identical to restoring an existing tablet. The only thing you need to be cautious about is that the tablet specifies its keyspace, shard and tablet type when it registers itself at the topology. Specifically, make sure that the following vttablet parameters are set:
-init_keyspace <keyspace> -init_shard <shard> -init_tablet_type replica|rdonly
The bootstrapped tablet will restore the data from the backup and then apply changes, which occurred after the backup, by restarting replication.
We recommend to take backups regularly e.g. you should set up a cron job for it.
To determine the proper frequency for creating backups, consider the amount of time that you keep replication logs and allow enough time to investigate and fix problems in the event that a backup operation fails.
For example, suppose you typically keep four days of replication logs and you create daily backups. In that case, even if a backup fails, you have at least a couple of days from the time of the failure to investigate and fix the problem.
The back-up and restore processes simultaneously copy and either compress or decompress multiple files to increase throughput. You can control the concurrency using command-line flags:
If the network link is fast enough, the concurrency matches the CPU usage of the process during the backup or restore process.