[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

631.0. "question about cloning" by EVTAI1::POUSSARD () Mon Apr 28 1997 08:22

	Hi,

	A customer does manual cloniong and he clones the entire volume.

	To do that, he needs 2 drives and the cloned tapes must have a 
specific label template attached to a specific clone pool.


	For example, the source tape is labelled FULL.001, and the cloned 
tape is CLFULL.001

	When a customer wants to do a recover of a data located on FULL.001 
and its clone, NSR asks for FUll.001 if FULL.001 is present on the jukebox.

	If FULL.001 is absent, but CLFULL.001 is present, NSR asks for 
CLFULL.001.

	If neither FULL.001 nor CLFULL.001 are present in the jukebox, NSR 
asks for FULL.001. But let's assume we loose FULL.001 , and we don't know 
that CLFULL.001 is the clone, what is the way to find the mapping of the 
labels between source label and clone label ??

	In another way, are we obliged to write on a notebook, the label's 
mapping between source tape and cloned tape, or is ther a way by specific 
commands to find this mapping ?? 



	Thanks for your replies



					Gilles.

T.R	Title	User	Personal Name	Date	Lines
631.1		DECWET::RWALKER	Roger Walker - Media Changers	`Mon Apr 28 1997 12:45`	3
	If you loose access to FULL.001 just remove the volume from NetWorker. The savesets on CLFULL.001 will still be known and CLFULL.001 will be requested for a recover if needed.
631.2	another way ??	EVTAI1::POUSSARD		`Tue Apr 29 1997 06:11`	3
	Is ther another way to find the mapping between original and clone volume, if for example we don't want to erase the source volume label ??
631.3	try mminfo	DECWET::CARRUTHERS	Life gets easier when you realize you can't have everything.	`Tue Apr 29 1997 13:32`	33
	The mminfo man page has an example that might work: mminfo -otc -v -q 'copies>1' This displays a verbose list of the instances of all save sets with more than one copy, sorted by save time and client name. For example: volume client date time size ssid fl lvl name droog.002 mudbone 4/25/97 3:33:12 59 MB 1653 cb full /usr/test droog_c.001 mudbone 4/25/97 3:33:12 59 MB 1653 cb full /usr/test droog.002 droog.zso.dec.com 4/25/97 3:33:13 10 MB 1654 cb full /usr/users/tlc/work/backup_tree droog_c.001 droog.zso.dec.com 4/25/97 3:33:13 10 MB 1654 cb full /usr/users/tlc/work/backup_tree droog_c.001 droog.zso.dec.com 4/25/97 3:34:04 120 MB 1655 cb full /usr/users2/test2 droog.002 droog.zso.dec.com 4/25/97 3:34:04 120 MB 1655 cb full /usr/users2/test2 droog_c.001 droog.zso.dec.com 4/25/97 3:34:04 120 MB 1655 cb full /usr/users2/test2 Looking at the date/time and the saveset id we can identify the clone volumes. Play around with mminfo, it has several ways to get information on savesets and volumes. Also see mmpool.