Supervisor is not offered directly because systemd is recommended, better integrated with Debian and available in Fast installer.

If you were to install it anyway, contact Infomaniak support in writing.

This guide explains how to back up a VPS Cloud in the form of a snapshot.

Introduction

• A snapshot is like a photo of your VPS Cloud at a given moment in time, containing everything on your server, including your operating system, applications, data, etc.
• Snapshots can be used notably for…
  • … protect your VPS Cloud in case of an issue: if you encounter a problem with your VPS Cloud, you can restore a snapshot to revert to a previous state.
  • … test changes without risk: before making significant changes to your VPS Cloud, you can create a snapshot to be able to go back if necessary.
• You benefit from a free snapshot to back up your entire server in a dedicated space. If needed, you can order additional space or delete a snapshot to create a new one.
• Two types of backup are possible:
  1. Data snapshot: allows you to create an image of the volume containing your data (not available for Windows distributions).
  2. **Operating system** snapshot: allows you to create an image of the volume containing your operating system. This type of backup involves a brief interruption of your applications and websites.
• It is recommended to create snapshots regularly, for example once a week or once a month; this will allow you to have a history of your VPS Cloud and to be able to go back in case of a problem.
• It is obviously possible to restore the state of the VPS Cloud thanks to the previously created snapshot.

Create a snapshot

For this:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Snapshot in the left sidebar.
4. Click on the blue button Create a snapshot:
   
5. Choose the type of snapshot to create (data or operating system).
6. Click on the blue button to start creating the snapshot:
   
7. An email is sent when the snapshot is generated.

Delete a snapshot

For this:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Snapshot in the left sidebar.
4. Click on the action menu ⋮ to the right of the relevant item in the displayed table.
5. Click on Delete:
   

Order additional snapshots

For this:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Snapshot in the left sidebar.
4. Click on the shopping cart icon:
   
5. Follow the instructions to complete the order.

It is not possible to order an additional snapshot if a snapshot is in progress.

This guide explains how to increase the storage volume of your VPS Cloud once the offer change has been made.

Preamble

• By default, the VPS Cloud comes with two volumes:
  • 1 volume for the operating system of your choice (/dev/vda).
  • 1 volume for storing your data (/dev/vdb), this is the one that will be increased.
• Note: depending on the installed operating system, the system volume may be named /dev/sda, /dev/sda1 or /dev/vda; the same applies to the data volume /dev/sdb, /dev/sdb2 or /dev/vdb … It is therefore necessary to replace these indications with those corresponding to your situation.

SSH commands to increase storage volume

If you choose **XFS**, for example, it is necessary to install the appropriate tools (if they are not already present):

sudo apt install xfsprogs

Then increase the volume with the following SSH commands:

sudo xfs_grow /dev/vdb

And if you choose EXT4:

sudo resize2fs /dev/vdb

Expanding the volume after increasing the storage volume

Two scenarios may arise once you have extended the storage volume of your Linux server. Note that no data is deleted when increasing the space via the VPS plan change.

First scenario

In the case where the entire volume is used without partitioning, it is not necessary to perform a resizepart, since there is no partition.

sudo umount /dev/vdb
sudo fsck.ext4 -f /dev/vdb
sudo resize2fs /dev/vdb

Second scenario

In the case of a volume that contains a partition (/dev/vdb1), you must first stop the processes that use this volume and then unmount the partition.

sudo umount /dev/vdb1

Next, you need to increase the partition size with parted, which has the resizepart command, unlike fdisk.

sudo parted /dev/vdb
GNU Parted 3.2
Using /dev/vdb
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) resizepart 1 100%
(parted) quit
sudo fsck.ext4 -f /dev/vdb1
sudo resize2fs /dev/vdb1

And the System volume?

It is not possible to increase the size of the system volume.

For Linux, Infomaniak provides 20 GB, sufficient for any Linux distribution.

For Windows, Infomaniak provides 100 GB on the C drive, which is sufficient for Windows. Applications must be installed on the D drive. If you have 50 GB, you can request 100 GB (contact Infomaniak support specifying a time slot for the operation as there will be a few minutes of interruption to expect).

This guide explains how to access the bootloader of a VPS Cloud / VPS Lite from the Infomaniak Manager.

Display the bootloader of a VPS Cloud / VPS Lite

The following procedure allows you to display the bootloader of GRUB:

