Greetings and salutations.

This topic sparked some interesting and quality feedback. Yes, I admit,
I was very confused by this aspect of maintaining NW, not being involved
very long. Plus, I exaggerated on the number of bootstraps I was getting
per day  (I said 300 - sorry, it is only 4, but 3 too many). 

Wow, knowing what I know now, you really must have thought I was mostly
retarded. That is another story....

I would like to summarize some of the things I learned with your help,
some testing, and through documentation, that I did not fully understand
from the beginning. I feel I have a much better handle on it now, but
please feel free to correct me if you think otherwise.

Making sure this topic is well understood is I think a prerequisite for
good DR recoverability, but also a must for normal upgrades.

1) Indexes are not bootstraps, they are separate controllable functions,
and you have to look at it that way when considering the operational
aspect of NW. I don't know why I was thinking any differently.

2) Indexes are either saved in the catalog, or they are not, you decide.
If you want to get an additional copy of the indexes, then perform a
savegrp -O -G (SGO). If you are looking for complete DR copies, then
make sure that group has the NW server in the client list, and make the
SGO the last command you issue in your DR process, and eject that tape.

3) Whenever a group contains the NW server as a client, it will collect
a bootstrap when the group finishes backing up all the clients in that
group. This officially cannot be turned off (although I'm sure there are
ways, but official was the key word there).

4) Since the bootstrap requires a frozen copy of the media DB as part of
the backups it collects, schedule the bootstrap in a quieter window.


Probably seen this a million times, but I got the impression I may not
be the only one that was confused, so maybe this will help. It helped
me.

Regards.

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