Surviving a disaster natural or man-made is never something an enterprise can predict in terms of what might happen in the event of a strong hurricane, widespread power outage, fire or explosion. Yet during the disaster, the company should have a viable way to use a remote disaster recovery site to stay online or to quickly reconnect. The disaster recovery (DR) site should not be too far and not too close to the damaged zone, but just right.
When it comes to disaster recovery, concerns now include the increasing number of natural disasters like fires, hurricanes, floods and earthquakes, says Fred Moore, an analyst with Horison Information Strategies. CIOs are also concerned about catastrophic power loss, hackers, employee sabotage and terrorist attacks.
Opinions vary as to what is truly needed for disaster recovery. Mike Karp, an analyst with Enterprise Management Associates, suggests that clustering, SAN mirroring and replication are some of the more important technologies. The KBX5000 Data Protection Platform by Kashya Inc., of San Jose, CA, for example, addresses the problem of data center availability.
The KBX5000 delivers enterprise-class data protection so that a business across the enterprise can ramp up quickly during disaster recovery, says Rick Walsworth, Kashyas vice president of marketing.
The KBX5000 is an appliance-based system that provides continuous data protection (CDP) and remote replication. The network-based architecture handles stringent data requirements and can replicate from Fibre Channel SANs to IP infrastructures without any distance limitation across the IP environment.
This factor of distance is a vital one in the DR arena. As last years hurricane season pointed out dramatically, its no good having one data center in New Orleans and another in Biloxi or Houston. In the former, the same weather event could simultaneously take out both data centers. In the case of the latter, two different hurricanes one month apart could serve up a one two punch that took out the backup data center shortly after the main center was destroyed.
The key, then, is to place a remote disaster recovery site far enough from the main office, but not too far away from where its needed the most. According to Karp, it is best to find a happy medium where events at one location are unlikely to be duplicated in the other location.
The KBX500 makes it possible to have remote data centers operating at a considerable distance without the usual distance limitations that challenge replication systems. You simply place one Kashya box in one location and another in the mirrored data centers and you are in business. These systems can sustain up to 2 GB/S (16 Gbps) of total throughput across a clustered environment.
User defined policies in the KBX5000 map directly to specific application requirements. They integrate with Oracle, Microsoft SQL, Microsoft Exchange and other applications for time and event-based recovery. Advanced data protection capabilities include local and remote continuous data protection, remote replicator, bandwidth reduction, compression and WAN optimization.
The total system costs begin at around $50,000 and for disaster recovery application an enterprise typically deploys a system at each location, says Walsworth. The KBX5000 is a complete data protection solution with user defined policies that map directly to specific application requirements and high levels of integration with key enterprise database and applications.
Who does Kashya compete against? In most cases, Kashya fights against array- and host-based solutions that provide replication and snapshot based technologies. Walsworth adds that the key differentiators for Kashya are the ability to provide superior replication and CDP capabilities across heterogeneous storage and server infrastructures at lower cost points.
Some analysts say 30 miles might be far enough. Others, however, suggest that in certain circumstances, the huge potential losses involved might make it feasible to place centers as far apart as possible.
The other side of the continent might be necessary to play it safe, says Karp.This article was first published on EnterpriseITPlanet.com.