Module 1:

Introduction to Backups
Learning Objectives:

By the end of this module, students will:

• Understand what a backup is and why it’s critical.

• Learn about the history and evolution of backup strategies.

• Recognize key terminology and basic concepts.

• Be able to explain the importance of backup in IT infrastructure.

1.1 What is a Backup?

A backup is a copy of data taken and stored separately to protect

against loss, corruption, or destruction. It allows restoration of original
data in case of events such as hardware failures, software bugs, human
errors, cyberattacks (like ransomware), or natural disasters.

1
1.2 Why Do We Need Backup?

Here are the most critical reasons:

• Data loss prevention: System crashes, theft, or user mistakes.

• Business continuity: Minimizes downtime and allows quick

recovery.

• Legal compliance: Many industries have regulations to retain

certain data.

• Audit and historical tracking: Useful for tracking changes over

time.

2
1.3 Common Scenarios Leading to Backup Use

• A user accidentally deletes a file.

• A hard drive in a server fails unexpectedly.

• Ransomware locks the entire file system.

• A fire destroys on-premise storage.

Tools Commonly Used for Backups:

Tool Name Purpose Type

Windows Backup Basic OS-level backup tool Local backup

Acronis TrueImage Disk cloning + backup Disk-based backup

rsync File-level sync and backup Script-based

Cobian Backup Scheduled backups for Windows GUI + script

Bacula Open-source enterprise backup Server-client

3
Summary Points:

• Backup is essential for data security and business continuity.

• Backups protect against system failure, natural disasters, and

human errors.

• Recovery strategies depend heavily on well-structured backup

practices.

• There are multiple backup types (to be covered in the next

module).

• Tools range from simple OS utilities to enterprise-level platforms.

Review Questions:

Q1. What is the main purpose of taking backups?

Q2. Mention two common reasons why backups fail.
Q3. What are the typical targets for storing backups?
Q4. Name one open-source and one commercial backup tool.
Q5. How does a backup contribute to business continuity?
Q6. Why is backup validation important?

4
Answers:

Q1. What is the main purpose of taking backups?

A1. To ensure data availability and recovery in case of data loss or
system failure.

Q2. Mention two common reasons why backups fail.

A2. Hardware malfunction and insufficient monitoring/logging.

Q3. What are the typical targets for storing backups?

A3. Disks, tapes, cloud storage, and network drives.

Q4. Name one open-source and one commercial backup tool.

A4. Bacula (open-source), Acronis TrueImage (commercial).

Q5. How does a backup contribute to business continuity?

A5. By enabling quick recovery, reducing downtime, and preventing
data loss.

Q6. Why is backup validation important?

A6. To ensure that the backups are usable and not corrupted.

5
Module 2:
What is Backup?
Why Do We Need It?
Learning Objectives:

By the end of this module, students will be able to:

• Define the concept of backup in detail.

• Articulate the necessity of regular backup operations.

• Describe the cost of data loss.

• Understand different business cases that mandate backup

strategies.

2.1 What is a Backup?

A backup is the process of copying and archiving computer data to

ensure it can be restored after a data loss event. It is the cornerstone of
data protection and disaster recovery strategies. It may be:

• Full system images

• Specific file backups

• Application/database-specific backups

“No backup = No recovery.” – It’s that critical.

6
2.2 Characteristics of a Good Backup

1. Integrity – Must be restorable without errors.

2. Frequency – Should meet business RPO/RTO standards.

3. Security – Should be encrypted and access controlled.

4. Redundancy – Should have multiple copies in different locations.

5. Verifiability – Should be testable regularly.

7
2.3 Why We Need Backups

Key scenarios:

A. Hardware Failures:
Hard drives, SSDs, and even cloud infrastructure can fail. Even with
RAID systems, data loss is not uncommon.

B. Human Errors:
Accidental deletion, formatting, or incorrect configuration changes can
lead to data loss.

C. Malware and Ransomware:

Modern ransomware encrypts files and demands payment. Backups are
your escape route.

D. Natural Disasters:
Floods, fires, or earthquakes can wipe out entire data centers.

E. Compliance and Legal Requirements:

Regulations like GDPR, HIPAA, and SOX demand businesses to retain
data for specific durations and ensure recoverability.

F. Business Continuity:
Even short downtimes can lead to revenue loss, reputation damage, and
customer dissatisfaction.

8
9
Common Backup Scenarios & Tools

Scenario Recommended Tool(s) Notes

Windows Server Backup,

Windows File Server File-level backup
Veeam

Scriptable, open-
Linux Production Server rsync, Bacula
source

VMware/Virtualized Veeam Backup &

VM-level backup
Servers Replication, VRanger

Cloud Workloads (AWS, AWS Backup, Azure Cloud-native

Azure) Recovery Vault tools

SQL Server Backup, App-consistent

Business Databases
NetBackup backups

Key Concepts to Understand

• RPO (Recovery Point Objective): How much data can you afford
to lose?

• RTO (Recovery Time Objective): How quickly must the system

be restored?

• 3-2-1 Rule: Keep at least 3 copies of data, on 2 different media,

with 1 copy offsite.

• Backup Validation: Regularly check backups for consistency and

usability.

10
Summary Points

• Backups are essential for data protection, continuity, and

compliance.

• Ignoring backups is risking total data loss.

• The cost of data loss is far greater than the investment in proper
backups.

• RPO and RTO should drive your backup strategy.

• Use tools that support encryption, automation, and verification.

Review Questions with Answers

Q1. What does RTO stand for?.

Q2. What are the two main objectives of backup planning?

Q3. What is the 3-2-1 backup rule?
Q4. How do backups help with compliance?
Q5. Why is backup verification important?
Q6. Name one cloud-native backup tool.

11
Review Questions with Answers

Q1. What does RTO stand for?

A1. Recovery Time Objective – maximum tolerable time to restore
services after a failure.

Q2. What are the two main objectives of backup planning?

A2. Recovery Point Objective (RPO) and Recovery Time Objective
(RTO).

