Skip to main content
Configure and Manage Backup Scripts
Updated over a week ago

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.

You can now add pre- or post-backup scripts to generate application-consistent snapshots for common applications such as SQL Server. This will grant CloudRanger access to SSM documents on your AWS environment and permissions to execute scripts on associated resources.

πŸ“ Note
​For enterprises that run Windows-based applications, Druva CloudRanger supports VSS-consistent snapshots on Windows instances. For more information, see Create VSS Consistent Snapshots for Windows Servers.

Before you begin:

Granting Permissions to AWS SSM Documents

To begin using backup scripts, you will first need to update your existing AWS Access Role to grant Druva CloudRanger the requisite permissions to access and execute your AWS SSM documents. For more information on updating your IAM role and the AWS CloudFormation template for account configuration, see Update Existing AWS Access Roles in Druva CloudRanger.

Adding New Scripts

To add new scripts:

  1. On the top navigation bar, select Policies > Scripts.

  2. Click Add Scripts.


  3. To add scripts to your Druva CloudRanger organization, select the script(s) and then click Add Only.
    Alternatively, click Add and Configure to add the selected script and map it to one or more EC2 resources.



Configure As

Select Pre-script or Post-script depending on whether the selected script is to be run pre- or post-backup.

Select Version

Select the appropriate version of the script to be run.
You may choose to run the Default or Latest versions, depending on the resources to be configured.

In Accounts

Specify the filter criteria to identify resources to be mapped to the selected script.
Select the Druva CloudRanger Account associated with the AWS resources.

In Regions

The AWS Region displayed here is associated with the Region where the script is configured in AWS.

πŸ“ Note
​The script can be associated only to resources within the same AWS Region in which the script originally resides. For more information, please refer to the AWS documentation.

Match By

Select the match criteria, based on Resource IDs or Tags. Based upon the Match selected, you will need to specify the criteria values appropriate to that criteria.
​For example: Tags: Origin ID ; Values: ID.

4. Click Configure to map the identified resources to the selected script.

Managing Scripts

To view detailed information on specific scripts, click a script Name from the main Scripts listing page.

  • Summary: The script summary tab provides information on the Document Type and Owner, Version, and the Region in which the script is configured in AWS.

  • Resource Mapping: Navigate to the Resource Mapping tab to configure specific resources with the selected backup script.

The newly added scripts can also be configured to additional resources from the main Scripts listing page.

  • To map specific resources to a backup script, select a script and click Configure.

πŸ“ Note
​When associating Amazon-owned scripts with a resource in Druva CloudRanger, any modifications to the parameter values will not work because script execution in CloudRanger works only with pre-defined parameters in the SSM document. Amazon-owned scripts cannot be modified from within Druva CloudRanger, and in such scenarios we recommend creating a copy of the script and adding or editing the parameters in the script content.

  • To delete script(s) from Druva CloudRanger, select the script(s) and click Remove.

Did this answer your question?