Hot Swap Backup Configuration

Hot backup mode supports you to register (activate) as many MetaDefender Core instances as you might need for backup purpose, and those backup instance(s) should be ready to take over with your active / production MetaDefender Core instance whenever applicable.

With engines and configurations ready to use, that helps mitigate any down time in scanning system in case of your recovery disaster plan needs to be triggered.

MetaDefender Core backup instance(s), once registered properly, does not accumulate into your actual license activation slots, that means, you will not be required to purchase additional product license just for this backup purpose alone.

Register a backup instance

1. Online environment: Using following REST API: $link[ref,7558,POST - Setup hot-backup instance,postlicensebackup]
2. Offline environment:

• Obtain license.yml file that supposed to use to active your MetaDefender Core active / production instance before.
• Using following REST API: $link[ref,7558,POST - Setup hot-backup instance,postlicensebackup] with that yaml file content.

Unregister a backup instance

This step will be required when following circumstances happen:

1. You want to activate that backup instance directly without using nomination method (see below) via $link[ref,7558,POST - Activate license online,licenseactivation]
2. You want to shutdown that backup instance for some reasons, but avoid removing the container or system where that MetaDefender Core instance is installed on for possible usage later.

Using following REST API: $link[ref,7558,DELETE - Remove a backup instance,removebackupinstance]

Upon unregistered successfully, that MetaDefender Core instance will no longer allow you to:

• Download engines and their databases from OPSWAT update server source (online mode)
• Upload engines and their databases manually
• Deploy engines and their databases on MetaDefender Core

Basically that MetaDefender Core will become an unlicensed one as a fresh installation.

Nominate a backup instance

Nominating a backup instance is to make that instance become an active / production one. That means, your nominated instance will be able to process files as in production.

Online environment: Using following REST API: $link[ref,7558,POST - Nominate a backup instance to a production instance,licensebackupnomination]

Offline environment: You are not allowed to directly nominate a MetaDefender Core backup instance which was previously registered in offline mode.