Monthly transfer planning
300TB-600TB Servers
Request 300 to 600 TB of data transfer per billing month for mirrors, video downloads or scheduled replication. This is traffic, not disk space. Include your busiest delivery window in the quote request.
Workload illustration, not live server measurements.
Price on quote
Pricing and availability depend on your requirements. Confirm the configuration, recurring price in EUR and any setup charge in your written quote.
Some workloads do not need the largest port all month. They need a predictable allowance for downloads, media delivery, patch distribution, or archive retrieval.
Peak Gbps still matters. If your traffic arrives in sharp windows, compare port-speed products before choosing a monthly transfer allowance.
Use cases
In a 30-day month, 300 decimal TB is about 0.93 Gbps averaged around the clock. Deliver the same volume in eight hours a day and the average during delivery rises to 2.78 Gbps, before overhead. Check the 1 to 5 Gbps port options.
Workload: A media library with predictable monthly views and known average bitrate.
Sizing: Monthly transfer, hot-title storage, and player bitrate ladder are the key sizing inputs.
Fit: 300TB to 600TB plans suit content libraries where total monthly delivery is the buying unit.
Limit: If many viewers arrive in a short live window, peak port sizing may matter more.
Workload: Large files, updates, packages, ISO images, or private distribution endpoints.
Sizing: Object size, retry behavior, regional audience, and cache strategy affect total transfer.
Fit: A transfer allowance gives a clear planning model for download-heavy services.
Limit: Mirrors with unpredictable bursts may need 10G, 20G, or pooled capacity.
Workload: Controlled restore and retrieval traffic for data archives.
Sizing: Storage redundancy, restore windows, and transfer targets should be scoped before order.
Fit: A monthly transfer plan can match predictable restore patterns better than oversized unmetered capacity.
Limit: Backups, retention, and replication are separate architecture decisions.
Provisioning
For large transfers, confirm support for your backup or synchronisation tools and record network counters over the same interval as the billing period.
Check installation, driver and licensing requirementsQuestions & answers
On this page it means monthly data transfer, not local disk capacity. Check the storage specification separately and confirm whether ingress, egress or both are counted.
Over 30 days, 300 decimal TB averages about 0.93 Gbps; 600 TB averages about 1.85 Gbps. These are planning averages, not port speeds. A short restore window can require a much faster port.
Multiply average object size by completed downloads and include retries, cache fills and replication if they count under the order. Use transfer counters over a full billing cycle when available.
Confirm the reset date, traffic accounting and overage or rate-limit terms before ordering. Do not assume the server stops, slows down or automatically buys another allocation.
Use the billing period specified in your order. Align your own usage alerts with that period; calendar-month graphs can give misleading remaining balances.
Related paths
Compare adjacent bandwidth, media, and pooled-capacity routes before choosing a configuration.
Send monthly TB target, busiest-hour traffic, object sizes, and storage requirements.
Configure 300TB-600TB Server
Debian stable
Ubuntu Server LTS
AlmaLinux
Rocky Linux
Fedora Server
Windows Server