Skip to content

Add warning to stop Puma and Sidekiq when restoring from backup

Stan Hu requested to merge sh-document-stop-sidekiq-puma-backup-restore into master

As we saw in #36405 (closed), having processes that can write to GitLab tables while restoring from a database backup can cause duplicate rows be inserted and schema changes to fail quietly. At the moment, we don't have a good story of restoring a database backup in a single transaction, so we need to tell admins to stop Puma and Sidekiq.

Before

image

After

image

Edited by Stan Hu

Merge request reports