Cloud administrators

Organization administrators

Group administrators

Cloud administrators (View-only)

Organization administrators (View-only)

Group administrators (View-only)

Data Protection Officer

Categorize servers, virtual machines, and NAS shares with common traits and organize these resources for better management. For example, servers located in one region can belong to one administrative group. Similarly, servers having the same operating system can belong to one administrative group.

Mandatory: Create an administrative group and attach servers for backup configuration.

Optional: Assign a group administrator to the administrative group for server management.

Used to activate multiple Enterprise Workloads agents and backup proxies.

Generated during server, virtual machine, or NAS Proxy registration.

Performs one-time authentication for agents and proxies.

Establishes persistent connection with the Cloud.

It's recommended to use a single token for servers, virtual machines, NAS shares with common traits.

Removing tokens doesn't affect ongoing backups.

An MS SQL server database mirroring technique that supports replicated environments for availability databases.

Allows one set of primary databases and up to eight sets of secondary databases.

Enables backup of databases from the secondary node.

For more information about the MS SQL availability group, see Overview of Always On Availability Groups.

The email address used to create an Azure subscription serves as the Azure account for that subscription.

The party linked to the email account is responsible for the monthly costs of the subscription's resources.

Provides secure storage of generic secrets, such as passwords and database connection strings.

Encrypts secrets at rest with a hierarchy of encryption keys, with all keys in that hierarchy are protected by modules that are FIPS 140-2 compliant. This service encrypts your secrets when you add them, and decrypts them automatically when you read them.

The deployment and management service for Azure.

Provides a management layer that enables you to create, update, and delete resources in your Azure account. You use management features, like access control, locks, and tags, to secure and organize your resources after deployment.

Entity managed by Azure. Examples include Azure Virtual Machines, virtual networks, and storage accounts.

Logical containers that you use to group related resources in a subscription. Each resource can exist in only one resource group.

Allow for more granular grouping within a subscription.

Commonly used to represent a collection of assets that are required to support a workload, application, or specific function within a subscription.

A JSON file that defines one or more Azure resources

Defines dependencies between the deployed resources. The template can be used to deploy the resources consistently and repeatedly.

A set of Azure datacenters that deploy inside a latency-defined perimeter.

The datacenters connect through a dedicated, regional, low-latency network. Most Azure resources run in a specific Azure region.

Logical container for your resources. Each Azure resource is associated with only one subscription. Creating a subscription is the first step in adopting Azure.

A group of users, or an organization, that share access privileges to an instance of a product, service, or application. In the Azure Active Directory, a tenant is an instance of Azure AD that an organization receives registering a cloud application like Microsoft 365.

Each Azure AD tenant is distinct and separate from other Azure AD tenants. Multitenancy refers to an instance of an application shared by multiple organizations, each with separate access to the instance.

A network that provides connectivity between your Azure resources, which are isolated from other Azure tenants.

Lets you establish connections between different virtual networks, or between a virtual network and an on-premises network. You can control the IP address blocks, DNS settings, security policies, and route tables within a virtual network.

Backup content specifies what data to be backed up on a server.

Two types: Content rule and Custom content.

Rules for automatic backups and data retention.

Create and attach policy to one or more servers, virtual machines, or NAS shares during configuration.

Druva performs backups based on the defined schedule.

Components of a backup policy: policy type, backup schedule, retention period, and platform-specific backup settings.

A virtual machine that you must deploy and register for backing up and restoring virtual machines in your VMware setup.

Contains Hybrid Workloads agent, which performs backup and restore of virtual machines. For more information, see About backup proxy for VMware.

A collection of backup proxy servers.

Automates mapping of virtual machines to backup proxy servers.

Backup requests assigned to proxy servers based on load balancing. For more information, see About backup proxy pool.

Defines automatic backup timing.

Druva follows a backup policy-defined schedule for server data backup.

Components of backup schedule are: start time, backup duration, maximum bandwidth per server, days for backup occurrence.

A data set configured for backups, including backup content and policies.

Customizable backup content, policy, and retention settings.

Defined for server, virtual machines, and NAS shares, and consists of:

Associated with backup set type (e.g., File, MS SQL, VMware).

Multiple backup sets can be attached to a File or MS-SQL server.

In VMware/Nutanix or Hyper-V setup, backup set is a virtual machine with attached policy.

A folder in the ZFS pool of the Phoenix Backup Store that is shared through the NFS.

Data written to this shared folder is backed up to Druva Cloud.

Creating a Backup Mount on Management Console for a registered Phoenix Backup Store creates a shared directory with the specified Backup Mount name on the ZFS pool of Phoenix Backup Store and shared through NFS.

Backup comprises copying and archiving of data from servers, virtual machines, and NAS shares to designated Druva storage.

Install and activate Hybrid Workloads agents for server backup.

Druva supports the following types of backups:

Incremental backups are self-sufficient for complete server restore.

Quick recovery with full backup and last differential backup.

Druva Cloud refers to the entire Druva setup.

It includes Hybrid Workloads agent or backup proxy and the cloud storage for data.

Druva protects workloads in Public Cloud and Gov Cloud.

CloudCache is a dedicated server in the local environment.

It locally stores backup and restore data from Hybrid Workloads agents.

Periodically synchronizes this data to Druva Cloud.

Setting up CloudCache ensures faster backups and restores for your organization.

For more information about CloudCache and its deployment, see CloudCache.

Credits allow pre-purchasing Druva storage, paying only for what you consume.

The Enterprise Workloads dashboard offers graphs to track purchased credits and storage consumption on the Druva Portal.

Credit balance and cumulative credits used update daily at 12:15 AM UTC based on storage consumption.

