AWS re:Invent Recap Day 1

After only the first day of AWS re:Invent, it’s clear that attitudes, perspective, and approaches to disaster recovery and data management are changing. The traditional on-premises hardware and colocation architecture can’t hold up in today’s fast-paced world of immediate demands and strict service level agreements.

And if you were wondering what separates Druva from its competitors, today’s joint “chalk talk” session with AWS was a good place to start.

Bhaskar Sirohi

In the session with Isaiah Weiner, Sr. Mgr. Solutions Architecture, Amazon Web Services, Inc., Druva’s Bhaskar Sirohi, Director Global Solutions Architect, walked through the changing needs of disaster recovery and data management, and how organizations can utilize a cloud-based data management solution. However, during the Q&A session, questions continuously steered to the changing approaches of enterprise IT as it increasingly moves to the cloud. After a session full of questions, it’s clear there are a number of concerns on the minds of every enterprise migrating to the cloud:

1. How do you migrate global data centers to a cloud and ensure data remains in the proper regions?

To meet global data residency law Druva leverages AWS global footprint to offer storage in regions around the globe. Through Druva products like Phoenix and CloudRanger, customers are able to protect their data and ensure it meets any regulatory or compliance needs.

2.What sort of backup solution do enterprises need to consider when moving workloads to the cloud?

When evaluating solutions, it’s important to consider cloud-native solutions that enable customers to scale on demand. A single solution that helps organizations meet consistent SLAs is preferable when compared to a multi-vendor approach with non-integrated, disparate solutions which can result in data silos, lack of visibility, and increasing business risk.

A comprehensive solution should enable disaster recovery in the cloud, clone VPCs, and automate disaster recovery testing for compliance reasons while enabling organizations to reduce costs and meet governance and regulatory requirements.

3. How do you do disaster recovery in the cloud?

Druva has two approaches to cloud backup and recovery: Druva Phoenix, which supports on-premises data center workloads, and Druva CloudRanger, which is designed for data already in AWS cloud environments.

Druva Phoenix enables disaster recovery in the cloud based on backed up virtual machines on-premises. Once a virtual machine has been backed up into the Druva Cloud Platform, those are then converted into AMIs and kept “at-the-ready” in the customer’s VPC S3 storage. This enables customers to boot up EC2 instances at the time of a disaster.

CloudRanger provides the ability to clone VPC across regions while enabling organizations to recover data within minutes if a VPC was to go down. Furthermore, with CloudFormation templates, customers can optimize, update and modify the disaster recovery plans and customers can automate testing for disaster recovery to easily meet compliance requirements.

4. How do I make my company comfortable with a zero-hardware solution?

It is not a question of making companies “comfortable”. It is more about if an organization has a cloud initiative and if the cloud solution can better meet their business continuity SLAs compared to an on-premises hardware solution. Druva Phoenix provides various models to help with business continuity SLAs – direct to cloud, CloudCache, and Snowball Edge. CloudCache enables organizations to have a local cache for up to 30 days on-premises for hot restores and provides high performance backups and recovery, thereby meeting RTO and RPO requirements. Meanwhile, Snowball Edge, offered at no additional cost, enables organizations to seed large volumes to the cloud quickly as well.

5. How can Druva solutions help reduce disaster recovery costs?

As a cloud-native solution, Druva minimizes the appliances and software investment required. Customers only pay for what is used, there is no need to buy hardware or storage in advance. Additionally, users only pay for data stored in the cloud post global deduplication which ensures only a single copy of data is stored in the cloud.

Additionally, by eliminating a multi-vendor approach for data protection with a single pane of glass to protect and manage enterprise data, there are no egress or restore charges. And once you are in the cloud, Druva CloudRanger helps with auto scheduling of resources, enabling users to turn them off when not in use and snapshot management via retention policies.

Want to learn more about Druva Cloud Platform and if your solutions are right for you? If you’re in Las Vegas or coming into town, be sure to stop by the Druva booth #1039 to learn more about Druva’s approach to data management!