AWS Backup » History » Version 9
Version 8 (Greg Mathis, 05/10/2018 08:45 AM) → Version 9/32 (Greg Mathis, 05/10/2018 08:54 AM)
h1. AWS Backup
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.
h2. Step 1, Create AMI
Log into the AWS console, go to the instances tab, select the server instance to back up, right click, select Image->Create Image.
!picture846-1.png!
Now name the image, check the "No reboot" box, then select "Create Image"
!picture62-1.png!
You should see Create Image request message below.
!picture953-1.png!
h2. Step 2, Prepare AMI
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).
!picture735-1.png!
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)
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.
h2. Step 1, Create AMI
Log into the AWS console, go to the instances tab, select the server instance to back up, right click, select Image->Create Image.
!picture846-1.png!
Now name the image, check the "No reboot" box, then select "Create Image"
!picture62-1.png!
You should see Create Image request message below.
!picture953-1.png!
h2. Step 2, Prepare AMI
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).
!picture735-1.png!
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)
