Endpoint Protection

Hi All.

One of my SEPM servers has died. unfortunately, before it died it hadn't replicated with it's partner for sometime but it went un-noticed.

anyway, I have one working SEPM server, which is a bit out of date - but still better than nothing

I want to migrate away from the embedded DB onto a SQL server hosted DB - what guides, info is there to do this?

cheers

try this 

Symantec Endpoint Protection Manager: Moving from the Sybase Embedded Database to Microsoft SQL Server

http://service1.symantec.com/support/ent-security.nsf/docid/2007092722095248

Symantec Endpoint Protection Manager: Moving from the Sybase Embedded Database to Microsoft SQL Server

http://service1.symantec.com/support/ent-security.nsf/docid/2007092722095248

thanks guys - I'm right near the end of this document - i'm trying to do the restore of the database but it's failing.....???

Do you get any error message ? a pop up? 

Perform a disaster recovery when the database backup/restore process fails using the "Database Backup/Restore Wizard" for an Embedded Database

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/3ad47116f1eaf81265257410005ed2ac?OpenDocument

just gonna try run again for the error mesage

I can't do the disaster recovery as I no longer have the sem5 database from this server.....

I have a sem5 database off the working (out of sync) server but don't want to use that as it's very much out of date......

ok  -forget that - restore worked ok 3rd time lucky :-/

on with the next bit now

cheers

If you have followed the document Symantec Endpoint Protection Manager: Moving from the Sybase Embedded Database to Microsoft SQL Server correctly, you should see the recent backup of the database in the location below:
C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\backup\

Do a ODBC test before restoring the database to ensure that the SQL database is connected to the manager

How-To:

• Verify SQL Server is running and properly configured.
• Verify the network connections between Symantec Endpoint Protection Manager and the SQL database.
• Test the ODBC connection.
  1. Click Start> Control Panel
  2. Open Administrator Tools
  3. Double-click Data Sources (ODBC)
  4. Select the System DSN tab
  5. Double-click SymantecEndpointSecurityDSN and go through the wizard to ensure the following settings:
     • Name: SymantecEndpointSecurityDSN
     • Description: <Anything>
     • Server: Servername\InstanceName (Only enter the server name or IP address if using the default instance)
     • Login ID: sa
     • Password: <password>
       
  6. Leave the defaults for the rest of the items and click Finish
  7. Click Test Data Source on the next page and ensure it states "Success"
  8. Click OK
  
  

Now try restoring the database. It should restore the database to the SQL server.

Perfect, lets get going now :)  

ok - it's up - data is there, great.

but looking at the admin=>servers section form the console, it thinks the database server is 'localhost' when that's not the case, it's actually on a seperate SQL server?

oh forget that too - although it says localhos, when I click it it shows the SQL server - phew

ok, next question

do I still need replication set up to my secondary server, or do I somehow need to reconfigure the secondary server to point to this DB?

cheers

you need to replicate or stand alone?
When you choose replication you need to select the second option: ? did you?
http://service1.symantec.com/support/ent-security.nsf/docid/2008091703483748 

well I don't want them to be stand alone - I need them to be fault tollerant

I'm just saying - when I was using embedded DB the 2 servers replicated - but my question is - now that I've converted the DB from one server onto SQL should I reconfigure the secondary server to share that DB - or should it keep it's own embedded one?

You need to  replicate them.
Since we installed new  i dont think the other one will have information.

ok - well I think it's replicating

but isn't it a bit odd that one SEPM server now has a SQL database and the other has just an embedded one?

cheers

 it doesn't matter in case of replication.

Though they have different DB to hold the data.
The way they send and receive updates are same. SEPM does upload the logs and fill the DB, as fas as sepm's are on same versions there wont be a problem.. 

ok - that's great - thanks everyone (especially Rafeeq)

looks like I'm back up and running....hope this replication finishes soon

:-)