I recently upgraded our NSR backup server to Legato v5.2. It's running on
DU 4.0D (patch kit 2), on an Alpha 1000A, to a DLT drive. Clients are
itself, two NT servers (one with Exchange BusinessSuite module), and three
Suns.
For the past several backups, the entire backup process seems to get
"wedged" on an 'nsrck -M NT-server' process. You can't even do an nsrwatch
or 'nsrmm -C' until you kill that process, then the backup proceeds
normally. However, killing an nsrck (which you have to kill -9) doesn't
seem like a terribly good solution to me. I ran the nsrck -F NT-server
command manually; the first time, it complained that it could not delete a
file because the file exists. Well duh. I'm hoping this is just a stupid
error message; it was probably complaining that the index file still had
some temporary files left over from the last run. Ran nsrck again, and it
gave nary a warning.
Apparently, that wasn't a permanent solution. Any ideas what I can do to
fix this? I'm not willing to blow away the index and either start from
scratch or re-create them from tape; I had to blow away the v4.4 indices
because the "converstion" program failed miserably. And I really would like
to know what's causing this so it can be prevented from happening in the
future.
Thanks in advance.
-----------
Mike Matthews, Mike_at_Matthews.net
http://mike.matthews.net
Received on Mon Jan 25 1999 - 02:13:20 NZDT