Our solution is to _not_ run the index backup with the savegroups at all
(Group option No Index Save - same as 'savegrp -I [group]') and have
separate client resources for the index backups - one for daily onsite
backups which lasts a week and another for offsite backups which match
the offsite backup's retention. The daily onsite index backup doesn't
need to match the daily retention because you'll always get the next
index backup tomorrow which is all inclusive
So we do a daily job for the short term index backup (Save Group O -
same as 'savegrp -O [sgo group]') so we call the pool SGO. You have to
use cron to fire this off because there is no GUI option to save _only_
the index. And after the long term retention backup we do the index
backup with long term retention manually
This way any index recovers will all be from one tape, not all over the
place - if you have more than a handfull of tapes in a set, you know how
long an index recover will take if it has to scan every backup volume
for the scattered chunks of index!
Also, this way, it's much easier to tell what your index retention will
be since you define it in the SGO client resources
HTH
Jerry
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of David Dulek
Sent: Tuesday, March 18, 2008 10:26 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] index default browse and retention
I was afraid that was the case. I was just hoping someone had a
solution.
Since the schedule is set on my groups, your "solution" would be a pain
in
the tape library to implement here but not impossible.
On Tuesday 18 March 2008, Teresa Biehler wrote:
> The default browse and retention time of client indexes depends on the
> setting for the NW server. If the NW server has a variety of browse
and
> retention times and is not part of the group that the client is a
member
> of, the longest NW server browse and retention times are used. For
> example:
>
> Group names: 8pm-daily, 8pm-weekly, 8pm-monthly, 1am-daily, 1am-weekly
> and 1am-monthly
>
> Daily backups are kept for 1 week, weekly backups for 1 month and
> monthly backups are kept for 1 year.
>
> 1) ClientA is in the 8pm groups and the NW server is in the 5am groups
> only. Then ClientA's index has a browse and retention time of 1 year
> for all backups.
>
> 2) If, on the other hand, both ClientA and the NW server are in the
5am
> groups, then ClientA's index will have the same browse and retention
> time as the NW server does within the group.
>
> So, if you want ClientA's index backups to have the same browse and
> retention time as ClientA's data, make sure the NW server is a member
of
> all groups. If the schedule is "skip", this will not result in
multiple
> backups of the NW server. It will, however, result in multiple
> bootstraps. Instead of printing the bootstraps through the NW
> notification (the default), we have changed our notification to write
> the bootstrap to a file. Once a day, we print a bootstrap via a
> separate script.
>
> Enjoy!
> Teresa
>
>
>
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On
> Behalf Of David Dulek
> Sent: Monday, March 17, 2008 4:52 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] index default browse and retention
>
> If I have 4 client definitions for my server
> one with 1 week browse and retention
> one with 5 week browse and retention
> one with one month browse and retention, and
> one with one year browse and retention,
>
> What is the browse and retention of client indexes I backup with this
> server
> when it is not in the group I am backing up?
>
> And if you happen to know, how do I affect that "choice"?
>
> 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
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
|
