This article can also be found in the Premium Editorial Download "Storage magazine: How to distance your data from disaster."
Download it now to read this article plus other related content.
Three data replication choices have emerged: array-based, host-based and network-based, with each having its distinct pros and cons. What method is best for your environment?
When it comes to preparing for an eventual disaster, it's better to scatter your eggs rather than fortify your basket. That risk-mitigation philosophy is at the heart of an important storage trend: replicating data to remote locations. And, increasingly, it's not enough for those copies to be offline on tape. Replicated data needs to be readily accessible—online—so that operations can resume as quickly as possible in the event of an outage at the primary site.
"We still do tape backup at night, but we wouldn't want to lose an entire day's worth of data," says Don Moran, database administrator at Hanson Brick & Tile, a brick manufacturer headquartered in Charlotte, NC. The company began replicating the Oracle database that runs its enterprise resource planning system in North Carolina to a Hanson office in Texas approximately two years ago. Disaster recovery (DR) tests have shown Moran that he can get his standby server up and running in less than 15 minutes. "I can go into full DR mode without ever leaving my office," he says.
Storage readers are very keen on replication. According to a survey published in our March issue (see "
But even though the economics of replication have changed dramatically, the technology changes have been relatively incremental. In the beginning, replication took place on the host. Large storage vendors eventually began offering replication as a function of their arrays. Today, startups are angling to have more replication take place off the host or array and in the network instead; each approach has its pros and cons.
This was first published in May 2006