Chapter 10

CHAPTER 10
BACKUP AND
ARCHIVE
EMC Proven Professional
Chapter 10: Backup and Archive
Upon completion of this module, you should be able to:

Describe backup granularities
Explain backup and recovery operations
Describe various backup targets
Explain data deduplication
Describe backup in virtualized environment
Explain data archive
Lesson 1: Backup Overview

During this lesson the following topics are covered:
Backup granularity
Backup method
Backup architecture
Backup and recovery operations
What
is
Backup?
Backup
It is an additional copy of production data that is created

and retained for the sole purpose of recovering lost or
corrupted data.
Organization also takes backup to comply with

regulatory requirements
Governance
Compliance
SLAs
Backups are performed to serve three purposes:

Disaster recovery
Operational recovery
Archive
Backup Purpose
Backups are performed to serve three purposes:
Disaster recovery
Is there a plan to recover the whole data center when a
natural disaster happens?
Based on RPO and RTO
From remote replication to tape
Operational recovery
Happens more often than natural disasters
Is there a plan to recover an individual server/compute
host in a cluster?
What happens if the backup infrastructure and the
compute host is gone?
Backup Purpose (continued)
Archive
Process of moving data that is no longer actively
used, from primary storage to low cost secondary

storage
Needed for regulatory compliance
Key Backup/Restore Considerations
First and foremost, it comes down to the amount of

data loss and downtime that a business can endure
$$$$$
Customer business needs determine:

What are the restore requirements RPO & RTO?
RPO determines backup frequency
Which data needs to be backed up?
How frequently should data be backed up?
How long will it take to backup?
How many copies to create?
How long to retain backup copies?
Backup media type is driven by the RTO
Location, size, and number of files?
Key Backup/Restore Considerations

How long to retain backup copies?
Backup media type is driven by the RTO
If recovery times is minutes, tapes wont do
Location, size, and number of files?
Larger sized files take less time to back up than the

equal amount of smaller sized files
Backup Granularity
Full Backup
Su
Su
Su
Su
Su
ncremental Backup
Su
M T W Th F S Su M T
W Th
S Su M T W Th F
S Su M T W Th F
S Su
S Su M T W Th F
S Su M T W Th F
S Su
mulative (Differential) Backup
Su
M T W Th F
S Su M T
W Th
Amount of Data Backup
Restoring from Incremental Backup

Monday
Files 1, 2, 3
Full Backup
Tuesday
Wednesday Thursday
File 4
Updated File 3
File 5
Incremental
Incremental
Incremental
Friday
Files 1, 2, 3, 4, 5
Production
Less number of files to be backed up, therefore, it

takes less time to backup and requires less storage
space
Longer restore because last full and all subsequent
incremental backups must be applied
10
Restoring from Cumulative Backup

Monday
Files 1, 2, 3
Full Backup
Tuesday
Friday
Wednesday Thursday
File 4
Files 4, 5
Files 4, 5, 6
Cumulative
Cumulative
Cumulative
Files 1, 2, 3, 4, 5, 6
Production
More files to be backed up, therefore, it takes more

time to backup and requires more storage space
Faster restore because only the last full and the
last cumulative backup must be applied
11
Backup Methods
Two methods of backup, based on the state of the

application when the backup is performed
Hot or Online
Application is up and running, with users accessing
their data during backup
Open file agent can be used to backup open files
Interacts directly with the operating system or application
to enable the creation of consistent copies of all open files
Consistency is extremely important for database
restartability
Disadvantage associated with using a hot backup is
that agents usually affect the overall application
performance
Cold or Offline
Requires application to be shutdown during the backup
process
Users cant access the application during a cold backup

12
Backup Methods (continued)

Point-in-time copy
Needed when downtime from a cold back or
performance impact from a hot backup is unacceptable
Bare-metal recovery (BMR)

OS, hardware, and application configurations are
appropriately backed up for a full system recovery

