Re: [Networker] Retention policy on clone pool
2009-12-04 06:48:39
Oh... you should also know that the fix you need is:
LGTsc24106: Volretent for the backup volume has been changed to the
ssretent of the save set on the volume that is extended after cloning,
resulting in a longer retention policy.
Frank
On 12/4/09 6:42 AM, Francis Swasey wrote:
My plan at present is (if we decide to stay with NetWorker) to skip
the 7.5 release and go straight to 7.6. However, because EMC does
overlapping development, there are always bugs in the new version that
you got fixed in the old version and EMC hasn't figured out that they
need to forward port the fixes -- until someone calls in and complains
about the same bug all over again. Even then if you don't get the
right support person, you're going to waste at least a week of your
life dealing with their script they were given to follow -- because
they don't know how the product even works.
Frank
PS -- Yes, since I've been dealing with multiple problems and have not
had a single day in the past three plus months that I haven't had to
deal with someone at EMC about them -- I'm very burned out and grouchy.
F
On 12/4/09 6:16 AM, Thierry FAIDHERBE wrote:
Thanks for the info.
I am still at 7.4 and realy afraid of
upgrading .... bugs of 743/744, multi 745 releases,
75/751 ... now 76 ... where to go ?
Cheers
Th
Kind regards - Bien cordialement - Vriendelijke groeten,
Thierry FAIDHERBE
Backup/Storage & System Management
LE FOREM - Administration Centrale
Département des Systèmes d'Information
Boulevard Tirou, 104 Tel: + 32 (0)71/206730
B-6000 CHARLEROI Fax: + 32 (0)71/206199
BELGIUM Mail : Thierry.faidherbe<at>forem.be
-----Original Message-----
From: Frank Swasey [mailto:Frank.Swasey AT uvm DOT edu]
Sent: vendredi 4 décembre 2009 11:52
To: EMC NetWorker discussion; Thierry FAIDHERBE
Subject: 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 that
should 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)
--
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
|
|
|