Limitations of SSB under VMware
The following limitations apply to running version 7.0.4 LTS of SSB under VMware:
-
SSB can be installed under the following VMware versions:
-
SSB supports both thin and thick provisioning but can only use fixed disk space assigned to the virtual host. To increase the virtual disk size, you must power down SSB, as it does not support on-the-fly disk allocation scenarios. To increase the size of the virtual disk, see Increasing the virtual disk size of SSB under a virtual machine.
-
If High Availability (HA) operation mode is required in a virtual environment, use the HA function provided by the virtual environment.
-
Hardware-related alerts and status indicators of SSB may display inaccurate information, for example, display degraded RAID status.
-
Creating Quiesced snapshots is not supported. Disable this option when taking a snapshot of your SSB appliance, otherwise the boot firmware of the appliance becomes tainted.
Installing SSB under VMware ESXi/ESX
The following describes how to install a new SSB under VMware ESXi or ESX.
To install a new SSB under VMware ESXi or ESX
-
Create the virtual machine for SSB using the following settings:
-
Guest operating system: Linux/Ubuntu 64-bit.
-
Allocate memory for the virtual machine. SSB requires a minimum of 1 GiB of memory, in addition to the memory limit of the indexed logspaces. The recommended size for the memory depends on the exact environment, but consider the following:
-
The base system requires 256 MiB.
-
The syslog-ng server running on SSB requires between 128 MiB and 1 GiB of memory, depending on the message load and on the configuration of SSB.
-
For every logspace, SSB requires additional memory to index the incoming messages. The amount of memory allocated for the indexer can be set individually for every logspace.
-
The hard disk controller must be LSI Logic Parallel or LSI Logic SAS.
-
Do not use RAID for the hard disk, use the data duplication features of your virtual environment instead. That way, a single hard disk is sufficient for the system. If you need to use the built-in RAID support of SSB for some reason, use two hard disks, and SSB will automatically use them in software RAID.
|
|
Caution:
Hazard of data loss When you install or reinstall SSB in a virtual environment, always create new hard disks. Using existing hard disks can cause unexpected behavior and operational problems. |
-
Configure a fixed size disk with at least 8 GiB space.
About 5 GB is required for the base system, the remaining disk space is used to store data. To increase the initial disk size, see Increasing the virtual disk size of SSB under a virtual machine.
-
SSB requires that you use either 1 network card or 4 network cards, all of them must be VMXNET3.
-
After creating the virtual machine, edit the settings of the machine. Set the following options:
-
Under Options > VMware Tools, enable the Shutdown, Suspend, Reset options, otherwise the SSB administrator will not be able to access these functions from the SSB web interface.
-
Under Options > Boot options, enable the Force BIOS Setup option. This is required to be able to check the system time (and modify it if needed) before installing SSB.
-
Log in to the support portal and download the latest syslog-ng Store Box installation ISO file. Note that you need to have purchased SSB as a virtual appliance or have partner access to download syslog-ng Store Box ISO files. If you are a partner but do not see the ISO files, you can request partner access within the support portal.
-
Mount the ISO image and boot the virtual machine. Follow the on-screen instructions to install SSB.
Once installation successfully completes, the virtual machine will restart automatically.
In case installation fails, a message will be displayed instructing you to press Ctrl+Alt+Delete to reboot the virtual machine.
syslog-ng Store Box Hyper-V Installation Guide
syslog-ng Store Box Hyper-V Installation Guide
This tutorial describes the possibilities and limitations of installing syslog-ng Store Box (SSB) 7.0.4 LTS as a virtual appliance under a Hyper-V server.
Limitations of SSB under Hyper-V
Version 7.0.4 LTS of SSB has no special support for running under Hyper-V. While the basic functionality of SSB is not affected by running as a virtual appliance, the following limitations apply:
-
If High Availability (HA) operation mode is required in a virtual environment, use the HA function provided by the virtual environment.
-
Hardware-related alerts and status indicators of SSB may display inaccurate information, for example, display degraded RAID status.
-
-
When rebooting SSB in Hyper-V, the following critical error message may appear in the event log of the Hyper-V host:
<Virtual machine name> was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault.
This is normal, there is no problem with SSB. For details, see Triple fault in event log shows reset of Linux virtual machines.
