Getting started with EC2 backup to Druva Cloud
The overall backup workflow on Druva Cloud is illustrated below:
Note: To enable this feature, you will need to update your AWS Access Role by deploying the latest CloudFormation template for each account in which you intend to provision Druva Cloud. For more information, see Update Existing AWS Access Roles in Druva CloudRanger.
Ensure that you have set appropriate service quotas for your EBS Direct Service prior to setting up the backup workflow on Druva Cloud. The quota limits will need to be set to an appropriate level to avoid performance-related issues. To request a service quota increase, navigate to the Service Quotas page on your AWS console.
• Set the GetSnapshotBlock requests per account to an appropriate value that corresponds to the number of devices that you wish to protect concurrently.
We recommend setting this to approximately 250 * the number of protected devices, to ensure a smooth backup performance across your AWS accounts.
• You may want to calibrate this value based on your data protection strategy and business requirements.
For more information, refer to the AWS documentation.
Step 1: Provisioning Storage on Druva Cloud
To get started, you will first need to provision storage on Druva Cloud. Once you initiate a storage request, this triggers a Support ticket to provision the storage on Druva Cloud based on your agreed credit limits.
Note: If you are currently not setup to use your SSO credentials via Druva Cloud Platform, you will first need to get your DCP account configured. On initiating the cloud storage request, Druva Support will configure the required credentials for your Druva Cloud Platform account. You may receive an email communication detailing the steps to set up and activate your DCP account.
If you have logged in to Druva CloudRanger via DCP or have a Phoenix account, all your existing Druva storage is displayed on the Storage page. For more information, see Provision Storage on Druva Cloud.
Step 2: Configure Storage Rules
Storage Rules help create a mapping between Druva Cloud and your AWS resources within specific Regions and Accounts. Once you identify the AWS resources to be backed up to Druva Cloud, the Storage Rules direct the data backups to the appropriate Druva Cloud Region provisioned within your chosen Account.
Note: You will need to configure Storage Rules to get started with backing up snapshots to Druva Cloud. A backup policy defined to move snapshots to Druva Cloud will be executed only when a corresponding Storage Rule is available.
Storage Rules are integral to your Druva Cloud data protection workflow. For more information, see Configure Storage Rules.
Step 3: Manage Client Credentials
Client Credentials enable access to your AWS Key Management System (AWS KMS) to generate and manage the data encryption key (ekey). The ekey once generated is used to encrypt the user data that is then backed up to Druva Cloud.
To get started with ekey management, you will need to import the relevant credentials to your Druva CloudRanger account. For more information, see Manage Client Credentials.
Step 4: Automate data protection with backup policies
Druva CloudRanger offers a simplified approach to backup policies, with options to define one or more policies to automate your backup schedule and retention for EC2 backups on Druva Cloud. Once defined, backup policies can be executed across AWS accounts at the organization level, and set to Active or disabled, depending on business requirements. For more information, see Manage Backup Policies.
Step 5: Manage your data protection workflow
With backup policies in place, your data protection schedule is automated based on your retention settings. You may still initiate backups to Druva Cloud on-demand or choose to restore snapshots. For more information, see Backup to Druva Cloud Workflow.