IslandsIT
asked on
Netware 6.5 Memory Leak when using Open File Manager for Backup Exec
When I use backup Exec 9.1 with Open file Manager on a Netware 6.5 SP5 server I keep hetting out of logical space errors. If I do not backup the server I do not get the errors only when backing up. If I increase the maximum logical cache files available to 2Gb it will then reset itself and keeps giving me the errors. This only started to happen when I patched the system to SP5
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ShineOn
Is OFM configured to use a particular volume for its work space? It might be that you just don't have enough room wherever it's trying to hold its copy of open files. Did you choose the option to do a backup of updated files when you did the SP5 update? Maybe your SYS: vol is too low on free space for OFM to allocate what it needs. Try moving the backup files off SYS: or deleting them. Before you do that, check your SYS: vol's salvage to see if maybe a purge of SYS: might fix it - I think the OFM wants "real" free space, not just "available" space, and if you've got salvage turned on on SYS: the SP update may have left a bunch of stuff in salvage for you.
ASKER
I have 3GB disk space on Sys volume so I dont think it is that. How would I go about checking the TSA and what version I am using and which is a good version.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I suiggested the TSA issue first and in lieu of no feedback from the user,my answer is just a good a ShineOn's.
So a split of points , maybe ,but his as the only accepted answer ,no.
TSA's from Novell are notoriously flakey and back revving to a known good one is always the preferred troubleshooting method.
So a split of points , maybe ,but his as the only accepted answer ,no.
TSA's from Novell are notoriously flakey and back revving to a known good one is always the preferred troubleshooting method.
... unless the latest TSA5UPxx has the bugfix. Then backrevving is just adding already-fixed bugs back in.
I have no prob with a split.
I have no prob with a split.