BMR builds the base system
Includes partitioning
File system layout
Operating system
Applications
All relevant configurations
13
Server Configuration Backup
Like BMR, but can also recover a server onto

dissimilar hardware
Creates and backs up server configuration profiles,
based on user-defined schedules (not done during
normal backups)
Profiles are used to configure the recovery server in
case of production server failure

Profiles include OS configurations, network
configurations, security configurations, registry
settings, application configurations
Two types of profiles used

Base profile
Contains the key elements of the OS required to
recover the server
Extended profile
Chapter
10: Backup
and Archive
Typically larger than base
profile
and
contains all
14
Backup Architecture
Backup Server
Backup client
Gathers the data that

needs to be backed up
and sends it to storage
node
Backup server
Manages backup
operations and maintains
backup catalog
Information about the

backup configuration
and backup metadata
Storage node
Backup
Catalog
g
in
k
ac
Tr
m
or
f
In
n
io
at
Backup Data
Tracking
Information
Backup Data
Backup Client
Storage Node
(Application
Server)
Backup
Device
Responsible
EMCProven
Professional
for writing
data to backup device
Manages the backup
device
15
Backup Operation
Application Servers
(Backup Clients)
Backup
server initiates scheduled backup process
1
Backup
server retrieves backup-related
2
information from the backup catalog.
Backup
server instructs storage node to
3a
load backup media in backup device.
Backup
server instructs backup clients to
3b
send data to be backed up to storage node.
3b
Backup
clients send data to storage node and
4
update the backup catalog on the backup server.
Storage
node sends data to backup device.
5
3a
2
7
Storage node sends metadata and media

information to backup server.
Backup
server updates the backup catalog.
7
EMCServer
Proven Storage
Professional
Backup
Node Backup Device
16
Recovery Operation
Application Servers
(Backup Clients)
Backup
client requests backup server for
1
data restore.
Backup
server scans backup catalog
2
to identify data to be restored and the
client that will receive data.
Backup
server instructs storage node
3
to load backup media in backup device.
Data
4 is then read and send to backup client.
Storage
node sends restore metadata
5
to backup server.
Backup
server updates the backup catalog.
6

Backup Server
Storage Node
Backup Device
17

Lesson 2: Backup Topologies and Backup in NAS
Environment
Common backup topologies
Backup in NAS environment
18
Direct-Attached Backup
Storage node is configured on a backup client and

the backup device is attached to the client
Only the metadata is sent to the backup server
through the LAN

Frees LAN from backup traffic
Not a good configuration because the backup devices

arent being shared poor utilization of resources
Chapter 10: Module Name
19
Direct-Attached Backup (continued)
Metadata
Backup
Data
LAN
Backup Server
Application Server/
Backup Device
Backup Client/
Storage Node
20
LAN-Based Backup
Clients, backup server, storage node, and backup

device are all connected to the LAN
Data that needs to be backed up is transferred from
the backup client (source) to the backup device
(destination) over the LAN
Can affect network performance if not segmented
21
LAN-Based Backup (continued)

Application Server/
Backup Client
Backup Server
Metadata
LAN
Backup Data
Storage Node
Backup Device
22
SAN-Based Backup
Most appropriate solution when a backup device

needs to be shared among clients
Also called LAN-Free backup
Backup device and clients are attached to the SAN
Client sends data to be backed up to the backup
device over the SAN

Backup data traffic is restricted to the SAN
Only backup metadata is transported over the LAN
Very small amount compared to production data
Disks arrays can be used in this configuration due the
low cost of disks that are emulated to look like tape
backups
23
SAN-Based Backup (continued)
LAN
FC SAN
Metadata
kup Server
Backup Data
Application Server/
Backup Client
Backup Device
Storage Node
24
Mixed Backup Topology

Application Server-2/
Backup Client
Metadata
FC SAN
LAN
Backup Data
Metadata
ackup Server
Application Server-1/
Backup Client
Backup Device

