Backup
Backup and snapshot management
Daily and weekly backups with Veeam, plus point-in-time snapshots before risky changes. Backups are held apart from production storage and restore tests are repeated on a schedule.
- Backup schedule
- Daily & weekly
- Independent of production
- Separate storage
- Rollback in minutes
- Snapshot
- Backup engine
- Veeam
A backup and a snapshot are not the same thing
A snapshot marks the state of a server at a moment in time on the same storage. It is indispensable for operations that must be reversible — version upgrades, patching, configuration changes — because you can return to the previous state within minutes if something breaks.
But a snapshot is not a backup. Because it lives alongside production storage, it is lost together with it in a storage-level failure. A backup is kept on separate storage, and that is where the real protection comes from.
The correct arrangement uses both. Snapshots are a short-term operational safety net; backups protect against long-term and disaster scenarios. Both layers are configured as standard in every EG678 Cloud deployment.
Having backups is not enough on its own. A backup that has never been restore-tested is just a file assumed to work until the moment you need it. Restore scenarios are therefore rehearsed at regular intervals and the results recorded.
- Snapshot: fast rollback, same storage
- Backup: separate storage, disaster protection
- Retention planned per organisation
- Restore tests rehearsed regularly
- Backup traffic runs on the private network, off your internet quota
Features
What the backup layer covers
Scheduled backup calendar
Daily and weekly jobs run in low-traffic windows so the impact on production performance stays limited.
Separate storage target
Backups are never held in the production disk pool, so a storage-level failure cannot propagate to them.
Snapshot management
Snapshots are taken ahead of upgrades and risky changes, and applied within minutes if a rollback is needed.
Job result monitoring
Failed backup jobs raise an alert. A backup plan that has silently stopped running is the most dangerous scenario there is.
Restore assistance
Our team performs restores on request — at single file, single database or full server level.
Retention policy
Retention duration and version count are set according to your sector's regulatory requirements and your data volume.
Comparison
Which one to use when
| Scenario | Snapshot | Backup |
|---|---|---|
| Rolling back an upgrade | Primary choice | Not needed |
| Accidentally deleted file | Works if recent | Primary choice |
| Ransomware | Insufficient | Primary choice |
| Storage failure | Lost with it | Primary choice |
| Historical data request | Limited | Within retention |
FAQ
Frequently asked questions
How long are backups retained?
Retention is agreed with your organisation. A tiered plan — daily backups kept short-term, weekly backups longer — is the common choice. If regulation obliges you to retain data for a set period, the plan is built around that.
How long does a restore take?
It depends on scope. A single file or database usually takes minutes. Restoring a full server takes longer depending on data volume; for critical systems we plan a separate disaster recovery scenario to shorten that window.
Will backups slow my server down?
Jobs are scheduled for low-traffic windows and backup traffic flows over the 10 Gbps private network rather than your internet uplink. Together these keep the impact on production performance limited.
How do you verify that backups work?
Job results are monitored and failures raise alerts. Beyond that, restore scenarios are tested at regular intervals — because the only way to know a backup truly works is to restore it.
Can ransomware encrypt the backups too?
To reduce that risk, backups are not kept anywhere the production server can directly reach. Separate storage and access separation are designed to stop an infection on the production side from reaching the backup copies.
More
Related pages
- Backup EngineVeeam Backup infrastructureVeeam backup integrated with VMware ESXi: image-based consistent capture, application-aware processing and selective file-level restore.
- Disaster RecoveryDisaster recovery planningA disaster recovery plan built on RTO and RPO targets: recovery ordering, a secondary copy at a separate site and regular rehearsals.
- StorageNVMe SSD storage infrastructureNVMe SSD disk pools across every cloud server: low latency, high random access, RAID redundancy and snapshot support. Optimised for database workloads.
Let's plan your infrastructure together
Tell us what you need and we prepare a configuration and pricing specific to you. We don't sell fixed packages; we build the deployment, licensing and backup plan with you.