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

Preamble

• By default, the Cloud VPS is provided 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.
• Warning: 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 the 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

Extend 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 offer change of your VPS.

First scenario

In the case where the entire volume is used without partitioning, it is not necessary to do 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, then you must unmount the partition.

sudo umount /dev/vdb1

You then 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, 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 are a few minutes of downtime to expect).

This guide details the creation of a GIT repository on your Web Hosting as well as on your Infomaniak Cloud Server.

Preamble

• GIT and GITHub are available by default on the two aforementioned supports.
• For additional help contact a partner or launch a free call for tenders — also discover the role of the host.

Creation of the GIT repository

Setup on the server:

• the GIT repository is on /git_depot
• the site is located in the folder /web/[project] (on your FTP server)

Commands to enter:

cd
mkdir git_depot
cd git_depot/
git init --bare [projet].git
cd [projet].git
git update-server-info

Sending the local repository to the server

To do on the local machine:

git init
git remote add origin ssh://user@[xxxxx].ftp.infomaniak.com:/home/clients/[123456789]/git_depot/[projet].git
git status
git add .
git commit -a -m "init"
git push --set-upstream origin master
git push

Cloning the site on the server directory

To do on the server:

cd
cd web
rm -r [projet]/
git clone /home/clients/[123465789]/git_depot/[projet].git [projet]/

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

Preamble

• Even if Debian or a package appears outdated, the displayed versions do not have vulnerabilities:
  • Infomaniak keeps them up to date through regular internal patches on all components and systems used.
  • The versions are chosen for their stability, then enhanced by security measures that classic tests do not detect.
• If you or your clients identify a vulnerability in an Infomaniak product, please submit a proof of concept. Although rare, these cases are handled quickly.
  • Data security is the user's responsibility: Infomaniak cannot be held accountable for poor management or use of access credentials.

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 display and interpret monitoring data (network statistics, CPU, RAM, etc.) of a Cloud Server.

Monitor 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 product concerned.
3. Click on Monitoring in the left sidebar

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

• incoming and outgoing traffic (network)
• the average system load (load average)
• the average CPU load
• the amount of RAM used
• disk space used
• the number of hits / sec.
• the average number of MySQL queries made

Interpreting the statistics

By interpreting the monitoring of the resources of a Cloud Server, 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 use of the virtual processors. In this example, the server therefore uses 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 used. In this example, the configuration of this server is therefore oversized compared to actual needs.

High cached memory

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

1. Caching for improved 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 efficiently using the available memory. Unused memory is wasted memory. Therefore, as long as the memory is being 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 the running applications. If an application needs 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 perspective, 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 without obvious memory-related issues. Caching is an essential tool for optimizing performance and making the most of available resources.

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

Display the bootloader of a Cloud VPS / Lite VPS

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

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 concerned.
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 then appears and you can leave it displayed by pressing a key on your keyboard:
   

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

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 Cloud Server:

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 concerned.
3. Click on the action menu ⋮ located to the right of the Web hosting concerned, in the Web Hostings section.
4. Click on Modify the disk space of the hosting:
   
5. Adjust the size according to the allocated and still available disk space.
6. Click on the Confirm button to validate the modification.

This guide explains how to access the configuration of an 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 Web site 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 product concerned.
3. Click on the Manage button under Advanced Settings:
   
4. Take note of the Web site 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 MySQL version of the Web hosting:
   

This guide explains how to mount the volume dedicated to storing your data on your Cloud VPS on Windows. In the case of a VPS Lite, the procedure is not necessary as there is only one disk, even on Windows.

Mount the storage volume

To mount the storage volume on Windows, you need to go to the "Disk Management" tool and bring the disk online:

• Right-click on the Start menu.
• Search for Disk Management.
• In the left sidebar, identify the offline disk (usually an icon with a white arrow on a red background and a blue icon).
• Right-click on it to select Online.

To initialize the disk and create a volume:

