Index size Zero\Networker 7.1.1_rtm-Build 277

[fazil1]

Hello,
Baffled by some clients on my Windows 2k server shows index size 0, % used 0.
History: Problem first appread when i repartitioned the existing server, moved NSR directory to the Network, updated Networker from ver 7.1 to 7.1.1 as above. New installation was in Same partition with Same driv letter.
I have over 100 mixed clients, NT, Win2k.
on Proliant ML-530.
Now i have run NSRCK -L6 and NSRIM -X without any errors.
every time i cross check index it reverts to its correct size, however, the problem reappears after Networker services are restarted, may even effecting new clients, i recreated some of the clients to fix it.
NSRLIC output indicated some of the clients may not be in its list (ones that are having zero index).
My licences are adequte and uptodate, more then what i need.
Any one had similar problem, please provide email or Phone if you need more details, i will call you .
One other thing, nsr host partition size changed form over 150 GB to 256 GB, my indexes are no more then 10 GB, this should not have any thing to do with this.
I have double check the permisions on the NSR and Index directory.

 

[605]

To my knowledge NW never supported a networked NSR directory, it must be on local devices.

If clients disappear from the nsrlic output, this means that they "are not known at all":
- once configured they should appear as "defined"
- with the first backup they become "connected2

So one it had been configured, it must exist.

 

[fazil1]

Little confusion, i created, NSR directory is Local on E drive as it existed on the server before,i just copied the nsr to Network so i can copy it back on to the server.
I have reset the permisions on the Index and nsr directory to allow administrators, system will full control, because when i copied the nsr dir to Network the permision has everyone full control on Legato directories.
I have attempted to delete the index, create it with nsrck-L6, this created index ok, However since i wanted ability to restore the older files, i ovwerwrote it again with copy i created before, restarted Networker services--Same result, although you can cross check index and the size reappiears, it disaapres or becomes zero once the services are restarted, since the backup from today have not run, it might be the reason for connected and defined clients, i will waite till tomorrow to double check NSRLIC output again, any other clues ?

 

[605]

Sure you can backup the nsr directory, people do this all the time. However, i never changed the rights - no matter which OS.

However, you should not separately copy (or mix) the file and the media index. If the save set info (in the media index) does not exist any more, NW will not recognize earlier file index information.

 

[fazil1]

The reason i copied the files (NSR) directory to the Network becasue i was repartioning the server to crete more disk space and did not wanted to depend on restore via tape, while copiying to the network file permisions changed according to where it was copied, so when i laid the NSR directory back on the Networker server, i had to reedo the permisions to what they were before.
I am waiting for Legato tech support today to see what they have to say regrading this, i am thinking that perhaps during the conversion from 7.1 to 7.1.1 some of the indexes were not converted cleanly or there is a correption somewhere within Networker, that i dont find it yet, have you seen this 7.1.1_rtm_Build277 ever, i dont remember having the extra letters in the builds before, i did download correctly version for windows directly form Legato.
I will have more on this later in the day.

 

[605]

To my knowledge, there is no index conversion when you update from 7.1 to 7.1.1.

I am rather sure that 'rtm' is just short for 'ready to manufacturing'.

 

[fazil1]

Does that mean it's still a Beta ? Its been out i believe since Jan-04

 

[605]

No. As long as you do not think that such complex software is always under development somehow ;-)

 

[Iago77]

Hello,

a few days ago We've installed this new version. It ocurred the same error, the command you must use is

# nsrchk -L6

You have to wait several minutes until you can see the correct sizes from the indexes.

Good luck!

 

[Iago77]

Excuse me,

# nsrck -L6