Endpoint Protection

 View Only
  • 1.  Taking High Memory utilization

    Posted Mar 03, 2011 05:26 AM

    SQL and SEPM both taking high Memory and CPU utilization

    Ram Speed:- 4GB and 

     

    EXE:-SQLSERVR.EXE *32  (utilization 2.5 GB )

    SemSvc.exe *32:- ( Utilization 500 MB )



  • 2.  RE: Taking High Memory utilization
    Best Answer

    Trusted Advisor
    Posted Mar 03, 2011 06:20 AM

    Hello,

    There are few Question.

    1) What version of SEP and SEPM are you using?

    2) What version of SQL are you using?


    I have seen this exact issue occur many times when there is a SQL Database that is being scanned on the system.  Are you running any form of Database?  If so, we will need to exclude those DB files from being scanned.

    If you are unsure, you can look for Sqlservr.exe running and also the default location of the SQL DB is located C:\Program Files\Microsoft SQL Server\MSSQL\MSSQL\Binn


    Here is the doc for excluding this:
    Title: 'How to exclude SQL files and folders using Centralized Exceptions'
     

    http://www.symantec.com/business/support/index?page=content&id=TECH105240&locale=en_US

     

    Also check the below,

    FIX: High CPU utilization by SQL Server 2005 may occur when you use NUMA architecture on a computer that has SQL Server 2005 installed

    http://support.microsoft.com/kb/931821
     

    To set sepm memory utilization use this document

    https://www-secure.symantec.com/connect/articles/things-you-can-do-confpropeties-file-and-serverxml-file-sepm


     



  • 3.  RE: Taking High Memory utilization

    Trusted Advisor
    Posted Mar 03, 2011 06:43 AM

    Hello,

    Please check Forums Threads with similar Issue.

    SEPM Server pegged at 100% / SQL 2008

    https://www-secure.symantec.com/connect/forums/sepm-server-pegged-100-sql-2008

    Again, after Looking into this a little bit more and here is what I found. 

    In general this issue is not cause specifically by the Symantec Endpoint Protection Manager or any of it's software. It is usual for a MS SQL server to take up as much physical RAM as 4 GB +. The specific process that you will see utilize a good chunk of memory is sqlservr.exe.

    The reason that the SQL server does this is for faster access. In fact the SQL memory manager will try to cache as much data in memory as possible so it can access it faser, and it will take more of the available memory on servers with a large amount of unused RAM.

    To resolve this you should contact Microsoft for instructions on how to configure the "Max Server Memory" setting in Microsoft SQL Server. 

    Setting Server Configuration Options

    http://msdn.microsoft.com/en-us/library/ms189631.aspx



  • 4.  RE: Taking High Memory utilization

    Posted Mar 26, 2011 10:19 PM

    Hi mithun ! 

     

    I dont get this" Are you running any form of Database?  If so, we will need to exclude those DB files from being scanned."

     

    Also could u helo me how do we check if SQL is exluded or not. 



  • 5.  RE: Taking High Memory utilization

    Posted Mar 27, 2011 05:28 AM

    i have been expirencing the smilar problem . 

    How do i check if the bcp.exe is working correctly



  • 6.  RE: Taking High Memory utilization

    Trusted Advisor
    Posted Mar 28, 2011 07:08 AM

    Hello,

    @ Fatima.

    SQL Server?

    You want to know :

    1) Figure out if the SQL is excluded or not?

    2) How to check if the bcp.exe is working correctly?

     

    Probably, you may like to read the following for your Question 1:

    1) How to exclude MS SQL files and folders using Centralized Exceptions

    http://www.symantec.com/business/support/index?page=content&id=TECH105240&locale=en_US

    2) Best Practices guide for Installing the Symantec Endpoint Protection Manager with a SQL Server 2000 Database

    http://www.symantec.com/business/support/index?page=content&id=TECH104404&actp=search&viewlocale=en_US&searchid=1301309216694

    3) Best Practices guide for Installing the Symantec Endpoint Protection Manager with a SQL Server 2005 Database

    http://www.symantec.com/business/support/index?page=content&id=TECH104405&actp=search&viewlocale=en_US&searchid=1301309216694

    4) Best Practices guide for installing the SEPM 11 RU5 and later using SQL Server 2008 Database

    http://www.symantec.com/business/support/index?page=content&id=TECH96451&actp=search&viewlocale=en_US&searchid=1301309158860

    5) Microsoft Guidelines for choosing antivirus software to run on the computers that are running SQL Server

    http://support.microsoft.com/kb/309422/

    6) How to Verify if an Endpoint Client has Automatically Excluded an Application or Directory

    http://www.symantec.com/business/support/index?page=content&id=TECH105814&actp=search&viewlocale=en_US&searchid=1301309391048

    7) Verifying SEP Exceptions for Windows Server 2008 and Windows Server 2003 Domain Controllers

    http://www.symantec.com/business/support/index?page=content&id=TECH96048&actp=search&viewlocale=en_US&searchid=1301309391048

     

    Your Question 2:

    Do you feel , you have issues with bcp.exe.

    If yes, check from the above articles, if the Best Practices were followed.