To migrate from previous database to the new database, you must perform the following steps:

Prerequisites

Note: Upgrade from 7.0u8 onwards to 7.3.0.5 does not need event migration, as both of these have Elastic Search database. Also, running the event migration task throws an exception, which can be ignored.
  • Install and configure previous M&R version. For example, install and configure 6.7u1.
  • Configure 6.7u1 for Smarts SP CDR/CMR configurations. Verify CallOverview reports are present.
  • Download the latest M&R build. The VMware Smart Assurance Installation and Configuration Guide for M&R provides more information.
  • Install the M&R, by invoking the following command: 
    sh EMC_MnR_7.3.0.5_Linux_64-bit_Setup_File.sh
  • To upgrade the platform, install the new packages in: 
    /opt/APG/Tools/Module-Repository [Y/n]? Y
/opt/APG/bin/manage-modules.sh update module-manager
/opt/APG/bin/manage-modules.sh service update all
/opt/APG/Tools/Module-Manager/1.16u3/bin/launch-update.sh
  • Configure the Elastic Search, see Configuring Elastic Search for more information.
  • Restart Elastic Search server. Ensure Elastic Search server is running.

Procedure

  1. Update the Smarts package.
  2. Update the Smarts versions from SolutionPacks.
  3. Update the post install procedure.
  4. Manually create the schema for the CDR database, you have to create the following FLOW-RPE2 resource for the tomcat server to enable the connection to the CDR database.
    On Linux: 
    ./bin/manage-resources.sh create dba/ES-RPE2-ARCH '{ "type": "elasticsearch", "datasource": { "hosts": ["http://<Elastic Search Server IP>:9200"],"prefix": "/cdr*"},"settings": {"mapping": "ES-RPE2.xml"},"disabled": false }'
    On Windows: 
    APG PATH\bin\manage-resources.cmd create dba/ES-RPE3-ARCH '{ "type": "elasticsearch", "datasource": { "hosts": ["http://<Elastic Search Server IP>:9200"],"prefix": "/cdr*"},"settings": {"mapping": "ES-RPE2.xml"},"disabled": false }'
  5. Delete "dba/FLOW-RPE2" table from manage-resources list.
  6. Restart the Tomcat service.
  7. Restart the Elastic Search server.
  8. Stop the event processing manager service for smarts.
  9. Run the data-migration task which is enabled for run, see the Scheduling the Event-Processing Tasks for more information.
  10. Verify the Event Processing for smarts*, CDR records are read and processed.
  11. Ensure from Elastic Search, that data is flowing.
  12. Add new CDR records and verify new CallOverview reports are also fetched.