Solved

sqlback up failure

Posted on 2013-12-12
3
269 Views
Last Modified: 2013-12-22
Hi,

I have a couple of databases in a  primary server and I am running maintenance job to backup database (daily at night time)  and transaction logs (every half an hour) to an attached SAS driver. It was working well without any issue.  Yesterday, I have detached the SAS drive from the server and took it to the secondary server for restoring one of my databases, "MyCustDB". After restoring, I have attached the SAS drive back to the primary server. After attaching it, the transaction logs as well as backup started failing with the following reason.  MyCustDB has a Filestream which is created not in the default C: drive of the primary server but in the SAS drive (G:).  The primary filegroup pathis is C: drive but the "FG_MyCust_FS" (filestream) path is G: drive (detachable SAS drive).

Error message:

Executing the query "BACKUP DATABASE [MyCustDB] TO  DISK = N'\\\\JoeServer..." failed with the following error: "The operating system returned the error '21(failed to retrieve text for this error. Reason: 15105)' while attempting 'FsFileHeader::Read' on 'G:\\MyCustDB_2.MyCust_FileStream'.
The header for file 'G:\\MyCustDB_2.MyCust_FileStream' is not a valid database file header. The File Header property is incorrect.
BACKUP DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.


The database in running in SQL SERVER 2008R2.

Please help me on this.

Thanks

Joe
0
Comment
Question by:JOLEEJJ
[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
  • 2
3 Comments
 
LVL 10

Expert Comment

by:PadawanDBA
ID: 39716944
Can you check the OS event logs for the corresponding error information so we can get more details?  My guess is there's an OS error preventing you from reading the file header, but we need to find that first.
0
 

Accepted Solution

by:
JOLEEJJ earned 0 total points
ID: 39725729
Hi

A simple server reboot has resolved the issue.

Thanks

Joe
0
 

Author Closing Comment

by:JOLEEJJ
ID: 39734478
Hi

A simple server reboot has resolved the issue.

Thanks

Joe
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

I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

630 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