Re: [Networker] Retention policy on clone pool

Today at 9:40am, Thierry FAIDHERBE wrote:

Effective results:
In Backup pools,
        all NOT CLONED backups to have retention set as 5 Weeks,
        all CLONED backups to have retention set as 10 Weeks,
In Clone pool, cloned copies set to 10 Weeks.

Am I wrong somewhere ? Shouldn't overrulled pool retention
policy to only apply on SSID/Clone id level ?

What's goal of pool's retention policy in such a case ?
My goal was to assign savegroup-based autocloned SSID a longer
retention period the normal backup copy seen now SSID copies
to support different retention date ...

Bug or expected behavior ... ?

BUG! I worked with EMC for hotfixes for this for both 7.4.3 and 7.4.4,it is finally fixed in 7.4.5.2 for me.

Be aware that after you get the fix installed, the BACKUP volumes thatshould have expired, will go to "undef" instead of "expired" status.You'll have to manually recycle them to get them usable again.


--
Frank Swasey                    | http://www.uvm.edu/~fcs
Sr Systems Administrator        | Always remember: You are UNIQUE,
University of Vermont           |    just like everyone else.
  "I am not young enough to know everything." - Oscar Wilde (1854-1900)

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