Backup, Restore, and Moving to a New Server

Applies to: Predict! Risk Controller 6 and Higher

 

Overview

Regular backups protect against data loss and allow Predict! to be restored, migrated to a new server, or duplicated into a test environment. This article covers each of these scenarios.

 

Best Practices — Regular Backups

Back up the following regularly:

• The Predict! database
• The entire Predict! installation folder (e.g. C:\prc6\)

Note: When restoring a MySQL database, drop the existing schema and import into a new schema with the same name. Do not import over existing data.

 

Restore Predict! on the Same Server

1. Stop the Predict! Risk Controller service.
2. Restore the Predict! database from the backup.
3. Restore the Predict! installation directory by overwriting the existing directory with the backup copy.
4. Restart the Predict! Risk Controller service.

Note: Ensure the database backup and installation directory backup were taken at the same point in time and match the same Predict! version.

 

Move Predict! to a New Server

Prerequisites:

• A backup of the Predict! database
• A backup of the entire Predict! installation directory
• A new licence from Risk Decisions (contact support in advance to avoid delays)
• The new server should have the same drive letter and equal or greater memory as the original

 

New Server Steps:

1. Install a fresh copy of Predict! 6 on the new server, using the same installation directory as the original.
   1. On the database parameters screen, select No Preparation to avoid corrupting the existing database.
2. Stop the Predict! 6 service on the new server.
3. If the service on the original server ran as a specific user (common with SQL Server Windows Authentication):
   1. configure the same user account on the new server's service.
4. Copy the backup of the entire Predict! installation directory to the new server
   1. This will overwrite all existing files.
5. If the database server address or credentials have changed:
   1. Open \prc6\wf26\standalone\configuration\standalone.xml and update the database connection details.
6. Restart the Predict! 6 service.
7. Contact Risk Decisions to obtain and apply a new licence.

 

Set Up a Test Environment

1. Follow all steps in the Move to a New Server section above.
   1. In Step 1, provide the connection details for the test database (not the LIVE database).
2. After starting the service:
   1. Verify the test environment is pointing to the test database by making a small change and confirming it does not appear in the live environment.
3. Generate and apply SSL certificates for the new server.
4. Update the certificate paths in \prc6\Apache24\conf\extra\httpd-ssl.conf if required.

IMPORTANT: If changes made in the test environment are reflected in the live environment, both are pointing to the same database. 

Update the database connection in standalone.xml immediately.