|
|
| Line 1: |
Line 1: |
| Howto:Implement V13 AppPlatform Redundancy with Microsoft Hyper-V
| |
|
| |
|
| ==Applies To==
| |
| This information applies to
| |
| * V13 AppPlatform
| |
| * Microsoft Hyper-V (Windows 10 / Server 2016 / Server 2019)
| |
|
| |
| ==More Information==
| |
|
| |
| ===Problem Details===
| |
| By design it is currently not possible, to design the V13-AppPlatform redundant. (master-slave scenario)
| |
| To make this possible nevertheless, the AppPlatform can be installed as a virtual machine on a Microsoft Hyper-V cluster.
| |
|
| |
| ===System Requirements===
| |
|
| |
| * Microsoft Hyper-V-Cluster (minimum version Windows 10 or Windows Server 2016)
| |
|
| |
| ====Live migration====
| |
| * Quorum
| |
| * Shared-Storage (NAS / SAN) on which the .vhds files are stored
| |
| ** the storage can be connected directly via fiber optics or provided via iSCSI
| |
| * both nodes must be members of a domain
| |
| * sufficient ressources per node, to be able to host all VMs at once, in case of an error
| |
|
| |
| ====Quick migration====
| |
| * Shared-Storage on which the .vhds files are stored
| |
| * sufficient ressources per node, to be able to host all VMs at once, in case of an error
| |
|
| |
|
| |
| ===Installation===
| |
|
| |
| * assignment of both nodes in the domain
| |
| * installation of the Hyper-V networks
| |
| * connection of shared storage to both servers
| |
| * installation Quorum
| |
| * creation of the VM in the HyperV manager
| |
| * make VM highly available in FailoverClusterManager
| |
|
| |
| For detailed information, see Microsoft documentation.<br>
| |
|
| |
| On the AP is no special configuration necessary.
| |
|
| |
|
| |
| ===How Failover works===
| |
| ====Live migration====
| |
| * RAM will be copied live, to the second node
| |
| * if one node fails, there is no downtime
| |
| * runs automatically, if a node crashes/fails or is restarted manually (e.g. scheduled restart)
| |
|
| |
| ====Quick migration====
| |
| * no automatic failover is possible and it has to be initiated manually
| |
| * VM will be paused and the RAM will be copied to the other node and afterwards, the VM is restarted there.
| |
| * Downtime approx. 10-20 seconds, depending on the size of the RAM
| |