Mounting file shares on remote clients

Stay organized with collections Save and categorize content based on your preferences.

This page shows you how to mount a Filestore file share on clients in a remote network, such as:

• Compute Engine VMs on a different project or VPC network.
• On-premises clients on your local network.

Establish a VPN connection between the remote network and the VPC network of the Filestore instance

Before you can mount a file share on a remote client, you must establish a VPN connection between the client's network and the VPC network of the Filestore instance.

1. Create an HA VPN or a Classic VPN. For detailed instructions, see Creating an HA VPN gateway to a Peer VPN gateway ro Create a Classic VPN gateway using static routing.

   Ensure that:

   • The subnet ranges of the client and the Filestore instance don't overlap.
   • The IP address of the Filestore instance is advertised as a custom route during BGP configuration.
   • You must use an external or third-party VPN provider.

   For details, see Known issues.

2. Configure the VPN gateway and tunnel on the remote network:

   • For specific configuration guidance for certain VPN devices, see VPN Interoperability Guides.
   • For general configuration parameters, see Configuring the Peer VPN Gateway.

Mount the Filestore file share on the remote client

Once the VPN connection is established, you can mount the file share on any client in the remote network using any of the standard mounting methods.

If you use HA VPN or Cloud Interconnect and mount the file share to client VM that's running Linux kernel version 5, set the nconnect mount option to 1. This setting prevents multiple connections to different Filestore backend nodes and ensures connection to mounted file shares.

   mount -o nconnect=1

What's next

• Learn more about creating Compute Engine instances.
• Learn more about creating Filestore instances.
• Learn more about Cloud VPN.