There are many use-cases for cloud adoption, from usage of native cloud Software-as-a-Service applications to agile development of 3rd platform applications using Platform-as-a-Service frameworks, to data tiering for either production or protection data.
But what if you’re moving existing applications to a public cloud?
This can be actual production applications or simply starting test & dev environments in support of production environments. Such moves don’t happen instantly and typically you end up having a mix of large on-premise data-centers and off-premise cloud environments.
We often refer to this as a Lift & Shift type of a scenario – you’re LIFTING existing application and SHIFTing it to a different infrastructure. In this case, the cloud.
This does reduce the need for managing infrastructure availability and resiliency as that responsibility moves to a cloud provider. But that does not eliminate the need for data protection: if data is deleted (inadvertently or intentionally) or corrupted on a logical level (and we know applications never corrupt data, don’t we?), it doesn’t matter on which infrastructure it runs. Furthermore, most businesses typically require more than just the most recent point in time copy of data.
One of the simplest ways to address such data protection requirements is to extend existing data protection solution so it can span both on-premises and in-the-cloud needs – and we got just the right tools for the job!
Introducing EMC NetWorker 9.0 SP1 and EMC CloudBoost 2.1!
So what’s new?
There are many improvements in both products and here we’ll focus on the Lift & Shift scenario:
- You can run both NetWorker and CloudBoost natively inside public cloud such as Amazon’s AWS. And that applies to any component: NetWorker server, storage node, client, management console and CloudBoost appliance.
- And, integration of NetWorker and CloudBoost is now done natively using well-proven & differentiated ClientDirect technology thus bringing efficiencies of deduplication, compression and encryption direct to each client.
What does this mean?
If you combine all of the above, you end up in a very flexible solution where you can have fully isolated environment running in public cloud or simply mix & match with the existing environment.
And that’s where it gets interesting.
You could have number of on-premise NetWorker clients backing up data to Data Domain and off-premises NetWorker clients backing up data to Amazon S3 object storage, both part of the same data zone and controlled by single NetWorker server.
And both sets of clients are fully optimized for their environments: ClientDirect with Data Domain Boost to Data Domain for on-premises workloads and ClientDirect with CloudBoost for in-the-cloud workloads.
Of course, when dealing with public clouds, efficiency and security are imperative.
- While ClientDirect with CloudBoost provides de-duplication, encryption and compression at the source, actual data can be stored on any of the number of supported object storage targets.
- With CloudBoost ClientDirect your data is encrypted at the source using industry leading AES-256 encryption and additionally wrapped with Secure HTTP over the wire.
Both NetWorker 9.0 SP1 and CloudBoost 2.1 will be available shortly.
Vladimir Mandic | Chief Technology Offier & Distinguished Engineer, Data Protection Cloud | EMC² Core Technologies Division