Antivirus strategy for AOS machine

(0) Share

Report

Posted on by Community Member

I have problems with a customer AOS. These problems are mainly that the AOS uses a lot of memory that never gets released. Other customers with similar environments do not have this problem.

One thing that I have noticed is that this customer uses Trend Micro on their AOS machine. Most of our customers do not use any antivirus on their AOS machine.

Also, the Trend Micro scannar (tmlisten.exe) looks rather strange. It has allocated over 2GB of virtual memory. I have never seen anything like that.

So, my questions aer: What are your antivirus strategies? Have you ever seen problems with antivirus on AOS machine? If you use antivirus on AOS machine, what exclusions have you made?

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Denis Patrakov on at

Like (0)

Report

First of all, how much is "a lot of memory" in your case? AX 2009 AOS can easily consume about 4-5 Gb: 2-2.5 for its own needs and 2-2.5 for memory-mapped application files (this memory is allocated by the Windows kernel). But the situation can be much worse if the AOS' host is virtualized and a lot of RAM is allocated to the VM, say 8-10 Gb. In that case a "baloon" driver can consume a lot of memory forcing the guest OS to swap. In any case you can elaborate the memory consumption details using either RAMMap or VMMap utils.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Well, after 12 days of uptime the process is using 2GB Private and 2GB Commit (not really sure what these values mean). The memory increases by 100-200 mb every day. With help from MS I have found a printer driver that leaked handles and took care of that. I also noticed that a batch job drove the memory up each night. I have rewritten that, but the situation is the same. The only difference is that memory seems to increase more even.

The server is virtualized (VMWare).

The following is a screendump from VMMap that you recommended. I don't know if this image looks "normal" at all.

I have been looking at a lot of possible problems. My latest idea was that the antivirus somehow was disturbing the AOS.

Was this reply helpful? Yes No
Denis Patrakov on at

Like (0)

Report

Your VMMap info looks pretty normal, here's how it looks in my case (uptime is almost a week). It's a batch server running in a VMware VM, but without any antiviruses installed.

Was this reply helpful? Yes No