Storage Node
25
Backup in NAS Environment
Common backup implementations in a NAS

environment are:
Server-Based backup
Serverless backup
NDMP 2-way backup
NDMP 3-way backup
26
Server-Based Backup
Application server-based backup

NAS head retrieves data from a storage array over
the network and transfers it to the backup client

running on the application server
Backup client sends data to the storage node to write
the data to the backup device
This configuration overloads the network with backup

data and also puts a strain on application server
resources
27
Server-Based backup (continued)

Storage Array
Application Server/
Backup Client
LAN
FC SAN
NAS Head
Backup
Data
Backup Device
Metadata
Backup Server/
Storage Node
28
Serverless Backup
Network share is mounted directly on the storage

node
Avoids overloading network and using application
server resources
Storage node, which is also the backup client, reads
data from the NAS head and writes it to the backup
device without involving the application server
One network hop is eliminated
29
Serverless Backup
Storage Array
NAS Head
LAN
FC SAN
Backup
Data
Application Server
Backup Device
Backup Server/
Storage Node/
Backup Client
30
NDMP 2-way Backup
Network Data Management Protocol

TCP/IP-based protocol
Communicates with all the NAS devices to perform
backups
OS and platform independent
Leverages the high-speed connection between the
backup devices and the NAS head

Doesnt support centralized management of all
backup devices since the backup device is dedicated
to a single NAS head
31
NDMP 2-way Backup

Storage Array
Backup
Device
Backup
Data
FC SAN
LAN
NAS Head
Application Server/
Backup Client
Metadata

Backup Server
32
NDMP 3-way Backup
A separate private backup network is established

between all NAS heads with the NAS head
connected to the backup device
Metadata and NDMP control data are still transferred
across the production network

Useful when backup devices need to be shared
33
NDMP 3-way Backup

NAS Head
FC SAN
Application Server/
Backup Client
Storage Array
LAN
Private
LAN
Backup Data
FC SAN
NAS Head
Metadata
Backup
Device

Backup Server
34
Lesson 3: Backup Targets

Backup to Tape
Backup to Disk
Backup to Virtual Tape
35
Backup to Tape
Traditionally low cost solution

Tape drives are used to read/write data from/to a
tape
Sequential/linear access
Multiple streaming to improve media performance
Writes data from multiple streams on a single tape
Limitation of tape
Backup and recovery operations are slow due to
sequential access
Wear and tear of tape
Shipping/handling challenges
EMCProven
Controlled
Professional environment is required for tape storage
Causes shoe shining effect or backhitching
36
Backup to Disk
Enhanced overall backup and recovery performance

Random access
More reliable
Can be accessed by multiple hosts simultaneously
Typical Scenario:
800 users, 75 MB
mailbox
60 GB database
24
Disk
Backup/Restore Minutes
108
Minutes
Tape
Backup/Restore
0
10
20
30
40
50
60
70
80
90 100 110 120
Recovery Time in Minutes*
Source: EMC Engineering and EMC IT
37
Backup to Virtual Tape
Disks are emulated and presented as tapes to

backup software
Does not require any additional modules or changes
in the legacy backup software
Provides better single stream performance and
reliability over physical tape
Online and random disk access
Provides faster backup and recovery
38
Virtual Tape Library
LAN

Backup Clients
FC SAN
Virtual Tape Library Appliance
Backup
Server/
Storage Node
Emulation Engine
Storage (LUNs)
39
Backup Target Comparison

Tape
Disk
Virtual Tape
Offsite
Replicatio
n
Capabilitie
s
No
Yes
Yes
Reliability
No inherent
protection methods
RAID, spare
RAID, spare
Performan
ce
Low
High
High
Use
Backup only
Multiple (backup
and production)
Backup only
40
Lesson 4: Data Deduplication

Deduplication overview
Deduplication methods
Deduplication implementations
Key benefits of deduplication
41
What is Data Deduplication?
Data
Deduplication
It is a process of identifying and eliminating

redundant data.
Deduplication methods
File level
Subfile level
Deduplication
implementations
Source-based
Target-based
42
Data Deduplication Methods
File-level deduplication (single-instance storage)

Detects and removes redundant copies of identical
files
After a file is stored, all other references to the same
file refer to the original copy
Subfile deduplication
Detects redundant data within and across files
Two methods
Fixed-length block
Variable-length segment
43
Data Deduplication Implementation Sourcebased

Data is deduplicated at
the source (backup
client)
Backup client sends
only new, unique
segments across the
network
Reduced storage
capacity and network
bandwidth
requirements
Increased overhead on
the backup client
De-duplication
at Source
Data set
Backup Client
Storag
e
Netwo
rk
Backup
Device
ADe-duplication agent
44
Data Deduplication Implementation Targetbased

Data is deduplicated at
the target
De-duplication
at Target
Inline
Post-process
Offloads the backup
client from
deduplication process
All the backup data
traverse the network
Data set
Backup Client
Storag
e
Netwo
rk
Backup
Device
45
Data Deduplication Key Benefits
Reduces infrastructure costs

By eliminating redundant data, less storage is
required to hold the backup images
Enables longer retention periods

Reduces the amount of redundant content in the daily
backup, and hence, users can extend their retention

policies
Reduces backup window

Less data to be backed up, which reduces backup
window
Reduces backup bandwidth requirement

Source based de-duplication eliminates redundant
data before data is sent over the network
46
Lesson 5: Backup in Virtualized Environment

Traditional backup approach
Image-based backup
47
Backup in Virtualized Environment Overview
Backup options
Traditional backup approach
Image-based backup approach
Backup optimization
Deduplication
48
Traditional Backup Approaches
Backup agent on VM
Requires installing a backup
agent on each VM running on a

hypervisor
Can only backup virtual disk
data
Does not capture VM files such
as VM swap file, configuration
file
Challenge in VM restore
Backup agent runs on each

VM
Backup agent on Hypervisor

Requires installing backup agent
EMC Proven
Professional
only
on hypervisor
Backs up all the VM files
Backup agent runs on

Hypervisor
= Backup
Agent
49
Image-based Backup
Creates a copy of the

guest OS, its data, VM
state, and
configurations
Application
Server
Proxy Server
as a single file
image
Mounts image on a
proxy server
Offloads backup
processing from the
hypervisor
Mount
The backup is saved

Backup Device
Snapshots
Storage
EMCEnables
Proven Professional
quick
restoration of VM
50
Chapter Module 10: Backup and Archive
Lesson 6: Data Archive

Fixed content
Data archive
Archive solution architecture
51
Fixed Content
Fixed content is growing at more than 90% annually

Significant amount of newly created information falls
into this category

New regulations require retention and data protection
Examples of Fixed Content
Electronic
Documents
Contracts and claims

Email attachments
Financial spread
sheets
CAD/CAM designs
Presentations
Digital Records
Documents
Checks, securities
trades
Historical
preservation
Photographs
Personal/professional
Surveys
Seismic, astronomic,
geographic
Rich Media
Medical
X-rays, MRIs, CT Scan
Video
News/media, movies
Security surveillance
Audio
Voicemail
Radio
52
Data Archive
A repository where fixed content is stored

Enables organizations retaining their data for an
extended period of time in order to
Meet regulatory compliance
Plan new revenue strategies
Archive can be implemented as

Online
Immediately accessible
Nearline
Must be mounted or loaded to access the data
Offline
Storage device that is not ready to use manual
intervention needed
53
Challenges of Traditional Archiving Solutions
Both tape and optical are susceptible to wear and

tear
Involve operational, management, and maintenance
overhead
Have no intelligence to identify duplicate data

