0f3cc6e990
Co-authored-by: docs-bot <77750099+docs-bot@users.noreply.github.com> Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Co-authored-by: Pallavi <96553709+pallsama@users.noreply.github.com> Co-authored-by: Stephanie Sabota <80356791+steph-sabotasan@users.noreply.github.com> Co-authored-by: Casey Tucker <dctucker@github.com> Co-authored-by: Hao Jiang <45571951+jianghao0718@users.noreply.github.com> Co-authored-by: Felicity Chapman <felicitymay@github.com> Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
1.9 KiB
title, shortTitle, intro, versions, type, topics
| title | shortTitle | intro | versions | type | topics | |||
|---|---|---|---|---|---|---|---|---|
| Restoring with GitHub Actions enabled | Restore with Actions | Learn how to prepare for and restore backups when {% data variables.product.prodname_actions %} is enabled with external blob storage. |
|
how_to |
|
[!IMPORTANT] Data stored in your configured external storage for {% data variables.product.prodname_actions %}—such as logs, artifacts, and other blobs—is not included in {% data variables.product.prodname_enterprise_backup_service %} snapshots. You must back up this data separately using your storage provider's tools and best practices.
When restoring an instance with {% data variables.product.prodname_actions %} enabled, follow these steps to preserve compatibility with existing Actions data:
-
Provision the target instance.
-
Preconfigure Actions storage:
-
In the {% data variables.enterprise.management_console %}, enable {% data variables.product.prodname_actions %}.
-
Enter the exact same external storage provider and credentials used in the original instance.
-
Click Save.
This step ensures the restored Actions metadata correctly references your existing external data.
-
-
Enable maintenance mode on the target instance.
-
Restore the backup:
- Run the ghe-restore command as described in Starting the restore operation.
- The restoration process includes Actions metadata but assumes external storage is already accessible and configured.
-
Finalize settings in the {% data variables.enterprise.management_console %}.
-
Re-register self-hosted runners:
All runners must be re-registered with the restored instance, as previous registration tokens are invalid after a restore.
For more information, see AUTOTITLE.