What Is Filestore
Filestore is Google Cloud's fully managed network file storage service: it exposes a standard NFSv3 (and, on some tiers, NFSv4.1) file share that multiple Compute Engine VMs, GKE pods, or on-premises machines can mount simultaneously and read and write to concurrently, just like a traditional POSIX file system. This makes it fundamentally different from Cloud Storage's object model — Filestore gives you real directories, file locking, and POSIX permissions, which many existing applications expect out of the box without code changes.
Cricket analogy: It's like a shared team dressing room where every player on the squad can walk in and use the same lockers and kit simultaneously, unlike a private locker assigned to just one individual player.
Service Tiers
Filestore offers several tiers: Basic HDD is the lowest cost, suited to general-purpose file sharing without demanding throughput needs; Basic SSD delivers substantially higher throughput and IOPS for performance-sensitive workloads at a higher price; Zonal (formerly High Scale SSD) scales up to hundreds of terabytes with high performance for large-scale workloads like machine learning training data; and Enterprise adds regional high availability with a 99.99% SLA and integrated snapshots, aimed at business-critical applications that can't tolerate a single zone failure.
Cricket analogy: It's like choosing a basic club-level practice net (Basic HDD), a solid state-level training facility (Basic SSD), a national academy with elite equipment (Zonal), and a fully redundant international stadium with backup floodlights guaranteeing play continues (Enterprise).
# Create a Basic SSD Filestore instance with a 1TB file share
gcloud filestore instances create nfs-share-1 \
--zone=us-central1-a \
--tier=BASIC_SSD \
--file-share=name="vol1",capacity=1TB \
--network=name="default"
# Get the instance's IP address for mounting
gcloud filestore instances describe nfs-share-1 --zone=us-central1-a \
--format='value(networks[0].ipAddresses[0])'
# Mount the NFS share on a Compute Engine VM
sudo mkdir -p /mnt/nfs-share
sudo mount -o rw,intr 10.0.0.2:/vol1 /mnt/nfs-shareUse Cases
Filestore is the right choice whenever multiple compute instances need concurrent, low-latency, POSIX-compliant read-write access to the same file set: rendering farms sharing frame assets, content management systems serving uploaded media, genomics or ML pipelines reading shared training datasets across a GKE cluster, and lift-and-shift migrations of existing on-premises applications that were built assuming an NFS mount. It is not meant to replace a database, and it is overkill for a single VM's own data, which belongs on a persistent disk instead.
Cricket analogy: It's like a shared match-day data feed that every broadcaster's commentary box accesses simultaneously during live play, unlike a single analyst's private laptop that only they need for personal notes.
Filestore requires the client VM to be on the same VPC network (or connected via VPC peering or Interconnect) as the Filestore instance, since it's accessed over NFS on a private IP address rather than through a public API endpoint like Cloud Storage.
Backups and Snapshots
Filestore backups create a regional, incremental copy of an entire file share that can be restored to a new instance in any zone within the region, protecting against zonal failure and accidental deletion of the whole instance. Snapshots, available on the Zonal and Enterprise tiers, are faster and cheaper point-in-time copies stored within the same zone, useful for quick recovery from an accidental file deletion or for cloning a share for testing, though they don't protect against a full zonal outage the way backups do.
Cricket analogy: It's like a full archived broadcast of an entire day's play kept in a separate regional facility (backup, protects against studio fire), versus a quick instant-replay buffer kept courtside for the last few overs (snapshot, fast but local).
Filestore instances must live in the same VPC network as the clients that mount them, and resizing a Basic tier instance down is not supported — you can only grow it. Plan capacity and network placement carefully before creating a production instance.
- Filestore is fully managed NFS file storage offering POSIX-compliant, concurrent multi-client read-write access.
- It differs fundamentally from Cloud Storage's flat object model by providing real directories, file locking, and POSIX permissions.
- Tiers span Basic HDD, Basic SSD, Zonal (high scale), and Enterprise (regional HA with 99.99% SLA).
- Filestore is accessed over NFS on a private IP, requiring the client VM to share the same VPC network.
- It suits shared datasets for render farms, CMS media, ML training pipelines, and lift-and-shift NFS applications.
- It's overkill for a single VM's own data, which belongs on a persistent disk instead.
- Backups are regional and protect against zonal failure; snapshots (Zonal/Enterprise) are faster but zone-local point-in-time copies.
Practice what you learned
1. What protocol does Filestore primarily use to expose file shares to clients?
2. What is required for a Compute Engine VM to mount a Filestore instance?
3. Which Filestore tier adds regional high availability with a 99.99% SLA?
4. What is the key difference between a Filestore backup and a snapshot?
5. When is Filestore the wrong choice compared to a persistent disk?
Was this page helpful?
You May Also Like
Persistent Disks Explained
How Google Cloud's network-attached block storage works for Compute Engine — disk types, snapshots, resizing, and read-write versus read-only attachment.
Choosing the Right GCP Storage
A decision framework for picking between Cloud Storage, Persistent Disks, and Filestore based on access pattern, cost, and performance needs.
Cloud Storage Basics
An introduction to Google Cloud Storage's object model — buckets, objects, naming, access control, and the durability and consistency guarantees behind it.