Solved

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

Posted on 2011-03-01
1
646 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

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

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

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
JSON is being used more and more, besides XML, and you surely wanted to parse the data out into SQL instead of doing it in some Javascript. The below function in SQL Server can do the job for you, returning a quick table with the parsed data.
Explain concepts important to validation of email addresses with regular expressions. Applies to most languages/tools that uses regular expressions. Consider email address RFCs: Look at HTML5 form input element (with type=email) regex pattern: T…
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties

751 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