[Networker] reusing clone volumes without affecting original savesets

Hey all,

Our organization has tended to keep only a limited number of clonesavailable for DR usage, and I think we've been going about it the wrongway (now that I understand about cloned saveset retentions). Afterlooking through archives, I seem to think I see a workaround suggested,but I wanted to see if this is something that others do with currentversions (I'm on 7.4.4) of networker.

Intended outcome: Reuse clone volumes without affecting savesetretention on the original savesets.

Where before we had been forcibly recycling old clone volumes (which Inow realize will mark the original savesets recyclable), it appears thatif I simply delete the clone volume from the indexes and media db, thenit will leave the original saveset retention as-is and I can insert thevolume into the jukebox and networker will pick it up as a new volume,write a new label to it, and proceed as usual. Or perhaps I will need tomanually label these volumes since they have valid NW labels already?

Input on this solution or any other workarounds (preferably not themanual recycling of backup pool volumes as EMC recommends as that wouldbe a lot more administrative overhead) is greatly appreciated.


Regards,
Greg

-----
Greg Etling <getling AT stern.nyu DOT edu <mailto:getling AT stern.nyu DOT edu>>
Systems Administrator
Stern IT Enterprise Operations
NYU Stern School of Business

-----

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