Release Notes V-Cube & V-Cube+ 6.8.24
Collax V-Cube / Collax V-Cube+
06.12.2018
Installation Notes
Install Update within Cluster
Please read the following release notes carefully, before continuing. When installing this update on a Collax V-Cube+ cluster the following steps have to be performed:
/ Important information
Please have a look at the Collax V-Cube 6.8.22 Release Notes if the nodes have Version 6.8.20 or above and haven’t been updated yet. For this update, it is necessary that both nodes are set in maintenance mode simultaneously.
Procedure
- Click at High Availability within the Dashboard.
- Select the other (not the local) V-Cube+ node and change into the Start Maintenance dialog.
- Now, put this other node into maintenance mode by confirming the query in the dialog. Wait until the maintenance mode is reached. Depending on the number of virtual machines and hard disk, this can take some time. Virtual machines will be migrated live, which can take a few minutes depending on the size of the RAM. The progress will be displayed in the list of background activities.
- Close the dialog.
- In the list of nodes, select again the other node whose software is to be updated by right-clicking it.
- Change to System Update ….
- Click Check for Updates. The completion will be displayed as “100%”.
- Click Download and Install. This function will download the latest software packages from the update server and install them. The completion will be displayed as Install - 100%.
- Close the dialog and set the node to active.
- Please repeat this procedure for the local node.
Issues Fixed in this Version
System Management: Memory Management
This update addresses a problem in the memory management of the Linux kernel. The error usually occurs when there is a lot of (free) memory and a fast I/O backend hits a relatively slow backup target where a large amount of data will be backed up. The data can be read-in very quickly. Because the backup target is slower, it filled up more and more the cache of the memory. In the concrete problem case, the kernel then dealt multiple seconds to sort the memory appropriately wasn’t available for programs/processes. This could also affect resources from the cluster that are time-critical, causing them to fail. This fix configures the setting of the cache so that the problem couldn’t occur anymore.
Notes
V-Cube+: Online Snapshots and backups
You can create an online snapshot or an offline snapshot. Apart from creating a separate snapshot disk, an online snapshot stores the current memory state of the machine during operation. You should commit all snapshots before updating to Collax V-Cube+ 6.8.8. Existing online snapshots can be started after the update but their current memeory state will be lost. Same for backups depending on online snapshots.
V-Cube+: Restore virtual harddiscs
From Collax V-Bien version 6.8.15 on the internal path for virtual harddiscs changes and a restore from previous backups isn’t possible anymore without manual intervention. In case of a baremetal resore please use the previous verion or don’t hesitate to contact support.
Misc: Windows Setup notes Error Message 0x80300001
If Windows Server 2008 R2 and above is to be installed on Virtio hard disks using the Virtio driver CD for Windows, Windows reports the error code 0x80300001. The error message occurs if the partitions are recognized and the user clicks the button Next. The message means, that the installation CD of Windows needs to be inserted again.
Misc: Install Collax-Server from template
When installing a Collax Server from a template only Collax Servers from version 7.x and later are supported. The installation of version 5.x is no longer supported.