ZENworks does not recommend maintaining a replica of the Vertica database to protect data in case of a failure in the zone. In the event of a failure of the Primary Server in which Vertica, Kafka or ZooKeeper is enabled, you need to replace the device hosting the Primary Server with a new device that has the same identity, that is the same host name and IP address as that of the old device. For more information, see Replacing an Existing Primary Server with a New Primary Server in the ZENworks Disaster Recovery Reference.
NOTE:If the replication count is 1, then before decommissioning the last server that has a Kafka role enabled in it, run the zman server-role-kafka-add-broker (zman srkab) to add a new broker and then proceed with the decommissioning of the existing server.
However, if you have already decommissioned the server, ensure that you bring up a server with the same hostname by backing up and restoring the Kafka data. For more information, see Replacing an Existing Primary Server with a New Primary Server in the ZENworks Disaster Recovery Reference.
After replacing the existing Primary Server with a new Primary Server, you need to re-execute the configure action to migrate data from the RDBMS to the Vertica database. For more information, see Migrating Data to Vertica. However, data like the patch CVE status data might not be available immediately unless you run patch scans for all the devices in the zone.
NOTE:In the event of a failure, any trending data that is created on Vertica cannot be recovered. However, Vertica provides a way to take a backup of specific tables in the database and enables you to import these onto another database. For more information, see Vertica Documentation. Therefore, as a precautionary measure, you can take periodic backup of these tables. After replacing the existing Primary Server with the new server, you can replicate and restore these tables from the backup location.