Create a complete system-level backup, or Ensure your backups are complete and current.Scheduled maintenance with a broadcast message banner. Some time before your migration, consider notifying your users of upcoming.This type of problem can occur with other services as well, such as aĪ non-packaged Redis instance, or non-packaged Sidekiq. Processing email at the same time, then both instances miss some data. Incoming email, if both GitLab instances are Servers could connect concurrently and process the same data.
If you’re running GitLab Geo, an alternative option is Geo disaster recovery for planned failover.Īvoid uncoordinated data processing by both the new and old servers, where multiple This section outlines a typical procedure for a GitLab deployment running on a single server. You can use GitLab backup and restore to migrate your instance to a new server. Restore GitLabįor detailed information on restoring GitLab, see Restore GitLab. Back up GitLabįor detailed information on backing up GitLab, see Backup GitLab. You can mitigate all of these risks with a disaster recovery plan that includes backups. You need to ensure this data is protected from adverse events such as: Your software or organization depends on the data in your GitLab instance. Related features Back up and restore GitLab.Prepare and transfer content from the old server.
0 kommentar(er)
