This is a revival of an old thread.
Don,
Does your tailored jumpstart CD include the TSM client?
I'm attempting to develop a bare metal restore procedure for Sun workstations
with only one hard drive, and the problem is that restoring over the OS that
you are running from breaks the restore when /usr/lib comes back.
I'm using Solaris 2.6, client 4.1.1 and server 3.1.2.50.
When I've got the base case working, I need to expand it to include VVM, VXFS
and Veritas clustering on E450 and E3500 Servers (obviously with more than one
drive!)
I'd really like to hear from anyone with a working Bare metal procedure for
Solaris. I'm aware of TKG's offerings but they aren't possible in this
environment. Also be gentle with me as I'm an AIX person adrift in a Solaris
sea .....
Thanks
Steve Harris
AIX and ADSM Administrator
Queensland Heath, Brisbane Australia
>>> "France, Don G (Pace)" <don.france-eds AT EDS DOT COM> 02/11/2000 9:53:25
>>> >>>
We have two schools-of-thought in use by our shop:
using ADSMPIPE, re-direct "ufsdump" or "dd" to TSM storage --- currently,
we have this in place for about 30+ machines; the OS file systems are the
only ones handled this way; full system recovery starts with the OS,
redefine the remaining physical and logical disk structures (partitions &
file systems, VFS configuration, etc.), restore OS, then restore the rest of
the system per dba design.
using standard, flat-file (daily, full-incr) of the OS (and file-served)
file systems in concert with a machine-type specific jump-start CD (built by
a Sun professional services team); we have 3 E10K's (with 12 domains) plus
about 20 E420's being protected this way. This is a new environment, and
the Unix admin. Team is looking at deploying the LFS-image (in TSM) or
ADSMPIPE approach.
Both methods are in place, and have been tested; I don't know the exact
details of audited-test results... we like the ADSMPIPE scenario for its
restore speed with the fewest tape mounts (of course), but flat-file works
fine, as well. Besides, the largest workload in restoring a system is the
data base & application data... not part of your question. (The OS piece is
strategically critical, but is less than 10% of the data being restored!)
BTW, we protect our AIX rootvg using mksysb tapes on a daily rotation; we
protect Win2k and WinNT using a "standard image" CD, with scripts that run
almost-unattended re-install followed by TSM full system restore for
recovery, similar to the Redbook examples.
Hope this helps.
Don France
Technical Architect - Unix Engineering/P.A.C.E.
San Jose, CA
mailto:dfrance AT pacbell DOT net
PACE - http://www.pacepros.com
Bus-Ph: (408) 257-3037
-----Original Message-----
From: Arturo Lopez [mailto:arturo.lopez AT USAA DOT COM]
Sent: Wednesday, November 01, 2000 1:13 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Restore Sun Solaris from scratch
Hello All
Is anyone familiar with restoring Sun Solaris from scratch. I have a Sun
Sys Admin that does not believe TSM can restore the entire OS from scratch.
With AIX we use a SYSBACK to take an image of the OS and restore the image
and then apply the incremental to bring the OS back to pristine level. Does
anyone have experience restoring a Sun Solaris box from scratch...
On the Intel world running WinNT 4.0. We load a second instance of NT and
then boot into the second instance and restore the original OS and Registry.
Then reboot server into original instance.....Can you do this with Sun......
Thx
Arturo Lopez
IT Systems Programmer
210.913.1845
210.753-1845
|
