1/21/2020 4:36 PM

1/21/2020 4:36 PM

This is a how-to guide if you want to migrate your ARM installation to a new server.

Access Rights Manager

You want to migrate your ARM installation to a new server because of an operating system upgrade.

Newer instructions are available at:

https://documentation.solarwinds.com/en/Success_Center/ARM/Content/migrate-the-arm-installation-to-a-new-server.htm

License

Legacy 8MAN licensing mechanism

Your current license file is named *.license and is located here:
%ProgramData%\protected-networks.com\8MAN\licenses
You will need this at the end of the migration to apply your license to the new server as described in
https://documentation.solarwinds.com/en/Success_Center/ARM/Content/load-the-license-file-and-check-covered-features.htm
 

SolarWinds ARM licensing mechanism

You need to deactivate the license on the old server and reactivate it later on the new server.
The deactivation is described in the following chapter:
https://documentation.solarwinds.com/en/Success_Center/ARM/Content/transfer-a-license-to-another-server.htm
The activation is described in the following chapter:
https://documentation.solarwinds.com/en/Success_Center/ARM/Content/switch-from-an-evaluation-license-to-a-production-license.htm

​
Prepare the new server

• Make sure all system requirements are met: https://documentation.solarwinds.com/en/Success_Center/ARM/Content/System_Requirements/system_requirements.htm
• Set up the new server with the desired OS.
• Apply the latest Windows updates.
• Install the required .NET version(s).
• Make sure that the IIS role is activated.
• Stop and disable the ARM service on the old server. Copy all files and folders from %ProgramData%\protected-networks.com\8MAN to the same location on the new server. Please note that this process may take a while depending on the number and size of your scan archives.

Do not install ARM at this moment!

Migrate the database

If your SQL Server and database was located on the old server then follow the steps given here:
https://support.solarwinds.com/SuccessCenter/s/article/Migrate-ARM-SQL-database
to move your database to the new location.

When the database is available at the desired location, some adjustments have to be made. There are still entries with the old server name that are not automatically updated. The SQL Server Management Studio is required for this.

The following steps are only necessary if the name of the ARM server will change.

Update ARM server names

Check which values are currently set

Start the SQL Management Studio and log in to the instance where the ARM database is located. Execute the following SQL query on the ARM database. 
SELECT [_id],[_property],[_value]
FROM [_8ManDB].[dbo].[_server_configuration_object_values]
WHERE _value = '<ARM-SERVER-A>'
ARM-SERVER-A is the NetBIOS name of your old server and is written in capital letters.
Replace "_8ManDB" (legacy default) with the name of your ARM database name if necessary.

 

Update names

Replace ARM_SERVER-A with the NetBIOS of your old server.
Replace ARM_SERVER-B with the NetBIOS of your new server.
Replace "_8ManDB" (legacy default) with the name of your ARM database name if necessary.
update [_8ManDB].[dbo].[_server_configuration_object_values]
set _value = '<ARM-SERVER-B>'
WHERE _property = 'machinename' AND _value = '<ARM-SERVER-A>'

update [_8ManDB].[dbo].[_server_configuration_object_values]
set _value = '<ARM-SERVER-B>'
WHERE _property = 'gaffermachinenames.0' AND _value = '<ARM-SERVER-A>'

update [_8ManDB].[dbo].[_server_configuration_object_values]
set _value = '<ARM-SERVER-B>'
WHERE _property = 'selectedentrypoints.0' AND _value = '<ARM-SERVER-A>'

The number after gaffermachinenames and selectedentrypoints can vary.  Which ones are assigned, you could see during the check.
 

Update scheduled jobs

Check which values are currently set

SELECT [_id],[_property],[_value]
FROM [_8ManDB].[dbo].[_jobconfig_object_values]
WHERE _value = '<ARM-SERVER-A>'
 

Update scheduled jobs

update [_8ManDB].[dbo].[_jobconfig_object_values]
set _value = '<ARM-SERVER-B>'
where _property = 'destinationgaffers.0' AND _value = '<ARM-SERVER-A>'

The number after destinationgaffers can vary.  Which ones are assigned, you could see during the check.

Install ARM on the new server

Before installation, the copied pnServer.config.xml under %ProgramData%\protected-networks.com\8MAN\cfg should be checked. It may not be possible to use it directly, especially if the SQL server is local and the instance may have a different name or is not entered as localhost. In this case rename the copied pnServer.config.xml and create a new with the configuration wizard or the configuration application after the installation. All customizations can later be merged from the old configuration file into the new one.

Install ARM on the new server. You can only use the same ARM version that was installed on the old server. You cannot update or downgrade during the migration.
At the first step of the installation wizard select Advanced Installation. Follow the instruction of the Installation Wizard.

If you can reuse your old pnServer.config.xml then you don't need to complete the Configuration Wizard. Start the ARM configuration application and double-check the integrated resources and collector settings.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.