What is the difference between backup and recovery?
Backup creates protected copies of data or systems. Recovery is the work of restoring from an available copy so systems and data can return to a usable state.
Backup & Restore
Protect business data with on-premises backup and recovery.
Image-based backup for on-premises systems, designed around the workloads you need to protect and how you would restore them when something goes wrong.
Which systems are covered, and who does what, is confirmed in your service agreement.
- Source Physical and virtual workloads
- Snapshot Point-in-time capture
- Protected Copy Separate recovery layer
- Restore Point Verified recovery positions
- Recovery Return systems to service
Illustrative sample — a conceptual path, not a live system status.
The recovery question
A backup is only useful when you can recover from it.
Modern environments mix physical systems, virtual workloads, business data, and changing infrastructure. Creating copies alone does not answer how those systems return to service.
Recovery readiness considers recovery points, restore options, system recovery, and verification— within the limits of the agreed service scope. Replication or off-site copies are only included when separately agreed.
Backup is not the outcome. Recovery is.
What we protect
Coverage that matches the systems you run
Coverage depends on the systems and workloads included in the agreed ExcelyTech service scope.
-
01
Physical Systems
Servers and hosts that run core business workloads on dedicated hardware.
-
02
Virtual Environments
Virtual machines and related workloads where virtualization is part of the environment.
-
03
Windows & Linux
Operating systems commonly found in mixed business infrastructures, where supported.
-
04
Business Data & Volumes
Application data and storage volumes that need a clear path back to usable state.
How it works
From protection to recovery
A simplified view of how protection moves toward a usable restore path.
- 01Business Systems
- 02Point-in-Time Protection
- 03Backup Image
- 04Verification & Management
- 05Recovery Point
- 06Restore / Recover
Illustrative sequence — actual steps depend on the environment and agreed service scope.
Recovery paths
Different incidents need different recovery paths.
Available restore options depend on the protected systems, the backup method in use, and the agreed service scope.
-
01
File & Folder Recovery
Restore selected files or folders from an available recovery point where supported.
-
02
Volume Recovery
Recover a volume when broader data sets need to return together, where supported.
-
03
Full System Recovery
Restore a system image to return a machine toward an earlier operating state, where supported.
-
04
Physical-to-Virtual Recovery
Recover a physical system into a virtual environment when that path is supported for the workload.
-
05
Virtual-to-Physical Recovery
Recover a virtual system onto physical hardware where the environment and tooling support it.
-
06
System Migration
Use recovery imagery to support planned moves between systems, where supported and agreed in scope.
Verification
Don't wait for an incident to discover that a backup cannot be used.
Backup-image verification can help establish that recovery points remain usable before they are needed. It is a readiness activity—not a guarantee that every restore will succeed in every circumstance.
Verification activities depend on the agreed service scope and environment.
Copy locations
Discuss where recovery copies should live.
Where backup copies are stored depends on your environment and agreement. Not every destination is appropriate—or included—for every customer.
- Local storage
- Network locations
- Remote servers
- Colocation environments
- Private cloud
- Third-party cloud locations (when agreed)
These are discussion examples only. Off-site replication or cloud copy destinations are not included unless confirmed in your ExcelyTech service agreement.
On-premises focus
Backup protection for business-critical on-premises systems.
ExcelyTech helps you put image-based backup in place for on-premises environments and keep recovery planning part of the conversation—not only whether a job finished once.
Specific activities and responsibilities depend on your service agreement and environment. Continuous monitoring or outsourced backup operations are not implied unless separately agreed.
- 01Backup planning
- 02Backup configuration
- 03Recovery planning
- 04Recovery-point review
- 05Verification activities
- 06Backup-image handling
- 07Restore assistance
- 08Recovery coordination
- 09Status reporting (when included)
Service philosophy
Protection should fit the workload—not force every system into the same model.
Environments differ. Some systems need frequent recovery points; others need careful restore planning. ExcelyTech frames backup around the workload, the operating context, and the recovery questions that matter to the business.
The customer-facing service remains ExcelyTech's. Supporting technology sits beneath the service and does not replace a clear conversation about scope.
Start with a conversation
Your backup strategy should have a recovery plan behind it.
Let's look at what you're protecting, where your recovery points live, and how you would restore critical systems when you need them.
Related services
Continue exploring recovery readiness.
Frequently asked questions
Questions about Backup & Restore
Which systems can be included in backup service?
Physical systems, virtual environments, Windows and Linux workloads, and business data may be discussed. Actual coverage depends on support for the environment and the agreed service scope.
What does the agreed service scope mean?
The agreed service scope records which systems and workloads are covered, which recovery activities are included, and who is responsible for each agreed task.
Does backup verification guarantee every restore will succeed?
No. Backup-image verification can help establish that recovery points remain usable, but it is a readiness activity and not a guarantee that every restore will succeed in every circumstance.
How do RTO and RPO relate to backup planning?
A recovery time objective (RTO) describes the target time to restore a service. A recovery point objective (RPO) describes the point in time to which data recovery is targeted. Both help frame recovery requirements.