A Deckhouse Code backup consists of an archive with the instance data and of files that the archive does not contain. The contents of the archive are the same for the Linux package and for Omnibus Docker: both deliveries run on the same engine, and the archive in them is created by the gitlab-backup command. The commands and the restore procedure for the package are on the Linux package page.
What the backup contains
The gitlab-backup create command collects into a single archive:
- Repositories
- The database
- Uploads
- CI artifacts
- LFS objects
- The package registry
What is stored separately
The archive does not contain these files, so copy them along with every archive:
/etc/gitlab/gitlab-secrets.json: Encryption keys of the database. Without this file the restore is incomplete: two-factor authentication settings, tokens and encrypted CI variables are lost./etc/gitlab/gitlab.rb: The instance configuration.- Certificates and keys from the
/etc/gitlab/ssl/directory.
Store the secret files with the same level of protection as passwords.
Deckhouse Kubernetes Platform module
In the module delivery, backups are created by the operator on the schedule from the CodeInstance resource and uploaded to object storage: the contents of the archive, the restore preconditions and the command matrix are described in the Backups and restore section of the module documentation.