Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm going to use an EC2 instance for DR purposes of my SQL 2008 server. My plan is to ship the transaction logs for ~500 databases up to AWS and then restore them to an EC2 instance running SQL.

I'm going to be using a PowerShell script on each side (1 to send the T-Logs to Amazon, another to restore them).

I'm trying to decide if I should ship them directly to EC2 or ship them to S3. My thoughts on using S3 were that it would always be available and allow me to take down the EC2 instance without disrupting the transfer of the files to Amazon.

Any thoughts on the best way to handle this?

share|improve this question
up vote 1 down vote accepted


You have the right idea. S3 is permanent, easy to push to and fetch from. S3 has many uses but this is most defiantly one of them.

using an EC2 instance for this would be possible, but would really not be worth it, and you would probably want to store in S3 anyway rather than EBS.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.