Dedicated Core Servers
August 18
This is solely for informational purpose and does not require any action from you. IONOS has renamed Virtual Server(s) to Dedicated Core Server(s). This change does not impact the functionality of the product in any manner. As a result, the documentation portal now reflects the product name changes. For more information, see Product Renaming FAQs.
Dedicated Core Servers that you create in the DCD are provisioned and hosted in one of IONOS physical data centers. Dedicated Core Servers behave exactly like physical servers. They can be configured and managed with your choice of the operating system. For more information about creating a Dedicated Core Server, see Create a Server.
Boot options: For each server, you can select to boot from a virtual CD-ROM/DVD drive or from a storage device (HDD or SSD) using any operating system on the platform. The only requirement is the use of KVM VirtIO drivers. IONOS provides a number of ready-to-boot images with current versions of Linux operating systems.
Availability Zones
Secure your data, enhance reliability, and set up high-availability scenarios by deploying your Dedicated Core 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)
Live Vertical Scaling (LVS)
If the capacity of your Virtual Data Center no longer matches your requirements, you can still increase or decrease your resources after provisioning. Upscaling resources allows you to change the resources of a Dedicated Core Server without restarting it, permitting you to add RAM or NICs ("hot plug") to it while it is running. This change allows you to react to peak loads quickly without compromising performance.
After uploading, you can define the properties for your own images before applying them to new storage volumes. The settings must be supported by the image, otherwise, they will not work as expected. After provisioning, you can change the settings directly on the storage device, which will require a restart of the server.
The types of resources that you can scale without rebooting will depend on the operating system of your VMs. Since kernel 2.6.25, Linux has LVO modules installed by default, but you may have to activate them manually depending on the derivative. For more information, see Linux VirtIO page.
For IONOS images, the supported properties are already preset. Without restarting the Dedicated Core Server, its resources can be scaled as follows:
Upscaling: CPU, RAM, NICs, storage volumes
Downscaling: NICs, storage volumes
Scaling up is the increase or speed up of a component to handle a larger load. The goal is to increase the number of resources that support an application to achieve or maintain accurate performance. Scaling down means reducing system resources, irrespective of whether you have used the scaling up approach. Without restarting the Dedicated Core Server, only upscaling is possible.
Limitations
CPU Types: Dedicated Core Server configurations are subject to the following limitations, by CPU type:
AMD CPU
Intel® CPU
A single Intel® physical core with Hyper-Threading Technology is exposed to the operating system of your Dedicated Core Server as two distinct “logical cores”, which process separate threads.
RAM Sizes: 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.
Live Vertical Scaling: Linux supports the entire scope of IONOS Live Vertical Scaling, whereas Windows is limited to CPU scaling. Furthermore, it is not possible to use LVS to reduce storage size after provisioning.
Last updated