Discussion Locked

Using Brdr Mngr, cache growth prob

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are using Border Manager. It was installed 2 admins ago and now realize that the cache should have been installed on a separate partition. We only have the SYS vol with BM. I am frequently getting out of disk space messages on BM due to the growth of the cache. Anyone know how to limit it or control its growth?
TIA for any help!

5 replies

by deroode

The best solution: get another disk, put the cache there (but you probable knew that allready). http://support.novell.com/cgi-bin/search/searchtid.cgi?/10018669.htm has a lot of advise about tuning and configuring tha cache.

The second best solution for now: Restrict the size of the directory your cache is in. Brows to the root of the cache directory in NWadmin or Console1, and in the properties on tab Facts select the "restrict size" box. That should do the trick..

by hiker

When I adjusted the limit to a slightly lower value in NWADMIN, the flow of BM requests came to a screeching halt. The phones started ringing from folks who could not do anything on the internet. I had to leave the setting where it was to work at all.

by budthegrey

Agreed that adding a volume just for caching is best Heck, any old SCSI drive will do, how much cache space do you really need?

Shutdown the proxy server (unload PROXy and PROXYCFG)

In NWADMIN, open the properties of the server hosting BMgr, then click the 'Border Manager' button. Finally, click on the 'Caching' button to get to the cache settings. perhaps you can crank down the amount of data being cached, or how long data is kept in the cache.

LOAD PROXY -cc (-cc means "clear cache")

One other thing to do is set the the proxy cache folder (/etc/proxy/cache, I think) to 'purge immediate'. That way, when cache files are removed, they really go away, and not to the salvage area.

HTH

by hiker

I tried to shut down the proxy server but with all that cache, it was going to take hours to clear and it locked up the server. Even though it was a week night, I couldn't hang around for as long as it was going to take. Ended up rebooting it and not clearing cache.

This discussion is closed to new replies.