April 27, 2006 at 1:44 pm
Good day,
I have a database that was backed up, and now, I want to restore that database to a test server. These servers are identical, from hardware to OS to patches. Windows 2003 sp1 and SQL2005. I use the backup tool on box a, copy the backup to box b, verify file systems exist, (no *.mdf .ndf or .ldf files exist yet), and then run the restore. The restore gets to 90% and then just as I would think it would finish, it fails. I cannot seem to find much in the errors, but here is some of what I can find (I have 2 of the following):
Date4/27/2006 1:44:45 PM
LogWindows NT (Application)
SourceSQLISPackage
Category(0)
Event1074802950
User
Computer
Message
Event Name: OnError
Message: An exception occurred while executing a Transact-SQL statement or batch.
StackTrace: at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(String sqlCommand)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(StringCollection sqlCommands)
at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.TransferDatabasesUsingSMOTransfer()
InnerException-->Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 3:2038176; actual 0:1192045984). It occurred during a read of page (3:2038176) in database ID 7 at offset 0x000003e3340000 in file 'H:\Database\DataMart\DataMart_data2.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(String sqlCommand)
Operator:
Source Name:
Source ID: {F9BDBEF9-E7B8-4E84-8B33-xxxxxxx07B6}
Execution ID: {2755C5F0-7942-40B0-90E4-CxxxxCBBF15F}
Start Time: 4/27/2006 1:44:45 PM
End Time: 4/27/2006 1:44:45 PM
Data Code: 0
-- Cory
April 27, 2006 at 1:53 pm
The I/O problem looks like it came during the CREATE DATABASE portion of the restore. I would suggest creating your database first. You should be able to size it according to how large the database is on your other server. Then attempt to force the restore over the newly-created database.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply