Skip to main content
Druva Documentation

Introduction to Druva Cloud Platform Console

Druva Cloud Platform Console is the starting point from where you administer data backed up from the configured data sources. It is the first page you see when you log in, and it provides:

  • An overview of all the services in an account
  • Information about the data protected by Druva
  • Information about the data sources that are registered with Druva

To navigate from the applicable Management Console to the Druva Cloud Platform Console at any time during the session, click the Druva icon druva_logo.png.
You see the following page when you access the Druva Cloud Platform Console:

DCP New dash.png

The sections of the page are described below. 

Administration

menu-prod.png

On the top-right corner of the page, you can access the administration section. If you are a Druva Cloud administrator, you can:

  • Add, edit, or delete inSync, Phoenix, or other Druva Cloud administrators
  • Set up a password policy
  • Set up SSO for administrators
  • Set up geofencing (block login requests from unauthorized networks)

For more information, see About Druva administrators.

Data Protection Summary

dps_1.png

Following table describes the information in the Data Protection Summary section:

Field Description
Data Sources Shows the number of sources in your account that Druva is backing up. Sources can be endpoints such as laptops, or remote servers such as virtual machines. 

Total Data

Shows the total amount of data that Druva has backed up across all the data sources, utilizing the Druva services.

The Total Data shown in this field is categorized product-wise as follows:

  • inSync: Total data backed up across all the devices.
  • Phoenix: Total Source + Changed data across all the data sources.

To view the total data backed up product-wise:

  • See Total data field in the Usage Trends area on the inSync dashboard.
  • See Source + Changes field in the License and Storage area on the Phoenix dashboard.
Data by Source Provides a comparative estimate of storage that the data sources consume.
Note: The storage consumed by file servers is equal to the total storage consumed by registered Windows servers, Linux servers, and NAS shares.

Service Utilization

service-utilization.png

Following table describes the information in the Service Utilization section:

Field Description

Successful Backups

Shows the total number of successful backups, utilizing the Druva services.

The total number of successful backups is counted as the sum of:

  • inSync: Total number of successful backups across all the devices, CloudApps, and Sharepoint sites.
  • Phoenix: Total number of successful backups for all the workloads across the organizations.

Only the last successful backups are counted. 

To view the successful backups product-wise:

  • See the Backup and Restore Status area on the inSync dashboard.
  • See the Organizations area on the Phoenix dashboard.

Total Restores

Shows the total number of all successful restore jobs to date, utilizing the Druva services. 

The total number of restores is counted as the sum of:

  • inSync: Total number of restores across devices, CloudApps, and Sharepoint sites.
  • Phoenix: Total number of restores done till date.

To view the successful restores product-wise:

  • See the Backup and Restore Status area on the inSync dashboard.
  • See the Summary area on the Phoenix dashboard.
Legal Holds Shows the total number Legal Holds applied to the snapshots in inSync.
Compliance Policies Shows the total number of Compliance Policies created within inSync account. 
DR Instances Shows the total number of virtual machines replicated in your AWS account.

Storage Growth

storage_growth_dcp_2.png

The storage growth section shows how the storage consumption for your account has changed over the last 90 days. When you hover over a particular place in the chart, you can see the storage consumed on a day. 

For a new account, the storage growth is zero percent. After the first backup job is complete, the chart shows the growth in comparison to zero bytes consumed on the day of the account creation. The chart is updated over a period of 90 days based on the data Druva backs up from different data sources according to different schedules.
The storage growth chart on the Druva Cloud Platform Console displays the total de-duped data backed up in inSync over the last 90 days and Source + Changed data backed up in Phoenix. 

Command palette

cmd-palette.png 

Use the command palette to search for services and documentation. For example, you want to modify the backup policy of a virtual machine. If you type Virtual Machine in the command palette, it shows the option to select the virtual machine service and documentation around virtual machines. You can either read through the documentation or access the virtual machine console to modify settings of a virtual machine registered for backup. 

Based on the license attached to the account, few services are unavailable. Phoenix only administrators cannot search for inSync options and inSync only administrators cannot search for Phoenix options. 

Services

The services section lists all the Druva services enabled for your account.

 

  • If you have licensed both inSync as well as Phoenix, the Druva Cloud Platform Console displays only the services applicable to the product which you selected at the time of login. And the services associated with the other product remain inactive.
  • If you attempt to access the services of other than the logged-in product, a prompt is displayed, which requests your permission to switch from one product to the other product.

