• Contents
  • 1 About the chapters of this manual
  • 2 An introduction to Virtual Server Appliance
  • 3 Activate the VSA
  • 4 Configuration Assistant
  • 5 Install additional HELIOS products
  • 6 Linux Runtime
  • 7 Volume Management
  • A System and data disk migration
• <
• 6 Linux Runtime
  • 6.1 Single-user/recovery mode
  • 6.2 SSH server
  • 6.3 NFS services
  •  6.3.1 Features
  •  6.3.2 Enable/disable NFS services
  •  6.3.3 NFS usage scenarios
  •  6.3.4 NFS client and server platform specifics
  •  6.3.5 VSA Linux man pages related to RPC/​NFS
  • 6.4 Linux Java runtime
  • 6.5 Included Linux packages
  • 6.6 Root file system
• >

6 Linux Runtime

The HELIOS Virtual Server Appliance Linux runtime is optimized for the exclusive use of HELIOS software server products. It includes only those Linux components that are required to run the HELIOS services. HELIOS provides full support for the Linux runtime, however non-HELIOS server products or additional Linux packages are not supported by HELIOS.

The Linux runtime is based on an 64 bit system (x86_64). Once Linux is started, a login as root will open the HELIOS Configuration Assistant.

6.1 Single-user/recovery mode

When starting the virtual machine, a blue “GNU GRUB” menu appears. Selecting “(recovery mode)” via the cursor and pressing RETURN allows booting into a single-user Linux for maintenance purposes, without any additional services (no HELIOS, no other Linux services). Entering the root password opens a shell. The root file system is mounted and the LVM (Logical Volume Manager) is active. Typing exit continues the regular boot process into multi-user mode.

6.2 SSH server

The only activated Linux network service after booting is the SSH server, to allow remote logins.

6.3 NFS services

HELIOS Virtual Server Appliance includes complete Linux NFS server and client services. These use RPC (Remote Procedure Call) services, which are always active by default. The NFS server will automatically be started when NFS shares are configured. The NFS server and client configuration is best done with the Configuration Assistant (see 4.2.2 “Network setup (hostname, IP addresses, DHCP, NFS)”). Consult your Linux manuals for more NFS details.

6.3.1 Features

• NFS 4 support:

  • NFS 4 server and clients can negotiate best communication parameters

• Support for NFS 2 & 3 protocol versions:

  • The NFS client can also mount shares by use of the NFS 2 or 3 protocol

  • The NFS server also offers the NFS 2 & 3 protocol

• NFS protocol version differences:

  • NFSv4: max. read-write size 1 MB, unlimited file size, stateful

  • NFSv3: max. read-write size 64 kB, unlimited file size, stateless

  • NFSv2: max. read-write size 8 kB, 2 GB file size limit, stateless

6.3.2 Enable/disable NFS services

Manually enabling/disabling NFS/RPC services is only needed if customers wish to stop these services for security reasons (stop RPC service daemons from listening on IP ports anymore), or if they have no use for them.

Note:

Before these services can be disabled, make sure that neither NFS shares are exported nor NFS mounts are connected. If required, use Configuration Assistant to remove the exported shares and NFS mounts.

Issue the following commands:

# service nfs-kernel-server stop
# service nfs-common stop
# service rpcbind stop

Issue the following commands:

# update-rc.d nfs-kernel-server remove
# update-rc.d nfs-common remove
# update-rc.d rpcbind remove

In case you installed additional services that also require RPC or NFS services, you must disable these additional services before disabling NFS and RPC services.

You can check dependencies with the apt-cache rdepends command, e.g.:

#  apt-cache rdepends rpcbind

If required, NFS services can be re-enabled at a later point in time.

Issue the following commands:

# update-rc.d rpcbind defaults
# update-rc.d nfs-common defaults
# update-rc.d nfs-kernel-server defaults

# service rpcbind start
# service nfs-common start
# service nfs-kernel-server start

6.3.3 NFS usage scenarios

• Mac or Windows clients should use their native protocols, AFP or CIFS respectively, because these are most compatible and performant

• Linux or UNIX clients can access data on this server via NFS

• Data on other Linux or UNIX servers can be accessed via NFS

• Backups with “dt sync” can be done by letting a Linux/​UNIX NFSv3 or NFSv4 client read from the VSA (compatible HELIOS versions required, i.e. HELIOS UB64 for sync source and destination)

6.3.4 NFS client and server platform specifics

This section contains some information about platform specifics for NFS client or server for the currently supported HELIOS UB64 platforms Solaris (SPARC and x86), AIX, OS X, Linux. See also www.helios.de/platforms.

• All NFS clients use the “mount” and “umount” commands

• All NFS servers must have NFS services active and running

On other UNIX platforms, use man -k nfs to find out about NFS related commands and files.

6.3.5 VSA Linux man pages related to RPC/​NFS

The following tables include NFS and NFS-related manual pages. Man pages can be accessed via the man command, e.g. man exports.

6.4 Linux Java runtime

The server includes a headless 64-bit Java SE runtime which is compatible with all HELIOS server products.

6.5 Included Linux packages

The shell command dpkg -l lists a short description of all included packages, including version numbers.

6.6 Root file system

The HELIOS virtual server Linux runtime uses LVM2 for the root file system and for swapping. The system disk volume group is called “rootvg”. Advantages are a flexible storage management and snapshots. The “rootvg” volume group can be managed via the HELIOS Configuration Assistant, in the Manage other volume groups (Advanced storage setup) menu.