This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
access:access_server_2013_robustification_project [2013/04/05 18:41] mjallison [Possible Solutions] |
access:access_server_2013_robustification_project [2013/04/05 19:02] (current) mjallison [Possible Solutions] |
||
---|---|---|---|
Line 47: | Line 47: | ||
* Most storage issues appear to be related to the Access Java Client, fix it. | * Most storage issues appear to be related to the Access Java Client, fix it. | ||
* Track storage can be moved to S3, increasing the safety of track storage. | * Track storage can be moved to S3, increasing the safety of track storage. | ||
+ | |||
+ | ===== Recommended Solution ===== | ||
+ | * TBD: Identify robustness goals, recovery speed, etc. to guide solution selection. | ||
+ | * Attend April 30 AWS conference to get briefed on more AWS tech. | ||
+ | * Document modern (2013) system architecture | ||
+ | * Document failover process (for manual recovery), recovery procedures for failure modes. | ||
+ | * Modify AccessSupport tool to automate instance creation (from existing AMI-create snap of existing AMI, reattach EBS), recover EBS from snaps, repopulate DB from backup snap, | ||
+ | * Modify AccessSupport tool to copy snaps to another region to prep for region failover process. | ||
+ | * Consider auto copy snaps to another region for backup. | ||
===== Possible Track items to consider at the same time ===== | ===== Possible Track items to consider at the same time ===== | ||
Likely only make these modifications when we rework a track product | Likely only make these modifications when we rework a track product |