Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Win 2000 Backup Gone Bad


  • Please log in to reply

#1
magusbuckley

magusbuckley

    Member

  • Member
  • PipPipPip
  • 625 posts
Hello:

At work, we have two Micros Servers - a Primary and a Secondary. Micros is our POS system. We've been running a tape backup on both machines for some time via the Windows Backup Program. Our Primary server has been having trouble lately though and I finally made time to investigate it today. The problem, as it turns out, seems more serious than I had hoped.

When I looked at the log files for the backups, they all stated that "The Backup Could Not Be Completed Because The Specified Media Could Not Be Found." That has been going on for more than a week now. I assumed the tape drive was on the blink because the power light was flashing. I rebooted the server and the flashing stopped. Then I wiped out all of our backup log files and the scheduled backups. My plan was to start from scratch. I was unable to get the drive to recognize one of the tapes so tried another. I got the same results. Tired of fooling with those old tapes, I opened seven new ones (one for each day's backup). I labled the tapes and popped the first one in. When trying to perform a manual backup with the Windows Backup software, I received the following message - "Library SEAGATE DAT 9SP40-000 SCSI Sequential Device Couldn't write to media 870. Eject it, fix the problem (see the event log), and try again."

Just as it asked, I checked the event log (viewer) and found the three following error messages for each days log.

Error 1 - The device, \Device\Tape0, has a bad block.

Error 2 - RSM could not identify the media in drive Drive 0 of library SEAGATE DAT 9SP40-000 SCSI Sequential Device. An error was encountered while attempting to read data from the media.

Error 3 - Library SEAGATE DAT 9SP40-000 SCSI Sequential Device failed to write a Free media label on media 870 because an I/O error occured while writing the label.

Asside from rebooting the server, the only other thing we've done is used the cleaning tape on the drive.

I assumed a bad block meant the tape was bad, but they seem to all have bad blocks. Now I'm wondering if the drive itself has gone bad.

Any and all information will be greatly appreciated.

Thanks,

Magus
  • 0

Advertisements


#2
piper

piper

    Retired Staff

  • Retired Staff
  • 2,459 posts
According to Veritas (Symantec now) tech article 241684, \Device\Tape0, has a bad block (Event ID 7), can indicate a problem with Firmware, Driver, or Controller Card. Check for updated drivers and firmware. In my case a month ago, it was the controller.
  • 0

#3
magusbuckley

magusbuckley

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 625 posts
LindaGail:

Thanks for the reply.

I downloaded a diognostic program from Seagate but it didn't help any. The problem is that the tool doesn't work on Tape Drives (go figure).

According to the Device Manager, the drive is operating normally. Still, I'll have a look to see if we can download anything to fix this problem.

If anyone else has an idea, please let me know. I'll be checking for drivers and such in the mean time.

Thanks,

Magus
  • 0

#4
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
you say you've got two servers running backups? so that would be two seperate tape drives right? the primary is not working but the secondary is right?

try doing a manual backup on the secondary with one of the primary's tapes...if it works...then it's not the tape that's messed up....

if you have the ability to do so...try switching tape drives...then run a manual on the primary (with the drive from the secondary attached)...if that works...then it's the primary's tape drive that's messed up
  • 0

#5
magusbuckley

magusbuckley

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 625 posts
dsenette:

Thanks for the reply.

I've downloaded a new driver for the drive but that didn't seem to help.

That's a good idea you have about putting the tapes in the working drive.

I'll try that today. If we suspect the tape drive, we won't be able to do any actual work on it until Tuesday or Wednesday in the middle of the night. We are in the casino industry so bringing down our POS machines on the weekend isn't really an option for us.

I'll let you know what I come up with.

Thanks,

Magus
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP