|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.|
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:
In MSSQL cluster, after restoring system database, the File Share Resources may not come backup online.
The following procedure describes the steps involved in recovering data associated with the following entities:
This procedure can be performed when the following are available:
See License Administration for more details.
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.
|When you start the Command Line Interface to capture data, use the name of the standby CommServe in the -commcell argument.|
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.)
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.