Manage Backup Policies
Assigning Policies to Application Groups
Administrators can apply a backup policy to specific Application Groups using Recipes. Once a backup policy is defined, it can be assigned to all application groups tagged with a particular recipe, for example, all application groups labeled with the crash consistent recipe.
Note: Application admins create the Application Definition yaml to assign recipes to application groups via the command-line interface. For more information, see
A backup policy can be mapped to application groups in the following ways:
- Assign policies to Application Groups: You can define a backup policy for Kubernetes application groups using specific labels or Recipes. A backup policy can be defined to be specific to Kubernetes clusters or to other AWS resources.
In other words, you will have to define a backup policy exclusively for those Kubernetes application groups that you wish to protect within a pre-defined schedule and retention. - Map Application Groups labeled with a recipe to a backup policy.
Creating a Backup Policy
Step 1: On the top navigation bar, select Policies, and then click Create Backup Policy.
Step 2: Specify the backup Schedule.
- Specify the backup Frequency.
Field | Description |
Create Backup Every |
Choose the backup frequency by day, week, month, or year. |
Backup Window |
[Optional] Specify the backup from and to time in HH:MM notation. |
Time Zone |
Select the time zone that applies to the backup frequency specified. |
- Click Save & Continue.
Step 3: 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:
Field | Description |
Find Resource types |
Select Application group to filter Kubernetes 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 regions |
Select the applicable AWS regions, or select All regions. |
Match |
Select the match criteria by Resource IDs, Label, or select All resources. Based upon the Match selected, you will need to specify the criteria values appropriate to that criteria. For example: Label: |
- 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. - Click Save & Continue.
Step 4: Specify the backup Retention criteria.
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.
Field | Description |
Retention | |
Tiered Retention |
Select this option to specify the criteria for tiered retention of backups.
You can choose to modify the default retention duration that is pre-populated. |
Never delete |
Select this option to retain snapshots indefinitely. |
Additional Copies | |
Save extra copies to other regions |
|
Save an extra copy to another account |
|
Copy Options |
Specify the retention criteria for the additional backup copies.
|
- Click Save & Continue.
Step 5: Specify Additional Options for the backup.
Note:
Execute VSS Consistent Scripts (Windows Only) applies only to generate consistent snapshots for any Windows server with VSS installed. For more information, please see Generate VSS consistent snapshots for Windows servers.
The Pre- and Post-backup scripts feature ensures that the point-in-time snapshots will remain crash consistent as well as application consistent. For more information, see Setup Script Execution via Backup Policy.
- Under Tags 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 upon the Key selected, you will need to specify the appropriate Value. - 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.
- Select the Recipe, as applicable, for each Application Groups discovered based on the Resources criteria specified.
- Click Save Policy.
The backup policy is now successfully defined and is displayed on the main Backup Policies page with the State toggle set to Active.
For more information on managing backup policies on Druva CloudRanger, see Create Backup Policies.
Configure Policy for an Application Group
You can choose to apply a pre-existing backup policy to a specific Kubernetes application group.
To configure a policy for a chosen application group:
- Log into your Druva CloudRanger console and navigate to Resources > Kubernetes.
- Select a Cluster Name.
- Navigate to the Application Groups tab, and select the application group that you wish to configure a policy for. Click Configure Policy.
- Select the appropriate Recipe to apply to the Application Group backup.
Note: Only those Recipes defined for the selected Application Group will be available here for selection.
- Select the appropriate Backup Policy to configure for the chosen application Group.
A summary of the Schedule and Retention criteria specified at policy level is displayed below for your reference. - Click Confirm.