> We have some old clients that are still listed in the client nwadmin GUI
> listing, but they're no longer being backed up and have not been for
> quite some time. They are not currently members of any groups. However,
> I notice when I go out to the server and I look at the date of the files
> under /nsr/index/client, I see one or more files that have dates that
> are far more recent than I would expect. I have a theory about this but
> wanted to check.
>
> 1. Is this behavior because the client is still listed in the client
> listing and has not yet been removed?

Depends.  Files may be being updated as file indexes expire.  Could that
be happening?

> For one particular client, I ran the following command to determine that
> the last time the client was backed up was like 04/25/03 (mminfo -s
> server -vq 'client=clientname' and sorted the output on the date). This
> makes no sense though given the dates below.

[snip]

> and here's the result of ls -lt db6:
>
> ./db6:
> total 56
> -rw-------   1 root     root         108 May  4 16:07 v6hdr
> -rw-------   1 root     other          0 May  4 16:07 v6journal
> -rw-------   1 root     other          0 Apr  5  2001 v6hdr.lck
[snip]

> It would appear that v6hdr and v6journal were recently updated. Why???
> Is this normal? Perhaps this happens as long as the client still exists
> in the nwadmin listing and/or is still listed in a group even though the
> group is not active?

Probably.  Just running an 'nsrck' seems to update the files on my
machine.

> 2. Which files under db6 should we expect to change and how often?

Hmm.  Well, from your observations, those two.  But why are you asking?
Does it matter that some of them are updated periodically?  Is this
causing a problem?

> 3. If you delete a client and then you re-create it later, but you still
> have the old index for that first client instance stored away somewhere
> else, is there a way, looking at the files under the old index, that you
> can determine when the last time that client instance was backed up?
> Which files under db6 will yield this information?

The best you could do would be to find the last backup in the index,
perhaps with 'nsrinfo'.

> Here's where I'm going with all this. I have these older client indexes
> stored away and I'd like to rename them according to the last time that
> instance was backed up. This avoids confusion with other similar named
> indexes we might create later and/or store away. So index =>
> index.MMDDYY. I thought I could look at the most recent date for files
> under index/db6 , but I'm confused about what signifies what if
> anything. Querying the media database might not help if the given client
> was added, removed, added again, etc. or in some cases there are no
> entries in the database because all savesets for client are gone.

If all the savesets in the database are gone, then there's nothing
useful in the indexes either.  You might as well nuke it.

Without corresponding info in the media database, stale information in
the index database would be worthless.


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

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=