I experienced the same thing as Matthias early on. MANDATORY: Upgrade the
client to the v2 client, which takes memory from Novell Cache Buffers
instead of Allocated Memory Pool. This is much more flexible.
If the problem persists, you must add chips to the server. In the
alternative, unload any unnecessary NLMs, dismount any non-critical volumes,
and generally minimize memory consumption. You could also do restores which
start further down the volume's tree and run successive restore passes.
This causes less memory usage on the client because you are restoring fewer
files per restore session. ADSM sends something like 24 - 30 bytes/file to
the client for each file/directory to be restored. Once the list is built
at the client and data flow begins, memory usage on the Novell client
becomes static. Play with it, but I recommend avoiding dropping below 20%
available cache buffers. Keep the users off the system until the restore is
complete to minimize drain there.
CAUTION: We discovered via disaster recovery tests that our old servers had
volumes that were too large for the amount of memory supported by the server
and replaced them with newer units. Best test before you assume they'll
come back.
Steve Kuhn Network Manager, Aegis Insurance Services, Jersey City, NJ
kuhns%aegis AT mcimail DOT com
----------
From: ADSM: Dist Stor Manager
To: Multiple recipients of list ADSM-L
Cc: KUHNS
Subject: NetwareClient low memory
Date: Tuesday, January 14, 1997 6:30PM
---------------------------------------------------------------------------
MCI Mail date/time: Tue Jan 14, 1997 6:31 pm EST
Source date/time: Tue, 14 Jan 1997 18:36:40 -0500
-------------------
---------------------------- Forwarded with Changes
---------------------------
From: INTERNET.OWNERAD at SNADGATE
Date: 1/14/97 1:08PM
To: Jerry Lawson at ASUPO
*To: *Multiple recipients of list ADSM-L at SNADGATE
Subject: NetwareClient low memory
----------------------------------------------------------------------------
---
-
Do you have SLOWINCREMENTAL=YES Specified in the DSM.OPT? The manual talks
about backups, but it would seem that the memory issues would be the same
for
both restore and backups.....
Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: NetwareClient low memory
01-14-97 01:08 PM
Hi ADSM'ers,
I'm trying to do an catastrohic restore of a
complete Netware-server volume ( about 350.000 files ).
After some time running the client brings out the
message 'your system is low on memory...'.
( examinating about 170.000 files )
I'm prompted to free resources.
The server has 130MB of memory and nearly nothing
other running than the ADSM-Client.
How can I reduce the resources needed for ADSM.
Notice : the server isn't restoring yet, he
is still querying the database.
I don't think that turning the TX??-parameters will help.
I know I could split the restore-process into smaller
pieces but that wouldn't be 'state of the art' i think.
Client level is lvl5, Server is MVS.
Anyone any idea ???
Best regards,
Matthias Brasch, HEW-Hamburg, M_Brasch AT compuserve DOT com
|
