Replication
AIStor Server’s support site replication for both synchronous and asynchronous replication of data between independent AIStor Server deployments.
Deploy AIStor Server peer sites in different racks, datacenters, or geographic regions to support functions like BC/DR (Business Continuity / Disaster Recovery) or geo-local read/write performance in a globally distributed AIStor Server AIStor Server.
An AIStor Server multi-site deployment with three peers. Write operations on one peer replicate to all other peers in the configuration automatically
Inter-site replication performance is typically dictated by latency.
With geographically distributed peer sites, high latency between sites can result in significant replication lag. This can compound with workloads that are near or at the deployment’s overall performance capacity, as the replication process itself requires sufficient free I/O (Input / Output) to synchronize objects.
In this peer configuration, the latency between Site A and its peer sites is 100ms. The soonest the object fully synchronizes to all sites is at least 110ms.
Use an enterprise-grade load balancer with support for high-speed failover logic.
The load balancer should support a health probe/check setting to detect the failure of one site and automatically redirect applications to any remaining healthy peer.
The Load Balancer automatically routes client requests using configured logic (geo-local, latency, etc.). Data written to one site automatically replicates to the other peer site.
If the peer site recovers, the replication protocol automatically handles resynchronization of data from peer sites.