Quantcast
Channel: Symantec Connect - Products - ディスカッション
Viewing all articles
Browse latest Browse all 11815

Will this work? SQL DB & SEPM Move

$
0
0
ソリューションが必要です

Hello,

Our SEPM servers 12.1.5 and the SEPM DB ( SQL 2008 64bit) server is in an unmanaged area of the network and we are trying to move them over to the managed (DB) area of the network.  Below is the plan that we are thinking and testing in.  If you agree with the plan, can you answer the question in 6C and also steps 8-10?  I have already looked at http://support.microsoft.com/kb/224071/en-us and http://www.symantec.com/docs/TECH104723

 

1.  Shutdown the SEPM related services on SEPM servers.

1.png

2.  Create a "copy only" back up of SQL 2008 Database. (.bak file) on the Database server.

2.png

3.  Shutdown the SQL database server or services.

3.png

3.  On the new SQL server, open Microsoft SQL Server Management Studio, right click on Databases, click on tasks and click on Restore Database.

4.png

3A. In the "Restore Database" window, type in the field "To Database" the same name as the previous SEPM database, i.e: sepadmin

6_0.png

3B. In the "Source for restore", select radio button for "from device" and browse to the location where .bak file is and click ok , until execution starts of restoration.

3C.  Make sure that the new SQL server is set up for Mixed Authentication if that is what the OLD SQL was set up for.

4. Once restored, under object explorer, click on security -> logins and right click on the login and create the same login as was used previously to set up SEPM servers.

7.png

4A.  If SQL Server authentication, make sure that "User must change password at next login" is checked off

5.  Once the login is created, click on newly restored database and run the following query:

5A. use database_name
       go
       EXEC sp_change_users_login 'Update_One', 'sde', 'sde'
       go

for more information on this query, go to : http://support.esri.com/ja/knowledgebase/techarticles/detail/29672

6.  Once the restor is done, on a newly built windows server, install sepm, configure SEPM to talk to the new database.

6A.  Make sure to choose "Add an Additional" server in the configuration window.

6B.  Make sure that port 1433 or whatever port is being used for SEPM to SQL communication is opened from the new SEPM server to the SQL database.

6C.  All clients should be able to get to this new SEPM servers on port 8433, so make sure this port is open.  Are there any other ports that client and GUPS needs to be able to talk to the new SEPM servers?

7.   Once the new SEPM server is added and functioning:

7A.  Start SEPM configuration on the OLD SEPM servers.

7B. In the configuration, reconfigure the SEPM servers to point to the new Database.

7C. Make sure that port 1433 or whatever port is being used for SEPM to SQL communication is opened from the OLD SEPM servers to the New SQL database Server

8.  Keep both old SEPM servers and New SEPM server on for couple days (or whatever the time frame is for the heartbeat of clients so that the new SEPM server is updated on the management server list on the clients.

9.  After couple days, delete the old SEPM servers from the SEPM Management console and update the management server list.

10.  Now all clients should be talking to the new SEPM server and new SQL servers.

 

 

 


Viewing all articles
Browse latest Browse all 11815

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>