GitHub Actions uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, GitHub Enterprise Server backups and GitHub Enterprise Server high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS.
If you use GitHub Enterprise Server Backup Utilities to back up your GitHub Enterprise Server instance, it's important to note that GitHub Actions data stored on your external storage provider is not included in the backup.
This is an overview of the steps required to restore your GitHub Enterprise Server instance with GitHub Actions to a new appliance:
- Confirm that the original appliance is offline.
- Manually configure network settings on the replacement GitHub Enterprise Server appliance. Network settings are excluded from the backup snapshot, and are not overwritten by
- Configure the replacement appliance to use the same GitHub Actions external storage configuration as the original appliance.
- Enable GitHub Actions on the replacement appliance. This will connect the replacement appliance to the same external storage for GitHub Actions.
- After GitHub Actions is configured with the external storage provider, use the
ghe-restorecommand to restore the rest of the data from the backup. For more information, see "Restoring a backup."
- Re-register your self-hosted runners on the replacement appliance. For more information, see Adding self-hosted runners.
For more information on backing up and restoring GitHub Enterprise Server, see "Configuring backups on your appliance."