The S3 Backup Restore Tool is the standalone utility for performing DR from the S3 backup bucket, either to the original cluster or to an empty cluster that is meant to replace the original. See S3 Backup Feeds.
Once the data is backed up in S3, the restore tool allows both examining a backup and control how, what, and where it is restored:
...
The S3 Backup Restore tool has a separate install package included in the Swarm download bundleavailable by Support request. Install it on one or more (for parallel restores) systems where the restore processes run.
...
The swarmrestore package is delivered as a Python pip3 source distribution. Each machine needs to be prepared to be able to install this and future versions of swarmrestore.
As root, run the following command:
Code Block language bash yum install python3
Verify version 3.6 is installed:
Code Block python3 --version
Upgrade pip
Code Block | ||
---|---|---|
| ||
pip3 install --upgrade pip |
...
Rerun this installation when a new version of swarmrestore is obtained:
Copy the latest version of the swarmrestore package to the server.
Run the following as root:
Code Block language bash pip3 install caringo-swarmrestore-<version>.tar.gz
swarmrestore is likely in
/usr/local/bin
and is already in the path.Repeat for any additional servers if planning to perform partitioning for parallel restores.
Restore Tool Settings
The tool uses a configuration file, .swarmrestore.cfg. Because the file contains sensitive passwords, the tool warns if the configuration file is not access-protected (chmod
mode 600 or 400).
The configuration file follows the format of Swarm Storage settings files, using sections listing name = value pairs. These setting names map to the S3 Backup feed definition, where the values have the same meaning.
Locate the sample configuration file where it is installed:
Code Block /usr/local/sample-.swarmrestore.cfg
Copy the file into the home directory and rename it, and open it for editing:
Code Block language bash cp /usr/local/sample-.swarmrestore.cfg ~/.swarmrestore.cfg vi ~/.swarmrestore.cfg # Edit config settings
sample-.swarmrestore.cfg
Code Block |
---|
# This is a sample configuration file for the swarmrestore utility. # Save this file as ~/.swarmrestore.cfg and chmod 600 ~/.swarmrestore.cfg to keep passwords private. # S3 host must be a fully qualified host name. The virtual host access style is supported if # the host's first component is the bucket name. # See https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region for Amazon S3 endpoints. [s3] host=s3.amazonaws.com port=443 accessKeyID=<youraccesskeyid> secretAccessKey=<yoursecretaccesskey> bucketName=<yourbucketname> region=us-east-1 # The option below uses HTTPS for access. For HTTP, set sslOption=none and adjust port. sslOption=trusted # The 4 options below are for swarmrestore initiating archival restore of content, such as GLACIER. performArchiveRetrieval=false retrievalTier=Standard accountID=<ninedigitaccountid> activeLifetimeDays=7 # Use these only if you need a forward proxy to reach the S3 service. [forwardProxy] host= port=80 username= password= # The log file can be /dev/null, but logs are useful for diagnosing problems. [log] filename=swarmrestore.log level=30 # The Swarm cluster must either be directly accessible or accessible via # a proxy. The password below is the administrative password for the cluster. [swarm] host=<space separated list of swarm host IPs or gateway host> password=ourpwdofchoicehere cluster=<yourclustername> |
Section | Settings |
---|---|
[s3] |
|
[s3] archival | Set these additional parameters if using an S3 bucket with an archival storage class (Glacier, Glacier Deep Archive):
|
[forwardProxy] | This section is for use with an optional forward proxy:
|
[log] | The same log settings as the Swarm cluster may be used; identify the logs by looking for those with the component "
|
[swarm] |
|
...