Service · Relocations and migrations
Server relocations and migrations.
Relocating premises, reorganising the server room, switching to a new provider, repatriating from the cloud: the trasloco server is a critical operation that requires meticulous planning to minimize downtime. We manage it methodically: audit of the existing setup, verified full backup, transfer plan with an agreed window, network and identity reconfiguration, testing and go-live.
02 / Types of server relocation
Types of server relocation
- Physical relocation (P2P) · same machine, new site or new rack. Disassembly, transport, reassembly, recabling, testing
- Hardware replacement (P2P refresh) · new server, data and configurations preserved. Reinstallation + restore
- P2V migration (Physical to Virtual) · from a legacy physical server to a VM on a new cluster
- V2V migration (Virtual to Virtual) · cambio hypervisor (es. ESXi → Proxmox VE, or VMware → Hyper-V)
- V2C migration (Virtual to Cloud) · from your data center to Azure/AWS/GCP
- C2V repatriation (Cloud to Virtual on-prem) · return on-premise for cost control or compliance
03 / Our relocation method
Our relocation method
- 1. Infrastructure audithardware, software, license inventory, application dependencies, acceptable RPO/RTO
- 2. Relocation plan: timeline, roles, downtime windows, rollback strategy, user communication
- 3. Full backup: full + incremental backup + restore test before touching anything
- 4. Destination configuration: server pronto e validato prima dello switch (modello rip-and-replace)
- 5. Execution finestra: night/weekend cut-over with real-time monitoring
- 6. Test go-livefunctional smoke tests + load + roll-back if KPIs not met
- 7. Hyper-care: reinforced monitoring for 7-14 days post-go-live
04 / Downtime minimization
Downtime minimization
- Live replication: data replicated in real time to the new server, cut-over of minutes instead of hours
- Incremental snapshots: final synchronisation of deltas only after the bulk copy
- Database mirroring / AlwaysOn AG / streaming replication PostgreSQL
- vMotion / live migration in case of virtual relocation (zero downtime)
- Reduced DNS TTL to 60s in the preceding days for a rapid IP switch
Altri services
Explore the altri services AssistenzaServer.
05 / FAQ
Most frequently asked technical questions about server relocations.
How much downtime for a typical server relocation?+
Physical relocation of stand-alone server: 6-12 hours (dismantling, transport, reassembly, testing). With preliminary live replication: 30 min - 2h of cut-over. P2V migration during relocation: zero downtime during business hours if well planned.
Server relocation between different cities: how do you handle transport?+
For Lombardy: direct transport with certified vehicles, server packed with anti-vibration insulation, and our own technical escort for unloading/installation. Beyond Lombardy: specialized server courier (e.g. Wartner, GLS Pro Express) with €25,000+ insurance.
Cloud → on-premise repatriation (C2V): typical cases?+
Companies that migrated to the cloud 2-3 years ago and whose costs have now grown (egress, storage, reserved compute). Repatriation: cloud VM snapshot → transfer to new on-prem cluster → DNS/firewall switch. Typical savings 40-70% on TCO.
VMware → Proxmox migration post-Broadcom: how?+
Steps: 1) VM and licensing inventory, 2) preliminary full Veeam backup, 3) OVF export from vSphere, 4) import into Proxmox with qm importovf, 5) replacement of VMware Tools with qemu-guest-agent, 6) testing, 7) vSphere decommissioning. Average time for a 20-30 VM cluster: 2-3 weekends.
TB data transfer between sites: bandwidth or physical disk?+
Quick calculation: 100Mbit = ~1TB/day. For 10TB: 10 continuous days. Often it is faster to ship physical disks (e.g. a NAS or enterprise USB 3.0 disk) via express courier = arrival within 24h. Also used by AWS (Snowball) and Azure (Data Box).
Let's talk
Ready to talk with a systems engineer?
You will always be answered by a technician, never a call centre.
02 95 17 550