BACKUP & DISASTER RECOVERY · EDMONTON

Backups Protect Data. Recovery Planning Protects the Business.

Local and off-site backup, Microsoft 365 protection, ransomware-resilient copies, restore testing and documented recovery planning – designed around your critical systems.

Local + off-site copies

Microsoft 365 backup

Recovery testing

RECOVERY CONTROL CENTRE
● READY
Local Backup
AVAILABLE
Off-Site Copy
PROTECTED
Recovery Plan
DOCUMENTED
Microsoft 365
COVERED
Restore Testing
VERIFIED
HOW BUSINESS DATA IS LOST

Data Loss Is Not One Scenario.

A useful backup strategy accounts for technology failure, human error, cyber incidents, cloud data and loss of the physical site.

Hardware Failure

Servers, storage and workstations eventually fail—and data may be trapped with them.

Ransomware

Attackers may encrypt production data and attempt to damage accessible backups.

Accidental Deletion

Files, mailboxes or records can be removed long before anyone notices.

Cloud Account Problems

Microsoft 365 data can be deleted, overwritten, compromised or retained differently than expected.

Site-Level Disaster

Fire, flood, theft or power events can make local systems and local backups unavailable.

Failed or Untested Backup

A successful job report does not prove that the right data can be restored when needed.
PROTECTED-DATA ARCHITECTURE

Multiple Copies. Different Locations. Controlled Access.

The architecture should prevent a single device failure, account compromise or site event from eliminating every recovery option.
01

Production Data

Servers, applications, workstations and Microsoft 365.
02

Local Recovery

Fast-access backup for common file and system restores.

03

Off-Site Protection

Separate cloud or remote copy beyond the production location.
04

Recovery Procedures

Priorities, access, documentation and tested restoration steps.

SEPARATION · ENCRYPTION · MONITORING · RETENTION · TESTING

BACKUP & RECOVERY SERVICES

Protection From the Device to the Cloud.

AlphaIT designs backup around the data, applications and systems the business must be able to recover.

Server & Virtual Machine Backup

Application-aware protection for supported physical and virtual server workloads.

Workstation Backup

Protection for critical endpoint data where information is not centralized elsewhere.

Local Backup Appliances

On-site backup storage designed for faster common restores and local recovery.

Cloud & Off-Site Backup

A separate copy outside the office to protect against site-level incidents.

Microsoft 365 Backup

Independent recovery options for Exchange Online, SharePoint, OneDrive and Teams data.

Disaster Recovery Planning

Documented priorities, dependencies, recovery options, roles and communication.
RECOVERY OBJECTIVES

Two Questions Every Backup Plan Must Answer.

Recovery expectations determine backup frequency, retention, infrastructure, cost and the recovery process.
RECOVERY POINT OBJECTIVE

How Much Recent Data Could the Business Recreate?

This determines how frequently protected systems should be backed up. Different workloads may require different intervals.
RECOVERY TIME OBJECTIVE

How Long Can Each System Remain Unavailable?

This helps prioritize systems and choose realistic recovery methods. Recovery time varies by incident and design.
RANSOMWARE RESILIENCE

Attackers May Target the Backups Too.

A ransomware-aware design separates backup administration and recovery copies from the systems most likely to be compromised.

Separate backup credentials

Restricted administrative access

Backup copies inaccessible from ordinary users

Off-site or isolated copies

Longer retention where appropriate

Recovery path documented before an incident

FROM INCIDENT TO OPERATIONS

Recovery Is a Sequence—not a Restore Button.

A documented process helps teams make controlled decisions when systems, people and time are under pressure.
01

Detect

Confirm what happened and prevent further damage.
02

Contain

Isolate affected systems, accounts or locations.
03

Prioritize

Identify which business services must return first.
04

Restore

Recover clean data and systems using the selected method.
05

Validate

Confirm applications, permissions and data integrity.
06

Resume

Return users to service and document follow-up actions.
OPERATIONAL ASSURANCE

A Backup Job Is Not the Same as a Recovery Capability.

Backup protection needs ongoing attention after the first successful job.
MONITOR & MAINTAIN

Know When Protection Changes

Failures, storage limits, expired credentials and infrastructure changes can quietly reduce coverage.

Job and alert review

Capacity and retention checks

Protected-workload changes

Credential and platform maintenance

TEST & DOCUMENT

Prove the Recovery Path

Testing confirms whether data is usable and whether the documented process still matches the environment.

Sample restore testing

Access and dependency validation

Recovery procedure reviews

Issue tracking and improvement

BACKUP PLATFORMS

Technology Chosen Around the Recovery Requirement.

The correct combination depends on workload type, data size, retention, connectivity, recovery objectives and budget.

Veeam

Server, virtual machine, cloud and Microsoft 365 backup capabilities.

QNAP & Synology

On-site network storage and backup platforms for appropriate environments.

Microsoft 365

Exchange Online, SharePoint, OneDrive and Teams data protection.

Hyper-V & VMware

Image-level protection for virtualized server workloads.

Windows Server

Application-aware backup and file or system recovery.

Cloud Storage

Off-site copy and retention options selected for the recovery design.
FREQUENTLY ASKED QUESTIONS

Questions About Backup & Disaster Recovery

Clear answers before you design, replace or review your business backup system.
Backup creates recoverable copies of data or systems. Disaster recovery defines how prioritized business services will be restored, validated and returned to users after a serious disruption.
Many businesses benefit from both. Local backup can support common restores, while an off-site copy helps protect against theft, fire, site loss and compromise of local infrastructure.
Microsoft provides service availability and native retention capabilities. Businesses may choose independent backup for additional recovery, retention and administrative control.
Frequency should follow how much recent data the business could reasonably recreate. Critical systems may need more frequent protection than lower-priority information.
Backup can provide recovery options after ransomware, but only when copies, credentials and administration are sufficiently separated and protected. It does not replace preventive security.
Monitoring confirms job status; restore testing confirms that selected data can actually be recovered. Both are important.
Recovery time depends on the affected systems, incident scope, data size, available infrastructure, internet connectivity and the recovery design. A realistic objective should be established during planning.
Yes. A review can examine protected workloads, job status, retention, storage, off-site separation, Microsoft 365 coverage, recovery procedures and restore testing.
FREE BACKUP & RECOVERY ASSESSMENT

Would Your Current Backups Survive the Incident You Are Planning For?

We’ll review protected systems, backup locations, Microsoft 365 coverage, retention, ransomware exposure and recovery procedures – and explain the gaps.

780-318-0149 · Edmonton, Alberta