On this page
Record the running installation
Note the exact GitLab version, edition, hostname, deployment type, and external storage services. A database dump alone is not a complete GitLab recovery plan.
Keep the full recovery set
Use the supported GitLab backup procedure for repositories and application data. Preserve configuration and the matching secrets file separately. Data in external object storage may require separate protection.
Match the restore target
GitLab restore requires the exact compatible version and edition of the backup. Missing secrets can break encrypted values, runner access, or two-factor authentication. Do not paste those files into chat or attach them to a ticket.
Verify in isolation
Restore to a fresh test destination, keep outgoing integrations controlled, and verify repositories, uploads, sign-in, and representative data. Restoring can overwrite database data; it is not a harmless diagnostic step.