[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:	NetWorker
Notice:	kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:	DECWET::RANDALL.com::lenox

Created:	Thu Oct 10 1996
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	750
Total number of notes:	3361

632.0. "recovering from standalone" by EVTAI1::POUSSARD () Mon Apr 28 1997 05:40

	Hi,


	Let's assume that a NSR UNIX client system disk has a nonrecoverable 
hardware problem , and the customer didn't do a backup of the system disk 
with the dump utility, can we recover the system disk from the NSR server by 
booting the standalone CDROM utility ?

	I mean:

	- we must boot the standalone on the client
	- start the network fronm the standalone
	- copy back the NSR binary recover from another machine with the 
same CPU architecture.
	-recover the /, /usr with this recover command


	Is there some experience about that ??

	

	thanks


					Gilles.

T.R Title User Personal
Name Date Lines

632.1 DECWET::FARLEE Insufficient Virtual um...er.... Mon Apr 28 1997 14:50 14

T.R	Title	User	Personal Name	Date	Lines
632.1		DECWET::FARLEE	Insufficient Virtual um...er....	`Mon Apr 28 1997 14:50`	14
	What you suggest might be possible, and I HOPE to make a summer project of adding this functionality to a bootable CD along with helper scripts to set up the network, mount physical disks, etc. Obviously, we have not fully tested it, and the CSC would likely call it "unsupported". If you attempt this, I would pull the srecover image, and make sure that it matches the version of the OS (i.e. pre/post 4.0) for the disk being booted. Another option is to add "srecover" to the system management root on a RIS server, and go from there. Just be sure to set the date on the client system after the RIS boot. Kevin

What you suggest might be possible, and I HOPE to make a summer project
of adding this functionality to a bootable CD along with helper scripts
to set up the network, mount physical disks, etc.

Obviously, we have not fully tested it, and the CSC would likely call it
"unsupported".  If you attempt this, I would pull the srecover image,
and make sure that it matches the version of the OS (i.e. pre/post 4.0)
for the disk being booted.

Another option is to add "srecover" to the system management root on
a RIS server, and go from there.  Just be sure to set the date on the
client system after the RIS boot.

Kevin