You observe that a Symantec Endpoint Protection Manager (SEPM) task truncates the database transaction logs during the migration to a newer version. If auto-growth on the transaction logs is disabled, it can cause issues during or after the upgrade until the transaction logs are manually set to an appropriate size/limit.
An example of such an issue is that one or more Symantec Endpoint Protection (SEP) installation packages fail to import.
Symantec Endpoint Protection Manager with a SQL database.
"The transaction log for database 'SEPM_DB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases"
"DBCC SHRINKFILE" on the transaction logs is always called during a SEPM upgrade and when adding a new SEPM replication partner with a Microsoft SQL database. This behavior is working as designed.
While auto-growth is not required during normal SEPM operations, it is currently required for upgrades and for adding a new SEPM replication partner. Once those tasks are complete the auto-growth option can be disabled, but the database will need to be monitored closely for errors and for the (growing) size of the transaction log. The database administrator or SEPM administrator should remember to incorporate a process to turn auto-growth back on before any upgrade and before adding any replication partner (even if the partner previously existed).
The default configuration of the SEPM database is to auto-grow the transaction logs, but a Database Administrator (DBA) may choose to manage the size manually.
And while log truncation occurs on migration or setting up a new replication partner, it can also be run on-demand from the SEPM (via DB maintenance settings or the truncate now command) and if the truncation log task is enabled (again: SEPM scheduled maintenance, by default runs every four hours as a task).
Subscribing will provide email updates when this Article is updated. Login is required.