Hi, Stan.  Thanks.

I've considered this.  The issue would be to identify
the savesets created since the last clone run because
a volume clone would make no sense - I'd keep cloning the same
stuff from last night and the night before, etc. if the source
volume was not full yet.  Identifying the individual savesets
would be very critical for a saveset clone.  One missed saveset
could be disastrous.  I'd ultimately need to leave the original tapes as
appendable or else I'd be in the same trouble as now, with the
only difference that I still had the originals on site (that's good) but
have "wasted" some tapes and tape drive availability on a clone (that's a bit 
bad).
Backing up all night and cloning all day is not a pleasant prospect.
Dealing with planned or unplanned downtime would be a mess.  There would
be no possibility to catch up.

Maybe I don't understand exactly what you had in mind.

Thanks again.

Jon

-----Original Message-----
From: Stan Horwitz [mailto:stan AT temple DOT edu]
Sent: Sunday, July 25, 2004 3:14 PM
To: Legato NetWorker discussion; Eichelberger, Jon
Subject: Re: [Networker] Utilization of Tapes




On Sun, 25 Jul 2004, Eichelberger, Jon wrote:
>
>So, any ideas?

It seems to me, you might want to consider revising your off-site
policy so that you do cloning and then send the copied tapes off
site. You could clone several tapes to fewer cloned tapes. The
benefits of this is that you would be sending tapes off-site that
have more data on them and  you would have the original tapes
on-site for use in the event that a quick restore is needed.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=