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.

Chef 360 Platform version

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

To download Chef 360 Platform, follow these steps:

1. In the Admin Console, download the Chef 360 Platform build that matches the version running when your backup was created.

2. Extract the archive:

   tar -xvzf chef-360.tgz
   

Restore Chef 360 Platform

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

1. Run the restore command with elevated privileges:

   sudo ./chef-360 restore
   

2. Enter the following disaster recovery storage settings that were defined when disaster recovery was configured:

   • S3 endpoint URL
   • AWS region
   • Bucket name
   • Prefix (velero-backup folder path)
   • Access key ID
   • Secret access key

3. Chef 360 Platform runs preflight checks to verify the following:

   • Host preflight checks pass
   • Node is ready
   • Storage is ready
   • Disaster recovery is ready
   • Backup storage location configured

4. Select a backup from the list of the latest available backups.

5. Chef 360 Platform may prompt you to add nodes to the cluster.

   If you’re prompted:

   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, then 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 right nodes.

6. Wait for all services to become healthy.

Resume a failed restore

To resume a failed restore:

1. Run sudo ./chef-360 restore again.
2. Select Yes when prompted to resume the previous restore operation.
3. Continue with backup selection and completion.

Troubleshooting

• Use the exact Chef 360 Platform build version that created the backup.
• Verify DR settings match the original configuration exactly.
• Allow sufficient time for post-restore system stabilization.