Bug 1348072
| Summary: | Backups for Gerrit | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Nigel Babu <nigelb> |
| Component: | project-infrastructure | Assignee: | bugs <bugs> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | mainline | CC: | bugs, gluster-infra, mscherer |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-12 12:31:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Nigel Babu
2016-06-20 05:59:49 UTC
This is blocked on having more disk space on the machine. I've brought this up with Michael. Once we move the VM over, we'll add more diskspace. So, what is needed to be backed up exactly ? Postgresql should be ok now, what else ? We'll need to backup /review/review.gluster.org/ entirely. And time it so it's at the exact same time as the postgresql back up. Extra points for switching off apache and xinetd during the duration of the back up (so that gerrit is effectively read-only) Any idea if this is done? Michael, is this being planned in the near future? I need to review the current status, I know we have database backups, but backups is one half of the coin, we also need to test the recovery from end to end. And testing the recovery requires to be able to automate the installation of Gerrit, something that was cautiously delayed due to the criticity of the service (aka, that's still not managed by ansible). This bug is moved to https://github.com/gluster/project-infrastructure/issues/16, and will be tracked there from now on. Visit GitHub issues URL for further details |