• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 282
  • Last Modified:

sqlback up failure

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
JOLEEJJ
Asked:
JOLEEJJ
  • 2
1 Solution
 
PadawanDBAOperational DBACommented:
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
 
JOLEEJJAuthor Commented:
Hi

A simple server reboot has resolved the issue.

Thanks

Joe
0
 
JOLEEJJAuthor Commented:
Hi

A simple server reboot has resolved the issue.

Thanks

Joe
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now