Endpoint Protection Manager using excess disk space after upgrade from 14.3 MP1 or below with an embedded database
search cancel

Endpoint Protection Manager using excess disk space after upgrade from 14.3 MP1 or below with an embedded database

book

Article ID: 246121

calendar_today

Updated On:

Products

Protection Suite Enterprise Edition Endpoint Protection

Issue/Introduction

After upgrading from Symantec Endpoint Protection Manager (SEPM) 14.3 MP1 or below, with an embedded database, to 14.3 RU1 or newer, the SEPM disk usage is higher by more than 50%.

Cause

Legacy Sybase database files failed to purge after successful upgrade.

Resolution

If the SEPM has successfully upgraded and is functioning with the new SQL Express database then prior Sybase database files may be removed from the legacy location.

  1. Open services.msc and confirm the Symantec Embedded Database service is no longer present, and SQL Express is running
  2. Open a file browser to <SEPM>\db
  3. Remove sem5.db and sem5.log along with any .out files of significant size.
    Note: Do not remove any subfolders or files within them. They belong to SQL Express and must remain intact.

If disk space used by the SEPM still appears excessive, please see: Low disk space on a Symantec Endpoint Protection Manager (broadcom.com)