From: Malli, Brandon (brandon.malli@nagrastar.com)
Date: Tue Mar 02 2004 - 13:50:44 EST
Managers,
Thanks to Alan for the info.
Basically what I found was that there was no reason we couldn't use our
existing procedure. The backup type - or way you do it for that matter
- is really inconsequential. The only thing that I noticed that you had
to do was make sure the IDE drive was the master, then when you get
booted to single user (after the restore), issue /sbin/mountroot, then
use the dsfmgr to swap your disks (something like "dsfmgr dsk3 0").
Here is a nice website that has a "Best practices" for tru64 5.0 and
above.
http://h30097.www3.hp.com/docs/best_practices/BP_RECROOT/TITLE.HTM
-----Original Message-----
From: Malli, Brandon
Sent: Monday, March 01, 2004 4:46 PM
To: tru64-unix-managers@ornl.gov
Subject: Gtar restore on 5.1a
Managers,
We typically use a script (that basically invokes a gtar) to create
backups of all our 4.0x hosts. Once the gtar of each filesystem has
been created we simply transfer it to the new host - which is booted off
cd with the drives mounted to a temp directory - untar the filesystems
to the appropriate mount point, fix the host specific files (/etc/fdmns
links, fstab, etc), reboot, rebuild the kernel, reboot again and voila.
The new host comes up just fine.
When we try to use this procedure on 5.1a I get a "panic (cpu 0):
init_rootdev: boot device translation failed" error and consequently am
unable to boot - even with single user. As I recall 5.1a manages the
disk drives differently and the procedure we use on 4.0x should not
work. What I'm looking for is a brief technical explanation why and a
suggestion as to what we might use for a simple backup solution similar
to the 4.0x procedure.
Not a urgent matter but one I would greatly appreciate any advice on.
Thanks in advance,
Brandon Malli
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:52 EDT