4.6 Migrating Data to Vertica

NOTE:Before bulk data migration, ensure that you run the Configure action to allocate appropriate memory for ZENworks services and for the Vertica and Kafka components. For more information, see Managing Vertica Memory Requirements.

The data migration process to Vertica involves two steps:

  • Bulk Data Migration: This process involves exporting of data in bulk to the configured tables in Vertica from the existing RDBMS. To initiate this process, from the command line utility of the Primary Server in which Vertica is installed, run the following Configure action:

    novell-zenworks-configure -c VerticaDBMigrate -Doption=start

    If a Configure action that was executed previously had failed, then the start option will resume the operation from the point at which it had failed. To restart the migration process from the beginning, use the Force option. This option will remove existing data from the Vertica database.

    For example, novell-zenworks-configure -c VerticaDBMigrate -Doption=force

    If the migration process fails, then check the logs as detailed in the section Data Migration.

  • Change Data Capture: This event is automatically triggered after the bulk migration process. This process syncs modified or newly added data from the RDBMS to Vertica. The sync action is performed at an interval of every 10 to 15 minutes. For the syncing process, a queue action is initiated that creates Kafka connectors and topics for each table that is already migrated. The Kafka connectors identifies updated or modified tables in the RDBMS database and publishes this data to the appropriate topics. The ZENworks loader stream services (Kafka consumer) then subscribes to this data and sends it to the Vertica database.

    To monitor the status of the Data Sync process, navigate to the Diagnostics page in ZCC. For more information, see Monitoring Diagnostics.