there's just the TOC and the magic boot block to worry about - aside
from that it should work

we usually just jumpstart another disk, install NW and overlay a full
recover - assuming the client machine is ok

HTH
Jerry

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of K D
Sent: Friday, December 15, 2006 10:35 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Directed recover to new disk

Some important clues that may help decipher my plan:

Server A is a Solaris box as is the machine (we will call Server B) with
the
empty drive bay.

Server B does not use the replacement disk at all.  It is a completely
self
sufficient system with its own boot disk.

The replacement disk for Server A is placed into the spare drive bay of
Server B for the sole purpose of restoring data to it.  The disk is
partitioned and formatted to exactly match the one that crashed on
Server A.
 Server B already is a client of Networker and has the Networker client
installed.

I should be able to do a directed recover of Server A's file sytems to
the
mounted partitions of replacement disk on Server B.

Thank you,
Kris

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER