Unsolved
This post is more than 5 years old
21 Posts
0
890
August 23rd, 2006 01:00
nsrmmdbd does not release memory
New problem, backups have apparently previously been working fine.
NW Server running Win2000 with SP4 and NW 7.2.1 for windows.
As backups proceed, the amount of memory used by the nsrmmdbd process grows steadily until it interferes with the basic memory requirements for the server which then hangs.
After a reboot, everything is back to normal.
Also, if NW services are restarted, the memory is released.
A small to medium backup succeeds, but the memory which has been allocated to nsrmmdbd does not get released.
The next backup causes the memory allocated to nsrmmdbd to start growing from the previous level. Finally, too much memory is used and the server hangs.
Has anyone seen this and resolved it ?
The knowledgebase does not seem to show anything directly related.
Thanks
John Hope-Bailie
NW Server running Win2000 with SP4 and NW 7.2.1 for windows.
As backups proceed, the amount of memory used by the nsrmmdbd process grows steadily until it interferes with the basic memory requirements for the server which then hangs.
After a reboot, everything is back to normal.
Also, if NW services are restarted, the memory is released.
A small to medium backup succeeds, but the memory which has been allocated to nsrmmdbd does not get released.
The next backup causes the memory allocated to nsrmmdbd to start growing from the previous level. Finally, too much memory is used and the server hangs.
Has anyone seen this and resolved it ?
The knowledgebase does not seem to show anything directly related.
Thanks
John Hope-Bailie
No Events found!


ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
August 23rd, 2006 06:00
Good thing to do would be to check what changes have been done to system if apparently everything was fine until now. Perhaps some change triggered this behavior.
jhope-bailie
21 Posts
0
August 24th, 2006 23:00
Curiously, although the memory was being hogged by nsrmmdbd, it was not a media DB problem. Rolling back the media DB using mmrecov did not resolve the problem. Nor did "rebuilding" (scavenging) the media index.
Finally a complete DR to a point 2 weeks ago resolved it, and we are busy scanning in the intervening volumes.
So it points to a client file index corruption.
regards
John Hope-Bailie