AWS Backup » History » Version 16
Greg Mathis, 05/10/2018 09:15 AM
| 1 | 1 | Greg Mathis | h1. AWS Backup |
|---|---|---|---|
| 2 | 1 | Greg Mathis | |
| 3 | 2 | Greg Mathis | We use Perforce and Redmine running on an AWS Server. Our backup strategy is to simply create an Amazon Machine Image (AMI) of the current server state. This AMI can then be used to launch a new server instance which will look just like the original, preserving all Perforce and Redmine data. |
| 4 | 2 | Greg Mathis | |
| 5 | 3 | Greg Mathis | h2. Step 1, Create AMI |
| 6 | 2 | Greg Mathis | |
| 7 | 2 | Greg Mathis | Log into the AWS console, go to the instances tab, select the server instance to back up, right click, select Image->Create Image. |
| 8 | 4 | Greg Mathis | !picture846-1.png! |
| 9 | 5 | Greg Mathis | |
| 10 | 6 | Greg Mathis | Now name the image, check the "No reboot" box, then select "Create Image" |
| 11 | 5 | Greg Mathis | !picture62-1.png! |
| 12 | 7 | Greg Mathis | |
| 13 | 8 | Greg Mathis | You should see Create Image request message below. |
| 14 | 1 | Greg Mathis | !picture953-1.png! |
| 15 | 8 | Greg Mathis | |
| 16 | 8 | Greg Mathis | h2. Step 2, Prepare AMI |
| 17 | 8 | Greg Mathis | |
| 18 | 8 | Greg Mathis | Go to the AMI tab on the AWS console. You should now see the new AMI. (It actually could take a few minutes to appear). |
| 19 | 8 | Greg Mathis | !picture735-1.png! |
| 20 | 9 | Greg Mathis | |
| 21 | 9 | Greg Mathis | As part of our backup strategy, we create another server instance of our backup AMI, but we actually run this instance on an entirely different AWS account. The idea here is if the primary AWS account is hacked somehow, and the backup AMI's are deleted, hopefully our "backup" AWS account is not also hacked, and we have a "hot spare" ready to go (Redmine should work right away, but we would need a new Perforce license for the backup server's IP address) |
| 22 | 10 | Greg Mathis | |
| 23 | 15 | Greg Mathis | To share this backup AMI with another AWS account, we have to modify the backup AMI's permissions. This step assumes you have already set up a backup AWS account and you have the account id handy. Select the backup AMI, right click, and select "Modify Image Permissions". |
| 24 | 13 | Greg Mathis | !picture968-1.png! |
| 25 | 14 | Greg Mathis | |
| 26 | 15 | Greg Mathis | You should then see the following window. Enter in the AWS Account Number of the backup AWS account, select "Add Permission", then check the "create volume" box and then select save. |
| 27 | 14 | Greg Mathis | !picture841-1.png! |
| 28 | 16 | Greg Mathis | |
| 29 | 16 | Greg Mathis | At this point this backup AMI is ready to be grabbed by the backup AWS account. So now log in to the backup AWS Console and go to the instances tab. Below is what my backup AWS server currently looks like. For no particular reason, 2 backup servers are running. Only 1 is really necessary. |
| 30 | 16 | Greg Mathis | !picture448-1.png! |
