Re: [Networker] Problem with Expiration and retention dates

Diane,

Not at all - the schedule associated with the client dictates the level
of backup of the index.  The browse/retention time of the server
dictates the browse/retention time for the index. 

In our environment we do daily, weekly and monthly backups.  Each is
done within a separate group with a different retention.  The server is
a member of each group to prevent all the index backups from having the
wrong retention time.  Here's a sample of one of our savegroup
completions to show that the index on the client does get backed up even
when the NW server has a schedule of "skip".

NetWorker savegroup: (notice) morning-daily completed, total 2
client(s), 0 Hostname(s) Unresolved, 0 Failed, 2 Succeeded. 
Start time:   Wed Apr  5 09:05:00 2006
End time:     Wed Apr  5 09:32:21 2006

--- Successful Save Sets ---

Successful Save Sets written to verified media noted with "V" in first
column.

V app: /app/u01             level=full,     13 GB 00:22:42   5943 files
V app: /app                 level=full,      3 KB 00:02:36      4 files
V NWsrv: index:app          level=full,    228 MB 00:00:34    613 files

  NWsrv: /                      level=skip,      0 KB 00:00:00      0
files
  NWsrv: index:NWsrv              level=skip,      0 KB 00:00:00      0
files
  NWsrv: bootstrap              level=skip,      0 KB 00:00:00      0
files


An unfortunate side effect of this set-up is that a bootstrap report is
generated for each group.  Instead of printing each of these, we have
the bootstrap notification send the reports to a file and then run a
daily job print just one copy.

Thanks.
Teresa



-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Diane Rolland
Sent: Wednesday, April 05, 2006 9:34 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Problem with Expiration and retention dates

Teresa Biehler wrote:
> Option 4:
> 
> Add the NW server to the group with the retention time you want.  So
> that you don't back up the NW server an extra time, set up this
> instance to do a level "skip" each day.  
> 
> -Teresa
> 
This is interesting; So, I need to create a schedule called "Skip" and
assign it to the instance of the Networker server that I will add to
this
new group?

Doesn't this effectively keep the indexes from being backed up at all?

I'm having trouble understanding the index backups.

Thanks for any advise.
Diane

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
wit 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
wit 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