Standardize backup instructions for upgrades
When searching "upgrade GitLab" on Google, the top two results were https://about.gitlab.com/update and https://docs.gitlab.com/omnibus/update/. The first page advises users to take a backup before updating GitLab and provides a command. The second page advises users that backups are automatically taken during the update.
Is there any difference in the data that is backed up if I a) let GitLab automatically back up my database during the update, versus b) run
sudo gitlab-rake gitlab:backup:create STRATEGY=copy prior to updating?
- If there is no difference in the data that is backed up using the two different methods, remove Step 1 from https://about.gitlab.com/update
- Consider removing the https://about.gitlab.com/update page altogether and having https://docs.gitlab.com/omnibus/update be the SSoT for updating GitLab so that we don't need to maintain two separate sets of instructions and risk divergence.