[Networker] Solaris 10 x86 host could not init 5/6 after full OS restore

>  Good suggestion, except that x86 doesn't have an "ok" prompt. It uses grub. 
> Interrupt the boot process and edit the command line and add "-s" to the 
> boot. That will boot it up to single user mode.
> 
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] 
> On Behalf Of Kinnison
> Sent: Saturday, December 11, 2010 3:31 PM
> To: NETWORKER < at > LISTSERV.TEMPLE.EDU
> Subject: [Networker] Solaris 10 x86 host could not init 5/6 after full OS 
> restore
> 
> I am assuming you do not have Sun Solaris support. First off, this sounds 
> like an OS problem, not a Networker problem (is your server's firmware up to 
> date?). I would suggest using the Solaris mailing list, of which there are 
> several. 



Dear all,

I followed exactly on what was documented on the Networker 7.6 SP1 DR Guide as 
follows but still encountered the init freeze problem again. 

- Install the Solaris 10 using OEM Full software cluster on a Solaris 10 x86 
machine
- Install the Solaris 10 patch cluster which brings it to Kernel patch 142910-17
- Perform a full backup of this maching using saveset "All" via Networker 
client running on version 7.6 SP1.
- Install a initial Solaris 10 base OS using Core User software cluster
- Install the same version of the Networker client
- Use the CLI recover command to perform a full restore overwriting existing 
files on the machine except for the following OS files which was exactly 
documented in the Networker 7.6 SP1 DR Guide

? Operating system boot files, such as:
? /unix
? /boot
? /etc/default/boot
? /stand/vmunix

? Other operating system files. For example, some of the files not to overwrite
on the Solaris platform include:
? /dev directory
? /etc/path_to_inst
? /etc/name_to_major
? /etc/mnttab
? /etc/dfs/sharetab
? /etc/rmtab
? /kernel
? /usr/kernel
? /etc/saf/zsmon/_pmpipe
? /etc/sysevent/piclevent_door

- Perform another recovery of the above excluded files/directories and direct 
them to a temp directory in /var/tmp
- Reboot to failsafe mode and restore the above files to the original locations 
and reboot
- Encountered boot archive inconsistency errors and boot to failsafe mode again 
to rebuild the boot archive
- Perform reconfiguration reboot of the server to multi user mode and the 
recovery is done


Anyone had successfully performed a Solaris OS recovery based on the DR guide 
and would like to share your experience?
Thanks for enlightening.[/quote]

+----------------------------------------------------------------------
|This was sent by ddl1976 AT yahoo DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

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