Quantcast
Channel: THWACK: All Content - Server & Application Monitor
Viewing all articles
Browse latest Browse all 12281

SAM migration question

$
0
0

Hi folks

 

We currently have a single SAM (6.1.1) server installed on a windows 2008 R2 Enterprise server, and would like to migrate the installation to a separate Windows 2008 R2 Standard server and at the same time upgrade to SAM 6.2.1

The DB is stored on a separate server cluster.

So far I've set up the new server OS to mirror our current SAM server. I've also already moved the SAM security certificates over, as there should be no changes from now to the migration. (Is there any reason this is so late in the process in the documentation?)

 

So I'm trying to get a handle on what the procedure will be, since I wasn't involved in the original installation. Does the following sound about right?

 

1) Stop Solarwinds Services on the current server

2) Get our DB team to backup the solarwinds databases

3) Get a VM snapshot of the current server

4) Install License Manager on the old server, deactivate the license, and activate it on the new server.

5) Run SAM installation on the new server with an evaluation license. Run advanced configuration and point it at the existing DB.

6) Reassign Nodes to the new server on the database

 

If everything goes smoothly, is there anything I would need to set up separately on the new installation? Am I correct in thinking I'll need to set up my alerts again? Any gotchas I should look out for?

 

And the final question - If something goes wrong and I need to roll back, can I just stop all services on the new installation, deactivate/reactivate the old license, restore the DB and just start services on the old server again? Is step number 3 needed or would it be better just to start the server up again?

 

Any help would be much appreciated.

 

Thanks and regards

Rodrigo


Viewing all articles
Browse latest Browse all 12281

Trending Articles



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