Endpoint Protection

Hi all,

Has anyone moved their SEPM 12.x SQL Server database from one server or version to another successfully?  Can I just have our DBA copy it from a SQL 2005 SP3 server to a SQL 2012 server?  I found out that SEP 12.1.2015.2015 (RU2) requires a backend SQL of 2008 or higher.  Before upgrading from SEP 12.1.1000.157 (RU1) to SEP 12.1.2015.2015 (RU2) I think I want to move the SEPM SQL database from 2005 SP3 to SQL 2012 first. 

I've been reading through multiple docs but I wanted to ask for some clear advice on this upgrade procedure.  Would these steps work?  If not what should be changed?

• Backup the SEPM database via SEPM console.
• Stop the SEPM service.  (I don't have replication.)
• Have my DBA copy the SEPM database from SQL 2005 SP3 to SQL 2012.  I think I can keep the same database name.
  • At this point I presume a SQL username has to be created on 2012 that will access the copied SEPM database.  I think I should be able to use the same one that existed on SQL 2005 SP3.
• On the existing SEPM RU1 server, run the Management Server Configuration Wizard and point to the new SQL 2012 database.
  • At this point, do I have to somehow tell the clients that there's a new SQL database and it has moved?  Or is it enough that the SEPM console knows it's been moved?
• Now I think I'm ready to upgrade the SEPM console from RU1 to RU2 (install over-the-top).  And then upgrade the clients from RU1 to RU2.

Will simply having my DBA "copy" the SQL database work?  Will I have to run the sylink updater for anything?

Thanks much, Tom.

I have not personally but these KBs should give more insight:

Moving the SEPM database to a new SQL server or instance using SQL backup/restore

https://www.symantec.com/business/support/index?page=content&id=TECH132761

How to move the Symantec Endpoint Protection Manager SQL database to a new SQL Server

https://www.symantec.com/business/support/index?page=content&id=TECH174821

SEPM 12.1 RU 2 compatible SQL 2005 SP4

pete_4u2002, I forgot to mention our SQL 2005 is SP3 -- and there's no plans to patch it.  So I'll just go to SQL 2012.  Thanks.

Hey Brian81, I had found KB 132761 but that sounded like moving from an embedded database to a SQL server.  However, I didn't see the other KB 174821.  That sounds more like what I'm trying to accomplish.  Thanks.

Since my SEPM is on a VM I had already actually tried the upgrade from RU1 to RU2, but was stopped when it said the SQL database needed to be 2008 or higher.  I think once the SQL database is on a supported version, the RU1 to RU2 upgrade should go OK.

Keep in mind that SQL Server 2012 is supported not before SEP 12.1 RU1 MP1 (12.1.1101.401). See this thread:

http://www.symantec.com/connect/articles/what-s-new-sep-121-ru1-mp1

greg12, thanks for reviewing my steps I outlined and finding an issue.  So based on the article you site and my current environment, the steps I outlined won't work.  That is, because SEP 12.1.1000.157 (RU1) does not support SQL 2012.

However, I rechecked my environment and had forgotten that I have actually already upgraded my SEPM console to 12.1.1101.401 (RU1 MP1).  My clients are still 12.1.1000.157 (RU1), but the SEPM console is RU1 MP1.  A while back I upgraded the SEPM console and stopped at that point when I found issues with the BASH drivers on the clients during testing.  So I've been waiting for this new release SEP 12.1.2015.2015 (RU2).

If clients send their data to the SEPM console and the SEPM console sends it to the SQL database, then theoretically my steps should work.

Since my SEPM console is RU1 MP1, do you (or anybody else) think that moving the database from SQL 2005 SP3 to SQL 2012 will still work?

Thanks, Tom.

For upgrades I never used the same versions as you, but  the workflow of your OP seems perfectly fine with SEPM 12.1 RU1 MP1.