Packet's Block Storage service looks and smells a lot like Amazon’s EBS. You can create volumes of different performance profiles, leverage snapshot policies and more - all via our API or portal. The service is highly redundant.
Comparing our block storage service to similar offerings at other clouds, an important difference is that at Packet you don’t have the benefit of a platform-managed hypervisor layer (we only offer bare metal compute and never leave an agent or any other tools/software on your server after it is deployed).
As such, there is a bit more you should know about how to troubleshoot or deal with any issues that may arise. Check out the tips below.
When you need persistent storage, with built-in replication and snapshots, our block storage product is a very useful tool. We offer two performance tiers:
Standard Tier ($0.000104/GB per hour) - With 500 IOPS per volume this is good for backups, dev/test, and medium use datasets.
Premium Tier ($0.000223/GB per hour) - With 15,000 IOPS per volume this is targeted at higher I/O heavy workloads.
A snapshot is a differential copy of your volume made at a specific moment in time. If you have a 500GB volume, but only 250 GB of data on it, your snapshot is only 250 GB. With a snapshots, you are only billed for the changes to the original block device from the time the snapshot is made — as such, a policy of 5 snapshots may end up being only a small amount of storage if your rate of change on the device is low. Billing for all snapshots is at our lower $0.07/GB per month tier.
While our Block Storage product is the perfect match for a wide variety of use cases, the first and most important step is to understand when not to use block storage at Packet.
As a general rule of thumb, databases are not a good fit for our Block Storage, especially those that are not resilient due to minor hiccups. While uncommon, even a small loss of connectivity to some databases can cause major issues.
If block storage doesn't meet your needs, we offer two other options:
Various local disk options (SSD's and NVMe Flash) on each server config.
The s1.large storage-focused server includes 24 TB of SATA w/ SSD's for cache.
|Elastic Block Storage Guide||How to setup, create, attach storage volume|
|Elastic Block Storage on Windows||How to setup Elastic Block Storage on a Windows Instance|
|Extending Block Storage Volume Guide||How to extend existing storage volume|
Was it helpful?