Endpoint Protection

 View Only
  • 1.  Migrating SEPM to another server, with remote database

    Posted Feb 23, 2018 11:20 AM

    Hi all,

    we are running SEPM 14 RU1 in a Windows 2008 R2 server, with a remote database in a SQL Server 2016. Our plan is to 'refresh' the OS of the SEPM server to Windows Server 2012 or 2016, installing the same SEPM version on it. Since they are virtual machines, I think my wintel colleagues will create a new instance of Windows Server 2016 with a different hostname and different IP for the new SEPM to be installed on it, and when the migration is completed, the old one will be decommissioned.

    I found this article: https://www.symantec.com/connect/articles/how-move-sepm-one-server-another-server  , the point 3.2 looks suitable for our case, but it deals with embedded database, not a remote database. How to proceed in our case? Is there any specific actions or measures having into account the remote database?. I do not know if using the recovery file, I still need to provide some database information during the installation process.

    Cheers!


     



  • 2.  RE: Migrating SEPM to another server, with remote database

    Posted Feb 23, 2018 11:26 AM

    The existing database server is not changing though, correct? Have a backup first then run the DR process once the new SEPM is ready.



  • 3.  RE: Migrating SEPM to another server, with remote database

    Posted Feb 23, 2018 11:30 AM

    Follow the disaster recovery method, the problem with replication is that, when you remove the replication , the first one will be considered as primary and might cause some difficulties when you wanted to expand it in future.



  • 4.  RE: Migrating SEPM to another server, with remote database

    Posted Feb 23, 2018 11:44 AM

    Yeah, that's right Brian, the existing database will remain the same. So... there won't be any issues in the meanwhile if I link the new SEPM to the database while the old SEPM is still linked to the database as well? Besides that, if I use the recovery file described in the DR process, which information about the database will need to provide during the installation?

    Rafeeq, yes, you are right, I have not read well the first point 3.1 in the article https://www.symantec.com/connect/articles/how-move-sepm-one-server-another-server 

    Thanks both!



  • 5.  RE: Migrating SEPM to another server, with remote database

    Posted Feb 23, 2018 11:49 AM

    You can run DR on the new SEPM once it's up and point it to the DB. All clients will re-connect. Just make sure you follow the DR best practices.



  • 6.  RE: Migrating SEPM to another server, with remote database

    Broadcom Employee
    Posted Feb 23, 2018 01:11 PM

    Please remember to Mark a Solution if you received your answer here!  Thanks!



  • 7.  RE: Migrating SEPM to another server, with remote database

    Posted Feb 28, 2018 06:25 AM

    Hi,

    I keep on reading some documentation on that regard, so, I will follow the DR procedure, and after entering the Recovery file when installing the SEPM,  I will be asked to enter some database information for connecting the SEPM to the existing DB, and that would be all, I am right?

    I assume that having entered the Recovery file, I will not be asked to select if the installation is for installing my first site or an additional one, or any other options.

    Talking about the 'old' SEPM server, should it be powered off before linking the new SEPM to the database? I assume that could arise some problems with two SEPM consoles pointing to the same database, or clients that point to one or another SEPM. So, when all clients have reported to the new SEPM, we can consider decommissioning the old one.

    I wanted to have a clear picture of the steps and the information I will be asked before proceed.

    Thanks again!

    Cheers!