Esta versión de GitHub Enterprise Server se discontinuará el 2026-08-25. No se admiten versiones discontinuas. No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para mejorar el rendimiento, mejorar la seguridad y las nuevas características de GitHub Enterprise Server, consulte Información general del proceso de actualización. Para obtener ayuda con la actualización, GitHub Soporte técnico empresarial.

Restoring with GitHub Actions enabled

Learn how to prepare for and restore backups when GitHub Actions is enabled with external blob storage.

Importante

Data stored in your configured external storage for GitHub Actions—such as logs, artifacts, and other blobs—is not included in GitHub Enterprise Server Backup Service snapshots. You must back up this data separately using your storage provider's tools and best practices.

When restoring an instance with GitHub Actions enabled, follow these steps to preserve compatibility with existing Actions data:

  1. Provision the target instance.

  2. Preconfigure Actions storage:

    1. In the Consola de administración, enable GitHub Actions.

    2. Enter the exact same external storage provider and credentials used in the original instance.

    3. Click Save.

      This step ensures the restored Actions metadata correctly references your existing external data.

  3. Enable maintenance mode on the target instance.

  4. Restore the backup:

    1. Run the ghe-restore command as described in Starting the restore operation.
    2. The restoration process includes Actions metadata but assumes external storage is already accessible and configured.

  5. Finalize settings in the Consola de administración.

  6. 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 Copia de seguridad y restauración de GitHub Enterprise Server con GitHub Actions habilitado.