Veeam backup in Greece: what a proper implementation includes
Published:
Short answer: a proper Veeam implementation is not just an installation. It includes a design around the 3-2-1 rule, a copy that cannot be changed or deleted (immutable) so it withstands ransomware, restore testing and clear licensing. Whatever is missing reduces the backup’s value.
The parts of an implementation
- An inventory of what is protected: servers, virtual machines, Microsoft 365, cloud workloads.
- RPO and RTO targets: how much data you can lose and how long you can be offline.
- 3-2-1 design: three copies, two media, one off-site, with one immutable.
- Security of the backup infrastructure itself: separate credentials, MFA and isolation from the main network.
- Regular restore testing, because a backup that has not been tested is no guarantee.
- Monitoring and failure alerts, so you do not discover the problem when you need it.
Licensing and support
Veeam usually licenses per protected workload, with a subscription that renews. Ask for a quote that states which workloads are covered, for how many years and what support includes.
ITHACA designs and sets up Veeam with the 3-2-1 rule, tests the restore with you and handles renewals and monitoring, with support in Greek.
Frequently asked questions
What is an immutable backup?
A copy that for a set time cannot be changed or deleted, even by an administrator. It protects against ransomware that targets backups.
Does Veeam cover Microsoft 365?
Yes, there is a separate solution for email, OneDrive, SharePoint and Teams.