This topic lists the errors that you may encounter during backup and restore of Azure SQL resources.

Error Message: Internal Error

Error Description: This is an internal error.

Error Solution: Download job logs and contact Support.

Error Message: No available databases eligible for backup

Error Description: This error might occur due to various reasons such as:

See the logs for exact cause.

Error Solution: Depending on the cause, fix the issue and retrigger backup. For example, if the backup fails cause there’s no data available, make sure data exists in the database and then trigger backup.

Error Message: Failed to poll status

Error Description: Failed to poll status.

Error Solution: Download job logs and contact Support.

Error Message: Failed to execute SQL command

Error Description: Failed to execute SQL command.

Error Solution: Download job logs and contact Support.

Error Message: Failed to start VDI database dump

Error Description: This error occurs due to one of the following reasons:

Error Solution: Download job logs and contact Support.

Error Message: Failed to create credentials

Error Description: This error occurs when the user does not have the sysadmin role for creating SQL Server credentials.

Error Solution: Log in as a user with the sysadmin role and try again.

Error Message: Failed to restore certificates

Error Description: This error occurs due to one of the following reasons:

Error Solution: Download job logs and contact Support.

Error Message: Failed to restore database

Error Description: Failed to restore database.

Error Solution: Download job logs and contact Support.

Error Message: No available databases eligible for restore

Error Description: You may get this error if none of the databases is eligible for restore as a database with the same name already exists.

Error Solution: Delete the database or give a new name while restoring.

Error Message: Database(s) skipped

Error Description: Some databases might be skipped from backup due to reasons such as:

See the logs for exact cause.

Error Solution: Depending on the cause, fix the issue and retrigger backup. For example, if the database was skipped because there’s no data available, make sure data exists in the database and then trigger backup.

Error Message: Login failed

Error Description: You may get this error if server authentication fails.

Error Solution: Check the authentication type and provide correct authentication.

Error Message: Failed to start CDC capture job

Error Description: You may get this error if there are reused database IDs that lead to stale data in the capture job details.

Error Solution: Disable and enable CDC and try again.

Error Message: Failed to get SQL Server timezone and offset

Error Description: Failed to get SQL Server timezone and offset.

Error Solution: Execute the following T-SQL query and fix any errors encountered:

Error Message: SQL Server Precheck failed

Error Description: You get this error if a SQL Server precheck fails.

Error Solution: Check if the SQL server agent is running. If not, start it.For more information, see Check and validate the required Services.

Error Message: Failed to initialize job

Error Description: You get this error if initiating a backup or restore job fails.

Error Solution: Download job logs and contact support.

Error Message: Post-processing of backup job failed.

Error Description: You get this error if the post-processing of a backup job fails.

Error Solution: Download job logs and contact support.

Error Message: Failed to backup database(s).

Error Description: You get this error if the database backup job fails.

Error Solution: Download job logs and contact support.

Error Message: Failed to create one or more database users.

Error Description: You get this error when users are present in the database, but corresponding logins are not available. See logs for details.

Error Solution: For failed users, check if the SQL server login exists. If not, create the user and corresponding login manually.

Error Message: CDC backup not allowed for system databases

Error Description: This error occurs when a Change Data Capture (CDC)-based backup is scheduled and an attempt to back up system databases is initiated.

Error Solution: Disable the CDC backup schedule from the backup policy and try again.

Error Message: Login failed

Error Description: You may get this error if:

Error Solution: Ensure the following:

Error Message: No VNet rule found

Error Description: You get this error if a VNet rule is not configured for the Azure SQL Database

Error Solution: Configure a VNet rule for the Azure SQL Database instance in the Azure management console. Druva performs Azure SQL backup and restore operations using the ephemeral Quantum Bridge compute resources (i.e. VMs). To allow these resources to connect to your database, you must add a Virtual Network rule to your database instance that permits the Quantum Bridge. You can complete this setup using the Azure Portal, CLI, or your preferred scripts. For more information, see Pre-requisites for protecting Azure SQL resources

Error Message: Unable to retrieve subnet information

Error Description: This error occurs if the Azure SQL Managed Instance cannot find a compatible landing zone for the ephemeral Druva Quantum Bridge (i.e. VMs). This usually means the subnet is missing or is already delegated to another service.

Error Solution: Modify your Azure SQL Managed Instance to allow incoming connections from a non-delegated subnet that has at least one free IP address for Druva Quantum Bridge usage. For more information, see Pre-requisites for protecting Azure SQL resources.

Error Message: Service Principal authentication is only available for SQL Server version 2022 and above

Error Description: You get this error when you use Service Principal authentication on SQL Server versions below 2022.

Error Solution: Upgrade to SQL Server 2022 or use SQL Authentication for legacy versions.

Error Message: Port 1433 is unreachable or blocked by your NSG rules

Error Description: This occurs when inbound security rules block traffic to the Azure SQL Managed Instance on TCP port 1433.

