VMware Installation

notempty

Dieser Artikel bezieht sich auf eine nicht mehr aktuelle Version!

notempty

Der Artikel für die neueste Version steht hier

notempty

Zu diesem Artikel gibt es bereits eine neuere Version, die sich allerdings auf eine Reseller-Preview bezieht

Installing a UMA VM on VMware

Last adaption: 03.2023

New:

Translation

notempty

This article refers to a Resellerpreview

2.5.10

Introduction

Setup without virtualization

Host with several guest systems

Virtualization software makes it possible to install different systems on a physical computer and use them simultaneously. The individual system is made to believe that it is the sole user of the physical hardware. The aim of this is to divide up the resources of a computer. It is therefore possible to operate several separate systems without having physically separate hardware.
The individual systems are created as virtual machines (VM). The physical computer is called the host. The virtualization software (in this example vSphere Hypervisor formerly ESXi from VMware) is installed on this, which manages the computer resources such as processor power, RAM and network connections and allocates them to the individual guest machines.
The client software vSphere Client from VMware can be used to connect to the vSphere Hypervisor server and administer the host.

The hypervisor virtualization program differs from other virtualization software in that it is itself an operating system and thus does not require an operating system installed on the server.

Preparation

The products vSphere Hypervisor and the vSphere Client are required from the VMware homepage.

Both products are downloaded.

An installation CD is created from the vSphere Hypervisor ISO file.
First, the server operating system vSphere Hypervisor is installed on a suitable machine or server.

Instructions for this can be found on the VMware homepage under the title "Getting started with ESXi Installable".

Then the vSphere Client is installed on the computer from which the server is to be administered.

Using vSphere Client

The vSphere Client is the central tool for managing and editing the vSphere Hypervisor Server. Here, the virtual machines are installed, users are created and the configurations of the various guest systems are defined.

Logging in to the server

Logging in to the server with changed credentials

The client is started.
The first login to the vSphere Hypervisor server is with username root and no password. :The credentials are changed after the first login.
The certificate is confirmed.

Overview

Overview tab of the vSphere Client

The Overview tab shows a summary of the server hardware, settings and resource usage.

Create a virtual machine

In order to install the Securepoint Unified Mail Archive, a guest system, a so-called virtual machine, is required on the server. This is a virtual machine that is assigned resources of the server by the vSphere Hypervisor.

Requirements

Up to version 2.1.2, two network cards must be available to the virtual machine. These network cards must be connected to different networks (virtual switches).
As of version 2.1.3, only one network card is required.
At least 4GB of main memory must be available.
At least 4 vCPUs must be integrated for productive use (current Xeons are recommended).
4GB as first hard disk for the UMA firmware
Depending on the email traffic, sufficient hard disk space must be available. At least 200GB.

Rough calculation basis for archive storage with the recommended 50% safety buffer on the increment:
Inventory data to be imported + data growth for 3 - 5 years x 3.5 = archive storage size

Discrepant size information in screenshots should be ignored.

To create a new virtual machine, there are several ways:

via the menu item File -> New -> virtual machine
via the icon New virtual machine
- in the toolbar
- in the Overview tab in the Commands section.

The Create New Virtual Machine wizard opens.

Create New Virtual Machine Wizard

The wizard will help you to create a new virtual machine.

First, the type of configuration is selected and then Next is clicked.	Wizard 1 - Configuration type
Next, the virtual machine is given a Name. In the example, the name Securepoint UMA was used. Click on Next.	Wizard 2 - Assign a name
In step three, select the data storage where the virtual machine and virtual hard disk will be stored. Click on Next.	Wizard 3 - Select storage pool
This step defines on which VMware version the virtual machine should run. And Next	Wizard 4 - Choosing the version
The operating system of the virtual machine must be selected. The UMA is a Linux system. Since it is a custom build, Other Linux System (32-bit) is selected as the version from the drop-down box. And Next.	Wizard 5 - Choosing the operating system
In this step the number of virtual CPUs is defined. A UMA that is to be used productively needs at least 4 virtual CPUs. Click on Next	Wizard 6 - Determine number of CPUs
Define the size of the RAM. A UMA must be equipped with at least 4 GB of working memory. And Next.	Wizard 7 - Determine the size of the RAM
The number of network cards to be used must be defined here. Only one network card is required to operate the current UMA. If a UMA version prior to 2.1.3 is still used, two network cards are required. However, these must then be connected to different networks (virtual switches). And Next.	Wizard 8 - Network configuration
Here you can select which SCSI controller should be used. Click on Next.	Wizard 9 - Selecting the SCSI controller
Typically, a new virtual hard disk for the UMA operating system is created at this point. And Next.	Wizard 10 - Selecting the type of hard disk
For the first hard disk, a size of 8GB is more than sufficient. The system works much more performant with Thick-Provision Eager Zeroed. Click on Next.	Wizard 11 - Creating a hard disk
Usually nothing needs to be changed in the Advanced Options. And Next.	Wizard 12 - Advanced options
Finally, all selected settings are displayed. These values should be checked again before continuing. Before starting the VM, some adjustments are necessary.	Wizard 13 - Summary of selected settings

Configuration adjustments

Selecting the installation medium

Settings 1 - Adjusting the settings

Next, the UMA ISO image must be included in the virtual machine. To do this, the following is selected.

In the Hardware tab, select the entry New CD/DVD disk 1.
Under Device status, activate the checkbox Connect on power up.
In the Device Type area, activate the Data Storage ISO File radio button.
Click on the Browse button and select the uploaded ISO image in the next dialog.
Finally click on OK in the Browse dialog.

Adding another hard disk

We need a second hard disk for the data archive of the UMA. It should be at least 200GB in size.

Settings 2 - Add a new device

Click on the button Add to add another hard disk.
A new dialog opens in which the device type Hard disk is selected first.
Click on Next.

Settings 3 - Add a new hard disk

Select Create new virtual hard disk.
Click on Next.

* Select Create new virtual hard disk. * Click on Next.

The size of the new hard disk is specified here. Since all emails, documents and other data are stored on this hard disk, it must be dimensioned according to the formula above.
Again, for better performance, the setting Thick-Provision Eager Zeroed should be selected.
Click on Next.

Settings 5 - Add new hard disk

The settings here are left at the default settings.
Click on Next.

Settings 6 - Add new hard disk

Finally, all selected settings are displayed. The settings should be checked again before they are saved by clicking on Finish.

Enable static RAM allocation

The RAM is dynamically allocated by VMware by default. We recommend assigning this statically to the UMA.

Settings 7 - Static RAM

This is done in the configuration overview under the Resources tab under Working memory.
Check the "Reserve all guest memory" box.

Settings 8 - Configuration overview

Finally, all selected settings are displayed. The settings should be checked again before they are saved by clicking on Finish.

Transparent mode

Transparent mode is no longer included as of UMA version 2.5.8.

Transparent Bridge* <ref>Transparent Bridge - Forum Vmware</ref>

For the "Transparent Mode" at least 2 physical NICs are needed, the setup of the bridges can be seen in the following figure:

In addition, the NICs must then be accepted in " Promiscuous mode":