Servers
Virtual servers are just like physical servers.
Virtual servers you create in the DCD are provisioned and hosted at one of IONOS physical data centers. Virtual servers behave exactly like physical servers, and can be configured and managed with your choice of an operating system.
For each server, you can select to a boot from a virtual CD-ROM/DVD drive or a storage device. Any operating system can be used on the platform. The only requirement is the use of KVM VirtIO drivers. IONOS provides for your use a number of ready boot images with current versions of common Windows and Linux operating systems; alternatively, you can upload your own images with our FTP access.

Limitations

Virtual server configurations are subject to the following limits, according to the CPU type:
    AMD CPU: Up to 62 cores and 240 GB RAM
    Intel® CPU: Up to 27 Intel® cores and 120 GB RAM
A single Intel® physical core with Hyper-Threading Technology is exposed to the operating system of your virtual server as two distinct “logical cores”, which process separate threads.

Availability zones

Secure your data, enhance reliability, and set up high-availability scenarios by deploying your virtual servers and storage devices across multiple Availability Zones.
Assigning different Availability Zones ensures that servers or storage devices reside on separate physical resources at IONOS.
For example, a server or a storage device assigned to Availability Zone 1 resides on a different resource than a server or storage device assigned to Availability Zone 2.
You have the following Availability Zone options:
    Zone 1
    Zone 2
    A - Auto (default; our system automatically assigns an Availability Zone upon provisioning)
    Server Availability Zone can also be changed after provisioning
    Storage device Availability Zone is set upon first provisioning and cannot subsequently be changed

Set up a server

The user who creates the server is the resource owner with full root or administrator access rights. A server, once provisioned, retains all its settings (resources, drive allocation, etc.), even after a restart at the operating system level. The server will only be removed from your virtual data center once you delete it in the DCD.
Because the working memory (RAM) size cannot be processed during the initial configuration, newly provisioned servers with more than 8 GB of RAM may not start successfully when created from IONOS Windows images.
We recommend initially setting the RAM size to 8 GB, and rescaling it as needed after the initial provisioning and configuration is complete.

Prerequisites

    You are logged in (?)
    You are the contract owner or an administrator (?)
      or -
    You have permissions to edit the required data center (?)
    The VDC is open (?)

How to set up a server

    Drag the server element from the Palette into the Workspace.
    Configure the server:
    Inspector > Settings tab
      Name: Enter a name that is unique within the VDC.
      Availability Zone: Select a zone in which you want the storage device to be maintained. When you select A - Auto, our system will select a zone automatically.
      The Availability Zone can be changed after provisioning.
      CPU Architecture: Select whether you want your server to run on AMD or Intel® cores.
      You can change the CPU type for a virtual server that is already running. This, however, requires a restart of the virtual server.
      Cores: Specify the number of CPU cores.
      You may change these after provisioning (?)
      Please note the configuration limits above
      RAM: Specify RAM size; you may select anything from 0.25 GB to 240 GB in steps of 0.25 GB.
      You may change these after provisioning (?)
    Inspector > Storage tab
      In order to assign an image and specify the boot device, you must to add and configure a storage element (?)
      CD-ROM: Click on CD-ROM to add a CD-ROM drive so that you can use ISO images to install and configure an operating system from scratch.
    Set up a network by connecting the server to other elements, such as an internet access element or other servers through their NICs (?)
    Configure a firewall (?)
    Provision your changes
    The server is available according to your settings.

Remote console

The Remote Console is used to connect to a server when, for example, no SSH is available. You must have the root or administrator password for this type of log-in to the server.

Prerequisites

    You are logged in (?)
    You are the contract owner or an administrator (?)
      or -
    You have read access to the data center that contains the required server (?)
    Your browser allows pop-ups
    Your browser is supported (?)
    The server is up (?)
    You know the root or administrator password

