Skip to main content

How can we help you?

Druva Documentation

Create Backup Policies

Step-by-step guide on how to create a backup policy for your AWS workloads in Druva CloudRanger.

This article provides a step-by-step guide on how to create a backup policy for your AWS workloads in Druva CloudRanger. You can create policies to backup your Amazon EBS, EC2, RDS, and Redshift resources. 

To create a backup policy:

Step 1: On the top navigation bar, select Policies, and then click Create Backup Policy.


Step 2: Specify the backup Schedule.


  • Add a Name and a brief Description of your policy.
  • Specify the backup Frequency.



Create backup every

Choose the backup frequency by day, week, month, or year.
For example:
Backup every week on Monday every hour at 30 minutes past the hour.
Backup every month on the 1st day of the month every 30 minutes.

Backup window

[Optional] Specify the backup from and to time in HH:MM notation.

Note:  This field applies only if you specify weekly backup every hour in the Create Backup Every field.

Time zone

Select the time zone that applies to the backup frequency specified.

  • Click Save & Continue.

Step 3: Specify the backup Retention criteria.

BP5 No S3.png

Note: Druva CloudRanger follows the Grandfather-Father-Son (GFS) retention model. For more information on retention, please see About Retention for Backup Policies.
  • Specify the Retention criteria. The standard retention options are pre-populated that you can modify based on your business requirements.



Tiered Retention

Select this option to specify the criteria for tiered retention of backups.

  • All backups retained for: Select the retention duration in hours, days, weeks, months, or years.
  • Select the retention criteria for Weekly, Monthly, or Yearly Backups.

You can choose to modify the default retention duration that is pre-populated.

Never delete

[Optional] Select this option to retain snapshots indefinitely.

Archive to S3  
Move backups to S3

Select the checkbox and specify the Storage Class to which the backup is to be transitioned as well as the retention period.
Example: Move weekly, monthly, and yearly backups to Glacier after 3 weeks.

Note: The storage class policy settings specified here will override any policy-based retention when moving a snapshot with an associated backup policy
Store backups in Select the Druva CloudRanger account and AWS region to which the backup is to be archived.
Additional Copies

Save extra copies to other regions

  • Select this checkbox to create additional copies of your AWS backups in multiple regions.
  • Specify up to two additional AWS regions to create copies in.

Save an extra copy to another account


  • Select the checkbox to create additional copies of your AWS backups in another CloudRanger account.
  • Specify the AWS region to create copies in.

Copy Options

Specify the retention criteria for the additional backup copies.

  • Select Same retention as source backup to retain the retention criteria.
  • Alternatively, you may specify the retention in hours, days, weeks, months, or years.
Note: Cross-region and cross-account backups are not supported for DynamoDB and Redshift instances.
  • Click Save & Continue.

Step 4: Specify the Resources for backup.


  • On Include Resources, click Add to identify resources that you wish to include in the backup.

  • On the Identify Resources page, specify the filter criteria to identify specific resources to include or exclude:
How Include/Exclude conditions apply on Druva CloudRanger
  • You can create multiple include and exclude rules.
  • Include rules: When multiple include rules are defined, this translates to an ‘OR’ condition. In other words, resources are matched against each include rule, and do not have to meet all specified conditions concurrently.
  • Exclude rules: Exclude rules take precedence when the same resource is matched based on the include and exclude criteria selected.
    An exception to this is when an EC2 resource is selected within include and an EBS volume within exclude. In such a scenario, the EBS volume that is part of EC2 will not be excluded from the backup.
  • When multiple tags are defined as part of include/exclude, this translates to an ‘AND’ condition.



Find Resource types

Select the Resource Type, for example, EBS Volume, EC2, RDS, or Redshift.
You may select All resource types to filter resources across resource types.

In account

Select the CloudRanger account associated with the AWS resources to be specified.
You may select All accounts to identify resources across accounts.

And in region

Select the applicable AWS regions, or select All regions.


Select the match criteria by Resource IDs, Tags, VPC IDs, Subnet IDs, or select All resources.
Based upon the Match selected, you will need to specify the criteria values appropriate to that criteria.
For example:
Tags: Backup Type; Values: Daily
VPC IDs: Select by VPC IDs or VPC Name

  • Similarly, on Exclude Resources, click Add to identify specific resources that you wish to exclude from the backup.
  • The resources identified are then displayed under Include or Exclude Resources, based on your selection criteria.
  • To eliminate a specific resource in the list from your backup policy, select the checkbox against that resource, and click Remove.

Note: The Backup Copy Encryption is applicable only if one or more resources included in the policy is encrypted, and a backup is to be generated. If the source resource is encrypted, then an Encryption Key is applied to the backup operation.

The Backup Copy Encryption options are displayed only if a cross-region or cross-account backup is to be generated for encrypted snapshots.

  • To backup encrypted resources, you will need to define the association of keys between the source and the target regions for that backup.
    To do this, select the Target Key for each target region specified.


  • Under Resource Backup Options, you have the option to create backups of EC2 resources as AMIs or as snapshots. In the case of AMIs, you may also select your reboot preferences.
  • Click Save & Continue.

Step 5: Specify Additional Options for the backup.


  • Select the Execute VSS Consistent Scripts (Windows Only) checkbox to generate consistent snapshots for any Windows server with VSS installed.
Note: If the selected Backup Policy has servers defined that do not have VSS installed, then a standard AWS EBS snapshot is generated. For more information, please see Generate VSS consistent snapshots for Windows servers.
  • Script Execution: The pre- and post-backup scripts feature offers enterprises the option to generate application-consistent snapshots for common applications like SQL Server. This ensures that the point-in-time snapshots will remain crash-consistent as well as application-consistent.
    • Select the Execute pre- and post-scripts for EC2 instances checkbox to enable script execution when creating a new backup policy.
      In addition, you can manage backup generation in the event that the scripts configured are unavailable.
    • Define the time limit to terminate script execution.
      For exampleAbort script execution in 5 minutes
    • Select the backup execution criteria if the script is unavailable.
      • Execute backup without the script: Selecting this option will execute the backup without the configured script.
      • Attempt backup execution with warning: Selecting this option will initiate the backup but fail it at the point of execution of script.
      • Fail the backup and generate an error: Selecting this option fails the backup and generates an error corresponding to the backup failure.

Note: You may configure scripts to specific resources from the main Scripts page. For more information, see Configure and Manage Backup Scripts.

  • Under Add Tags to Backups specify the tags to be applied to each backup generated by the policy. Tags act as metadata to help identify and organize your AWS resources. Based on the Key selected, you will need to specify the appropriate Value. For example:
    Key: Created by Policy; Value: New
    Key: Origin; Value: Specify Origin ID
  • Select the Inherit tags from Source checkbox to inherit or retrieve tags from the Origin servers and apply them to backups generated by the policy.
  • Click Save.
Note: To manage tags on existing snapshots, please refer to AWS Management Console - Tag Editor.

The backup policy is now successfully defined and is displayed on the main Backup Policies page with the State toggle set to Active.

Modify backup policy state

You can choose to set a backup policy to Active or Disable it. When a new Backup Policy is defined, the State toggle is set to Active by default.

Note: Disabling a policy suspends all associated activities including backup retention and cleanup.

To modify the state of the backup policy, click the State toggle icon against the backup policy.