EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on 
03/19/2008 04:51:19 AM:

> David Dulek wrote:
> > I am now using 7.4.1 SP1 and ...
> > 
> > I am pleasantly surprise to let everyone know that "apparently" 
> that behavior 
> > is no longer true.  My index saves "appear" to have the same browse 
time as 
> > the clients that were backed up.
> > 
> > I am in the process of changing all the clients to have different 
> browse and 
> > retention policies based on the group that they are in so I didn'tknow 
that 
> > changed 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 I 
> > could not find a browse/retention policy on the groups )
> 
> Whoa - 3 client resources for each client? Try to avoid that, you will 
> have a very difficult system to manage.

I have 2 client definitions for some of my clients. Here's why - these are 
MS SQL servers, and we use the SQL Module to back them up. So what we do 
is: FULL backup on the SQL DBs every night, and only backup the rest of 
the filesystem of those servers (which is pretty much static) only on the 
weekend. So I have 1 definition for SQL DBs, and one definition for ALL, 
for these clients. The former are in a group which is scheduled for FULL 
every night, and the other definitions in a group which is only FULL on 
Friday night.

Been working out well for us. Currently on 7.4.1 for Win2003.

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