access:access_server_2013_robustification_project
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
access:access_server_2013_robustification_project [2013/04/04 00:27] mjallison [Server Architecture Improvements] |
access:access_server_2013_robustification_project [2013/04/05 19:02] (current) mjallison [Possible Solutions] |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| ===== Possible Solutions ===== | ===== Possible Solutions ===== | ||
| + | |||
| + | AWS Tools | ||
| + | * RDS snapshots, currently being done and retained for last 3 days. (50Gib) Can restore from a snapshot. | ||
| + | * EC2 snaps shots done once per day, keeping last two days (100 GiB) Can restore from snapshot. | ||
| + | * EBS Snapshots can be moved between regions. | ||
| + | * AWS console operations (new instance, snapshot, etc) can be automated. | ||
| Virtual Machine failure recovery strategies | Virtual Machine failure recovery strategies | ||
| Line 41: | 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 | ||
| Line 50: | Line 65: | ||
| * SQL customer tables; assetid, association, gps, rtk, rtktrack, track, vehicle | * SQL customer tables; assetid, association, gps, rtk, rtktrack, track, vehicle | ||
| * SQL customer tables; tsm, tmm, device | * SQL customer tables; tsm, tmm, device | ||
| + | * Remove SupportTool tabs for Devices, Trackwork Modules, Trackwork Servers (associated tables if not already present). | ||
| ===== Server Architecture Improvements ===== | ===== Server Architecture Improvements ===== | ||
| The following areas are routine maintenance items and/or feature requests that need to be done. The timing is right to do these at the same time as the other efforts. | The following areas are routine maintenance items and/or feature requests that need to be done. The timing is right to do these at the same time as the other efforts. | ||
access/access_server_2013_robustification_project.1365035268.txt.gz · Last modified: 2013/04/04 00:27 by mjallison
Page Tools
