Endpoint Protection

I am using Symantec 12.1R2 with the embedded databse. I noticed that the drive that had SEPM installed was running out of diskspace.

On investigation it was observed that the file sem5.log [D:\Program Files\Symantec\Symantec Endpoint Protection Manager\db] was increasing in size.

To resolve the issue we need to delete the sem5.log file. This process can be automated by using the following script:

net stop semsrv
net stop SQLANYs_sem5
attrib -r "D:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.log"
del "D:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.log"
CD D:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\
dbsrv12 -f "D:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db
net start SQLANYs_sem5
net start semsrv

I have referred to the following post:

http://www.symantec.com/connect/forums/sem5log-keeps-growing

Purpose of this post is to consolidate to the process into a single script.

Hello,

Check these Articles:

Symantec Endpoint Protection Manager (SEPM) Database Transaction Log (sem5.log) Consumes Hard Drive Space in SEP SBE 12.1 RU1

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

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

How to periodically free up the space used by the sem5.log in EPSBE 12.1 RU1

https://www-secure.symantec.com/connect/articles/how-periodically-free-space-used-sem5log-epsbe-121-ru1

Hope this helps!!

Hi,

Thanks for sharing this script.

Mentioned issue is not seen with the latest SEP version 12.1 RU2.

If issue persist then I would suggest to log a case with Support.

Hi,

I'm sorry to report but this issue does appear in the latest release of SEPM 12.1 RU2.

I'm researching in why I have this sem5 log file size issue. At present the size of my log file is 60GB and growing. I am using a Sybase Database not SQL.

I only have one SEPM so will assume this process can not be performed during business hours.   

Before I run the script to reduce it's size I would like to know consequences. What are the best practices.

Thanks

It's worth mentioning that the sem5.log is the transaction log for the DB.  Deleting it means that any data that has not yet been committed to the DB will be lost.

Perhaps you could increase the frequency of the Truncate Logs job in the DB Maintenance tasks (i.e. reduce time in between them)?

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

Alternatively, you could setup an external task to truncate the logs if you wanted (possible but ideally this should be done by the SEPM if using an ebmedded DB):

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

Many thanks for responding. Running a Truncate Transaction Logs resolved my problem..

I'm glad to hear this helped!

Hopefully the OP will have the same results (as deleting the transaction log and potentially losing data is never a great idea )

As always, it'd be appreciated if you mark any posts you find useful with a "Thumbs Up"!

Sorry wasn't aware of the Thumbs Up icon. Could it be made bigger?

This has also happened with us over the weekend and we recently upgraded to SEPM 12.1 RU2 (2 months prior).  The log file increased to about 17 GBs and my netadmin increased the disk space until i could get into the office the next day.  By the next day, the log file truncated on its own. 

Hi

You can configure the schedule of Truncating of Logs

Regards