Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 On a scale of 1 - 10

Author  Topic 

elwoos
Master Smack Fu Yak Hacker

2052 Posts

Posted - 2006-12-11 : 11:27:06
How worried should I be about this?

Today we got an error in the SQL server logs (SQL Server 7) -

quote:
The Microsoft Tape Format (MTF) soft filemark database on backup device 'N:\backup\MyDB.BAK' cannot be read, inhibiting random access.


This led me to [url]http://support.microsoft.com/kb/290787[/url] which suggests a write failure. Given Kristens recent experiences [url]http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=76085[/url] I am becoming increasingly concerned about this box which is over 6 years old already.

Anyone have any thoughts?

I've run DBCC CHECKDB which came back ok. Any thoughts on anything else that I should run?

Many thanks in advance

steve

-----------

Don't worry head. The computer will do all the thinking from now on.

Kristen
Test

22859 Posts

Posted - 2006-12-11 : 11:39:31
Isn't this just a problem with the Tape media? If it occurs often then the tape head needs cleaning, or the tape unit needs replacing. Or is that too simplistic a view?

Kristen
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2006-12-11 : 13:03:16
Can that file be restored? If not, can you make a new backup and then restore that?

Tara Kizer
Go to Top of Page

elwoos
Master Smack Fu Yak Hacker

2052 Posts

Posted - 2006-12-12 : 03:30:40
quote:
Isn't this just a problem with the Tape media


My apologies, I haven't explained enough in the mild hysteria of the moment.

What should be happening is that SQL Server does it's backups to disc and then this is backed up elsewhere by our network team. As they haven't been doing that for a while I only have the backups on disc at the moment. I am concerned that this error highlights a potential issue with the disc or the disc controller. In particular the discs that the backups are done to are the same array that the data files are held on!! (nowhere else to put them apart from a seperate server that is physically in the same location)


quote:
Can that file be restored?


Good question Tara I'll give that a go. I've already made another backup so if neccessary can use that.

Nice to see you back Tara, hope you are well.

Thanks both

steve

-----------

Don't worry head. The computer will do all the thinking from now on.
Go to Top of Page

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2006-12-12 : 04:03:27
Maybe the backup time is too long so the backup device aborts?
http://www.sqlteam.com/item.asp?ItemID=136


Peter Larsson
Helsingborg, Sweden
Go to Top of Page

elwoos
Master Smack Fu Yak Hacker

2052 Posts

Posted - 2006-12-12 : 04:22:58
Nice one Peso, I haven't noticed that before. It's certainly a possibility and that means I can look for recent changes which may be a cause.

The database itself is relatively small (<3GB) which means backups don't take too long normally but I know our Network guys have put new software on it. That could be a factor

steve

-----------

Don't worry head. The computer will do all the thinking from now on.
Go to Top of Page

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2006-12-12 : 04:48:42
Sending 3 gig over the network to drive N (which probably is a network attached driectory), is prune to so many thing to go wrong. Slow network, any switch failure, the remote server temporarily busy and so on...

Just a clarification of my previous post.


Peter Larsson
Helsingborg, Sweden
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2006-12-12 : 06:31:48
Maybe the hardware guys have economised and replace the SAN on the N: drive with a random-access-tape unit? Probably the up-market 4-reel tapes you see on James Bond movies ...
Go to Top of Page

elwoos
Master Smack Fu Yak Hacker

2052 Posts

Posted - 2006-12-12 : 08:28:49
quote:
Sending 3 gig over the network to drive N (which probably is a network attached driectory)


I see where you are coming from but it's all on the same box. This is before it goes over the network, no other servers of any type are involved at this point.

The initial backup to disc is onto the disc(s) on the same box that the SQL Server is on. Only after that is complete would it get shuffled over the network and I don't think any error there would show in the SQL logs.

Kristen if you are talking about the very early Bond films then you could be right


steve

-----------

Don't worry head. The computer will do all the thinking from now on.
Go to Top of Page
   

- Advertisement -