Yes, this is a 3.12 NetWare server - sorry, I should have included that
info. I have also found out that this server has only 48Mb of memory.
All of the patches and latest NLMs have been applied (most were already
up-to-date before I got involved). The latest version of the NetWare
client is installed, SLOWINCREMENTAL is ON, and COMPRESSION is OFF. I
have not yet gotten a good backup of the APPS: volume. In fact, I
haven't gotten even a bad backup of this volume! Backups of SYS: and
DATA: are clean and complete.
Is there a minimum memory requirement for ADSM Client on NetWare? I
know enough about NetWare to be dangerous, but I don't know how to
interpret it's resource stats. If someone would be so kind as to look
at these, maybe it will make some sense.
--MAIN MONITOR SCREEN--
File Server Up Time: 5 Days 22 Hours 52 Minutes 38 Seconds
File Server Up Time: 5 Days 22 Hours 52 Minutes 38 Seconds
Utilization: 2 ¦ Packet Receive Buffers: 100
Original Cache Buffers: 11,606 ¦ Directory Cache Buffers: 85
Total Cache Buffers: 7,881 ¦ Service Processes: 9
Dirty Cache Buffers: 0 ¦ Connections In Use: 33
Current Disk Requests: 0 ¦ Open Files: 53
--RESOURCE UTILIZATION SCREEN--
Permanent Memory Pool: 1,775,616 Bytes 4% 1,744,612 In Use
Permanent Memory Pool: 1,775,616 Bytes 4% 1,744,612 In Use
Alloc Memory Pool: 1,401,048 Bytes 3% 1,124,348 In Use
Cache Buffers: 33,289,344 Bytes 68%
Cache Movable Memory: 9,073,152 Bytes 18%
Cache Non-Movable Memory: 3,598,848 Bytes 7%
Total Server Work Memory: 49,138,008 Bytes
--AUTOEXEC.NCF SETTINGS (that may apply)--
SET MAXIMUM PACKET RECEIVE BUFFERS=500
SET MAXIMUM PACKET RECEIVE BUFFERS=500
SET MAXIMUM RECORD LOCKS PER CONNECTION=10000
SET MAXIMUM FILE LOCKS PER CONNECTION=1000
SET MAXIMUM RECORD LOCKS=100000
SET MAXIMUM FILE LOCKS=100000
SET MINIMUM FILE CACHE BUFFERS=100
--STARTUP.NCF SETTINGS (that may apply)--
set Maximum Physical Receive Packet Size = 1514
set Maximum Physical Receive Packet Size = 1514
set Minimum Packet Receive Buffers = 100
Thanks again for all the input,
Joelle Booher
AMP Incorporated
Harrisburg, PA
jmbooher AT amp DOT com
>----------
>From: Pittson, Timothy ,HiServ/NA[SMTP:tpittson AT HIMAIL.HCC DOT COM]
>Sent: Friday, May 23, 1997 7:43 AM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: Netware Client - ANS0433E
>
>Joelle,
> Since you mentioned backing up the bindery I assume you're running
>Netware 3.11 or 3.12. The size of the APPS volumes isn't as big a
>factor as the number of files on the volume. Have you gone in to
>Monitor to check the resource utilization on this server - what % are
>the cache buffers at ?? Have you ever gotten a clean backup of the APPS
>volume using ADSM ?? Sounds like you don't have enough memory in the
>server but here are a couple of things you can try....
>
>1) Did you also install the TSA and SMDR NLMs that were distributed with
>the latest ADSM code?? If not, install them.
>
>2) Make sure you have the following in your DSM.OPT file
>
> SLOWINCREMENTAL ON
>
>3) Are you using ADSM compression - if so, try turning it off.
>
>4) There were a couple of versions of the 2.1.06 code for Netware - I
>think 2.1.06g is the latest - make sure you're using that.
>
>5) Try rebooting the Netware server, then immediately run an incremental
>backup. Netware 3.1x can have problems with memory fragmentation,
>especially if the server's been up for a long time. If the incremental
>backup works after rebooting the Netware server, you're most likely low
>on memory and adding some would help both ADSM and the clients who use
>the server as well.
>
>Good luck !!!
>
>Tim Pittson
>tpittson AT himail.hcc DOT com
>
>
>>----------
>>From: Booher, Joelle M[SMTP:jmbooher AT AMP DOT COM]
>>Sent: Thursday, May 22, 1997 4:44 PM
>>To: ADSM-L AT VM.MARIST DOT EDU
>>Subject: Netware Client - ANS0433E
>>
>>Hi all...
>>
>>Thanks for all the responses to my questions about database size
>>disaster recovery for ADSM NT. I think I'm back on track with both of
>>those issues. Now I have yet another strange happening - I thought I'd
>>see if anyone else has encountered this (or a similar) situation.
>>
>>Novell file server running ADSM client v2.1.6
>>ADSM NT Server (ptf1)
>>
>>When a backup is performed (either manually or with the scheduler), the
>>bindery and two of the three volumes back up with no errors. However,
>>every time the server gets to the APPS: volume, it comes up with the
>>message
>>
>>"ANS4033E System ran out of memory. Process ended."
>>
>>This volume is NOT the largest one on that server, so I don't think it
>>has anything to do with the volume of data. I can do a selective of
>>files on the other volumes with no problem. However, if I attempt to
>>start a selective of ALL files on the APPS: volume, it gives me the same
>>message as above. When I attempt to backup a specific file on APPS:, I
>>get a message that no files were found matching the criteria.
>>Weirdness.
>>
>>I tried all of the tips that have been posted about Novell performance
>>such as TXNBYTELIMIT, TXNMAXGROUP, settings in the TCPIP.CFG,
>>SLOWINCREMENTAL, versions of NLM's etc. None of these seem to have
>>affected the results. I thought maybe tonight I would try running a
>>VREPAIR, and maybe a BINDFIX, but I can't imagine that either of these
>>would be the solution.
>>
>>Thanks in advance for any tips you may have to offer!
>>
>>Joelle Booher
>>AMP Incorporated
>>Harrisburg, PA
>>jmbooher AT amp DOT com
>>
>
|
