Solved

Logshipping --SQLserver2005-- not a valid Microsoft Tape Format backup set

Posted on 2011-03-01
1
640 Views
Last Modified: 2012-05-11
Hello,
 I have log shipping running for a while  but today I getting the error below. How do I fix this issue.

Message
2011-03-01 09:15:08.18      Starting transaction log restore. Secondary ID: '112ad7af-0593-47b3-9e88-72443f75cbc2'
2011-03-01 09:15:08.19      Retrieving restore settings. Secondary ID: '112ad7af-0593-47b3-9e88-72443f75cbc2'
2011-03-01 09:15:08.19      Retrieved common restore settings. Primary Server: 'GRATWA01', Primary Database: 'osv_projects_hipath8k_v4_0_db', Backup Destination Directory: 'F:\logshipping\hipath8k_v4_0', File Retention Period: 43200 minute(s)
2011-03-01 09:15:08.19      Retrieved database restore settings. Secondary Database: 'osv_projects_hipath8k_v4_0_db', Restore Delay: 0, Restore All: True, Restore Mode: Standby, Disconnect Users: True, Last Restored File: F:\logshipping\hipath8k_v4_0\osv_projects_hipath8k_v4_0_db_20110228190010.trn, Block Size: Not Specified, Buffer Count: Not Specified, Max Transfer Size: Not Specified

---

2011-03-01 09:15:08.43      *** Error: Could not apply log backup file 'F:\logshipping\hipath8k_v4_0\osv_projects_hipath8k_v4_0_db_20110228223011.trn' to secondary database 'osv_projects_hipath8k_v4_0_db'.(Microsoft.SqlServer.Management.LogShipping) ***
2011-03-01 09:15:08.43      *** Error: The file on device 'F:\logshipping\hipath8k_v4_0\osv_projects_hipath8k_v4_0_db_20110228223011.trn' is not a valid Microsoft Tape Format backup set.
RESTORE LOG is terminating abnormally.(.Net SqlClient Data Provider) ***
0
Comment
Question by:SiemensSEN
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 4

Accepted Solution

by:
rocky_lotus_newbie earned 250 total points
ID: 35009712
Looks like there is problem with the log backup file. This might happen due to some disk write errors while the log backup is taken.
try running restore verifyonly to see if the log backup file is valid. You will get saying it is not valid if there is any corruption

Please try copying the file once again from primary server.

0

Featured Post

Free Tool: Postgres Monitoring System

A PHP and Perl based system to collect and display usage statistics from PostgreSQL databases.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Introduction In my previous article (http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/A_9150-Loading-XML-Using-SSIS.html) I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
Ever wondered why sometimes your SQL Server is slow or unresponsive with connections spiking up but by the time you go in, all is well? The following article will show you how to install and configure a SQL job that will send you email alerts includ…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question