Connect file storage to a cloud server in a different pool

If you plan to use file storage for backups, we recommend creating the storage and the cloud server in pools from different availability zones or regions. This will increase system fault tolerance. If the file storage and cloud server are located in different pools, you need to configure private network connectivity at the L3 level via the Global Router.

1. Create a global router.

2. Connect a network and subnet for the cloud server to the global router.

3. Connect the network and subnet for file storage to the global router.

4. Assign an IP address to the cloud server.

5. Specify a route on the cloud server.

6. Specify a route in the file storage subnet.

7. Create file storage.

8. Mount the file storage to the cloud server.

See an example of connecting file storage to a cloud server in another pool.

If you need to increase disk space with file storage, we recommend creating the storage in the same pool as the cloud server. For more details, see the guide Connect file storage to a cloud server in the same pool.

Example of connecting file storage to a cloud server

For example, you need to connect file storage in the ru-2 pool to a cloud server in the ru-8 pool.

1. Create a global router.

2. Connect two private networks to the global router — 192.168.0.0/29 with a gateway of 192.168.0.1 for the ru-8 pool and 172.16.0.0/29 with a gateway of 172.16.0.1 for the ru-2 pool.

3. Assign an address from the 192.168.0.0/29 subnet to the cloud server, for example, 192.168.0.2.

4. Specify a route on the cloud server in the ru-8 pool — to the 172.16.0.0/29 subnet via the gateway 192.168.0.1.

5. Create file storage in the 172.16.0.0/29 subnet.

6. Mount the file storage to the cloud server.

1. Create a global router

1. In the Control panel, in the top menu, click Products and select Global Router.
2. Click Create router. A limit of five global routers is set for each account.
3. Enter the router name.
4. Click Create.
5. If the router was created with the status ERROR or is stuck in one of the statuses, create a ticket.

2. Connect the network and subnet for the cloud server to the router

You need to connect the network and subnet to the global router for the project and pool where the cloud server is created.

You can connect a new or existing network to the router if it is not already connected to any of the account's global routers.

Connect a new network

1. In the Control panel, on the top menu, click Products and select Global Router.

2. Open the router page → Networks tab.

3. Click Create network.

4. Enter a network name. It will only be used in the control panel.

5. Select the Cloud Platform service.

6. Select a location for the network.

7. Select a project.

8. Enter a subnet name. It will only be used in the control panel.

9. Enter the CIDR — IP address and subnet mask. The subnet must meet the following conditions:

   • belong to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
   • have a size of at least /29, as three addresses will be occupied by Servercore network equipment;
   • it does not overlap with other subnets added to this router — there must be no identical IP addresses within the subnets of one router;
   • if a Managed Kubernetes cluster on cloud servers is to be connected to the global router network, the subnet must not overlap with the 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. If a cluster on dedicated servers is connected to the network, it must not overlap with the 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. These subnets are used for Managed Kubernetes internal addressing, and their use may cause conflicts in the global router network.

10. Enter the gateway IP or leave the first address from the subnet, which is assigned by default. Do not assign this address to your devices to avoid disrupting network operation.

11. Enter the service IPs or leave the last addresses from the subnet, which are assigned by default. Do not assign these addresses to your devices to avoid disrupting network operation.

12. Click Create network.

13. Optional: check the network topology on the global router. In the Control panel, on the top menu, click Products → Global Router → router page → Network Map.

Connect an existing network

1. Ensure the network is not already added to any global router in your account. In the Control panel, on the top menu, click Products → Cloud Servers → Network → tab Private networks → check that the network card does not have the tag Global Router.

2. Verify that the subnet meets the following conditions:

   • belongs to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
   • is at least /29, as three addresses will be occupied by Servercore network equipment;
   • it does not overlap with other subnets added to this router: the IP addresses of each subnet on the router must not match the IP addresses of other subnets on it;
   • if a Managed Kubernetes cluster on cloud servers is to be connected to the global router network, the subnet must not overlap with the 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. If a cluster on dedicated servers is connected to the network, it must not overlap with the 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. These subnets are used for Managed Kubernetes internal addressing, and their use may cause conflicts in the global router network.

3. In the Control panel, on the top menu, click Products and select Cloud Servers.

4. Go to Network → tab Private networks.

5. From the network menu, select Connect to Global Router.

6. Select a global router.

7. For each subnet in the network, enter the IP address to be assigned to the router or leave the first available address from the subnet, which is assigned by default. Do not assign this address to your devices to avoid disrupting network operation. The last two available subnet addresses will be reserved as service addresses.

8. Click Connect. Do not close the window until a message appears confirming the network has been connected. After that, in the control panel:

   • the network will appear in the section Servercore Global Router on the router page to which you connected it;
   • in the section Cloud Servers → Network → on the tab Private networks, the network will have the tag Global Router.

3. Connect the network and subnet for the file storage to the router