1. Click here to access the management of your product on the Manager Infomaniak (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on Open VNC console.
4. Click on Restart the server while keeping the new window with the VNC console displayed.
5. Refresh the VNC console as soon as the server restarts to display the server's bootloader; GRUB will then appear and you can keep it displayed by pressing a key on your keyboard:
   

This guide explains how to display and interpret monitoring data (network, CPU, RAM statistics, etc.) for a Cloud Server.

Monitoring the activity of a Managed Cloud Server

To access monitoring

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on Monitoring in the left sidebar

Various data is available to monitor the activity of your Cloud Servers, including:

• incoming and outgoing traffic (network)
• the system load average
• the average CPU load
• the amount of random access memory (RAM) used
• disk space used
• the number of hits per second.
• the average number of MySQL queries performed

Interpret the statistics

By interpreting the monitoring of a Cloud Server's resources, you can estimate the resources (power) you need to run your websites and web applications.

Total system load

The total system load summarizes, in percentage, the level of utilization of the virtual processors. In this example, the server is therefore using less than 10% of its resources (0.10).

Processor (CPU) and memory (RAM)

These graphs show that less than 10% of the virtual processors are used and that less than 3 GB of RAM are actually utilized. In this example, the configuration of this server is therefore oversized compared to the actual needs.

High cached memory

High cached memory on a server is not abnormal and is often beneficial in many cases. Here's why:

1. Caching for enhanced performance: Modern operating systems, such as Linux, use free memory to cache data from the disk to improve performance. When you access files or applications, the system can quickly retrieve the data from the cache instead of reading it from slower storage devices, such as hard drives. This helps to reduce the overall response time of your server and can significantly improve performance.
2. Efficient memory usage: High memory usage due to caching means that your server is effectively utilizing the available memory. Unused memory is wasted memory. Therefore, as long as the memory is used for useful purposes like caching, it is a positive sign.
3. Automatic memory management: Operating systems are designed to automatically adjust the size of the cache based on the needs of running applications. If an application requires more memory, the cache can reduce its size to accommodate it. This dynamic memory management ensures a balance between caching and serving active applications.
4. Monitoring perspective: From a monitoring standpoint, seeing high memory usage due to caching can initially raise concerns, but it is essential to interpret the metrics in the context of your server's behavior. If you observe good performance and notice no signs of memory-related issues, such as swapping or application crashes, the high cache usage is likely expected and beneficial.

In summary, high cache memory on a server is normal and can contribute to improving the overall system performance. Do not worry if you observe significant cache memory usage, as long as your server is functioning correctly and there are no obvious memory-related issues. Caching is an essential tool for optimizing performance and making the most of available resources.

This guide explains how to find out the version of the operating system of the server for your Web Hosting.

Preamble

• Even if Debian or a package does not appear to be up to date, the displayed data/information (component names and versions) are not subject to vulnerabilities or other security flaws:
  • Infomaniak keeps all these elements up to date and secures the components regularly through active maintenance of all components and operating systems used (internal patches).
  • Infomaniak selects a particular version for stability reasons and then applies patches or various countermeasures that these tests do not account for.
• If you or one of your clients detect a vulnerability in our tools/products, submit a Proof of Concept (POC) to demonstrate/point out the vulnerability; in these rare but not impossible cases (no security is infallible) Infomaniak will intervene as quickly as possible to correct the issue.
  • Note that since data security is the user's responsibility, Infomaniak cannot be held responsible for any issues arising from poor management and/or misuse of the user's login and access data.

What OS is on my site?

To find out the version:

1. Log in to the server via SSH (need help?).

2. Run the following command:

   lsb_release -a

3. You will get information of this type:

   Distributor ID: Debian
   Description: Debian GNU/Linux 7.9 (wheezy)
   Release: 7.9
   Codename: wheezy

This guide explains how to modify the disk space of a hosting on Serveur Cloud.

Preamble

• The databases are installed on the same Cloud server, so the disk space for the databases is not limited to the size of the hosting but to the total disk space of the Cloud server.
  • To modify this total disk space, it is necessary to modify the configuration of the Cloud server.
     

Modify the disk space of a web hosting

To access the hosting on Serveur Cloud:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on the action menu ⋮ located to the right of the relevant web hosting, in the Web Hosting section.
4. Click on Modify the disk space of the hosting:
   
5. Adjust the size according to the allocated and remaining disk space.
6. Click on the button Confirm to validate the change.

This guide explains how to access the configuration of a Infomaniak Web site to display technical information such as the PHP, Apache version or the activated PHP extensions and modules.

View the site's technical information

To access the website management:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on the Manage button under Advanced Settings:
   
4. Review the website information under the General, PHP / Apache and PHP Extensions tabs:
   
5. Click on the back arrow in the left sidebar.
6. Click on Databases in the left sidebar to get the version of MySQL for the web hosting:
   

This guide concerns MySQL on Infomaniak hosting and their compatibility with stored procedures.

Preamble

• “Stored procedures” & “stored routines” are not possible on Web Hosting.

Understanding stored procedures and routines

If stored procedures are essential to your project and you currently have a shared hosting plan, you might consider a VPS or dedicated server, where you will have more control and resources.

Stored procedures offer a powerful and efficient way to automate tasks and manage business logic at the database level, which can result in more performant and easier-to-maintain applications.

On Serveur Cloud, as soon as the user has administrator rights on the relevant MySQL database, they have the necessary permissions to execute SQL instructions, including the EXECUTE command, which is used to run existing stored procedures in the database.

He also has the required privileges to create new stored procedures. Creating a stored procedure typically involves using specific SQL syntax to define the instructions to be executed, followed by saving this definition in the database.

This guide explains how to customize the time slot(s) during which Infomaniak can perform maintenance to enhance your services (new features, fixes, etc.).

Preamble

• This feature is only available for:
  • Cloud Servers
  • VPS Cloud / VPS Lite
  • Jelastic Cloud
• Unless otherwise specified, planned maintenance is generally carried out by Infomaniak between 10 PM and 6 AM.

Change the scheduled maintenance period

To do this:

1. Click here to access the service for which you want to schedule maintenance on the Manager Infomaniak (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Scheduled maintenances in the left sidebar.
4. Click on the blue button to set a preferred intervention slot: