Endpoint Protection

Hi,

I want to migrate from SEPM11 to SEPM12 but no space on disk ( about 35 Go free) because the sem5 database file is about 14 Go. How can I reduce or purge it.

tahank you for your help.

 Shrink the Symantec Endpoint Protection Manager 12.1 embedded database

http://www.symantec.com/connect/downloads/shrink-symantec-endpoint-protection-manager-121-embedded-database

Use this tool:

Readme included

Attachment(s)

ShrinkEmbeddedDB_0.zip   13 KB 1 version

Hello,

Try the Following steps to Create new transaction log(sem5.log):

1. Verify if there is any running instance of dbsrv11 in the Task Manager > Processes tab. If yes, then end that process;
2. Stop the Embedded database service;
3. Go to "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\" and renamesem5.log to sem5.log.old for SEP12.1. ( Please use "Program Files (x86)" instead of "Program Files" if it is a 64 bit machine;
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 for SEP 12.1;
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 for SEP 12.1;
6. Click Start, click on Run and Type “services.msc” then click OK and start the SymantecEmbedded Database Service;
7. Start the Symantec Endpoint Protection Manager service;
8. If it stays started then go ahead and log into the Symantec Endpoint Protection Manager and everything should now be working properly.

OR

Simply enable both options to Truncate the database transaction logs and Rebuild Indexes from the SEPM Database Maintenance Tasks to keep Sem5 under control:

1. Log in to the Sep 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.

(Source: TECH166658 and https://www-secure.symantec.com/connect/articles/symantec-endpoint-protection-manager-121-database-using-high-amount-hard-drive-space )

To reduce the size of Sem5 right away, simply click on Truncate Transaction Log Now and Rebuild Indexes Now from Admin/Servers/Tasks.

OR

There is a Tool available for Shrinking the Database.

Shrink the Symantec Endpoint Protection Manager (SEPM) 12.1 embedded database

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

Also, check this Article:

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 that helps!!

hello,

I have Symantec EndPoint Protection Manager 11, not 12.1

thanks,

ok

Try this artical

How to shrink the embedded database for the SEPM using the Dbunload tool

http://www.symantec.com/business/support/index?page=content&id=TECH104278

Hi Brian81,

is this tool valid for SEPM 11 ?

ok

Try this artical

How to shrink the embedded database for the SEPM using the Dbunload tool

http://www.symantec.com/business/support/index?page=content&id=TECH104278

For 11.x, use dbunload:

To use the Dbunload tool on 32-bit Operating Systems

1. Ensure that you have available free drive space equal to 1.5 to two times the size of the database.
2. Using the Database Back Up and Restore wizard, make a backup copy of the following file:
   
   \Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db
3. Stop the following services:
   • Symantec Endpoint Protection Manager
   • Symantec Embedded Database
4. Start the service Symantec Embedded Database.
5. Click Start > Run, type CMD, click OK, and then type the following two lines at the prompt:
   
   cd \Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32
   dbunload -c "uid=dba;pwd=password_set_during_install" -ar

Note:
If the following results are seen:

 ***** SQL error: Specified database file already in use

Stop the Symantec Embedded Database Service and run the command again.

Note:
If the following results are seen:

***** SQL error: Database server not found

Run the following command :

dbunload -c "dbf=C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db;start=dbsrv9;uid=dba;pwd=password_set_during_install" -ar

To use the Dbunload tool on 64-bit Operating Systems

On 64-bit Operating systems, the path should be changed accordingly, and only the dbunload command that specifies the full path to the sem5.db database will work. The procedure and commands will like this:

1 Stop the following services:

• Symantec Endpoint Protection Manager
  Symantec Embedded Database

2. Click Start > Run, type CMD, click OK, and then type the following two lines at the prompt:
cd \Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\ASA\win32
dbunload -c "dbf=C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db;start=dbsrv9;uid=dba;pwd=password_set_during_install" -ar

What is the reisk involved in shrinking the Database ?

I assume doing the backup first through the start menu should be sufficient to cover for rollback in case something wrong happens.

Possible corruption.

In the SEPM folder is a "db" folder; in that folder, what are the sizes of the sem5.db and sem5.log files?

Michael

Yes, that is why doing the backup before doing the transaction log truncation is always good to go,

Hi HB2012,

By design when you want to perform a migration of your SEPM Console, the SEPM migration needs temporary the equivalence of your existing database file size multiplied by 3.

In your situation, SEPM Migration from 11.X to 12.1 will request you temporary 42Gb free.

What is the OS of your Server ? Could you extend the partition size where SEPM is installed ? (5-7Gb should be large enough to avoid any issue during the migration).

Please do not forget at the same time that there is specific migration path supported.

Check this nice KB which clearly explains on which version you could migrate depending your existing SEP version installed.

=> http://www.symantec.com/business/support/index?page=content&id=TECH194313

Do not shrink your database, especially embedded database, that's too risky and your clients might not be able anymore to update their definitions from your SEPM.

The database shrink tool is there only if the database file has a very very big abnormal size but you should keep in mind that if you did plenty of previous migration, there are some datas that will probably never be completely purged.

If your database file sizes 14Gb and you have for example less than 200 clients. Forget completely the migration and perform a fresh install because your existing database contains probably a plenty of corrupt/broken links/invalid data.

Your database file size could depend of many things like below.

- Client quantity/Group quantity/Policy quantity.

- Logs settings and how long you keep them.

- If you have various platforms (Win32, Win64, MAC).

- If you have various and different SEP versions installed on your machines.

- The number of revisions kept on your SEPM Console.

- The number of SEP install packages present on your SEPM Console.

So before using Shrink database tool or anything like that, better tell us how many managed clients you have, how many different SEP version you have, how many Live Update contents you're keeping on your SEPM Console.

An easy solution might be to reduce temporary your Live Update contents to keep on your SEPM 11.X to free up some disk space and then perform the migration, restart your server and set it back the Live Update contents to keep to the initial values.

But honestly, if you have for example over thousand of managed clients , do not expect to have a slightly reduced database file size after using DB Shrink Tool. As I told you it might generate more issues than improvements.

Kind Regards,

A. Wesker

Hi,

Any update on this ?

Update us the status......... plzzzzz

Hi,

Yes, I prefer to reinstall from scrach. I have only 25 clients on this site.

thank you for your help.