Skip to main content
Druva Documentation

A Walkthrough of the Druva CloudRanger Console

The Druva CloudRanger Console is the starting point from where you administer data backed up from the configured data sources.

Org selector3.png

Organization Selector

Druva CloudRanger brings to you the option to access multiple organizations and AWS accounts from within your console. You can select your Organization from the top navigation bar on your Druva CloudRanger console. Once you log into Druva CloudRanger, you will be navigated to your default AWS account.

Click the icon.PNG icon on the top navigation panel to select the appropriate organization.

Org selector.png

Once selected, the Account drop-down on the left navigation displays all AWS accounts linked to that Organization to which the user is granted access. In other words, the Account drop-down will be filtered based on the Organization selected and will display those Accounts within the Organization that is configured for the logged-in user.

Note: Organizations with no specific name defined on Druva CloudRanger will display as a Default Organization. CloudRanger administrators can choose to update the Organization Name from the Organization Settings page. It is recommended that you assign unique Organization names to avoid multiple Default Organizations.

Org selector2.png

Navigation Panel

Use the left navigation panel to navigate to the various components of the application. Druva CloudRanger offers an intuitive user interface with the navigation organized into Account-specific and Global configuration elements. 

Account-level Administration

This allows administrators to easily configure the AWS infrastructure, backups, restores, as well as disaster recovery at the AWS account level.

Left Nav Ac.png

You can configure and manage the following at an account-specific level:

  • Account settings
  • AWS Infrastructure: Resources and Environments
  • Backups and Restores
  • File Search
  • Disaster Recovery Plans and Resource Schedules


The Druva CloudRanger Dashboard provides an at-a-glance view of the following components into one integrated console:

Resources: An overview of the AWS Resources that are Protected or Non-Protected, as well as Resources that are currently running. In other words, this provides information on the number of servers that are available and running, and that have an active Backup Policy or Schedule associated with them.
Simply hover over the Resources pie charts to know the exact number of resources that are Protected/Not Protected or Scheduled/Not scheduled.


Note: The Scheduled Resources widget does not currently include the number of scheduled Auto Scaling Groups (ASGs). Consequently, the Weekly Saving data on the dashboard applies only to resources that are on a standard schedule.
  • Schedules: The number of Schedules currently defined which can be applied to specific Resources.
  • Disaster Recovery Plans: The number of DR Plans currently defined which can be applied to specific Resources.
  • Backups: The total number of Backups created and a link to view All Backups on Druva CloudRanger.

  • Weekly Overview: This provides a weekly summary of server uptime based on the schedules defined for all resources. Users can also view a weekly snapshot of the cost-savings realized upon administering Druva CloudRanger across resources.


Global Administration

Backup policies are managed globally across all AWS accounts, but users can choose to apply a predefined backup policy to a specific AWS account. In addition, Jobs and Audit Trail are maintained at the global level.

Left Nav Glb.png

Global configuration allows you to manage the following:

  • Backup Policies
  • Jobs
  • Follow the Audit Trail for Druva CloudRanger
  • View and download Reports

Account-level Administration

Account Management

The Account settings allow you to access and manage the AWS accounts defined on Druva CloudRanger.

Click the Settings icon to view and manage the following account settings:

  • Account Overview: Account name and time zone settings
  • AWS Access: Configure and test your AWS access settings
  • Notifications: Manage notifications to be triggered and the intended recipients or webhooks
  • Team: Add or manage team members with the permitted levels of access
  • Network settings: Manage the subnets that CloudRanger will apply on temporary instances for each region
  • File Search Settings: Enable File Indexing to define the accuracy of search in backups – a higher frequency of indexing enhances search accuracy, while also impacting costs

Click the user profile icon on the top right to configure and manage the Organization Settings and the User Settings for the user currently logged in:

User profile blur.png


Use the Infrastructure section to access all resources linked to your AWS account. You can also access the AWS Environments, which you can choose to clone as part of a Disaster Recovery plan.


Resources cover all servers and resources linked to your AWS account including Amazon EC2, EBS, RDS, and Redshift.

To access Resources, navigate to Infrastructure > Resources.

Res Main1.png

This page displays all AWS Resources defined in Druva CloudRanger, their current State, Backup Region, Backup Protection Status, as well as their Last Backup and Schedule Status. You may also drill down resources by EC2, EBS, RDS, or Redshift.

Use the Search by resource name or ID text box to quickly locate a specific resource. You can also use the Icon1.PNG icon to filter resources by Backup Protection Status, Schedule Status, Region, or Tags.

