After reviewing the options for migrating SEPM 12.1 from one server to another, it appeared replication would be the easiest. However, if we already have a SQL database for SEPM 12.1 stored on our SQL server, if we replicate the SEPM 12.1 server, it will create another SQL database for the new server correct? Should we setup the new server as using an embedded database instead before we replicate this way it does not create another database or am I off track here?

 

It shouldn't create another DB. It will be mirrored to the new install.

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

Article:TECH171767

|

Created: 2011-10-13

|

Updated: 2012-07-10

|

Article URL http://www.symantec.com/docs/TECH171767

 

Replication method

Symantec Endpoint Protection clients will be able to reach the new SEPM using new communication settings, the database will be mirrored from the previous installation to the new installation via replication. The management server list will then be updated accordingly and sent automatically to clients.

It will be same DB mirrored.

If you have sql db. you can install new sepm. restore the db, update the communication settings.

How to deploy/update communication settings from your SEPM to your SEP clients machines with SEP 12.1 RU2

 

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

Hi cra2323,

if we already have a SQL database for SEPM 12.1 stored on our SQL server, if we replicate the SEPM 12.1 server, it will create another SQL database for the new server correct?

-->  Yes it would create another database for the new server.

Should we setup the new server as using an embedded database instead before we replicate this way it does not create another database or am I off track here?

--> Yes it won't create another SQL database. It would create only embedded database on SEPM installed machine.

Check this article as well

Hot to move SEPM from one server to another server.

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

Helpful other articles:

Best Practices guide for moving the Symantec Endpoint Protection Manager SQL Server database from one drive to another on the same machine

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

Best Practices guide to moving the Symantec Endpoint Protection Manager SQL Server database from an existing SQL Server database to a new SQL Server database

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

Best Practices guide to moving the Symantec Endpoint Protection Manager SQL Server database from an existing SQL Server database to a new SQL Server database

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

 

Ok, I'm trying to picture this. We currently have the database stored on a SQL server, not locally on the SEPM server. When I install SEPM on the new server to be replicated, If we replicate, how does that affect the current SQL database? We plan to have a new name and IP for the SEPM server. When I install SEPM on the new server, part of the install process asks me to pick either embedded or SQL. If I put in the SQL server information, will it create another SQL databse for the new server since it has a new name and IP? I guess what I really need to ask is: What is the best and easiest way to migrate a SEPM 12.1 server that uses a SQL database that is not stored locally?

Hi,

When I install SEPM on the new server, part of the install process asks me to pick either embedded or SQL. If I put in the SQL server information, will it create another SQL databse for the new server since it has a new name and IP?

--> No it won't create until and unless you select 'create a new database'

You can check it here: https://www-secure.symantec.com/connect/articles/sepm-121-fresh-installation-sql-database-graphical-overview

I guess what I really need to ask is: What is the best and easiest way to migrate a SEPM 12.1 server that uses a SQL database that is not stored locally?

--> I would suggest install new SEPM and connect it to the existing remote SQL database. Refer the following article to do that.

Disaster/Recovery- How to rebuild and restore your #1 Symantec Endpoint Protection Manager and re-connect it to your existing SQL database

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

 

Sorry about asking the same questions twice, I did not see the other reply's when I posted the second time. Thanks Chetan, thats what I was looking for! All the other posts/info that I saw talked about local DB's.

Hi,

Do you have that link with you when you posted the second time?

Yes. I got the link http://www.symantec.com/docs/TECH134475 and we are about to follow the steps. Really appreciate the help! One more question... Since we still have our SEPM server online but want to replace it with our new one using the same name and IP's, can we just do the following: 1. Perform the backups as per the link you posted. 2. Remove the current SEPM server from AD and rename the new SEPM server to be to the same name and IP's THEN follow the rest of the directions you linked? Will this cause an issue?

If you are planning to remove the first SEPM completely from the environment I believe this KB should answer your questions: http://www.symantec.com/docs/TECH104389

Thanks, I did see that article before but I do not think it is quite what we are trying to do. We currently have a functioning SEPM server and now want to try this method (Disaster/Recovery- How to rebuild and restore your #1 Symantec Endpoint Protection Manager and re-connect it to your existing SQL database) http://www.symantec.com/docs/TECH134475 as linked by Chetan, to replace it with a new SEPM server using the same name and IP's.

Being that all the data is already stored in a SQL database on another server and all we have to do is restore backups and re-connect it to our existing SQL database, the question I have is, what to do with the exisiting SEPM server now? If I just shut it off, removed the object from AD or just rename it to something else, rename the new SEPM to the same name and IP's, follow the directions in the link thus restoring the configs, keys etc, and reconnecting it to SQL, will that not work?

What would happen if the original SEPM server just fried today? The only option I would have would be to remove from AD, rename replacement server to match the fried server name using the same IP's, restore backup files, and reconnect to SQL database correct? So could I not simulate that by doing the same now? (leaving out the frying the server part of course)

check this link,

 

 

REPLICATION

 

Best practices for replication server sizing

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

 

How to add "Replication Partners" and Schedule Replication

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

Best Practice for setting replication frequency
http://www.symantec.com/business/support/index?page=content&id=TECH91509

 

How to install the Symantec Endpoint Protection Manager(s) for replication

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

 

How to Perform Offline Replication between 2 Remote SEPM

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

Hi,

Before installing new SEPM in the network with the same hostname & ip address you will have to remove existing SEPM machine from the network. Otherwise it would be a conflict in the network.

 

Thanks for the help everyone! It turns out our plan and the link Chetan posted did the trick. Since our SEPM database was located on our SQL server, not locally, we were able to easily point the new SEPM server to it without going through all the process of the above links. I figured there had to be an easier way. The screenshots on the link were a bit out of date and had a few different steps not listed but overall it was easy to follow. For anyone who is interested we did the following: 1. We took our current SEPM 12.1 server and renamed it. 2. In DNS, we created entries still pointing to the original SEPM server so that the clients still had connection. 3. We renamed the new SEPM server to match the original one. 4. I installed SEPM 12.1 on the new server and followed the steps here: http://www.symantec.com/docs/TECH134475 5. At the point where I had to update the certificate I shut down the original SEPM 12.1 server and finished the process in the link. 6. I changed the IP's to match what the original SEPM server had and rebooted the server. 7. The clients lost the green dot on the shield and after a short while, without rebooting the clients, the green dots came back. The post said to reboot clients but it may appear that may not be necessary. Done! Nice and simple. If you want to swap out a new server that has a separate SQL database, with the same version of SEPM, and same name and IP, this was a very easy way to go. Personally, I found the guides listed here seemed to confuse me more than help! Hope this saves someone a lot of time in the future!