Moving your xMatters database from one machine to another

This article describes the steps necessary to migrate an instance of the xMatters database from one computer to another. This article applies to both Oracle and SQL Server deployments.

Step One: Stop all xMatters components

Before making any changes to the database, you must stop all xMatters components that access the database, such as web servers, Notification servers, Application servers, and the xMatters Developer IDE.

To stop xMatters components:

  1. Log into xMatters as a Super Administrator.
  2. On the Admin tab, click Nodes and Device Engines.
  3. On the Nodes page, select all of the Nodes in the deployment, and then click Stop Selected.
  4. Log out of xMatters.
  5. On each machine hosting an xMatters webserver, use the command line to navigate to the xMatters installation directory, and then do one of the following:
    • On Unix systems, run the following command:
sh webserver.sh stop  
  • On Windows systems, run the following command:
webserver.bat stop  
  1. Close any instances of the xMatters Developer IDE.

Step Two: Back up your database

Before attempting to move your database to another machine, be sure to run your full backup procedures to preserve your existing data.

The process required to perform this step is dependent on your specific database. For more information, consult your database documentation.

Step Three: Copy your backup to the new machine

The easiest way to transfer your data to another machine is to copy the backup file to the new location.

Step Four: Restore your database to the new location

On the new database machine, use your database software to restore the information. When specifying the details for the new instance (such as database name, login name, authentication and password), use the same details as the original installation.

The process required to perform this step is dependent on your specific database. For more information, consult your database documentation.

Step Five: Redirect all xMatters components to use the new database

Note: This step is not required if the IP address of the new database is the same as the original installation, and if the login ID and password of the xMatters database user were not changed.

To update either the IP address or the login credentials of the xMatters database, you must update the connection information for each Node and web server, stored in the common.properties file. The file is encrypted; to modify it, you must decrypt the file, make the modifications, and then re-encrypt the file. For complete details on how to configure the database connection settings, see the FAQ here.

Step Six: Start all xMatters components and test.

To restart xMatters components:

  1. On each machine hosting an xMatters webserver, use the command line to navigate to the xMatters installation directory, and then run one of the following commands:
    • On Unix systems:
sh webserver.sh start  
  • On Windows systems:
webserver.bat start  
  1. On each machine hosting an xMatters Notification or Application Server Node, use the command line to navigate to the xMatters installation directory, and then run one of the following commands:
    • On Unix systems:
sh node.sh start  
  • On Windows systems:
node.bat start  

To test the xMatters database connection:

  1. Login to xMatters.
  2. On the Admin tab, click Nodes and Device Engines.
  3. On the Nodes page, confirm that Activity State for all Nodes is Running.

xMatters Reference

JDN-1072 Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk