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. Once you log into Druva CloudRanger, you will be navigated to your AWS Accounts page.

AWS Accounts Listing Page

Once you log into the Druva CloudRanger console, you will be directed to the AWS Accounts listing page within your Default Organization.

1WK_Acc page2.png

You may add or delete one or more accounts from your AWS Accounts page:

  • Add Account: Click Add New Account on the top right to configure the AWS Access Role to your AWS environment, thus allowing Druva CloudRanger to access and manage your AWS workloads. For more information, see Create an AWS Access Role.
Note: You may choose to add single or multiple accounts from your AWS Accounts page by provisioning a stack or stackset within your AWS environment. For more information, see Configure Multiple AWS Accounts.
  • Delete Account: Select the Account(s) to be deleted and then click icon.PNG. Select Delete Account and confirm the deletion.

The main Accounts listing page allows you to update, manage, and configure your AWS accounts within your chosen Organization.

Field

Description

Name

Click the Account Name to navigate to your Account-level Administration dashboard from where you can easily configure your AWS Resources, manage resource backups and restores, DR plans, and schedules.

State

When a new Account is setup and synchronized with your AWS environment, the State toggle is set to Active by default. You can choose to set an Account to Active state or Disable it.
To modify the state of the Account, click the State toggle icon against the account Name. Alternatively, select an Account and then click icon.PNG. Select Activate Account or Deactivate Account and confirm the update.

Active St1.PNG
Disabled St2.PNG
Note: Disabling an account suspends all associated activities including backup schedule, retention, disaster recovery, and resources schedules.

Last Sync Time

The time of previous synchronization with your AWS environment.

Note: To initiate manual Sync with AWS, select an Account and then click Sync.

Last Sync Status

The status of the previous synchronization with your AWS environment.

  • Success: Indicates a successful synchronization.
  • Failed: Indicates that the synchronization failed. Click the link to view the associated message to ascertain the reason for the Sync failure.
  • In Progress: Indicates that the Sync is still underway. Depending on the outcome, the Status updates to Success or Failed.

Last Access Status

The access status with your AWS environment.

  • Latest: Indicates that the AWS access role is up to date.
  • Update: Indicates that the AWS access role needs to be updated. Click the link to update the CloudFormation template on your AWS console.
Note: To verify the access status with your AWS environment, select an Account and then click Verify AWS account access.

Settings

Click gear.PNGto view and manage Account Settings, such as account access, notifications, network settings, and user administration.


Druva CloudRanger offers an intuitive user interface with the navigation organized into Organizational and Account-level configuration elements.

Organization-level Administration

Use the top navigation bar to manage and administer the following globally across all AWS accounts within an organization.

1WK3.png

  • Policies: Backup policies are managed globally across all AWS accounts, but users can choose to apply a predefined policy to a specific AWS account
  • Reports: End-to-end Reporting functionality that allows you to customize and subscribe to reports on Backup and Restore status, Schedules, and Disaster Recovery Plans, across AWS accounts.
  • Monitor: Jobs are maintained at the organization level and offer an integrated view of all UI-triggered scheduled and maintenance activities. You may also view Audit Trail, as part of compliance and governance, where needed.
Note: The left navigation menu for Account-level administration can only be accessed once you navigate to a specific Druva CloudRanger account. The top menu bar for Organization administration will, however, remain static and accessible at all times.

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.

Click the icon.PNG icon on the top navigation panel to select the appropriate organization. Once selected, the Accounts drop-down 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.

Organization Management

Click the Settings gear icon on the top navigation bar to configure and manage the Organization Settings and Billing information for the user currently logged in.

1WK7.png

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.

Account-level Administration

Use the left navigation menu to manage and administer the following at the AWS Account-level. You can easily configure and manage your AWS resources, backups, and restores, as well as manage DR plan and schedules at an account level:

1WK2.png

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

  • Overview: The dashboard provides an at-a-glance view of each account in one integrated console:
  • Resources: Configure AWS Resources as well as create and manage resource backups and restores for EC2, EBS, RDS, DynamoDB, and Redshift resources.
  • Disaster Recovery: Create and manage DR Plans and Environments.
  • Resource Schedules: Manage on/off schedules for AWS resources and Auto-Scaling Groups.
  • File Search: Search and recover files, in case of accidental deletions or as part of compliance and governance. to locate specific files within your backups using unique meta-data attributes.
  • Settings: Manage account access, notifications, network settings, and user administration.

