Data Center • Virtualisation • Storage • High Availability

For a hosting provider or data centre operator, infrastructure is part of the product itself. Its performance, availability and security directly affect the services delivered to customers.

We design, modernise and develop environments for hosting providers, data centres and infrastructure service providers — from virtualisation clusters and distributed storage to networking, backup, monitoring and security.

In a hosting environment, it is not enough for individual servers to work correctly. What matters is the resilience of the entire architecture and the ability to maintain services predictably during failures, expansion and planned changes.

Infrastructure that is part of the service

In a hosting company, an infrastructure failure is not simply an internal IT issue. It can affect dozens or hundreds of customers using servers, virtual machines, storage or backup services at the same time.

Infrastructure should therefore be designed not only around hardware specifications, but also around how the complete environment behaves during failures, overload, maintenance and future expansion.

Virtualisation

We design clusters for virtual machines and hosting services with HA, storage, networking and future scalability in mind.

Storage

We design local and distributed storage tailored to workloads, required capacity, performance and fault-tolerance requirements.

Networking

We design the network layer connecting hosts, storage, customers, locations and security systems.

Proxmox and virtualisation platform modernisation

For hosting providers, the virtualisation platform is one of the core components of the service. It must provide predictable resource management, workload migration, storage integration and High Availability capabilities.

We design environments based on Proxmox VE, both as new clusters and as target platforms in migration projects.

The scope can include:

  • cluster architecture,
  • server and compute resource selection,
  • local or distributed storage,
  • cluster and migration networking,
  • High Availability,
  • backup,
  • monitoring,
  • future expansion planning.

A virtualisation platform should not be designed separately from storage, networking and backup. Only all of these layers together form a production-ready environment.

Ceph and distributed storage

In environments that require shared and scalable storage, we use technologies such as Ceph.

A distributed architecture can reduce dependency on a single storage array and make it possible to expand storage together with additional infrastructure nodes.

A Ceph design should consider not only disk capacity, but also:

  • number of hosts and OSDs,
  • workload profile,
  • network performance,
  • replication or Erasure Coding,
  • failure domains,
  • free-capacity headroom,
  • recovery and rebalancing,
  • future scaling plans.

Block Storage

Storage for virtual machines and other workloads that require block-level access.

File Storage

Distributed file storage for services that require shared access to data.

Object Storage

Object storage architecture for applications and services using an S3-compatible API.

Storage designed for the workload

Not every service has the same requirements. Virtual-machine hosting, backup, object repositories and data archives generate very different I/O profiles.

Before selecting an architecture, we analyse areas such as:

  • IOPS,
  • throughput,
  • latency,
  • read/write ratio,
  • typical I/O sizes,
  • required capacity,
  • data growth rate,
  • infrastructure behaviour during failures.

The fastest disks cannot compensate for a poorly designed architecture. Storage needs to be designed around the real way data is used.

Data centre networking as part of the architecture

In hosting environments, networking connects every other layer — compute, storage, backup, Internet access, firewalls and communication between locations.

The design can include:

  • virtualisation host networks,
  • storage networks,
  • VLANs and segmentation,
  • link aggregation and redundancy,
  • routing,
  • firewalls,
  • data-centre interconnects,
  • management and out-of-band networks.

Depending on requirements, we use technologies such as Fortinet and MikroTik.

High Availability without single points of failure

In a data centre environment, High Availability should be analysed across several layers at the same time.

Compute

Failure of a single host should not result in prolonged downtime for critical workloads.

Storage

Data should not depend on a single disk, controller or storage device when the required availability level does not permit it.

Network

Redundancy of network links and devices should reflect the actual availability requirements of the services.

Hardware redundancy alone is not enough. Failure scenarios also need to be tested, with a clear understanding of what happens after losing a particular host, switch, link, storage system or entire location.

Backup as a separate protection layer

Storage replication, RAID and HA clustering do not replace backup.

We design Backup and Disaster Recovery so that data copies remain independent from production infrastructure and can also be used after administrative errors, accidental deletion or security incidents.

Depending on the environment, we use technologies such as Veeam as well as backup solutions integrated with Proxmox.

Local Backup

A fast recovery layer for common failure scenarios and accidental data loss.

Off-site

Backup copies stored outside the primary production environment or in a second location.

Disaster Recovery

Procedures for restoring infrastructure and services after a major failure affecting multiple components.

Backup protects data. Disaster Recovery defines how to use that data to rebuild a working service.

Multi-site environments and a second data centre

A second location can serve as a backup layer, a Disaster Recovery site or an active component of the production architecture.

When designing multi-site environments, we analyse:

  • bandwidth and latency between locations,
  • data replication model,
  • network dependencies,
  • DNS and traffic routing,
  • RPO and RTO,
  • failover and failback,
  • backup outside the primary failure domain.

A second data centre does not automatically improve availability if both environments still depend on the same shared infrastructure component.

Monitoring hosting infrastructure

The larger the infrastructure becomes, the less effective manual status checking becomes.

We build centralised monitoring based on technologies such as Zabbix, covering servers, storage, networking and customer-facing services.

Monitoring can include:

  • host availability,
  • CPU and memory utilisation,
  • disk and RAID status,
  • Ceph and its components,
  • network throughput,
  • switch ports and interfaces,
  • temperature and hardware sensors,
  • backup jobs,
  • TLS certificates,
  • customer-facing services.

Monitoring should answer not only “is the server running?” but also “is the infrastructure still operating within the parameters we expect?”.

Cybersecurity for data centre infrastructure

Hosting-provider infrastructure often has privileged access to a large number of customer systems and data. Its security therefore needs to be designed at both administrative and operational levels.

The scope can include:

  • management-network segmentation,
  • restricted administrative access,
  • VPN and MFA,
  • central identity management,
  • administrative activity logging,
  • security monitoring,
  • protection of backup systems,
  • access control for management interfaces.

For centralised security monitoring and event analysis, we use technologies such as Wazuh.

Migrations are more than moving individual VMs

Migrating a hosting platform requires much more than moving virtual machines from one hypervisor to another.

The project may also need to account for:

  • customer networks,
  • IP addressing,
  • VLANs,
  • storage,
  • backup,
  • monitoring systems,
  • firewalls,
  • integrations and automation,
  • maintenance windows,
  • rollback planning.

We therefore treat migration as an infrastructure architecture project rather than a single technical operation.

Scaling without constantly rebuilding the environment

Hosting infrastructure should have a defined scaling model. Adding more hosts or storage capacity should not require redesigning the environment from the beginning every time.

During architecture design, it is worth defining:

  • target cluster size,
  • storage expansion model,
  • network port and bandwidth headroom,
  • addressing model,
  • capacity for future workloads,
  • thresholds that trigger expansion of individual infrastructure layers.

Good infrastructure does not only work today. It also has a predictable path for growth tomorrow.

Supporting the existing infrastructure team

Hosting providers and data centres usually already have their own administrators and infrastructure engineers. Our role does not need to be replacing that team.

We can participate in projects that require additional expertise or an independent view of the existing architecture.

New Architecture

Design of clusters, storage, networking, backup or a complete infrastructure platform.

Modernisation

Assessment of the current platform and planning changes that reduce bottlenecks, risk or dependency on ageing technology.

Technical Problem

Analysis of performance, failures, storage, networking, backup, monitoring or cluster behaviour.

When can we be a good fit?

Working with sLogic Group may be particularly useful when:

  • you are building a new virtualisation cluster,
  • you are modernising a hosting platform,
  • you are evaluating Proxmox as an alternative to the current hypervisor,
  • you need Ceph or another distributed storage architecture,
  • your existing infrastructure is reaching performance or capacity limits,
  • you are designing a second location or Disaster Recovery environment,
  • you want to improve backup and monitoring,
  • you need an independent assessment of the current architecture.

How do we work?

01. Environment Assessment

We analyse the existing infrastructure, services, workloads, limitations and planned growth.

02. Architecture

We design compute, storage, networking, backup, security and monitoring as cooperating layers of one environment.

03. Implementation and Migration

We introduce changes in stages, test the environment and prepare it for ongoing operations and future expansion.

If the infrastructure is already complex and needs to be structured before the next modernisation project, we can start with an IT Audit and Architecture.

Infrastructure designed as one system

In a hosting environment, virtualisation cannot be separated from storage, storage from networking, or availability from backup and monitoring.

This is why we look at infrastructure as one system — from physical servers and networking to virtualisation, data protection and recovery procedures.

Larger projects are delivered as part of our Infrastructure and Private Cloud services.

Developing a hosting platform or data centre infrastructure?

We can assess your current environment and help design virtualisation, storage, networking, backup and monitoring architecture aligned with the future growth of your services.

Discuss your infrastructure