Access your Pro+ Content below.
Virtualizing disaster recovery infrastructure
This article is part of the Virtual Data Center issue of October 2008, Vol. 5
If your organization has embarked on using virtualization but now struggles with more advanced deployments, you’re not alone. Like others, you’ve probably incurred benefits from your first phase of deployment, but the second phase presents its own challenges. Many companies first delved into server virtualization by consolidating servers to achieve cost savings and reduce power consumption, conserve space, and eliminate idle physical resources. But now they’ve expanded deployment to encompass new goals like improved disaster recovery (DR). Indeed, according to the Data Center Decisions 2008 Purchasing Intentions Survey of more than 600 IT professionals, the second most popular use of server virtualization deployment was for disaster recovery, with more than 40% of respondents using virtualization technologies for DR. Now, with server virtualization, organizations can create virtual machines (VMs) that serve as backup servers when primary servers fail or in the event of a data center disaster. Virtualization enables organizations...
Access this PRO+ Content for Free!
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Features in this issue
With virtual architecture, your hardware considerations change, so you can’t make hardware purchases in isolation. Virtualization has implications for CPU, memory, storage and network bandwidth.
Your choice of operating system often dictates your hardware choice.
Organizations have progressed in their virtual deployments, and many now use virtual machines for disaster recovery strategies. But a virtual architecture introduces new concerns for data recovery, data management and more