Resources New Search.png

Click on a resource Name to view the Backup volumes, resource Tags, and Jobs associated with that resource.

Res Search1.png

To apply a predefined Backup Policy to a specific resource, select the resource Name and click Configure Policy.



Environments allow you to group specific components of your cloud infrastructure and enable you to effortlessly visualize and manage your AWS resources.

Druva CloudRanger Environments enable you to:

  • Identify VPC components and group them into environments
  • Manage Automatic Disaster Recovery of resources
  • Manage specific VPCs by Subnets or Security Groups

To access your Environments, navigate to Infrastructure > Environments.


This page displays all Environments defined in Druva CloudRanger, Source Region, Created period, as well as their current Status (for example, Ready, Clone Failed, etc.).

Use the Search Environments text box to quickly locate a specific environment.


Click Create Environment to define a new environment within a specific Source Region. This allows you to add specific AWS Resources to that environment.

Create Env1.png

You can choose to add multiple VPCs available within the Region and then select the appropriate Subnet, Security groups, and DB Subnet Groups from the drop-down list.

Click on a predefined environment Name to view the associated resources and Source Region.

  • You can choose to add or remove resources assigned to that Environment.
  • Click Save Environment to return to the main page.

To clone a predefined environment, select the environment Name and click Clone:



Druva CloudRanger allows you to view and manage all your resource Backups as well as Restore a specific snapshot, when necessary.

The Backups page displays all previous backups across all servers and resources linked to your AWS account including Amazon EC2, RDS, and Redshift.

To access your Druva CloudRanger backups, navigate to Backups > Backups.


This page displays all previous backups, backup Region, Size, Type, State of availability, Created time, and the Location. You may also drill down backups by EC2, RDS, or Redshift.

Use the Search by backup name or ID or resource name or ID text box to quickly locate a specific backup. You can also use the clipboard_e5de55f0263c5ce151ad81f55386c63d7.png icon to filter backups by Type, Region, or Tags.


Druva CloudRanger offers multiple approaches to restoring a snapshot. You can initiate restore as an instance, restore at the volume level, or request a file-level restore.

  • You can choose to Restore any of the snapshots listed on the Backups page. To initiate a Restore, select the backup Name and click Restore.
  • Alternatively, click the backup Name to view the snapshot details, and then initiate Restore.


Druva CloudRanger offers multiple approaches to restoring a snapshot. You can initiate restore as an instance, restore at the volume level, or request a file-level restore.

To access your backup restores, navigate to Backups > Restores.


The Restores page displays all previous backup restores, including the Origin and Restored To locations, Status, and Type.


Disaster Recovery Plans

Druva CloudRanger offers enhanced capabilities and custom ADR workflows to streamline disaster recovery planning. Disaster recovery is imperative to recovering business-critical AWS cloud data ensuring seamless business continuity minus additional infrastructure expenses.

Druva CloudRanger allows you to define customized DR plans based on the business SLAs and environments, as well as easily clone VPCs and their associated subnets and security groups. With CloudRanger disaster recovery, you can validate RTO and RPO objectives upon actual execution of the recovery process.

To view and manage Disaster Recovery Plans, navigate to Policies > Disaster Recovery Plans.


Use the Search Plans text box to quickly locate a specific DR plan.


Click Create Disaster Recovery Plan to define a new DR plan.


You can define the following on the Create Disaster Recovery Plan page:

  • The appropriate Service Level Objective (SLO), that is the RPO and RTO for that DR plan
  • The Source and Target Accounts and Environments
  • The Component Mapping of the Source and Target VPCs.
  • The AWS Resources on the Source and Target Environment

Click Advanced to define the Target Instance Type and the Test Plan Instance Type. You can also select the Run Books option, which allows you to shut down source servers upon failover, in the event of disaster recovery.


Click on a predefined DR plan Name to view the associated SLOs, the Source and Target Environment details, and Component Mapping of the Source and Target VPCs.

  • You can choose to modify the SLOs, the environment, the resources, or the mapping for that DR plan.
  • Click Save Plan to return to the main page.

To initiate the DR Plan Testing, select a DR Plan Name, and then click Execute Test. Click Confirm.


Resource Schedules

The Resource Scheduling functionality allows you to optimize your AWS costs by creating an On/Off schedule for your Amazon EC2 and RDS resources.

To view and manage Resources Schedules, navigate to Policies > Resources Schedules.


Use the Search Schedules text box to quickly locate a specific resource schedule.


