Druva uses a deduplication technique that makes use of a variable block sizing technique based on file type to determine globally duplicated data across all your servers. The Hybrid Workloads agent only transfers unique blocks of data to the cloud. This ensures massive bandwidth savings of up to 90% in many cases.

Druva backs up your data in the cloud hosted by Amazon. Druva relies on the robustness and the security standards of Amazon Web Services to ensure that your backup data stays safe and secure.

Druva is designed to work efficiently even for organizations with intermittent connectivity. If Hybrid Workloads agents cannot reach Druva Cloud, backups or restores stop temporarily. When connectivity resumes, backups or restores start again. A single backup can, therefore, span across multiple backup windows.

A recovery point is a point-in-time image of your backup data. To know the type of recovery points that Druva supports, see Common terms.

Druva retains the data from your server that is not operational. You can restore the data to another server.

Yes, you can. Druva retains data from the servers that you deprecate. To set up new servers in their place, restore the data from the deprecated servers to the new servers.

No, you cannot. However, you can create backup sets to back up the content from your secondary servers and your tertiary servers. Druva will back up data from your primary, secondary, and tertiary servers according to the schedule defined in the backup policy.

Yes, you can specify the bandwidth limitation for backup.

No, you cannot specify the bandwidth limitation for restore.

After the expiration of your contract, Druva does not back up your servers. However, your data is retained on the cloud. You can choose to extend your contract, and then perform a restore of the data.

No, you cannot export Druva data. However, you can choose to restore data to the server to which it belongs, or a new server.

By default, Druva performs two retries with a 10-minute interval between the two attempts.

Organizations in Druva are independent entities by design. Druva does not have a functionality that allows inter-Organizational restore.

The first backup of your servers is a full backup. Thereafter, Druva performs an incremental backup of all File servers.

Getting your File servers ready for backup is simple. For more information about how to configure File servers for backup, see Configure Druva to back up File servers.

Before configuring your File servers, we recommend that you read File server configuration checklist. The checklist should help you perform a configuration that is best-suited for your environment.

Druva provides support for several file types, out-of-the-box. To see the full list of files that Druva backs up, see Default file types for backup.

By default, Druva excludes some file types from backup. To see the full list of files that Druva excludes, see Default folder exclusions.

To know how to back up your File servers, see Back up servers. To know how to restore your File servers, see Restore a File server.

To understand the workflow at the time of backup, see File server backup workflow.
To know how Druva restores your File server data, see File server restore workflow.

Druva continues to back up the File server as the 'Deviceid' of the server remains the same.

📝 Note
​ The other changed AD domain should have '*.druva.com' allowed in gateway/firewall for the outgoing traffic.

After you upgrade the client,

The first backup of your servers is a full backup. Thereafter, Druva performs an incremental backup. Additionally, Druva also supports differential backups of SQL servers. To know more, see Common terms.

To know how you can configure SQL servers for backup, see Introduction to Druva for SQL servers.

Before configuring your SQL servers, we recommend that you read SQL server prerequisites and limitations. The checklist should help you perform a configuration that is best-suited for your environment.

Druva provides support for backup of MDF, NDF, and LDF files.

To know how to back up your SQL servers, see Back up servers. To know how to restore SQL servers, see SQL server restore.

To understand the workflow at the time of backup, see full backup, differential backup, and log backup.
To know how Druva restores your file server data, see SQL server restore.

For MS-SQL server, you can create backup set either for "All instances" or "individual instances". If you have created backup set for "All instances", then Druva does not allow you to create backup set for individual instances. Similarly, if you have created backup set for individual instances, then Druva does not allow you to create backup set for All instances. However, if you have created backup set for All instances and the backup set is disabled, Druva allows you to create backup set for individual instances.

The details of the existing MS-SQL backup sets can be found on the Protect > Windows/Linux Servers > All Servers > servers_name page > SQL Backup Sets tab. To view the available instances and AGs along with their configured backup sets, upgrade the Hybrid Workloads agent to the version 4.7.1 or later.

You cannot create MS-SQL backup sets for Hybrid Workloads agents older than version 4.7.1. However, backups for the old backup sets continue to run as configured.

No. Druva cannot discover MS-SQL instances and AGs running on the server installed with an agent older than version 4.7.1.

Druva creates a new backup set for each instance present on the physical server. All the newly created backup sets have the same backup policy and same content rule as that of the earlier backup sets for All instances.

The maximum number of backup sets that you can configure on the MS-SQL server depends on the number of the instances existing on that server. You can create one backup set per instance.
For MS-SQL server, you can create backup set either for "All instances" or "individual instances". If you have created a backup set for "All instances", then Druva does not allow you to create a backup set for individual instances. Similarly, if you have created a backup set for individual instances, then Druva does not allow you to create a backup set for All instances. However, if you have created a backup set for All instances and the backup set is disabled, Druva allows you to create a backup set for individual instances.

Check whether you have SQL standalone or SQL FCI installation done. In case you have SQL FCI, upgrade to build 4.7.1 or later and follow setup instructions as described in Configure Druva for the backup of databases in SQL Failover Cluster Instance (FCI).