Migrating Vocera Report Server

Follow the instructions given in this section to migrate Vocera Report Server (VRS) data to Vocera Analytics.

Pre Data Migration

Before migrating Vocera Report Server, perform the following pre migration tasks:

1. Login to VRS admin console using administrator credentials.
2. Click Task Scheduler.

   The Task Scheduler screen appears.

   

3. Select Dataload and click Edit Task.

   The Edit Task screen appears.

   

4. Uncheck the Enabled field in Task Information screen.
5. Click Save.

Migrating VRS Configuration

To migrate VRS configuration, perform the following steps:

6. Navigate to the VoceraAnalytics>AnalyticsServer>conf folde
7. Open the vrs-migration-config.json file.
8. Provide the VRS SQL database details in the source fields.
9. Provide the Vocera Analytics database details in the target fields.
   The following screenshot displays the information to be added to the JSON file.

   

10. Save the file.

Updating the Spark Configuration File

To update the Spark configuration file, perform the following tasks:

11. Navigate to the VoceraAnalytics>AnalyticsServer>conf folder.
12. Open the spark-defaults.conf file, and update the value for spark.driver.memory field from 8g to 32g for medium and large size servers or 16g for small size servers.
    For more information on hardware requirements, refer to Hardware Details.

Executing the VRS Migration bat file

To excute the VRS migration file, perform the following tasks:

13. Navigate to VoceraAnalytics>AnalyticsServer.
    The runVRSmigration.bat is displayed.
14. Select runVRSMigration.bat file and run it.
    The following command prompt window displays the status of the database table that are currently being migrated.

    

    Note: Depending on the amount of data on VRS, it may take a longer time to complete the execution of the runVRSMigration.bat command.

Locating the Log files

To locate the log files, perform the following tasks:

15. Navigate to VoceraAnalytics>AnalyticsServer>vrs-migration-output folder.

    The following files are displayed:

    • report-log-source.status
    • vs-log-source.status

    

Creating a Flume Status File

To create a flume status file, perform the following tasks:

16. Navigate to VoceraAnalytics>Agent>Flume folder on the Voice Server.
17. Create a flume-status folder and copy report-log-source.status and vs-log-source.status files to this folder. Ensure that the folder name flume-status is used.
    The VRS migration is complete. There might be instances of data loss that you must rectify. For more information on rectifying data loss, refer to Rectifying Data Loss Issues in VRS Data Migration.
    Note: If there are multiple Voice Servers, ensure that you copy both the files to all Vocera Voice Server machines.

    Note: The report-log-source.status and vs-log-source.status files contain the checkpoints to indicate the completion of data migration from VRS to Vocera Analytics. When pipeline is initiated, it processes data after this checkpoint.

Reverting the Spark Configuration File

To rever the spark configuration file, perform the following tasks:

18. Navigate to the VoceraAnalytics>AnalyticsServer>conf folder.
19. Open the spark-defaults.conf file and update the value for spark.driver.memory field to 12g.

Post Data Migration

After migrating Vocera Report Server, perform the following post migration tasks:

20. Run the PostMigrationCleanup.bat located at <InstallDir>/VoceraAnalytics/AnalyticsServer/ to clear plain-text passwords from the configuration file.
    This step ensures that the credentials of VRS database and Vocera Analytics database are protected.
21. Login to VRS admin console using administrator credentials.
22. Click Task Scheduler.

    The Task Scheduler screen appears.

    

23. Select Dataload and click Edit Task.

    The Edit Task screen appears.

    

24. Check the Enabled field in Task Information screen.
25. Click Save.