1. Resonate RFID Reader Management User Guide
  2. Disaster Recovery
  3. Recovery Overview
  • Resonate RFID Reader Management 2.0 User Guide
Recovery Overview

Recovery Overview

Resonate RFID Reader Management supports fault tolerance to ensure
Resonate
 can recover automatically without human intervention in the event of a software failure, without the expectation of continuous uptime. It also supports being distributed across multiple machines (nodes) to recover in case a machine goes down. However, in the case of a single-node configuration, you are responsible for backup and restore.
Resonate
 uses several internal databases for persistent settings data and configuration of
Resonate
. These are typically databases internal to a containerized service and not some large, centralized database holding everything. Transient data, or data that is expected to change soon anyway, is generally held in one or more of the various message queues to support quick resumption of operation in the event of containers going offline and coming online due to restart, scale up, or other reasons.
Most of the extra reliability built into
Resonate RFID Reader Management
 focuses on making the containers automatically recover instantly and on using Kubernetes for software, data, and state replication across multiple high availability (HA) nodes. In general, however,
Resonate RFID Reader Management
 is not set up to take periodic snapshots of the state and save extra copies outside Kubernetes and the high-availability nodes. Therefore, when installed in a single-node configuration, it is highly recommended that administrators use external tools to set up regular copy backups of either full disk or individual volumes, and that those backups be written to external devices off the main server node.
Keep in mind that
Resonate
 does not do data collection of RFID tag read data, so
Resonate
 does not have any tag data to backup/recover.