Same content could be archived many times
Inadequate for long-term preservation (yearsdecades)

Unable to provide online and fast access to fixed
content
54
Content Addressed Storage An Archival

Solution
Disk-based storage that has emerged as an
alternative to traditional archiving solutions
Provides online accessibility to archive data
Enables organization to meet the required SLAs
Provides features that are required for storing
archive data
Content authenticity and content integrity
Location independence
Single-instance storage
Retention enforcement
Data protection
Chapter Module 10: Backup and Archive
55
Concepts in Practice
EMC NetWorker
EMC Avamar
EMC Data Domain
56
EMC NetWorker
Centralizes, automates, and accelerates data

backup and recovery operations across the
enterprise
Key features
Supports heterogeneous platforms such as Windows,
UNIX, Linux, and also supports virtual environments

Supports different backup targets tapes, disks, and
virtual tapes
Supports Multiplexing (or multi-streaming) of data
Provides both source-based and target-based
deduplication capabilities by integrating with EMC
Avamar and EMC Data Domain respectively
EMCProven Professional
Cloud-backup option enables backing up data to
cloud
57
EMC Avamar
Disk-based backup and recovery solution that

provides source-based data deduplication
Three major components include Avamar server,
Avamar backup clients, and Avamar administrator
Avamar server includes
Software only, Avamar Data Store, Avamar Virtual
Edition
58
EMC Data Domain
Target-based deduplication solution

Provides technological advantages
Data invulnerability architecture
Data Domain Stream-Informed Segment Layout (SISL)
scaling architecture
Support native replication technology
Global compression
EMC Data Domain Archiver

Solution for long term retention of backup and archive
data
Designed with internal tiering approach
Supports deduplication technology
59

Chapter 10

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Chapter 10

Încărcat de

Drepturi de autor:

Formate disponibile

CHAPTER 10

Chapter 10: Backup and Archive

Chapter 10: Backup and Archive

Upon completion of this module, you should be able to:

Chapter 10: Backup and Archive

Chapter 10: Backup and Archive

Lesson 1: Backup Overview

EMC Proven Professional

Chapter 10: Backup and Archive

It is an additional copy of production data that is created

Organization also takes backup to comply with

Backups are performed to serve three purposes:

Chapter 10: Backup and Archive

Chapter 10: Backup and Archive

Backup Purpose (continued)

used, from primary storage to low cost secondary

Needed for regulatory compliance

EMC Proven Professional

Chapter 10: Backup and Archive

Key Backup/Restore Considerations

First and foremost, it comes down to the amount of

Customer business needs determine:

Chapter 10: Backup and Archive

Key Backup/Restore Considerations

Larger sized files take less time to back up than the

EMC Proven Professional

Chapter 10: Backup and Archive

mulative (Differential) Backup

EMC Proven Professional

Amount of Data Backup

Chapter 10: Backup and Archive

Restoring from Incremental Backup

Less number of files to be backed up, therefore, it

Restoring from Cumulative Backup

More files to be backed up, therefore, it takes more

Two methods of backup, based on the state of the

EMC Proven Professional

Users cant access the application during a cold backup

Backup Methods (continued)

Bare-metal recovery (BMR)

appropriately backed up for a full system recovery

EMC Proven Professional

Chapter 10: Backup and Archive

Server Configuration Backup

Like BMR, but can also recover a server onto

case of production server failure

Two types of profiles used

Gathers the data that

Information about the

Storage node sends metadata and media

Chapter 10: Backup and Archive

EMC Proven Professional

Chapter 10: Backup and Archive

Chapter 10: Backup and Archive

EMC Proven Professional

Chapter 10: Backup and Archive

Storage node is configured on a backup client and

through the LAN

Not a good configuration because the backup devices

EMC Proven Professional

Chapter 10: Module Name

Direct-Attached Backup (continued)

EMC Proven Professional

Chapter 10: Backup and Archive