When a cluster is recreated, all data in the Cassandra database is erased, including important submission records, reports, and statistics. To help avoid this data loss, a new CLI-based backup and restore is now available. This feature allows users to back up only the record-level data and not the configuration and restore it later if needed, even after the cluster has been recreated. It ensures that key submission-related data is preserved, while still starting fresh with a new configuration.
Key highlights:
Maximum five backups supported. Older backups must be deleted before adding new ones.
Single background operation (backup/restore/delete) is allowed at a time.
Backup/Restore operations work seamlessly across single or multi-broker node clusters.
Restore overwrites the existing records present in database. Ensure no active submission is in progress during restore.
Backup can be executed at any time. However, it is recommended to take backup when no active submission is in progress.
The following CLI commands are used to perform Cassandra database backup, restore, and backup management operations.
mvx node cdbmgr backup— Initiates the backup of records present in IVX cluster.show mvx node cdbmgr backup— Lists available backups present in the system with Name, Size and Timestamp.no mvx node cdbmgr backup <backup_name>— Deletes a specified backup. If any background operation of this feature (backup/restore/delete) is in progress, this command will not execute.mvx node cdbmgr restore <backup_name>— Restores a specified backup. This command stops database services temporarily. Please ensure no submission are in progress while executing this command.show mvx node cdbmgr backup-status— Displays the status of the last backup, restore, or delete operation, including PID and progress.