The client resource does not directly control the retention policy
of its associated indexes... yet.
I thought this had been fixed in 7.x, but when I queried support
they informed me that this was still a known issue, and it
is slated to be officially fixed in the 7.5 release of networker.
Below are the details I was provided by Legato,
Rodney
legato28802
Fact: NetWorker
Symptom: Volumes are not recycleable
Symptom: Indexes have different policy than the savesets
Symptom: Index information does not get removed based on the browse and
retention policy of the client
Symptom: Browse and Retention policy settings from client are set at the
server
Cause: Browse and retention policies of the client file index are
different from the client's saveset policies, as the indexes are owned
by the NetWorker server. If you have more than one instance of the
NetWorker server and NetWorker server is not a part of the group that is
running the backup then the browse and retention policies of the client
file index will follow this Criteria
1) Locate all the client resources which belong to the same group that
the save set belongs this set of client resources, apply the following
rules to get the best match. If no client belongs to the save set?s
group, or if the group no longer exists, or if the saveset is from
earlier than version 5 (when group information was not recorded in the
save set),
apply rules to all the client resources to get the best match.
2) Locate a client resource explicitly listing the save set. (ie
index:client.domain.com) If more than one client resource set, choose
the client resource with the longest policy.
3) Search for a client resource listing the save set "All". If more than
one client resource set "All", choose the client resource with the
longest policy.
4) Find the client resource listing a save set with the most common
prefix (longest) of the set. If more than one client resource lists the
save set with the most common prefix, choose resource with the longest
policy.
5) Among all of the client resources, choose the client resource with
the longest policy.
Also check command line reference for nsrim under RETENTION AND BROWSE
POLICY
Fix: <a href = "javascript:history.back()">Click Here To Go Back</a>
Create a "Skip" schedule with "skip" level for all days. Create a client
resource for the NetWorker server with "skip" schedule and modify the
browse and retention policies to match the policies of the NetWorker
client. Add this NetWorker Server client resource to the group that is
running the backup, so that the browse and retention policy of the
client file index will be of the NetWorker Server that is in the group.
If several NetWorker client resources are created with different browse
and retention policies, create as many client resources of NetWorker
Server as the number of NetWorker client resources, and modify retention
policies for each of them to mach retention of the clients.
An RFE LGTpa35740 has been filed to request that Networker Server takes
the index policies set backed up client instead of taking the policies
of the server.
This RFE LGTpa35740 has been fixed in NetWorker future release which is
NetWorker 7.5
Darren Dunham wrote:
I'm not sure what you're saying. The retention policy is controlled by
the client resource. If the retention isn't right, that's where it has
to be changed.
Is there something wrong with Anuj's response?
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
