Backup Central

Dears,



I suspect I hit a bug in following context :



Actually, I am still at 7.5.3.2 on Windows x64 2008 R2.

Yes, I should go to 7.6.x.x soon …



The bug I suspect :



IF ALL OF THESE CONDITIONS ARE TRUE :

- When group has “auto-clone” enabled,



AND



- when selected group target clone pool has pool

retention filled in (to apply a longer retention

than backup copy),



AND



- when backup pool has NO pool retention flagged in,



THEN backups issued by the savegroup and that succeeded

are correctly cloned **BUT** clone pool based retention

is applied on both saveset copies in way of just

clone copy.



As far as I know, it should only apply clone pool retention

change on saveset copies written to that target clone pool.



Am I thinking correctly ?

Anyone has met same problem ?



Thanks



Th





Kind regards - Bien cordialement - Vriendelijke groeten,



Thierry FAIDHERBE

Backup/Storage & System Management



LE FOREM

Département des Systèmes d'Information

Direction Infrastructure



Boulevard Tirou, 104 Tel: +32 (0)71/206730

B-6000 CHARLEROI Mobile: +32 (477)/995319

Fax: +32 (0)71/206199

BELGIUM Mail : Thierry.faidherbe<at>forem.be





via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

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


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER