Search

Top 60 Oracle Blogs

Recent comments

Installing an #Exasol 2+0 Cluster on Hyper-V

After having installed Hyper-V, an ISO file with the Exasol software needs to be downloaded. The 2+0 cluster consisting of two data nodes and one license server needs a host machine with at least 8 GB memory and 60 GB free disk space. I do it on my Windows 10 notebook with 16 GB memory. This is for educational purposes of course and not suitable for production use.

2+0 means two active nodes and no reserve node. A reserve node can be added later, expanding the environment to a 2+1 cluster.

We’ll start adding two virtual switches to be able to connect the network adapter of the VMs to them later.

Create Hyper-V Switches for Private and Public Network of the cluster

Click the Virtual Switch Manager in Hyper-V Manager:

https://uhesse.files.wordpress.com/2019/09/hyper1.png?w=1240&h=604 1240w, https://uhesse.files.wordpress.com/2019/09/hyper1.png?w=150&h=73 150w, https://uhesse.files.wordpress.com/2019/09/hyper1.png?w=300&h=146 300w, https://uhesse.files.wordpress.com/2019/09/hyper1.png?w=768&h=374 768w, https://uhesse.files.wordpress.com/2019/09/hyper1.png?w=1024&h=498 1024w" sizes="(max-width: 620px) 100vw, 620px" />

 

Select Private and click Create Virtual Switch:

https://uhesse.files.wordpress.com/2019/09/hyper2.png?w=1240&h=476 1240w, https://uhesse.files.wordpress.com/2019/09/hyper2.png?w=150&h=58 150w, https://uhesse.files.wordpress.com/2019/09/hyper2.png?w=300&h=115 300w, https://uhesse.files.wordpress.com/2019/09/hyper2.png?w=768&h=295 768w, https://uhesse.files.wordpress.com/2019/09/hyper2.png?w=1024&h=393 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Name the Private switch edu-cluster-interconnect:

https://uhesse.files.wordpress.com/2019/09/hyper3.png?w=1240&h=588 1240w, https://uhesse.files.wordpress.com/2019/09/hyper3.png?w=150&h=71 150w, https://uhesse.files.wordpress.com/2019/09/hyper3.png?w=300&h=142 300w, https://uhesse.files.wordpress.com/2019/09/hyper3.png?w=768&h=364 768w, https://uhesse.files.wordpress.com/2019/09/hyper3.png?w=1024&h=485 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Create another Virtual Switch of type Internal and name it edu-public-network:

https://uhesse.files.wordpress.com/2019/09/hyper4.png?w=1238&h=588 1238w, https://uhesse.files.wordpress.com/2019/09/hyper4.png?w=150&h=71 150w, https://uhesse.files.wordpress.com/2019/09/hyper4.png?w=300&h=142 300w, https://uhesse.files.wordpress.com/2019/09/hyper4.png?w=768&h=365 768w, https://uhesse.files.wordpress.com/2019/09/hyper4.png?w=1024&h=486 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Go to Network and Sharing Center and click on the edu-public-network there, then on Properties:

https://uhesse.files.wordpress.com/2019/09/hyper5.png?w=1240&h=832 1240w, https://uhesse.files.wordpress.com/2019/09/hyper5.png?w=150&h=101 150w, https://uhesse.files.wordpress.com/2019/09/hyper5.png?w=300&h=201 300w, https://uhesse.files.wordpress.com/2019/09/hyper5.png?w=768&h=516 768w, https://uhesse.files.wordpress.com/2019/09/hyper5.png?w=1024&h=688 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Then select TCP/IPv4 and click again Properties:

https://uhesse.files.wordpress.com/2019/09/hyper6.png?w=150&h=150 150w, https://uhesse.files.wordpress.com/2019/09/hyper6.png?w=300&h=298 300w, https://uhesse.files.wordpress.com/2019/09/hyper6.png?w=768&h=762 768w, https://uhesse.files.wordpress.com/2019/09/hyper6.png 898w" sizes="(max-width: 620px) 100vw, 620px" />

Select Use the following IP address and type in 192.168.43.1 and the Subnet mask 255.255.255.0

https://uhesse.files.wordpress.com/2019/09/hyper7.png?w=131&h=150 131w, https://uhesse.files.wordpress.com/2019/09/hyper7.png?w=262&h=300 262w, https://uhesse.files.wordpress.com/2019/09/hyper7.png?w=768&h=878 768w, https://uhesse.files.wordpress.com/2019/09/hyper7.png 982w" sizes="(max-width: 620px) 100vw, 620px" />

The IP above can be different as long as it doesn’t conflict with other IPs used in your virtual environment. I find it convenient to let it end with the digit 1, though.

Create the License Server

In Hyper-V Manager, click New then Virtual Machine:

https://uhesse.files.wordpress.com/2019/09/hyper8.png?w=1974&h=436 1974w, https://uhesse.files.wordpress.com/2019/09/hyper8.png?w=150&h=33 150w, https://uhesse.files.wordpress.com/2019/09/hyper8.png?w=300&h=66 300w, https://uhesse.files.wordpress.com/2019/09/hyper8.png?w=768&h=169 768w, https://uhesse.files.wordpress.com/2019/09/hyper8.png?w=1024&h=226 1024w" sizes="(max-width: 987px) 100vw, 987px" />

Do not use Quick Create.

Give it the name ls and click Next:

https://uhesse.files.wordpress.com/2019/09/hyper9.png?w=1240&h=740 1240w, https://uhesse.files.wordpress.com/2019/09/hyper9.png?w=150&h=90 150w, https://uhesse.files.wordpress.com/2019/09/hyper9.png?w=300&h=179 300w, https://uhesse.files.wordpress.com/2019/09/hyper9.png?w=768&h=458 768w, https://uhesse.files.wordpress.com/2019/09/hyper9.png?w=1024&h=611 1024w" sizes="(max-width: 620px) 100vw, 620px" />

It must be Generation 1:

https://uhesse.files.wordpress.com/2019/09/hyper10.png?w=1580&h=436 1580w, https://uhesse.files.wordpress.com/2019/09/hyper10.png?w=150&h=41 150w, https://uhesse.files.wordpress.com/2019/09/hyper10.png?w=300&h=83 300w, https://uhesse.files.wordpress.com/2019/09/hyper10.png?w=768&h=212 768w, https://uhesse.files.wordpress.com/2019/09/hyper10.png?w=1024&h=283 1024w" sizes="(max-width: 790px) 100vw, 790px" />

Give it 1500 MB memory if your host has >= 16 GB memory, else give it 1100 MB. De-select Use Dynamic Memory:

https://uhesse.files.wordpress.com/2019/09/hyper11.png?w=1556&h=364 1556w, https://uhesse.files.wordpress.com/2019/09/hyper11.png?w=150&h=35 150w, https://uhesse.files.wordpress.com/2019/09/hyper11.png?w=300&h=70 300w, https://uhesse.files.wordpress.com/2019/09/hyper11.png?w=768&h=180 768w, https://uhesse.files.wordpress.com/2019/09/hyper11.png?w=1024&h=240 1024w" sizes="(max-width: 778px) 100vw, 778px" />

Do not yet connect it to a network:

https://uhesse.files.wordpress.com/2019/09/hyper12.png?w=1536&h=272 1536w, https://uhesse.files.wordpress.com/2019/09/hyper12.png?w=150&h=27 150w, https://uhesse.files.wordpress.com/2019/09/hyper12.png?w=300&h=53 300w, https://uhesse.files.wordpress.com/2019/09/hyper12.png?w=1024&h=181 1024w" sizes="(max-width: 768px) 100vw, 768px" />

Give it a disk of 100 GB maximum size:

https://uhesse.files.wordpress.com/2019/09/hyper13.png?w=1518&h=406 1518w, https://uhesse.files.wordpress.com/2019/09/hyper13.png?w=150&h=40 150w, https://uhesse.files.wordpress.com/2019/09/hyper13.png?w=300&h=80 300w, https://uhesse.files.wordpress.com/2019/09/hyper13.png?w=768&h=205 768w, https://uhesse.files.wordpress.com/2019/09/hyper13.png?w=1024&h=273 1024w" sizes="(max-width: 759px) 100vw, 759px" />

Select Install operating system later:

https://uhesse.files.wordpress.com/2019/09/hyper14.png?w=1462&h=540 1462w, https://uhesse.files.wordpress.com/2019/09/hyper14.png?w=150&h=55 150w, https://uhesse.files.wordpress.com/2019/09/hyper14.png?w=300&h=111 300w, https://uhesse.files.wordpress.com/2019/09/hyper14.png?w=768&h=284 768w, https://uhesse.files.wordpress.com/2019/09/hyper14.png?w=1024&h=378 1024w" sizes="(max-width: 731px) 100vw, 731px" />

After creating ls, click on Settings:

https://uhesse.files.wordpress.com/2019/09/hyper15.png?w=1240&h=910 1240w, https://uhesse.files.wordpress.com/2019/09/hyper15.png?w=150&h=110 150w, https://uhesse.files.wordpress.com/2019/09/hyper15.png?w=300&h=220 300w, https://uhesse.files.wordpress.com/2019/09/hyper15.png?w=768&h=564 768w, https://uhesse.files.wordpress.com/2019/09/hyper15.png?w=1024&h=751 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Add a Legacy Network Adapter:

https://uhesse.files.wordpress.com/2019/09/hyper16.png?w=1240&h=488 1240w, https://uhesse.files.wordpress.com/2019/09/hyper16.png?w=150&h=59 150w, https://uhesse.files.wordpress.com/2019/09/hyper16.png?w=300&h=118 300w, https://uhesse.files.wordpress.com/2019/09/hyper16.png?w=768&h=302 768w, https://uhesse.files.wordpress.com/2019/09/hyper16.png?w=1024&h=402 1024w" sizes="(max-width: 620px) 100vw, 620px" />

We need Legacy Adapters in the VMs because later, the data nodes need to boot from network and that requires Legacy Adapters to be used. Connect it to the Virtual Switch edu-cluster-interconnect and click Apply.

Connect a normal (not legacy) Network Adapter to the switch edu-public-network:

https://uhesse.files.wordpress.com/2019/09/hyper17.png?w=1240&h=1104 1240w, https://uhesse.files.wordpress.com/2019/09/hyper17.png?w=150&h=134 150w, https://uhesse.files.wordpress.com/2019/09/hyper17.png?w=300&h=267 300w, https://uhesse.files.wordpress.com/2019/09/hyper17.png?w=768&h=684 768w, https://uhesse.files.wordpress.com/2019/09/hyper17.png?w=1024&h=912 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Confirm the boot order is CD first for ls:

https://uhesse.files.wordpress.com/2019/09/hyper18.png?w=1240&h=472 1240w, https://uhesse.files.wordpress.com/2019/09/hyper18.png?w=150&h=57 150w, https://uhesse.files.wordpress.com/2019/09/hyper18.png?w=300&h=114 300w, https://uhesse.files.wordpress.com/2019/09/hyper18.png?w=768&h=292 768w, https://uhesse.files.wordpress.com/2019/09/hyper18.png?w=1024&h=389 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Now power on the virtual machine just created and configured. It should come up with this screen and you type in install

https://uhesse.files.wordpress.com/2019/09/hyper19-1.png?w=150&h=79 150w, https://uhesse.files.wordpress.com/2019/09/hyper19-1.png?w=300&h=158 300w, https://uhesse.files.wordpress.com/2019/09/hyper19-1.png 713w" sizes="(max-width: 620px) 100vw, 620px" />

There’s no need for device encryption on an educational system. Tab to OK and press return:

https://uhesse.files.wordpress.com/2019/09/hyper20-1.png?w=150&h=76 150w, https://uhesse.files.wordpress.com/2019/09/hyper20-1.png?w=300&h=152 300w, https://uhesse.files.wordpress.com/2019/09/hyper20-1.png 711w" sizes="(max-width: 620px) 100vw, 620px" />

Confirm the LS number as 10. Tab to OK and press return:

https://uhesse.files.wordpress.com/2019/09/hyper21.png?w=150&h=74 150w, https://uhesse.files.wordpress.com/2019/09/hyper21.png?w=300&h=149 300w, https://uhesse.files.wordpress.com/2019/09/hyper21.png 711w" sizes="(max-width: 620px) 100vw, 620px" />

Confirm to install EXAClusterOS on first boot. Tab to OK and press return:

https://uhesse.files.wordpress.com/2019/09/hyper22.png?w=150&h=74 150w, https://uhesse.files.wordpress.com/2019/09/hyper22.png?w=300&h=149 300w, https://uhesse.files.wordpress.com/2019/09/hyper22.png 715w" sizes="(max-width: 620px) 100vw, 620px" />

Enter exasol12 as the password for the maintenance user:

https://uhesse.files.wordpress.com/2019/09/hyper23.png?w=150&h=74 150w, https://uhesse.files.wordpress.com/2019/09/hyper23.png?w=300&h=149 300w, https://uhesse.files.wordpress.com/2019/09/hyper23.png 715w" sizes="(max-width: 620px) 100vw, 620px" />

Check with ipconfig (using the cmd shell) for the Ethernet adapter vEthernet (edu-public-network): Then replace the last digit 1 with 10 for the IP of the public interface. It should be 192.168.43.10

https://uhesse.files.wordpress.com/2019/09/hyper24.png?w=1240&h=282 1240w, https://uhesse.files.wordpress.com/2019/09/hyper24.png?w=150&h=34 150w, https://uhesse.files.wordpress.com/2019/09/hyper24.png?w=300&h=68 300w, https://uhesse.files.wordpress.com/2019/09/hyper24.png?w=768&h=175 768w, https://uhesse.files.wordpress.com/2019/09/hyper24.png?w=1024&h=233 1024w" sizes="(max-width: 620px) 100vw, 620px" />

https://uhesse.files.wordpress.com/2019/09/hyper25.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/hyper25.png?w=300 300w" sizes="(max-width: 485px) 100vw, 485px" />

Check the network configuration comparing it to the tab Networking in Hyper-V Manager

https://uhesse.files.wordpress.com/2019/09/hyper26.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/hyper26.png?w=300 300w" sizes="(max-width: 511px) 100vw, 511px" />

Private must match edu-cluster-interconect and Public must match edu-public-network

https://uhesse.files.wordpress.com/2019/09/hyper27.png?w=150&h=27 150w, https://uhesse.files.wordpress.com/2019/09/hyper27.png?w=300&h=54 300w, https://uhesse.files.wordpress.com/2019/09/hyper27.png 684w" sizes="(max-width: 620px) 100vw, 620px" />

Click on Configure in the Advanced Network configuration to change it accordingly otherwise:

https://uhesse.files.wordpress.com/2019/09/hyper28.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/hyper28.png?w=300 300w" sizes="(max-width: 533px) 100vw, 533px" />

Confirm the (corrected) network configuration. Tab to OK and press return:

https://uhesse.files.wordpress.com/2019/09/hyper29.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/hyper29.png?w=300 300w" sizes="(max-width: 476px) 100vw, 476px" />

This triggers the installation of various components on the License Server and takes some time, depending on the hardware resources of your machine. The critical resource is CPU, so try to avoid running anything else on your machine that consumes CPU during the install.

If the License Server reboots during that process and presents the choice to install, update or boot from local disk, type in local. You may then remove the virtual CD from the CD drive of the VM.

When prompted for login on the node n0010, you may login as the OS user maintenance with the password exasol12 :

https://uhesse.files.wordpress.com/2019/09/hyper30.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/hyper30.png?w=300 300w" sizes="(max-width: 498px) 100vw, 498px" />

Refresh until it shows EXAoperation status: Online

This may take several Minutes depending on your hardware.

Connect to EXAoperation

Now open a Chrome browser (preferred) with the https URL of your License Server’s IP:

https://192.168.43.10

https://uhesse.files.wordpress.com/2019/09/hyper31.png?w=150&h=103 150w, https://uhesse.files.wordpress.com/2019/09/hyper31.png?w=300&h=207 300w, https://uhesse.files.wordpress.com/2019/09/hyper31.png 630w" sizes="(max-width: 620px) 100vw, 620px" />

User Name is admin, Password is admin

Check Network Configuration

The network configuration should look like this:

https://uhesse.files.wordpress.com/2019/09/hyper32.png?w=150&h=143 150w, https://uhesse.files.wordpress.com/2019/09/hyper32.png?w=300&h=286 300w, https://uhesse.files.wordpress.com/2019/09/hyper32.png 756w" sizes="(max-width: 620px) 100vw, 620px" />

Click on Edit and modify it to the above settings otherwise. You may change the Cluster Name to something else. Notice that the value None is not allowed for NTP Servers and you have to remove it. Then click Apply.

Add Monitoring Service

To be able to follow the node’s installation, it’s useful to add a monitoring service now. Click on Services at the left and then on the Add button:

https://uhesse.files.wordpress.com/2019/09/monitoringservice.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/monitoringservice.png?w=300 300w" sizes="(max-width: 560px) 100vw, 560px" />

Select all cluster services with the Log Priority Information to get the most verbose output, then click Add.

Add first data node

In Hyper-V Manager, create another VM with the name n11:

https://uhesse.files.wordpress.com/2019/09/hyper33.png?w=150&h=76 150w, https://uhesse.files.wordpress.com/2019/09/hyper33.png?w=300&h=151 300w, https://uhesse.files.wordpress.com/2019/09/hyper33.png 707w" sizes="(max-width: 620px) 100vw, 620px" />

Specify Generation 1 on next page.

Give it 2500 MB memory if your host has >=16 GB  and 2200 MB otherwise and de-select dynamic memory:

https://uhesse.files.wordpress.com/2019/09/hyper34.png?w=150&h=57 150w, https://uhesse.files.wordpress.com/2019/09/hyper34.png?w=300&h=114 300w, https://uhesse.files.wordpress.com/2019/09/hyper34.png 697w" sizes="(max-width: 620px) 100vw, 620px" />

Give it a 100 GB max. sized disk and name it n11sda:

https://uhesse.files.wordpress.com/2019/09/hyper35.png?w=150&h=53 150w, https://uhesse.files.wordpress.com/2019/09/hyper35.png?w=300&h=107 300w, https://uhesse.files.wordpress.com/2019/09/hyper35.png 682w" sizes="(max-width: 620px) 100vw, 620px" />

Select install OS later and finish the creation dialog. Then click on settings. Add a legacy network adapter to n11 and connect it to the switch edu-cluster-interconnect:

https://uhesse.files.wordpress.com/2019/09/hyper36.png?w=150&h=58 150w, https://uhesse.files.wordpress.com/2019/09/hyper36.png?w=300&h=117 300w, https://uhesse.files.wordpress.com/2019/09/hyper36.png 718w" sizes="(max-width: 620px) 100vw, 620px" />

Connect another normal network adapter to the switch edu-public-network.

Configure the boot order for n11 with legacy network adapter first:

https://uhesse.files.wordpress.com/2019/09/hyper37.png?w=150&h=56 150w, https://uhesse.files.wordpress.com/2019/09/hyper37.png?w=300&h=112 300w, https://uhesse.files.wordpress.com/2019/09/hyper37.png 697w" sizes="(max-width: 620px) 100vw, 620px" />

Add a second hard drive to n11:

https://uhesse.files.wordpress.com/2019/09/hyper38.png?w=150&h=67 150w, https://uhesse.files.wordpress.com/2019/09/hyper38.png?w=300&h=134 300w, https://uhesse.files.wordpress.com/2019/09/hyper38.png 701w" sizes="(max-width: 620px) 100vw, 620px" />

Select New Virtual Harddisk of type VHDX, dynamically expanding up to 100 GB max. and name it n11sdb:

https://uhesse.files.wordpress.com/2019/09/hyper39.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/hyper39.png?w=300 300w" sizes="(max-width: 481px) 100vw, 481px" />

We need to know the MAC addresses of the data nodes upfront to enter them in EXAoperation, so the data nodes can connect to the license server to get booted over network. The MAC addresses below can be different as long as you know they do not conflict with other machines in your virtual environment,

Select Advanced Features of the legacy network adapter and configure it with a static MAC address of 08:00:27:A9:D1:22

https://uhesse.files.wordpress.com/2019/09/hyper40.png?w=150&h=92 150w, https://uhesse.files.wordpress.com/2019/09/hyper40.png?w=300&h=184 300w, https://uhesse.files.wordpress.com/2019/09/hyper40.png 651w" sizes="(max-width: 620px) 100vw, 620px" />

Select Advanced Features of the normal network adapter and configure a static MAC address of  08:00:27:92:10:6B

https://uhesse.files.wordpress.com/2019/09/hyper41.png?w=150&h=108 150w, https://uhesse.files.wordpress.com/2019/09/hyper41.png?w=300&h=217 300w, https://uhesse.files.wordpress.com/2019/09/hyper41.png 663w" sizes="(max-width: 620px) 100vw, 620px" />

Do not yet power on the new VM. Instead, click on Add in the EXAoperation Nodes screen:

https://uhesse.files.wordpress.com/2019/09/hyper42.png?w=150&h=89 150w, https://uhesse.files.wordpress.com/2019/09/hyper42.png?w=300&h=177 300w" sizes="(max-width: 620px) 100vw, 620px" />

Configure the added node:

https://uhesse.files.wordpress.com/2019/09/hyper43.png?w=91 91w, https://uhesse.files.wordpress.com/2019/09/hyper43.png?w=182 182w" sizes="(max-width: 497px) 100vw, 497px" />

Click on Add, then click on the new node to configure it further:

https://uhesse.files.wordpress.com/2019/09/hyper44.png?w=150&h=70 150w, https://uhesse.files.wordpress.com/2019/09/hyper44.png?w=300&h=141 300w, https://uhesse.files.wordpress.com/2019/09/hyper44.png 726w" sizes="(max-width: 620px) 100vw, 620px" />

Scroll down on the node’s detail page and click on Disks:

https://uhesse.files.wordpress.com/2019/09/hyper45.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/hyper45.png?w=300 300w" sizes="(max-width: 535px) 100vw, 535px" />

Click on Edit on the EXACluster Disk Information for node n0011 screen:

https://uhesse.files.wordpress.com/2019/09/hyper46.png?w=150&h=33 150w, https://uhesse.files.wordpress.com/2019/09/hyper46.png?w=300&h=66 300w" sizes="(max-width: 620px) 100vw, 620px" />

Add the device /dev/sda with the other values like on the picture:

https://uhesse.files.wordpress.com/2019/09/hyper47.png?w=150&h=112 150w, https://uhesse.files.wordpress.com/2019/09/hyper47.png?w=300&h=224 300w" sizes="(max-width: 620px) 100vw, 620px" />

Do this accordingly for the other three storage partitions. Make sure to reduce the size to 30 GB for the Data partition and assign /dev/sdb for the Storage partition. It should look like this in the end:

https://uhesse.files.wordpress.com/2019/09/hyper48.png?w=150&h=32 150w, https://uhesse.files.wordpress.com/2019/09/hyper48.png?w=300&h=63 300w" sizes="(max-width: 620px) 100vw, 620px" />

Now power on the n11 VM. It should come up booting from network and start installing. Check that the install starts normally without errors:

https://uhesse.files.wordpress.com/2019/09/hyper49.png?w=150&h=69 150w, https://uhesse.files.wordpress.com/2019/09/hyper49.png?w=300&h=139 300w, https://uhesse.files.wordpress.com/2019/09/hyper49.png?w=768&h=355 768w, https://uhesse.files.wordpress.com/2019/09/hyper49.png 1000w" sizes="(max-width: 620px) 100vw, 620px" />

If you see errors in the log at this point, turn off the VM and check the configuration as above described, especially the disk layout. After having corrected it, power the VM on again. Make sure the state of the node shows as Unknown to install (Not Unknown Active) here. Execute the action Set install flag for the node to change it to the state Unknown to install otherwise.

While the install of n11 is ongoing, add the second data node as a Hyper-V VM just like the n11 VM before. Give it the name n12 with all the same properties as n11, except these MAC addresses:

Legacy network adapter (Private Network) 08:00:27:AA:61:8D

Normal network adapter (Public Network)  08:00:27:A3:AB:46

After having created n12 in Hyper-V, go to EXAoperation and click on the n11 node:

https://uhesse.files.wordpress.com/2019/09/hyper50.png?w=150&h=70 150w, https://uhesse.files.wordpress.com/2019/09/hyper50.png?w=300&h=141 300w, https://uhesse.files.wordpress.com/2019/09/hyper50.png 726w" sizes="(max-width: 620px) 100vw, 620px" />

Scroll down on the node’s detail page and click on Copy Node.

Change the node numbers to 12 and the MAC addresses as above listed:

https://uhesse.files.wordpress.com/2019/09/hyper51.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/hyper51.png?w=300 300w" sizes="(max-width: 393px) 100vw, 393px" />

Click on Copy Node again to finish the creation of n12.

Click on the Nodes screen:

https://uhesse.files.wordpress.com/2019/09/hyper52.png?w=150&h=53 150w, https://uhesse.files.wordpress.com/2019/09/hyper52.png?w=300&h=106 300w, https://uhesse.files.wordpress.com/2019/09/hyper52.png?w=768&h=271 768w, https://uhesse.files.wordpress.com/2019/09/hyper52.png 918w" sizes="(max-width: 620px) 100vw, 620px" />

The install of n11 is still ongoing and n12 is now ready to start in Hyper-V. Power it on.

It should come up and install like n11. The install ends with the nodes prompting for login and a message like Boot process finished after xxx seconds in the logservice.

The install consumes much CPU resources. Try to avoid running anything else on the machine while it is ongoing. It may take quite a long while to complete, depending on your local machine power.

It looks like this in the end:

https://uhesse.files.wordpress.com/2019/09/hyper53.png?w=150&h=44 150w, https://uhesse.files.wordpress.com/2019/09/hyper53.png?w=300&h=88 300w, https://uhesse.files.wordpress.com/2019/09/hyper53.png?w=768&h=225 768w, https://uhesse.files.wordpress.com/2019/09/hyper53.png 901w" sizes="(max-width: 620px) 100vw, 620px" />

Now select the two nodes and execute the action Set active flag for them:

https://uhesse.files.wordpress.com/2019/09/hyper54.png?w=150&h=68 150w, https://uhesse.files.wordpress.com/2019/09/hyper54.png?w=300&h=135 300w, https://uhesse.files.wordpress.com/2019/09/hyper54.png 715w" sizes="(max-width: 620px) 100vw, 620px" />

Their state should now change to Running Active.

On the EXAStorage screen, click on Startup Storage Service:

https://uhesse.files.wordpress.com/2019/09/hyper55.png?w=150&h=52 150w, https://uhesse.files.wordpress.com/2019/09/hyper55.png?w=300&h=105 300w, https://uhesse.files.wordpress.com/2019/09/hyper55.png 682w" sizes="(max-width: 620px) 100vw, 620px" />

Now select the two data nodes and click on Add Unused Disks:

https://uhesse.files.wordpress.com/2019/09/hyper56.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/hyper56.png?w=300 300w" sizes="(max-width: 509px) 100vw, 509px" />

Add a data volume

On the EXAoperation Storage screen, click on Add Volume:

https://uhesse.files.wordpress.com/2019/09/hyper57.png?w=150&h=39 150w, https://uhesse.files.wordpress.com/2019/09/hyper57.png?w=300&h=78 300w, https://uhesse.files.wordpress.com/2019/09/hyper57.png?w=768&h=201 768w, https://uhesse.files.wordpress.com/2019/09/hyper57.png 815w" sizes="(max-width: 620px) 100vw, 620px" />

Specify a Redundancy of 2, add user admin to Allowed Users, Volume Size should be 8 GB, add n11 and n12 to the Nodes List, Number of Master Nodes is 2 and Disk is d03_storage:

