Reliable, high-performance block storage for virtual machine instances. Enterprise scale, limitless flexibility, and competitive price for performance.
Block storage that is easy to deploy and scale
No volumes, no striping, no sizing—just disks. Stop the headache of dealing with partitioning, redundant disk arrays, or subvolume management. Scale up or down as needed, and only pay for what you use.
Industry-leading price and performance
HDD offers low-cost storage when bulk throughput is of primary importance. SSD offers consistently high performance for both random-access workloads and bulk throughput. Both types can be sized up to 64 TB.
Flexibility that comes with no downtime
Attach multiple persistent disks to Compute Engine or GKE instances simultaneously. Configure quick, automatic, incremental backups or resize storage on the fly without disrupting your application.
"By using Persistent Disks we got very easy differential backups with Snapshots. Coming from a world where we did full backups every single day, this improved our backup times from two to three hours down to three minutes."
Jeremy Tinley, Senior Staff Systems ArchitectWatch the full video
Adding or resizing zonal persistent disks.
Creating persistent disk snapshots
Create snapshots to periodically back up data from your zonal persistent disks or regional persistent disks.
Codelab: Creating a Persistent Disk
Follow along with this lab to learn how to create persistent disks and attach them to a virtual machine.
How to set up a new persistent disk for PostgreSQL Data
Learn how to set up a basic installation of PostgreSQL on a separate persistent disk, which is also the boot disk, on Compute Engine.
Deploying apps with regional persistent disks
See how to release a highly available app by deploying WordPress using regional persistent disks on Google Kubernetes Engine.
Standard Persistent Disks (HDD)
Big data, big compute workloads.
Most cost-effective disk type.
Balanced Persistent Disks (SSD) (new!)
Standard enterprise applications
Best price per GB
Performance Persistent Disks (SSD)
Scale-out analytics, databases, persistent cache
Extreme Persistent Disks (SSD)
Enterprise applications such as SAP HANA, Oracle
Highest performance to meet the needs of largest in-memory databases
Hot cache for databases and for real-time analytics
Flash-optimized ephemeral storage offering the lowest latencies
|Find the right price and performance for your workload||Persistent Disks come in four types at different price points and performance profiles. We've designed these disk types based on years of working with customers to understand the range of uses of our Persistent Disks. Understand the price and performance of each disk type.|
|Scale anytime: resize your block storage while it's in use||Persistent Disk allows you to flexibly resize your block storage while it’s in use by one or more virtual machines. Performance scales automatically with size, so you can resize your existing persistent disks or add more persistent disks to an instance to meet your performance and storage requirements—all with no application downtime.|
|Use disk clones to create new disks from a data source||Use Disk Clones to quickly bring up staging environments from production, create new disks for backup verification or data export jobs, and create disks in a different project.|
|Use Local SSD option for temporary storage||Local SSDs are physically attached to the server that hosts your VM instance. This tight coupling offers superior performance, very high input/output operations per second (IOPS), and very low latency compared to other block storage options. Local SSDs are often used for temporary storage such as caches or scratch processing space.|
|Automatic security and encryption||Automatically encrypt your data before it travels outside of your instance to Persistent Disk storage. Each Persistent Disk remains encrypted with system-defined keys or with customer-supplied keys. Google distributes Persistent Disk data across multiple physical disks, ensuring the ultimate level of security. When a disk is deleted, we discard the keys, rendering the data irretrievable.|
|Decoupled compute and storage||Your storage is located independently from your virtual machine instances, so you can detach or move your disks to keep your data even after you delete your instances.|
|Use snapshots to back up your data on a schedule||Create snapshots to periodically back up data from your zonal or regional Persistent Disks. To reduce the risk of unexpected data loss, consider the best practice of setting up a snapshot schedule to ensure your data is backed up on a regular schedule.|
|Use Machine Images to store your disk metadata and permissions||Use a Machine Images to store all the configuration, metadata, permissions, and data from one or more disks for a VM instance running on Compute Engine. The VM instance that you use to create a machine image is referred to as a source instance.|
Cloud AI products comply with the SLA policies listed here. They may offer different latency or availability guarantees from other Google Cloud services.
Ex: ORACLE® is a registered trademark of Oracle Corporation.