Geo: Support database backup from secondary
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
There may be a noticeable performance penalty when running a regularly scheduled rake backup task against a large primary postgresql database.
Proposal
For performance-minded customers managing large geo-replicated and heavily-used instances, it may be beneficial to avoid backing up the primary database (i.e. as gitlab-rake gitlab:backup does) and instead take the backup from the geo-replicated secondary.
This could be a configurable setting in GitLab.
Other Considerations
It's important that the restore of a secondary backup behave similarly to the primary backup. I would call #209813 (closed) a prerequisite, or at least closely-tied.
It is documented that Geo secondaries cannot be used for backups. Remove/revise that documentation this is implemented.