Symantec Backup Exec - Capacity Wrong for Tape Drive
Posted on 2009-05-13
Hello, experts. I've checked many similar questions/answers on EE and found a lot of great info, but none of it solves my problem.
~ SUMMARY ~
I think my issue is that Symantec is showing the wrong capacity for the tape in my tape drive (400MB rather than 400GB), and so the capacity check fails when I try to run a backup. I need to figure out how to correctly detec tape size.
~ DETAILS ~
I'm running Symantec Backup Exec on our server to backup various files, including our database. However, all backup jobs-- including test runs-- fail. The log file shows success on everything except the media capacity check. But there's obviously a problem there:
Online append capacity: 0.000 MB
Online overwrite capacity: 396 MB
Total append capacity: 395 MB
Total overwrite capacity: 1,189 MB
Capacity check status: Failed
Besides the fact that those numbers don't add up right, the issue is that TANDBERG1 is a tape drive loaded with a 200GB native/400GB compressed tape. My backup job is roughly 40GB, so it's no wonder it's failing if it thinks TANDBERG1's capacity is a mere 400MB.
A bit of history: everything was working great with Symantec Backup Exec writing to TANDBERG1, and we cycled about a dozen of these tapes in and out for nightly backups. However, I needed to free up space on our OS partition, so I uninstalled and reinstalled on a different drive. Now this issue, but I know there's nothing wrong with the drive or the tapes themselves.
So why the faulty capacity? It's not just this tape-- I have this issue with all of them. I have tried associating the tape with different media sets, including Scratch Media and a custom media set I created with only 1 hour overwrite protection and an appendable period of "Infinite - Allow Append." When I look at the details on that tape (and I know it's the right one, because I've labeled them all), it shows it is indeed Overwritable. And just to verify, my job is set to "Overwrite Media."
So I'm guessing the root issue is just that the tape capacity is not being detected correctly. One post I saw suggested running a long erase on the tape, and I've done so. However, the capacity still shows up wrong and backups still fail. In short, it did no good.
Any help you can provide would be great! We're a few days behind on db backups and I'm starting to get antsy! :-)