You need to connect the network and subnet to the global router for the project and pool where the file storage will be created in the future.

You can connect a new network to the router or an existing network if it is not yet connected to any of the account's global routers.

Connect a new network

1. In the control panel, from the top menu, click Products and select Global Router.

2. Open the router page → Networks tab.

3. Click Create network.

4. Enter a network name. It will only be used in the control panel.

5. Select the Cloud Platform service.

6. Select the location where the file storage will be created.

7. Select the project where the file storage will be created.

8. Enter a subnet name. It will only be used in the control panel.

9. Enter the CIDR — the IP address and subnet mask. The subnet must meet the following conditions:

   • belong to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
   • have a size of at least /29, as three addresses will be occupied by Servercore network equipment;
   • do not overlap with other subnets added to this router — there must be no duplicate IP addresses in the subnets of a single router;
   • if a Managed Kubernetes cluster on cloud servers is included in the Global Router network, the subnet must not overlap with the 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24 ranges. If a cluster on dedicated servers is included — with the 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14 ranges. These subnets are used for Managed Kubernetes internal addressing, and their use may lead to conflicts in the Global Router network.

10. Enter the gateway IP address or leave the first address from the subnet, which is assigned by default. Do not assign this address to your devices to avoid network disruption.

11. Enter the service IP addresses or leave the last addresses from the subnet, which are assigned by default. Do not assign these addresses to your devices to avoid network disruption.

12. Click Create network.

13. Optional: check the network topology on the Global Router. In the control panel, from the top menu, click Products → Global Router → router page → Network map.

Connect an existing network

1. Ensure that the network has not already been added to any global router in your account. In the control panel, in the top menu click Products → Cloud Servers → Network → Private networks tab → make sure the network card does not have a Global Router tag.

2. Ensure that the subnet meets the following conditions:

   • belong to a private address range per RFC 1918: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
   • have a size of at least /29, as three addresses will be occupied by Servercore network equipment;
   • do not overlap with other subnets added to this router — there must be no duplicate IP addresses in the subnets of a single router;
   • if a Managed Kubernetes cluster on cloud servers is included in the Global Router network, the subnet must not overlap with the 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24 ranges. If a cluster on dedicated servers is included — with the 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14 ranges. These subnets are used for Managed Kubernetes internal addressing, and their use may lead to conflicts in the Global Router network.

3. In the control panel, from the top menu, click Products and select Cloud Servers.

4. Go to Network → Private networks tab.

5. In the menu of the network, select Connect to Global Router.

6. Select a global router.

7. For each subnet in the network, enter the IP address to be assigned to the router, or leave the first available address from the subnet, which is assigned by default. Do not assign this address to your own devices to avoid network disruption. The last two available subnet addresses will be reserved as service addresses.

8. Click Connect. Do not close the window until a message appears confirming the network has been connected. Once connected, in the control panel:

   • the network will appear in the Servercore Global Router section on the page of the router you connected to. You can view it in the control panel: in the top menu click Products → Global Router → Servercore Global Router section → router page;
   • the network will have a Global Router tag. You can view it in the control panel: in the top menu click Products → Cloud Servers → cloud server page → Network section → network card.

4. Assign an IP address to the cloud server

Configure a local port on the cloud server that is included in the global router network.

Assign an IP address to the port from the cloud server subnet that you connected to the global router in step 2.

1. Add the cloud server to the subnet you connected to the global router in step 2. If you do not have a cloud server yet, create one. When creating a server:

   • in the Internet block, select Public floating IP address or No internet access;
   • in the Private network block, select the subnet you connected to the global router in step 2.

2. Apply changes depending on the port parameter Apply changes. You can view the parameter value in the control panel: in the top menu, click Products → Cloud Servers → cloud server page → tab Ports → block Port settings:

   • When rebooting the server — programmatically reboot the cloud server or manually make changes to the network configuration file on the server;
   • Manually in the server network configuration file — manually make changes to the network configuration file on the server.

5. Specify a route on the cloud server

In the cloud server subnet that you connected to the global router in step 2, you need to specify a static route to the file storage subnet that you connected to the global router in step 3.

Use the Configure static routes in a subnet subsection of the Static Routes.

6. Specify a route in the file storage subnet

In the file storage subnet that you connected to the global router in step 3, you need to specify a static route to the cloud server subnet that you connected to the global router in step 2.

Use the Configure static routes in a subnet subsection of the Static Routes.

7. Create file storage

Control panel

1. In the Control panel, on the top menu, click Products and select File Storage.

2. Click Create Storage.

3. Enter a storage name or leave the name that is automatically created.

4. Select a location where the storage will be created.

   If you need to increase the disk space of a cloud server or Managed Kubernetes cluster using file storage, select the location where the server or cluster is located. To increase the disk space of dedicated servers, file storage can be created in any location.

   If you plan to use storage for backups, we recommend choosing a location different from the main infrastructure location to improve fault tolerance.