• Once the disk is online, right-click on it and select Initialize Disk.
• Choose between MBR (for disks < 2 TB) and GPT (recommended for disks > 2 TB), then click OK.
• Then, right-click on the unallocated space of the disk and select New Simple Volume.
• Follow the wizard's steps to assign a drive letter, format the volume in NTFS, then finalize by clicking Finish.

The disk will now be accessible from Windows File Explorer.

You can also use diskpart, the Windows disk and partition management utility.

This guide presents the use of MySQL on Infomaniak hosting, particularly the operation of stored procedures.

Preamble

• “Stored procedures” and “stored routines” are not available on a shared web hosting.

Understanding stored procedures and routines

If stored procedures are essential to your project and you are currently using shared hosting, it is advisable to consider a VPS or a dedicated server, which offer more control and resources.

Stored procedures are an effective way to automate tasks and integrate business logic directly into the database. This results in more performant and easier-to-maintain applications.

On a Cloud Server, 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, used to launch stored procedures already present in the database.

The user also has the required privileges to create new stored procedures. Creating a stored procedure is done via specific SQL syntax defining the instructions to execute, followed by its recording in the database.

Example

DELIMITER //
CREATE PROCEDURE GetUserCount()
BEGIN
    SELECT COUNT(*) AS total_users FROM users;
    -- Returns the total number of users in the table
END //
DELIMITER ;

-- Execute the stored procedure
CALL GetUserCount();

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

Preamble

• This feature is only available for:
  • Cloud Servers
  • Cloud VPS / VPS Lite
  • Jelastic Cloud
• Without any indication from you, scheduled maintenance is generally performed by Infomaniak between 10 PM and 6 AM.

Modify the scheduled maintenance period

To do this:

1. Click here to access the service for which you want to schedule maintenance on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product concerned.
3. Click on Scheduled Maintenance in the left sidebar or on the central page depending on the service concerned:
   
4. Click the buttons to define, in blue, a preferred intervention slot.
5. Validate by clicking the button at the bottom:
   

This guide helps resolve any issues with activating your Windows Server license.

Preamble

• Also check for any current issues on https://infomaniakstatus.com/.
• For **Public Cloud** specifically, the list of scheduled maintenances and current issues can be found at https://status.infomaniak.cloud/.

Change the registered key

Open the Run utility (key Windows logo + R).

Remove the registered key

Run the following command:

cscript.exe c:\windows\system32\slmgr.vbs -upk

Add a new key

Relaunch the Run utility and then execute the following command:

cscript.exe c:\windows\system32\slmgr.vbs -ipk {CLE}

by replacing {CLE} with the key from your configuration below:

Activate Windows

Restart the Run utility and then run the following command to associate the key with the Infomaniak activation bot:

cscript.exe c:\windows\system32\slmgr.vbs -skms kms.infomaniak.cloud

Restart the Run utility and then run the following command to activate your Windows system:

cscript.exe c:\windows\system32\slmgr.vbs -ato

The CGID module for Apache has been disabled on Infomaniak's shared web hosting offers.

If necessary, you should consider changing your plan to a Cloud Server if you are currently on a shared web hosting plan. This can be done transparently: refer to this other guide on the subject.

This guide explains how to reboot a VPS Cloud / VPS Lite and what you can do if you no longer have access to the server.

Reboot of VPS Cloud / VPS Lite

The classic mode allows you to normally reboot your server. To access the VPS Cloud / VPS Lite:

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.
4. Click on Restart (classic mode):
   
    

Enable/disable safe mode

If you have lost your SSH key, or made a configuration error, etc.

You have the option to reboot in rescue mode. This involves rebooting from a base image from which you can mount the partitions of your cloud. This way, you will be able to modify/repair your configuration.

To activate the rescue mode:

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.
4. Click on Reboot (safe mode):
   
   
    

Perform operations

Once safe mode is active, access your Cloud via SSH, either with your ssh key or with the temporary password available in the interface.

