Since HPE Ezmeral Data Fabric Database tables are created in volumes, volume mirroring lets you automatically replicate differential data across clusters and is done so, as designated, through the use of mirror schedules or through a manual mirroring operation one time without defining a schedule. Consider mirroring volumes to create disaster recovery solutions for databases or provide read-only access to data from multiple locations.

As HPE Ezmeral Data Fabric Database does not require RegionServers to be reconstructed, databases can be brought up on the mirrored site if the active site goes down.

Mirroring is a parallel operation, copying data directly from the nodes of one data-fabric cluster to the nodes in a remote data-fabric cluster. The contents of the volume are mirrored, even if the files in the volume are being written to or deleted.

Data Fabric captures only data that has changed at the file-block level since the last data transfer. After the data differential is identified, it is then compressed and transferred over the WAN to the recovery site, using very low network bandwidth. Finally, checksums are used to ensure data integrity across the two clusters. There is no performance penalty on the cluster because of mirroring.

See Mirror Volumes for more details on mirror volumes.

See Guidelines for Setting Mirror Schedules for more details on setting mirror schedules.