Browse this section

Understanding disks, RAID and usable storage

An offer showing several drives describes raw hardware capacity. The space available to your application depends on the selected RAID layout, filesystem, reserved space and any replication. Ask for a usable-capacity estimate before deciding that a configuration is large enough.

Check the proposed layout

  • Identify the drive count, capacity and type, and which drives hold the operating system, database and other application data.
  • Confirm whether RAID is implemented in hardware or software, the intended redundancy level and the procedure for a failed drive.
  • Allow space for growth, logs, temporary files, updates and rebuild activity. Filling a filesystem can disrupt applications.
  • Specify an independent backup plan. RAID can help with certain disk failures, but it does not reverse accidental deletion or application corruption.

Do not initialise drives, recreate arrays or change controller settings on a live server without a reviewed migration and recovery plan. For a storage alert, send the service reference and the exact warning before attempting a repair.

Was this guide helpful?

Related guides

Choosing a control panel and its licence

A control panel can simplify website, database or mail administration, but it also introduces software compatibility, resource and licensing requirements. Panel installation should be coord…

Choosing CPU and RAM for a dedicated server

CPU model, core count, memory capacity and your application design all matter. A workload that runs one busy thread has different needs from parallel build jobs or many independent virtual …

Need help applying this to your service?

Tell us your service reference and what you need to achieve. Never include passwords or private keys in a ticket.

Contact support →
← All knowledgebase topics