How to use the remote console

    Start the Remote Console from the server:
      Open the data center containing the required server (?)
      In the Workspace, select the server.
      In the Inspector, click on Remote Console
        or -
      Select Remote Console from the context menu of the server.
    Start the Remote Console from the Start Center (contract owners and administrators only):
      Open the Start Center:
      Menu Bar > Data Center Designer > Open Start Center
      Open the Details of the required data center.
      A list of servers in this data center is displayed.
      Select the server and click Open Remote Console.
      Remote Console version matching your browser opens; you can now log on to the server with root or administrator password.
Use the 'Send Key Combo' button on the top right of the Remote Console window to send shortcut key combinations (such as CTRL+ALT+DEL).
Launch this Remote Console window again with one click by bookmarking its URL address in your browser.
For security reasons, once your session is over, always close the browser used to connect to VM with this bookmark.

Start, stop, or reboot a server

We maintain dedicated resources available for each customer. You do not share your physical CPUs with other IONOS clients. For this reason, the servers, switched off at the operating system level, still incur costs.
You should use the DCD to shut down virtual machines so that resources are completely deallocated and no costs are incurred. Servers deallocated this way remain in your infrastructure, while the resources are released and can then be redistributed.
This can only be done in the DCD. Shutting down a VM at the operating system level alone does not deallocate the resources or suspend the billing. Regardless of how the VM is shut down, it can only be restarted using the DCD.
A reset forces the server to shut down and reboot, but data loss may result.

Prerequisites

    You are logged in (?)
    You are the contract owner or an administrator (?)
      or -
    You have permissions to edit the required data center (?)
    The VDC is open (?)

How to start, stop or reboot a server

    Select the server in the Workspace
    Stop the server and deallocate resources:
      From the context menu of the server element, select: Power > Stop
      (Optional) In the dialog that appears, connect using Remote Console and shut down the VM at the operating system level to prevent data loss.
      In the dialog box that appears, confirm your action by selecting the appropriate check box and clicking Apply STOP.
      Provision your changes
      Confirm the action by entering your password.
      The server is switched off. CPU, RAM, and IP addresses are released and billing is suspended. Connected storage devices will still be billed. Reserved IP addresses are not removed from the server. The deallocated virtual machine is marked by a red cross in DCD.
    Start the server:
      From the context menu of the server element, select Power > Start
      In the dialog box that appears, confirm your action by selecting the appropriate check box and clicking Apply START.
      Provision your changes
      Confirm the action by entering your password.
      The server is booted. A new public IP address is assigned depending on the configuration. Billing is resumed.
    Restart the server:
      From the context menu of the server element, select Power > Reset
      (Optional) In the dialog that appears, connect using the Remote Console and shut down the VM at the operating system level to prevent data loss.
      In the dialog box that appears, confirm your action by selecting the appropriate check box and clicking Apply RESET.
      Provision your changes
      Confirm the action by entering your password.
      The server will shut down and reboot.

Delete a server

When you no longer need a particular server in your cloud infrastructure, you can remove it with a click of a mouse or keyboard, with or without the associated storage devices. To ensure that no processes are interrupted and no data is lost, you should turn off the server before you delete it.

Prerequisites

    You are logged in (?)
    You are the contract owner or an administrator (?)
      or -
    You have permissions to edit the required data center (?)
    The server is shut down (?)
    The VDC is open (?)

How to delete a server

    Select the server in the Workspace
    Delete the server:
      Open the context menu of the element and select Delete.
        or -
      Select the element and press the Del key.
    In the dialog that appears, choose whether you also want to delete storage devices that belong to the server.
    Provision your changes
    The server and its storage devices are deleted.
When you delete a server and its storage devices, or the entire data center, their backups are not deleted automatically. Only when you delete a Backup Unit will the backups it contains actually be deleted.
When you no longer need the backups of deleted VMs, you should delete them manually in the Backup Unit Manager to avoid unnecessary costs.
Learn how to:
Last modified 1mo ago