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........