Hello,

I am testing the move of a SEP Manager running on a Windows Server 2003 R2 that is using a separate SQL Server database for SEP to a Windows Server 2008 R2 server using the steps described at http://www.symantec.com/business/support/index?page=content&id=TECH160736

As I am using a external SQL Server, do I need to restore the database that I've backed up on the previous steps? Because when I reinstalled the SEP Manager in the other server using the recovery file, I've connected to se SQL Server that I was using alongside the old SEP Manager server and the wizard told me that there was data on that database and asked if it should keep those or cleanup the database.

Thanks!

See here

How to move Symantec Endpoint Protection Manager 12.1 from one machine to another

Is the IP/hostname staying the same or changing?

install a new SEPM

restore the backup 

update the keystoke file

See Chetan articles

How to move SEPM from one server to another server.

https://www-secure.symantec.com/connect/articles/how-move-sepm-one-server-another-server

If the SEPM server keeps the same IP and host name, you can refer to "Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager"

Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

How to move Symantec Endpoint Protection Manager 12.1 from one machine to another

As you have an external DB already, none of the long-winded migration articles are really needed here.  Assuming you're happy for the new SEPM to have a different name and IP address you can just do the below:

1. Install new SEPM as "Additional Server to Existing Site" (essentially creating a multi-SEPM site)
2. Create a new Management Server List that tells your clients to talk to the new SEPM only and assign everywhere (allow time for clients to apply)
3. Shutdown old SEPM
4. Verify continued management and communciations with clients
5. Log into new SEPM and delete old SEPM from the Site's server list
6. Done

No messing around with backups or DR steps.

#EDIT#

Oh yeah, the bleow articles should aid in the above steps:

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

http://www.symantec.com/docs/HOWTO81154
http://www.symantec.com/docs/HOWTO80735
(New MSL should list only the new SEPM)

Thank you all! the solution SMLatCST gave me solved my problem!

Glad you go it! Don't forget to mark his post as solved so it can help admins looking for a resolution to the same problem.

Thanks and take care!

Brian