Backup, Recovery, and Data Encryption Options for Sophie
This topic outlines several setup options for backup and recovery for Loom-System’s Sophie.
- Setup options may change for different IT operations.
- This document was written under the assumption that regarding high-availability, Search is the only critical functionality.
Backup and Recovery Options
Sophie’s backup and recovery can be configured in either Hot-Hot setup, Hot-Cold setup.
In this setup, all components are replicated across two data-center in one of the following methods:
- Data is replicated upon indexing (shard duplication across nodes).
- Data is shipped to a broker that forwards each event to both locations.
Option 2 is recommended as it allows for more agility.
- It can be configured that some part of the data isn’t replicated to the fail-over setup.
- Lower retention can be set at the fail-over setup.
- As compression is configured in the scope of an index, is it possible to set a more aggressive compression at the fail-over site (at the cost of performance.) by disconnecting the Elasticsearch clusters.
In this setup, data is copied over to a second site periodically.
Loom-Systems recommend a setup of hourly-indices, copying the indexes to the fail-over site every hour, but other configurations are viable.
Inactive Second Site
At this setup the virtual machines running the Elasticsearch nodes are inactive. When switching to the fail-over site, the nodes will activate and the copied indices will be imported.
- The time-to-recover will be up to one-hour
Backup Setup Considerations
The following considerations should be taken when choosing a backup setup:
- Cost Costs will be significantly lower in a hot-cold setup, as both storage and compute requirements are significantly lower.
Only the Hot-Hot setup offers an always-on environment