IBM z13s, Technical Manual

Page: 575 / 588

Appendix I. GDPS Virtual Appliance
547
The GDPS Virtual Appliance implements the following functions:
򐂰 Awareness of a failure in a Linux on z Systems node or cluster by monitoring (heartbeats)
all nodes and cluster master nodes. If a node or cluster fails, it can be set up to
automatically IPL the node or all the nodes in the cluster again.
򐂰
Shutting down a Linux on z Systems node or cluster for service (planned maintenance).
򐂰 Initiation of z/VM Live Guest Relocation to move active guests from one member of a z/VM
subsystem interface (SSI) cluster to another
򐂰 Graceful shutdown/startup of the Linux on z Systems cluster, nodes in the cluster, and the
z/VM host. Graceful shutdown/startup of z/VM systems includes any z/VSE guests.
򐂰 Use of HyperSwap to non-disruptively swap z/VM and its guests from the primary to
secondary Peer-to-Peer Remote Copy (PPRC) devices, for both planned disk subsystem
maintenance and unplanned disk subsystem failure.
I.3 GDPS Virtual Appliance recovery scenarios
This section presents the following recovery scenarios using GDPS Virtual Appliance:
򐂰
Planned disk outage
򐂰
Unplanned disk outage
򐂰
Disaster recovery
I.3.1 Planned disk outage
In a planned disk outage, the HyperSwap provides the ability to non-disruptively swap from
using the primary volume of a mirrored pair to using the secondary volume. A planned
HyperSwap is started manually by operator action by using GDPS facilities. One example of a
planned HyperSwap is where a HyperSwap operation is initiated in advance of a planned
disruptive maintenance of a disk subsystem.