Troubleshooting Restore - SQL Server iDataAgent

Backup Restore  

Browse Failures

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 registry key 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:

File Share Resources not coming back online

In MSSQL cluster, after restoring system database, the File Share Resources may not come backup online.

Recovering Data Associated with Deleted Clients and Storage Policies

The following procedure describes the steps involved in recovering data associated with the following entities:

Before you Begin

This procedure can be performed when the following are available:

Recovering Deleted Data

  1. Locate the latest Disaster Recovery Backup which contains the information on the entity (Storage Policy, Client, Agent, Backup Set or Instance) that you are trying to restore.
  2. On a standby computer, install the CommServe software. For more information on installing the CommServe, see CommServe Deployment.
  3. Restore the CommServe database using the CommServe Disaster Recovery Tool from the Disaster Recovery Backup described in Step 1. (See Restore a Disaster Recovery Backup for step-by-step instructions.)
  4. Verify and ensure that the CommVault Client Event Manager CommVault Communications Service (EvMgrS) is running.
  5. 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.
  6. 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.
  7. Import the exported data to the main CommServe as described in Import Data on the Destination CommCell.

    This will bring back the entity in the CommServe database and the entity will now be visible in the CommCell Browser. (Press F5 to refresh the CommCell Browser if the entity is not displayed after a successful merge.)

  8. If you have additional data that was backed up after the disaster recovery backup and before the deletion of the entity, use the procedure described in Import Metadata from a Tape or Optical Media to obtain the necessary information.
  9. You can now browse and restore the data from the appropriate entity.

    As a precaution, mark media (tape and optical media) associated with the source CommCell as READ ONLY before performing a data recovery operation in the destination CommCell.