Re: [Networker] Can an old index still be used?

Hi There,

Very similar to the "merging server indexes" query.

As far as I am aware (meaning you might need to have a pinch of salt handy)
Client indexes as well are stored against the name AND very important)
against the client-id.

As a pre-caution, I would always save this client identifier and when I
re-create this client (that if you know you might be re-creating it) use the
client id. Then restoring old indexes (perhaps from tape) etc doesn't pose a
problem. (I have done this before).

If you just create a new client with the same name as far as NetWorker is
concerned it ISNT the same client.

Having learned this the hard way I am normally meticulous when dealing with
clients / ID's and server names (etc etc etc).

Regards,
Riaan

-----Original Message-----
From: George Sinclair [mailto:George.Sinclair AT NOAA DOT GOV]
Sent: Friday, May 14, 2004 6:26 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Can an old index still be used?


Hello,

Two questions here on moving indexes around.

When you remove a client from the client listing (lets say 2 month
browse policy), its index still remains under /nsr/index on the primary
server .. okay, right.

1. But if you then rename the index and later re-create the client, can
you remove the new empty "template" index and replace with the original
index and then be able to browse back 2 months, beginning with the date
the first instance last backed up or left off at?

Seems like you should be able to do this, but there is the resource
identifier that shows up under nsardmin for NSR client type. If the
primary server recorded the new resource identifier when the client was
re-created would the old index still work? Maybe old index contains old
resource id so mismatch might occur?  Just was wondering if keeping the
old index around for a while might be prudent so that if you needed to
use nwrecover (browse) sometime after client was removed, you could
re-create client, and move old index into place which might be faster
and easier than merging in an older copy of the index using uasm.

2. Same scenario, but the new client index does have data in it. If you
rename it and move the original back, recover your data, can you then
move new one back in place and NetWorker will be okay with that and
won't be the wiser?

George

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

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.687 / Virus Database: 448 - Release Date: 5/16/04


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.687 / Virus Database: 448 - Release Date: 5/16/04

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