Bug 1022764

Summary: Add a note about the backup instance
Product: [Community] PressGang CCMS Reporter: Matthew Casperson <mcaspers>
Component: DocumentationAssignee: pressgang-ccms-dev
Status: ASSIGNED --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.2CC: cbredesen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matthew Casperson 2013-10-24 01:05:53 UTC
A backup instance of PressGang has been setup at http://pressgang.lab.eng.pnq.redhat.com:8080/pressgang-ccms-ui. This instance is read only, and contains a copy of the database from the last backup, which is done around 6AM AEST every morning.

Comment 1 Jared MORGAN 2013-12-18 04:57:00 UTC
I've documented this in:

Back-up (Read-only) Instance of PressGang CCMS [26702]

Why do we have this though, if it is read-only? I want to put in some suggestions for use of the back-up server so folks know why it exists.

Comment 2 Lee Newson 2013-12-18 05:22:50 UTC
Matt would probably be the better one to explain this, but I believe the idea behind is was so that users could still access their data if the main production server was down (ie for maintenance, or a larger issue).

Anyways since I don't know the exact details I'm moving the needinfo over to Matt.

Comment 3 Matthew Casperson 2014-03-17 20:26:13 UTC
The server holding the readonly instance will be part of a PressGang cluster, although we don't have a time scheduled to do the work required to cluster the back end at this time.

Until this happens, the read only server provides us with the ability to verify our backup procedures, to provide people with access to their content (from the last backup) in the event that the main server goes down, and to have a server configured and ready to go in the event that the main server is inoperable for an extended period (switching off readonly takes only a minute or so).