This guide provides procedures and guidance for deploying HPC Pack where the head node is configured in a failover cluster.. The failover cluster will contain two servers (or more, depending on the version of ) that work together, so if the server that is acting as the head node fails, another server in the failover cluster automatically begins acting as the head node (in a process known as failover). Even if an outage occurs on a server, existing jobs can continue to run and new jobs can be submitted.
Setting up failover clustering enhances the availability of head node services for unscheduled and scheduled outages.
Unscheduled outages If there is a failure of a resource such as a hardware or software failure on a server that is acting as the head node, the result is a brief interruption during failover. After failover, you can work on the server that has the problem while the needed functionality continues to run on another server in that cluster.
Scheduled outages You might not want to lose functionality during routine node maintenance (for example, applying a service pack or hotfix, upgrading hardware, or updating an application). If your head node is configured in a failover cluster, one server in that cluster can support needed functionality while you apply software updates or upgrade hardware on another server in that failover cluster.
|Before you begin your deployment, review the Release Notes for your version of HPC Pack.|