Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Background of our setup:
We've hosted our web-based application in Amazon EC2 US East (Virginia) Region. Our instance is based on Linux distribution (CentOS) and AMI is S3-backed. 1 EBS volume (400 GB size) is attached to this instance.

Question:
We've planned to migrate our deployment to US West (N. California) Region. From AWS doc, I understood that for moving AMI, there is a command-line tool available - ec2-migrate-bundle. But for moving EBS volume across Region, currently there is no tool available.

I'm looking for easiest and/or fastest way of copying/moving EBS volume from one Region to another. Also, are there any hidden risks involved during and/or after the migration?

Experts ideas/suggestions/recommendations on this are highly appreciated.

share|improve this question

2 Answers 2

Amazon recently announced EBS Snapshot Copy which enables to copy EBS snapshots across AWS regions, thus making it easier to leverage multiple AWS regions and accelerate geographical expansion, data center migration and disaster recovery.

NOTE: Amazon EC2 is also planning to launch Amazon Machine Image (AMI) Copy as a follow-up to this feature, which will enable to copy both public and custom-created AMIs across regions.

share|improve this answer

Take a look at this post they explain how to do it. BTW the use cpipe to copy the content across the network, that means 400Gb over the wire :S

share|improve this answer
    
Thanks for that useful link. In that post, there is a command cpipe -vt -b 1024 < /dev/sdf | netcat -q 1 ec2-hostname 9999. But in my CentOS 5.2, I don't find the option -q in netcat command. Any ideas? –  Gnanam Jun 29 '11 at 12:21
    
@Gnanam I couldn't find that option on my nc... I don't know for what it is, also the man documentation do not say anything :S. I think you can try without it to see what happens –  Christopher Valles Jun 29 '11 at 15:44
    
From mine, "-q after EOF on stdin, wait the specified number of seconds and then quit. If seconds is negative, wait forever.". You're probably OK without it, but I suppose it might be useful if there was some lag in pulling the data off the disk. –  El Yobo Jun 19 '12 at 19:58

Your Answer

 
discard

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.