From: Caparroso, Nelson T. (AAS) (Nelson.T.Caparroso@sbcdo.com)
Date: Mon Apr 08 2002 - 10:19:25 EDT
For the above mentioned reasons (but in our case DR and ServerBuilds), I've
the following procedure in quickly building a transported bootdisk. By
"transported bootdisk" I mean (1) a clone of an existing reference server's
bootdisk or (2) a restore of a dumped OS image using any means imaginable.
And by "reference server" I mean a server built using Solaris 8 Full+OEM so
you could "transport" a bootdisk from an Ultra-2 to a E10K/15K domain.
Assuming you've already got the disk connected to the new server:
1. boot the target system to miniroot (boot cdrom -s or boot net -s)
2. reckon from format what your bootdisk is on thie system from format ex: -
c2t0d0
3. mount up your system partition / to /a
4. rm /a/dev/cfg/* rm /a/dev/rdsk/* rm /a/dev/dsk/*
5. devfsadm -C -v -r /a -p /a/etc/path_to_inst -t /a/etc/devlink.tab
6. check /a/dev/dsk for the bootdisk's device path
7. update /a/etc/vfstab
8. various /etc/ modifiations and clean up.. ie( E10K dependencies,
/etc/system, network host settings, etc...)
9. reboot off the bootdisk in reconfiguration mode
This has worked for us in recovering UExx00 servers, a 280r and an UE2 to
E10K domains in a DR exercise - siginificantly cutting system recovery time.
I know some of you may frown at the idea and I'd like to get your comments /
opinions on this strategy. I am aware of flash archive technology - in fact
this is what we've used when we transitioned from Solaris 2.6 to Solaris 8.
Thanks.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:10 EDT