Documentation forAccess Rights Manager

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 your 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 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.

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 at learn.microsoft.com.

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. Click OK.
  7. Create a backup.

Create a backup

For more information, see Create a Full Database Backup located on the Microsoft Learn website.

  1. Set Backup type to Full.
  2. Set Destination to Disk.
  3. Add a Destination. SolarWinds recommends using the default path for backups. For example: C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Backup\. Add the extension .bak to the file name.
  4. (Optional) Remove any backup destinations that are not required or needed.
  5. Click OK.

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 instance

For more information, see Restore a Database Backup Using SSMS located on the Microsoft Learn website (© 2020 Microsoft Corporation, obtained on February 17, 2020).

Access the Restore Database window

  1. Connect the object explorer in SSMS to the new instance to which the ARM database is to 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

  1. Select Source Device.
  2. Click the ellipsis button to select the backup devices.
  3. Click the Backup media type drop-down menu and select File.
  4. Select the file and then set the path to the copied backup file (.bak).
  5. Click OK.

(Optional) Change the database name

  1. In the Database field, enter a new database name.
  2. Click OK.

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 object explorer expand Security > Logins.
  2. Double-click on the login that you want to use for ARM.
  3. Set the login permissions.

Set the login permissions

  1. Select User Mapping.
  2. Select the restored database.
  3. Select db_owner.
  4. Click OK.

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.

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.
  3. Select Start in the contextual menu.

Re-enter the Basic Configuration information

Start and log in to the ARM configuration application. Within a few seconds, the configuration application automatically switches to the Basic Configuration, as shown in the following illustration.

Perform the following steps to re-enter the Basic Configuration information:

  1. Re-enter the Active Directory credentials.

    You can use the same credentials as before the migration. SolarWinds recommends using the service account credentials. For Windows authentication, these credentials are also used for the SQL login.

  2. Enter the following:

    • New SQL server name

    • Instance

    • Database name

    • SQL login credentials (if SQL Server authentication is required)

  3. Verify that your settings are valid.
  4. Save the new Basic Configuration.

The ARM service will restart, which may require a few minutes. 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.