Endpoint Protection

Someone from Symantec, please takeover this case until my server upgrade to latest version is done.

History:
1) SEPM is working fine 11.0.2.000 1567
2) I have recieved SEPM license for V12 in March and still I cant upgrade due to DB size which was 8GB few days back and now 11.7GB. I cant control it.
3) I dont have 3 times disk space of DB size, I want to reduce the DB size but it is growing unexpectedly.
4) I have recovered the First installation password for DB.

Problem Discription:
1) I cant connect ODBC. See my settings below:
  User: DBA
  Password: first password
  Server Name: RH-OCS
  Databas Name: SEM5
  C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5
  TCP/IP: 192.168.1.106

  Error: if I enter IP: Connection failed: connection error: error in TCPIP port options
  If I check IP then: Connection failed: Unable to start database server.

2) I must need to unload the DB to reduce size, my question, if My DB is 11.7GB, how much it will after shrink?
3) Why it is growing too fast unexpectedly?
 

Please note from last two months I am not able to step up just because of DB size and disk space issue. I cant increase disk space so I must deal with DB. Secondly I tried to tune up DB maintinance, log entries to reduce DB size but nothing works.

Thank you very much.

Hello,

SEP 11.0.2000 is an old version released in Apr 2008.

Yes, Migration is surely required.

In your case, take the backup of the database before performing the document.

Also : ODBC test and server certificates

Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager
http://www.symantec.com/business/support/index?page=content&id=TECH102333&locale=en_US

How to shrink the embedded database using the Dbunload tool
http://www.symantec.com/docs/TECH104278

(Note : The size depends on the number of client in the SEPM)

Disk Space Management procedures for the Symantec Endpoint Protection Manager

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

Best Practices for configuring the number of content revisions to keep in Symantec Endpoint Protection Manager
http://www.symantec.com/docs/TECH92225

SEPM has large number of files in the \SEPM\Inetpub\content folder
http://www.symantec.com/docs/TECH102891

Hope that helps!!

Did you open a support case with Symantec? If not, I would suggest doing this so they can work with you to get this taken care of.

you have 11.0.2000? thats the oldest version I know so far. how many clients you have in your  network?

if you have less numbers then you run a fresh install of latest 12.0 version.

as far as db connection is concerned

try providing the port number.

is the db service started:

in the tcp / ip option. you need to add port number 2638

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

1) Just opened the case with Symantec

2) 30 Clients only

3) It does not work even the port numbers 192.168.1.106:2638 or port number alone or IP alone...nothing works

4) DB service is started and I am able to work inside SEPM.

If I were you, I would just make a fresh start on a new server with the latest SEP 12.1.2 MP1 and reconnect your clients using the CDW:

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

If you need to use the same host server, fully remove the existing SEPM, database and backups and start fresh.

MJD

Hi

Please check the free space available in SEPM

Regards

DB Size 11.7GB

While free space in C:\ is 13GB. After removing virus definations and stuff it is now 18GB.

Can I delete content in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\content ??

Not recommended to remove it manually - this is the mirrored content from the database. If you won't to limit here the space used by content definitions updated - change the settings for definitions updates stored on the SEPM :

How to change the number of downloaded content revisions that are retained by the Symantec Endpoint Protection Manager versions 11.0. or 12.1

Ok,

I was able to perform DBUNLOAD safely. Now DB size is 4GB and I have more three time space of DB size.

I am going to follow best practise upgrade article, would you guys stay with me incase of any urgent help required?

Regards

we will be here

for 30 clients with SEP 11.2000 its better to do a fresh install.....a start from the scratch so that you can be bug free :) 

I am thinking for upgrade. I must trust Symantec, if it fails I will never trust Symantec.

Ok. I am dowingloading following files:

Symantec_Endpoint_Protection_12.1.2_MP1_SEPM_EN.exe 12.1.2 MP1 = 08-Apr-2013
Symantec_Endpoint_Protection_12.1.2_MP1_Win32-bit_Client_EN.exe = 08-Apr-2013
Symantec_Endpoint_Protection_12.1.2_MP1_Win64-bit_Client_EN.exe = 08-Apr-2013

My question is that, is it latest build of Symantec 12?
Second, should I use this downloaded client versions for client upgrade or fresh install?

But before we used to download the package inside SEPM, now it is seprate or what, please explain.

My question is that, is it latest build of Symantec 12?

- yes

Second, should I use this downloaded client versions for client upgrade or fresh install?

- as you are on very old 11.x version, fresh install will be more reliable

But before we used to download the package inside SEPM, now it is seprate or what, please explain.

- on the fileconnect you will find as well the download of the full installation = clients + sepm

Symantec_Endpoint_Protection_12.1.2_MP1_Part1_Installation_EN.exe -> beside that afte you install the SEPM - you can push the client packages directly from the manager

Thank you all!

Upgrade was smooth.

Now I will be working on upgrading clients. Stay with me!

Hello,

After Migration of SEPM, the best way to migrate the clients is going with Auto-upgrade.

Upgrading clients by using AutoUpgrade http://www.symantec.com/docs/TECH96789

Upgrade clients to SEP 12.1 by Auto upgrade feature

https://www-secure.symantec.com/connect/articles/upgrade-clients-sep-121-auto-upgrade-feature

NOTE: Clients that are Group Update Providers (GUPs) should be upgraded before other SEP clients

Secondly, check this Article:

Best practices for upgrading to Symantec Endpoint Protection 12.1.2

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

Hope that helps!!

So far everything is going well.