How to enable CDC for your database?
How to enable CDC for your database?
- By default CDC is enabled on your database. But for that, make sure you have the the sysadmin role. If not, you need to enable CDC manually by running the scripts on your database. For more information, see Enable CDC on database and tables.
Do we support Azure Arc?
Do we support Azure Arc?
- No.
I am an existing tenant for Azure VM. How do I onboard subscriptions for Azure SQL?
I am an existing tenant for Azure VM. How do I onboard subscriptions for Azure SQL?
You can onboard Azure SQL subscriptions by updating your tenant registration permissions on Management Console. For more information, see Update Azure Tenant Registration.
Can I delete an Azure SQL subscription from the Enterprise Workloads Management Console?
Can I delete an Azure SQL subscription from the Enterprise Workloads Management Console?
No, you cannot delete an Azure SQL subscription directly from the Enterprise Workloads Management Console. To delete a subscription, contact Support.
What is Druva Quantum Bridge?
What is Druva Quantum Bridge?
For each backup or restore job request, Druva creates a virtual machine called Druva Quantum Bridge within the customer's Azure environment. This bridge facilitates communication between the SQL resource being protected and Druva Blob Storage. The naming convention for the Druva Quantum Bridge VM is:
DruvaQuantumBridge-<customerid>-<jobid>_<attempt_no>.
For example DruvaQuantumBridge-4354-1868_0
When should I use the Isolated Copy Protection backup method?
When should I use the Isolated Copy Protection backup method?
- Use Isolated Copy: For databases with Basic or Standard (S0, S1, and S2) service tiers, or if your database contains unsupported table types (like Graph or Memory-Optimized).
- Use CDC Backups: When you require more frequent recovery points and granular data capture for higher-tier databases (Standard S3 and above).
Does Isolated Copy protection work with Private Link?
Does Isolated Copy protection work with Private Link?
Yes. Isolated Copy is fully compatible with Private Link environments. All data movement occurs over the Azure private backbone, ensuring traffic never traverses the public internet and remains compliant with strict network isolation policies.
Will Isolated Copy Protection slow down my production database?
Will Isolated Copy Protection slow down my production database?
No. Because the backup is performed on a temporary, isolated copy, the primary backup processing is offloaded from your live production instance.
However, consider the following minor impacts:
Transaction Logs: There is a negligible, temporary load during the initial transaction log capture.
Elastic Pools: If your database is in an Elastic Pool, the temporary copy will consume pool resources (DTUs/vCores) for the duration of the backup. Ensure your pool has sufficient headroom to accommodate the copy.
Are there hidden Azure costs associated with the Isolated Copy Backup method?
Are there hidden Azure costs associated with the Isolated Copy Backup method?
While Druva is egress-free, the Isolated Copy method utilizes temporary resources within your Azure subscription. You will see standard Azure consumption charges for:
Temporary Database Copy: Billed at your database's current tier rate for the duration of the backup.
Quantum Bridge VM: Billed as a standard ephemeral compute instance while the backup job is active.
Druva automatically deletes these resources as soon as the backup job finishes to minimize costs. These resources are tagged for easy identification in your Azure Cost Management reports.
How does Druva handle the temporary resources created during backup?
How does Druva handle the temporary resources created during backup?
Druva uses a fully ephemeral architecture. It automatically orchestrates a temporary database copy and a Quantum Bridge VM for the duration of the backup. Once the data transfer is complete, Druva immediately deletes both resources to prevent "orphan" costs in your Azure environment.
Do I have to pay for data egress when using Azure SQL data protection?
Do I have to pay for data egress when using Azure SQL data protection?
No. All data transferred from your Azure environment to the Druva Cloud is 100% egress-free. You are only responsible for the nominal Azure infrastructure costs during the backup window. This is regardless of the backup method you are using.
Why can't I change the backup method on my policy?
Why can't I change the backup method on my policy?
The Isolated Copy method is designed exclusively for Azure SQL Database. If your policy is applied to Managed Instances or SQL Server on Azure VMs, the option to switch will be disabled. To use Isolated Copy for SQL databases:
Disassociate the Managed Instances or SQL Server on Azure VMs from the policy
(Recommended) Create a new policy with Isolated Copy backup method for your SQL databases
Which Azure SQL tiers are supported by each backup method?
Which Azure SQL tiers are supported by each backup method?
Isolated Copy:
All tiers including
Basic
Standard (S0, S1, S2, and higher)
General Purpose
Business Critical
Full + Incremental:
High-Performance Tiers including
Standard (S3 and higher)
General Purpose
Business Critical
Note:
The Full + Incremental method requires CDC and Microsoft does not support CDC on Basic, Standard S0, S1, and S2 tiers. For these databases, use the Isolated Copy method.
Why should I use Isolated Copy instead of Full + Incremental?
Why should I use Isolated Copy instead of Full + Incremental?
The Isolated Copy method is the best fit for specific environmental requirements and service tiers.
Use Isolated Copy when:
Your databases are on Basic, or Standard (S0–S2) tiers (where CDC is not available)
You require a backup solution that makes no configuration changes (such as enabling CDC) to your production environment.
You do not require Point-in-Time Restore capability
You prefer a simpler backup approach that utilizes native Azure copy functionality for maximum isolation from the primary database performance
What happens if I switch from Full + Incremental to Isolated Copy?
What happens if I switch from Full + Incremental to Isolated Copy?
Transitioning an existing backup set to the Isolated Copy method results in the following:
All the future backups will use the Isolated Copy method to create full, standalone recovery points
Point-in-Time Restore will only be available for recovery points captured prior to the switch. New backups will support full restores only.
Existing recovery points created with Full + Incremental remain available for Point-in-Time Restore
CDC remains enabled on your databases (it is not automatically disabled). To reduce unnecessary overhead, manually disable CDC on the databases if it is no longer required for other processes.
You will begin incurring Azure charges for the ephemeral database instances created during the copy process.
For more information, see Impact of Changing Backup Methods or Backup Policy.
What happens if I switch from Isolated Copy to Full + Incremental?
What happens if I switch from Isolated Copy to Full + Incremental?
Switching to the Full + Incremental method upgrades your protection capabilities but introduces specific tier requirements. Review these impacts before proceeding:
The system will automatically enable Change Data Capture (CDC) on all compatible databases to track changes.
Databases on Basic or Standard (S0–S2) tiers do not support CDC and will be automatically excluded from the backup set and will no longer be protected by this policy
Point-in-Time Restore will be available only after the first successful Incremental backup has been completed following the switch.
All future backups will transition from full standalone copies to high-performance incremental streams
For more information, see Impact of Changing Backup Methods or Backup Policy.
What happens if I only provide the DRUVA_QB_SUBNET tag?
What happens if I only provide the DRUVA_QB_SUBNET tag?
The Quantum Bridge resources (VM, NIC, and Disk) will be created in the target subnet, but they will be placed inside the default Druva Resource Group created during initial subscription onboarding. For example, dcp-drv-rg-<xxx-xx-xxx-xxxxxx>.
What happens if a SQL resource has no tags applied at all?
What happens if a SQL resource has no tags applied at all?
If a specific Azure SQL Logical Server does not have any tags applied, the system will automatically look for and utilize the tags applied at the broader Azure Subscription level.
If neither level has tags, it defaults to the Resource Group and Subnet associated with the Virtual Network identified during the initial subscription onboarding.
Do I need to set up VNet Peering to protect my SQL resources with Quantum Bridge?
Do I need to set up VNet Peering to protect my SQL resources with Quantum Bridge?
No, Druva does not require VNet peering. Druva expects the selected subnet to have access to the database instance; however, if your networking topology requires peering to achieve this connectivity, please configure it according to your organization's requirements.
How long do these resources stay in my account?
How long do these resources stay in my account?
They are ephemeral. They are created at the start of a task (like a scheduled backup or a manual pre-check) and are destroyed immediately after the task finishes or fails.
Are there extra costs that I will incur on my cloud bill when using Quantum Bridge to protect Azure SQL?
Are there extra costs that I will incur on my cloud bill when using Quantum Bridge to protect Azure SQL?
You are responsible for Azure compute and storage costs incurred while the resources are active. Resources runtime is minimized, and resource sizes are cost-optimized, so ongoing costs are typically negligible.
Why haven't my resource group changes taken effect?
Why haven't my resource group changes taken effect?
Azure metadata is cached for efficiency. If you've recently updated your tags, perform a manual Sync in the Druva console to ensure your latest configurations are active.