Thanks for your reply....
Yes, we used your method with versions prior to TSM 4.x.... but I would be
interested in knowing if you were able to use this method with the new 4.x
version.... when we tried to boot off the solaris 8 jumpstart cd, and then
run tsm 4.x, it complained about not having some solaris libraries --that
you can only get if you do a complete "end user" solaris install to disk,
but then it would seem that you must "restore over" the solaris OS, which
then produces other errors.....
That is why we are thinking about somehow installing a complete OS (not just
the jumpstart in /tmp), or using bootp.....
Would appreciate any additional input you have, -as I will also try and
update this list with our experiences as we try to find a BMR solution
(which I think is really strange, since Tivoli claims to be a complete
enterprise solution --tivoli support acutally told me there are not BMR
solaris procedures, and it is not supported!)
Keith
----- Original Message -----
From: "Brian T. Huntley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 04, 2001 11:42 AM
Subject: Re: Can you use dual boot method to BMR Solaris with TSM 4.x?
> On Fri, 4 May 2001, Keith Kwiatek wrote:
>
> // Hello,
> //
> // Has anyone tried to use a dual boot method to allow a bare metal
restore
> // with a solaris 4.x client? In other words, would installing a bootable
> // solaris instance into a "temporary" filesystem, along with the TSM4x
> // client, --permit you to recover the original system "Completely"...
kinda
> // like using bootp....
> //
> // It seems if you try BMR by installing solaris on top of a solaris
instance
> // you get a bunch of errors as it steps on active OS files.....
> //
> // Keith
> //
> //
>
> We have worked on this, although on Solaris 2.6 and 8, not 4.
>
> The best way we have found is this:
>
> - Boot off a CD or an appropriate image on a JumpStart Server
> - Configure the slices on your disk at least as big as they were
> before
> - NFS mount the TSM software
> - Run restore
> - Reboot.
>
> Just make sure that you update the TSM files to put the logs in /tmp, and
> update the dsm.sys to reflect the node you want to restore.
>
> The reason we actually did this was to make 'images' of servers, thus
> ensuring that all of our round-robin-ed and redundant servers were running
> the exact same configuration, with little or no potential for human error;
> just change the hostname and IP and go! Works very well.
>
> -Brian
>
> --
> +-----------------------------------------------------------------------+
> | Brian T. Huntley Systems Administrator |
> | Campus Information Services, Clarkson University |
> | Ph/FAX: 315.268-6723/6570 |
> | [EMAIL PROTECTED] www.clarkson.edu/cis |
> +-----------------------------------------------------------------------+
> UNIX *is* user friendly. It's just selective about who its friends are.
>
