See thread480-922653
Hello.
We've just find another way to "correct" this problem quickly if no time ti install fixes. We have mounted all volumes where there was indexes for this client and re-lauch nsrck -L7 <client>.
To know which volumes are required, see the command which is waiting during the "NSR server <server> busy" error message.
With Unix, we can see savesetID then with an mminfo or with the nwadmin, we found all the required volumes.
The post talks about 7.1.1, we were with 7.2.1, so this probleme is not corrected in this version.
Hello.
We've just find another way to "correct" this problem quickly if no time ti install fixes. We have mounted all volumes where there was indexes for this client and re-lauch nsrck -L7 <client>.
To know which volumes are required, see the command which is waiting during the "NSR server <server> busy" error message.
With Unix, we can see savesetID then with an mminfo or with the nwadmin, we found all the required volumes.
The post talks about 7.1.1, we were with 7.2.1, so this probleme is not corrected in this version.