Restore Troubleshooting - SQL Server iDataAgent
|No Data to Restore||The following error message is displayed during a browse operation if CommServe and SQL Server time are not synchronized.
There is no data to restore. Verify that the correct dates have been entered.
Verify and ensure that the CommServe and SQL Server time are synchronized as close as possible. The SQL Server client can be ahead of the CommServe but not behind.
|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.|
|Time Out Failures for large databases|| If the database you are attempting to restore is particularly large, it may become necessary to increase this time-out value.
Re-run the restore after increasing the VDI Timeout value as described in Set the VDI Timeout Value for Large SQL Database Restores, see Increasing the VDI Timeout for step-by-step instructions.
|Restore Failure of large Database||For large databases with over 2TB of Data, restore may fail due to not enough timeout in minutes. Set the timeout value of the query thread (for backup or restore) to a higher value, use nSQLQueryWaitMaxRetryCount additional setting to change the timeout value.|
Completed with one or more errors
Restore jobs from Microsoft SQL Server iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:
- When multiple databases are restored, if restore of one of the databases fail.
In a disaster recovery scenario, use the following procedure to recover data associated with the following entities:
- Deleted storage policy
- Deleted client, agent, backup set or instance
Before You Begin
This procedure can be performed when the following are available:
- You have a Disaster Recovery Backup that contains information on the entity that you are trying to restore. For example, if you wish to recover a storage policy (and the data associated with the storage policy) that was accidentally deleted, you must have a copy of the disaster recovery backup that was performed before deleting the storage policy.
- Media containing the data you wish to recover is available and not overwritten.
- If a CommCell Migration license was available in the CommServe when the disaster recovery backup was performed, no additional licenses are required. If not, obtain the following licenses:
- IP Address Change license
- CommCell Migration license
See License Administration for more details.
- A standby computer, which is used temporarily to build a CommServe.
Recovering Deleted Data
- Locate the latest Disaster Recovery Backup that contains the information on the entity (storage policy, client, agent, backup set or instance) you are trying to restore.
- Check the Phase 1 destination for the DR Set or use Restore by Jobs for CommServe DR Data to restore the data.
- If the job was pruned and you know the media containing the Disaster Recovery Backup, you can move the media in the Overwrite Protect Media Pool. See Accessing Aged Data for more information. You can then restore the appropriate DR Set associated with the job as described in Restore by Jobs for CommServe DR Data.
- If the job is pruned and you do not know the media containing the Disaster Recovery Backup, you can do one of the following:
- If you regularly run and have copies of the Data on Media and Aging Forecast report, you can check them to see if the appropriate media is available.
- If you do not have an appropriate report, and know the media that contains the DR Backup, catalog the media using Media Explorer. Once the cataloging process is completed, details of the data available in the media are displayed.
- On a standby computer, install the CommServe software. For more information on installing the CommServe, see Install the CommServe.
- Restore the CommServe database using the CommServe Disaster Recovery Tool from the Disaster Recovery Backup described in Step 1. (See CommServe Disaster Recovery Tool for step-by-step instructions.)
- Verify and ensure that the NetApp Client Event Manager NetApp Communications Service (EvMgrS) is running.
- If you did not have a CommCell Migration license available in the CommServe when the disaster recovery backup was performed, apply the IP Address Change license and the CommCell Migration license on the standby CommServe. See Activate Licenses for step-by-step instructions.
- Export the data associated with the affected clients from the standby CommServe as described in Export Data from the Source CommCell.
When you start the Command Line Interface to capture data, use the name of the standby CommServe in the -commcell argument.
- Import the exported data to the main CommServe as described in Import Data on the Destination CommCell.
This brings back the entity in the CommServe database and the entity is visible in the CommCell Browser. (Press F5 to refresh the CommCell Browser if the entity is not displayed after a successful merge.)
- You can now browse and restore the data from the appropriate entity.
As a precaution, mark media (tape media) associated with the source CommCell as READ ONLY before performing a data recovery operation in the destination CommCell.
File share resources not coming back online
In MSSQL cluster, after restoring system database, the File Share Resources may not come backup online.
- Manually bring online the File Shared Resource using the Failover Cluster Manager.
Unable to restore SQL Server data from an earlier time
When attempting to browse and restore a SQL Server database from an earlier time, only the latest backup cycle is shown. Also, attempting to set an earlier time using the "Point in time" option results in a failed backup.
This situation occurs because the latest cycle is selected by default when right-clicking on a database and selecting restore.
In order to restore SQL data from an earlier time:
In the CommCell® Browser, right-click the database.
Point to All Tasks.
Click Browse Backup Data.
On the browse options dialog box, enter the desired time for the restore.
SQL Server MASTER DB restore fails (Error Code 30:299)
A SQL MASTER DB restore will run, and then report failed. On the SQL server, the SQL services will be stopped. When you manually restart SQL, you will find the MASTER DB was actually successfully restored.The job and the "SQLiDA.log" file will report this as the error:
Error Code: 30:299 Description: Query Result [An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) Failed to connect to server [ ].].
In the SQL ERRORLOG files and the application event logs, you will see events similar to this when attempting to start SQL:
Server Server local connection provider failed to listen on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. Error: 0x5
Server Error: 17182, Severity: 16, State: 1.
Server TDSSNIClient initialization failed with error 0x5, status code 0x40.
Server Error: 17182, Severity: 16, State: 1.
Server TDSSNIClient initialization failed with error 0x5, status code 0x1.
Server Error: 17826, Severity: 18, State: 3.
Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Server Error: 17120, Severity: 16, State: 1.
Server SQL Server could not spawn FRunCM thread.
Check the SQL Server error log and the Windows event logs for information about possible related problems.
This is caused by a permissions issue. When the restore process attempts to restart using an impersonated account, SQL services fail to start.
Before doing the MASTER DB restore:
Log into the SQL server you are restoring to.
Start the two CommVault services as the backup account.
Run the MASTER DB restore successfully.
Restart the CommVault services as LOCALSYSTEM.
SQL database backup fails (Error Codes 30:302, 30:323, 30:325)
A SQL database backup fails with one of the following errors:
Error Code 30:302 AutoDiscover Failed, please check if SQL services are running and connectivity between CommServe and client.
Error Code 30:323 may be presented: Error encountered when transferring data for db [...] to the MediaAgent. Please check the SQL VDI.LOG AND connectivity between client and MediaAgent.
Error Code 30:325 may be presented: Error encountered during backup. Error: [....]
The SQL DB iDataAgent Server SQLiDA.log file contains the following error:
CCvSQLVDIBase::StartDBBackup() - !!!!QUERY: [BACKUP DATABASE [SharePoint_Config] FILE = 'SharePoint_Config' TO VIRTUAL_DEVICE = '...' WITH MAXTRANSFERSIZE=65536, BLOCKSIZE=65536, BUFFERCOUNT=1, NOINIT, name='...']. CCvSQLVDIBase::RunQuery() - Error: The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS. BACKUP DATABASE is terminating abnormally. An exception occurred while executing a Transact-SQL statement or batch.. The CommServe "JobManager.log" file has this error in it. Scheduler Set pending cause [Error encountered during backup. Error: [The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS. BACKUP DATABASE is terminating abnormally. An exception occurred while executing a Transact-SQL statement or batch.]]::Client [...] Application [SQLiDA] Message Id  RCID  ReservationId . Level  flags  id  overwrite  append  CustId.
There is a Microsoft® SQL limitation when a backup is run on a SQL DB set up in SIMPLE Recovery Model.
To do a file/file group backup of a database in SIMPLE Recovery Model, there are some configuration changes:
- Set up a 'database' subclient with just this database in it.
- When running backups of the database, go to the Advanced tab and select the partial backup option.
- Set up a 'filegroup' subclient with all files EXCEPT for the primary file (it cannot be backed up in this fashion when SIMPLE Recovery Model is enabled.)
Refer to the following Microsoft KB articles for additional information: