1.Create a cluster resource of resource type “Cluster Extension 3PAR for VM Management” in the VM Role.

NOTE: Corresponding CSV is dependant on CLX.

Example: Using the PowerShell

Add-ClusterResource -Name VM_MGMT_Res -Group VM4_2k12 -ResourceType "Cluster Extension 3PAR for VM Management"

2.Set the dependency of VM configuration resource on the newly created resource of resource type “Cluster Extension 3PAR for VM Management”.

Example: Using the PowerShell

Add-ClusterResourceDependency -Resource VM_MGMT_Res -Provider “Virtual Machine Configuration VM4_2k12”

The configuration is now complete and the VM role is enabled with VM management functionality.

Behavior of VM Management functionality in various disaster scenarios

This section describes various disaster scenarios and how the VM management functionality behaves in these scenarios:

1.CSV disk owning cluster node and the VM owning cluster node are in different datacenter and the VM Role is offline:

When user tries to bring the VM role online, the online operation fails as owner nodes of the respective resource are running in different datacenters. Once the resource fails on the cluster node, depending on the cluster role failover policies, the role behaves accordingly.

2.CSV disk owner node and the VM owner node are in same datacenter and the VM Role is offline:

When user tries to bring the VM role online, the online operation succeeds as owner nodes of the respective resource are running in same datacenters.

3.The cluster node which owns the CSV disk fails or the CSV disk fails and the CSV disk moves to a node in the same datacenter or CSV disk is moved manually to a node in the same datacenter:

In this scenario, since the CSV disk is moved to a node in the same datacenter, all the VMs continue to run on their respective cluster nodes. There will not be any change in the ownership for the VMs.

4.The cluster node which owns the CSV disk fails or the CSV disk fails and the CSV disk moves to a node in the remote datacenter or CSV disk is moved manually to a node in the remote datacenter:

In this scenario, all the VMs which are configured with CLX feature for VM management will wait for the CSV disk to come online on a cluster node in the remote datacenter. Since the CSV disk is moved to a node in the remote datacenter, all the VMs which are running in the respective cluster nodes in the primary datacenter will be live migrated by CLX to cluster nodes in the remote datacenter. Every role has next preferred node property. Selection of the target node for the live migration will be based on how the next preferred owner property has been set for the VM role.

Preferred Owners is not set: In this scenario, the next preferred owner node will be selected randomly among the cluster nodes which are there in the remote datacenter. The selected cluster node should be up. If not, search will continue until a cluster node is found in the remote datacenter.

Preferred Owners is partially set: In this scenario, cluster nodes which are not part of the next preferred owner node property, will be added to the list in the order of NodeID. Next preferred owner which is in the same datacenter as the datacenter where CSV disk is owned will be

Virtual Machine Management hosted on a Cluster Shared Volume on Windows Server 2012 45

Page 45
Image 45
HP Cluster Software manual

Cluster Software specifications

HP Cluster Software is a robust solution designed to enhance the reliability, availability, and scalability of computing environments in enterprise settings. This software is instrumental in managing clusters of servers, providing a unified framework that allows for efficient resource management, workload distribution, and high availability.

One of the main features of HP Cluster Software is its ability to deliver high availability through failover mechanisms. In the event of a hardware or software failure, the software automatically shifts workloads from the affected node to a standby node within the cluster, minimizing downtime. This feature is critical for organizations that require continuous access to their data and applications.

Scalability is another significant characteristic of HP Cluster Software. Organizations can easily add or remove nodes from the cluster without disrupting ongoing operations. This flexibility ensures that enterprises can adapt to changing workloads and resource demands efficiently, making it suitable for environments ranging from small businesses to large data centers.

Load balancing is a key technology employed by HP Cluster Software. It intelligently distributes workloads across the available nodes, optimizing resource utilization and ensuring that no single server is overwhelmed. By balancing the load, organizations can achieve better performance and enhance the response times of applications, which are essential for user satisfaction.

HP Cluster Software supports various clustering topologies, including active-active and active-passive configurations. This versatility allows organizations to choose the architecture that best fits their operational requirements. Additionally, the software integrates seamlessly with various HP and third-party hardware and software solutions, thus providing a holistic environment for managing IT resources.

Moreover, HP Cluster Software offers centralized management tools that simplify cluster administration. Administrators can monitor cluster performance, manage workloads, and configure settings all from a single interface. This ease of use reduces the complexity often associated with managing large clusters and empowers IT teams to respond rapidly to issues.

In summary, HP Cluster Software is an essential tool for organizations looking to enhance their IT infrastructure's availability, reliability, and performance. With its failover capabilities, scalability options, load balancing technology, and centralized management features, it stands out as a comprehensive solution for modern computing challenges.