Keep users and applications running undisturbed despite the general storage upheaval occurring behind-the-scenes.
When preparing business continuity plans, some IT organizations focus on equipment failures and mistakenly trust highly reliable hardware to keep them out of trouble. They fail to account for the many other factors that greatly contribute to business upheaval:
- Power outages
- Water leaks
- Terrorists attack
- Technician error
- Planned maintenance
- Unplanned maintenance
- Major equipment failure
- Technology refresh
- Localized acts of God (storms, floods, fire)
Instead, they concede these interruptions, either penciling in remediation steps into their Disaster Recovery guide, or crafting elaborate and prohibitively expensive failover schemes to minimize downtime while switching between identical devices. In contrast, DataCore storage virtualization software prevents these more frequent sources of storage-related disruptions from ever affecting applications. And we enable you to do this in a cost-effective manner that leverages potentially different devices for redundancy.
Architecturally, we help you to maintain business continuity by emulating a standard, multi-ported, co-located shared storage resource that is physically separated between facilities some distance apart. The current practical limit is around 100 kilometers. For some IT facilities, the mirrored halves of their DataCore virtual storage pool are housed in different floors on opposite sides of the same building. Others choose to split their pool between buildings on the same campus. Those with data centers on opposite ends of a city enjoy the most protection, often using a co-location facility for the other hot-site.
The storage devices at either end may be different models and brands, depending on what you have available. Essentially, both mirrored halves of the pool are always active, generally servicing the workloads closest to them. When either half of the storage infrastructure (or the facility that it resides in) is taken out-of-service, the other half automatically takes over without applications sensing a difference. The hosts continue to read and write to the same virtual disks unaware of the chaos occurring in the background. After the affected half of the storage infrastructure is put back into service, the mirrored pairs are automatically resynchronized and the original paths are restored. No special host scripts are needed.