Re: SCO UW disaster recovery
- From: Dan Martin <dc.martin@xxxxxxxxxxx>
- Date: Tue, 11 Dec 2007 06:04:07 -0800 (PST)
On Dec 10, 8:44 pm, mvsguy <kkin...@xxxxxxxx> wrote:
Whats your time worth?
Hello mvsguy,
One last plug for the commercial stuff...
My time? I have to show up at least 8 hours each day. I might as
well do some work...
they help out on those days when you show up for work only to find
that you need 25 hours in the day to get the job done.
I've cleverly disguised my handle to cover the fact that I'm an MVS
guy. Mainframes. I know how important DR is.
I've had a full on disaster caused by IBM applied hardware
maintenance. We only lost 18 hours of data.
Do you mean 18 hours times a thousand users? Or 0.018 minutes per
user a thousand times? The former sounds catastrophic to me.
Likewise, if a drive fails and you can't boot the Unixware machine,
how
many users will be sidelined, and for how long, while you do the
recovery?
Later that month, we did
our first DR test. We did amazingly well.
Thank you both for trying, but buying software is simply not in the
cards.
Cactus and Microlite offer their prodcuts on a time-limited eval
basis.
Get the free download, create the emergency boot media and create a
master
backup. Lock them away in case disaster strikes. AFAIK, you can
restore from them even after the eval period has expired.
So far, you've spent only your time and no discretionary dollars.
Then, 6 months
from now, or whenever something bad happens, you can restore the
system to
the way it looks today. Then restore from whatever backups you create
on a
daily basis. Then, ask your boss if you can spend the ~$400 to buy
the software.
Maybe I should ask a specific question. How do I go about using the
emergency tape/disks I've been making?
Sorry, I don't know enough about Unixware to be specific. I'd start
by
testing the floppies, to make sure they can boot a computer other
than
the production system. Once you know the floppies work, schedule
a time when you can test boot the production system with them. Don't
assume that, because the floppies booted a test machine, they will
successfully boot your production system.
Once booted from floppies, test to see if you can mount the hard disk,
and read
your backup tape in its entirety (note that this does not verify the
data
on the tape). Duplicate the floppies. Don't forget to store an image
on the
production system (so they get backed up). Buy some disk drives to
use
as spares, preferably exactly what you have in the production box.
Booted
from the floppies, see if you can get your data onto one of those
spare hard
drives, and be able to successfully boot from that hard drive.
Carefully
document all of the steps, because that's what you'll be facing when
you
have a disk failure.
A better approach might to work from the commercial backup evals
again.
Test a disaster recovery to a spare drive. Choose the step by step
method
so that you can get an idea of all that's involved.
Best regards,
Dan Martin
Regards,
MVSGuy
.
- References:
- SCO UW disaster recovery
- From: mvsguy
- Re: SCO UW disaster recovery
- From: Jeff Hyman
- Re: SCO UW disaster recovery
- From: mvsguy
- SCO UW disaster recovery
- Prev by Date: Re: SCO UW disaster recovery
- Next by Date: Re: SCO UW disaster recovery
- Previous by thread: Re: SCO UW disaster recovery
- Next by thread: Re: SCO UW disaster recovery
- Index(es):
Relevant Pages
|
