1 Comment

Summary:

The new ability of AWS users to move EBS storage volumes between Amazon’s regions could drastically improve disaster recovery scenarios. Amazon announced this EBS Snapshot Copy feature early on Tuesday.

Source: Barb Darrow

In what could be a big improvement for business users of Amazon Web Services, Amazon is now allowing them to  move data snapshots between Elastic Block Storage (EBS) regions. The news was announced on an AWS support forum.

awslogojpegIt should come as especially good news for AWS customers shanghaied  by snafus earlier this year at Amazon’s big US-East data center complex. According to Amazon’s post-mortem, the October 22 “event”  started, when “a small number of Amazon Elastic Block Store (EBS) volumes in one of our five Availability Zones in the US-East Region began seeing degraded performance, and in some cases, became ‘stuck’ (i.e. unable to process further I/O requests).”

To be clear, you could move snapshots between availability zones within a given AWS region. And you could move snapshots between AWS regions before, but it required quite a bit of work and usually the use of a third-party technology like Ylastic. It was, in short, a pain. Now, in theory, if customers spread data volumes across regions will be less susceptible to issues in a single data center geography.

Per the forum post:

“EBS Snapshot Copy enables you to copy your EBS snapshots across AWS regions, thus making it easier for you to leverage multiple AWS regions and accelerate your geographical expansion, data center migration and disaster recovery.

EBS Snapshot Copy is simple to use. In the AWS Management Console, you can select the snapshot to be copied, set the destination region, and start the copy. This feature can also be accessed via an EC2 Command Line Interface or an EC2 API as described in the EBS Snapshot Copy page. The copied snapshot behaves the same as other snapshots in the destination region: it can be used to create new EBS volumes which can then be attached  to an EC2 instance in the destination region.

For AWS geeks, this is indeed big news. Said one: “Up until now, we either had to write code or use a service like Ylastic for $50 a month to move volumes between regions. This will greatly simplify cross-region disaster recovery set up for us.”

  1. It was previously unavailable or of little value to the SMB market – create and test a Disaster Recovery (DR) plan and, just as importantly, create and test a Business Continuity Plan (BCP). From an information systems perspective, DR planning covers the steps from identification of a disaster, to ensuring that systems are restored to operation within the time period required by the business, the Recovery Time Objective (RTO), and with access to the data to the period required by the business, the recovery point objective (RPO). The BCP takes over after the disaster has been contained. It focuses on the steps to ensure that the people and processes can return to work, even in a temporary environment while recovering to a “permanent” state.
    Read more: http://www.dincloud.com/blog/Business-Continuity-Using-the-Cloud-for-SMBs

Comments have been disabled for this post