[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

394.0. "recovering /nsr from a tar and not from mmrecov" by EVTAI1::POUSSARD () Fri Feb 07 1997 06:44

	Hi,


	I did mmrecov and recover to recover a specific /nsr directory. The 
process was long.

	Will it work, if we restore from a tar the /nsr directory, and start 
nsr, and have the image of the database at the time we did the tar ??
	
	The customer thinks it could do a tar of /nsr once a week.


	Thanks for your answer


	Gilles.

T.R Title User Personal
Name Date Lines

394.1 disaster recovery DECWET::EVANS Be a Point Of Light! Fri Feb 07 1997 10:36 20

T.R	Title	User	Personal Name	Date	Lines
394.1	disaster recovery	DECWET::EVANS	Be a Point Of Light!	`Fri Feb 07 1997 10:36`	20
	in the addendum, there is a section about disaster recovery... that is, recovering the /nsr portion. This is known as a Primary Disk, since it had the /nsr tree on it, and it is the indexes that allow NetWorker to do it's stuff. to recover the /nsr tree on the NetWorker Server, one is expected to use recoverindex. To recover the various client index files in the /nsr tree, one is expected to use recover. Yes... to simplify this we recognize that using tar (or dump/vdump) will be fine to reconstitute a /nsr tree... usually, customers do NOT do both NetWorker backups, AND dumps, so if you recover an /nsr tree using tar it would be "out-of-date" relative to the saves done recently (since the tar) and then one would have to do the same recover/recoverindex operations to get back the NetWorker indexes as of the latest save (if that was important). Also, of note is that the most lengthy part of a disaster recovery of the /nsr tree (I have found) is looking up the server's index saveset ID!! which is why we ask people to keep that printout around - otherwise, you wait for scanner to find it for you...

in the addendum, there is a section about disaster recovery... that is,
 recovering the /nsr portion. This is known as a Primary Disk, since it
 had the /nsr tree on it, and it is the indexes that allow NetWorker
 to do it's stuff.

to recover the /nsr tree on the NetWorker Server, one is expected to use
 recoverindex. To recover the various client index files in the /nsr tree,
 one is expected to use recover.

Yes... to simplify this we recognize that using tar (or dump/vdump) will
 be fine to reconstitute a /nsr tree... usually, customers do NOT do both
 NetWorker backups, AND dumps, so if you recover an /nsr tree using tar
 it would be "out-of-date" relative to the saves done recently (since the tar)
 and then one would have to do the same recover/recoverindex operations to
 get back the NetWorker indexes as of the latest save (if that was important).

Also, of note is that the most lengthy part of a disaster recovery of the /nsr
 tree (I have found) is looking up the server's index saveset ID!! 
 which is why we ask people to keep that printout around - otherwise, you
 wait for scanner to find it for you...