https://uhesse.files.wordpress.com/2019/09/hyper58.png?w=107&h=150 107w, https://uhesse.files.wordpress.com/2019/09/hyper58.png?w=214&h=300 214w" sizes="(max-width: 620px) 100vw, 620px" />

The new volume should then look like this:

https://uhesse.files.wordpress.com/2019/09/hyper59.png?w=150&h=31 150w, https://uhesse.files.wordpress.com/2019/09/hyper59.png?w=300&h=63 300w, https://uhesse.files.wordpress.com/2019/09/hyper59.png 740w" sizes="(max-width: 620px) 100vw, 620px" />

Create a database

On the EXASolution screen, click on Add:

https://uhesse.files.wordpress.com/2019/09/hyper60.png?w=150&h=91 150w, https://uhesse.files.wordpress.com/2019/09/hyper60.png?w=300&h=183 300w" sizes="(max-width: 620px) 100vw, 620px" />

On the Add Database screen, specify 2 Active Nodes, assign the two data nodes and click Add

https://uhesse.files.wordpress.com/2019/09/hyper61.png?w=120&h=150 120w, https://uhesse.files.wordpress.com/2019/09/hyper61.png?w=240&h=300 240w, https://uhesse.files.wordpress.com/2019/09/hyper61.png 649w" sizes="(max-width: 620px) 100vw, 620px" />

The new database shows a Status of Not created. Click on the database link:

https://uhesse.files.wordpress.com/2019/09/hyper62.png?w=150&h=34 150w, https://uhesse.files.wordpress.com/2019/09/hyper62.png?w=300&h=68 300w, https://uhesse.files.wordpress.com/2019/09/hyper62.png?w=768&h=175 768w, https://uhesse.files.wordpress.com/2019/09/hyper62.png 804w" sizes="(max-width: 620px) 100vw, 620px" />

Select the Action Create and click Submit:

https://uhesse.files.wordpress.com/2019/09/hyper63.png?w=150&h=31 150w, https://uhesse.files.wordpress.com/2019/09/hyper63.png?w=300&h=61 300w, https://uhesse.files.wordpress.com/2019/09/hyper63.png?w=768&h=156 768w, https://uhesse.files.wordpress.com/2019/09/hyper63.png 849w" sizes="(max-width: 620px) 100vw, 620px" />

The Action should change to Startup, n11 and n12 appear as Selected. Click Submit again:

https://uhesse.files.wordpress.com/2019/09/hyper64.png?w=150&h=30 150w, https://uhesse.files.wordpress.com/2019/09/hyper64.png?w=300&h=59 300w, https://uhesse.files.wordpress.com/2019/09/hyper64.png?w=768&h=152 768w, https://uhesse.files.wordpress.com/2019/09/hyper64.png 894w" sizes="(max-width: 620px) 100vw, 620px" />

The State changes to Starting for n11 and n12. Click on EXASolution on the Services menu on the left:

The new database should now show as Online.

https://uhesse.files.wordpress.com/2019/09/hyper65.png?w=150&h=33 150w, https://uhesse.files.wordpress.com/2019/09/hyper65.png?w=300&h=65 300w, https://uhesse.files.wordpress.com/2019/09/hyper65.png?w=768&h=167 768w, https://uhesse.files.wordpress.com/2019/09/hyper65.png 844w" sizes="(max-width: 620px) 100vw, 620px" />

Congratulations for going the whole way, it was a bit long at times, wasn’t it? But now you have your own Exasol cluster sandbox on Hyper-V – have fun with it!

Going forward, I find it convenient to create Hyper-V checkpoints with the database and storage service shutdown and the nodes having the cluster services shutdown as well. That way I make sure nothing can change on the disks of the data nodes when I take the checkpoint. I can then just turn off the VMs and apply these checkpoints afterwards. Then starting the VMs saves me the time they would need to go through the normal boot process otherwise. My next article will explain how to add a reserve node to this cluster, bringing it from 2+0 to 2+1. Hope you find this mini-series useful </p />
</p></div>

    	  	<div class=