Storage 264
- AMD EPYC 4565P16 cores · 32 threads
- 128 GBDDR5 ECC
- 12 × 22 TBHDD + 3.84 TB NVMe
- 25 Gbps portUnmetered traffic
Storage series · 12-bay HDD
Twelve 22 TB hard drives, a pair of NVMe drives for the OS and metadata, and a 25 Gbps port with unmetered traffic, for $699/mo. Storage 264 is built for backups, archives, media libraries and object storage.

Configurations
Monthly prices in USD, excluding taxes. Unmetered traffic, DDoS protection, IPMI and 24/7 support included.
Twelve 22 TB hard drives that you lay out yourself, from mirrors to double or triple parity.
Two 1.92 TB NVMe drives hold the operating system and can keep metadata and small files off the spinning disks.
Restores, replication and media delivery run with no traffic cap and no egress fees, so reading your data back costs nothing extra.
The 16-core EPYC 4565P, boosting to 5.7 GHz, and 128 GB of DDR5 ECC leave room for compression, checksums, encryption and caching.
Buying guide
Storage 264 combines a 16-core AMD EPYC 4565P (Zen 5, 4.3 / 5.7 GHz) and 128 GB of DDR5 ECC with 12 × 22 TB hard drives for 264 TB raw, 2 × 1.92 TB of NVMe and a 25 Gbps port with unmetered traffic. It is assembled to order, usually delivered the same day, and available in Ashburn, Los Angeles, Amsterdam and Frankfurt.
It is built for backup repositories such as Proxmox Backup Server, restic or Borg, S3-compatible object storage, media libraries and origins, log archives and datasets.
With one model in the series, the main decision is the disk layout. Estimated usable capacity, in decimal TB before filesystem overhead:
| Layout | Usable (estimate) | Drive failures tolerated |
|---|---|---|
| RAIDZ2 or RAID 6, 12 drives | about 220 TB | 2 |
| RAIDZ3, 12 drives | about 198 TB | 3 |
| Two 6-drive RAIDZ2 groups | about 176 TB | 2 per group |
| Mirrors (RAID 10) | about 132 TB | 1 per pair |
Use the NVMe pair for the OS and, with ZFS, a mirrored special vdev for metadata. For other disk counts, ask for a custom build.
Availability
Other families




FAQ
As an estimate in decimal terabytes before filesystem overhead, Storage 264 gives about 220 TB with RAIDZ2 or RAID 6 across all twelve drives, 198 TB with RAIDZ3, 176 TB with two six-drive RAIDZ2 groups and 132 TB with mirrors. Filesystems reserve some additional space for metadata, so plan for a little less.
ZFS is a common choice for backup and archive servers because it checksums every block, compresses data and makes snapshots cheap. Linux software RAID (mdadm) with XFS or ext4 is simpler if you prefer standard tools. S3-compatible object storage software can run on top of either.
Yes. Place it in a different location from your production servers, for example Frankfurt for production in Amsterdam, and send encrypted backups over the public network, where traffic is unmetered. Within one location, free private VLANs keep backup traffic off the public network. Backups remain your responsibility on unmanaged servers, so test restores regularly.
Custom builds with other disk counts or sizes are available by quote, and fleet pricing starts at 5 servers. You can also add more Storage 264 servers in the same location and connect them over free private VLANs.
$699/mo with unmetered traffic, DDoS protection and IPMI included. Usually delivered the same day.