We're using the Windows 2000 backup software Version 5.0 on a Dell 530
desktop to backup data to a Dell Powervault 110T DELT VS 80 tape drive.  A
year ago we did a backup.  We are now trying to restore data from this
backup.  The program allows us to select the correct backup and asks for the
tape #12 (final tape) which it then reads.  Then it acts for a non-existant
tape #13.  When it doesn't find it, it aborts the restore, without creating a
catalog set for us to restore from.  Dell said it sounded like the catalog on
tape #12 was corrupted which is why it was asking for #13.  They knew of no
way around this to restore the data and suggested that we try Microsoft.  Any
advice would be appreciated as this is 18+ months of data!!

My suggestion at this point would be to get hold of a copy of Veritas
Backup Exec (or -- with less enthusiasm -- Arcserve). Either of
these can read msbackup tapes and I'm pretty sure Veritas
at least is able to rebuild a catalog by reading the tape contents,
though I've never tried it with an msbackup. Veritas may have a
30-day demo you can download - I'm not sure.

A <gulp> data recovery service is the next step. After that, looking
for another job tends to attain a certain allure.

Now for the cold, hard truth-telling time. This wasn't part of your
question I know, but that's the problem with free advice :-)

If you're doing a 12 sequential non-raid tape backup with msbackup,
you have a problem. For the same reason that a 12-disk raid0 stripe
set would be a problem; one failure and >poof<. And if you're not verifying
and checking your backups you have a problem.

Your problem is that your company is not taking server backup
seriously enough. And now you stumbled into the awful reality as to
why you have to take it so seriously. Most of us get that lesson at
one point or another, so I feel your pain.

After you get past this mess, the first thing you need is a DLT 320,
LTO or other high-capacity enterprise tape solution that can handle
the data footprint you have. You may want to consider adding
differentials and incrementals to the mix to reduce the overall
backup load.

Then - as overpriced as they tend to be - you absolutely need "real"
backup software and there are a half-dozen or so reasonable ones
out there to choose from.

I would also recommend a weekly "safety backup" to a network share
or NAS box on another machine. And of course you need rotating offsites.
You need a disaster rebuild contingency in case you have to build up your
server/domain from a fresh or flattened state (imaging software
can be helpful here, or you can use an option on the backup software.)

You need to verify your backups and you need to check them occasionally
by trying to restore something from them. You need to periodically review
your selection and exclusion lists to make sure new stuff is getting captured.
Check the logs. All the usual scut-work sorts of things that nobody wants
to bother with as long as things are working.

Backup is the one true and ultimate redemption for all cybersins,
mortal and venial. It doesn't matter what it costs, it can get you in to
heaven when you need it. Spend it.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.

Show quoteHide quote

Registry_error
copy files and keep security
Deploying icon to numerous desktops
Can't open Network and Dial-up properties
Task Scheduler not run
This systems is shutting down
Why would I want an OU?
W2K loops during startup
Moving software
What does Take Ownership mean?