Remote Mirroring is nothing but to provide data accessibility protection for an application/s using physically separate locations. To understand it in simple terms, let’s go with an example. If suppose, some data is being written to a storage server on premises. If the same data is replicated to other storage source on other premises, it is called remote mirroring and the availability of an extra copy proves useful for disaster recovery purposes.
Remote mirroring is possible in two possible ways
Synchronous Remote Mirroring is treated as the highest possible level for Disaster Recovery when it comes to recovery point objective and recovery time objective. The RPO is “zero” lost data, and the RTO is typically seconds to minutes. Synchronous remote mirroring does this by neither completing nor acknowledging the local write until the remote write is completed and acknowledged. Additional writes can’t occur until each preceding write has been completed and acknowledged. This means local performance is directly related to the performance of the DR remote device; distance is the limiting factor. Remote synchronous mirroring is rarely deployed for circuit distances greater than 160km (100 miles).
Asynchronous Remote monitoring local writes are completed and acknowledged before the remote writes. Asynchronous remote mirroring is a “store-and-forward” technique that reduces I/Os and wait delays, allowing remote writes to fall behind the local writes. This means the RPO for lost data can range from seconds to minutes, and even hours in some cases.
Asynchronous remote mirroring is most often utilized when the remote site is a long distance from the local site.
In simple terms- Synchronous replication means data writing takes place simultaneous on the premises and at the remote site. Asynchronous replication means data write takes place after the on-premises write is full completed.
Both these replications help in minimal or zero risk exposure in losing data during disaster and help in quick data recovery when a disaster occurs.
Going with the general notion, Remote Mirroring applications are often touted to be pricey, as the equipment is usually expensive, and it typically requires at least twice the primary disk space and sometimes much more. However, for lowest (zero) RPO or RTO Remote replication is the only answer.
With the advent of cloud computing, the demand for disaster recovery as a service is also growing.
StoneFly, Inc is one such company which is offering advanced disaster recovery as a service. Under this service option, companies opting for the service from this wholly owned business unit of DNF Corporation can get remote mirroring services to 2-3 sites.
StoneFly Cloud drive hosted in Microsoft Azure cloud platform can help in easily mirroring the data from an enterprise physical or virtual StoneFly iSCSI or FC SAN storage appliances to a StoneFly Cloud Drive hosted in Microsoft Azure. If an outage or disaster occurs on-premises, the StoneFly Cloud Drive can be quickly mounted as a remote iSCSI drive to easily access all of the enterprise data that has been asynchronously replicated to Azure.
Remote mirroring to a StoneFly Cloud Drive ensures minimum downtime and maximum data availability should the unthinkable occur.
So, the user can save a lot by this practice, as the need to buy storage and replicate the data to that appliance gets eliminated.
To know more call 510.265.1616 or click on StoneFly Cloud Drive