Important information: Change to the Maincubes data center
Tuesday, December 1, 2020
The move to the Maincubes data center has been planned for a few months and we are now slowly in the "final phase". This data center offers extensive infrastructure improvements for our IT services. By switching, you not only benefit from improved and optimal network performance, but also the best possible network security. In order to keep the announcement with the information about the switch as short as possible, we have also created a precise FAQ that should answer all your questions (see below). We ask that you give yourself enough time to answer the questions and read this through.
What advantages will I get from switching?
- Improved network infrastructure
- Improved network protection (including 750Gbit/s Arbor DDoS permanent protection)
- 100% power availability through 6-fold redundancy
- TÜV level 2 & 3, as well as ISO 27001: 2013 certification
- Improved latency (ping) due to the closer connection to the DE-CIX node
This means that we can currently offer you the best possible infrastructure. We are not aware of any other way of being able to offer an even better infrastructure.
When will the switch be made?
The change will take place on December 16, 2020 from 11 p.m. and ends according to plan at around 2 a.m. (morning). This is the time of day when the traffic is at its lowest, so that few or almost no one should notice the change.
Will anything change on my server?
No, everything on your server will remain the same after the change (apart from the advantages mentioned) (also IP address, server package, etc.).
Will the change increase my tariff?
No, although you as a customer will benefit from many new advantages by switching, it will not increase your tariff.
Will my server be offline during the transition?
Not quite, we already have a solution for customers who need an active server at this time of day. If you need a server for your services exactly at the specified time of the change, we offer you a so-called "change server". This server runs during the time when the change takes place and is then removed again as soon as the change has been successfully carried out.
If it is imperative that the server should still be available online at the above time, please contact us as soon as possible via a ticket so that we can provide you with the "switch server" in good time.
I am not at the PC in the morning and can therefore not start my applications on the server after switching, what can I do about it?
If you cannot start your applications on the server via PC / laptop after the change has been carried out successfully, there is a wonderful possibility to easily establish an SSH connection via the smartphone (Android / iOS). All you need is the "Termius" program. This SSH program not only offers a secure (S)SH connection via smartphone, but is also free of charge and also very easy to use. You can easily and conveniently select your mobile OS (Android or iOS) via the website https://termius.com/ and you will then be redirected to the appropriate store (App Store, Google Play Store).
This is not the only solution if your applications can only be started by a command (e.g. a start script) and you want to have your applications online again immediately after the server has started, there is still the option described below.
Note: LAMP applications (e.g. Apache2, PHP7, MySQL, etc.) start automatically after restarting the server!
I have applications / scripts that need to be started manually and I want this to be done immediately after the server starts.
In this case we also already have an ideal solution for you. By using "certbots" you can have applications start automatically after the server has started so that they are online again immediately after the server has started.
All you have to do is enter the following commands:
export VISUAL = nano; crontab -e
@reboot /<your-directory>/<your-start.Script>.sh
Example:
export VISUAL = nano; crontab -e
@reboot /home/server/start.sh
Examples of popular uses:
TeamSpeak:
@reboot sleep 45 && cd / home / <TEAMSPEAK-FOLDER> / && sudo -u <TEAMSPEAK-USER> bash ts3server_startscript.sh start
Games, Bots, etc.:
@reboot sleep 60 && cd / <GAME-DIRECTORY> / && bash start.sh
You can add a new command for the "@reboot" in the crontab per line. You can also test crontabs in action by restarting the server once with the "reboot" command and checking whether your configuration worked.
I have another question.
If you have any other question that is not listed, you can contact us at any time via ticket at https://www.kernelhost.de/cp/submitticket.php?step=2&deptid=3!
