Veritas Backup Exec served UK SMB + mid-market well for two decades but most organisations now migrate to Veeam Data Platform as Backup Exec reaches a natural refresh point or as ransomware-recovery demands modernisation. This is the 90-day playbook Servnet runs for UK customers, with the technical gotchas + the realistic timeline.
Why migrate
Modern architecture. Backup Exec's single-server architecture caps at modest scale; Veeam Backup & Replication scales horizontally with repositories, proxies and tape gateways.
Ransomware posture. Immutable repository options (hardened Linux, ReFS with lock, S3 Object Lock) are first-class in Veeam.
Workload breadth. M365, AWS, Azure, GCP, Kubernetes — all supported natively in Veeam.
UK skills market. Far more Veeam-trained engineers than Backup Exec for new hires + cover.
Days 1-14 — Discovery + design
Audit existing Backup Exec estate — protected workloads, retention policy, current repository capacity + utilisation, historic restore frequency.
Identify net-new Veeam repository sizing — Veeam compression + dedup typically reduces capacity needs by 30-50% vs Backup Exec.
Design immutability strategy — hardened Linux repository, Object First Ootbi, AWS S3 Object Lock, or dedicated tape gateway.
License sizing — Veeam Universal Licence (VUL) per workload. Workload count + retention drive total cost.
Days 15-30 — Deploy in parallel
Stand up new Veeam Backup Server (Windows Server 2022 + SQL Server / PostgreSQL).
Deploy backup proxies + repositories.
Connect to immutable target (S3 / Linux / Ootbi).
Pilot backup of 10-20% of workloads — confirm performance + restore.
Days 31-75 — Phased cutover
Move workloads in tier groups — Tier 3 (dev/test) first, then Tier 2 (file shares, email archive), then Tier 1 (production VMs, databases).
Run Backup Exec + Veeam in parallel for 30+ days minimum so you have both restore points during transition.
Each cutover: stop Backup Exec job, run Veeam first full, validate restore.
Days 76-90 — Legacy decommission
Confirm Veeam has full retention coverage matching previous Backup Exec policy.
Stop final Backup Exec jobs. Retain Backup Exec server + storage for 90-180 days minimum for legal-hold restore.
Decommission Backup Exec licences at next renewal. Reallocate storage where possible.
Common gotchas
BEDIA agent uninstall — Backup Exec agents (BEDIA) need clean removal before Veeam agents go on Windows / Linux hosts. Test on pilot machine.
GFS rotation — Backup Exec GFS (Grandfather-Father-Son) translates to Veeam GFS but the syntax differs. Map carefully.
Tape — if you keep tape long-term, map LTO library Backup Exec partitions to Veeam tape gateway pools correctly.
What Servnet does
Servnet runs Backup Exec → Veeam migrations as a defined practice. Typical UK engagement: 90 days end-to-end, fixed-fee, with named project manager + Veeam VMCE-certified engineers.
Engagement includes: licensing procurement (we're a Veeam ProPartner), hardened repository deployment, phased cutover, documentation handover, and 30-day post-migration hypercare.