Resources can be scheduled using the ‘On/Off’ schedule or a ‘Reboot’ action specified. Each resource schedule can be applied across specific resources by Instance ID or Instance Tags.

Click Create Schedule to define a new schedule for a specific Server or Auto Scaling Group.


To execute a predefined schedule:

  • Select the schedule Name and click Start Now.
  • On the Confirm dialog box, click Confirm and Execute.

To view or edit a predefined resource schedule:

  • Click the schedule Name to navigate to the Edit Schedule page.
  • You can modify all associated parameters, including the resource Type, the ‘On/Off’ Schedule, and the Instance ID or Instance Tags.

File Search

Use the Druva CloudRanger File Search feature to locate specific files within your backups using unique meta-data attributes. You may also track changes and download individual files directly from the snapshots.

You will first need to configure the file search settings for each AWS account before you can get started with file search. File Indexing allows you to define the accuracy of search in backups – a higher frequency of indexing enhances search accuracy, while also impacting costs.

On the main navigation panel, click File Search:


Click Go To Settings to navigate to the Account Settings page, and enable file indexing.


You can also define the Backup Index Settings to index backup files for search, if relevant.

Once file indexing is enabled, you can search files by Name, File Size, Date Modified, as well as files in specific Resources or Backups.


Global Administration

Backup Policies

Druva CloudRanger offers a simplified, global approach to backup policies, with options to define one or more policies that can be applied across multiple AWS accounts and instances. The Backup Policies defined can be executed across multiple AWS accounts, and set to Active or disabled depending on business requirements.

To access Backup Policies, navigate to Global > Backup Policies.


Use the Search Policies text box to quickly locate a specific backup policy.


Use Druva CloudRanger Backup Policies to define the backup parameters such as:

  • The backup schedule and frequency
  • The backup retention plan
  • The AWS accounts and resources to be backed up, with options to define inclusions or exclusions
  • The number of additional copies to be maintained
  • Backup encryption and applicable scripts and tags
  • Perform extra tasks such as rebooting the EC2 instance prior to the backup

You can choose to create a unified backup policy for your AWS workloads, while still customizing your global policies to include or exclude instances based on specific Instance IDs, Tags, AWS accounts, Regions, VPCs, or Subnets.

Note: The Backup Policies and Retention criteria defined should consider the value of your data, the business requirements, as well as associated legal constraints, before being implemented. Consequently, different types of data may be backed up and retained for different durations across specific regions in keeping with changing business needs.


Druva CloudRanger provides an integrated view of all scheduled and maintenance activities on the Jobs page. The Job Details page includes detailed information about the selected job, the progress, and associated logs.

To access Jobs, navigate to Global > Jobs.


You can access Jobs scheduled or triggered within the following categories:

  • Backup
  • Retention
  • Restore
  • Disaster Recovery
  • Scheduling

Use the Search by Resource ID or Job ID text box to quickly locate a specific Job. You can also use the clipboard_ead55d814c9c40df4837e826a82aff0ed.png icon to filter jobs by Region, Account, Resource Type, Policy, Action, Status, or by Date Range (for example, Jobs triggered in the Last 30 days).


Audit Trail

Audit Trail captures all activities performed by the administrators and users on the Druva CloudRanger Console. This is a valuable feature for data governance and ensures that organizations can effectively meet compliance requirements, where needed.

To access Audit Trail, navigate to Global > Audit Trail.


The Audit Trails capture the following user information for ease of tracking and transparency:

  • Druva CloudRanger Account
  • Type or component modified (for example, backup policy, network settings etc.)
  • Action performed
  • User information
  • Status and Time of action
  • Audit information

Click clipboard_eb1bbb2e066b3e2338c5217d80bb5bb67.png against each record to view the exact modifications performed.


Druva CloudRanger provides an end-to-end reporting functionality that allows you to generate and customize cross-account Reports on Backup Policies, Schedules, and Disaster Recovery Plans across AWS accounts.

The Reports subscription functionality allows you to generate and manage subscriptions to the following reports:

  • Resource Schedule
  • Resource Restore Status
  • Resource Protection Status:
  • Resource Backup Status
  • DR Plan

To generate and view Reports, navigate to Global > Reports:

Rep RN1.png

You can choose to Preview a report directly on Druva CloudRanger or Export it into .pdf or .csv files.

Druva CloudRanger offers a Report subscription functionality that enables administrators to subscribe to specific reports as part of monitoring and compliance. Report subscriptions allow administrators to create and manage email schedules for periodic delivery of specific reports to chosen recipients. 

For more information, please see Reports.

  • Was this article helpful?