Migrating Without Service Interruption

Follow these steps to migrate GVP without service interruption.

Notes: The Resource Manager must be deployed in either active-active or active-standby HA mode for this procedure to be completed successfully. Genesys recommends that you execute the steps in the following procedure during low call traffic periods only.

1.[+] Back Up the Configuration

Back up the GVP 8.x Application objects.
For each GVP Application object in your existing GVP 8.x deployment, using Genesys Administrator:

1. Go to the Provisioning > Environment > Applications > GVP Application > Options tab.
2. On the toolbar, click Export.
3. In the dialog box, select the export format. The options are to export as a .cfg file or as an .xml file.
4. In the File Download dialog box, click Save, and then save the configuration file to a convenient location.
5. To ensure that you retain the built-in audio files that your deployment uses for DTMF tones and for prompts, back up the files in the <MCP installation path>/audio directory and subdirectories.

2.[+] Upgrade the Reporting Servers

If the Reporting Server is not running in High Availability (HA) mode, perform the first three steps (a, b, and c) only. If the Reporting Server is running in HA mode, then complete all of the steps:

1. Use a graceful shutdown to stop the standby Reporting Server, as described in "Stop GVP Processes" (step 2 of Steps to Migrate to GVP 8.5.0).
2. Uninstall the Reporting Server in Genesys Administrator, as described in "Uninstall GVP 8.x" (step 3 of Steps to Migrate to GVP 8.5.0).
3. In Genesys Administrator, create and install the Reporting Server Application, as described in "Create and Install 8.5.x Applications" (step 4 of Steps to Migrate to GVP 8.5.0).
   Note: Do not restart the standby Reporting Server.
4. Use a graceful shutdown to stop the active Reporting Server.
5. Uninstall the Reporting Server. See <onlineblue>Steps b and <onlineblue>c above. Note: Call data is not lost while both Reporting Servers are off line because the call handling components retain the data in their buffers.

3.[+] Create the Reporting Server Database
1. Migrate the old database. See Migrating the Reporting Server Databases.
   Or, you can create a new database. For more information, see the GVP 8.5 Deployment Guide.
2. Verify that the database connection parameters are configured correctly for the new database.
3. Restart the standby and active Reporting Servers.

Note: If the Reporting Server is not running in HA mode, follow the steps for migrating the active Reporting Server.


4.[+] Upgrade the Resource Manager
1. Upgrade the Resource Manager, starting with the server that is configured as cluster.mymemberid = 1 in the HA cluster:
   1. Use a graceful shutdown to stop the Resource Manager, as described in "Stop GVP Processes" (step 2 of Steps to Migrate to GVP 8.5.0).
   2. Uninstall the Resource Manager in Genesys Administrator, as described in "Uninstall GVP 8.x" (step 3 of Steps to Migrate to GVP 8.5.0).
   3. In Genesys Administrator, reinstall the existing Resource Manager Application, as described in "Create and Install 8.5.x Applications" (step 4 of Steps to Migrate to GVP 8.5.0). Use the second option, Reuse Existing 8.5.x Applications.
   4. Using Genesys Administrator, import the new Application template. A dialog appears to ask whether the you want to overwrite the existing data. Select No.
   5. Restart the Resource Manger (cluster.mymemberid = 1).
   6. Wait a few minutes to allow the calls that are in progress to complete. Note: When you reuse the existing Resource Manager Application, you do not have to reassign the Logical Resource Groups (LRG). However, this is not recommended if your the platform has undergone major functional changes. In that case, create a new Resource Manager Application.
2. Check the status of port 5060 to ensure the Resource Manager is fully started:
   • On Windows, open the Command Line Console (CLC) and enter netstat -n -a | find “5060”.
   • On Linux, enter netstat -a | grep 5060.
   The port should be in the LISTENING state and both the TCP and UDP ports should be allocated.
3. To prevent SIP transaction failures, check port status for 9801 (the port where the cluster heartbeat is detected and where replication occurs):
   • On Windows, open the CLC and enter netstat -n -a | find “9801”.
   • On Linux, enter netstat -a | grep 9801.
4. Upgrade the other Resource Manger in the HA pair (cluster.mymemberid = 2).

5.[+] Migrate the Resource Groups

Migrate and provision your existing GVP 8.5.x resource groups, by using the Logical Resource Group Migration Tool (LRGMT) in Genesys Administrator.
See "Migrate the Resource Groups" (step 5 of Steps to Migrate to GVP 8.5.0).


6.[+] Upgrade the Media Control Platforms

Upgrade each Media Control Platform application individually.
Follow the same steps that you used to upgrade the Resource Manager in "Upgrade the Resource Manager" (step 4 of this procedure)).


7.[+] Upgrade the Call Control Platforms

Upgrade each Call Control Platform application individually.
Follow the same steps that you used to upgrade the Resource Manager in "Upgrade the Resource Manager" (step 4 of this procedure).