Single and multiple hypervisors

Single and multiple hypervisors

Listed are some of the benefits and trade-offs between using single and multiple hypervisors:

  • Simplified management a single hypervisor environment can be managed with a single tool, giving a global view of the entire environment. A multi-hypervisor environment may require multiple tools to manage the environment, providing a more limited view, as well as requiring administrators to understand multiple systems, configurations, etc.
  • Flexibility in allocating resources a single hypervisor environment allows administrators to reallocate resources anywhere within the environment. For example, unused or underused servers can be moved to a cluster that is approaching capacity or is experiencing performance issues. If there are multiple hypervisors, the underlying hardware may not be compatible, and minimally, the hypervisor would need to be reinstalled or changed to match the target destination. This also impacts longer-term capacity planning, as multiple environments must be analyzed independently, and runs the risk of having idle systems.
  • BC and DR planning Each hypervisor platform must be treated independently from a recovery perspective, since not all hypervisors have the same options available. This can also complicate the storage and network recovery options, as there may need to be multiple options available within those layers as well.
  • Performance and compatibility a single hypervisor may not be able to run all of the required operating systems within the data center. In addition, optimal performance might only be possible for a particular application if it is paired with a specific hypervisor. Depending on the criticality of the application and the performance improvement, this alone may be a valid reason to deploy a second hypervisor. Also, if the eventual plan is to move to a hybrid or cloud environment, ensure that the hypervisors are compatible with the provider’s systems.
  • Cost A single hypervisor will generally cost less in terms of Operational expenses. However, capital expenses may or may not be higher, depending upon factors such as licensing, hardware costs, etc.

To view or add a comment, sign in

More articles by ossama rashad

  • Cloud-native application protection platforms (CNAPPs)

    A unified and tightly integrated set of security and compliance capabilities designed to secure and protect…

    1 Comment
  • knowledge factor

    The knowledge factor, in a security context, is a category of authentication credentials consisting of information that…

  • IT Security that Keeps Up with Business and IT Operations

    Today’s data centers are transitioning into software-defined data centers (SDDC). In the SDDC, the core elements of the…

  • Cyber-security Strategy and Implementation Plan (CSIP)

    On October 30, 2015, President Obama and Federal CIO Tony Scott introduced the Cybersecurity Strategy and…

  • Storage Virtualization

    Storage Virtualization, at both the block and file level, provides a good way to scale and environment beyond a single…

  • Next-Generation Firewall – NGFW “Two”

    Passive DNS DNS traffic exists in nearly every organization, creating an overwhelming ocean of data that security teams…

  • Next-Generation Firewall – NGFW “One”

    Early to mid-90s Firewalls were little more than filtering rule sets on routers. As more organizations connected to the…

    1 Comment
  • Vendor lock-in

    Vendor lock-in makes a customer dependent on a vendor for hardware or software, creating a situation where they are…

  • Data Center Networking, What's Changed?

    During the past 12 months, we have seen the market stabilize and many enterprises focus on executing the first steps of…

    3 Comments
  • Do you think that ACI and NSX aren't really in competition?

    I think ACI and NSX aren't really in competition -- one an SDN solution, one an NFV solution -- might I want both? The…

    2 Comments

Others also viewed

Explore content categories