Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1441183

Summary: backups.gluster.org offline
Product: [Community] GlusterFS Reporter: Nigel Babu <nigelb>
Component: project-infrastructureAssignee: Nigel Babu <nigelb>
Status: CLOSED WORKSFORME QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: 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: 2017-11-24 10:11:20 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 2017-04-11 12:12:00 UTC 
The backup server has been offline for some time. I'm wondering if it's worth resetting it entirely and bringing up a new machine with a good strategy to figure out what needs to be backed up and having the backups set in Ansible (if it isn't already)

At some point, we should establish the process of restoring something from backup and test it regularly. For example, restoring Jenkins from backup is going to need some documentation to get right. Perhaps it's even worth automating a prod -> staging push every week so we can test things better.
Comment 1 M. Scherer 2017-08-30 16:53:46 UTC 
I did install another backup server a few month ago:
https://github.com/gluster/gluster.org_ansible_configuration/commit/40202aa41a732a41d68c2c36df498eca089b7a9e

We have doc awaiting some reviews too:
https://github.com/gluster/infra-docs/pull/23
Comment 2 Nigel Babu 2017-11-24 10:11:20 UTC 
This is now back online.