Cluster replacement can be achieved using a mirrored system architecture. This allows you to recover an entire system very quickly without data loss.
You have the option of architecting your system for fast recovery from a disaster in which you lose an entire ThoughtSpot instance. This involves running two ThoughtSpot appliances in a mirrored configuration. This configuration is used in mission critical systems or for business processes in which ThoughtSpot data has been operationalized.
The two ThoughtSpot instances are called:
Primary: The production ThoughtSpot instance.
Mirror: A standby instance that can be placed into service in the event that the primary fails.
In this configuration, the primary initiates periodic full backups of itself. It pushes the backups to a shared NAS (network attached storage). The mirror instance pulls the backups from the shared NAS at defined intervals. It uses each new backup to restore itself to match the production cluster.
Some operations, like backup/restore and data loading, require you to either read or write large files. You can mount a NAS (network attached storage) file system for these operations.
Set up a disaster recovery configuration
Use this procedure to set up a disaster recovery configuration with a primary and a mirror instance. If the primary cluster fails, the mirror cluster can take over its operations after a small manual intervention. The manual procedure makes the mirror instance into the primary.