Error Solution: Configure the Network Security Group rules on the delegated subnet to allow inbound traffic to port 1433 from the virtual network used by the Druva ephemeral Quantum Bridge virtual machines. For more information, see Configure NSG for Azure SQL Managed Instance.

Error Message: Subnet does not have outbound access to Azure Key Vault

Error Description: This error occurs when Network Security Group rules or routing configurations block secure outbound communication to Azure Key Vault. This path must be established using Virtual Network Service Endpoints, Private Endpoints, or an Azure NAT Gateway (required only when accessing Key Vault via public endpoints).

Error Solution: Update the Network Security Group rules for the Azure SQL Managed Instance subnet (where Druva Quantum Bridge is spawned) to allow outbound traffic. Depending on your network design, ensure this path is established via Virtual Network Service Endpoints, Private Endpoints, or an Azure NAT Gateway (for public routing without service endpoints). Validate that the NSG Route Tables do not divert this traffic to an external firewall that might block the connection.

Error Message: Internal error

Error Description: This error typically occurs during transient platform issues or when the Azure SQL Managed Instance delegated subnet is in the Updating state, preventing API requests.

Error Solution: Wait for any pending subnet or instance operations to complete and retry the request. If the issue persists, contact Support.

Error Message: User does not have the sysadmin role.

Error Description: This error occurs when the SQL Server user account provided for backup operations does not have the sysadmin role.

Error Solution:

Error Message: User does not have db_owner permission for database(s): <db1, db2..>.

Error Description: You get this error if

Error Solution:

USE [DatabaseName];

ALTER ROLE db_owner ADD MEMBER [YourUserName];

```

3. Verify the permissions by running:

```sql

USE [DatabaseName];

SELECT IS_MEMBER('db_owner') AS IsDBOwner;

```

Error Message: No user tables exist in databases: <db1, db2..>

Error Description: You get this error if

Error Solution:

1. Review the list of databases identified as having no user tables.

2. For each database, determine if it is:

- A newly created database that hasn't been populated yet

- A template or placeholder database

- A database that should be excluded from backups

3. To verify the table count in a database, run the following command:

```sql

USE [DatabaseName];

SELECT COUNT(*) AS UserTableCount

FROM sys.tables

WHERE is_ms_shipped = 0;

```

Error Message: SQL Server Agent is not running

Error Description: You get this error if the SQL Server Agent service is not running or is disabled on the SQL Server instance.

Error Solution:

Start the SQL Server Agent using one of the following options:

Error Message: Databases %s contain table types that are not supported for backup

Error Description: You get this error if

Error Solution: Edit the backup set to exclude the database with unsupported tables. The next backup will skip these databases.

Error Message: CDC configuration failed for <db1,db2..>

Error Description: You get this error if

Note:
​Druva enables CDC on a database, but it does not modify the existing CDC configuration. You must manually update the existing CDC configuration if needed.

Error Solution: You may encounter issues like:

To resolve the above-mentioned issues, enable CDC at the database level using the sp_cdc_enable_db command using the following query:

USE YourDatabaseName;

GO

EXEC sys.sp_cdc_enable_db;

Run the following query to enable CDC at table/column level:

EXEC sys.sp_cdc_enable_table @source_schema = N'<Schema-Name>', @source_name = N'<Your-DatabaseName>', @role_name = NULL;

For more information, see Pre-requisites for protecting Azure SQL resources.

Error Message: CDC capture and cleanup job parameters are invalid not within the recommended range for <db1, db2..>

Error Description: This error occurs when the SQL Server Agent jobs that manage Change Data Capture (CDC) operations have misconfigured parameter values for the capture and cleanup jobs.

Error Solution: Reconfigure the capture and cleanup job parameters with the recommended values. For more information, see Pre-requisites for CDC-based backups.

Error Message: Names of database(s) <db1, db2,..> contain a semicolon ‘;’

Error Description: This error occurs when the database name contains a semicolon ‘;’. This is a Microsoft limitation. For more information, see Microsoft's official Go MSSQL driver.

Error Solution: Do not use a semicolon ‘;’ in the database name.

Error Message: One or more databases <db1,db2..> are not in an Online state and cannot be accessed

Error Description: This error occurs when one or more databases are not in an Online state and are inaccessible for backup.

Error Solution:

1. Check the current state of all databases by running the following command:

```sql

SELECT

name,

State_desc

FROM sys.databases

WHERE state_desc <> 'ONLINE';

```

2. If a database is in the offline state, run the following command to make it online:

```sql

-- Bring database online

ALTER DATABASE [DatabaseName] SET ONLINE;

Error Message: A database with the same name exists on the target for <db1,db2..>

Error Description: You get this error if

Error Solution:

Do one of the following:

Error Message: Failed to run precheck

Error Description: This error may occur if the database is offline or inaccessible to the identity performing the backup/restore operation.

Error Solution: Verify that the database is accessible to the identity performing the backup/restore operation, and retry the operation.