5. Fill in the blocks:

   • Subnet
   • Settings
   • Access rules

6. Check the price of the file storage.

7. Click Create.

Subnet

1. Select a private subnet for the file storage that you connected to the global router in step 3. You will not be able to change the subnet after the storage is created.

2. Enter a private IP address for the storage or leave the first available address from the subnet, which is assigned by default. You will not be able to change the IP address after the storage is created.

Settings

1. Select a file storage type:

   • HDD Basic,
   • SSD Universal,
   • SSD Fast.

   Once created, the storage type cannot be changed.

2. Specify the storage size: from 50 GB to 50 TB. After creation, you can increase file storage, but you cannot decrease it.

3. Select a protocol:

   • NFSv4 — for connecting storage to servers running Linux and other Unix systems;
   • CIFS SMBv3 — for connecting storage to Windows servers.

   Once created, the protocol cannot be changed.

Access rules

NFSv4

1. Configure access rules for the file storage:

   • accessible by everyone — the storage will be accessible from any IP address in the private subnet where it is created;
   • access restricted — the storage will be accessible only to specific IP addresses or private subnets. If you create file storage without rules, access will be restricted for all IP addresses.

2. If you selected the Access restricted option, click Add rule.

3. Enter the IP address or CIDR of the private subnet and select the access level.

   After the storage is created, you can configure new access rules.

CIFS SMBv3

1. Configure access rules for the file storage:

   • accessible by everyone — the storage will be accessible from any IP address in the private subnet where it is created;
   • access restricted — the storage will be accessible only to specific IP addresses or private subnets. If you create file storage without rules, access will be restricted for all IP addresses.

2. If you selected the Access restricted option, click Add rule.

3. Enter the IP address or CIDR of the private subnet.

   After the storage is created, you can configure new access rules.

OpenStack CLI

1. Open the OpenStack CLI.

2. Create a file storage network:

   openstack share network create \
     --name <share_network> \
     --neutron-net-id <net_uuid> \
     --neutron-subnet-id <subnet_uuid>

   Specify:

   • <share_network> — the file storage network name;
   • <net_uuid> — the ID of the private or public network to which the file storage will be connected. You can view the list of networks using the openstack network list; command;
   • <subnet_uuid> — the subnet ID. You can view the list of subnets using the openstack subnet list. command.

3. Create the file storage:

   openstack share create <share_protocol> <share_size>\
     --name <share_name> \
     --share-network <share_network_id> \
     --share-type <share_type_name> 

   Specify:

   • <share_protocol> — the file storage connection protocol, NFSv4 or CIFS SMBv3;
   • <share_size> — the file storage size in GB;
   • <share_name> — the file storage name;
   • <share_network_id> — the ID of the file storage network you created in step 2. You can view the list of file storage networks using the openstack share network list; command;
   • <share_type_name> — file storage type. You can view the list of types using the openstack share type list. command.

Terraform

Follow the Create file storage instructions in the Terraform documentation.

8. Mount file storage to the cloud server

The mounting process depends on the operating system on the server and the file storage protocol: NFSv4 or CIFS SMBv3.

NFSv4

Linux

1. Connect to the cloud server.

2. Open the CLI.

3. Install the package for the NFS protocol:

   sudo apt install nfs-common

4. Create a folder for mounting the storage:

   sudo mkdir -p /mnt/nfs

5. Mount the file storage:

   sudo mount -vt nfs "<filestorage_ip_address>:/shares/share-<mountpoint_uuid>" /mnt/nfs

   Specify:

   • <filestorage_ip_address> — file storage IP address. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Connection block → GNU/Linux tab.

Windows

To work with file storage from Windows, we recommend using file storage with the CIFS protocol. If you need to connect storage with the NFSv4 protocol, install and use a client that supports this protocol, then mount the file storage. To mount the file storage, refer to the documentation of your chosen client.

File storage only works with the NFSv4 client version. By default, Windows OS supports NFSv2 and NFSv3 client versions. For more information on NFS versions, see the NFS Overview article in the Microsoft documentation.

CIFS SMBv3

Linux

1. Connect to the cloud server.

2. Install the package for the CIFS protocol:

   sudo apt install cifs-utils

3. Create a folder for mounting the storage:

   sudo mkdir -p /mnt/cifs

4. Mount the file storage:

   sudo mount.cifs -o guest //<filestorage_ip_address>/share-<mountpoint_uuid> /mnt/cifs

   Specify:

   • <filestorage_ip_address> — file storage IP address. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Connection block → GNU/Linux tab.

Windows

1. Connect to the cloud server.

2. Open the CLI.

3. Mount the file storage:

   net use X: \\\\<filestorage_ip_address>\share-<mountpoint_uuid>

   Specify:

   • <filestorage_ip_address> — file storage IP address. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Connection block → Windows tab.