Endpoint Protection

 View Only
  • 1.  Embedded database size

    Posted Jun 17, 2013 06:51 AM

    Hi,

     

    I'm running SEP 12,1.2 on Windows XP SP3 machines and this morning have had many reports of slow application responces. Apparently this is a known issue according to one of my colleagues who investigated the Symantec forums.

    The main reason for writing is to ask about the recommended size for an embedded database running approximately 800 clients as I have a feeling the database size could be an issue.

    Currently the size of my embedded database is 8.2GB. Should I be concerned about this file size and what actions can I take to reduce it's size.

    I have read articals on database size and performed maintenance tasks but still the DB size increases.

    Many Thanks



  • 2.  RE: Embedded database size

    Posted Jun 17, 2013 07:01 AM
    Check the article to reduce the DB size http://www.symantec.com/connect/articles/symantec-endpoint-protection-manager-121-database-using-high-amount-hard-drive-space


  • 3.  RE: Embedded database size

    Broadcom Employee
    Posted Jun 17, 2013 07:07 AM

    reduce yhe log retention period.

    reduce the content revision to store.

     



  • 4.  RE: Embedded database size

    Trusted Advisor
    Posted Jun 17, 2013 07:40 AM

    Hello,

    What OS is the SEPM running on?

    Check these Articles: 

    Shrink the Symantec Endpoint Protection Manager 12.1 embedded database

    https://www-secure.symantec.com/connect/downloads/shrink-symantec-endpoint-protection-manager-121-embedded-database

    Symantec Endpoint Protection Manager 12.1 database using a high amount of Hard drive space

    https://www-secure.symantec.com/connect/articles/symantec-endpoint-protection-manager-121-database-using-high-amount-hard-drive-space

    Symantec Endpoint Protection Sizing and Scalability Best Practices White Paper

    http://www.symantec.com/docs/DOC4448

    Hope that helps!!



  • 5.  RE: Embedded database size

    Posted Jun 17, 2013 07:42 AM

    The SEPM Embedded DB size is unlikely to have a detrimental effect on the performance of the clients.  A large DB can slow down the SEPM itself (though not usually at the sizes you're reporting).  Can you provide some more details on what performance problems you're hearing about?

    Just in case it's a common issue, you may want to take a look at the performance related articles below:
    http://www.symantec.com/docs/HOWTO55872
    http://www.symantec.com/docs/HOWTO81048

    Also, what version of SEP are you using?  The Insight lookups by SONAR in SEP12.1 and later, have been reported to cause a slight delay when starting an application (especially if the client doesn't have an Internet connection).  If this sounds applicable, then please follow the below article on how to disable the Inight lookups and test if this has an impact:

    http://www.symantec.com/docs/HOWTO81000
    You'd want to uncheck the "Allow Insight lookups for threat detection" option described in step 7 for this test.  Note: that this does affect security, so the recommendation would be to investigate why the clients are failing the Insight Lookup and fix that, rather than rolling this change to all your clients.



  • 6.  RE: Embedded database size



  • 7.  RE: Embedded database size

    Broadcom Employee
    Posted Jun 17, 2013 08:07 AM

    Edit#

    Hi,

    Thank you for posting in Symantec community.

    I would be glad to answer your question.

    Following fixes are mentioned in SEP 12.1 RU3 notes:

    Network performance slows on Windows XP with Symantec Endpoint Protection 12.1.2 MP1 installed

    Fix ID: 3180923
     
    Symptom: Computers experience network performance problems when the Network Threat Protection (NTP) firewall component of the Symantec Endpoint Protection 12.1.2 MP1 client is installed and enabled. Symptoms include:
     
    •Copying files from a network location over Windows File Sharing takes significantly more time.
    •Programs that are started from a network share take significantly longer to load.
    •Ping responses take longer to return.
    Solution: Modified the firewall to call the correct notification routine for Windows XP.
     
    Symantec Endpoint Protection Manager performance is slower after upgrade to 12.1.1 MP1 or later
     
    Fix ID: 2882607
     
    Symptom: After upgrade to Symantec Endpoint Protection Manager 12.1 RU1 MP1, performance of the Symantec Endpoint Protection Manager server is degraded. Delaying the security mining task (scm.timer.securitymining.delay) resolves the issue.
     
    Reference: New fixes and features in Symantec Endpoint Protection 12.1.3
     
     
    For 800 clients installing SEPM on Windows XP machine can have some OS limitations.

    8.2 GB database size for 800 clients is acceptable.

    I would suggest to install it on Server operating system if possible.

    Maintaining the database

    http://www.symantec.com/docs/HOWTO55337 

    Disk Space Management procedures for the Symantec Endpoint Protection Manager

    http://www.symantec.com/docs/TECH96214 

     



  • 8.  RE: Embedded database size

    Posted Jun 17, 2013 08:13 AM

    Hi,

    Please check.

    (SEPM) database transaction log (sem5.log)  taking lots of space.

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

     



  • 9.  RE: Embedded database size

    Posted Jun 17, 2013 09:28 AM

    For 800 clients that size is normal. Embedded can handle upto 5000 clients, 

    Dowload this tool 

    https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CCoQFjAA&url=http%3A%2F%2Fwww.symantec.com%2Fbusiness%2Fsupport%2Fresources%2Fsites%2FBUSINESS%2Fcontent%2Flive%2FTECHNICAL_SOLUTION%2F105000%2FTECH105256%2Fen_US%2FSymantec_Endpoint_Protection_Database_Sizing_Tool.xls&ei=PA6_Ud2VCvPG0AHMw4HYDA&usg=AFQjCNEytnAnJCWYazl1EweULCkndQd5EQ&bvm=bv.47883778,d.dmQ

    check the size, it should be same. if you still want to reduce further chance the content size to 10.

    under

    admin - servers - right click servers - under database change it to 10