You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

General Information

Virtual servers can be used to operate specialized services that the LRZ does not offer directly. These are offered in the "Attended Hosting" operating model. This means that the LRZ installs a supported version of Linux or Windows and provides updates. Before end of support, whole installation will be upgraded or replaced by a new version. The customer receives full administrative access.
These "Managed Servers" are housed on LRZ's own hardware in air-conditioned security areas of the data center with uninterruptible power supply, access protection systems, fire detection and extinguishing systems as well as 24-hour surveillance.

Description of services

  • Setup of the virtual server in the LRZ infrastructure within the defined service parameters according to the customer's requirements
  • Operational provision of the desired operating system
  • Network connection with its own IP address

    • By default, virtual servers are operated either in one of two subnets

      • MWN-wide: private IP address that is available within the Munich Science Network

      • Worldwide: public IP address 

    • For configurations with several servers, it is optionally possible (at an additional cost) to provide a separate VLAN with its own subnet and firewall
  • Operation and troubleshooting of the virtual server
    • Faults are rectified according to the "best effort" principle, i.e. The aim is to resolve the problem quickly, but a fixed solution time cannot be guaranteed.
  • Automatic security updates for operating system components
  • Daily snapshot data backup of the entire storage of the virtual machine (VM) for a period of 14 days
  • Additional snapshot data backup every 4 hours for a period of 24 hours
  • Administrative access for customers
    • The customer receives an ID with administrator rights on the virtual server
    • The customer receives access to a management platform for the following administrative activities
      • Remote maintenance of the installed operating system via the VM console
      • (Re) start and stop the VMs
  • Update of operating system before end of support, i.e. upgrade of version or, if not possible, replace operating system by a new virtual server

Further details can be found in our

Dienstleistungskatalog (DLK), Section 6.1 Managed Server

Answers to frequently asked questions about our LRZ service are available as follows − see also adjacent page hierarchy:

FAQs zu virtuellen Maschinen am LRZ

→ Management virtueller Maschinen   (under construction)

→ Betriebssystem-Management   (under construction)

Administrative requirements

The use of virtual servers requires knowledge of how to regularly install, update and configure the desired services or service software. If software from the so-called standard installation sources is used, the regular automatic update is done by the LRZ. If this is not possible or desired, the customer is responsible for regular software updates. Security updates must be applied within 7 days.

An upgrade to the next higher version will be done before the operating system support period expires. If this is no longer supported, the LRZ provides a new virtual server with an up-to-date operating system. After an appropriate migration phase, the obsolete server is shut down. The customer must plan for sufficient experience to reactivate the desired services when the operating system is renewed.

Available operating systems

SUSE Linux Enterprise Server12 SP5en
15 SP2en

18.04 LTS

20.04 LTSen

Windows Server


en, de

2019en, de



Number vCPUs


RAM size

LinuxWindowsLinux / Windows
1 GiB4 GiB64 GiB

Number of virtual hard disks


Hard disk size

LinuxWindowsLinux / Windows
20 GiB
100 GiB
1.024 GiB
SSD total
5.120 GiB
SATA total


The cost rates differ according to user class. Class 1 includes TUM, LMU and BAdW, class 2 includes all other state Bavarian universities. Class 3 is made up of all state institutions with a scientific mandate in the StMWFK division – see also DLK, chap. 15 user classes and service matrix.

You can ask for the concrete price information via the following entry point:

LRZ Servicedesk

Project binding

To manage and bill the fee-based service, you need to be bound by a so-called LRZ project. The activation of a new LRZ project is described as option 1. If you already have an LRZ project, for example to use the LRZ service "TSM Archive / Backup", you can use this for your purpose; see option 2.

  • Option 1: If you do not yet have a (suitable) LRZ project, a corresponding application must be made by the chair holder or the institute management.
    The LRZ service "Managed Server" must be checked in the project application. The completed project application will be sent to the LRZ supervisor responsible for your facility.

  • Option 2: With an existing project, the master user must apply for a so-called quota for the "VM-Management-Portal".
    This is done in the IDM portal by opening the "[ Permissions/Quotas ]" section in the respective project. In the "Number of permissions:" table, the "VM-Management-Portal" row is also listed. Here the desired quota is entered in the right cell, i.e. in the "requested:" column. Alternatively, the free text field at the bottom of the page can be used to enter an individual request text to the LRZ advisor responsible for the project. Click on the "Send E-mail ..." button to submit the request.

Result: As soon as the responsible LRZ supervisor initiates the project with option 1 and has set up the so-called quota for the "VM-Management-Portal" with access authorization for the master user for both options the master user is authorized to order and manage VMs.

In addition, the master user can expand the access authorization for the "VM-Management-Portal" within the scope of the allocated quota by entering additional accounts. The "ADS" authorization for registration / validation for the "VM-Management-Portal" must also be granted for the respective account.

Note: The master user himself requires "ADS" authorization for authentication, but automatically has access authorization for the "VM-Management-Portal". In the event of access problems, the master user should take a look at the IDM portal: in the list of accounts, the "ADS" column must be crossed for the account of the master user, but not the "VM-Management-Portal" column. In the case of accounts for which the master user grants access authorization, both the "ADS" and the "VM-Management-Portal" column must be checked.

Service requests

For all service requests regarding "Managed Server", especially for the VM actions described below, please use the following link:

This will take you to the "Selfservice area". Please log in there with your master user account and password and describe your request in the "Details" field. By clicking on the blue "Save" button, your request will be sent.

Note: By using the LRZ Servicedesk, all requests are documented and can be traced later in the event of queries, e.g. about billing details. All other communication channels - telephone, e-mail, etc. - are not suitable!

VM order

If the above-mentioned project binding exists, the master user can order the desired VMs using the following VM order forms for Linux or Windows.

Order forms

Please fill in all marked mandatory fields and, if applicable, the optional fields:

Note: So-called "Unattended VMs" are not supported.

VM change

A master user is authorized to request changes, i.e. more or less resources of an existing VM. First of all, it is important to mention the respective VM host name. It is then sufficient to provide the required information.

VM deletion

If you no longer need a VM, please notify us which VM is no longer in use. We will then deprovision the VM and stop calculating the resources used from the day of your notification.

Note: Please keep this point in mind already when ordering the VM. Without official deprovisioning, services will be billed even if they are no longer used.

  • No labels