Restore using data protector
-
Hi all,
Data Protector agent is waiting for SQL Server 7.0/2000 to perform recovery of the restored database.
[Warning] From: OB2BAR_Main@abc01.XX.XXXX.net "(DEFAULT)" Time: 10/28/2005 11:23:37 AM
Error has occurred while executing a SQL statement.
Error message: '<Microsoft SQL-DMO (ODBC SQLState: 42000)?15 [152:5] 13f1 [Microsoft][ODBC SQL Server Driver][SQL Server]Device activation error. The physical file name 'd:\mssql\mssql\data\abc01.mdf' may be incorrect. [Microsoft][ODBC SQL Server Driver][SQL Server]File 'abc01_Data' cannot be restored to 'd:\mssql\mssql\data\abc01.mdf'. Use WITH MOVE to identify a valid location for the file. [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot use file 'l:\mssql\logs\abc01_log.ldf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. [Microsoft][ODBC SQL Server Driver][SQL Server]File 'abc01_Log' cannot be restored to 'l:\mssql\logs\abc01_log.ldf'. Use WITH MOVE to identify a valid location for the file. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally.'
[Normal] From: OB2BAR_Main@abc01.XX.XXXX.net "(DEFAULT)" Time: 10/28/2005 11:23:56 AM
Database statistics:
--------------------------------------------------------------
1. abc01 1 MB 80 min ( 1 Mb/h)
--------------------------------------------------------------
[Normal] From: RSM@swidp01.XXX.hp.com "" Time: 28.10.2005 12:24:03
OB2BAR application on "XXXabc01dvsql1.XXX.hp.com" disconnected.
What I understand is
The data protector restore operation was trying to restore with the options configured in the source which eventually fail since the destination server don’t have the directory structure similar to the source.
2. Then the client gave the correct location to move the files but still we get this error
Error message: '<Microsoft SQL-DMO (ODBC SQLState: 01000)?15 [152:5] fc3 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()). [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation. [Microsoft][ODBC SQL Server Driver][SQL Server]Processed 9364 pages for database 'abc01', file 'abc01_Log' on file 1.'
I think the error occurred due to time-out which happened in the restoration due to the size of the backup. I have checked the server, the database is in "LOADING" state. The restore operation from the data protector has initiated the two files in the folder d:\mssql2000\Data\MSSQL\Data\. But didnt completely restored them. They have taken the option "Leave Database operational. No additional transaction logs can be restored"
which is the default.
+ "Force restore over existing Database".
3. In the meantime I have tried to restore the db several times using different backup versions, but always got the SQL error during recovery:
[Warning] From: OB2BAR_Main@abc01.XX.XXXX.net "(DEFAULT)" Time: 11/7/2005 1:26:23 PM
Error has occurred while executing a SQL statement.
Error message: '<Microsoft SQL-DMO (ODBC SQLState: 42000)?15 [152:5] 1435 [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot associate files with different databases.'
The SQL errorlog file on the SQL server shows following at the same time:
2005-11-07 13:26:22.79 spid55 Starting up database 'abc01'.
2005-11-07 13:26:22.80 spid55 Bypassing recovery for database 'abc01' because it is marked IN LOAD.
If I understand this correctly, the recovery fails BECAUSE esmg DB is in "LOAD" state.
This might be the case because of the very first restore attempt using incorrect (non-existent)
restore locations.
Helen
--------------------------------
Are you a born again. He is Jehova Jirah unto me -
Hi all,
the restore of the SQL DB abc01(Version 15.11.) to the test server finished successfully.
So it is quite clear that the installation of the MS MDAC hotfix:
Q827452_MDAC28_x86.exe patch
has resolved the issue
Helen
--------------------------------
Are you a born again. He is Jehova Jirah unto me
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply