Rackspace by rack unit
Specify rack units, depth, weight, power and access for individual servers or small expansions.
Select service: Rackspace by rack unitFocus of this page: Rackspace and datacenter services for your operations.
Services in detail
Services for your datacenter
From rackspace to operations: choose your service area. Location, capacity, service hours and terms are reviewed for your request.
Dedicated rack
Plan a dedicated rack with agreed power, cabling, access and expansion space. Occupancy and location availability require review.
Select service: Dedicated rackPrivate cage & segregated areas
Discuss physical separation, access roles and expansion space for larger installations. Design and location are assessed individually.
Select service: Private cage & segregated areasPower, cooling & capacity planning
Assess power demand, A/B feeds, metering, heat output and reserves. Agree redundancy and billing for the rack design.
Select service: Power, cooling & capacity planningRemote hands & on-site service
Coordinate inspections, authorised restarts, cabling and component replacement. Agree access and service windows beforehand.
Select service: Remote hands & on-site serviceCross-connect & cabling
Plan connections between racks, handover points and carriers, including media, interfaces, labelling and documentation.
Select service: Cross-connect & cablingManaged servers & operating systems
Define responsibilities for operating systems, updates, monitoring and incident handling. Agree application support scope separately.
Select service: Managed servers & operating systemsVirtualisation, private cloud & containers
Plan compute, tenant separation, standards and provisioning for virtual machines and containers. Document capacity and operating boundaries.
Select service: Virtualisation, private cloud & containersStorage & data management
Plan block, file or object storage around capacity, access patterns, growth and protection. Include retention and deletion requirements.
Select service: Storage & data managementBackup, retention & restore testing
Define scope, frequency, separate copies and restore tests. Plan evidence that restored systems are usable.
Select service: Backup, retention & restore testingDisaster recovery & continuity planning
Plan recovery order, dependencies, communication and exercises. Agree RPO and RTO per application rather than assuming blanket guarantees.
Select service: Disaster recovery & continuity planningNetwork, firewall & segmentation
Review network zones, access paths, firewall rules and administrative permissions together. Organise traceable changes and approvals.
Select service: Network, firewall & segmentationMonitoring, patch & incident management
Agree metrics, alert routing, maintenance windows and escalations. Document service hours, response paths and reporting scope.
Select service: Monitoring, patch & incident managementHardware lifecycle & replacement
Coordinate procurement, installation, spare parts and retirement. Include inventory, warranty scope and secure media handling.
Select service: Hardware lifecycle & replacementMigration & datacenter relocation
Plan inventory, dependencies, transport, cutover and rollback. Define technical acceptance and operational handover before moving.
Select service: Migration & datacenter relocationAccess, documentation & operating records
Agree authorised visitors, access procedures, rack documentation and required records. Certifications and reports must be confirmed for the specific location.
Select service: Access, documentation & operating recordsFrom rack capacity to a clear operating plan
A datacenter design starts with capacity, recovery requirements and responsibilities. These three steps help prepare the discussion.
Map capacity
Plan rack units, power consumption, weight and growth together. Include existing hardware, network connections and your preferred start date.
Define operations
Clarify access permissions, service hours, monitoring and escalation paths. For backup and recovery, specify acceptable data loss and maximum downtime.
Prepare handover
Document acceptance criteria, migration windows, a rollback plan and operating documentation. The proposal defines the agreed services and responsibilities.
Datacenter planning questions
How much rackspace do I need?
Device count alone is not enough. Rack units, mounting depth, power, cooling, cabling and growth reserves determine the space required. A smaller initial setup and later expansion are assessed for feasibility.
Are backup and high availability the same?
No. Redundancy can keep operations running after a component failure; a backup restores data from an earlier state. Both require suitable retention, access protection and regularly tested recovery procedures.
What information helps with my request?
Include the preferred location, rack units or racks, estimated power, connections and start date. Describe operational support and recovery targets. Prices, availability and service commitments are reviewed individually.
Discover
Your infrastructure. Well thought out until the restart.
From daily platform operations to dealing with outages: These topics provide orientation for your next decisions.
Operate infrastructure
Plan monitoring, maintenance and capacity together. A coordinated operating model makes it clear who is responsible for which service.
Learn more
Prepare for recovery
What data must be available again and when? Derive backup, retention and verifiable recovery tests from this.
Learn moreDeveloping the cloud in an orderly manner
Identities, platform standards, automation, and cost form the foundation of controlled cloud operations.
Learn morePut ideas into practice
Plan recovery as a shared task
A backup becomes useful when recovery fits the application. Consider access, dependencies and the order in which services are needed as well as the data itself.
What should a recovery test cover?
Test usable applications, permissions and connected systems as well as restored files. Record elapsed time, deviations and follow-up actions. Recovery objectives are agreed for each individual service.
Three points to prepare
- Priorities: Which business processes need to work first?
- Targets: What data loss and interruption can each service tolerate?
- Evidence: Who tests recovery and records the outcome?