Unsolved
This post is more than 5 years old
45 Posts
0
1226
Indices for Networker 8 AIX client gets deleted after NSRIM runs.
Hi All
We have developed a strange problem , a certain AIX client with Nw 8 installed is having problems with recoveries.
When we open networker user we observed the "No Index Found error", on lot of brainstorming we figured that the indexes get deleted whenever NSRIM runs, whether Automatic or Manually.
Tried restoring the indexes but it throws strange errors or completes a restore with 0 files restored.
I need urgent help here as we are required to perform several FLR for this client
Hrvoje Crvelin Ur take on this would be highly appreciated, as we look for a speedy resolution.
Has this issue been experienced by someone else too ?
CarlosRojas
1.7K Posts
0
May 15th, 2014 00:00
Hi Abishek,
My first thought is related to the following 2 aspects:
1.- What is the browse policy set for those clients?
2.- Potential client ID issue or nested indexes.
Can you please run the following command and attach it here?:
nsrls
Also, what is the retention set for those clients?
Thank you,
Carlos
CarlosRojas
1.7K Posts
0
May 15th, 2014 00:00
Thank you Abhishek,
Can you see the index saveset? If so, what is the status of that saveset?
Are the indexes saved on any particular pool? If so, is there any special retention set for that pool?
What is the version of NW server and NW client?
Thank you,
Carlos
DataProtectxr
45 Posts
0
May 15th, 2014 00:00
Browse and Retention Policies are both set to 30 Days
DataProtectxr
45 Posts
0
May 15th, 2014 00:00
The Status is recoverable :
No specific pool for these, gets saved along with the group.
Nw Server : NetWorker 8.0.1.1.Build.132 , Win2008R2
Nw Client : NW 8.0.1.1.Build.132 , AIX
DataProtectxr
45 Posts
0
May 15th, 2014 00:00
Thanks for your quick response Carlos Rojas .
O/P (nsrim has already run) :
nsrls fgbt24
F:\Program Files\Legato\nsr\index\fgbt24: 0 records requiring 0 KB
F:\Program Files\Legato\nsr\index\fgbt24 is currently 100% utilized
Also , i do-not see any nesting of the CFI's or any duplication as well.
Just a single CFI with the client name fgbt24 and it does not contain any nested indexes.
CarlosRojas
1.7K Posts
0
May 15th, 2014 01:00
Hi Abhishek,
I would strongly recommend you to upgrade to the latest version, as there are few known issues with 8.0.1.1
In order to allow you to do the FLR, did you try running nsrck -L7 fgbt24
If didn't work then scan the saveset:
scanner -v -im -S SSID
Also what is the status of the savesets you want to recover? I don't think the indexes get deleted, as the saveset is still there.
I suspect you could be also facing some issues with the media DB, but that should be dealt by support over a new SR.
Thank you,
Carlos
bingo.1
2.4K Posts
0
May 15th, 2014 01:00
No some guesses:
- 'name resolution' issues
in /nsr/index verify whether a similar host exist (for example with FQDN).
Verify that the short and the FQDN are listed in the client's Aliases field.
- The index files may have been deleted
in /nsr/index/fgbt24 verify that it is not empty.
- the index directory has been changed in the interim
the index has been moved but the client's index path has not been adjusted.
- the index directory has not been changed
but the client's index path has been misconfigured.
- Recover the index save set and verify where the restore goes to.
This is obviously where the index has been saved from.
Then investigate the issue further.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
May 15th, 2014 01:00
I think you already received enough good input. Starting from scratch, I I would change index folder first:
- cd F:\Program Files\Legato\nsr\index\fgbt24 and do dir /s ; what you should see db6 folder and not any other client name inside like fbgt24.domain for example
- second thing, and most likely, is the name resolution of this client. This may be DNS or hosts or simply configuration. Such examples usually result in mismatch between index and media db records thus nsrim will always removed it from index db. Typical mistake is where loopback address in hosts table contains name of the client for example.
Check clientids with mminfo:
mminfo -avot -q client=fgbt24 -r clientid (they should all be the same and just to be sure check that number against number you have in client resource)