Replication or redundancy of your GitHub Actions data
GitHub Actions 使用外部存储来存储工作流程工件和日志。 此数据存储在外部提供商上，例如 Azure Blob 存储、Amazon S3、Google Cloud Storage 或 MinIO。 因此，GitHub Enterprise Server 备份和 GitHub Enterprise Server 高可用性配置无法为存储在此外部存储上的数据提供保护，而是依赖于外部存储提供商（如 Azure、Google Cloud或 AWS）提供的数据保护和复制。
We strongly recommend that you configure your GitHub Actions external storage to use data redundancy or replication. For more information, refer to your storage provider's documentation:
High availability replicas
Promoting a replica
When enabling a high availability configuration, any replicas are automatically configured to use the GitHub Actions external storage configuration. If you need to initiate a failover to promote a replica, no extra configuration changes are required for GitHub Actions.
For more information, see "发起到副本设备的故障转移."
Removing a high availability replica
Avoid letting multiple instances to write to the same GitHub Actions external storage. This could occur when using the ghe-repl-teardown command to stop and permanently remove a GitHub Actions-enabled replica. This is because the replica will be converted into a standalone GitHub Enterprise Server, and after the teardown it will still use the same external storage configuration as the primary.
To help avoid this issue, we recommend either decommissioning the replica server or updating its GitHub Actions configuration with different external storage.