What version are you running? I believe the behavior of the
browse/retention time changed somewhere between v7.2.x and v7.4.x. I
*think* it is supposed to match the client's policies in the newer
versions.
-Teresa
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Werth, Dave
Sent: Wednesday, May 27, 2009 4:32 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Index vs. saveset browse/retention policies
Don't the indexes take on the browse/retention policy of the NetWorker
server they are written on, not the systems they back up? Of course the
contents of the particular index are directly related to the
browse/retention policy of the client but the index itself relates to
the server. At least that's the way I understand it.
Dave Werth
Garmin AT, Inc.
Salem, Oregon
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Tim Mooney
Sent: Wednesday, May 27, 2009 1:25 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Index vs. saveset browse/retention policies
In regard to: [Networker] Index vs. saveset browse/retention policies,
Len...:
> Here's the scenario --
>
> Our clients "A" through "W" all have the same browse and retention
> policies (5 weeks for both). Clients "X" & "Y" back up to their own
unique
> pool and have much shorter policies (1 week). However, X & Y's indexes
> apparently have the majority's longer policies: The volumes containing
X &
> Y aren't becoming recyclable when X & Y's savesets expire, but rather
when
> their indexes expire much later.
>
> For example, here are a couple of lines from mminfo :
>
> volume client name completed browse
retent
> 001703 backup-srv index:X 05/20/09 06/24/09
> 06/24/09
> 001703 X C:\ 05/20/09 05/27/09
> 05/27/09
>
> As you can see, the savesets themselves expire on time, but the
indexes
> take much longer, therefore holding the volumes non-recyclable.
They're
> all in X & Y's own pool, BTW. I can only guess this is because the
backup
> server's client (via which indexes are saved, presumably) is not
subject
> to X & Ys' policies, but rather the longer ones.
I think that's exactly correct.
> Is there something obvious I've overlooked? Can I somehow force X &
Y's
> indexes to be subject to the shorter policies? Or is this just the way
it
> is?
Sure, nsrmm will do that for you. Look at the last usage synopsis in
the
man page (or PDF docs of the man page, since it appears you may be on
windows). You want the -w and -e options, as well as the saveset ids.
Tim
--
Tim Mooney
Tim.Mooney AT ndsu DOT edu
Enterprise Computing & Infrastructure 701-231-1076
(Voice)
Room 242-J6, IACC Building 701-231-8541
(Fax)
North Dakota State University, Fargo, ND 58105-5164
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
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient. If you are not the intended
recipient, please be aware that any disclosure, copying, distribution or
use of this e-mail or any attachment is prohibited. If you have received
this e-mail in error, please contact the sender and delete all copies.
Thank you for your cooperation
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
|
