Replication alternatives


This article can also be found in the Premium Editorial Download "Storage magazine: How to successfully deploy data replication."

Download it now to read this article plus other related content.

"Just like with Continuous Data Replicator, array-based replicas of supported arrays are integrated into the backup application index and catalog, allowing users to restore an array-based snapshot by simply right-clicking it within our application," said Brian Brockway, vice president of product management at CommVault. Similarly, Symantec's Veritas NetBackup is integrated with more than 40 arrays and virtual tape libraries (VTLs), and EMC NetWorker offers tight integration for EMC's RecoverPoint network-based replication product.

Requires Free Membership to View

Choosing a data replication solution

1. Selection of a data replication method should start with a business impact analysis to determine required recovery time objectives (RTOs) and recovery point objectives (RPOs).
2. For applications that can't accept data loss (RTO equals zero), synchronous replication is required. Heed latency in synchronous replication because it will drag down application I/O performance. If there is any risk of latency or unreliable bandwidth, or for replication beyond certain distances (50 km to 300 km), asynchronous replication is the way to go.
3. Besides the replication mode, application performance can be impacted by the replication platform. Host-based replication competes with applications for valuable processor, memory and I/O resources.
4. Have a clear understanding of the bandwidth requirements, impact on bandwidth cost, and how data replication will impact other applications and users. Clearly understand and take advantage of replication features related to bandwidth such as compression, bandwidth throttling and configurable bandwidth usage depending on the time of day. Consider wide-area network (WAN) optimization devices to preserve bandwidth.
5. Replication products that support heterogeneous environments can substantially reduce cost by supporting less-expensive or legacy arrays. They also limit vendor lock-in.
6. The disadvantage of vendor lock-in of array-based replication is offset by the advantage of close integration between replication and the storage platform and easier support, eliminating the risk of finger-pointing in multivendor configurations.

Network-based replication

In network-based replication, the replication occurs in the network between storage arrays and servers. I/Os are split in an inline appliance or in a Fibre Channel (FC) fabric; the I/O splitter looks at the destination address of an incoming write I/O and, if it's part of a replication volume, forwards a copy of the I/O to the replication target. Network-based replication combines the benefits of array-based and host-based replication. By offloading replication from servers and arrays, it can work across a large number of server platforms and storage arrays, making it ideal for highly heterogeneous environments. Most network-based replication products also offer storage virtualization as an option or as part of the core product.

This was first published in April 2009

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: