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
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.
Illustrative sample — a conceptual path, not a live system status.
The recovery question
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 depends on the systems and workloads included in the agreed Excelytech service scope.
Servers and hosts that run core business workloads on dedicated hardware.
Virtual machines and related workloads where virtualization is part of the environment.
Operating systems commonly found in mixed business infrastructures, where supported.
Application data and storage volumes that need a clear path back to usable state.
How it works
A simplified view of how protection moves toward a usable restore path.
Illustrative sequence — actual steps depend on the environment and agreed service scope.
Recovery paths
Available restore options depend on the protected systems, the backup method in use, and the agreed service scope.
Restore selected files or folders from an available recovery point where supported.
Recover a volume when broader data sets need to return together, where supported.
Restore a system image to return a machine toward an earlier operating state, where supported.
Recover a physical system into a virtual environment when that path is supported for the workload.
Recover a virtual system onto physical hardware where the environment and tooling support it.
Use recovery imagery to support planned moves between systems, where supported and agreed in scope.
Verification
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
Where backup copies are stored depends on your environment and agreement. Not every destination is appropriate—or included—for every customer.
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
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.
Service philosophy
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.
Ontario and Canada
Excelytech is based in Mississauga and provides on-premises backup and restore to businesses across the GTA, the rest of Ontario, Canada and the United States. The service is delivered remotely in Eastern Time, and the scope is written into your agreement: what is protected, how often, how long copies are kept and who performs the restore.
We partner with Arcserve, and the supporting software sits underneath the service. You deal with our team, not with a product console and a support queue.
Questions to ask any backup provider
A useful rule of thumb
A long-standing guideline is to keep three copies of important data, on two kinds of storage, with one copy somewhere else. It is a starting point, not a guarantee.
The live data plus at least two backups, so a single failed disk or deleted file is never the end of the story.
Copies on different types of storage, so one failure mode does not take out every copy.
At least one copy that a fire, flood, theft or an attack on your network cannot reach or alter.
The Canadian Centre for Cyber Security recommends backing up systems that hold essential business information, keeping backups encrypted, keeping long-term backups offline at a secure offsite location where possible, and documenting and regularly verifying restore procedures. We build the plan around those ideas.
Local pages
If you want to see how we apply this in your part of the region, these pages cover the typical systems, risks and obligations in each area: Mississauga, Brampton, Toronto, Oakville, Burlington, Hamilton, Vaughan, Markham. The full list is on our areas we serve page.
Start with a conversation
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
Frequently asked questions
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.
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.
The agreed service scope records which systems and workloads are covered, which recovery activities are included, and who is responsible for each agreed task.
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.
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.
It depends on how many systems you protect, how much data they hold, how long copies are kept, where the copies live and how often restores are tested. We scope each environment and put the service and its price in writing, so you can see what is included before you commit.
It is a guideline: keep three copies of important data, on two different kinds of storage, with one copy kept somewhere else. It is a useful starting point, but the plan still needs encryption, a protected copy that an attack cannot alter, and restore tests.
Yes. We are based in Mississauga and serve Toronto, Brampton, Oakville, Burlington, Hamilton, Vaughan, Markham and the rest of the GTA remotely in Eastern Time, as well as businesses elsewhere in Canada and in the United States.
Retention depends on your business and any legal or contractual requirements. For example, the Canada Revenue Agency says businesses should keep records for six years from the end of the last tax year they relate to. We agree retention with you and write it into the service agreement.
On a schedule you can rely on, and after any major change to your systems. The Canadian Centre for Cyber Security recommends documenting restore procedures and regularly verifying that backup and restore processes work. We agree a testing cadence with you.