Re: [Networker] index default browse and retention

Subject:

From:

Davina Treiber <Davina.Treiber AT PEEVRO.CO DOT UK>

To:

Date:

Wed, 19 Mar 2008 08:51:19 +0000

David Dulek wrote:

I am now using 7.4.1 SP1 and ...
I am pleasantly surprise to let everyone know that "apparently" that behavioris no longer true. My index saves "appear" to have the same browse time asthe clients that were backed up.
I am in the process of changing all the clients to have different browse andretention policies based on the group that they are in so I didn't know thatchanged until today's backups ran. ( I had to create 3 client definitions,one for each of the groups they are in. I assume this is still true since Icould not find a browse/retention policy on the groups )

Whoa - 3 client resources for each client? Try to avoid that, you willhave a very difficult system to manage.

With 7.4.1 you can set a retention policy on the pool, and this is VERYuseful. Combine this with schedules set on groups rather than clientsand you can go back to a single client resource for each client. I haveimplemented this strategy on two customer sites recently and it worksjust great.


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

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Networker] Determine how long a job ran for ?, Michael Nored

Next by Date:

Re: [Networker] index default browse and retention, MIchael Leone

Previous by Thread:

Re: [Networker] index default browse and retention, David Dulek

Next by Thread:

Re: [Networker] index default browse and retention, MIchael Leone

Indexes:

[Date] [Thread] [Top] [All Lists]