Protect every virtual machine for the recovery outcome you require.
eEVOS combines virtualisation and data protection in one software environment. Instant recovery, deduplicated network and S3-compatible cloud backup, external backup integration and off-site disaster recovery address different recovery times and failure boundaries.
Use the right protection method for the event.
No single backup mechanism should be expected to deliver the shortest recovery time, long retention, independence from production and complete site recovery at once. eEVOS therefore provides several methods that can be combined.
Instant Backup & Recovery
Creates space-efficient eEVOS-managed recovery points for complete virtual machines. A protected VM can be returned as a whole, while individual-file recovery is available when only selected content is required.
- Designed for backup and whole-VM recovery within seconds
- Minimal additional capacity through shared-block efficiency
- Best suited to recent operational rollback
Network Backup
Transfers unique data to a user-selected NAS server. Scheduling and block-level deduplication reduce repeated traffic and preserve VM recovery points beyond the virtualisation host.
- Whole-VM and file-level recovery
- Automated schedules
- Separate target under the organisation’s control
Cloud Backup
Sends space-efficient VM backups to an S3-compatible cloud or on-premises object-storage service. The target, retention and access model determine the actual level of separation.
- Works with S3-compatible services
- Whole-VM and file-level recovery
- Suitable for geographically separate copies
External Backup
Prepares virtual-machine snapshots in a dedicated location for supported third-party backup or tape workflows. Recovery behaviour and retention remain governed by the external backup product.
Off-Site Disaster Recovery
Transfers protected virtual machines asynchronously to a remote eEVOS location on a schedule or manually. DR combines the remote copy with compute, networking and an operational recovery procedure.
Important distinction: Instant Backup & Recovery is designed for recovery speed. Network Backup, S3-compatible Cloud Backup and off-site DR add different forms of separation. They complement one another rather than forming interchangeable labels for the same copy.
Protection remains close to virtual-machine operations.
Administrators can define targets, select virtual machines, schedule protection and start recovery through the eEVOS interface. The recovery procedure should still validate the application before users are reconnected.
Choose by recovery objective and failure boundary.
| Method | Primary objective | Destination or boundary | Recovery granularity | Operational characteristic |
|---|---|---|---|---|
| Instant Backup & Recovery | Very rapid rollback | eEVOS-managed recovery points | Complete VM or individual files | Designed for recovery within seconds |
| Network Backup | Separate retained VM copy | User-selected NAS server | Complete VM or individual files | Deduplicated transfer and scheduled operation |
| Cloud Backup | Remote backup and retention | S3-compatible object storage | Complete VM or individual files | Target-independent S3-compatible integration |
| External Backup | Integration with existing policy | Third-party backup repository or tape workflow | Depends on the external product | eEVOS prepares VM snapshots for collection |
| Off-Site DR | Recovery after a wider outage | Remote eEVOS location | Protected virtual machines and service workflow | Asynchronous scheduled or manual transfer |
Actual backup duration, recovery time and retained history depend on VM size, changed data, target performance, network bandwidth, schedule and the validated product configuration.
Recover the VM—or only the files that are required.
Whole-VM recovery
Return the protected virtual machine when the operating system, application or complete workload state must be recovered.
- Instant Backup & Recovery for the shortest local return
- Network or Cloud Backup when the source host is not the right boundary
- Off-site DR when the primary environment is unavailable
File-level recovery
Retrieve selected files without restoring an entire workload when the operating system and application remain healthy.
- Available with Instant Backup & Recovery
- Available from Network Backup recovery points
- Available from S3-compatible Cloud Backup recovery points
Transfer unique data instead of repeating complete copies
The backup engine reuses matching data and sends unique content to the selected destination.
Select whole-VM or individual-file recovery
Recovery points expose the appropriate action without requiring a separate command-line workflow.
Combine recovery speed with a meaningful separation boundary.
The appropriate design depends on RPO, RTO, retention, available bandwidth and which system or site failures the organisation needs to survive.
Instant recovery + Network Backup
Use local eEVOS recovery points for rapid operational rollback and a deduplicated NAS copy on a separate system for retained recovery.
Instant recovery + S3-compatible backup
Combine rapid local recovery with remote object storage. Credentials, retention and deletion protection should be separated from production where the target permits it.
Backup history + Off-Site DR
Use retained backup copies for historical recovery and remote eEVOS capacity for the controlled return of virtual machines after a wider outage.
S3 compatibility does not automatically make a backup immutable or air-gapped.
What eEVOS provides
eEVOS can send VM backups to Network Backup and S3-compatible targets and can combine these with rapid local recovery and off-site DR.
- Multiple destination types
- Scheduled protection
- Space-efficient transfer
- Whole-VM and file-level recovery where supported
What the target design must provide
The backup destination determines whether additional controls are available and correctly separated from production.
- Retention and capacity policy
- Independent credentials and restricted deletion rights
- Object lock or immutability when supported and configured
- Monitoring and regular restore tests
Clarify the recovery model before defining schedules.
Is Instant Backup & Recovery a replacement for off-system backup?
No. It is optimised for rapid operational recovery. A Network Backup, S3-compatible copy or another independent backup path provides a different failure boundary.
Can individual files be recovered without restoring the complete VM?
Yes. File-level recovery is available with Instant Backup & Recovery, Network Backup and S3-compatible Cloud Backup.
Does Cloud Backup require AWS?
No. eEVOS works with S3-compatible object-storage targets. Compatibility, endpoint configuration and target-side features must be validated for the selected service.
Does S3 automatically provide immutability?
No. Immutability or object lock depends on the chosen target, account permissions, retention settings and the supported configuration.
Is Disaster Recovery the same as backup?
No. Backup retains recovery points. Disaster Recovery also requires compute, networking, identity, application validation and a procedure for returning the service.
Define the recovery objective before choosing the backup path.
For business customers, system houses and service providers, we can map workloads, RPO, RTO, retention, target systems and site boundaries to a practical eEVOS protection design.