Once connected, do:

sudo -i

then list the available partitions (replace ov-abcd by your hostname):

[root@ov-abcd ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 8G 0 disk
└─vda1 253:1 0 8G 0 part /
vdb 253:16 0 20G 0 disk
└─vdb1 253:17 0 20G 0 part

vdb corresponds to your cloud disk.

To access it in write mode, you must mount it:

[root@ov-abcd ~]# mount /dev/vdb1 /mnt/

You can then edit the files:

[root@ov-abcd ~]# ls /mnt/
bin boot dev etc home initrd.img initrd.img.old lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var vmlinuz vmlinuz.old

Depending on your cloud's operating system, you can also perform a chroot to replicate your usual environment:

[root@ov-abcd ~]# chroot /mnt/
bash: ls: command not found
root@ov-abcd:/# export PATH="$PATH:/usr/sbin:/sbin:/bin"
root@ov-abcd:/# ls
bin boot dev etc home initrd.img initrd.img.old lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var vmlinuz vmlinuz.old

Once the necessary modifications have been made, disable safe mode to restart your cloud on the original disk.

This guide explains how to replace, within an Infomaniak Web hosting, the address of a site currently a subdomain (https://dev.domain.xyz for example) with the main domain (https://domain.xyz).

Preamble

• The operations in brief:
  1. We start with a site created and accessible via the URL of the main domain dev.domain.xyz.
  2. We add an alias domain.xyz.
  3. We swap the two types (the main domain becomes an alias and the alias becomes the main domain).
  4. We remove the old name dev.domain.xyz.
• Note that the site remains in the original folder on the server; the name of this location may be in the form /sites/dev.domain.xyz but this has absolutely no impact on the live site.
• Also, familiarize yourself with the last chapter of this other guide.

The operations in detail

To switch from a site with a subdomain address "dev.domain.xyz" to a direct address "domain.xyz":

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 chevron ‍ to expand the Domains section of this site:
4. Click on the button Add a domain:
   
5. Add the desired new name, check the corresponding boxes.
6. Click on the button to Confirm:
   
7. Once the addition is complete, click on the action menu ⋮ located to the right of the relevant item.
8. Choose to set the item as the primary domain:
   
9. Confirm the operation to proceed with the domain swap.

This guide explains how to install and configure systemd on a Serveur Cloud and presents the main commands that can be used.

Prerequisites

• Follow the installation guide for systemd on Serveur Cloud.
• Consult the official documentation to learn about all the possibilities offered by systemd
• The "unit" files must be placed in: ~/.config/systemd/user/ (/home/clients/absolute-path-id/.config/systemd/user) (replacing absolute-path-id visible in your Manager) and the permissions must be set to 0644.
• The --user parameter must be specified in each command.

Main commands

Here is a non-exhaustive list of commands that can be used with systemd.

Force systemd to reload the unit files and take the changes into account:

systemctl --user daemon-reload

Activating a service:

systemctl --user enable --now SERVICENAME.service

Checking the status of a service:

systemctl --user status SERVICENAME.service

Configuration of Node as a service with systemd

It will be necessary to create a "Unit" file with the ".service" extension, which will need to be saved in the directory:

~/.config/systemd/user/

It is possible to reuse the example below by replacing the values starting with {}:

[Unit]
Description={Le nom du service} # Spécifier ici un nom du service. Celui-ci est obligatoire mais n'a pas d'impact sur le fonctionnement

[Service]
Restart=always
Environment=NODE_VERSION={la version souhaitée} # Spécifier ici la version de Node à utiliser. S'assurer qu'elle soit installée au préalable avec "nvm install {la version souhaitée}"
WorkingDirectory=%h/{repertoire du projet Node} # %h correspond à la racine de l'hébergement
ExecStart=/bin/bash -c "exec $HOME/.nvm/nvm-exec {commande de lancement du script node}" # Cette commande dépend du projet. Par exemple, "npm run start", "npm run serve" ou encore "node server.js" sont courants

[Install]
WantedBy=default.target

Additional actions with a Unit file

systemctl --user daemon-reload

Start the service (if it is already active, nothing happens):

systemctl --user start [Nom du Unit]

Stop the service (if it is not active, nothing happens):

systemctl --user stop [Nom du Unit]

Restart the service (if it is not running, it will be started):

systemctl --user restart [Nom du Unit]

Get information about the service; namely:

• "Active" which indicates whether the service is running and for how long
• "CGroup" shows the process group managed by the service, this allows you to see the active processes, with their arguments and their ID

Below "CGroup" are any logs (the standard output and error of the process):

systemctl --user status [Nom du Unit]

Enable automatic startup of the service at server boot; NB: this does not start the service:

systemctl --user enable [Nom du Unit]

Disable the automatic startup of the service at server boot; NB: this does not stop the service:

systemctl --user disable [Nom du Unit]

Configuration with user entries:

[Unit]
Description="nom service"

[Service]
Restart=always
Environment=NODE_VERSION=16.17
WorkingDirectory=%h/sites/"nom-repertoire-site"/
ExecStart=/bin/bash -c "exec $HOME/.nvm/nvm-exec npm run start"

[Install]
WantedBy=default.target

This guide provides instructions to synchronize kDrive with a VPS (or vice versa) using the WebDAV protocol found in the rClone application.

⚠ Available with:

Prerequisites

• Have a VPS.
• Know your kDrive identifier (kDrive ID).

Synchronize kDrive and VPS via rClone

This operation allows you to retrieve in real-time the files and folders from kDrive and to read, create, or modify these files from your VPS while ensuring they are synchronized back to the kDrive server. An rClone mount point can be created with a folder on your VPS to manipulate these kDrive files.

Refer to the rClone documentation if you are looking for information about the available options:

1. Example of rClone command:

   • rclone mount kdrive:/My_kDrive_Folder_Path /home/ubuntu/Target_Folder_Path --vfs-cache-mode full --vfs-cache-max-age 24h --vfs-cache-max-size 10G --cache-dir /home/ubuntu/rclone/cache --daemon --allow-other --dir-cache-time 1h --log-file /home/ubuntu/rclone/rclone.log --log-level INFO

   • The --daemon attribute of this command allows you to run the synchronization as a background task because without it, this sync stops with each VPS disconnection…
2. Example of rClone configuration file:

   • [kdrive]
     type = webdav
     url = https://***.connect.kdrive.infomaniak.com/***
     vendor = other
     user = ***
     pass = ***

   • Server address: https://IDkDrive.connect.kdrive.infomaniak.com (refer to the prerequisites above)
   • Username: email address to log in to your Infomaniak user account
   • Password: application password if two-factor authentication is enabled or the one from your Infomaniak user account if you have not enabled 2FA

This guide explains how to enable PHP-FPM status to, for example, debug a slow site at the PHP level.

Preamble

• PHP-FPM status allows you to monitor in real-time the scripts that are executed as well as their execution time.
• This operation is only possible on Serveur Cloud.

Enable PHP-FPM status

To activate PHP-FPM on a site, contact Infomaniak support from an email address listed on your user account to authenticate your request.

In your request, please specify the source IP address that should be authorized.

Once PHP-FPM status is activated, the following URL links will display the necessary information:

• https://domain.xyz/fpm-status?json&full
• https://domain.xyz/fpm-status?html&full
• https://domain.xyz/fpm-status?xml&full

Warning: if your site contains rewrite rules including the path /fpm-status, you will likely need to make an exception for it.

This guide concerns the redirection of web traffic to a specific port, including when using a dedicated IP and a specific web application (such as Node or Varnish for example).

Prerequisites

• Add a site to your hosting.
• Install HAProxy on the Cloud Server.

Redirect web traffic to a specific port

By default, on Serveur Cloud, web traffic is sent to Apache. To send requests to a Node script or another service (provided it "listens" on a port between 4000 and 4009), you need to go through HAProxy.

This applies notably to servers Express, Socket.IO, Meteor.js, Nuxt.js, Django, Flask, Ruby on Rails, even possibly Java (J2E), etc.

For this, you must ensure that the service is listening on a port between 4000 and 4009 (especially with server.listen(4000) for Express or a basic HTTP Node server, but depending on the type of project by other means, a configuration file, in the code or otherwise) and on all interfaces (0.0.0.0).

It will also be necessary to configure HAProxy as in the example below:

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 Fast installer in the left sidebar.
4. Click on the action menu ⋮ located to the right of HAProxy.
5. Click on Configure:
   
6. Choose the desired information and save:
   
    

Retrieving the source IP of a request

When you redirect web traffic to your web application, the way requests are processed changes, and the request is first received by a reverse proxy (local to the server) which then forwards the request to the chosen port. Thus, due to the request forwarding, the methods usually used to retrieve the visitor's IP will return the IP of the reverse proxy instead of the visitor's.

In these cases, to retrieve the real source IP of the visitor, you need to consult an HTTP header named X-Forwarded-For, which will contain the source IPs accumulated during each redirection. This header will therefore contain last the original IP address of the client, allowing the real visitor to be identified.

Warning: It is important to note that HTTP headers can be manipulated, which presents security risks. To minimize these risks, it is recommended to verify that the request comes from a reliable server before trusting the content of the X-Forwarded-For header. This verification may involve ensuring that the request was transmitted by a trusted intermediary server, identified by a pre-established list of IP addresses. In the case where the site uses a dedicated IP, the trusted servers are:

• 83.166.133.15
• 83.166.133.17
• 83.166.133.16
• 84.16.92.5
• 84.16.92.43
• 10.2.32.255
• 10.2.34.164

This guide explains how to reset a VPS Cloud / VPS Lite.

Preamble

• This procedure erases all the content of the volume dedicated to the operating system (/dev/vda).
• In the case of a VPS Cloud, the volume dedicated to data storage (/dev/vdb) is not affected by the reset.
   

Reset of the VPS Cloud / VPS Lite OS

To access the VPS:

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 concerned.
3. Click the Reset button.
4. Follow the displayed instructions to complete the reset.

This guide explains how to restore a snapshot of VPS Cloud Infomaniak.

Restore a snapshot

To do 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 concerned.
3. Click on Snapshot in the left sidebar menu.
4. Click on the action menu ⋮ to the right of the object concerned in the table that appears.
5. Click on Restore:
   
6. Click the blue button to start the snapshot restoration.
7. An email is sent when the snapshot is restored.

Restore the operating system disk

Restoring the system volume as in the example above is an irreversible operation. The operating system disk will be replaced by the snapshot and the server will be in the exact state of the backup date.

The data stored on the data volume (vdb) is not affected by this operation.

Restore the data disk (vdb)

Two data restoration modes are possible:

1. “Read-only” mode

If the size of the snapshot differs from the size of the volume, only this read-only mode is available.

This option allows you to mount the snapshot data image, which allows read-only access to the backup data.

For information, here are useful commands to exploit your backup:

• To access the main data volume: mount /dev/vdb /mnt/.
• To mount the data volume in a specific folder "backup": mount -o nouuid -o ro,norecovery /dev/vdc /backup.

To know which letter to use (/dev/vd?), use the command lsblk:

2. “Restore” mode

Restoring the data volume is an irreversible operation. The data disk (vdb) will be replaced by the snapshot. At the end of the restoration, it will be necessary to remount the data volume so that your operating system refreshes the content.

The following procedure and commands are provided for informational purposes only:

1. Make sure your data volume is not mounted:
   * umount /mnt (/mnt or the location you chose to access your data).
2. Remount the data volume:
   * mount /dev/(vdb) /mnt

To know the name of the data volume attached to your server, use the command lsblk (see above).