Using this procedure, you can set up a Crunchy 5 environment on the target system that is Avaya Analytics™ version 4.3.1.1. You can perform migration from the source system Crunchy 2 to the target system Crunchy 5.
Before you begin
A single node cluster must be deployed.
A Source system with Crunchy 2 environment must be configured.
Procedure
Log in to the Cluster Control Manager (CCM) console as the customer user.
Switch to being the root user by entering the command su.
Run the following script:
ccm release orca-dbmgr migration2to5.sh
When prompted, provide the IP address and Port for the source warehouse analytics_db.
Note:
Here, you need to enter the IP address and port number which you noted after running HAsourcemigrate2to5.sh script on the source system.
Enter the postgres password for the source database.
There is a prompt to enter mstr db password. Ignore it as the script will not work with mstr db as a source.
Select the Migrate source to target option, enter the corresponding number.
This option starts migration from the source system to the target system.
Note:
The migration process on the target system can fail if the script on the source system does not finish its process. If the migration process fails on the target system, go to the source system and ensure that the script ./HAsourcemigrate2to5.sh has successfully completed and shows status as Process complete.
In Avaya Analytics™ 4.0.0.1 and 4.1.0.1 releases, while the migration replication process is in progress, the Engagement and Messaging reports are blocked from working on the source system. If the migration process is aborted or completed, these reports will be functional again.
Once the migration process is completed, there is a prompt to enter next option. The data keeps syncing from source system to target system until you run the option Break link to source make target independent.
If any errors occur, you need to run option Cleanup failed attempt and then run option Migrate source to target again.
Select Cleanup failed attempt, enter the corresponding number.
This option rolls back all the migration steps in the event of a failure at any point in the process. In the event of a failure in the migration process, you must perform cleanup before running Migrate source to target option again.
Note:
If you see error on selecting Cleanup failed attempt option, it can be because the migration did not complete all the steps. For example,
If migration process fails at step Break link to source make target independent and you run the cleanup, you will see errors trying to clean up next steps because these steps are not completed. You can ignore such an error.
Select Break link to source make target independent, enter the corresponding number.
This option notifies the target system to stop copying from source system. It disconnects the source database, which means data coming on the source system will not be synced with the target system.
You must run this option when you want to move to the target system Avaya Analytics™ version 4.3.1.1. You must ensure that the target system is usable, and a final switchover is needed. You must check the following conditions.
Before disconnecting the source system, verify that the data is matching in the source system and the target system. You can verify this by running option Check Migration Status in another console. Before running Check Migration Status in another console, run command ccm release orca-dbmgr migration2to5.sh.
Note:
After running option Break link to source make target independent, the new data that comes in the source system is not available in the target system.
Select Check Migration Status, enter the corresponding number.
This option performs row counts and database object counts to compare the source system and the target system. Run this option only after the Migrate source to target step is completed successfully.
