AWS Backup » History » Version 8
Greg Mathis, 05/10/2018 08:45 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! |
