Hi Preston,

Sorry this thread got so long I missed a few posts when trying to catch up.  I 
understand the use of clone-id and ssid, and how clone-id is -1 in a disk 
backup situation.....  clone-id is based on nsavetime so the only way to 
differentiate is by decrementing by -1 for the RO device.  All other cases 
(staging, cloning, etc.) the clone-id will differ according to the nsavetime 
value of when the operational occurred.  Hopefully I now understand this after 
the numerous examples...  thanks!   

Now back to the example and perhaps I can apply the logic from above.  The 
save-set on the full backup volume has a retention of 11/02/09, and a clone-id 
retention of 1/1/2009.  This clone-id retention is for a single instance, the 
instance created during the normal full backup (2 months as specified by the 
client resource).  The clone operation ran after the full backup completed, 
extending the save-time retention on the original volume to 11/02/09.  This 
happened because the second instance (2nd clone-id) had a retention of 
11/02/09... thus the save-set as a whole now has a retention of 11/02/09.  

Hopefully this is correct.  Now the problem:

How can I have a volume expiration based on a 2-month retention policy for my 
full backup volume, and a volume retention for 1-year on my clone volumes.  If 
I understand correctly... the save-set retention is going to be the longest of 
any of the clone retentions.   I hoped to automatically expire media, and 
recycle to other pools when needed.  If the clone retention for the 2nd 
instance of the save-set is 1 year... the whole save-set won't expire...thus 
the volume won't expire until the clone expires.

+----------------------------------------------------------------------
|This was sent by Jonathan.Gill AT uconn DOT edu via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

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