[DOCU-730] create a disaster recovery page that covers most common use cases Created: 21/Apr/16  Updated: 30/Sep/19  Resolved: 30/Sep/19

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Done Votes: 0
Labels: HowTo, outdated
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Topics to be covered:

  1. A section on what pieces of the system need back up. Customers need to understand how their architecture choice may limit their backup options. For example, keeping the app sever separate from the db server.
  2. Magnolia Backup module - While the backup module "works" it has known bugs and can be difficult to use if you're not super familiar with it. In times of real crisis using it could create a frustrating situation. Often the people in charge or performing a restore aren't the people using magnolia. DB admins, systems admins, etc. Often I recommend customers use this module as a second line of defense.
  3. Virtualization approach
  4. DB and repository (filesystem) backups. Usually nightly. Involves shutting the system down to perform the backup.
  5. Customers using oracle may choose to store everything in the DB. The Oracle product has more sophisticated backup options.
  6. Maybe a section on what amazon offers, or rackspace perhaps. If anything.


 Comments   
Comment by Julie Legendre [ 30/Sep/19 ]

In order to better focus our efforts on DOCU tickets that are still relevant and important, all tickets older than 18 months have been labelled as outdated and are being automatically closed.
If you think your ticket is still relevant and should remain open, please add a comment and set it back to open.

Generated at Mon Feb 12 01:11:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.