How to Refresh a Retail Pro Prism Lab from a Production System

It is common to have lab systems separate from production systems for testing purposes. However, your lab systems become stale and require a data refresh from the production systems. This article will outline the steps to refresh a lab environment from production backups.

 

1. Restore RP9 / RP Prism and Store MySql

Ensure that the Database Retail Applications for RP9 and RP Prism (MySql) systems are on the same version as the backup data to be restored.

Stop all RP Prism Replication Services on all systems to be restored and set the RP Prism Replication Services to Manual until the process is complete.

 

2. Complete a source backup

Source Oracle System

In RP9, make a TechToolkit.exe complete backup.

Source MySql Server

1. Stop MySql Server on Source System
2. Back up Data folder
3. Start MySql Server on Source System

 

3. Stop services in target system

Target Oracle System

1. Stop RP Prism Services:
   • Retail Pro Prism Back Office Service
   • Retail Pro Prism Common Service
   • Retail Pro Prism DRS Service
   • Retail Pro Prism License Service
   • Retail Pro Prism POS V1 Service
   • Retail Pro Prism Replication Service
   • Retail Pro Prism Resiliency Service
   • Retail Pro Prism Scheduling Service
2. Set Retail Pro Prism Replication Service to manual

Target MySql System

1. Stop Prism Services:
   • Retail Pro Prism Back Office Service
   • Retail Pro Prism Common Service
   • Retail Pro Prism License Service
   • Retail Pro Prism POS V1 Service
   • Retail Pro Prism Replication Service
   • Retail Pro Prism Resiliency Service
   • Retail Pro Prism Scheduling Service
2. Set Retail Pro Prism Replication Service to manual

 

4. Restore services in target system

Target Oracle System

1. Restore complete backup using TechToolkit
2. In TechToolkit update rps.controller set address = ‘local FQDN' where active = 1
3. In TechToolkit Update rps.controller set v9_address = ‘New V9 FQDN' where v9_address is not null
4. Deleting the following data requires DB access (RPI will provide a tool for these actions).
   1. Delete from rps.rem_subscr_resource
   2. Delete from rps.rem_subscription
   3. Delete from rps.rem_connection_subscr
   4. Delete from rps.remote_connection
   5. Delete from drs.remote_connection
   6. Delete from drs.replication_subscription
   7. Delete from drs.replication_sub_resource
   8. Delete from rps.controller where controller_no = ( each controller not used)

Target MySql System

1. Stop MySql Server
2. Rename Data folder
3. Copy MySql data folder from the Backup
4. Start MySql
5. Update rpsods.controller set address = ‘local FQDN' where active = 1
6. Update rpsods.controller set v9_address = ‘New V9 FQDN' where v9_address is not null
7. Delete from rpsods.rem_subscr_resource
8. Delete from rpsods.rem_subscription
9. Delete from rpsods.rem_connection_subscr
10. Delete from rpsods.remote_connection
11. Delete from rps.controller where controller_no = ( each controller not used)

 

5. Restart and Replication

After verifying that the process above was successful, set services back to automatic, restart the computers, and verify that both systems can connect over TCPIP.

You can then add remote connections for day-to-day replication.