Issue: The Symantec Endpoint Protection Manager (SEPM) folder for version 12.1 takes a lot of disk space.
In version 11.X the workaround was to decrease the number of contents revisions, if they are not required to keep updates for specified days, then delete the revision folders manually from inside C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\Content\C60D... or 1CD8..., with the service stopped. TECH153952
In version 12.1 we do not have the same folders.
Also, the database transaction log file (sem5.log) may grow to 10-15 GB, or larger, after upgrade and it is not possible to log on to the manager.
Cause: Number of Content revisions are more than required. OR Did not select options to "Truncate the database transaction logs" and "Rebuild Indexes"
Solution:
1. Go to: C:\Program FIles\Symantec\Symantec Endpoint Protection Manager\Inetpub\Content (Default Location of SEPM)
2. Check
- {535CB6A4-441F-4e8a-A897-804CD859100E} for 32 Bit
- {07B590B3-9282-482f-BBAA-6D515D385869} for 64 Bit
Note: These two folders take more disk space, compared to other folders which are used to store the Virus definitions
3. Once the number of content revisions has been decreased, then this would be reflected on the number of revision folders. See TECH96214 for recommendations.
To reduce the size of the database transaction log file :
1. Log in to the Symantec Endpoint Protection Manager.
2. Click Admin and select Servers.
3. Select the localhost under Servers.
4. Under Tasks, Select Edit Database Properties.
5. In the General tab under Database Maintenance Tasks.
6. Select the checkboxes next to Truncate the database transaction logs and Rebuild Indexes.
7. Click OK to apply the changes.
It will make changes to the database on the mentioned time under "Scheduled task". To reflect the changes immediately click on Truncate Database Transaction Log Nowand Rebuild Indexes Now under Tasks.
Once this is done, a lot of disk space will be freed up on the C drive.
If incase, you are unable to log on the the manager, you can recreate the sem5.log file to resolve the issue.
1) Stop SEPM and database services.
2) Rename / Delete the current log
3) Click Start, click on Run and Type "CMD" then click OK
4) In the Command Prompt type: "CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\" and press Enter this will change directories to the folder containing dbsrv11.exe.
5) To force the recreation of sem5.log. Type: "dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" and press Enter
6) Click Start, click on Run and Type "services.msc" then click OK and start the Symantec Embedded Database Service
7) Start the Symantec Endpoint Protection Manager service.
Also, Please check ContentInfo.txt file for more information about the folders stored in Symantec Endpoint Protection Manager folder