Migrate the ARM database to a new SQL server

If you are running Microsoft SQL Server Express Edition in your deployment, you can migrate your ARM database to an SQL Server instance. This SQL version is required for large deployments in a Production environment.

1. Record the current configuration credentials, including the currently used credentials, SQL server, and authentication method.

2. Stop the ARM service on the ARM server.

3. Back up the ARM database using SQL Server Management Studio (SSMS).

4. Copy the backup file to the default backup folder of the new database instance.

5. Restore the ARM database to the new database instance.

6. Set the login permission on the new SQL server instance.

7. Edit the ARM server configuration file.

8. Start the ARM service on the ARM server.

9. Re-enter the basic configuration settings.

Record the current configuration credentials

1. Start the ARM Configuration application.
2. On the home screen, click Basic Configuration.
3. In the ARM Server and SQL Server sections, record the currently user credentials, SQL server, and authentication method.

Stop the ARM service

Stop the ARM service running on the ARM server. This process ensures that users are not accessing ARM during the database migration.

1. Start the services.msc console.
2. Right-click ARM-Service.
3. Select Stop from the context menu.

Back up the ARM database

Create a backup copy of the ARM database using SQL Server Management Studio. You can download SQL Server Management Studio (SSMS) from the Microsoft Learn website located on the Microsoft Learn website.

Access the ARM database

1. Open SSMS.
2. Using the information you obtained in a previous section, log in to the instance where the ARM database is currently stored.
3. In the Object Explorer, expand Databases.
4. Right-click the ARM database.
5. From the context menu select Tasks > Back Up.
6. Save your changes.

Create a backup

When you create a full database backup in SSMS, perform the following steps:

1. Set the Backup type to Full.
2. Set the Backup component to Database.
3. Set the Destination backup to Disk.

4. Add a destination to the backup file.

   SolarWinds recommends using the default path for backups:

   C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Backup\.

   Ensure that the backup file name is appended with the .bak file extension. For example:

   backup_file.bak

5. (Optional) Remove any backup destinations that are not required or needed.
6. Save your changes.

Copy the backup file

After the backup is completed, copy the backup file (.bak) to the default backup folder of the new database instance.

Restore the ARM database to the new database instance

Access the Restore Database window

1. Connect the Object Explorer in SSMS to the new instance where the ARM database will be moved.
2. Right-click the Databases node.
3. From the context menu, select Restore Database.
4. Restore the database.
5. (Optional) Change the database name.

Restore the database

When you restore the database in SSMS, perform the following steps:

1. Select Device as the source.
2. Select the backup devices.
3. Click the Backup media option and select File.
4. Select the file and set the path to the copied backup file (.bak).
5. Save your changes.

(Optional) Change the database name

To change the database name in SSMS, enter a new destination database name and then save your changes.

Set the login permissions on the new SQL server instance

After the restore is completed, check/set the Login properties on the new instance. You can use an existing login or create a new login. SolarWinds recommends using a service account to perform this procedure.

Access the Login Properties window

1. In the SSMS Object Explorer, expand Security > Logins.
2. Double-click the login you want to use for ARM.

Set the login permissions

When you set the login permissions in SSMS, perform the following steps:

1. Select User Mapping.
2. Select the restored database.
3. Select db_owner.
4. Save your changes.

Edit the ARM server configuration file

Before you begin, navigate to the %ProgramData%\protected-networks.com\8MAN\cfg directory and back up the pnServer.config.xml file to another location.

1. Log in to the ARM server with administrator privileges.

2. Edit the configuration file.

   

   1. Open the pnServer.config.xml file with administrator privileges.

   2. Delete the database and the credentials tags (including tag content).

   3. Save your changes.

Start the ARM service on the ARM server

1. Start the services.msc console.
2. Right-click ARM-Service and select Start,

Re-enter the basic configuration settings

1. Log in to the ARM Configuration application.

   The application automatically switches to the Basic Configuration screen.

2. Under ARM Server, re-enter the Active Directory credentials.

   

   You can use the same credentials that were valid prior to the migration. SolarWinds recommends using the service account credentials. For Windows authentication, these credentials are also used for the SQL login.

3. Under SQL Server, enter the SQL Server settings.

   

   1. In the SQL Server name field, enter the name or IP address of the SQL Server database server.

      If SQL Server is running on the same machine as the ARM Server, you can enter localhost or local.

   2. In the SQL Server instance field, enter the name of the ARM database instance.

   3. In the SQL Database Name field, enter the name of the ARM database.

   4. If SQL Server authentication is required, enter the SQL Server user name and password.

4. Under Configuration Status, click to test your basic configuration settings.

   If the settings are valid, Test successful displays in the window for each setting.

   

5. Click to save the basic configuration settings.

   The ARM service will restart, which may require several minutes to complete. During the restart, the connection between the ARM server and the configuration application will be lost. A warning message in a red frame will be displayed. This behavior is expected. Wait until this process is completed.