Dual Node Cluster Creation
Before you can start using EVOS and start installing the VMs on it you need to run the initial configuration.
In this video we will show you how to create a dual node cluster.
Its intelligent services will detect if one of the nodes goes offline and will make sure that the functioning node takes over the VMs and the virtual network of the failed server without requiring administrative intervention.
Depending on the reason why node goes offline virtual machines will be either transferred to other node without downtime (proper shutdown of the node) or restarted on the other node (node crash).
It does not matter on which node you are creating the configuration or managing the cluster. Both server nodes are equal within the cluster ( there is no master or slave ).
eEVOS Cluster uses automated tools that helps you configure it in few easy steps.
eEVOS Cluster requires minimum of 2 network cards per mirrored server. It uses 2 types of connection. One connection is used
for the replication network which is in charge of replication between 2 eEVOS server nodes. Other connection is used for the corporate network – network in which your clients will be accessing VMs on the cluster.
You can also team the network ports for better redundancy and performance.
When the cluster is created we can see that both nodes are online and communicating with each other. From now on any cluster related configuration change will be automatically performed on both servers.
Creating Cluster Drive ( Mirrored Drive )
After Cluster creation you can start with the cluster drive creation.
A cluster drive represents a mirror of 2 disks on each individual server.
These 2 disks can be a single disk, software or raid array. They are mirrored between the server nodes real-time. This cluster drives will be used later for the virtual machines.
Cluster drives are in Active/Active mode allowing both nodes to use them simultaneously.
Virtual Network Creation
eEVOS enables you to create virtual networks for your VMs. It supports 2 types of networks: NAT and Bridge.
You can assign different virtual networks to individual virtual NICs of a VM.
VM Creation window contains 4 tabs. The mandatory settings for the VM creation are listed in “General Tab”. The settings in all other tabs are optional. For adjusting the settings you can use mouse or for fine tuning the “arrow keys”
Name for the new VM
Guest Operating System
Selection of the appropriate guest operating system makes sure that the VM is configured the most optimal way.
You can select the installation CD for the installation of the Guest OS. Installation ISO must be copied on one of the VM drives. VM drives are accessible via SMB/CIFS and NFS shares.
Select amount of CPU sockets and cores that you wish to assign to the VM
VM Memory Size
Select amount of max memory that the VM is allowed to use. GUI will also show you the amount of memory that is currently assigned to all other VMs.
You can also overcommit memory however keep in mind that if all VMs try to use more memory than available this could cause some of the VMs to crash.
The drive that the VM will be installed on
You can select 2 storage types
RAW – it provides best performance, reserves whole capacity immediately
QED – thin provisioned. Good performance and uses space dynamically
Size of the VM disk. You can also add additional disks by clicking on “Storage Tab” and selecting the option “Add More Drives”. This can be also done later after VM creation.
Live Migration without downtime
eEVOS helps you to migrate running virtual machines from one cluster node to the other without downtime.
The VM will keep its connections, RAM and all its settings will be moved. The whole migration takes just several seconds.
It is a very useful functionality if you wish to shut down or reboot one of the nodes for maintenance or upgrade.
eEVOS supports enterprise class snapshots.
- It will preserve current state incl. RAM
- VSS API ensures highest data integrity
- You can create new snapshots, revert to old snapshots or make new VMs out of the snapshots. They can even run on a different node from the original
You can create fully independent clones of your original virtual machine at its current state. A cloned VM uses data blocks of the original VM as a reference and requires much less disk space to store. The clone can still be started and used on any of the nodes. You can even delete the original VM without influencing ist clone
Installing paravirtual drivers
The most modern Linux Distributions include embedded paravirtual drivers out-of-the-box. Those are ensuring the best possible performance and communication with the host OS. For Microsoft Windows Systems these drivers must be added during the installation. This article describes the installation within Windows Server 2012, other versions are very similar. The following drivers must be installed – Memory driver – Disk driver – Network driver – VSS Communication port (important for the live snapshots)
Click here for the installation instructions