Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Network File Storage is a managed service that uses the Network File System (NFS) protocol to offer shared file storage to numerous Virtual Machines (VMs) within the Virtual Data Center (VDC).
Note: Network File Storage is currently available on a request basis and will be initially available only in German data centers. To access this product, please contact your sales representative or IONOS Cloud Support.
For more information about:
VMs, see Cubes or Compute Engine.
VDCs, see Data Center Designer and Basic Tutorials.
Explore the key use cases for implementing Network File Storage.
Get started with creating and managing Network File Storage clusters and shares via the DCD.
Get started with creating and managing Network File Storage clusters and shares via the API.
To get answers to the most commonly encountered questions about Network File Storage, see FAQs.
Network File Storage uses the NFS protocol to provide shared data storage accessible to your VMs via a private network. It allows fine-grained POSIX permissions at file and directory levels. You can provision a shared Network File Storage using the protocol. It enables easy data sharing between the connected VMs, all while benefiting from the reliability and security of a cloud-based storage solution.
During cluster creation, you must specify an IP address from your LAN for the cluster. The specified IP address is used as a floating IP address for the two VMs that the Network File Storage uses to provide high availability.
As seen in the illustration, you create a cluster within the Network File Storage and create shares within a cluster. Multiple VMs from within a VDC are connected to shares of a Network File Storage's cluster via a private LAN.
Each cluster can contain multiple shares within it. Shares are individual file systems within the storage. For example, you can imagine it as a cluster being a computer and shares are folders within it that are accessed by VMs. An administrator can allow VMs to use specific shares.
VMs on the same private network can connect to the Network File Storage's cluster. In addition, data can be accessed simultaneously from multiple compute instances (for example, VMs, and containers) without compromising data consistency. Multiple VMs from within the VDC can access the data simultaneously.
IONOS manages maintenance operations, such as software updates and hardware replacement, by offering redundant, high-availability cluster services.
You can also integrate it with Kubernetes clusters to provide persistent storage for containerized workloads.
SSD Storage: Supports swift data retrieval and reliable data storage.
Storage Size: The minimum cluster size is 2 TiB and the maximum cluster size is 42 TiB. It is a usable space; hence, you do not have to reserve free space for optimal performance.
NFSv4.2: The latest NFS protocol version, NFSv4.2, allows standard read and write operations directly to storage.
Encryption at rest: Provides encryption at rest, by default.
Root squash security: Network File Storage's built-in security mechanism reduces the risk of unauthorized root-level access from the client machine to the NFS server. Enabling this feature prevents superuser privileges to the root user on a client machine. It also prevents potential attacks on the NFS server when the client machine is compromised.
High Performance & Reliability: NFSv4.2 protocol provides high availability and durability and the following benefits:
Reduced protocol overhead with compound operations and caching.
Efficient file operations with minimal server interaction.
Live data movement without interruption.
Detailed file-level access and performance telemetry.
Seamless Management: Benefit from proactive IT infrastructure management and maintenance with IONOS’s managed Network File Storage.
Efficient Data Sharing: Easily distribute and manage data across multiple VMs within a VDC, with centralized data organization and fine-grained POSIX access control.
The billing for Network File Storage is based on the cluster size. The data transfer between the Network File Storage and VMs is not tracked and free.
The initial cluster size must be between 2 TiB and 42 TiB, increasing in 1 TiB increments. All cluster space is fully usable. After creation, the cluster size can only be increased, not decreased.
Prices are listed in the respective price lists:
IONOS Ltd. – United Kingdom.
IONOS Inc. – United States and Canada.
The following use cases have been derived to meet your business needs based on the features and benefits of Network File Storage:
Network File Storage for user home directories: Host user home directories in a networked environment where user data, including home directories, are stored and managed centrally.
Shared storage for databases and application servers: With Network File Storage—central storage for your databases and application servers—you can enable seamless and secure access to the shared database and application server. It also optimizes storage costs through efficient usage and scaling mechanisms.
Store web content and serve it to multiple web servers: It provides centralized cloud-based storage for web content accessible by multiple servers, thus simplifying content management and ensuring content uniformity.
VMs are mounted on the POSIX-compliant exported file system inside a local mount point. It provides a fully managed and scalable storage on file level. The service manages all the file storage infrastructure, meaning you can avoid the complexity of deploying, patching, maintaining and scaling complex file system configurations. The service is highly scalable, highly available, and highly durable.
Currently, the Network File Storage is based on the Solid State Drive (SSD) - Standard performance class. Data is stored on two storage servers, providing active-active redundancy. For additional data protection, every storage server is based either on a hardware or a software RAID system.
Currently, the Network File Storage is based on the SSD Standard performance class, which is recommended for instant data access.
The table below lists the drive types and their specifications:
Usage mode
Shared
Minimum and maximum cluster size
2 TiB – 42 TiB
Maximum bandwidth
300 MB/s per 4 TiB with a 1 MiB block size
Maximum Read IOPS
24.000 IOPS per 4 TiB with a 4 KiB block size
Maximum Write IOPS
18.000 IOPS per 4 TiB with a 4 KiB block size
Encryption at rest involves encrypting data stored on physical media. It protects data from unauthorized access when the data is not actively being used. Network File Storage is based on Block Storage, and it implements encryption at rest.
Secure deletion ensures that once data is deleted, it cannot be restored, even with access to the physical media. Network File Storage is based on Block Storage, and it implements secure deletion.
Network File Storage is currently limited to German data centers.
The cluster size cannot be decreased despite deleting some shares or data within them; the cluster will not shrink.
You can retrieve a list of all Network File Storage clusters in your contract. The number of results displayed on each page depends on the following values:
limit
limits the number of response elements.
offset
specifies the starting point within the collection of resource results returned from the server.
Additionally, you can also use a response filter (filter.datacenterId
) to list only the clusters within the specified data center.
Use the regional endpoints to retrieve all clusters:
Berlin, Germany: https://nfs.de-txl.ionos.com/clusters
Frankfurt, Germany: https://nfs.de-fra.ionos.com/clusters
Paris, France: https://nfs.fr-par.ionos.com/clusters
London, Great Britain: https://nfs.gb-lhr.ionos.com/clusters
Logroño, Spain: https://nfs.es-vit.ionos.com/clusters
Las Vegas, United States: https://nfs.us-las.ionos.com/clusters
Newark, United States: https://nfs.us-ewr.ionos.com/clusters
Lenexa, United States: https://nfs.us-mci.ionos.com/clusters
The region 'Worcester, GB' will follow shortly.
Note: The following request contains sample values. Remember to replace them with the relevant information.
To make authenticated requests to the API, the following fields are mandatory in the request header:
A 200 message confirms that a list of clusters is fetched.
To create a Network File Storage cluster via the API, perform a POST request with the name and description of the cluster.
Important: The user privilege for accessing and managing Network File Storage is not effective yet. Any user with an active token will be granted access to the service management independent of the privilege setting. The group privilege will be added to the application with an upcoming release and the documentation will be updated accordingly.
Use the regional endpoints to create a cluster:
Berlin, Germany: https://nfs.de-txl.ionos.com
Frankfurt, Germany: https://nfs.de-fra.ionos.com
Paris, France: https://nfs.fr-par.ionos.com
London, Great Britain: https://nfs.gb-lhr.ionos.com
Logroño, Spain: https://nfs.es-vit.ionos.com
Las Vegas, United States: https://nfs.us-las.ionos.com
Newark, United States: https://nfs.us-ewr.ionos.com
Lenexa, United States: https://nfs.us-mci.ionos.com
The region 'Worcester, GB' will follow shortly.
Note: The following request contains sample values. Remember to replace them with the relevant information.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Below is the list of mandatory body parameters:
A 201 message confirms that the cluster creation is successful.
After creation, you can view the list of Network File Storage clusters or delete an existing one if it is no longer required.
To view a list of the clusters, follow these steps:
Log in to the DCD with your username and password.
Go to Menu > Storage > Network File Storage.
Result: A list of all clusters are displayed: — NAME: Displays the name of the cluster. Select the name to view its details in the Cluster Details window. — STATE: Displays the state of the respective cluster: — BUSY: When the cluster is in the creation mode or it is being updated. — AVAILABLE: When the cluster is available and healthy. — DESTROYING: When the cluster is being deleted. — FAILED: When the cluster is not accessible due to an error. — SIZE: Displays the size of the respective cluster. — CREATION DATE: Displays the date of creation of the cluster. — OPTIONS: Select to perform the following: — View Cluster: Displays the cluster settings. The Change cluster settings window is displayed. You can change the Cluster Name and its Size. Click Save to save the settings. — Edit Cluster: Modify and manage the cluster settings. — Manage Shares: Manage the shares that are associated with the respective cluster. — x Delete Cluster: Delete the chosen cluster. In the dialog box that appears, select Delete to confirm deletion. For more information, see Delete a Network File Storage Cluster.
Learn how to create Network File Storage clusters.
Learn how to access a list of Network File Storage clusters.
Learn how to manage a Network File Storage cluster.
Learn how to delete a Network File Storage cluster.
Learn how to create shares within a Network File Storage cluster.
Learn how to view and manage shares that are associated with a Network File Storage cluster.
Learn how to delete a share from a Network File Storage cluster.
A cluster represents a directory with individual file systems, called shares, within the Network File Storage cluster.
Important: The user privilege for accessing and managing Network File Storage is not effective yet. Any user with an active token will be granted access to the service management independent of the privilege setting. The group privilege will be added to the application with an upcoming release and the documentation will be updated accordingly.
To create a Network File Storage cluster, follow these steps:
Log in to the DCD with your username and password.
Go to Menu > Storage > Network File Storage.
Select Create Cluster to create a new cluster.
Enter the following details in the Create Cluster window:
Click Save to create the cluster.
Result: Your Network File Storage Cluster is created and is currently in a BUSY state.
To define cluster properties, specify the following:
Cluster Name: Enter an appropriate name for your cluster.
Location: This product is currently available in the German data centers. The value is set to Germany / Berlin, by default. Select a value from the drop-down list to change the data center.
Size: Select the size of the Network File Storage cluster in TiB using the slider. The size determines the billing fees.
File System Version: By default, the cluster supports the latest NFS protocol version NFSv4.2.
You can also follow the steps mentioned in the Finding your Private IP address section on the right side to retrieve an IP address.
Datacenter: Select a data center from the drop-down list to associate it with the cluster. The datacenter indicates the location of the Network File Storage cluster. The available data centers in the drop-down list vary according to the chosen Location. For more information, see Define cluster properties. Currently, the product is available only in the data centers in Germany.
Datacenter LAN: Select a LAN to which the Network File Storage cluster must be connected in the data center.
Private IPv4 IP: Enter a private IP address or the subnet using the available Private IPs.
Note: To find your private IP address/Subnet, refer to the instructions on the DCD as seen in the following image.
To delete a Network File Storage cluster, follow these steps:
Log in to the DCD with your username and password.
Go to Menu > Storage > Network File Storage. You will find a list of all the Network File Storage clusters.
Click in the OPTIONS column and select Delete Cluster.
Alternatively, you can also click on the NAME of the cluster and choose Delete Cluster on the Cluster Details window.
Select Delete in the dialog box to confirm deletion.
Result: The STATUS of the respective Network File Storage cluster is set to DESTROYING before it is completely deleted.
A share represents individual file systems within the Network File Storage cluster. Each cluster can contain multiple shares within it.
Important: The user privilege for accessing and managing Network File Storage is not effective yet. Any user with an active token will be granted access to the service management independent of the privilege setting. The group privilege will be added to the application with an upcoming release and the documentation will be updated accordingly.
To create a share within a Network File Storage cluster, follow these steps:
Log in to the DCD with your username and password.
Go to Menu > Storage > Network File Storage.
Select a cluster from the list of clusters and select Manage Shares from the OPTIONS column.
Select Create Share in the Manage shares window and enter the following details:
Click Save to create a share.
Result: A share is created within the selected Network File Storage Cluster.
To define share properties, specify the following details:
Name: Enter an appropriate name for the share.
(Optional) Quota: Specify the quota in MiB to restrict the amount of data that can be stored within the export file. Set the value to zero, if you want to disable the quota for export.
(Optional) GID: The ID of the group that owns the exported share. The default value is 512.
(Optional) UID: The ID of the user who owns the exported directory. The default value is 512.
Multiple VMs from within a VDC can be connected to shares of a Network File Storage's cluster via a private LAN.
(Optional) Description: Enter necessary information about the client group.
IP Networks: Select + Add IP Network to add an IP address with the mask CIDR notation. The specified network therefore becomes an authorized network while restricting access to all other networks. Example: 127.0.0.1/24.
Note: The IP Networks setting will always supersede the list of hosts. Only use this field if you want the share access on the entire network. In case you need to grant access to specific hosts, leave this field blank.
Hosts: Select + Add Host to add the number of VMs that is allowed to access the share. Example: 10.234.62.123.
NFS Squash Mode: Select a squash mode for export. For more information, see Root squash security. You can choose one of the following:
None: Select if you do not want a squash mode. For security reasons, we do not recommend setting the mode to None.
Root Anonymous: Select to map a root user to an anonymous user.
All Anonymous: Select to map all users to anonymous user.
After creation, you can view the list of Network File Storage clusters, modify the settings, or delete an existing cluster if it is not required.
To manage clusters, follow these steps:
Log in to the DCD with your username and password.
Go to Menu > Storage > Network File Storage.
Select an existing cluster and do the following to modify the cluster settings:
click on the NAME of the cluster and select the Change cluster settings option in the Cluster Details window which will redirect you to the Change cluster settings window.
select Edit Cluster from the OPTIONS column and the Change cluster settings window is displayed.
Make the necessary modifications in the Change cluster settings window. You can only update the Cluster Name and its Size.
Additionally, you can click the Manage Shares tab to update the shares. To delete the respective cluster, click x Delete Cluster. For more information, see Delete a Network File Storage Cluster.
RESULT: A message confirms that the cluster update is successful.
You can retrieve the information about a specific cluster using its clusterId
.
Use the regional endpoints to retrieve a specific cluster:
Berlin, Germany: https://nfs.de-txl.ionos.com/clusters/{clusterId}
Frankfurt, Germany: https://nfs.de-fra.ionos.com/clusters/{clusterId}
Paris, France: https://nfs.fr-par.ionos.com/clusters/{clusterId}
London, Great Britain: https://nfs.gb-lhr.ionos.com/clusters/{clusterId}
Logroño, Spain: https://nfs.es-vit.ionos.com/clusters/{clusterId}
Las Vegas, United States: https://nfs.us-las.ionos.com/clusters/{clusterId}
Newark, United States: https://nfs.us-ewr.ionos.com/clusters/{clusterId}
Lenexa, United States: https://nfs.us-mci.ionos.com/clusters/{clusterId}
The region 'Worcester, GB' will follow shortly.
Note: The following request contains sample values. Remember to replace them with the relevant information.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Below is the list of mandatory path parameter:
A 200 message confirms that the specific cluster information is successfully retrieved.
To delete a share from a Network File Storage cluster, follow these steps:
Log in to the DCD with your username and password.
Go to Menu > Storage > Network File Storage.
Select Manage Shares in the OPTIONS column of the cluster to delete shares. You will find a list of all the shares within the respective Network File Storage cluster.
Select Delete in the dialog box to confirm deletion.
Result: The STATE of the respective share within the Network File Storage cluster is set to DESTROYING before it is completely deleted.
Network File Storage APIs allow contract owners, administrators, and authenticated users with the required permissions to create clusters and shares within the storage system via the API.
Use the regional endpoints to interact with Network File Storage:
Berlin, Germany: https://nfs.de-txl.ionos.com
Frankfurt, Germany: https://nfs.de-fra.ionos.com
Paris, France: https://nfs.fr-par.ionos.com
London, Great Britain: https://nfs.gb-lhr.ionos.com
Logroño, Spain: https://nfs.es-vit.ionos.com
Las Vegas, United States: https://nfs.us-las.ionos.com
Newark, United States: https://nfs.us-ewr.ionos.com
Lenexa, United States: https://nfs.us-mci.ionos.com
The region 'Worcester, GB' will follow shortly.
The API uses the following two authentication methods:
Basic Authentication: Ensure that the string containing your username
and password
is base64-encoded and separated by a colon: username@domain.tld:password
.
Token Authentication: Provide a header value as Bearer
followed by your token
.
Important: From March 15, 2024, the Basic Authentication option will only be accessible if the 2-factor Authentication (2FA) is disabled for your account.
After creation, you can view the list of shares that are associated with a Network File Storage cluster. You can also delete an existing one if it is no longer required.
To view the list of shares, follow these steps:
Log in to the DCD with your username and password.
Go to Menu > Storage > Network File Storage.
Select Manage Shares from the OPTIONS column to view the shares associated with the respective cluster.
Alternatively, you can also click on the cluster's NAME and select the Manage Shares tab in the Manage shares window.
Click in the ACTIONS column and select Delete Share in the Manage Shares window.
Result: A list of all shares associated with the respective cluster are displayed. You can view the following details: — NAME: Displays the name of the share. Select the name to view its details. — QUOTA: Displays the respective share's quota in MiB. — GID: Displays the respective share owner's group ID. — UID: Displays the respective share owner's user ID. — CLIENT GROUPS: Displays the number of client groups that are associated with the respective share. — ACTIONS: Select to perform the following: — View/Edit Share: Select the option to either view or edit its or via the View / Edit Share window. Click Save to save the updates. — Copy ShareId: Select the option to copy the corresponding share ID. — x Delete Share: Select the option to delete the chosen share and select Delete in the dialog box to confirm deletion. For more information, see .
Authorization
yes
string
You can use Basic Authentication
or a Bearer token
. For more information, see Authentication.
Content-Type
yes
string
Set this to application/json
.
clusterId
string
The ID (UUID) of the Cluster.
e69b22a5-8fee-56b1-b6fb-4a07e4205ead
Learn how to create a cluster for Network File Storage.
Learn how to retrieve a specific cluster.
Learn how to retrieve all clusters of a Network File Storage.
Learn how to update a cluster via the API.
Learn how to delete a cluster via the API.
Learn how to create a share within a cluster.
Learn how to retrieve a specific share.
Learn how to retrieve all shares of a cluster.
Learn how to update a specific share via the API.
Learn how to delete a share from within the cluster via the API.
Authorization
yes
string
You can use Basic Authentication
or a Bearer token
. For more information, see Authentication.
Content-Type
yes
string
Set this to application/json
.
Authorization
yes
string
You can use Basic Authentication
or a Bearer token
. For more information, see Authentication.
Content-Type
yes
string
Set this to application/json
.
name
string
The human-readable name of your cluster.
NFS cluster
datacenterId
string
The ID of the data center where the NFS cluster is located in.
e69b22a5-8fee-56b1-b6fb-4a07e4205ead
lan
string
The LAN to which the NFS cluster should be connected.
1
ipAddress
string
The IP address and prefix of the NFS cluster. The IP address can be either IPv4 or IPv6. The IP address must include the CIDR notation.
10.254.64.1/24
Here is a pivotal use case you can implement after configuring the Network File Storage via the DCD or the API:
Network File Storage has its own set of limitations. For more information, see Technical Specifications and Limitations.
Currently, IONOS supports NFSv4.2, which is the latest version of the NFS protocol for Network File Storage. It allows standard Linux users to read and write directly to storage, scaling performance linearly for both IOPS and throughput, maximizing the limits of storage and network infrastructures. Some of its benefits are as follows:
Reduced protocol overhead with compound operations and caching.
Efficient file operations with minimal server interaction.
Enhanced performance with multiple parallel network connections.
Live data movement without interruption.
Detailed file-level access and performance telemetry.
This tutorial will guide you through the process of mounting an Network File System (NFS) volume on Debian-based systems. It is intended for administrators who want to learn how to mount this type of volume. The configuration in the tutorial is specific to self-managed NFS 4.2 servers.
By the end of this tutorial, you will be able to mount an NFS volume on Debian-based Systems.
Ensure that:
you have the appropriate access rights to mount NFS volumes.
you have the following details: IONOS_TOKEN
and NFS_CLUSTER_UUID
. You can retrieve them from the DCD or using the API.
After your cluster has been set up, retrieve the IP address and NFS share path of an NFS cluster from the IONOS API and export it as an environment variable.
1.1. Execute the following command to retrieve the IP address of an NFS cluster:
Note: Remember to replace IONOS_TOKEN
and NFS_CLUSTER_UUID
with your authentication token and the NFS Cluster UUID, respectively.
Command
Description
NFS_CLUSTER_IP
This is the name of the environment variable being set.
-H 'accept: application/json'
This option specifies the Accept header to be used in the request, which is set to application/json to indicate that the client expects the response to be in JSON format.
-H "Authorization: Bearer ${IONOS_TOKEN}"
Specifies the Authorization header to be used in the request, which includes the IONOS API token.
https://nfs.de-txl.ionos.com/clusters/${NFS_CLUSTER_UUID}
The URL of the IONOS API endpoint that provides information about the NFS cluster.
jq .properties.connections[].ipAddress
The command-line JSON processor jq
that is used to parse the JSON response from the IONOS API and extract the IP address of the NFS cluster.
Result: Upon execution, the command makes an HTTP request to the IONOS API, retrieves the IP address of the NFS cluster, and exports it as an environment variable named NFS_CLUSTER_IP
, which can then be used in subsequent commands to mount the NFS cluster.
1.2. Execute the following command to retrieve the NFS share path of an NFS cluster:
Note: Remember to replace IONOS_TOKEN
and NFS_CLUSTER_UUID
with your authentication token and the NFS Cluster UUID, respectively.
Command
Description
NFS_SHARE
The name of the environment variable being set.
https://nfs.de-txl.ionos.com/clusters/${NFS_CLUSTER_UUID}/shares
The URL of the IONOS API endpoint that provides information about the NFS shares of the specified cluster.
Result: Upon execution, the command makes an HTTP request to the IONOS API, retrieves the NFS share path of the first share, and exports it as an environment variable named NFS_SHARE
.
2.1. On the NFS client, open a command window, and install and configure the NFS client nfs-common
, and the necessary packages for an NFS client on a Linux system, specifically on Debian-based distributions, such as Ubuntu:
apt-get update && apt-get -y install nfs-common autofs
Command
Description
apt-get update
The command updates the package list on the system, ensuring that the package manager has the latest information about available packages and their versions.
apt-get -y install nfs-common autofs
The command installs new packages or updates existing ones.
-y
The flag automatically answers "yes" to any prompts that might appear during the installation.
nfs-common
The package provides common files and programs for NFS, including the mount.nfs
command.
autofs
The package provides a tool for automatically mounting and unmounting file systems when they are accessed.
2.2. To determine which file systems are available for mounting from an NFS server, execute the following command:
showmount -e ${NFS_CLUSTER_IP}
Command
Description
showmount
A command-line tool used to query an NFS server for its exported file systems.
-e
This option stands for "exports". It tells showmount
to display the list of exported file systems from the specified server.
${NFS_CLUSTER_IP}
The variable that represents the IP address of the NFS server or the cluster. Remember to replace it with the appropriate IP address.
Result: It displays a list of exported file systems, allowing you to choose which one to mount on your client machine.
2.3. Create directories that can be used as mount points for an NFS on a Linux client machine using the following command:
mkdir -p /mnt/nfs-cluster /data/nfs-cluster
Command
Description
mkdir
A command-line tool used to create new directories.
-p
This option stands for "parents" and indicates mkdir
to create the parent directories if they do not already exist.
/mnt/nfs-cluster
This is the first directory created in the /mnt
directory, which is a common location for mounting file systems.
/data/nfs-cluster
This is the second directory that will be created in the /data
directory.
Result: The command creates the following directories: /mnt
, /mnt/nfs-cluster
, /data
, and /data/nfs-cluster
.
2.4. Mount an NFS on a Linux client machine:
mount -t nfs ${NFS_CLUSTER_IP}:${NFS_SHARE} /mnt/nfs-cluster
Command
Description
mount
A command-line tool used to attach a file system to a directory on a Linux system.
t nfs
This option specifies the type of file system to be mounted, which in this case is an NFS.
${NFS_CLUSTER_IP}
This is the IP address of the NFS server or cluster that is exporting the file system. Remember to replace it with a valid IP address.
${NFS_SHARE}
This is the name of the exported file system or share that you want to mount. Remember to mention the appropriate share.
/mnt/nfs-cluster
This is the mount point on the client machine where the NFS will be attached.
Result: Upon execution, the NFS exported by the server at ${NFS_CLUSTER_IP}
is mounted to the /mnt/nfs-cluster
directory on the client machine.
Alternatively, use autofs
to mount the share(s) on-demand
3.1. The following command is used to add an entry to the /etc/auto.master
file, which is the main configuration file for the autofs
service. The entry / - /etc/auto.nfs
tells autofs
to use the /etc/auto.nfs
file as the configuration file for the mount point:
echo "/- /etc/auto.nfs" >> /etc/auto.master
Result: By adding the / - /etc/auto.nfs
entry to the /etc/auto.master
file, you are telling autofs to use the /etc/auto.nfs
file as the configuration file for the / mount point, which allows autofs to mount the NFS share automatically when the /mnt/nfs-cluster
directory is accessed.
3.2. Execute the following command to create a new file called /etc/auto.nfs
with a single entry that defines an NFS share to be mounted under the /data/nfs-cluster
directory:
echo "/data/nfs-cluster ${NFS_CLUSTER_IP}:${NFS_SHARE}" > /etc/auto.nfs
The entry "/data/nfs-cluster ${NFS_CLUSTER_IP}:${NFS_SHARE}"
defines an NFS share to be mounted under the /data/nfs-cluster
directory. The ${NFS_CLUSTER_IP}:${NFS_SHARE}
specifies the IP address and share name of the NFS server.
Note: Remember to replace the ${NFS_CLUSTER_IP}
and ${NFS_SHARE}
with the actual IP address and share name of the NFS server.
This command is typically used in conjunction with the autofs
service, which is a Linux service that automatically mounts and unmounts file systems based on the contents of the /etc/auto.master
and /etc/auto.nfs
files.
Result: The entry in the /etc/auto.nfs
file indicates the autofs
to mount the NFS share at ${NFS_CLUSTER_IP}:${NFS_SHARE}
under the /data/nfs-cluster
directory. When the /data/nfs-cluster
directory is accessed, autofs
automatically mounts the NFS share.
3.3. Restart the autofs
service on a Linux system using the following command:
service autofs restart
Note: The exact command to restart the autofs
service may vary depending on the Linux distribution being used.
Restarting the autofs
service is typically necessary after making changes to the configuration files, such as adding or removing entries, or updating the IP address or share name of an NFS server. It re-reads the configuration files (/etc/auto.master
and /etc/auto.nfs
) and refreshes the list of automatically mounted file systems to ensure that the changes take effect and that the automatically mounted file systems are updated accordingly.
In this tutorial, you have learned how to successfully mount an NFS volume and share on Debian-based Systems.
You can delete a specific cluster using its clusterId
.
Prerequisite: Only contract administrators, owners, and users with accessAndManageNFS privilege can delete clusters via the API.
Use the regional endpoints to delete a cluster:
Berlin, Germany: https://nfs.de-txl.ionos.com/clusters/{clusterId}
Frankfurt, Germany: https://nfs.de-fra.ionos.com/clusters/{clusterId}
Paris, France: https://nfs.fr-par.ionos.com/clusters/{clusterId}
London, Great Britain: https://nfs.gb-lhr.ionos.com/clusters/{clusterId}
Logroño, Spain: https://nfs.es-vit.ionos.com/clusters/{clusterId}
Las Vegas, United States: https://nfs.us-las.ionos.com/clusters/{clusterId}
Newark, United States: https://nfs.us-ewr.ionos.com/clusters/{clusterId}
Lenexa, United States: https://nfs.us-mci.ionos.com/clusters/{clusterId}
The region 'Worcester, GB' will follow shortly.
Note: The following request contains sample values. Remember to replace them with the relevant information.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Content-Type
yes
string
Set this to application/json
.
Below is the list of mandatory path parameter:
clusterId
string
The ID (UUID) of the Cluster.
e69b22a5-8fee-56b1-b6fb-4a07e4205ead
A 202 message confirms that the specified cluster has been successfully deleted.
You can append a cluster, or update the content of an existing cluster within your Network File Storage using the PUT
API request.
Use the regional endpoints to update a cluster:
Berlin, Germany: https://nfs.de-txl.ionos.com/clusters/{clusterId}
Frankfurt, Germany: https://nfs.de-fra.ionos.com/clusters/{clusterId}
Paris, France: https://nfs.fr-par.ionos.com/clusters/{clusterId}
London, Great Britain: https://nfs.gb-lhr.ionos.com/clusters/{clusterId}
Logroño, Spain: https://nfs.es-vit.ionos.com/clusters/{clusterId}
Las Vegas, United States: https://nfs.us-las.ionos.com/clusters/{clusterId}
Newark, United States: https://nfs.us-ewr.ionos.com/clusters/{clusterId}
Lenexa, United States: https://nfs.us-mci.ionos.com/clusters/{clusterId}
The region 'Worcester, GB' will follow shortly.
Note: The following request contains sample values. Remember to replace them with the relevant information.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Content-Type
yes
string
Set this to application/json
.
A 200 message confirms that the specified cluster is successfully updated.
You can retrieve the list of all shares from within a cluster using its clusterId
. The number of results displayed on each page depends on the following values:
limit
limits the number of response elements.
offset
specifies the starting point within the collection of resource results returned from the server.
Use the regional endpoints to retrieve all shares:
Berlin, Germany: https://nfs.de-txl.ionos.com/clusters/{clusterId}/shares
Frankfurt, Germany: https://nfs.de-fra.ionos.com/clusters/{clusterId}/shares
Paris, France: https://nfs.fr-par.ionos.com/clusters/{clusterId}/shares
London, Great Britain: https://nfs.gb-lhr.ionos.com/clusters/{clusterId}/shares
Logroño, Spain: https://nfs.es-vit.ionos.com/clusters/{clusterId}/shares
Las Vegas, United States: https://nfs.us-las.ionos.com/clusters/{clusterId}/shares
Newark, United States: https://nfs.us-ewr.ionos.com/clusters/{clusterId}/shares
Lenexa, United States: https://nfs.us-mci.ionos.com/clusters/{clusterId}/shares
The region 'Worcester, GB' will follow shortly.
Note: The following request contains sample values. Remember to replace them with the relevant information.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Content-Type
yes
string
Set this to application/json
.
Below is the list of mandatory path parameter:
clusterId
string
The ID (UUID) of the Cluster.
e69b22a5-8fee-56b1-b6fb-4a07e4205ead
A 200 message confirms that all shares from within the specific cluster are successfully retrieved.
You can retrieve the information about a specific share using its clusterId
and shareId
.
Use the regional endpoints to retrieve a specific share:
Berlin, Germany: https://nfs.de-txl.ionos.com/clusters/{clusterId}/shares/{shareId}
Frankfurt, Germany: https://nfs.de-fra.ionos.com/clusters/{clusterId}/shares/{shareId}
Paris, France: https://nfs.fr-par.ionos.com/clusters/{clusterId}/shares/{shareId}
London, Great Britain: https://nfs.gb-lhr.ionos.com/clusters/{clusterId}/shares/{shareId}
Logroño, Spain: https://nfs.es-vit.ionos.com/clusters/{clusterId}/shares/{shareId}
Las Vegas, United States: https://nfs.us-las.ionos.com/clusters/{clusterId}/shares/{shareId}
Newark, United States: https://nfs.us-ewr.ionos.com/clusters/{clusterId}/shares/{shareId}
Lenexa, United States: https://nfs.us-mci.ionos.com/clusters/{clusterId}/shares/{shareId}
The region 'Worcester, GB' will follow shortly.
Note: The following request contains sample values. Remember to replace them with the relevant information.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Content-Type
yes
string
Set this to application/json
.
Below is the list of mandatory path parameters:
clusterId
string
The ID (UUID) of the cluster.
e69b22a5-8fee-56b1-b6fb-4a07e4205ead
shareId
string
The ID (UUID) of the share.
7b1ef56d-dfc6-51fe-aff0-7af2d6747868
A 200 message confirms that the information of the specific share from within the cluster has been successfully retrieved.
You can append or update the content of an existing share within your Network File Storage using the PUT
API request.
Use the regional endpoints to update a share:
Berlin, Germany: https://nfs.de-txl.ionos.com/clusters/{clusterId}/shares/{shareId}
Frankfurt, Germany: https://nfs.de-fra.ionos.com/clusters/{clusterId}/shares/{shareId}
Paris, France: https://nfs.fr-par.ionos.com/clusters/{clusterId}/shares/{shareId}
London, Great Britain: https://nfs.gb-lhr.ionos.com/clusters/{clusterId}/shares/{shareId}
Logroño, Spain: https://nfs.es-vit.ionos.com/clusters/{clusterId}/shares/{shareId}
Las Vegas, United States: https://nfs.us-las.ionos.com/clusters/{clusterId}/shares/{shareId}
Newark, United States: https://nfs.us-ewr.ionos.com/clusters/{clusterId}/shares/{shareId}
Lenexa, United States: https://nfs.us-mci.ionos.com/clusters/{clusterId}/shares/{shareId}
The region 'Worcester, GB' will follow shortly.
Note: The following request contains sample values. Remember to replace them with the relevant information.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Content-Type
yes
string
Set this to application/json
.
A 200 message confirms that the corresponding share within the specified cluster has been successfully updated.
To create a share within the Network File Storage's cluster, via the API, perform a POST request with the clusterId
. The request automatically creates a share within the respective cluster.
Important: The user privilege for accessing and managing Network File Storage is not effective yet. Any user with an active token will be granted access to the service management independent of the privilege setting. The group privilege will be added to the application with an upcoming release and the documentation will be updated accordingly.
Use the regional endpoints to create a share:
Berlin, Germany: https://nfs.de-txl.ionos.com/clusters/{clusterId}/shares
Frankfurt, Germany: https://nfs.de-fra.ionos.com/clusters/{clusterId}/shares
Paris, France: https://nfs.fr-par.ionos.com/clusters/{clusterId}/shares
London, Great Britain: https://nfs.gb-lhr.ionos.com/clusters/{clusterId}/shares
Logroño, Spain: https://nfs.es-vit.ionos.com/clusters/{clusterId}/shares
Las Vegas, United States: https://nfs.us-las.ionos.com/clusters/{clusterId}/shares
Newark, United States: https://nfs.us-ewr.ionos.com/clusters/{clusterId}/shares
Lenexa, United States: https://nfs.us-mci.ionos.com/clusters/{clusterId}/shares
The region 'Worcester, GB' will follow shortly.
Note: The following request contains sample values. Remember to replace them with the relevant information.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Content-Type
yes
string
Set this to application/json
.
Below is the list of mandatory path parameter:
clusterId
string
The ID (UUID) of the Cluster.
e69b22a5-8fee-56b1-b6fb-4a07e4205ead
A 201 message confirms that the share creation is successful. Your values will differ from those in the sample code. It may contain different IDs, timestamps etc.
You can delete a specific share from within a cluster using its clusterId
and shareId
.
Use the regional endpoints to delete a specific share:
Berlin, Germany: https://nfs.de-txl.ionos.com/clusters/{clusterId}/shares/{shareId}
Frankfurt, Germany: https://nfs.de-fra.ionos.com/clusters/{clusterId}/shares/{shareId}
Paris, France: https://nfs.fr-par.ionos.com/clusters/{clusterId}/shares/{shareId}
London, Great Britain: https://nfs.gb-lhr.ionos.com/clusters/{clusterId}/shares/{shareId}
Logroño, Spain: https://nfs.es-vit.ionos.com/clusters/{clusterId}/shares/{shareId}
Las Vegas, United States: https://nfs.us-las.ionos.com/clusters/{clusterId}/shares/{shareId}
Newark, United States: https://nfs.us-ewr.ionos.com/clusters/{clusterId}/shares/{shareId}
Lenexa, United States: https://nfs.us-mci.ionos.com/clusters/{clusterId}/shares/{shareId}
The region 'Worcester, GB' will follow shortly.
Note: The following request contains sample values. Remember to replace them with the relevant information.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Content-Type
yes
string
Set this to application/json
.
Below is the list of mandatory path parameters:
clusterId
string
The ID (UUID) of the cluster.
e69b22a5-8fee-56b1-b6fb-4a07e4205ead
shareId
string
The ID (UUID) of the share.
7b1ef56d-dfc6-51fe-aff0-7af2d6747868
A 202 message confirms that the specified share has been successfully deleted.
You can use Basic Authentication
or a Bearer token
. For more information, see .
You can use Basic Authentication
or a Bearer token
. For more information, see .
You can use Basic Authentication
or a Bearer token
. For more information, see .
You can use Basic Authentication
or a Bearer token
. For more information, see .
You can use Basic Authentication
or a Bearer token
. For more information, see .
You can use Basic Authentication
or a Bearer token
. For more information, see .
You can use Basic Authentication
or a Bearer token
. For more information, see .