Restore Chef 360 Platform from a backup

This page documents how to restore Chef 360 Platform from a backup.

Prerequisites

Before beginning the restore process, verify the following:

Disaster recovery is configured in the Admin Console.
Sufficient additional storage space on the restore system, as the system downloads backup data from S3 locally before restoring.
The cluster is accessible using the same tenant FQDN that was used when the backup was created.
If you’ve deployed Chef 360 Platform in high availability configuration, verify that all nodes are ready to join when prompted during the restore process.

You must restore Chef 360 Platform using the same version that was used to create the backup.

To download Chef 360 Platform, follow these steps:

In the Admin Console, download the Chef 360 Platform build that matches the version running when your backup was created.
Extract the archive:
```
tar -xvzf chef-360.tgz
```

To restore Chef 360 Platform from a backup, follow these steps:

Run the restore command with elevated privileges:
```
sudo ./chef-360 restore
```
If your object storage service (for example, MinIO) uses HTTP, add the --skip-store-validation flag to skip TLS certificate verification of the object storage endpoint:
```
sudo ./chef-360 restore --skip-store-validation
```
For air-gapped environments, add the --airgap-bundle flag with the path to the air-gap bundle file:
```
sudo ./chef-360 restore --airgap-bundle chef-360.airgap --skip-store-validation
```
Enter the following disaster recovery storage settings that were defined when disaster recovery was configured:
- S3 endpoint URL
- Region
- Bucket name
- Prefix (velero-backup folder path)
- Access key ID
- Secret access key
Wait for Chef 360 Platform to complete preflight checks and verify the following:
- Host preflight checks pass
- Node is ready
- Storage is ready
- Disaster recovery is ready
- Backup storage location is configured
Select a backup from the list of available backups.
If Chef 360 Platform prompts you to add nodes to the cluster:
1. Open the Admin Console using the provided URL.
2. Add the required number of nodes to your cluster.
3. Return to the terminal, type continue, and press Enter.
For tiered and hyperscaled high availability configurations, verify that nodes have the correct labels (frontend, backend, controller) so pods are scheduled on the correct nodes.
Wait for all services to become healthy.

To resume a failed restore: