Actually I think I had it backwards, it's browse which is non-unique -
it's limited to be less than or equal to the shortest of any retentions
of clones

from nsrmm:

     -w browse time
          Specifies the browse time for the  specified  save  set
          (supplied with the -S option).  Note that once the save
          set becomes recoverable, the browse  time  may  not  be
          changed.   The  browse  time should be specified in the
          format   that   is   acceptable   to    the    function
          nsr_getdate(1m).   The  browse time has to be after the
          insert time in the save set record, but  it  cannot  be
          after  the  retention  time.  If  the option -e was not
          used, the existing  retention  time  in  the  save  set
          record  is used for comparing with the specified browse
          time.  See under the option  -e  for  more  details  on
          retention time.

     -e time
          When used in conjunction with the -S  option,  it  sets
          the  clone  retention time of the specified save set or
          save set clone instance.  The retention time should  be
          specified in the format that is acceptable to the func-
          tion nsr_getdate(1m).  If a  clone  identifier  is  not
          specified  all  clone  instances  will  be updated with
          specified clone retention time. The save set  retention
          time   will   reflect  the  longest  recoverable  clone
          instance retention time.  It is possible  for  a  clone
          instance  to  have  a  retention  time less that browse
          time. However, the save set retention time may  not  be
          set  such  that  the  save  set would become recyclable
          while it is still browsable.  Refer to  the  -w  option
          for more details on browse time.  When used in conjunc-
          tion with  volumes,  the  volume  labeled  will  be  an
          Archive volume if the value of time is forever (Archive
          volumes mean that the volume label never expires).  Any
          other value of time are not applicable to a volume.
 

That's why it wouldn't work for us, we wanted one clone to expire after
a month, but another to be _browseable_ for 2 years.  So I had to make
them all browseable for 2 years and manually delete some.

My apologies!


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Landwehr, Jerome
Sent: Monday, April 14, 2008 9:34 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] need to change clone id expiration date


That's not how it was working when I gave up on cloning - I use 7.3.3
now - perhaps that was 7.3.2 then?

Frank, Can you do a report on a saveset and it's clone to demonstrate?

something like this:

mminfo -q ssid=[some saveset which was cloned] -r
"ssid,cloneid,sscreate,ssbrowse,ssretent"


thanks in advance
Jerry

-----Original Message-----
From: Francis Swasey [mailto:Frank.Swasey AT uvm DOT edu] 
Sent: Monday, April 14, 2008 9:24 AM
To: EMC NetWorker discussion; Landwehr, Jerome
Subject: Re: [Networker] need to change clone id expiration date


On 4/14/08 8:31 AM, Landwehr, Jerome wrote:
> _only_  browse times can be unique, retention times are all the same
for
> every clone of the same SSID
> 
> You'll notice in the man page for nsrmm they speak of different browse
> times for clones, but not different retention times for clones

If you look at the nsrclone command, its -y parameter sets the retention

time of the cloned copy of the SSID's.  So, it appears that retention 
times are unique per cloneid (and that's the way I find it is working in

practice with 7.3.3 here).

Frank

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

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