| Title: | NetWorker |
| Notice: | kits - 12-14, problem reporting - 41.*, basics 1-100 |
| Moderator: | DECWET::RANDALL .com::lenox |
| Created: | Thu Oct 10 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 750 |
| Total number of notes: | 3361 |
Heippa! I was updating the customer's Networker from V4.2A to V4.3 (will be on July Digital UNIX Layered Products CD:s). The updating was because of IPMT (see note 575). Anyway I had a problem when doing update. Somebody else might run into this, so I'll post it here. I shutdown the Networker server, removed the Networker patches and then removed the Networker V4.2A. Shutdown to single-user mode and installed with dupatch the Digital UNIX V4.0A patches, built the kernel and rebooted to multiuser mode. Then I installed V4.3 of Networker. During the installation it does nsrck -F, which does checking and compressing of all client indexes. This lasts very long if client-indexes are big (as they are on this customer site). Everything went fine until it started to do checking of server's own index-file. For some reason after doing checking of index (is very small) it started to do "cross checking index". And there it slept a long time until I figured out that to do cross checking it needs nsrmmdbd, which was not yet started (I was doing installation). What I did was from another terminal window "kill nsrck-pid" and the rest of the installation proceeded successfully. I got networker up and did nsrck -F for the rest of the clients manually. I don't know why nsrck -F wanted to do cross checking for server's index, but this type of possibility is not been taken care with the installation script. Also the installation takes a long time because of nsrck, if there are clients with big indexes (2 Gb or so). What would be the risks if nrsck -F would be done after the installation - not during it? Best regards, Takku
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 729.1 | Why the nsrck -F is done | DECWET::GRAHAM | Mon Jun 02 1997 14:22 | 18 | |
nsrck -F is included as part of the installation procedure because of significant changes in the index code between NetWorker V3.2a and V4.2a. Legato recommended the nsrck -F as a way to ensure that indexes were in good order for conversion from the 3.2x format to the 4.2x format. Since we don't know what a user is upgrading from, the installation procedure always does the nsrck -F. If you're upgrading from NetWorker V4.2a/b/c to V4.3 there is no index conversion, so the nsrck is not critical. It appears that you're correct, that in the case where nsrck -F flags an index for a cross check during installation, nsrck will hang. Thanks for letting us know about the problem; we will look into it. Debbie | |||||