Backup | Restore |
The following section provides information on troubleshooting backups.
Database name contains [ and ] brackets | The use of embedded brackets '[' and ']' in database name may result in backup failures. |
All data paths for the subclient are offline or busy |
This error may be displayed if the Override Datapaths option is
selected in the Data Paths dialog box in the Subclient Properties
for a Log Storage Policy. This results in the Transaction Log backup
operation waits for resources.
To work around this issue, deselect the Override Datapaths option. |
Time Out Failures | The default time allocated for backup and restore operations of SQL databases is 0 (infinite). If a backup or restore operation fails due to a timeout being reached, you can configure the nSqlQueryTimeout registry key to increase the amount of allocated time for backup or restore operations. |
SQL Server jobs that cause backups to terminate |
There are a few jobs that SQL Server restricts during a backup. If one of
these jobs are initiated while a backup is already in progress (or if a backup
is initiated while one of these jobs is in progress) the backup job will
terminate. These jobs are:
|
Backup chain is broken |
When a full or differential backup is performed outside of the system,
for example, from SQL Enterprise Manager, the subsequent log backups performed
using SQL Server iDataAgent
is set Do not convert log backups to full if log backup was performed
using other software in the Subclient - Backup Rules
tab. Make sure to enable the Disable Log Consistency Check in the Subclient - SQL Settings tab to ensure that the backup job completes successfully. |
Backup jobs from Microsoft SQL Server iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:
If the job goes into pending state, the job will restart from the point where it failed and if an attempt to back up the failed database has already been made, another attempt will not be performed.
An event will be created for the inaccessible database during backup. If the inaccessible database is not needed, it can be permanently deleted from the subclient content.
Virtual nodes have to be configured manually after installing the SQL Server iDataAgent in a Veritas Cluster Environment from the CommCell Console. Follow the steps given below to configure the Virtual node: