Relocating the SentryOne Database

Moving the SentryOne database to a new SQL Server instance

Shared steps:

These steps are the same for the EPI and non-EPI versions of SentryOne. Move the SentryOne database to a new SQL Server instance by completing the following steps:

  1. Obtain the new Server Name or Group_ID that you plan to host your SentryOne datbase on. This is used to regenerate your license key because it's based on one of these values.
    1. If you plan to use a standalone or Failover Cluster instance for hosting your SentryOne database then you can get the Server Name by running the following T-SQL statement SELECT SERVERPROPERTY('SERVERNAME').
    2. If you plan to host your SentryOne database in an Availability Group then you can get the Group_ID by running the following T-SQL statement: SELECT group_id as AG_ID, name
      FROM sys.availability_groups.
  2. Login to the Customer Portal and go to the License Maintenance section. Select View / Modify Existing SentryOne Licenses and complete the following:         
    1. In the Perpetual Licenses section your SentryOne license is listed. Select the plus symbol next to the instance name to expand the license management options.
    2. Select the License Configuration tab.
    3. In the SQL Server Instance Name field enter the new instance name from step one.
    4. In the Reason For Change field, enter a reason for the change.
    5. Select Update and the license is automatically emailed to you.
  3. Once you've received the new key, shut down all SentryOne clients and SentryOne monitoring services.
  4. Perform a full backup of the SentryOne database.
  5. Set the SentryOne Databases to Offline.
  6. Restore the SentryOne database to the new location that's used to host the SentryOne database.

Next steps:  non-EPI

  1. Open the SentryOne client on any machine with a SentryOne monitoring service. After failing to locate the SentryOne database, the Connect window appears. Enter the new location of the SentryOne database. The SentryOne client alerts you that it needs to be restarted to connect to the new SentryOne database. Upon restarting, you are asked for the new license key.
  2. After successfully applying the license and starting the SentryOne client, run the Service Configuration Utility, pointing the monitoring service at the new SentryOne database. The Service Configuration Utility is found in the SentryOne program group. After running the Service Configuration Utility, restart the monitoring service.

Note:  Repeat steps 7 and 8 on all machines with SentryOne monitoring services. You won't be asked for the license again. You may now start any other SentryOne client and enter the new SentryOne database location when asked.

Next steps:  EPI

  1. Uninstall the services:
    so uninstall -n <connectionName>
  2. Add the new registration
    so addreg -n <connectionName> --connectionServer <serverName> --connectionDatabase <databaseName> 
  3. Re-install the services
    so install -n <connectionName> -u <serviceAccount> 

Note:  Repeat steps 7, 8, and 9 on all machines with a SentryOne controller service or monitoring service.

Additional Information: See the EPI article for guidance on using these commands.

Final steps

Once you have validated that the SentryOne platform is working as planned with the database on the new server, you can remove the old database from the server that was hosting it.

Success: Your SentryOne database has been relocated.

Important:  Don't forget to set up SentryOne database maintenance on the new server.

Removing an old server from the All Instances view

Remove an old server from the All Instances view to stop prompts about it when opening the SentryOne client by completing the following steps:

  1. Select the server name of the server you'd like to remove in the Please Specify the Server Name drop-down list, and then press Shift + Delete. 
  2. The new server should now be the only one listed in the drop-down list. Select the Connect command and connect to the new installation.

 Success: The next time you open the client it will automatically connect to the new installation.