A utility for backing up and restoring a Couchbase cluster
Prints the cbbackupmgr suite version that the cbbackupmgr program came from.
Prints the synopsis and a list of commands. If a cbbackupmgr command is named, this option will bring up the manual page for that command.
Backs up data from a Couchbase cluster.
Collects diagnostic information.
Compacts a backup.
Creates a new backup repository.
Developer preview command that displays information about the backups in the archive.
Merges backups together.
Deletes a backup repository.
Restores a backup from the archive.
The root directory containing multiple backup repositories. This is the top-level backup directory and contains all backup data as well as backup logs.
Contains a backup configuration used for taking actual backups. A repository should be created for a specific Couchbase cluster and it will contain multiple incremental backups.
A backup of a Couchbase cluster at a given point in time. All backups are incremental backups.
A backup may consist of one or more buckets. Each bucket is stored separately.
A dot separated string which indicates the location of documents on a Couchbase cluster. Collection strings are expected in the format 'bucket.scope.collection'. The collection string 'food.produce.fruit' refers to the 'fruit' collection inside the 'produce' scope which is contained in the 'food' bucket. In the case where the bucket name contains a '.' character you should escape the '.' character. e.g. 'fo\.od.produce.fruit' is a valid collection string. You are also free to omit the scope/collection portion of the collection string; in this case the absence of a scope/collection is treated as a wildcard indicating all collections inside a scope or all scopes inside a bucket. For example the collection string 'food.produce' indicates that we are that we are talking about all of the collections that fall inside of the 'produce' scope inside of the 'food' bucket.
Please see the cbbackupmgr-archivelayout document.
Specifies the hostname of the Couchbase cluster to connect to. If the hostname is supplied as a command line argument then this value is overridden.
Specifies the username for authentication to a Couchbase cluster. If the username is supplied as a command line argument then this value is overridden.
Specifies the password for authentication to a Couchbase cluster. If the password is supplied as a command line argument then this value is overridden.
Specifies the path to the backup archive. If the archive path is supplied as a command line argument then this value is overridden.
Specifies the path to the staging directory. If the
--obj-staging-dirargument is provided in the command line then this value is overridden.
Specifies the object store region. If the
--obj-regionargument is provided in the command line then this value is overridden.
Specifies the object store access key id. If the
--obj-access-key-idargument is provided in the command line this value is overridden.
Specifies the object store secret access key. If the
--obj-secret-access-keyargument is provided in the command line this value is overridden.
By default cbbackupmgr will disable fetching EC2 instance metadata. Setting this environment variable to true will allow the AWS SDK to fetch metadata from the EC2 instance endpoint.
The cbbackupmgr command is used for backing up Couchbase clusters, managing those backups, and restoring them.
The cbbackupmgr command was built around the concept of taking only incremental backups. This concept is important because as the data in a cluster grows it becomes increasingly difficult to take full backups in a reasonable amount of time. By taking incremental backups we are able to reduce the time it takes to backup a cluster by ensuring that we transfer the smallest amount of data possible each time we back the cluster up.
A consequence of taking incremental backups is that we must know about the previous backups that we have taken in order to know where we left off. This means that the cbbackupmgr command must manage the backups it has taken. The cbbackupmgr command does this by using the concept of a backup archive and a backup repository. A backup repository is a directory that contains a backup configuration for backing up a specific cluster. Normally there will be one backup repository per Couchbase cluster. Each time you want to back up this cluster you will specify this backup repository with the cbbackupmgr-backup command and the backup tool will automatically find where the last backup finished and incrementally backup new data in that cluster.
The backup archive is the top-level directory and contains one or more backup repositories and a logs folder. Logging for all backup repositories is contained in the logs folder in the backup.log file. For more information on the backup archive structure see cbbackupmgr-archivelayout.
In an incremental approach the amount of data being stored in the backup archive is always increasing. To handle this issue the backup command allows backups to be merged together. This allows data to be deduplicated resulting in a single backup that takes up less disk space than the multiple previous backups. More information about how to take advantage of incremental backups and merges is contained in cbbackupmgr-strategies.
The minimum hardware requirement for running cbbackupmgr is four CPU cores, 8GiB RAM. The recommend hardware is sixteen CPU cores, 16GiB RAM and SSD disks.
Part of the cbbackupmgr suite