Services.png

Druva services are categorized as:

inSync

Clicking inSync launches the inSync Management Console. The inSync services available on the Druva Cloud Platform Console are described below:

  • Devices: The total number of devices activated and enabled for backup and the total number of devices that has inSync installed. For more information on devices that Druva can backup, see Hardware and software prerequisites. After a device is backed up, you can restore its data if the device is lost or stolen. For more information on inSync client, see inSync Client for Druva Cloud and Get started: Backup and Restore.  
  • Cloud Apps: Number of Cloud Apps registered with Druva. Druva can backup data created and managed on Cloud Apps such as G Suite. For more information, see Cloud Apps.
  • Compliance: Number of compliance policies created on Druva. inSync Compliance provides visibility of compliance breaches associated with end-user data in your organization. Use inSync Compliance to proactively track, monitor, and get notified of data compliance risks in your organization. For more information, see Governance, DLP, and Compliance
  • E-Discovery: Number of legal holds in your organization. With legal hold, you can preserve user backup data and avoid data deletion. When you keep a user on legal hold, the backup data for that user is excluded from compaction. inSync does not delete the data that the user backs up from any user device. Administrators can analyze the user data by using eDiscovery tools. For more information, see Legal Hold
  • Enterprise Search: A tool to let you search across backed up data. Using the Enterprise Search capability, inSync administrators can quickly find end-user files and emails that are backed up by inSync. inSync uses the metadata attributes of files and emails to deliver fast and accurate search results. For more information, see Enterprise search for backed up data

Phoenix

Clicking Phoenix launches the Phoenix Management Console. The Phoenix services available on the Druva Cloud Platform Console are described below:

  • Physical Servers: The number of physical servers registered with Druva for backup and recovery. Supported physical servers are:

    The number of physical servers on the Druva Cloud Platform Console is equal to the number of physical servers on the Phoenix Management Console. 

  • Virtual Machines: Number of virtual machines registered with Druva for backup and recovery. Supported hypervisors are:
  • Disaster Recovery: Number of VMware virtual machines set up for disaster recovery. Use Phoenix disaster recovery to create copies of your on-premise VMware virtual machines on your Amazon Web Services (AWS) Virtual Private Cloud (VPC). In-case some of your VMware virtual machines experience downtime, you can spin up your AWS EC2 instances within minutes and reroute the traffic to the EC2 instances. For more information, see Disaster Recovery-as-a-Service.

Note: It is possible that few services are not available based on the license. If you click on a service that is not enabled, you are taken to a web page that either provides a video or a walkthrough of the service. If you are interested in buying the service, contact Druva Support

CloudRanger

Clicking CloudRanger will redirect the user to the CloudRanger Management Console. To learn more about CloudRanger services refer https://docs.cloudranger.com/

Cloud Status

cloud_status_outline.png

This section shows the region where your snapshots are stored and its health. In the above example, two locations in your account are operational. The possible states are:

State Denoted with Description
Operational green.png All Druva services are up and running
Planned Maintenance blue.png Few or all regions are undergoing scheduled maintenance. Druva services may not be available for some time. 
Partial Service Disruption orange.png Regions denoted with the orange dot are unavailable. Druva services linked to this region are not available for use until the regions are operational. 
Service Disruption red.png All regions are unavailable and none of the Druva services are available for use until the regions are operational. When you hover on the region you can see how much storage a service consumes in the region. 

The cloud status section shows service disruption for a region if it is unavailable for either inSync or Phoenix. It is possible that the region unavailable for one of the products while it is available for the other service. To see if a region is available for Phoenix or inSync, hover over the region and see more details about it.

For example, it is possible that a region is unavailable for Phoenix while it is available for inSync, and the cloud status section shows service disruption. However, if the Phoenix license is not attached to the account, the cloud status shows operational for that region since it is available for inSync.

Additional Services

In addition to the services above, you also see the following services:

  • Platform update: Provides information on what’s new and what’s changed with Druva Cloud platform. It also provides information about inSync and Phoenix Cloud updates. 
  • Support links:  Provides support links for more help. Use support links to contact Druva support, go through the forum posts, or read articles in the knowledge base to resolve issues.
  • Videos: Provides videos for better understanding of Druva services.