Dashboard

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.

    1 WK_Widget.png
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.

    1_WK_Widget2.png
     
  • 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.

    1_Wk Widget 3.png

Account Management

The Account settings allow you to access and manage the AWS accounts defined on Druva CloudRanger. Click Settings on the left navigation menu 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.

Resources

Druva CloudRanger simplifies and reduces costs associated with the complexity of data lifecycle management for AWS cloud workloads. You can now manage all aspects of the backup and restore lifecycle across multiple regions and AWS accounts, all via one unified console.

Once you add and sync your AWS account(s) with Druva CloudRanger, all servers and resources linked to your AWS account including Amazon EC2, EBS, RDS, DynamoDB, and Redshift instances will be available on your CloudRanger console.

To view your resources, navigate to Resources and then select the resource type from the drop-down:

EC2_Res Main.png

The Resource 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.

To view detailed information on each resource, click the resource Name.

1_EC2_2.png

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

You can choose to automate your backup process using backup policies or generate a manual backup of a specific resource on Druva CloudRanger.

Note: You can configure a backup policy or initiate a backup from the main Resource page. To apply a predefined backup policy to a specific resource, select the resource Name and click Configure Policy.

Resource Backups

To access your resource backups, navigate to Resources, select the appropriate AWS resource type, and then click Backups.

EC2_Bk Main.png

The Backups page displays the backup Region, Size, Type, State, Created, and the Location.

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  icon to filter backups by Type, Region, or Tags.

Restores

The restore process varies based on the resource type that has been backed-up. In general, the restore process depends on the backup type applied to the specific resource, that is, AMIs or snapshots.For example, you may choose to restore an EC2 instance from AMIs or snapshots. You can initiate restore as an instance, restore at the volume level, or request a file-level restore. On the other hand, RDS snapshots are restored as an RDS instance.

Druva CloudRanger offers multiple approaches to restoring your AWS backups.

  • 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.

To access your backup restores, navigate to Resources, select the appropriate AWS resource type, and then click Restores.

EC2 Rest Main2.png
 

Disaster Recovery

DR 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 DR Plans, navigate to Disaster Recovery > DR Plans.

DR1.png

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

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

  • The appropriate Service Level Objective (SLO) and Service Time Objective (STO) parameters for the 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, as well as the Target Instance Type and the Test Plan Instance Type.

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.

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

For more information, see Automated Disaster Recovery Workflow.

Environments

Environments allow you to group specific components of your cloud infrastructure and enable you to effortlessly visualize and manage your AWS resources. You can also clone environments as part of a Disaster Recovery plan.

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 Disaster Recovery > Environments.

ENV.png

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

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

  • 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 to view the associated resources and Source Region. You can choose to add or remove resources assigned to that Environment.
  • To clone a predefined environment, select the environment Name and click Clone.
     

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 Resources Schedules on the left navigation menu.

WK_Res Sch.png

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.

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.

The File Level Search feature is optional and will need to be enabled from your Account Settings page. File Indexing allows you to define the accuracy of search in backups – a higher frequency of indexing enhances search accuracy, while also impacting costs.

Note: File Level Search feature when enabled will create an S3 Bucket per user account to store the file system metadata of the target backups. The CloudFormation scripts may need to be updated to allow access to the S3 bucket.  

To enable File Indexing, click Settings on the left navigation menu and navigate to File Search Settings.

WK_FLS.png

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.

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.

To access Backup Policies, on the top navigation bar click Policies.

BP1.png

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.

For more information, see Create Backup Policies.
 

Monitoring

Jobs

Druva CloudRanger provides an integrated view of all scheduled and maintenance activities on the Jobs page. To access Jobs, navigate to Monitor > Jobs.

Job1.png

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

  • Backup
  • Retention
  • Restore
  • Disaster Recovery
  • Scheduling

The Job Details page includes detailed information about the selected job, the progress, and associated logs. For more information, see Jobs.
 

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 Jobs, navigate to Monitor > Audit Trail.

1_1audit.png

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, ADR plan, etc.)
  • Action performed
  • User information (email ID)
  • Status of action performed
  • Time of action

For more information, see Audit Trail.

Reports

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
  • Licensing
  • DR Plan

To generate and view Reports, on the top navigation bar click Reports.

Rep1.png

You can choose to Preview a report directly on 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?