About data store synchronization
For maximum redundancy and performance, use data store synchronization between a primary and backup appliance. This ensures that if an appliance fails, there’s no loss of bandwidth savings, as the data segments and references are replicated on the backup appliance.
Data store synchronization works with physical in-path, virtual in-path, or out-of-path deployments. It requires setting up two SteelHeads: one as the primary and the other as the backup. The synchronization traffic uses the primary or auxiliary network interfaces, not the in-path interfaces.
Data store synchronization is a bidirectional operation, regardless of which deployment model you use. The SteelHead primary and backup designation is only relevant in the initial configuration, when the primary SteelHead’s data store essentially overwrites the backup appliance’s data store. The synchronization primary and its backup:
• must have the same hardware or virtual model.
• must be running the same software version.
• don’t have to be in the same physical location. If they’re in different physical locations, they must be connected with a fast, reliable LAN connection with minimal latency.
After configuring the appliances, restart the optimization service on the backup appliance. The primary restarts automatically. The data stores are actively kept synchronized.
If one of the synchronized SteelHeads is under high load, some data might not be copied.