To follow up on George on this issue.  I am looking for similar information.
I know that you can migrate a networker client name from "whatever" to
"whatever" as long as you save the resource ID and move the directory name
around.  However I was wondering if any one know where NetWorker held the
Resource Identifier after you delete the client from the resource database.

My problem is I have a client that somehow got deleted but still has it's
index directory.  Because I do know what the Client ID is I will have to
re-add it in as a new one?  Anyone know how to find the Client Resource ID?
Is it in the media database somewhere?  Is it in the index directory for the
client?

Thanks,


Chad Smykay, RHCE, LCNA
Systems Storage Administrator
Rackspace Managed Hosting (TM)
210-892-4025 ext 1603
Cell: 210-273-2344

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] 
On
Behalf Of George Sinclair
Sent: Friday, May 14, 2004 11:26 AM
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

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