> If you have multiple nsr client resources for the same client, and you
> run a level full against one of them then I assume:
>
> A. The only portion of the server's client index path that will be
> updated will be the files that pertain to the given resource while the
> other pieces/parts that correspond to the other resources will not be
> touched, correct?
I believe that is correct. Although there's not really much of anything
"updated". Each file backed up adds an entry into the file index with
the location on the media along with the information about the file
(path, metadata). 'nsrim' or 'nsrmm' can go in and purge entries
manually or based on browse time.
> B. However, when NetWorker backs up the client index it will back up the
> entire /nsr/index/client directory to tape and not just the part of the
> index that was affected by the given client resource?
Correct.
> What about incrementals?
Indexes don't do incremental backups. They'll be upgraded to level 9.
So I presume you'll put all changes since the last lower level on tape.
Normally this is exactly what you need for the recovery information. If
you have overlapping groups going to different pools simultaneously,
then I think you could cause some index information to be sent to a
different volume than the data that it references, but I've never run
into that in practice.
--
Darren Dunham ddunham AT taos DOT com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
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
|
