More about the suspected bug :

In fact I believe guilty to be nsrclone's -y option:

According doc :
Sets the date (in nsr_getdate(3) format) when the cloned data will become
                                              +++++++++++++++
recyclable. The special value forever is used to indicate that a volume that
never expires (i.e. an archive volume) must be used. By default, the server
determines this date for the save set based on the retention policies in
effect. This option allows overriding the existing policies. See also nsrmm
(1m) and its -S & -e options.


But all copies of the SSID have retention policy overridden.


Th

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