Hi,
I have the following situation where the SEPM downloads Liveupdate content successfully but does not update SEPM or clients and I have found the following KB article:
| Article:TECH211147 | | | Created: 2013-10-01 | | | Updated: 2013-10-08 | | | Article URL http://www.symantec.com/docs/TECH211147 |
Solution
- Reduce the number of content revisions being retained by the SEPM.
- Increase the autogrowth setting for the sem5_content file within SQL Server.
I have 2 SEPM (replication) serving as load balancer and failover for 5000 clients with 1 SQL Database.
I have reduced the number of content revisions from 30 revisions to 28 revisions but afraid that the problem might occur again.
As I would not want to corrupt the SQL Database and avoid any complications with the SEPM, I would like to seek advice on my queries below.
1. With regards to ammending the autogrowth setting within the SQL Server for the sem5_content file:
- Am I required to stop the SQL Database service before I do the ammendment with the autogrowth and restart the service again?
- Am I required to stop and restart my SEPM service?
- Do I need to stop replication for the SEPM before I proceed to increasing the autogrowth setting?
- Is it necessary to run Management Server Configuration Wizard to reconfigure the Symantec Endpoint Protection Manager?
2. Would increasing the autogrowth setting in the sem5_content file enough or I also need to increase the rest of the sem5 files such as sem5_index file, sem5_loginfo, sem5_log1, sem5_log2 etc.?
Has anyone tried these before or any advise would be appreciated?