For more information about credits and various credit consumption scenarios, see Druva Credits.

Druva performs global deduplication to optimize storage by removing duplicate data.

Only unique data blocks from all servers are backed up, enabling single-instance restoration.

Data deduplication helps reduce redundant data, manage backup activity, and achieve cost savings.

Let us consider an organization performs full-file incremental backups of files, where only a few bytes have changed, and occasionally performs full backups due to age-old design challenges in backup systems. A 10 TB file server would create 800 TB of backups just from eight weekly fulls, and probably another 8 TB or so of incremental backups over the same amount of time. A good deduplication system can reduce this 808 TB down to less than 100 TB – without lowering restore speed.

A discrete storage unit on tape, disk, or other media that supports data.

It serves as storage blocks for saving data.

CloudCache license determines the size of CloudCache for your setup.

A data volume permits you to consume a portion of this storage. You can only consume a portion of the storage that is equivalent to the size of the data volumes that you create.

If your setup requires more storage, you can add up to 10 data volumes, and set a size for these data volumes.

Adding multiple data volumes helps scale CloudCache to match server data size requirements.

Disaster Recovery (DR) plan is a set of rules for recovering your data in case of emergency or disaster.

A DR plan defines the following:

FCI stands for Failover Cluster Instance of SQL Server.

It is a single SQL Server instance installed across Windows Server Failover Clustering (WSFC) nodes.

The FCI may span multiple subnets.

On the network, it appears as if SQL Server is running on a single computer.

FCI provides failover from one WSFC node to another in case the current node becomes unavailable.

Hybrid Workloads agent is the client-side component of Druva and is deployed locally on servers for backup and restore operations.

Hybrid Workloads agent communicates with Druva Cloud for data backup and restoration.

To enable backup and restore of server data, you must install and activate Hybrid Workloads agent on all relevant servers.

The Hybrid Workloads agent is installed on Windows or Linux servers.

It handles backup and restore requests from NAS Shares.

To establish connectivity with Druva, you need to install and activate the NAS Proxy.

The link between Druva and a NAS device is established by mapping a NAS Proxy to the device.

Once mapped, the proxy can be attached to a backup set for backup and restore operations.

Multiple proxies can be mapped to a device, and a proxy can be attached to multiple backup sets.

Druva uses organizations (sites) as access-based control to segregate resources with no shared data.

Each organization manages its servers, virtual machines, and databases, and policies independently.

Servers, virtual machines, and databases, administrative groups, and policies are isolated within each organization.

Organizations share storage, cloud administrators, and customer licenses.

Access to resources in one organization is restricted from other organizations.

For information about configuring organizations, see Configure Organizations.

An NFS server with Druva binaries installed on it.

Phoenix Backup Store has a ZFS pool using disks available on the Phoenix Backup Store.

Backup Mounts in the ZFS pool are shared through NFS.

Data written to a Backup Mount on Phoenix Backup Store is converted to a recovery point and backed up to Druva Cloud.

Data is restored from Druva Cloud to a Backup Mount on Phoenix Backup Store.

Configure file server and NAS backup policies with pre-backup and post-backup scripts to perform specific tasks before and after a backup job.

Druva executes pre-backup scripts before backup.

Post-backup scripts run after backup for specific tasks.

For more information about pre-backup and post-backup scripts, see Pre-backup and post-backup scripts for File server and Pre-backup and post-backup scripts for NAS.

Retention period is the duration the data is kept on Druva Cloud.

Druva Cloud purges data you chose to delete after the retention period.

For example, with a 15-day retention, deleted data is purged after 15 days.

You can define the retention period when configuring the server, virtual machine, or database on Druva Cloud.

Recovery point is a point-in-time image of backup data.

It indicates the state of the backup data at a particular point-in-time.

Druva supports three types of recovery points:

At the time of restore, data from the cold tier is retrieved, moved temporarily to the warm tier, and then restored.

Once you click Restore and initiate the restoration process, the data retrieval from cold tier and its restore from the warm tier happen automatically. Warmed up data is deleted from the warm tier after 10 days.

A location in the cloud where Druva stores data backed up from different servers.

Pre-purchase Druva storage using credits depending on your data needs and location preferences, and in-effect pay only for the storage that you consume. The purchased storage is translated into credit allocation. For example, if you have purchased a 10-TB Druva storage for a contract term of one year, 120 credits (TB months) are allocated to your account. You can effectively track the purchased credits and storage consumption using Dashboard. For more information about credit usage, see Druva Credits.
​

📝 Note

​ If you have a Business license, you can purchase Druva storage only in one AWS region.

Druva directly backs up data from servers to warm storage where the data stays. Because the warm storage is fast in performance, restoring of the data in warm storage is "on-demand" in nature, and starts immediately.

Druva backup proxy can access virtual machine data from data stores using three different methods – NBD, HotAdd, NBDSSL. These methods are referred to as VMware Transport modes.

For more information about transport modes, see Transport modes.

Volume Shadow Copy Service (VSS) is a Windows service for capturing and creating recovery points that are called as shadow copies. VSS, which operates at the block level of the file system, provides a backup infrastructure for Microsoft operating systems.

Druva instructs Microsoft VSS to create shadow copies of data on Windows servers. When shadow copies are created on the same volume they can result in heavy input and output load. Therefore, if VSS is enabled, administrators can configure the operating system to create shadow copies on a separate volume.

Consult your Windows operating system documentation for further information about making this configuration change.

A specific type of server or virtual machine whose data you want to back up, ensuring its protection and recoverability in case of data loss or system failure.

Druva extends data protection and cyber resiliency solutions catering to an array of workloads including: