[Networker] To index save or not?
2008-04-09 09:48:23
So all of my backup jobs have "No index save" set as an option; this was
apparently done under advice of EMC, when they originally set us up. Now,
I can understand the reasoning for a separate Bootstrap group and separate
tape; this facilitates ease of DR recovery, so I can get back all of my
clients at once (I think). But why would I *not* want to save the index
with each backup job? Wouldn't having the index make restoring/recovering
from tape easier? i.e., it's easier to do a "scanner -m" rather than
having to do a more time-consuming "scanner -i".
So I'm thinking of changing my job definitions to remove the "No index
save", but also keep my separate Bootstrap group, tape and scheduled job
to run the "savegrp -O" every morning.
Thoughts? Good idea? Best practice? Waste of time? etc
Thanks
--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>
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>
|
- [Networker] To index save or not?,
MIchael Leone <=
|
|
|