Q3. What is the 3-2-1 backup rule?

A3. 3 copies of data, 2 on different media, 1 offsite.

Q4. How do backups help with compliance?

A4. They provide historical data and support for audits and regulatory
demands.

Q5. Why is backup verification important?

A5. To ensure data is not corrupted and is restorable when needed.

Q6. Name one cloud-native backup tool.

A6. AWS Backup or Azure Recovery Vault.

12
Module 3:
Types of Backups
Learning Objectives:

By the end of this module, students will:

• Understand different types of backup and how they work.

• Identify which backup types are best suited for specific scenarios.

• Analyze trade-offs in terms of speed, storage, and recovery.

• Gain knowledge of practical backup strategies in enterprises.

3.1 Why Do We Need Different Backup Types?

Different scenarios demand different backup approaches depending on:

• Volume of data

• Frequency of changes

• Recovery speed requirement

• Network/storage capacity

Backup types help optimize performance, storage space, and restore

speed.

13
3.2 Major Types of Backup

1. Full Backup

A full backup makes a complete copy of all selected data. It is the most
reliable but time-consuming.

• Pros: Simple recovery, complete image.

• Cons: Large storage required, slower to run.

Example: Full server backup every Sunday night.

2. Incremental Backup

This only backs up data that changed since the last backup (full or
incremental).

• Pros: Saves space and time.

• Cons: Recovery needs multiple files (full + all incrementals).

Example: After Sunday full backup, daily incrementals (Mon–Sat).

3. Differential Backup

This backs up everything changed since the last full backup.

• Pros: Faster restore than incremental.

• Cons: More storage than incremental.

Example: Full backup on Sunday, differential each weekday.

4. Synthetic Full Backup

A synthetic full is created from a previous full backup and subsequent

incremental—without copying from the source again.

• Pros: Less impact on live systems.

• Cons: Requires smart backup software and processing time.

14
5. Mirror Backup

Creates an exact mirror image of source data. Useful for quick swaps or
system replacement.

• Pros: Real-time or near-instant.

• Cons: No versioning; if a file is corrupted/deleted, it’s

mirrored too.

6. Snapshot Backup

Uses storage-level snapshots to freeze and copy the data state instantly.

• Pros: Fast, low impact.

• Cons: Not a long-term backup; mostly for short-term recovery.

15
16
Common Tools Supporting These Backup Types

Synthetic
Tool Name Full Incremental Differential Snapshot
Full

Veeam Backup

Acronis

Windows
Server

(via
rsync (Linux)
flags)

NetBackup

Commvault

17
Summary Points
• Full backup is the baseline but consumes the most resources.

• Incremental is efficient for storage but slowest to restore.

• Differential offers a balance between storage and restore time.

• Synthetic backups reduce source system load.

• Snapshot backups are great for quick rollbacks, not long-term

recovery.

• Choosing the right type depends on your RPO/RTO and

infrastructure capacity.

Review Questions
Q1. What is the key difference between Incremental and Differential
backups?
Q2. Why is full backup important?
Q3. What is a synthetic full backup?
Q4. Which backup method is fastest in terms of recovery?
Q5. Which backup method uses the least storage over time?
Q6. What type of backup is best for critical systems that change
frequently?

Review Questions with Answers

Q1. What is the key difference between Incremental and

Differential backups?
A1. Incremental backs up changes since the last backup, differential
backs up changes since the last full backup.

18
Q2. Why is full backup important?
A2. It captures the complete state of the system/data and is required to
restore incrementals or differentials.

Q3. What is a synthetic full backup?

A3. A backup generated by combining previous full and incremental
backups without accessing the original source.

Q4. Which backup method is fastest in terms of recovery?

A4. Full backups offer the fastest recovery time.

Q5. Which backup method uses the least storage over time?
A5. Incremental backup.

Q6. What type of backup is best for critical systems that change
frequently?
A6. Snapshot or incremental, depending on required restore speed and
RPO.

Perfect. Let’s dive into the next essential concept in the Backup and
Restore course.

19
Module 4:
Backup Targets – Disk / Tapes

Learning Objectives:

By the end of this module, students will:

• Understand the role of storage targets in backup strategies.

• Compare disk-based and tape-based backup solutions.

• Analyze performance, reliability, and cost trade-offs.

• Know when to use which storage type in enterprise

environments.

4.1 What Are Backup Targets?

A backup target is the storage location where backup data is written. It

could be:

• On-premise hardware like hard disks or tape drives.

• Off-site storage like cloud storage or remote servers.

• Hybrid models combining multiple targets.

Choosing the right backup target depends on:

• Size of data

• Speed of backup/restore

• Budget

• Compliance requirements

20
4.2 Disk-Based Backup

Disk-based backup refers to storing backup data on hard drives, SSDs,

or disk arrays.

✅ Advantages:

• Faster backups and restores.

• Supports deduplication and compression.

• Easier integration with software automation.

• Supports random access.

❌ Disadvantages:

• Higher cost per GB than tape.

• Less optimal for long-term storage.

• May require more power, cooling, and space.

Common Disk-Based Storage Types

1. DAS (Direct Attached Storage)

o Directly connected to the backup server.

o Simple and fast but not scalable.

2. NAS (Network Attached Storage)

o Shared file-based storage over the network.

o Accessible to multiple systems.

3. SAN (Storage Area Network)

o Block-level, high-speed access.

o Expensive but high performance and scalable.

21
4.3 Tape-Based Backup

Tapes are magnetic media used to write backups in sequential format,

typically through LTO (Linear Tape-Open) technologies.

✅ Advantages:

• Extremely cost-effective for long-term storage.

• Tapes can be stored offsite (air-gapped).

• High durability—data retention for 30+ years.

❌ Disadvantages:

• Slower access time.

• Sequential data access (not random).

• Manual intervention for rotation/offloading.

LTO Tape Generations

Generation Capacity (Uncompressed) Speed Released

LTO-5 1.5 TB 140 MB/s 2010

LTO-6 2.5 TB 160 MB/s 2012

LTO-7 6.0 TB 300 MB/s 2015

LTO-8 12.0 TB 360 MB/s 2017

LTO-9 18.0 TB 400 MB/s 2021

22
23
24
4.4 When to Use Disk or Tape

Recommended
Use Case
Target

Fast restores, short-term retention Disk

Long-term archival (5–30 years) Tape

Air-gapped offline storage Tape

Cloud-integrated backup gateways Disk/NAS

Very large datasets (petabytes) Tape libraries

Frequent, quick test restores Disk

4.5 Tools That Support Both Disk & Tape

Disk
Tool Tape Support Notes
Support

Veeam (with Supports D2D2T

Backup integration) architecture

NetBackup Robust enterprise support

Can automate both

CommVault
workflows

Open-source, Linux-
Bacula
friendly

Optimized for tape

IBM TSM
environments

25
Summary Points

• Backup targets define where your backup data is stored.

• Disk backups are faster and suited for short-term or frequent use.

• Tape backups are slower but excellent for archival and cost
efficiency.

• A hybrid strategy (Disk-to-Disk-to-Tape) is ideal in many

enterprise setups.

• Tape remains relevant, especially for compliance-heavy

environments.

Review Questions with Answers

Q1. What are the three main types of disk-based storage?

Q2. Name two advantages of tape-based backup.
Q3. Which backup target allows random access to files?
Q4. What does LTO stand for?
Q5. Why are tapes preferred for archival storage?
Q6. What is the role of hybrid backup models?

26
Review Questions with Answers

Q1. What are the three main types of disk-based storage?

A1. DAS (Direct Attached Storage), NAS (Network Attached Storage),
SAN (Storage Area Network).

Q2. Name two advantages of tape-based backup.

A2. Low cost for long-term storage and durability over decades.

Q3. Which backup target allows random access to files?

A3. Disk-based backup.

Q4. What does LTO stand for?

A4. Linear Tape-Open – an open-format magnetic tape data storage
technology.

Q5. Why are tapes preferred for archival storage?

A5. Because of their long lifespan, low cost, and portability.

Q6. What is the role of hybrid backup models?

A6. To combine speed (disk) and longevity (tape) for efficient, cost-
effective backups.

27
Module 5:
Overview of
Basic Disk and Deduplication
Learning Objectives:

By the end of this module, students will:

• Understand what disk-based backup systems are and how they

work.

• Learn the concept and mechanics of data deduplication.

• Distinguish types of deduplication and their use cases.

• Evaluate disk storage efficiency and optimization techniques in

backups.

5.1 Disk-Based Backup Systems – A Quick Recap

Disk-based backup refers to using hard drives, SSDs, or arrays as

backup storage. They are commonly deployed in the following forms:

• Standalone disks (internal/external)

• RAID arrays (for redundancy and speed)

• NAS/SAN appliances

• Virtual backup appliances (software-defined)

Disk-based systems are fast and flexible, support automation, and allow
efficient integration with backup software.

28
5.2 Storage Efficiency Challenges

Disk-based systems face challenges:

• High data redundancy (multiple copies of same data).

• Limited disk space (especially in SMBs).

• Rising storage costs with data growth.

• Inefficient backup cycles without optimization.

That’s where deduplication comes in.

5.3 What is Deduplication?

Deduplication is the process of identifying and eliminating duplicate

data blocks or files during backup. Instead of storing every copy of the
same file, only one copy is retained and referenced.

“Why store the same email attachment 10 times when it can be stored
once?”

29
5.4 Types of Deduplication

1. File-level (Single-instance storage)

• Identifies duplicates based on file hash (e.g., MD5, SHA-1).

• Stores only one copy of identical files.

• Efficient but limited when changes are within files.

2. Block-level Deduplication

• Breaks files into chunks or blocks (fixed or variable).

• Identifies and stores only unique blocks.

• Superior granularity and storage savings.

Fixed vs Variable Block Sizes

Type Description Use Case

Splits data into equal-sized Simpler, faster

Fixed-size
blocks processing

Variable- Splits based on content Higher deduplication

size structure ratio

5.5 Where Does Deduplication Occur?

1. Source Deduplication

• Done on the client-side before sending data to the backup server.

• Reduces bandwidth usage.

• Higher load on client CPU.

30
2. Target Deduplication

• Performed on the backup server or appliance.

• Offloads processing from client.

• May consume storage bandwidth and I/O.

31
5.6 Compression vs Deduplication

Feature Compression Deduplication

Reduces size by removing Removes duplicate data

Operation
redundancy blocks

Across multiple
Scope Within a file
files/backups

Speed Fast Slower (but more efficient)

Saving space on individual

Use Case Optimizing backup storage
files

32
5.7 Real-World Examples

Deduplication
Vendor/Product Notes
Support

Target-side via repository

Veeam Block-level
configuration

Dell EMC Data Purpose-built backup

Advanced
Domain appliance

Enterprise-grade
Veritas NetBackup Both
performance

Works with cloud and disk

CommVault Adaptive dedup
storage

Built-in for some editions

Windows Server File dedup
(NTFS only)

5.8 Benefits of Deduplication

• Reduces disk usage by up to 90%.

• Decreases network load (for source dedup).

• Enables longer retention policies.

• Reduces backup windows and storage costs.

• Supports efficient replication.

5.9 Limitations of Deduplication

• CPU/Memory intensive during processing.

• Not ideal for encrypted or compressed data (low deduplication

ratio).

33
 • Deduplication databases require maintenance.

• Data corruption can have wider consequences if not carefully

managed.

Summary Points

• Disk backups are common due to speed and automation

flexibility.

• Deduplication is critical for reducing storage cost and enhancing

performance.

• File-level dedup is simpler; block-level offers deeper savings.

• Source dedup saves bandwidth; target dedup is easier to manage

centrally.

• Many modern backup tools offer built-in deduplication features.

Review Questions with Answers

Q1. What is data deduplication?

Q2. Which deduplication type breaks files into chunks?
Q3. Where does source deduplication happen?
Q4. Name one limitation of deduplication.
Q5. What’s the key difference between compression and deduplication?
Q6. Give one example of a deduplication-enabled backup product.

34
Review Questions with Answers

Q1. What is data deduplication?

A1. The process of identifying and eliminating duplicate data to save
storage.

Q2. Which deduplication type breaks files into chunks?

A2. Block-level deduplication.

Q3. Where does source deduplication happen?

A3. At the client side, before transmitting data to the backup server.

Q4. Name one limitation of deduplication.

A4. It is ineffective on encrypted or compressed files.

Q5. What’s the key difference between compression and

deduplication?
A5. Compression removes redundancy within a file; deduplication
removes duplicates across files or datasets.

Q6. Give one example of a deduplication-enabled backup product.

A6. Dell EMC Data Domain or Veeam Backup.

35
Module 6:
Overview of Cloud / NAS Storage
Learning Objectives:

By the end of this module, students will:

• Understand the role of Cloud Storage and NAS (Network

Attached Storage) in backup infrastructure.

• Compare performance, reliability, and cost benefits of each.

• Learn integration approaches for backup software.

• Identify use cases, advantages, and challenges of using these

storage systems.

6.1 What is Cloud Storage in Backup?

Cloud storage refers to storing data on off-site remote servers,

accessed over the internet. These services are maintained by cloud
providers like AWS, Azure, Google Cloud, etc.

In backup systems, cloud storage is often used for:

• Offsite replication
• Long-term archival
• Disaster recovery (DR) sites

36
6.2 Cloud Storage Models:

Type Description Example

Object Data stored as objects with Amazon S3, Azure

Storage metadata & ID Blob Storage

Block Raw storage volumes for virtual

AWS EBS, Azure Disks
Storage machines

Shared file systems accessed via Amazon EFS, Azure

File Storage
protocols (SMB) Files

6.3 What is NAS (Network Attached Storage)?

NAS is a dedicated file storage system connected to a network, enabling

multiple users and client devices to retrieve data from a centralized disk
capacity.

It’s often used for:

• On-premise shared backups

• Small to medium business (SMB) environments

• Fast LAN-based recovery systems

37
 NAS Advantages:

• Easy integration with most backup software.

• Uses common file protocols: NFS, SMB, FTP.

• Accessible across LAN/WAN.

• Ideal for local backups and quick restores.

NAS Limitations:

• Performance is limited to network throughput.

• Vulnerable to ransomware if not isolated.

• Not suitable for massive-scale offsite storage.

6.4 Cloud vs NAS Backup Storage:

Feature Cloud Storage NAS

Access Type Internet LAN

Limited to hardware
Scalability Virtually unlimited
capacity

38
Feature Cloud Storage NAS

Upfront cost +
Cost Structure Pay-as-you-go
maintenance

Slower (depends on
Backup Speed Faster (LAN speeds)
bandwidth)

Disaster Local only unless

Excellent
Recovery replicated

Data
May be cross-border Remains on-premises
Sovereignty

6.5 Cloud Backup Tiers:

Cloud Tier Purpose Example (AWS) Cost

Hot Storage Frequent access S3 Standard High

Warm S3 Infrequent
Occasional access Moderate
Storage Access

Cold Storage Rarely accessed Glacier Low

Archival access Glacier Deep

Deep Archive Lowest
(days/weeks) Archive

39
40
6.6 Tools That Support Cloud / NAS:

NAS
Tool Cloud Integration Notes
Support

AWS, Azure, Native integration,

Veeam Backup
Google, Wasabi backup tiers

Cloud via Acronis

Acronis Unified platform
Cloud or others

Enterprise-grade
Commvault Multi-cloud backup
support

MSP360 AWS, Azure, GCP,

Affordable for SMBs
(CloudBerry) Backblaze B2

(built-in AWS Glacier, Ideal for NAS/cloud

Synology DSM
NAS OS) Dropbox, etc. backup automation

6.7 Security Considerations:

Cloud Backup:

• Encryption at rest and in transit.

• IAM and Role-based access.

• Use Multi-Factor Authentication (MFA).

• Audit logs, versioning, and object lock (for ransomware

protection).

41
NAS Backup:

• Regular OS and firmware patching.

• Enforce strong ACLs and SMB/NFS authentication.

• Segmentation from public networks.

• Snapshots + replication for quick recovery.

6.8 Challenges:

Challenge Cloud NAS

Bandwidth limits Large datasets over WAN LAN bottlenecks possible

Access control Requires strict IAM Risk of open shares

Ransomware Cloud: lower risk NAS: high if exposed

Vendor lock-in Proprietary storage APIs Limited to appliance OS

Summary Points

• Cloud storage enables scalable, offsite, and long-term backup

strategies.

• NAS is ideal for local, fast-access backup and recovery.

• Use tiered storage in the cloud to optimize costs.

• Security, access control, and bandwidth are key considerations.

• Backup software can seamlessly integrate with both types.

42
Review Questions with Answers

Q1. What is the main protocol used by NAS devices for file sharing?
Q2. What is the difference between Hot and Cold storage in cloud?
Q3. Name one advantage of cloud storage in backup.
Q4. What is a typical use case for NAS in backup systems?
Q5. List one tool that integrates with both NAS and Cloud.
Q6. Why is security important in NAS environments?

43
Review Questions with Answers:

Q1. What is the main protocol used by NAS devices for file sharing?
A1. SMB or NFS.

Q2. What is the difference between Hot and Cold storage in cloud?
A2. Hot storage is for frequent access, cold is for rarely accessed data at
a lower cost.

Q3. Name one advantage of cloud storage in backup.

A3. It offers virtually unlimited scalability and offsite disaster recovery.

Q4. What is a typical use case for NAS in backup systems?

A4. Fast, on-premise backups and recovery for local systems.

Q5. List one tool that integrates with both NAS and Cloud.
A5. Veeam Backup or Commvault.

Q6. Why is security important in NAS environments?

A6. Because NAS is susceptible to ransomware attacks if not properly
secured.

44
Module 7:
Volume Shadow Copy
Service (VSS) for Backups
Learning Objectives:

By the end of this module, students will:

• Understand what Volume Shadow Copy Service (VSS) is and why

it's important.

• Learn how VSS enables backups of active files and applications.

• Explore how VSS integrates with backup tools.

• Understand VSS components, workflow, and troubleshooting

basics.

7.1 What is Volume Shadow Copy Service (VSS)?

VSS is a Windows service that allows backup applications to create

consistent snapshots (or shadow copies) of data, even when it is in
use.

It was introduced in Windows Server 2003 and is widely used for:

• File-level backups

• Application-aware backups (e.g., Exchange, SQL Server)

• VM-level backups with Windows guests

Use Case: Backing up an open MS Word file or a running SQL database

without shutting them down.

45
7.2 Why VSS is Critical

• Without VSS, backing up files in use would result in incomplete

or corrupt backups.

• VSS coordinates between applications, file systems, and backup

tools to ensure point-in-time consistency.

7.3 Core VSS Components

Component Description

VSS The backup application that initiates the snapshot (e.g.,

Requester Veeam, Acronis).

Application component that prepares data for backup

VSS Writer
(e.g., SQL Writer).

The service or driver that creates the snapshot (usually

VSS Provider
Microsoft's provider).

46
7.4 VSS Process Flow

1. Backup starts.

2. Requester tells Writers to prepare for snapshot.

3. Writers flush data (e.g., cache, memory) and freeze writes.

4. Provider creates a snapshot.

5. Writers resume operations.

6. Requester reads data from the snapshot and stores it.

7. Snapshot is deleted after completion.

47
7.5 VSS Writers and Applications

Application VSS Writer Name

Microsoft SQL Server SQLServerWriter

Microsoft Exchange Exchange Writer

SharePoint SPSearch4 VSS Writer

Hyper-V Hyper-V IC Writer

Windows Registry Registry Writer

Use vssadmin list writers command to view current writers and their
state.

7.6 Common Tools Supporting VSS

Tool/Platform VSS Integration Notes

Veeam Backup & Uses VSS for consistent VM +

Yes
Rep. app backups

Acronis Cyber File + Disk-level backup with

Yes
Protect VSS

48
Tool/Platform VSS Integration Notes

Windows Server
Built-in Native tool using VSS
Backup

Enterprise-
Commvault Supports custom VSS writers
grade

Integrates with Exchange, SQL,

Veritas Backup Exec Yes
AD, etc.

7.7 VSS Snapshot Types

Type Description

Remains after system reboot (used in rollback

Persistent
scenarios)

Non-
Temporary snapshot used during backup only
persistent

Most backup operations use non-persistent snapshots.

7.8 Common VSS Issues and Troubleshooting

Symptom Possible Cause Fix

Writer "Waiting for App freeze or time- Restart VSS service or

completion" out related app

Storage volume full

Snapshot creation fails Check disk space and retry
or in use

Writer not
Backup is inconsistent Re-register VSS writer
registered

Snapshot deleted Snapshot lifespan Increase snapshot timeout

before backup exceeded in backup settings

49
Summary Points

• VSS enables reliable backups of live/locked files.

• It uses a requester–writer–provider model to coordinate backup.

• Key Windows applications register VSS writers for consistency.

• Most major backup tools support VSS integration.

• Basic VSS health can be checked using vssadmin list commands.

Review Questions with Answers

Q1. What is the purpose of VSS in backups?

Q2. Name the three core VSS components.
Q3. What command lists all registered VSS writers?
Q4. What happens if a VSS writer is not stable?
Q5. Name one backup tool that relies on VSS for application consistency.
Q6. What is the difference between persistent and non-persistent
snapshots?

50
Review Questions with Answers

Q1. What is the purpose of VSS in backups?

A1. To create consistent snapshots of in-use files or applications for
backup without downtime.

Q2. Name the three core VSS components.

A2. VSS Requester, VSS Writer, and VSS Provider.

Q3. What command lists all registered VSS writers?

A3. vssadmin list writers

Q4. What happens if a VSS writer is not stable?

A4. Backups may fail or be inconsistent; the writer needs to be restarted
or re-registered.

Q5. Name one backup tool that relies on VSS for application
consistency.
A5. Veeam Backup & Replication.

Q6. What is the difference between persistent and non-persistent

snapshots?

A6. Persistent remain after reboot; non-persistent are temporary and

deleted post-backup.

51
Module 8:
Introduction to
TSM / NetBackup / Backup Exec /
Networker / CommVault
Learning Objectives:

By the end of this module, students will:

• Gain a foundational understanding of leading enterprise backup tools.

• Compare features, strengths, and ideal use cases of each.
• Learn architectural basics and supported environments.
• Understand licensing, deployment models, and real-world scenarios.

8.1 Why Multiple Tools Exist

Enterprises have diverse needs:

• Heterogeneous environments (Windows, Linux, VMware, databases).

• Complex compliance, SLAs, and retention policies.
• Budgetary constraints and preferences.
Hence, no one-size-fits-all solution—multiple enterprise-grade tools
exist.

8.2 IBM TSM (Tivoli Storage Manager / Spectrum Protect)

Overview:

• Developed by IBM.
• Now branded as IBM Spectrum Protect.
• Focus on policy-based, scalable backup.

52
Features:

• Centralized management of thousands of clients.

• Supports incremental forever backups.
• Tape, disk, cloud storage options.
• Advanced deduplication and compression.

Architecture:

• Client–Server model.
• Data moved to storage pools.
• Tight integration with IBM storage hardware.

8.3 Veritas NetBackup

Overview:

• Enterprise-grade backup solution by Veritas.

• Focused on high scalability and cross-platform support.

53
Features:

• Supports VMware, Hyper-V, Oracle, SQL, SAP, cloud platforms.

• Deduplication with NetBackup Appliances.
• Intelligent workload-aware policies.
• DR automation and cloud-tiering.

Architecture:

• Master server, media server, clients.

• Optional appliance-based deployments.
• REST API, web UI, CLI support.

8.4 Veritas Backup Exec

Overview:

• More SMB-focused than NetBackup.

• Windows-centric, easy GUI setup.

Features:

• VM-level backup with granular restore.

• Exchange, SQL, SharePoint support.
• Tape/disk/cloud hybrid support.
• Instant recovery and integrated VSS.

54
Architecture:

• Single-server install.
• Add agents for apps or remote systems.

8.5 Dell EMC NetWorker

Overview:

• Formerly Legato NetWorker.

• Strong Linux/Unix support and centralized management.

Features:

• Parallel streaming backups.

• Cloud tiering and long-term retention.
• Snapshot management.
• Integrates with Data Domain for deduplication.

Architecture:

• NetWorker Server → Clients → Storage Node (media).

• Control via NetWorker Management Console (NMC).

8.6 CommVault Complete Backup & Recovery

Overview:

• Full-featured, all-in-one enterprise suite.

• Renowned for flexibility and automation.

Features:

• Agentless VM backups.
• Application-aware support for 30+ platforms.
• File analytics, deduplication, cloud integration.
• AI-driven anomaly detection in backups.

55
Architecture:

• CommServe (central server), MediaAgent, and Clients.

• Web-based Command Center for modern UI.

56
8.7 Use Case Scenarios

Scenario Recommended Tool Reason

Enterprise with complex DR automation,
Veritas NetBackup
DR needs scalability
Windows-heavy small
Backup Exec Simple, GUI-based
business
Cloud-first enterprise CommVault Deep cloud integration
Native Linux/Unix
Linux/unix data center Dell NetWorker
support
Long-term archival with IBM Spectrum Protect Tape optimization and
tape (TSM) retention

8.8 Licensing & Cost Models

Tool Licensing Model

IBM TSM Capacity-based (TB)
NetBackup Per-socket / per-TB
Backup Exec Per-agent or per-subscription
NetWorker Per-client or per-capacity
CommVault Subscription + workload-based

Many tools now offer cloud-based SaaS deployment models.

Summary Points

• Multiple enterprise backup tools exist, each with strengths in specific

environments.
• NetBackup and CommVault are top choices for large, heterogeneous
environments.
• Backup Exec is ideal for SMBs with Windows servers.
• Spectrum Protect and NetWorker excel in tape environments and
Linux/Unix workloads.
• Choosing a tool depends on your platform, RTO/RPO needs, budget,
and IT maturity.

57
Review Questions with Answers

Q1. Which tool is now known as IBM Spectrum Protect?

Q2. Which Veritas product is suitable for small Windows environments?
Q3. Name one tool that integrates with Dell EMC Data Domain.
Q4. What is CommServe in CommVault?
Q5. Which tools support VM-level backups?
Q6. Which tool offers anomaly detection using AI?

58
Review Questions with Answers

Q1. Which tool is now known as IBM Spectrum Protect?

A1. IBM TSM (Tivoli Storage Manager).

Q2. Which Veritas product is suitable for small Windows

environments?
A2. Veritas Backup Exec.

Q3. Name one tool that integrates with Dell EMC Data Domain.
A3. Dell EMC NetWorker.

Q4. What is CommServe in CommVault?

A4. The central control server managing the backup environment.

Q5. Which tools support VM-level backups?

A5. All five: TSM, NetBackup, Backup Exec, NetWorker, CommVault.

Q6. Which tool offers anomaly detection using AI?

A6. CommVault.

59
Module 9:
Introduction to Veeam and vRanger
Learning Objectives:

By the end of this module, students will:

• Understand the core functionalities of Veeam Backup & Replication

and Quest vRanger.
• Learn how these tools simplify VM backup, replication, and recovery.
• Compare capabilities, architecture, and supported environments.
• Explore real-world VM backup strategies using these tools.

9.1 Why Specialized VM Backup Tools?

While traditional backup tools can handle VM backups, virtualized

environments require speed, intelligence, and app-awareness.

Reasons:

• Need for agentless backups.

• Restore single files or entire VMs quickly.
• Integration with hypervisors (VMware, Hyper-V).
• Replication for Disaster Recovery (DR).

9.2 What is Veeam Backup & Replication?

Veeam is a powerful, all-in-one backup, recovery, and replication solution

tailored for VMware, Hyper-V, and cloud-native environments.

Core Features:

• Agentless VM backup.
• Instant VM Recovery.
• File-level and app-aware backups (Exchange, SQL, AD).
• Backup copy, replication, and SureBackup for auto-testing.
• VSS integration for Windows-based apps.
• Multi-cloud integration: AWS, Azure, GCP.

60
Veeam Architecture:

Component Description
Central management &
Veeam Backup Server
scheduling.
Proxy Moves data from source to target.
Repository Where backup files are stored.
Enterprise Manager Central web UI for reporting.

Supported Platforms:

Hypervisor/Platform Support
VMware vSphere
Microsoft Hyper-V
Nutanix AHV (via plug-in)
Physical Workloads
Cloud (AWS, Azure)

9.3 What is vRanger?

Quest vRanger is a backup and recovery solution focused primarily on

VMware and Hyper-V environments. It was once the industry leader before
Veeam rose in popularity.

61
 Core Features:

• Image-based backups.
• File-level recovery.
• Compression and deduplication.
• VMware Changed Block Tracking (CBT).
• Direct-to-tape support (optional).

Limitations:

• Limited cloud integration.

• Less frequent updates compared to Veeam.
• Smaller ecosystem and community.

62
9.4 Feature Comparison Table

Feature Veeam vRanger

VMware Support Yes Yes
Hyper-V Support Yes Yes
Instant VM Recovery Yes Limited
File-Level Restore Yes Yes
Cloud Backup Integration AWS, Azure, GCP Limited
Backup Copy (Secondary) Yes No
Tape Support Via plug-ins Optional
Licensing Per-VM or Socket Per-Socket
UI and Ease of Use Modern + Web UI Legacy Windows UI
Support and Ecosystem Excellent Declining

63
9.5 Veeam Backup Types

Type Description
Full Backup Entire VM snapshot
Incremental (Forever) Changed blocks only after initial full
Synthetic Full Combined incremental into a new full backup
Application-aware Uses VSS to back up SQL, Exchange, etc.

9.6 Real-World Use Cases

Use Case Tool Notes

Agentless backup of 100+
Veeam Fast, scalable, efficient
VMware VMs
File-level restore from VM backup
Both Veeam is faster with UI
Cloud backup to AWS S3 Veeam Native cloud-tiering support
Budget-friendly, light
Simple local VM backups (SMB) vRanger
environment
Backup compliance with DR
Veeam SureBackup + reporting
testing

9.7 Tools and Interfaces

Tool CLI Web UI Reporting API Support

Veeam (REST API)
vRanger

Summary Points

• Veeam and vRanger are specialized for VM backup and recovery.

• Veeam offers a comprehensive, modern, cloud-integrated platform.
• vRanger is lightweight, suitable for basic virtual environments.
• Instant VM recovery, replication, cloud backup are Veeam strengths.
• Choose based on environment complexity, cloud needs, and budget.

64
Review Questions

Q1. What platforms does Veeam support for backup?

Q2. What is Instant VM Recovery in Veeam?
Q3. Which tool offers cloud-native backup capabilities?
Q4. What is Changed Block Tracking (CBT)?
Q5. Name one limitation of vRanger.
Q6. Which tool has a larger ecosystem and better support?

65
Review Questions with Answers

Q1. What platforms does Veeam support for backup?

A1. VMware, Hyper-V, Nutanix AHV, physical servers, AWS, Azure, GCP.

Q2. What is Instant VM Recovery in Veeam?

A2. A feature that allows booting a VM directly from backup files without
restoring it first.

Q3. Which tool offers cloud-native backup capabilities?

A3. Veeam.

Q4. What is Changed Block Tracking (CBT)?

A4. A VMware feature that tracks modified blocks, enabling efficient
incremental backups.

Q5. Name one limitation of vRanger.

A5. Limited support for cloud storage and less modern UI.

Q6. Which tool has a larger ecosystem and better support?

A6. Veeam.

66
Module 10:
Restoring Files from the Backups
Learning Objectives:

By the end of this module, students will:

• Understand various restoration techniques: full, partial, file-level.

• Learn how to restore data from disk, tape, NAS, and cloud targets.
• Explore restoration in virtual and physical environments.
• Understand disaster recovery planning through real-world restore
workflows.

10.1 What is Restore in Backup Terminology?

Restore is the process of retrieving lost, corrupted, or deleted data from a

backup copy. It is the actual reason why backups are made.

Types of restores include:

• File-level (a single file/folder)

• Volume-level (entire drive/partition)
• Application-level (SQL, Exchange, etc.)
• VM-level (entire virtual machine)
• Bare-metal (complete OS+data restore)

10.2 Key Restore Concepts

Term Definition
Timestamp of available backup to restore
Recovery Point
from.
Recovery Time Time it takes to complete the restore process.
Granular Restore Ability to restore a single item (e.g., email)
Bare-metal Restoring a full system onto new hardware.
Restoring apps in a usable state (e.g., no DB
Application-consistent
corruption)

67
10.3 Types of Restore Workflows

1. Full Restore

• Rebuilds a complete system or disk from backup.

• Time-consuming but comprehensive.

2. Incremental Restore

• Uses full + incremental backups to reconstruct data.

• Requires chain of backups to be intact.

3. Differential Restore

• Restores full backup and latest differential.

• Quicker than incremental in some cases.

4. Instant Recovery

• Boots a VM or mounts backup image directly from storage.

• Near-zero downtime (offered by Veeam, Commvault, etc.).

68
10.4 Restore from Different Targets

Disk/NAS Restore

• Fastest restore method.

• Mostly used for file/volume or VM image restores.

Tape Restore

• Slower, sequential access.

• Often used for archival restores.
• Requires index cataloging and tracking.

Cloud Restore

• Depends on bandwidth and provider API.

• Can be automated via tools (Veeam, Commvault).
• Use cold-to-hot tier migration if needed.

69
70
10.5 Common Restore Scenarios

Scenario Restore Type Tools Best Suited

Veeam, Windows
Accidentally deleted files File-level
Server Backup
Ransomware wipeout Full system restore Acronis, NetBackup
SQL Server corruption App-aware restore Veeam, Commvault
Restore from old tape (3+
Tape restore TSM, NetWorker
years)
Test VM deployment from
Instant Recovery Veeam, Commvault
backup

10.6 Considerations Before Restoring

• Validate backup source (integrity, date).

• Check storage availability for the restored data.
• Select correct recovery point.
• Understand dependencies (e.g., app-specific restores).
• Perform test restores regularly.

10.7 Restore Tools & Interfaces

Tool Restore Options Notes

Easy UI and powerful
Veeam Full, Instant, File, App-aware
features
Windows
File/Volume, System State Basic but functional
Server
Commvault App, file, VM, object restore Granular + cloud support
NetBackup Full system or per-file Enterprise-level control
Image-based, bootable media Good for endpoint
Acronis
restore recovery

71
10.8 Restore Failures and Troubleshooting

Issue Cause Solution

Backup deleted, media Enforce retention
Backup not found
lost policies
Snapshot corrupted Incomplete backup Use another restore point
Wrong restore target or
Permissions denied Restore as administrator
user rights
Application fails post- Use app-aware/VSS
Inconsistent state
restore backups
Restore slow from Use staging area or
Bandwidth or throttling
cloud cold/hot tier

Summary Points

• Restores are the reason backups exist—test them regularly.

• Know the difference between full, file-level, and instant recovery.
• Tools offer multiple restore workflows including cloud, tape, disk.
• Always plan and document restore procedures (as part of DR plans).
• Granular recovery saves time in real-world scenarios.

Review Questions with Answers

Q1. What is granular recovery?

Q2. Name two backup tools that support Instant VM Recovery.
Q3. What is required before doing a restore from tape?
Q4. What is the risk of not testing backups?
Q5. What is a Bare-Metal Restore?
Q6. Which tool can perform file-level restore from cloud backups?

72
Review Questions with Answers

Q1. What is granular recovery?

A1. The ability to restore specific items like files, emails, or records without
restoring the entire system.

Q2. Name two backup tools that support Instant VM Recovery.

A2. Veeam and Commvault.

Q3. What is required before doing a restore from tape?

A3. Index/catalog must be available to locate the correct tape and backup
set.

Q4. What is the risk of not testing backups?

A4. Backups may be corrupt, outdated, or unusable in an emergency.

Q5. What is a Bare-Metal Restore?

A5. Restoring a complete system (OS + data) onto new hardware from a full
image.

Q6. Which tool can perform file-level restore from cloud backups?
A6. Veeam, Commvault, or Acronis.

73
Module 11:
Creation of Backup Policies and
Understanding All Necessary Attributes
Learning Objectives:

By the end of this module, students will:

• Understand what a backup policy is and why it’s critical.

• Learn how to define backup schedules, retention, RPO/RTO, and
storage tiers.
• Explore best practices in designing, implementing, and documenting
policies.
• Be able to implement policies in popular backup tools (Veeam,
Commvault, etc.).

11.1 What is a Backup Policy?

A backup policy is a formal document or configuration that outlines:

• What to back up
• When to back it up
• Where to store it
• How long to keep it
• How often to verify it
• Who is responsible

Backup policies are the blueprint that turn technical procedures into a
managed, auditable backup strategy.

74
11.2 Why Backup Policies Are Essential

• Prevent data loss due to oversight.

• Ensure legal/regulatory compliance (e.g., GDPR, HIPAA).
• Define clear RTO/RPO objectives.
• Help with cost optimization.
• Improve accountability and auditability.

11.3 Core Components of a Backup Policy

Component Description
Scope Systems, apps, users, and environments included.
Schedule Frequency: hourly, daily, weekly, etc.
Backup Type Full, Incremental, Differential, Synthetic, etc.
How long backups are stored (e.g., 30 days, 7
Retention Policy
years).
Objectives for data loss tolerance and recovery
RPO/RTO
time.
Encryption Data protection in-transit and at-rest.
Testing & Verification Frequency and method of backup validation.
Roles &
IT team, backup admins, application owners.
Responsibility
Non-critical systems or volatile data (e.g., temp
Exceptions
logs).

75
11.4 Example Policy Template

Policy Name: HR-FileServer-Policy

Scope: HR Shared Drive on Server XYZ

Schedule: Full backup every Sunday; Incremental Mon–Sat

Backup Type: Full + Incremental

Retention: 6 months

Storage: NAS + Cloud Tiering (Glacier)

RPO: 4 hours

RTO: 1 hour

Encryption: AES-256 at-rest

Verification: Weekly test restore of 1 file

Responsible: Backup Admin – John Smith

Exceptions: Temp folder excluded

76
11.5 RPO and RTO—A Refresher

Term Meaning Example

30 minutes for production
RPO Max data loss allowed (how recent)
database
Max downtime allowed before 2 hours for web server after
RTO
recovery crash

Backup policy must define and align with RPO/RTO values.

11.6 Retention Planning

Data Type Retention Time Storage Tier

Daily Operational Files 14–30 days Disk/NAS
Monthly Reports 1–3 years Cloud Archive
Legal/Financial Data 7–10 years Tape or Glacier
Audit Logs 1 year (rotating) Cold Disk or Cloud

11.7 Implementing Policies in Backup Tools

Veeam

• Policies are created via Backup Jobs.

• Define schedule, storage, retention, app-aware settings.
• Use Backup Copy Jobs for offsite retention.

Commvault

• Define Plans, Storage Policies, and Schedules.

• Granular control over copies, dedup, replication.

NetBackup

• Create Policy Objects.

• Specify client list, schedule, and backup selection list.

Backup Exec

• Use Job Templates.

• Easy GUI to select schedule, retention, compression.
77
11.8 Monitoring, Validation, and Audit

Backup policies are only useful if enforced and monitored.

Task Frequency Tool/Method

Backup Job Monitoring Daily Dashboards, Alerts
Test Restore Weekly/Monthly Random file restores
Audit Reports Monthly/Quarterly Export logs, compliance
Storage Check Monthly Capacity and cost review

11.9 Common Policy Mistakes

Mistake Risk
No test restores Backups may be corrupt or unusable
No retention limit Storage bloats; high cost
Overly frequent full backups Wasted time/resources
Ignoring RPO/RTO Failure to meet business SLAs
One-size-fits-all approach Missed optimization for system priorities

Summary Points

• Backup policies define the “how, what, and when” of backup

operations.
• Must align with business continuity, compliance, and storage
efficiency goals.
• Include scope, frequency, retention, RTO/RPO, and roles.
• Tools like Veeam, Commvault, and NetBackup implement policies as
jobs/templates.
• Regular audits and testing are essential to maintain confidence.

78
Review Questions with Answers

Q1. What is a backup policy?

A1. A formal plan defining what data to back up, when, where to store it,
and for how long.

Q2. What do RTO and RPO stand for?

A2. Recovery Time Objective (how fast to recover) and Recovery Point
Objective (how much data loss is acceptable).

Q3. What happens if no retention period is defined?

A3. Backup storage grows uncontrollably, increasing cost and complexity.

Q4. Name one tool that uses "Backup Plans" for policy creation.
A4. Commvault.

Q5. Why is regular testing important in a backup policy?

A5. To ensure backups are valid and can be successfully restored.

Q6. Who is typically responsible for enforcing backup policies?

A6. Backup Administrators, monitored by IT leadership and compliance
officers.

79