Restore

[edit on GitHub]

Restore Chef Automate from a filesystem backup, an Amazon S3 bucket backup, or a Google Cloud Storage (GCS) bucket backup.

Before restoring a Chef Automate installation, see how to configure your backups.

Prerequisites

On the restore host, download and unzip the Chef Automate command-line tool:

     curl https://packages.chef.io/files/current/latest/chef-automate-cli/chef-automate_linux_amd64.zip | gunzip - > chef-automate && chmod +x chef-automate

To restore from filesystem backups, Chef Automate requires access to a backup directory in the configured location. Ensure access for the backup type used:
1. To restore a network-attached filesystem backup, mount the shared backup directory to the same mount point configured at the time of the backup.
2. To restore a backup directory that is not a network-attached filesystem, copy the backup directory to the configured location at the time of the backup.
3. To restore a single-file backup archive, copy your archive to the restore host and extract it to the configured backup directory.

To restore a backup to a host with a different fully qualified domain name (FQDN) than the original backup host, create a patch.toml file that specifies the new FQDN and provide it at restore time:

     [global.v1]
     fqdn = "<new-fqdn>"

     # To provide a cert and key for the restore host, uncomment and fill
     # these sections.
     # [[global.v1.frontend_tls]]
     # The TLS certificate for the load balancer frontend.
     # cert = """-----BEGIN CERTIFICATE-----
     # <certificate-for-new-fqdn>
     # -----END CERTIFICATE-----
     # """

     # The TLS RSA key for the load balancer frontend.
     # key = """-----BEGIN RSA PRIVATE KEY-----
     # <key-for-new-fqdn>
     # -----END RSA PRIVATE KEY-----
     # """

To restore a backup to a machine with less memory than the original system, adjust for the appropriate lower memory settings by creating a patch.toml file that specifies the heapsize, and providing the file at restore time:
```
  [elasticsearch.v1.sys.runtime]
    heapsize = "4096m"
    # Use "m" for megabytes and "g" for gigabytes
```

Restore From a Filesystem Backup

Meet the required prerequisites before beginning your restore process.

Restore in an Internet-Connected Environment

If you have configured the backup directory to a directory other than the default directory (/var/opt/chef-automate/backups), you must supply the backup directory. Without a backup ID, Chef Automate uses the most recent backup in the backup directory.

To restore on a new host, run:

chef-automate backup restore </path/to/backups/>BACKUP_ID

To restore on an existing Chef Automate host by overwriting the existing installation with the backup, run:

chef-automate backup restore </path/to/backups/>BACKUP_ID --skip-preflight

Use the --patch-config option with a configuration patch file to restore to a host with a different FQDN than that of the backup host:

chef-automate backup restore </path/to/backups/>BACKUP_ID --patch-config </path/to/patch.toml> --skip-preflight

Restores from a filesystem backup may fail with incorrect directory permissions. Run the fix-repo-permissions command to address such issues:

sudo chef-automate backup fix-repo-permissions <path>

Restore in an Airgapped Environment

To restore a backup of an airgapped installation, you must specify the Airgap Installation Bundle used by the installation. If you have configured the backup directory to a directory that is not the default /var/opt/chef-automate/backups, then you must supply the backup directory. If you do not provide a backup ID, Chef Automate uses the most recent backup in the backup directory.

To restore on a new host, run:

chef-automate backup restore --airgap-bundle </path/to/bundle> </path/to/backups/>BACKUP_ID

To restore on an existing Chef Automate host, run:

chef-automate backup restore --airgap-bundle </path/to/bundle> </path/to/backups/>BACKUP_ID --skip-preflight

To restore using AWS S3 on an existing Chef Automate host, run:

chef-automate backup restore --airgap-bundle </path/to/bundle> s3://bucket_name/</path/to/backups/>BACKUP_ID --skip-preflight

To restore using Google Cloud Storage (GCS) on an existing Chef Automate host, run:

chef-automate backup restore --airgap-bundle </path/to/bundle> gs://bucket_name/</path/to/backups/>BACKUP_ID --skip-preflight

Use the --patch-config option with a configuration patch file to restore to a host with a different FQDN than that of the backup host.

Restores from a filesystem backup may fail with incorrect directory permissions. Run the fix-repo-permissions command to address such issues:

sudo chef-automate backup fix-repo-permissions <path>

Restore From an AWS S3 Backup

Meet the required prerequisites before beginning your restore process.

See how to back up to AWS S3.

To restore from an AWS S3 bucket backup on a new host, run:

chef-automate backup restore s3://bucket_name/path/to/backups/BACKUP_ID

To restore from an AWS S3 bucket backup on an existing Chef Automate host, run:

chef-automate backup restore s3://bucket_name/path/to/backups/BACKUP_ID --skip-preflight

Use the --patch-config option with a configuration patch file to restore to a host with a different FQDN than that of the backup host:

chef-automate backup restore s3://bucket_name/path/to/backups/BACKUP_ID --patch-config </path/to/patch.toml> --skip-preflight

A successful restore shows the timestamp of the backup used at the end of the status output:

Success: Restored backup 20180517223558

Restore From a Google Cloud Storage Backup

Meet the required prerequisites before beginning your restore process.

See how to back up to GCS.

To restore from a Google Cloud Storage (GCS) bucket backup on a new host, run:

chef-automate backup restore gs://bucket_name/path/to/backups/BACKUP_ID

To restore from a Google Cloud Storage (GCS) bucket backup on an existing Chef Automate host, run:

chef-automate backup restore gs://bucket_name/path/to/backups/BACKUP_ID --skip-preflight

Use the --patch-config option with a configuration patch file to restore to a host with a different FQDN than that of the backup host:

chef-automate backup restore gs://bucket_name/path/to/backups/BACKUP_ID --patch-config </path/to/patch.toml> --skip-preflight

A successful restore shows the timestamp of the backup used at the end of the status output:

Success: Restored backup 20180517223558

Troubleshooting

Set the log level to debug before re-running a failed restore to output debug info to the Chef Automate log:

chef-automate debug set-log-level deployment-service debug

References

See the chef-automate backup restore command reference.