To ensure reliable and predictable data protection, Druva’s built-in prechecks validate your Azure SQL resources against core prerequisites before backup or restore operations. These automated checks proactively detect incorrect credentials and network misconfigurations—such as missing VNet rules or non-delegated subnets. By identifying these issues early, the system provides clear error codes and specific solutions, significantly reducing the likelihood of subsequent job failures.
Authentication Prechecks
Pre-check | Description | Recommended Action |
SQL Server Credential Check | Verifies whether the provided authentication credentials are valid. | For Service Principal, make sure you have mapped the concerned admin (as per your organization in the Management Console) for your Azure SQL resource. For more information, see How to map service principal in Azure. For SQL authentication, validate the authentication credentials provided by your database administrator and reassign the authentication with the correct authentication credentials. For more information, see Assign Authentication. |
VNet Rule Check | This check ensures that the database is configured with a VNet rule permitting inbound network connection from the specific virtual network where the Quantum Bridge VMs are deployed. | No VNet rule that allows Druva to connect to the database is found. Configure a VNet rule for the database. For more information, see Pre-requisites for protecting Azure SQL resources. |
Subnet Check | This check ensures the subnet is configured, is non-delegated, and is not used by the following Azure built-in services:
| Configure a non-delegated subnet in the virtual network associated with the Azure SQL Managed Instance. Also, ensure it is not used by the Azure built-in services. For more information, see Pre-requisites for protecting Azure SQL resources. |