Definitive method to backup HP-UX root disks
Kyle Tucker
I am trying to figure out how to ensure I have backed
up to tape *exactly* what I need to recover a crashed
root disk should disaster strike. On Solaris, this is cut
and dry how to do this and recover from it. But in my
readings of docs at docs.hp.com and news articles on
DejaNews there appears to be no set method. I've seen
fbackup and mkboot, Excite-UX, copyutil, dd, get a new
job if it crashes, etc. Can anyone point out *THE* absolute
way one would do this? This is on some 10.20 S800 using LVM,
/ not mirrored (yet). If it matters, OmniBack II will be
running once I get a handle on that. Thanks.
--
- Kyle
--------------------------------------------
${randomsig:="Oh well"} ky...@shore.net
--------------------------------------------
rco...@voicenet.com
Kyle Tucker <ky...@shore.net> wrote:
> Hi,
> I am trying to figure out how to ensure I have backed
> up to tape *exactly* what I need to recover a crashed
> root disk should disaster strike. On Solaris, this is cut
> and dry how to do this and recover from it. But in my
> readings of docs at docs.hp.com and news articles on
> DejaNews there appears to be no set method. I've seen
> fbackup and mkboot, Excite-UX, copyutil, dd, get a new
> job if it crashes, etc. Can anyone point out *THE* absolute
> way one would do this? This is on some 10.20 S800 using LVM,
> / not mirrored (yet). If it matters, OmniBack II will be
> running once I get a handle on that. Thanks.
>
I have used the make_recovery utility that's part of the Ignite-UX toolkit on
several occasions. I used to use copyutil, but the machine has to be down in
order to use that so it is a little impractical. However, you get an exact
byte for byte copy of the disk you are backing up, so it does have some
advantages.
My vote is make_recovery - you can even duplicate a system using it, which I
have done many times. It's really easy to use, but you need to use DDS
technology tapes with it.
Simple command line: make_recovery -Av -d /dev/rmt/0mn and in 40 minutes or
less you have a bootable tape of your system.
I will say thought that you must fully understand how your root volume group
is constructed to be sure that you are infact getting all the root volume
group data backed up. Read the make_recovery man page and check your system
configuration to be sure.
My two cents ...
Rick
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
John Pezzano
>
> Hi,
> I am trying to figure out how to ensure I have backed
> up to tape *exactly* what I need to recover a crashed
> root disk should disaster strike. On Solaris, this is cut
> and dry how to do this and recover from it. But in my
> readings of docs at docs.hp.com and news articles on
> DejaNews there appears to be no set method. I've seen
> fbackup and mkboot, Excite-UX, copyutil, dd, get a new
> job if it crashes, etc. Can anyone point out *THE* absolute
> way one would do this? This is on some 10.20 S800 using LVM,
> / not mirrored (yet). If it matters, OmniBack II will be
> running once I get a handle on that. Thanks.
fbackup = file backup - not an operating system (hard disk) backup
mkboot = makes a boot area on a disk. Not a backup utility at all
Excite-UX - Huh! You mean Ignite-UX? One of its features is a program
called make_recovery which creates a bootable tape that will restore a
blown root disk. You create the tape (customizable) online and it is
bootable itself so no additional tapes are needed to restore the root
disk. After restore of make_recovery tape, you restore the updated files
from an fbackup or other file backup utility.
Copyutil - an offline backup/restore that existed before make_recovery.
Does bit by bit backup of root disk OFFLINE. Use make_recovery instead.
copyutil requires not only that you not be booted up but you need to
keep your backup plus have available the Support CD or tape with
copyutil on it.
dd = online bit image of disk to tape but nothing to recover it with.
In summary, make a make_recovery tape every time your LV or VG
information changes. This should not be very often. Use fbackup,
OmniBack or your favorite file backup utility for file backup or
recovery. The make_recover tape is for loss of root disk.
Frank Slootweg
"*THE* absolute way". If there was, then the other ways would not exist,
so it would be "the ONLY way".
Enough rambling! :-)
fbackup is a file backup utility, so it can not be used for crash
recovery, because it does not back up the LIF area, the boot area, the
LVM datastructures, etc. dd(1) is no longer advised because of its
limitations (see the "RESTORE" section in hpux(1M).
So what remains are Ignite-UX (I love your "Excite-UX" typo! :-)) and
COPYUTIL. I think that most people would agree that Ignite-UX
(make_recovery) takes some time to study, plan and execute for the first
time, but once you have done that, it is relatively easy, and very
flexible and fast. The learning curve for COPYUTIL is much easier, but
it is not flexible (compared to make_recovery) and rather slow.
I hope this helps.
Kyle Tucker
>
> Like for anything else in this universe, there is no such thing as
> "*THE* absolute way". If there was, then the other ways would not exist,
> so it would be "the ONLY way".
It seems as though it was a progression of methods from HP.
> So what remains are Ignite-UX (I love your "Excite-UX" typo! :-))
Yah, what a goof.
> I hope this helps.
Absolutely, thanks much. It appears unanimous from follow-ups
and email replies that make_recovery is the way to go.
--
- Kyle
--------------------------------------------------
${MS_ADVANTAGES:="I thought so"} ky...@shore.net
--------------------------------------------------