DataCore & AWS DR Strategies

Dec 01, 2016 AT 10:37 AM

Many are looking to migrate workloads or setup a DR strategy to the cloud, and it soon becomes very apparent that doing so can become complex and expensive. It’s my goal in this post to illustrate a couple inexpensive and easy ways to move data to the cloud using DataCore software. The focus of today’s post will be using Amazon AWS and the integration options available, however this is certainly not a limiting factor as there are other cloud offerings that can also be utilized using DataCore software. 

There are two ways for someone to migrate, replicate, move or backup data between an on-premises DataCore installation and an Amazon service. The first way is using the AWS Storage Gateway appliance. This local appliance securely transfers your data to AWS over SSL, and securely stores your data in Amazon S3 and/or Amazon Glacier. You can use this service to backup and archive one’s storage but the gateway can also be used to migrate workloads to the cloud. 

The Amazon gateway can also be used with DataCore’s tiering functionality as mentioned in Jeff Slapp’s post recently.

For example, the AWS Storage Gateway can take a snapshot of your on-premises data volumes exposed to DataCore, so that it can be transparently copied into Amazon S3 for backup. You can then subsequently create local volumes or Amazon EBS volumes from these snapshots to run the workloads on AWS EC2 instances. Notice in the diagram that the replication moves the data first to Amazon S3 at which an AWS snapshot can be taken, then it can be attached as an EBS volume to an EC2 instance. Note, this method doesn’t require a separate DataCore node to reside on AWS. 

For more information on the Amazon Storage Gateway product, check out this overview as it has a new interface to expose migration, bursting and tiering use cases.


The second way to migrate data to AWS is using our own DataCore replication functionality. This can be done synchronously or asynchronously depending on your use case constraints between an on-premises DataCore node and an DataCore AWS EC2 windows instance. 


This means one would install DataCore software on a EC2 windows instance where it would be connected to an on-premises DataCore node using either either use a VPN or AWS Direct Connect service. This allows you to mirror your data synchronously or setup an asynchronous policy for transparent data migration to AWS. Once the data has been migrated to AWS it then becomes possible to take a DataCore snapshot for prosperity or further migrations to another AWS region or availability zone.  As an optional step you could also take a AWS snapshot like in the first example, however one would need to make sure that all data has been persisted on the EBS volume so that there is data consistency. 

Another great post that goes into detail regarding DataCore migration strategies can be found here.

As you can see there are two great ways to migrate your on-premises workloads to AWS. All without the heavy expense of a consultant or specialized expensive transcoding software to move data blocks. The next post in this AWS series will look at performance options using DataCore software on Amazon AWS.