Infrastructure Engineered for Multi-Country Scale
Networks, virtualization, identity, and storage designed for resilience across multi-site, multi-country footprints — 79+ locations, 99.7% sustained uptime, and a deployment model where shipping at 2 AM is uneventful because it was rehearsed.
The Approach
Multi-country IT estates collect debt the way old buildings collect wiring. Every acquisition brings its own datacenter, its own naming convention, its own escape hatch. Five years in, nobody can explain why the Sofia office talks to the Limassol office through Frankfurt, or why three different hypervisors are in production, or why uptime is calculated differently in each country.
My role is to make the estate one estate. That means a deliberate network topology — SD-WAN where it earns its place, dedicated paths where it does not — virtualization standardized on platforms the team can actually operate, identity and storage with explicit RTOs and RPOs, and a deployment model where production change is a routine event, not a crisis.
The output is measurable: 99.7% sustained uptime across 79+ locations, deploys that ship during business hours because they are boring, and a runbook every on-call engineer can execute under pressure. Infrastructure becomes invisible — which is exactly the point.
Capabilities In Scope
-
Multi-Site Datacenter Design
Active-active or active-passive topologies with explicit RTO/RPO targets, capacity planning honest about the next five years.
-
Cross-Border Networking
SD-WAN, MPLS, IPSec, BGP — the right mix per route. Latency budgets respected, failover tested in production, not in a slide.
-
Virtualization Platforms
VMware and Hyper-V standardized across estates — clusters sized for real workloads, HA/DRS configured, host hygiene enforced.
-
Storage & Backup Architecture
Tiered storage matched to workload IOPS, immutable backups, geo-redundant copies, restores rehearsed quarterly.
-
Directory & Identity Plumbing
Active Directory and Entra ID hybrid done right — sites, replication, group strategy, and a tier model that survives M&A.
-
Perimeter & Segmentation
FortiGate, Cisco, micro-segmentation, and policy that matches the actual data flows of the business.
-
Observability & SLOs
Metrics, logs, and traces that surface trouble before users do. SLOs that align with how the business measures itself.
-
Zero-Downtime Deployment
Blue/green and canary patterns brought into the infrastructure layer. Change becomes routine, not an incident waiting.
Engagement Roadmap
-
01
Estate Survey
Inventory every site, link, host, store, and identity. Establish ground truth — nothing gets designed against assumptions.
-
02
Target Topology
Network, virtualization, identity, storage, and security baselines designed against business RTO/RPO and growth plans.
-
03
Migration Waves
Sequenced site-by-site or workload-by-workload, with backout paths. Every wave validated before the next begins.
-
04
HA & Failover Testing
Live failover exercises across regions — not scheduled by the calendar, but by an unannounced fire drill the team passes.
-
05
Observability Rollout
Metrics, logs, traces, dashboards, and on-call rotations wired before the platform is declared production-grade.
-
06
Operational Handover
Runbooks, change-management discipline, capacity planning cadence, and the internal training that keeps the lights on.
Measurable Impact
Numbers from real engagements in this domain.
-
0
Sustained Uptime
Across 79+ locations after migration to the new topology.
-
0
Office Locations
Managed under a single architecture, naming, and observability standard.
-
0
Countries in Scope
EU jurisdictions consolidated into one operating model.
-
0
Mean Deployment Window
Production change executed without scheduled downtime, measured per release.
Stack & Tooling
- VMware
- Hyper-V
- SD-WAN
- Cisco
- FortiGate
- Windows Server
- Linux
- Active Directory
- Veeam
- PRTG
- Zabbix
- Grafana
Let's Talk IT Infrastructure
Tell me the constraint, the timeline, and the outcome. I respond personally within 24 hours.