Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Virtualisation and business continuity - where the wild gaps are

450 views

Published on

Virtualisation promised more affordable business continuity, but there are still issues to consider around availability, continuity and backup for virtual machines, particularly as companies begin using more than one virtualisation or storage platform. Ian will cover the challenges that still exist around business continuity and virtualisation.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Virtualisation and business continuity - where the wild gaps are

  1. 1. Virtualisation & Business Continuity<br />Ian Masters, UK sales director<br />
  2. 2. Introduction<br />With solutions for Windows®, Linux®, AIX® and IBM®i, Vision leads the way in keeping systems and applications resilient and available <br />Personally working in the high availability and disaster recovery for Windows® space since 1996<br />
  3. 3. Virtualisation advantage?<br />virtualisation brings its own availability tools<br />but virtualisation could be its own worst enemy when it comes to availability<br />
  4. 4. Virtualisation advantage?<br />With minimal, incremental investments, IT managers can use virtualisation as an HA platform<br />
  5. 5. VMware tools<br />the VMotion® and Storage VMotion functionality in vSphere makes it possible for organisations to dramatically reduce planned downtime<br />VMware HA provides rapid recovery from outages<br />shared storage is a single point of failure<br />local availability only<br />VMware fault tolerance provides continuous availability<br />shared storage is a single point of failure<br />local availability only<br />
  6. 6. Hyper-V tools<br />Hyper-V™ live migration allows you to move running VMs from one Hyper-V™ physical host to another<br />
  7. 7. Hyper-V tools<br />failover clustering at the Hyper-V host level<br />shared storage is a single point of failure<br />local availability only<br />clustering at the Hyper-V guest level<br />shared storage is a single point of failure<br />local availability only<br />clustering at the Hyper-V guest level on a single physical server<br />Physical server is a single point of failure<br />shared storage is a single point of failure<br />local availability only<br />
  8. 8. Virtualisation disadvantage?<br />some HA techniques and technologies, however, outstrip the capabilities of virtualisation platforms<br />what do you do if you run more than one hypervisor?<br />what do you do for DR?<br />what happens if you use more than one storage platform or vendor?<br />
  9. 9. Virtual backups<br />there are some very simple, yet far-reaching challenges to deal with when it comes to virtualisation backup<br />when you plan a backup and recovery strategy for a virtualized server environment, there are several factors to consider<br />
  10. 10. Virtual backups<br />if a virtual machine is expected to be up-and-running for example, there is nothing to preclude treating it as a traditional physical machine and backing it up accordingly<br />a backup can be run on the host physical machine and backup the VHD or VMDK for example<br />
  11. 11. Virtual backups<br />tools such as snapshots and cloning can help<br />plenty of options, online vs. offline, streamed vs. snapshot, guest vs. host<br />
  12. 12. Virtual backups<br />in-guest<br />Snapshots<br />VCB<br />Third party tools<br />
  13. 13. Is there a solution?<br />replication could provide the answer...<br />works across all virtualisation platforms<br />works across storage platforms & vendors<br />works with physical & virtual servers<br />
  14. 14. Is there a solution?<br />migrate P2P, P2V, V2P and V2V all with zero user downtime<br />failover between any combination of physical and virtual servers, between mixed hypervisors, across any distance<br />recover individual files, emails, data and system states from latest copy or previous point-in-time<br />
  15. 15. Q&A<br />

×