Solved

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

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

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

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

In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
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…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.

627 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