OFFSHORE STORAGE SERVERS
Choose SATA for retained collections or SSD for active datasets. Compare the drive count, aggregate capacity and storage layout, with a separate system drive for your operating environment.
Storage populated. Pool configured. Data path connected.
01 / THE SHORT ANSWER
An offshore storage server is a dedicated physical server configured around high-capacity data storage, with a separate system drive, a published set of storage drives and package-specific network resources. WebCare360 lists 6 SATA configurations and 4 SSD configurations. System drives vary by plan: 400GB SSD or 2 x 2TB NVMe or 240GB SSD; the data-drive count and capacity define the advertised storage total. Your chosen array and filesystem determine usable capacity.
02 / SATA VS SSD
SATA: capacity-oriented storage. Consider the SATA family for archives, backup repositories, media libraries and large-file collections. Its published sets include 1, 3, 6, 9, 10, 11 data drives, spanning 18–200TB of aggregate capacity. Size the retention window and expected growth before choosing a package.
SSD: flash storage for active data. Consider SSD for active datasets and applications that frequently read or update stored data. Flash media can offer greater I/O responsiveness than rotating drives, but the application, access pattern and array still matter. Published SSD configurations span 15.36–122.88TB; no benchmark result is assumed.
Choose by retained capacity and the way data is accessed.
| Storage decision | SATA storage | SSD storage |
|---|---|---|
| Media / orientation | Capacity-oriented SATA drive sets | Flash storage for I/O-oriented access |
| Typical data | Archives, retained copies, media collections | Active datasets and persistent application data |
| Published aggregate capacity | 18–200TB | 15.36–122.88TB |
| Published drive sets | 1, 3, 6, 9, 10, 11 data drives | 4, 5, 8, 10 data drives |
| Separate system drive | 400GB SSD or 2 x 2TB NVMe | 240GB SSD |
| Capacity planning | Retained copies + growth + recovery needs | Active data + access pattern + growth |
| Monthly EUR range | €199.99–€799.99 | €359.99–€1359.99 |
03 / AVAILABLE STORAGE SERVERS
System drives vary by plan: 400GB SSD or 2 x 2TB NVMe or 240GB SSD. Each is separate from the data-drive capacity. Storage figures below are published aggregate drive capacities; usable capacity depends on your array and filesystem configuration. Deployment depends on hardware availability.
* Stock dependent.
* Stock dependent.
Review the Service Agreement ↗ for the governing service and payment terms.
04 / HOW THE STORAGE IS BUILT
The system drive holds the operating environment; current plans specify 400GB SSD or 2 x 2TB NVMe or 240GB SSD. It is a separate device role, not extra capacity added to the advertised SATA or SSD data-drive total.
The storage drives form the physical drive set. For example, the 18TB SATA configuration publishes 1 x 18TB HDD. Those drives can be arranged into volumes or an array according to the chosen configuration.
A storage pool is the logical arrangement presented to files and applications. Its usable capacity depends on the selected layout and filesystem. The network then carries data between that pool and your clients or services. No single RAID level or filesystem is assumed.
Applications reach stored files through services and the network.
05 / CAPACITY & WORKLOAD FIT
Start with the data you need to retain: active files, retained copies, versions and expected growth. Then allow for the selected array layout and filesystem. A published drive total is raw aggregate capacity, not a guarantee of usable space. Choose SATA or SSD by how often the data is accessed as well as how much you keep. For example, if the two 10TB data drives are configured as a mirror, they hold two copies and provide at most 10TB before filesystem overhead. This is a planning example, not the default RAID configuration.
Capacity for retained copies, archives and recovery datasets. Define the backup workflow and retention policy separately.
Video, audio and image collections where total capacity and sustained delivery requirements shape the drive set.
Downloadable packages, assets and large objects: plan their combined size and room for future versions.
Long-lived datasets and project archives where retained data volume is the primary sizing requirement.
Stored content feeding websites, applications or delivery workflows. Match Port and Traffic to the volume you need to move.
Persistent application data: evaluate access pattern, capacity and media together, especially for frequently updated datasets.
06 / RAID, REDUNDANCY & BACKUPS
RAID / array layout. Multiple drives can be organized into a chosen redundancy or performance layout. Options are published, including hardware RAID wording for SSD; no specific default RAID level is listed per package.
Redundancy. Depending on the selected layout, the set may tolerate certain drive failures. It does not provide a separate historical copy or protect against every cause of data loss.
Backup. A separate recoverable copy supports recovery after loss, deletion or corruption. Dedicated servers are not backed up by WebCare360 unless an additional backup service is ordered. Maintain and test that recovery plan.
A separate recoverable copy serves a different purpose.
07 / MOVING LARGE DATA
Large storage becomes useful when the data can be moved where it needs to go. Estimate the dataset you need to ingest, retrieve or distribute, together with the time available for each transfer.
Storage sets how much data can be held. Port describes the published connection arrangement: SATA lists 1Gbps Uplink / 10Gbps Port or 1Gbps Uplink; SSD lists 1Gbps Uplink / 10Gbps Port. Keep both parts of that wording when planning a large transfer.
Traffic is the transfer model. All 10 packages list Unmetered Traffic, which does not remove the selected port/uplink constraints. Storage reads, protocol, route and destination also affect how quickly a dataset can be moved.
The destination and route also shape a large transfer.
08 / OPERATING SYSTEMS & CONTROL
The operating environment controls how the data drives are mounted, which filesystem is used, and how files are exposed to applications or network services. Linux or Windows is listed; confirm IPMI / iLO access for remote administration with the selected configuration. Confirm the installation image, hardware compatibility and any required licence for your storage setup.
26.04 LTS · 24.04 LTS · 22.04 LTS
Confirm installation image
13.x · 12.x
Confirm installation image
10.x · 9.x · 8.x
Confirm installation image
10.x · 9.x · 8.x
Confirm installation image
10 · 9
Confirm installation image
2025 · 2022 · 2019
Confirm licence and image
Fedora and custom OS / ISO installation are also listed on the public storage page. Discuss image and storage-layout requirements before provisioning. Dedicated servers are unmanaged unless specifically agreed: root or administrator control makes the filesystem, storage services and maintenance your responsibility.
09 / OFFSHORE SERVICE CONTEXT
Stored files and data services remain subject to the applicable hosting-location law and current service rules. Storage use does not exempt prohibited activity. Review the Service Agreement and its current handling of legal or takedown requests before choosing the environment for your data.
10 / FAQ
Choose by retained capacity and access pattern. SATA is the capacity-oriented option for archives, retained copies and large media collections; SSD is flash storage for active datasets and frequent I/O. Compare the complete drive set and application needs without assuming a fixed speed improvement.
Each package lists a separate system drive for the operating environment (400GB SSD or 2 x 2TB NVMe or 240GB SSD, depending on the plan), in addition to the storage-drive set. It is not counted in the advertised SATA or SSD data-drive total.
The source lists both. For example, 1 x 18TB HDD totals 18TB; 4 x 3.84TB totals 15.36TB. Those are aggregate drive capacities before the selected array and filesystem affect usable space.
Published SATA configurations span 18–200TB and SSD configurations 15.36–122.88TB. Include retained copies, versions, data growth and the required layout when sizing capacity.
It is a logical arrangement of the physical drive set that presents storage to the operating system and applications. The chosen layout determines how drives are organized; no universal filesystem or RAID level is specified for these packages.
RAID options are published, including hardware RAID wording for the SSD family. No specific default RAID level is listed per package. Confirm the required arrangement and its effect on usable capacity.
No. Redundancy within an array is different from a separate recoverable copy. WebCare360 does not back up Dedicated servers unless an additional backup service is ordered. Keep and test an independent recovery plan.
Read the complete Port wording, including Standard or Uplink qualifiers. SSD lists 1Gbps Uplink / 10Gbps Port; SATA lists 1Gbps Uplink / 10Gbps Port or 1Gbps Uplink. All 10 publish Unmetered Traffic. A 10Gbps interface label alone does not establish a guaranteed 10Gbps transfer service.
Both families state 24–48 Hours based on hardware availability, with a 1 month minimum term. Confirm the selected drive and operating-system requirements before provisioning.
Linux and Windows are listed, with custom OS/ISO installation described on the public page. Confirm image compatibility and licences. You control how storage is mounted and exposed; management is not bundled by default.
YOUR NEXT CONFIGURATION
Compare the drives, system resources and network terms for your workload.
Talk to Our Team ↗