Skip to main content
Druva Documentation

SQL errors

This topic lists the SQL errors that you may encounter while working with Phoenix. 

SQL1

Error Message: Streams were not uploaded properly in the previous backup cycle. 

Error Description: This error can occur if the data that was getting uploaded at the time of backup got corrupted due to network issues. 

Error Solution: Use a different restore point. 

SQL2

Error Message:  No database found for restore

Error Description: This error occurs if a database was not selected for restore.

Error Solution: Select a database and then attempt a restore. 

SQL3

Error Message: Metadata mismatched.

Error Description: This error can occur if the metadata of the database selected for backup does not match with the database metadata when it was backed up earlier. 

Error Solution: Run a full backup. 

SQL4

Error Message: Specified instance not found on present application server.:[Attempting to restore to instance <logical path of instance> not found in server]

Error Description: This error can occur:

  • During restore to the original location, if the specified instance is not present on the target machine.

Error Solution:  To resolve the error:

  • Restore the database file to an alternate location. These files can be used to restore databases by attaching it to other SQL instance.

SQL5

Error Message:  sqlcmd utility failed to get query result.:[Error in fetching the SERVERPROPERTY('ProductVersion') for sql server instance: <instance name>.]

                                    OR

                                     sqlcmd utility failed to get query result.:[Error in fetching the SERVERPROPERTY('ProductLevel') for sql server instance: <instance name>..]

Error Description:  This error can occur because of one of the following reasons:

  • sql cmd is not configured.
  • Some error with the sqlcmd.

Error Solution:   To resolve this error:

  • On the command prompt, type "sqlcmd" to check if sql cmd is configured.
  • Retry the operation.

Note: This error is applicable for SQL agent versions 4.6.5 and earlier. 

SQL6

Error Message:  Phoenix SQL agent found no instance/database on the server to backup if the SQL service is not running or the backup policy is set to exclude all the databases.

Error Description:  This error can occur because of one of the following reasons:

  • Log chain is broken for selected databases.
  • All databases in simple recovery mode for log backup.
  • All databases excluded from UI.

Error Solution:   To resolve this error:

  • Ensure at least one instance is online and in working state.
  • Check backup policy and the excluded folder entries.
  • Trigger a full/differential backup.
  • Disable third-party backup tool.
  • At least one database should have FULL recovery mode.
  • Update excluded databases list.

SQL7

Error Message:  PYODBC Library error

Error Description:   This error can occur because of one of the following reasons:

  • Connection with SQL server lost.
  • Meta information for database not available.
  • Not enough permission to access SQL server.

Error Solution:   To resolve this error:

  • Check if SQL server instance is up and running.
  • Permissions for local system account enabled as per documentation.

SQL8

Error Message:  VDILIB application error

Error Description: This error can occur because of one of the following reasons:

  • Local network connection disabled
  • Unable to create virtual connection with SQL server
  • Not enough permissions to access SQL server
  • The point-in-time or transaction mark restore of the database fails when log chain for database breaks due to changed/replaced data files.

Error Solution:  To resolve this issue:

  • Wait for next log backup
  • Permissions for local system account enabled as per documentation.

SQL9

Error Message:  SQL Agent internal error occurred

Error Solution:   Contact Druva Support.

SQL10

Error Message:  Insufficient transaction logs to restore marked transaction

Error Description:  This error can occur because of:

  • Broken transaction log chain.

SQL11

Error Message:  Invalid time-stamp for point in time restore

Error Description:  This error can occur because of:

  • Provided timestamp for database is not valid

Error Solution:   To resolve this issue:

  • Try some other point in time restore

SQL12

Error Message:  Database is not compatible on a for target SQL server. Please check version compatibility level. 

Error Description:   This error can occur because of:

  • SQL Server restore instance is incompatible.

Error Solution:  To resolve this issue:

  • Try to restore your database on a compatible SQL server instance.

                                                      See ALTER DATABASE Compatibility level

Note: This issue is not applicable on SQL server agent 4.6.5 and earlier. 

SQL14

Error Message: SQL Cluster name not found

Error Description: This error occurs if the MS-SQL cluster name is not found.

Error Solution: To resolve this issue, verify the MS- SQL cluster name. 

SQL15

Error Message: Incorrect parameters for SQL server

Error Description: This error occurs when you provide incorrect parameters for the MS-SQL resource.

Error Solution: To resolve this issue, provide valid parameters for the MS-SQL resource.

SQL16

Error Message: SQL Server backup node not healthy.

Error Description: This error occurs when the availability group node is not connected or not in the healthy state.

Error Solution: To resolve this issue, check the status of the cluster and availability group and identify whether there are nodes available based on the backup preference.

SQL17

Error Message: Auto discovery cron job failed.

Error Description: This error occurs when Phoenix does not discover MS-SQL resources, such as instances and AGs.

Error Solution: To resolve this issue, check the Phoenix client log file for errors. Contact Druva Support.

SQL18

Error Message: Different client versions for ag nodes.

Error Description: This error occurs when the different Phoenix client versions are installed on the availability group nodes.

Error Solution: To resolve this issue, ensure that you install the same version of the Phoenix client on all the availability group nodes.

SQL19

Error Message: Failed to delete availability group.

Error Description: This error occurs when the attempt to delete the availability group fails.

Error Solution: Contact Druva Support.

SQL20

Error Message: Failed to trigger backup request due to unavailability of SQL node.

Error Description: This error occurs when the MS-SQL node you intend to back up is unavailable.

Error Solution: To resolve this issue, check the status of the cluster and availability group and identify whether there are nodes available based on the backup preference.

SQL21

Error Message: Failed to find the schedule for triggering backup job.

Error Description: This error can occur if no backup schedule is found for a CLI-triggered backup job.

Error Solution: To resolve this issue, provide a backup schedule to trigger a backup job from the command line.  

SQL22

Error Message: Failed to find the sql resource for triggering the backup job.

Error Description: This error can occur if you provide an invalid name for an instance or availability group for a CLI-triggered backup job.

Error Solution: To resolve this issue, provide a valid MS-SQL resource name.

 

SQL23

Error Message: Failed to find the backup set/policy for triggering backup job.

Error Description: This error can occur for a CLI-triggered backup job, because of the following reasons:

  • A backup set is not configured
  • A backup set is disabled
  • A backup type is not configured in the backup set.

Error Solution: To resolve this issue, ensure that the backup set is configured and enabled. Also, check the desired backup type is configured for backup in the backup set.

SQL24

Error Message: Backup job can't be triggered because 2 or more backup jobs are running. 

Error Description: This error can occur, if two or more CLI-triggered backup jobs are already running.

Error Solution:  To resolve this issue, wait until there are less than two CLI-triggered backup jobs running.

SQL25

Error Message: Triggered backup job for log backup is not created. 

Error Description: This error can occur if no full backup exists, or another full or differential backup is ongoing for the CLI-triggered backup job.

Error Solution:  To resolve this issue, ensure that you perform a full backup and then retry when no full or differential backup is ongoing.

SQL32

Error Message: No new backup job can be created until the first full backup is completed.   

Error Description: This error can occur if backup jobs are triggered from the command line before the first, full backup completes.

Error Solution:  To resolve this issue, ensure that you wait until the first, full backup completes.

SQL33

Error Message: Database not found during upload.

Error Description: This error can occur if the database on an instance is deleted during backup.

Error Solution: To resolve this issue, ensure that the database on the instance is not deleted during the backup operation.