Log Shipping Issue

Hello All,

I am trying to set up Log Shipping, but, in the second screen of Database Maintenence wizard, when I select any database, the log shipping option gets grayed out. I am not able to select both. But in the step by step guide, it mentions to select both. I could have provided a screenshot of what's happening, but I could not locate a place for the same. Please let me know about this at the earliest. I'll be very grateful. Thanks a lot.

Mannu.

What is the recovery model for the databases you are want to include in the log shipping?

What is the edition of SQL you are using?

|||

That is corrrect. It was in Simple mode. Changing it to Full Mode, gave me what I want.

Thanks a lot.

Log shipping fails the second time.

Log shipping fails the second time to restore 5Gb transactional log backup with the following error.

Error 823: [Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID)

detected during read at offset 0x000001f340e000 in file 'e:\program files\microsoft sql server\DBName.mdf'.

There is no hardware problem. The restore failed in a test server on the same step with the same error message.

The DBCC CHECKDB does not give any error message.

What it might be?

My guess is that the transaction log backup is corrupt and is laying down a full-page format log record (which contains a full page image) that has a corrupt page ID. Is the source database clean as far as CHECKDB is concerned?|||

CHECKDB does not give any error. The transactional backup got corrupted after indexes rebuild operation. It does not happen every time. Is there any way to check transactional backup integrity?

|||

yes its possible to check the integrity of a backup file.just refer this command......

Restore verifyonly from disk='Full path of your tran log file'.........it will check whether all the pages in the trn file are readable and also if the backup set is complete........

Log shipping fails the second time.

Log shipping fails the second time to restore 5Gb transactional log backup with the following error.

Error 823: [Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID)

detected during read at offset 0x000001f340e000 in file 'e:\program files\microsoft sql server\DBName.mdf'.

There is no hardware problem. The restore failed in a test server on the same step with the same error message.

The DBCC CHECKDB does not give any error message.

What it might be?

My guess is that the transaction log backup is corrupt and is laying down a full-page format log record (which contains a full page image) that has a corrupt page ID. Is the source database clean as far as CHECKDB is concerned?|||

CHECKDB does not give any error. The transactional backup got corrupted after indexes rebuild operation. It does not happen every time. Is there any way to check transactional backup integrity?

|||

yes its possible to check the integrity of a backup file.just refer this command......

Restore verifyonly from disk='Full path of your tran log file'.........it will check whether all the pages in the trn file are readable and also if the backup set is complete........

Log shipping failing

Hi I have 2 SQL 2005 enterprise servers and I am trying to make a read only
copy of one of our databases on the second server using log shipping. I have
set this up from the database properties page on the primary server and
everything starts working correctly.
The initial database is restored correctly and then the first of the
tranaction logs is also restored correctly but after that all additional
transaction log restores fail.
In the job History the following errors occur.
Error: Could not apply log backup file
'\\servname\logshipping\database_20061107094501.tr n' to secondary database
'databasename'.(Microsoft.SqlServer.Management.Log Shipping)
***<nl/>2006-11-07 10:15:21.05*** Error: Exclusive access could not be
obtained because the database is in use.<nl/>RESTORE LOG is terminating
abnormally.(.Net SqlClient Data Provider) ***,00:00:21,0,0,,,,0
Followed by
Error: The log backup file
'\\servername\logshipping\Databasename_20061107094 501.trn' was verified but
could not be applied to secondary database
'databasename'.(Microsoft.SqlServer.Management.Log Shipping)
***<nl/>2006-11-07 10:15:21.33Deleting old log backup files. Primary
Database: 'databasename'<nl/>2006-11-07 10:15:21.33The restore operation
completed with errors. Secondary ID:
'b115c13b-1e8d-47fc-8625-6ca4ed84bc52'<nl/>2006-11-07 10:15:21.35-- END
OF TRANSACTION LOG RESTORE --<nl/><nl/>Exit Status: 1
(Error),00:00:21,0,0,,,,0
I have tested this with the log shipping as the only actions running on the
server and the same results occur. The first restore works and the rest fail.
Any ideas as to what I can do to resolve this.
James - it looks like you have a connection to the standby database but this
is prohibited. You need to select the option to disconnect users from the
secondary database while the restore operation is underway.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .