01
Planning around physical resources
Assess processors, memory and storage as a system. Identify the software requirements for hardware and operating-system compatibility before ordering.
COMPUTE / BARE METAL
A clear infrastructure decision when the physical server matters.
Consider Bare Metal for hardware-level control, specific software requirements or consolidated workloads. Plan operating-system compatibility, storage layout and maintenance responsibilities alongside processor and memory capacity before choosing a physical server.
FibaCloud platformBare Metal
Workload first
Planning around physical resourcesClear criteria for consolidationExplicit operating responsibilities
01 / Overview
More direct control calls for a clearer operating plan.
Bare Metal lets you address infrastructure at the physical-server level. It is not automatically the best answer whenever a virtual server feels constrained. First identify whether the requirement is capacity, hardware access, licensing or control over the virtualisation layer.
Plan the operating system, storage layout, networking and recovery methods together. Confirm hardware, installation and administrative access options against the current service scope. Treat hardware redundancy and application continuity as separate questions, and prepare the application for physical-server maintenance.
02
Clear criteria for consolidation
When several services share one machine, account for resource competition, licences and failure impact. The size of the affected workload matters as much as utilisation.
03
Explicit operating responsibilities
Document ownership of hardware, operating-system, virtualisation and application maintenance. Administrative access and recovery procedures belong in the same plan.
02 / Architecture
Operating layers of a physical server
Illustrative layers: hardware, operating system and applications have distinct maintenance responsibilities. Data recovery is planned separately.
Selection guideArchitecture explained
- Physical hardware
- Operating system
- Service layer
- Data and recovery
03 / Selection guide
Before you choose the physical configuration.
| Consider | How to decide | Why it matters |
|---|---|---|
| Processor and compatibility | Match processor characteristics against software and licensing requirements. | The highest core count is not necessarily the best application fit. |
| Memory and storage layout | Size active data, persistent data and growth separately. | Storage redundancy does not eliminate the need for an independent backup. |
| Networking and access | Define user traffic, administrative access and data movement. | Selecting hardware alone does not complete secure operations. |
| Maintenance and continuity | Plan restarts, hardware work and recovery procedures. | Application behaviour during server unavailability should be understood in advance. |
04 / Use cases
Situations where a physical server may be a useful fit.
Specific software requirements
Review vendor requirements for software tied to hardware or licensing conditions. Confirm compatible components and supported operating systems before deployment.
Consolidated service infrastructure
Measure the combined requirements of services or virtualisation workloads. Assess the shared impact of relying on one physical machine.
Demanding data processing
Test processor, memory and storage requirements together for long-running work. Include the time needed to move inputs and results.
Test your connection
Choose a location to measure your connection latency.
05 / From planning to operation
Define the operating scenario before installation.
Confirm the requirement
Document software, licensing, hardware and access needs. State which requirement the Bare Metal choice is intended to satisfy.
Prepare the installation
Plan around the supported operating system and storage layout. Assign responsibility for updates and ongoing administration.
Migrate deliberately
Test transfer duration and data consistency. Validate the application on the new server before changing production traffic.
Practise recovery
Test backup restoration and the response to server unavailability. Keep operating instructions accessible to the people responsible.
Is Bare Metal always faster?
No. Results depend on hardware, application parallelism, data access and configuration. Compare the same workload in both environments before assuming a performance advantage.
Can I run virtualisation on Bare Metal?
Confirm the technical requirements, hardware support and service terms for your chosen configuration. Virtualisation software, licences and management need their own plan.
Does a physical server replace backups?
No. Redundant disks or copies on the same machine are not an independent recovery plan. Define backup scope, retention and storage location separately.
Is server management included?
Hardware service and operating-system or application management can have different scopes. Clarify update, monitoring, support and recovery responsibilities against current terms before ordering.
Go deeper with practical guides.
Connect product decisions with installation, configuration and operating knowledge.
Technical references
These references explain the technical concepts discussed on this page. Available configurations and service scope are defined by FibaCloud product and order information.
FIBACLOUD / Bare Metal
Start with your project. Build on the right resources.
Tell us about your application, expected usage and operating requirements. Let’s bring the resource choices together.