StudentGuide v1.4

NSB Installation, Configuration,
and Management
Copyright
2012 Syncsort Incorporated. All rights reserved. DMExpress, Backup Express, DMX, MFX and
BEX are trademarks of Syncsort Incorporated. All other company and product names used herein
may be the trademarks of their respective companies.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS.
SYNCSORT
INCORPORATED MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH
RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.
Syncsort Education Services is committed to providing accurate and up to date information.
However, we cannot and do not guarantee that the publications are free from errors or omissions.
The information is subject to change without notice and is at the sole discretion of Syncsort
Education Services.
The use of this information or implementation of any of these techniques is a customer
responsibility and depends on the customers ability to evaluate and integrate them into the
customers operational environment. All elements such as examples, demos, exercises, and any
simulations included in this training have been developed and performed in a controlled lab
environment. While each item may have been reviewed by Syncsort for accuracy in a specific
situation, there is no guarantee that the same or similar results will result elsewhere. Customers
attempting to adapt these techniques to their own environments do so at their own risk.
The content may include references to third party claims, assertions, statements, or quotes.
Syncsort does not endorse, verify, or validate the accuracy of such references.
No part of the contents of this book may be reproduced, delivered, or transmitted in any form or
by any means without the written permission of Syncsort Education Services.
About Syncsort
Syncsort is a global software company that helps the worlds most successful organizations
rethink the economics of data. Syncsort provides extreme data performance and rapid time to
value through easy to use data integration and data protection solutions. With over 12,000
deployments, Syncsort has transformed decision making and delivered more profitable results to
thousands of customers worldwide.
2012 Syncsort Incorporated. All rights reserved. DMExpress, Backup Express and BEX are trademarks of Syncsort Incorporated. All other company and product names
used herein may be the trademarks of their respective companies.
Syncsort Global Education Services
NSB Installation, Configuration, and Management
NSB IInstallation,
t ll ti
Configuration and
Management
Revision History
Rev Number
Course Date
Revisions
1.0
Feb 2012
Completed
p
1.1
April 2012
Completed
1.2
June 2012
Completed
1.3
Sep 2012
Completed
1.4
Jan 2013
Work In Progress
Module 00 - Course Agenda
For use by Syncsort and its Authorized Training Partners only
Page 0 - 1
Pre-Assessment
Log on to https://iLearn.syncsort.com
You will need an iLearn account
Browse to the course you are attending
Complete the Pre-Assessment
Course Objectives
Upon completion of this course, you will be able to:
Describe the major
j components
p
of the NSB solution
Install and configure DPX
Define, run, and monitor DPX backup and recovery jobs
Use DPX Advanced Recovery options including IA, BMR, IV and FV
Explain and use DPX application protection features for Exchange, SQL,
SharePoint,, and Oracle environments
Discuss the importance of DPX Catalog Protection and Maintenance
Explain the Tertiary Protection and DR Features of DPX and how they can
be used to provide total enterprise protection
Page 0 - 2
Course Agenda
Day 1:
NSB Overview
DPX IInstallation
t ll ti
Configuring DPX Backups
Protecting MS Clusters with
DPX
Day 3:
DPX Agentless
VMware Protection
g
DPX Disaster Recovery Overview
Archiving to Tape
Catalog Maintenance
Change Journal Overview
DPX Design Considerations and
Advanced Configuration
Day 2:
DPX Advanced Recovery Options
Overview
Restoring Files using DPX
DPX Instant Access
DPX Application Protection
Exchange Protection
SQL and SharePoint Protection
Oracle Protection
DPX Bare Metal Recovery
DPX Virtualization
NSB Partner Education Learning Path

Sales: Accreditation
Continued Education
ABCs of NSB
Selling the NSB

Solution
Sales Discovery and

Qualification
15 Minutes
60 Minutes
15 Minutes
Pre-Sales SE: Accreditation

ABCs of NSB
NSB Product
Overview
NSB Technical
Fundamentals
15 Minutes
60 Minutes
1 Day
NSB Technical
Deep Dive
Post-Sales SE: Certification
Notes
Accreditation/Certification
Exams can be taken at any
time
Deliveries available through

e-Learning, Online Instructor
(OLT) & Instructor-Led (ILT)
Details on
partnerportal.syncsort.com
(3) 4-Hour Sessions
NSB Installation, Configuration and

Management
You
Are
Here
3 Days
Page 0 - 3
Validate Your Knowledge, Prove Your Skills

NSB Accreditation Program
Targets Sales and Pre-Sales

Technical Professionals
Online Exam accessed through iLearn
Free of Charge
NSB Certification Program
Targets Post-Sales and All Technical

Roles
Details and practice exam on iLearn
Exam proctored at over 5,000
Pearson Vue Testing Centers
Worldwide
7
Latest on the NSB Solution
https://partnerportal.syncsort.com
http://community.syncsort.com
https://iLearn.syncsort.com
www.blog.syncsort.com
Page 0 - 4
Module 01 - NSB Solution Overview
NSB S
Solution
l ti
O
Overview
i
Module Objectives
Upon completion of this module, you will be able to:
Discuss the NSB solution

Identify the basic components of an NSB solution
Articulate NSB Solution topology
List operating systems and technologies supported by
DPX
Explain NSB Solution architecture
List the key features and benefits of the NSB Solution
Page 1- 1
The NSB Solution

A fully integrated, seamless, block-level data protection solution
Combines Syncsorts data protection software DPX* with high
performance NetApp disk storage
A new paradigm in heterogeneous open systems data
protection
DPX Software*
NSB
SnapVault Secondary,
FlexClone, iSCSI,
SnapMirror (optional)
* Traditionally known as BEX / Backup Express

Syncsort Terminology
Syncsort DPX
Also known as the Syncsort Data Protection Software
Part of the NSB Solution
Latest Release v4.1
Backup Express
Commonly referred to as BEX
g y Data Protection solution from Syncsort
y
Legacy
Combined File, AROS, and ARSV functionalities
Last Release v3.4.x
Page 1- 2
NSB Solution Topology

DPX
Master
Server
Single Pane of
Glass
Replication
DPX Backup
WAN
LAN
DPX Clients
Exchange, SharePoint, SQL, VMware
optional
NetApp FAS
NetApp FAS
D2D Backup Target
DR Target
SAN
Any Primary Disk

SAN or DAS
optional
Tape Archive
Physical and
Virtual Servers
optional
Instant / Full
Virtualization
Target disk and tape,

local recovery
Tape Archive
Remote Disaster
Recovery
DPX Technology
DPX is a block-level, snapshot based data protection
technology
DPX is built on NetApps SnapVault and Open
Systems SnapVault (OSSV) technologies
Uses SnapVault block-incremental replication to offer
D2D and D2D2T backup
Page 1- 3
Why NSB?
Extends NetApps core data protection technologies
Full catalog spans disk and tape for wildcard
search/restore
Heterogeneous application support
Exchange, Oracle, SQL, SharePoint
Bare Metal Recovery to dissimilar hardware
Advanced recovery options like Instant Access (IA),
Instant and Full Virtualization (IV & FV)
Recovery from replicated DR (SnapMirror) copy
Deeper integration with VMware for advanced and
more efficient protection of virtual environments
Host-based and Agentless protection
Tape support
7
One Solution for Multi-Tiered Data Recovery

Restore selected
folders and files
from catalog
File
Recovery
DPX
Snapshots
Application
and Item
Recovery
Exchange, SQL,
Oracle, SharePoint
Base
Block update
Server
Recovery**
R
**
C:\
D:\
OS and Data
Block update
Block update
Site
Recovery**
** Agentbased/Agentless
Integrated DR,
SnapMirror
8
Page 1- 4
Supported Technologies
Operating Systems
Microsoft Windows
Linux
RedHat Enterprise Linux, SUSE Linux Enterprise
Server, CentOS (x64, x86)
Storage
Any block-level primary storage, both SAN and Direct
Attached
Windows Cluster aware
Always refer to the online compatibility guide for latest information
Supported Technologies (contd)

Database and Application Interfaces
Microsoft Exchange
Microsoft SQL Server
Microsoft SharePoint
Oracle* (64-bit/32-bit)
* on supported OS platforms
Storage Area Networks

Tape Sharing for Nodes on SAN
Virtual Environments
VMware
ESX Server; ESXi; vSphere
Microsoft Hyper-V
Always refer to the online compatibility guide for latest information
10
Page 1- 5
Compatibility Guide
Latest compatibility guide or support matrix can be
downloaded from the Syncsort website
www.syncsort.com
Update this screenshot
11
Distributed Architecture
All systems (nodes) in the NSB Enterprise are
classified as one of these types:
Master Server
Client
12
Page 1- 6
Master Server
Only one in an enterprise
Initiates and manages jobs
DPX
Catalog
Contains the DPX catalog - single central database

Runs web server for Management Console
Windows, Linux
13
Client
Any node which is the source of data to be backed up
or any node where data will be restored
Physical
Ph i l or Vi
Virtual
t l
Supported OS: Linux, Windows, Solaris
14
Page 1- 7
DPX Management Console

One-stop shop for all Enterprise Management
Platform Independent, Java Application
Customizable reporting in PDF format
Default user id: sysadmin
Connects to the web server on the Master Server
Uses port 6122
15
Technical References
Syncsort Support
Syncsort online customer support
http://www.syncsort.com/support
Requires MySupport account to:
Download latest software and
patches
Access latest Support Matrix
Search Knowledge Base (KB)
articles
Refer to and download Product
Documentation
Request Emergency license keys
NetApp Support
NetApp online customer support
http://support.netapp.com
Requires NOW account to:
Download ONTAP updates
Search KBs
16
Page 1- 8
Knowledge Check
1. Which type of primary storage can be protected using DPX?
2 What is the target (destination) for DPX backups?
2.
3. DPX belongs to which data protection solution category?
o
o
o
Block-level
File-level
Snapshot-based
4 What
4.
Wh t are th
the basic
b i components
t off an NSB Solution?
S l ti ?
5. Which application backups are supported by DPX?
17
Module Summary
You are now able to:
Di
Discuss N
NetApp
tA S
Syncsortt IIntegrated
t
t d Backup
B k (NSB)
solution
Identify the basic components of an NSB solution
Articulate NSB topology
List operating systems and technologies supported by
NSB
Explain
E l i NSB architecture
hit t
List the key features and benefits of NSB
18
Page 1- 9
Module 2 DPX Installation
DPX IInstallation
t ll ti
Module Objectives
Install DPX Master Server and Clients
Use the DPX Management Console
Update nodes using the Autoupdate feature
Recognise, start and stop DPX services
Add and Configure Node Groups and nodes, including
NetApp Storage Systems, in the Enterprise
Module 02 - DPX Installation
Page 2- 1
DPX Installation: Basic Steps

Four main steps are required:
1. Install/Patch the DPX Master Server
2. Install/Patch clients/agents
3. Setup/Customize the NetApp Storage System
4. Add the Storage System(s) to the Enterprise
Note: Further clients can be added at any time
Lesson 1
Installing the DPX Master

Server
Page 2- 2
DPX Master Server Installation

Can be installed only on 64-bit hardware and OS
Installation files available on MySupport site
http://www.syncsort.com/support
Downloadable ISO images
Use the correct installation executable (based on OS)
Option
available
il bl only
l
on 64-bit
machines
DPX Master Server Installation (contd)

Default components installed on the DPX Master
Server
Virtualization
Vi t li ti P
Proxy S
Server
Client
Page 2- 3
DPX Master Server Installation (contd)

Choose installation location (SSPRODIR)
Default is C:\Program Files\DPX
Strongly recommended to use a dedicated drive
Non System drive
Automatically creates a DPX Enterprise
(Optional) Add the Master Server to it
A Node Group can be specified
DPX Licensing
Source-side, Capacity-based License
One license for most of the features, including:
Windows,
Wi d
and
d Li
Linux nodes
d
All supported applications
Exchange, SQL, SharePoint, Oracle
Virtualized environments
Both Host-based and Agentless
Unlimited clients (nodes)
Tape Archive
Additional licenses required for:
Application Recovery Options (EMR, SPOR)
File-Level Backups (Backup Express)
Managing OSSV relationships
Page 2- 4
DPX License Key

A string specified during Master Server installation
Stored in a text file on the Master Server
.ssbe_key file in DPX Installation folder
Generated by Syncsort Licensing
licensing@syncsort.com
Based on the Master Server hostname, number of
processors, and processor type
Verified before running every DPX backup
DPX License Keys

3 types of License Keys:
Evaluation keys
Have a set expiration date
Allow to run all DPX features
Emergency keys
Download from MySupport
Up to 4 per year per customer
p one week from download
Expire
Allow to run all DPX features
Production keys
Reflect the capacity and options purchased
10
Page 2- 5
License Keys
Copy and Paste
the actual key
DO NOT
BROWSE
Verify Checksum
11
Lab Exercise
Introduction to the Lab

Environment
Lab 2-1: Installing DPX Master
Server
Duration: 20 mins
12
Page 2- 6
DPX Lab Environment
13
Lesson 2
Installing DPX Clients
14
Page 2- 7
DPX Client Install Overview

Can be installed on 32-bit and 64-bit hosts
Recommended to install after installing the Master
Server
Use the correct installation executable (based on
OS/Kernel type)
Supported OS: Windows, Linux
Only one client to install
No additional agents for protecting applications like
SQL,
Oracle,
SQL Exchange,
E h
O l or SharePoint
Sh P i t
No installation required on certain clients
NDMP, SnapVault, or OSSV (NetApp) servers
Virtual machines protected using Agentless features
15
DPX Client Install: Windows Prerequisites

Chkdsk/Defrag/BEXCHKDSK
Install / enable iSCSI initiator
(Optional) Install Java
Required to launch the DPX Management Console from the
client
(Optional) Install Adobe Acrobat Reader, if not present.
required to be able to run the reports on the host which is
running the DPX Management Console.
If a 2003 host, install Microsoft fix KB925336 to prevent
getting this error during DPX Installation
Installation, and reboot before
installing DPX:
16
Page 2- 8
DPX Client Install: Windows

Use the correct executable
different for 32- and 64- bit versions
The client-only executable can also be used
Choose installation location (SSPRODIR)
Default is C:\Program Files\DPX
((Optional)
p
) Add Node to the Enterprise
p
Requires the Master Server to be already installed
17
DPX Client Install: Windows

(Optional) Choose additional components to be
installed on the client
Virtualization
Vi t li ti P
Proxy S
Server
18
Page 2- 9
DPX Client Install: Unix / Linux Install

Run the installation using the .bin files
Select the installation directory
Default location is /opt/DPX
Select the component to be installed
19
DPX Client Install: Unix / Linux Install

Add the client to an DPX Enterprise
To an existing or a new Node Group
20
Page 2- 10
Lab Exercise
Lab 2-2: Installing DPX Clients
Duration: 30 mins
21
Lesson 3
22
Page 2- 11

Installed automatically on the Master Server
Can be accessed from any node in the DPX Enterprise
Default Administrator: sysadmin
Used to configure the DPX Enterprise
23
Configuring DPX Enterprise
Change Enterprise name

Change sysadmin
password.
Add Node Groups and
Nodes
24
Page 2- 12
DPX Enterprise
Enterprise : set of all DPX components
Node Groups
Device Clusters
Media Pools
25
Node Groups
Node Group A logical grouping of nodes
Node Each host running DPX
Node Groups are logical
No relationship with backups or recoveries
Typical Node Groups are based on:
Physical / Geographical Location
Business Function
OS type
Operational Responsibility
Nodes can be moved across groups
26
Page 2- 13
Nodes
Each Node must belong to a Node Group
2 methods to add Nodes to a Node Group
During DPX Client installation
Using the DPX Management Console
Backup jobs are defined at the Node level
Nodes without a Client installation
NAS (NDMP) devices
pp storage
g systems
y
NetApp
SnapVault Secondary, SnapMirror Secondary
27
Adding DPX Client Nodes via Management Console

In Configure > Enterprise,
highlight Node Group, right
click and choose Add Node
Then provide name and
networking details
28
Page 2- 14
Knowledge Check
1. Which two components are installed as part of an DPX
Installation?
2. Which type of Windows operating systems are supported
for the DPX Master Server?
3. Differentiate Evaluation Keys from Emergency Keys.
4. How many Emergency Keys can be downloaded per
year?
?
5. What are the recommended pre-requisites when
installing DPX client on a Windows host?
29
Lesson 4
Upgrading Clients and

Applying Patches
30
Page 2- 15
DPX Auto Upgrade

Major Version push upgrade for Windows and Unix
clients running DPX (not suitable for all node types e.g.
Clusters)
This is distinct from Autoupdate, which is used to push
patches to nodes in the DPX enterprise (discussed next)
Run autoupgrade.bat, located in the root directory of the
DPX DVD
Supply master server name and password
Choose which nodes to upgrade
Execute
31
DPX Autoupdate System

Patching Servers can be controlled
by the DPX Management Console,
in the Help, Autoupdate DPX
Screen
Manual moving/renaming/etc is not
necessary, but as DPX patches
are delivered as java .jar files they
can be manually executed if
desired.
DPX patches are versioned

allowing the update system to track
and
d selectively
l ti l update
d t clients
li t
Updates will continue to be
cumulative with all modules
included in each package, so only
the latest patch need be applied.
32
Page 2- 16
DPX Autoupdate System
33
Lab Exercise
Lab 2-3: Applying DPX Updates
Duration: 15 mins
34
Page 2- 17
Lesson 5
DPX Services and

Processes
35
DPX Services - Windows Host

The following services can be started / stopped via
the Windows Control Panel:
Syncsort DPX CMagent Service

Syncsort DPX Advanced Protection Manager
Syncsort DPX Web Server (Master Server only)
Syncsort DPX Autoupdate Agent
The BEXsvc command-line utility can also be used

to stop the services
36
Page 2- 18
DPX Services UNIX/Linux host

Show Running Services
SSPRODIR/bin/bexps
Starting DPX
cmagent:
nibbler:
SSPRODIR/misc/sscmagent start
SSPRODIR/misc/bexads start
nibbler is process used for advanced client functionality
Stopping DPX
cmagent:
nibbler:
SSPRODIR/misc/sscmagent stop
SSPRODIR/misc/bexads stop
37
Lesson 6
Configuring NetApp
Storage for DPX
38
Page 2- 19
NetApp Storage System Setup

1. Verify Licensed Features
2. Check Services
3. Initialize Disks
4. Create Storage Aggregates
5. Create Storage Volumes
* Steps 1 through 4 are usually performed by a NetApp Storage Administrator
39
Connecting to NetApp Storage System

First, connect to the NetApp Storage System
2 ways to connect:
Command Line Interface via Telnet / PuTTy / SSL
NetApp System Manager / OnCommand System
Manager (Recommended Method)
Note: Most, but not all configuration parameters can currently be checked /
set in System Manager
40
Page 2- 20
Connect Using the CLI

Telnet / PuTTy to the NetApp Storage System
telnet <hostname_of_FAS>
Log in as root
From the login prompt, type license
Lists all the licenses for the services and their
appropriate keys (if licensed)
To update a license key
key, type license add sv_ontap_sec
sv ontap sec
<code>
<code> is the actual key associated with the
sv_ontap_sec service
41
Connect Using NetApp System Manager

Download and install the application to your Windows
Workstation (NSM can be obtained from the NetApp
website)
Launch the Application and discover all NetApp devices
on the Network.
42
Page 2- 21
NetApp Storage System Setup Licenses

Verify the licenses on the NetApp Storage System
(backup destination)
SnapVault ONTAP Secondary *

FlexClone *
iSCSI *
ASIS
NearStore Option
* Required for DPX
43
NetApp Storage System Setup Services

Enable and setup the needed services on the Storage
System :
>
>
>
>
ndmpd on
option ndmpd version
option ndmpd version 4
options ndmpd.access all
>
>
>
options snap
snapvault.access
a lt access all
options snapvault.enable on
options httpd.admin.ssl.enable on
44
Page 2- 22
NetApp Storage System Setup Services

HTTPD
options httpd.enable on
iSCSI
options iscsi.enable
iscsi enable on
Tape
options tape.reservations scsi
FTP
options ftpd.enable on (for log collection)
SSH
options ssh.enable on (for scripts)
If Storage System indicates that SSL must be configured,

> secureadmin setup ssl
respond to prompts
then enable the option above, again
45
NetApp Storage System Setup - Storage Volumes

User accessible areas on the Storage System
Used to store DPX backups
FlexVols (with space reservation set to None) should be used
for DPX deployment
As a general rule, a storage volume should be created when
a backup job is defined
Recommended to reserve at least 10% of each aggregate for
administrative overhead
Consider A-SIS deduplication overhead as specified by
NetApp
46
Page 2- 23
NetApp Storage System Setup - Storage Volumes

Clear the snapshot schedule for each volume
Configure A-SIS on each volume by using command
line
li
For each volume individually, turn on A-SIS
sis on /vol/<volume_name>
For each volume individually, turn off the A-SIS
schedule
sis config -s - /vol/<volume>
47
Lesson 7
Adding NetApp Storage to

an DPX Enterprise
48
Page 2- 24
NetApp Secondary Storage in DPX

No DPX Client installed on the NetApp Storage
System (NDMP node)
Each NetApp Storage System must be added as a
Node to the DPX Enterprise to use as a destination
A proxy node is used for NDMP nodes
Usually it is the Master Server, can be other Nodes too
Add SnapMirror Secondary nodes also
NDMP nodes must be added manually using the DPX
Management Console
49
Adding NDMP Nodes to DPX Enterprise

From Configure > Enterprise, highlight the Node
Group and click Add Node
Change Access
Method to NDMP
Client Node is
usually your
master server
Default Port No is
10000 for NDMP
Specify root
username and
password for FAS
50
Page 2- 25
Adding NetApp Storage Systems to DPX

Click Test to check
NDMP connectivity to
NetApp Storage System.
If this fails, check:
1. Resolvable Node
Name or IP address is
correct
2. Login information is
correct
3. Ndmpd status on
storage system
When it succeeds, click
Add
51
Ensure dump is
selected for Backup
type and click OK
52
Page 2- 26

Node is
successfully
added to the DPX
Enterprise
53
Catalog
The Catalog is the heart of an DPX Enterprise and is essentially
just a set of files stored on the master server
For Windows Master Servers the default Catalog Location is:
...\DPX\db
...\DPX\sched
...\DPX\cat
And for Unix/Linux:
/opt/DPX/db
/opt/DPX/sched
/opt/DPX/cat
54
Page 2- 27
Catalog
Every time you perform a backup or make a configuration
change to your Enterprise, the Catalog is updated
In particular, a backup job updates the Catalog with
information identifying the location of every
node/volume/file that has been backed up. This
information is crucial during restores
Because the Catalog is so vital to DPX,
DPX it needs to be
properly maintained. To maintain the Catalog, you should
regularly perform essential Catalog operations
* We will discuss in detail about DPX Catalog Maintenance in a later module
55
Lab Exercise
Lab 2-4: Configuring NetApp

Storage for DPX
Duration: 20 mins
56
Page 2- 28
Knowledge Check
1. Which NetApp licenses are required on the secondary
storage system to be used as a destination for DPX
backups?
2. What are the recommended best practices when
enabling ASIS on a volume?
3. What must be the Access Method attribute set to when
adding a NetApp storage system as a node to the DPX
Enterprise?
4. Which port is used, by default, for NDMP?
57
Module Summary
E
Explain
l i th
the major
j steps
t
required
i d tto install
i t ll and
d
configure an DPX Enterprise
Perform an DPX Master Server and Client installation
Start and log in to the DPX Management Console
Update all nodes using the Autoupdate feature
Recognise, start and stop DPX Services on various
client
li t types
t
Add and Configure Node Groups and nodes, including
NetApp Storage Systems, in the Enterprise
Discuss the DPX Catalog
58
Page 2- 29
Module 3 Configuring DPX Backups
C fi
Configuring
i
DPX B
Backups
k
Module Objectives
Differentiate NetApp SnapVa
SnapVault
lt and Open S
Systems
stems
SnapVault from Syncsort Advanced Recovery
SnapVault
Describe how SnapVault backups work
Define, save, run and monitor an DPX backup job
Create different types of schedules for a backup job
Discuss the implications of modifying a backup job
Module 03 - Configuring DPX Backups
Page 3 - 1
Lesson 1
NetApp SnapVault and

OSSV
What is SnapVault?
A disk-based backup technology by NetApp
Initially developed for NetApp Storage Systems
And
A d th
then ffor other
th open systems
t
servers that
th t use
block-based data transfer
Uses snapshots and asynchronous mirroring to
create an incremental-forever backup scheme
Protects data residing on a hosts primary storage by
maintaining a number of read-only versions of that
data on a SnapVault secondary system
Destination for the backup (SnapVault Secondary) is
always a data storage system running Data ONTAP
Page 3 - 2
Benefits of a Block-level Data Transfer

Fast compared to File level transfers, especially in
small-file environments
Low resource utilization (memory and CPU)
Transfers only changed blocks as part of incremental
backups
Not the entire file, as is the case for file level
incremental backups
Vastly reduces the amount of data that needs to be
backed up and therefore can greatly reduce overall
backup times
Benefits of a Block-level Backups - Recovery

The SnapVault secondary constructs a full backup,
referred to as a synthetic base, out of the Block-level
Incremental backup,
backup but uses only the size of the
incremental changes for storing this image
When recovering data using these incrementals
there is no need to mount multiple images (tapes).
Everything can be recovered from the last incremental
p
back completed
Page 3 - 3
SnapVault Backup Types

SnapVault (SV)
NetApp software
Used for NetApp
pp System
y
to NetApp
pp System
y
backups
p
Open System SnapVault (OSSV)
NetApp software
Open systems to NetApp System backup
Agents available for Unix / Linux / Windows
DPX Client
Syncsort software
a.k.a. Advanced Recovery SnapVault (ARSV)
Syncsort Client (currently only Windows, Linux and Solaris)
to NetApp System Backup
Adds considerable functionality above OSSV agent
7
SnapVault Backup Types (contd)

Mode
Vendor
Source
Destination
Purpose
Requirements
SnapVault
NetApp
NetApp
Storage
System
(Primary)
NetApp
Storage
System
(Secondary)
Block-Level SnapVault
Backup of NetApp
Systems to NetApp
System
NetApp SV Primary
and Secondary
Licenses
Open Systems
SnapVault
(OSSV)
NetApp
NetApp
Open
Systems
Clients
NetApp
Storage
System
(Secondary)
Backup of non-NetApp
systems to NetApp
System
NetApp OSSV Client

& NetApp Secondary
licence
DPX Advanced
Recovery for
SnapVault
(ARSV)
Syncsort &
NetApp
DPX
Advanced
Clients
NetApp
Storage
System
(Secondary)
Backup of non-NetApp
systems to NetApp
System
DPX Advanced
Client & NetApp
Secondary License
Page 3 - 4
SV Terminology
SnapVault Snapshot
Point in time image of a dataset that SnapVault creates on its
primary and secondary nodes
SnapVault Primary
A system whose data is to be backed up (client)
SnapVault Secondary
NetApp Storage System to which the data will backed up
SnapVault Relationship
The backup relationship between a QTree on the primary node
(or a directory on a open system (OSSV) primary node) and its
corresponding secondary node Qtree
DPX Advanced Recovery
DPX Advanced Client Software
SnapVault Backup
1. For the first backup, a complete copy of the source data
is transferred to the secondary device (Base)
2. Subsequent backups only transfer data blocks modified
since the last backup (Incremental)
3. No further Base backups are ever run
This is the Incremental-forever backup scheme
10
Page 3 - 5
Block Level SV Backup Process

Backup Client (SV Primary)
NetApp SV Secondary
Snapshots
Full Backup
9am
9am
9am
Snapshots
Incremental Backup 10am

10am
9am
10am
Snapshots
Incremental Backup 11am

11am
9am
10am
11am
11
SnapVault Snapshots
The backups are stored in the WAFL (Write Anywhere File
Layout) file system
A snapshot is created at the end of each backup
SnapVault takes advantage of the snapshotting capability
of the WAFL filesystem in ONTAP
Maximum of 250 snapshots per volume can be stored at
any one time
Snapshots are always made at the volume level
All managed from DPX Management Console
12
Page 3 - 6
SnapVault Snapshots (contd)

Each Snapshot consumes an amount of disk equal to
the difference between itself and the previous
snapshot
Example:
1st Backup transfers 200GB of data
10GB of modified blocks in the primary since first
backup
2nd
Backup
2 dB
k transfers
t
f
10GB off data
d t
Total space on the secondary being used: 200GB +
10GB
* A-SIS deduplication can further reduce storage consumption
13
SnapVault & DPX

DPX allows management of NetApp SV and OSSV backups
and restores through the DPX Management Console,
including scheduling, retention period, source, destination
etc.
However, only NetApp SnapVault relationships created in
DPX can be managed in DPX. Other SnapVault
relationships, such scheduled snapshots created by
NetApp Storage systems, cannot be imported into DPX.
DPX Advanced Client provides significant additional
functionality over the NetApp OSSV agents for Windows,
Linux and Solaris
These used to be known as SSSV (Syncsort SnapVault)
Clients and now as DPX Advanced Client.
14
Page 3 - 7
OSSV Primary Nodes

OSSV agents for these platforms
are currently available to
download from the NetApp NOW
site
These are handled by DPX as if
they were a SnapVault Primary
Storage System device i.e.
NetApp Storage System running
DATA Ontap, and added to the
DPX Enterprise in the same way
as any other NDMP node
DPX Agents
Windows, Linux & Solaris
Installed as part of the DPX
Client installation - no additional
configuration is required
15
Adding a NetApp Device to the Enterprise

If a NetApp Storage System is licensed as a SnapVault Primary or
Secondary Device (NetApp license), this information will be
displayed in the Management Console after the node is scanned in
If the node is a SV Primary, the Management Console displays
If the node is a SV Secondary, the Management Console displays
16
Page 3 - 8
SV Backup Data Selection (NetApp - NetApp)

1.
Go to
Backup >
Advanced
Recovery
Recovery
2.
Select
NetApp
volume to
backup
3.
Select
NetApp
Storage
System
Volume as
destination
Note: The management Console will only display SnapVault primary

and secondary nodes in the SnapVault Window. All other nodes are
filtered out
17
Non-Qtree Data
Non-QTree data is any data on a Storage System that is not
contained in its QTrees. Non-QTree data can include
Configuration and logging directories on the Storage System
(for example, /etc or /logs) that are not normally visible to
Storage System clients
Directories and files on a Storage System volume that has
no QTree configured
Use logical object non-QTree data for backup selection.
Note
The non-QTree part of the primary storage system volume can be
replicated only to the SnapVault secondary storage system. The
data can be restored to a QTree on the primary storage system,
but cannot be restored as non-QTree data.
18
Page 3 - 9
OSSV Backup Data Selection

Select OSSV data volume(s) to backup
Select NetApp Storage system volume as a destination
19
Knowledge Check
1. What are the two data protection technologies
offered by NetApp?
2. Differentiate SnapVault and Open Systems
SnapVault (OSSV).
3. Which data protection software offers the Advanced
Recovery for SnapVault (ARSV) agent?
4. Which operating systems are currently supported
by the DPX Advanced Client?
20
Page 3 - 10
Lesson 2
DPX Advanced Client
21
SnapVault Backup Types

During this next section we will cover the Advanced Recovery
for SnapVault agents from Syncsort
Mode
Vendor
Source
Destination
Purpose
Requirements
SnapVault
NetApp
NetApp
Storage
System
(Primary)
NetApp
Storage
System
(Secondary)
Backups of NetApp
Systems to NetApp
System
NetApp SV Primary
and Secondary
Licenses
Open Systems
SnapVault
(OSSV)
NetApp
NetApp
Open
Systems
Clients
NetApp
Storage
System
(Secondary)
Backups of non-NetApp
systems to NetApp
System
NetApp OSSV Client

& NetApp Secondary
licence
DPX Advanced
Recovery for
SnapVault
(ARSV)
Syncsort &
NetApp
DPX
Advanced
Clients
NetApp
Storage
System
(Secondary)
Backups of non-NetApp
systems to NetApp
System
DPX Advanced
Client & NetApp
Secondary License
22
Page 3 - 11
DPX Advanced Recovery

Syncsort developed a SV agent for Windows that has
improved functionality and performance benefits over
the current Windows OSSV agent from NetApp,
including:
Block-level, full and incremental backups
DPX Instant Access (iSCSI mapping of any ARSV
backup)
DPX BMR (Bare Metal Recovery from any ARSV
backup )
Virtualization restore capabilities with Instant
Virtualization (IV) and Full Virtualization (FullV) options.
Installed as part of DPX Client with no further
configuration required
23
DPX Application & Database Support

Special care needs to be taken when backing up partitions
that contain databases since database integrity cannot be
guaranteed if the backup is done without interfacing
directly with the database
The DPX Advanced Client supports online (hot) backups
and restores of these applications (on supported
platforms):
Exchange
SQL Server
SharePoint
Sh P i t
Oracle
These are constantly being updated. Please check with the
latest DPX Compatibility Guide
24
Page 3 - 12
DPX Backup Data Selection
Application Aware for SQL,

Exchange, SharePoint and Oracle.
This object points to the images
(disks) that house the database
BMR/ExpressDR object points to the

images (disks) that house the
operating system. This object must
be included in order to perform BMR
or Virtualization type recoveries
25
Stages of an Advanced Recovery SV Job

1. Create a Snapshot per Logical Drive on the
Primaries
2. Data Movement Phase (Create Relationship if Initial
Backup)
3. Create Snapshot on Secondary Volume(s)
4. Catalogs Data (add data to DPX Catalog)
26
Page 3 - 13
DPX Filter Driver

The filter driver keeps track of blocks that change while the
backup job runs
If a block on the active file system changes, during a
backup job, but after the original snapshot, the
snapshotted block is copied to cache before the block
gets updated by the application
The backup job will read the cached as well as unchanged
blocks and copy them to the Secondary
At the conclusion of the backup job
job, the snapshot is
deleted, and the cache is cleared
The size of the cache is a function of the number of blocks
that change during the period of backup
27
Incremental Advanced Recovery SV Backups

After the SnapVault relationship is created, a Change
Journal is started on each logical disk on each Primary.
This Change Journal keeps track of the blocks that change
on the given logical drive.
When a subsequent ARSV backup job starts, DPX knows
which blocks have changed since the last backup job, and
these blocks are then copied over to the secondary.
The QTree on the Secondary is updated with these blocks,
and a snapshot is taken of the volume that contains the
Qtree.
28
Page 3 - 14
Checkpoint Restart
Checkpoint Restart is supported within the context of
a backup job (failed jobs will not be retried)
The failed task will continue from the last checkpoint
taken
Checkpoints are taken every 128MB (configurable)
The behavior is controlled by the DPX Job Options
Down Node Retries: how many times should the task
(relationship) be retried
Task Retry Interval: what should be the interval (in
minutes) between retries
29
SnapVault Backup Definition - ARSV Agents

Source: Logical Object (C:, D:, SQL:, ExpressDR: etc)
Destination: NetApp Volume (through the DPX
Console)
DPX creates QTrees under the selected Volume
Each logical drive (C: D: etc.) is backed up to its own
QTree
If source is a logical drive (C: D: etc.) the names of
these corresponding QTrees contain the jobname,
hostname and diskID
Each of these QTrees contain two files:
BEXimage.raw: image backup of the entire disk
BEXimage.toc: table of contents (block-to-file
mapping) of the disk
If source is an application (SQL:, EXCHANGE:) or
ExpressDR: a single QTree (called APPS) is created
and its name contains the jobname and hostname
This QTree contains metadata associated with
the application
30
Page 3 - 15
SnapVault File Structure on Secondary

Volume
(SnapVault
Destination)
SnapShot
Folder
Latest
SnapShot
Volume
Contents
att SnapShot
S
Sh t
Time
QTrees
(SnapVault
Destination)
31
Advanced Recovery SV Backup Data Selection

Select Source: Logical
Object (C:, D:, SQL:, BMR:
etc))
Select SV destination
volume on secondary
BMR/ExpressDR - points to
the images (disks) that
house the operating system
EXCH / SQL etc point to the
images (virtual disks) that
house the application and all
its data
Select whole node for
complete protection with all
recovery options
32
Page 3 - 16
Lab Exercise
Lab 3-1: Performing DPX Backups

Duration: 45 mins
33
Lesson 3
Configuring DPX Jobs
34
Page 3 - 17
Backup Jobs - [Sources] / [Destinations]

Various backup schemes
Traditional Scheme 1 Source : 1 Job : 1 Destination
New Scheme N Sources: 1 Job : 1 Destination
Recommended to use the new scheme (N:1:1) to take
advantage of NetApp de-duplication
Each node selected within [Sources] can go to the same
or different [Destinations] if the filer has multiple target
volumes.
35
Backup Jobs - [Sources] / [Destinations]

DPX is a job based data protection product, not a host
based.
Each job including a host will have its own base and
incrementals of that host.
Even if a job expires all instances of a job out of the
catalog, the last full will be kept on disk until the job is
deleted.
deleted
36
Page 3 - 18
Backup Jobs - [Multiple Destinations]

Select the
destination for the
backup job.
If multiple nodes
have been selected
in the [SOURCES],
it is possible that
each node can go to
a different target
destination.
Right click on each
node to View
Destination.
37
Implications of a New Job Name

Creating a new job name will force a new base.
A new relationship is established in the Qtree,
therefore there will be no indication that the job has
been backed up before.
Editing an existing job to reflect a new destination will
also force a new base since there is no indication of
an existing relationship on the destination that a job
has been backed up before.
38
Page 3 - 19
Lesson 4
Scheduling DPX Jobs
39
Schedule
A backup job can be run
interactively or scheduled to
run once, hourly, daily,
weekly or monthly
weekly,
monthly.
A scheduled job can have
multiple schedules of
different schedule types, all
with the same or different
retention periods.
NB - Be sure to click Apply
to save any changes made
on these Scheduling
Screens.
OK closes the screen, but
not save changes made.
40
Page 3 - 20
Schedule - Once
Use Once to run a
backup at a specified
date and time with a
specified retention
period
41
Schedule - Hourly
Hourly Schedules allow
q
backups
p
more frequent
for mission critical
servers / applications
Example shows
backups configured for
every 2 hours by using
two separate hourly
schedules
42
Page 3 - 21
Schedule - Daily
Daily schedules allow
p to run every
y
backups
day at the specified
time(s)
Example shows a
backup configured for
every day at 11pm,
y
retention 7 days
43
Schedule - Weekly 1
Use Weekly Schedules
((Select Weeks)) to
configure backups to run
on only certain days of the
week or month.
Example shows a backup
to be run:
Sunday Friday at 11pm
with retention of 7 days
Saturday with a retention
of 30 days
44
Page 3 - 22
Schedule - Weekly 2
Use Weekly Schedules
((Weekday
y in Month)) to
configure backups to run
on only certain days of the
month.
to be run:
Monday Friday at 11pm
with retention of 7 days
The last Saturday of the
month with a retention of
30 days
45
Schedule - Monthly
Use Monthly Schedules to
g
regular
g
monthly
y
configure
backups with long
retention periods
to be run:
Last day of the month
with a retention of 365
days
46
Page 3 - 23
Schedule - Exceptions
Exceptions can be set for
a particular date and
point in restore.
A date can be selected
from the calendar.
Example shows
Christmas and Boxing
Day exclusions
Or on configured Holiday
(Set
Configure,
(S t iin C
fi
Holidays)
47
Schedule - Preview
The preview screen
allows the user to see
the current job and all
jobs scheduled to run in
DPX on a particular day
A date can be selected

within the calendar to
view the run times.
48
Page 3 - 24
Lesson 5
DPX and Deduplication
49
Using NetApp Deduplication

What is Deduplication?
Reduce storage needs by eliminating redundant data
NetApp A-SIS(Advanced Single Instance Storage)
Deduplication on Secondary Storage
ONTAP 7.2 and higher
Volume level
p
y and at specific
p
Scheduled on specific
days
times
Automatically, when 20% new data has been written to
the volume
A-SIS needs to be enabled
50
Page 3 - 25
Definitions
Target-side
Deduplication
identifies redundant streams of data and eliminates the

duplicates
p
at the destination ((after backup
p data transfer))
Client-side
Deduplication
using hash algorithms, identifies redundant data only

transfers non-redundant data
Source-side Data
Reduction
transfers only the changed blocks from the data source
Single Instancing
identifies like files and eliminates them at the destination
Compression
compresses each file as it is written to disk
51
Using NetApp Deduplication

Installing and Licensing Deduplication
Deduplication is included in Data ONTAP and just
needs to be licensed.
licensed Add the deduplication license by
using the following command:
license add <a_sis license key>
To run deduplication on any of the FAS platforms, you
also need to add the NearStore option license:
license add <nearstore_option license key>
Once the license is added enable A-SIS on required
volume
sis on <vol>
52
Page 3 - 26
Deduplication Solutions the Full Picture

Traditional Backup Software with Dedupe-Appliances
Changedfiles
CPUUtilization
DedupeAppliance
3rd PartyStorage
BU&Recovery
Hours
DPX with Dedupe-Appliances or Storage-Arrays with Deduplication

Onlychangedblocks
3rdPartyStorage
CPUUtilization
DedupeApplianceor
StorageArraywithDeduplication
BU&Recovery
Mins
53
DPX and NetApp Deduplication

Traditional scheme
One Server One Job One Destination Volume
Recommended scheme
N Servers One Job One Destination Volume
Enabling A-SIS on a Secondary volume already
containing data will only show a gradual space
savings over time
Enabling on an empty SnapVault volume, the space
savings are realized on the initializing transfers itself
and can be significant
54
Page 3 - 27
DPX and NetApp Deduplication (contd)

How does it work?
S
SnapVault
V lt d
data
t ttransfer
f operations
ti
are iinitiated
iti t d as per th
the
defined job schedule
When all data transfers are complete, a new snapshot is
created on the secondary volume - ex. SSSV_myjob.0
An A-SIS run is automatically triggered at this time.
Once the A-SIS run has completed any identified duplicate
blocks are coalesced and a new snapshot is created. The
original SSSV_myjob.0
SSS
0 snapshot is deleted and the new
snapshot is renamed as SSSV_myjob.0
The job will then proceed to completion using the A-SIS
snapshot as the final backup instance
55
Pre-Implementation Considerations
Design Considerations
Maximum number of data streams
Restrictions
R t i ti
on the
th volume
l
size
i if deduplication
d d li ti is
i tto b
be
enabled on that volume
Maximum number of snapshots on volume is limited to 255
Only 250 are usable on a SV Secondary volume
Maximum Qtrees per volume
Depends on the ONTAP version
at itt means
ea s to DPX?
What
Number of parallel data streams limits the number of servers
a job can have OR two jobs that may overlap can have
Stream = volume/disk (plus an additional stream for APPS)
Retention policy of snapshots on volume
56
Page 3 - 28
Module Summary
Explain features of NetApp SnapVault, NetApp Open
S t
Systems
SnapVault
S
V lt (OSSV) and
d Advanced
Ad
d Recovery
R
SnapVault (ARSV)
Describe how SnapVault backups work
Understand the considerations in configuring
SnapVault Secondary storage
Define, save, run and monitor an DPX backup job
Create
backup
C t different
diff
t ttypes off schedules
h d l ffor a b
k job
j b
Discuss the implications of defining a new job name
and/or new destinations
57
Page 3 - 29
Module 4 Protecting MS Clusters using DPX
Protecting
P
t ti
MS Clusters
Cl t
with
ith
DPX
Module Objectives
Discuss the basics of Windows Cluster Data Protection
with DPX
List the Installation Requirements for DPX on MS
Clusters
Explain how to backup and restore Local and
Clustered Volumes
Explain the Failover process in Windows Clusters
Module 04 - Protecting MS Cluster with DPX
Page 4 - 1
Windows Cluster
Physical view
C:
Local Disk
D:
C:
D:
Heartbeat
FC Switch
Shared Disks
for the Cluster
3
Windows Cluster
Logical View of Volumes
C:
D:
C:
D:
G:
H:
L:
Page 4 - 2
Windows CCR Cluster or Exchange 2010 DAG

Physical view
Local Disk
C:
D:
C:
D:
Heartbeat
FC Switch
Replicated Disks
for the Cluster
5
Windows CCR Cluster or Exchange 2010 DAG

Logical View of Volumes
C: D: G: H: L:
C: D: G: H: L:
Page 4 - 3
Installation Summary
Cluster services must be up and running
Install DPX on every
y physical
p y
cluster node
Configuration questions will be asked during the installation
(available IP addresses etc)
Required changes will be made to the cluster - Backup Express
group will be created and brought online
An available IP address must be provided at install time for the
Backup Express cluster resource
The Backup Express cluster resource must be able to run on all
nodes in the cluster
DPX Client Cluster Installation Prerequisites

You must
understand the
existing
g clusters
networking
resources:
Determine the name
of the PUBLIC
network being utilized
by all nodes in the
cluster.
Obtain an un-used IP
Address on this
network to assign to
the DPX Virtual
Node.
Page 4 - 4
DPX Client Cluster Install

The DPX Client Install is a cluster aware application and automatically
detects the presence of cluster services running on the node (For Client
installation only) and presents some additional screens

Specify the Logical Node Name of this node and the Cluster Node Group
Name to use for this installation
10
Page 4 - 5

Enter the AD authentication
information. Must be a
Domain Administrator
Enter the IP
Address and
subnet mask you
have obtained for
the DPX Virtual
Node
From pull-down,
select the public IP
of the physical
node
From pull-down,
select the name of
the public cluster
network
11
DPX Cluster Configuration
Cluster now
shows the DPX
Cluster Service
Group
And DPX Cluster

Resources
12
Page 4 - 6
Windows Cluster in the Management Console

Cluster is
automatically a
Node Group
p
Virtual Node with
shared resources
Physical Node1
with local
resources
Physical Node2
with local
resources
13
Scanning in Cluster Nodes

You can scan in nodes already
have the DPX Client installed.
Under Configure > Enterprise,
Right-click on a node group and
select Add node.
Populate the fields for one of the
physical nodes in the cluster:
Logical Node Name (displayed
name in
Managementt C
Console
i M
l
to represent the node)
Resolvable Node Name or IP
Address
Click Add
14
Page 4 - 7
Scanning in Cluster Nodes (Resolvable Node name)

For any host, not just clustered nodes, Resolvable
Node name must either be:
A DNS or hosts
h t file
fil resolvable
l bl hostname,
h t
or
The IP Address of the host
15
Scanning in Cluster Nodes
Scanning in after local installation will automatically add

virtual and other cluster node(s)
16
Page 4 - 8
Scanning in Cluster nodes (Logical Node Names)

When scanning existing nodes into the enterprise, you have two
options as to how they will be displayed in the Management
Console:
BEX_
Set Logical Node Name to Host Name
y enter the Logical

g
Manually
Node Name to
what ever you want (IP Address,
Hostname, Application, Usage, etc.)
17
Cluster Awareness - Windows

Management Console represents the Virtual Node in a
Windows Cluster with the shared resources under it
as well as the BMR and Application Objects (SQL,
Exchange or Oracle)
Management Console represents the Virtual Node in a
Windows CCR Cluster or Exchange 2010 DAG with
only the BMR and Application Objects (SQL,
Exchange or Oracle)
If any type of failover occurs during a backup or
recover job, the job will fail. Once the failover has
completed, the job can be manually restarted or it will
re-run at next scheduled time.
18
Page 4 - 9
Cluster Object Selection for Backup Jobs

Microsoft Cluster and CCR Cluster:
Best practice is to protect all BMR objects on the physical nodes, and
all objects in the virtual node in one job to one NetApp volume.
If physical nodes have local resources to protect
protect, then they can be
selected, as well. The OS drive, System State and System table are
automatically backed up with just the BMR object.
Microsoft CCR Cluster (only):
After a failover to the inactive node, a new base of data will be created
due to the new volumes being active.
Microsoft Exchange 2010 DAG:
For each node, create a separate job and select:
BMR object under the physical
The hosts resources under the virtual node.
During failover, the job will fail until resources are moved back.
Recommendation is to create a new job with the new configuration if
backups are needed during this time or if it is a permanent change.
This way the old job, once all instances are expired from disk, can be
deleted so that storage is freed up on disk.
19
Microsoft Exchange 2010 DAG Backup Job Selection Example

Job name: ClusNode1
Select ClusNode1 under the
virtual node BEX_ExchCL to
select all active DBs for this
node
Select the BMR object under
the ClusNode1 physical node
The destination will be a
separate NetApp volume for
each physical nodes job.
Create a second job for
ClusNode2 and the virtual
resources of that node.
20
Page 4 - 10
Module Summary
Discuss the basics of Windows Cluster Data Protection
with DPX
List the Installation Requirements for DPX on MS
Clusters
Install the DPX Client Software in a Microsoft Cluster
Environment
Explain
how tto backup
Locall and
E l i h
b k and
d restore
t
L
d
Clustered Volumes
Explain the Failover process in Windows Clusters
21
Page 4 - 11
Module 5 DPX Advanced Recovery Options
DPX Ad
Advanced
dR
Recovery
Options Overview
Module Objectives
By the end of this module, you will be able to:
Describe the various recovery options for data,
applications, volumes, servers, virtual machines and
sites that form part of the DPX Advanced Recovery
Suite.
Module 05 - DPX Advanced Recovery Options: Overview
Page 5 - 1
DPX Advanced Recovery Overview

Whats covered next?
Restoring Files and Folders
DPX Instant Access (IA)
DPX Application Recovery for Exchange, SQL and
SharePoint
DPX Bare Metal Recovery (BMR)
DPX Instant and Full Virtualization, with Rapid Return
to Production (RRP)
DPX Tertiary Data Protection using DPX+ Tape
DPX Disaster Recovery Options using Alternate
Secondary Nodes
DPX Agentless VMware backup and restores
3
One Solution for Multi-Tiered Data Recovery

Restore selected
folders and files
from catalog
File
Recovery
DPX
Application
and Item
Recovery
Exchange, SQL,
Oracle, SharePoint
Base
Block update
Server
Recovery**
R
**
C:\
D:\
OS and Data
Block update
Block update
Site
Recovery**
** Agentbased/Agentless
Integrated DR
SnapMirror
4
Page 5 - 2
File Recovery
Ability to perform file-level restores from snapshots
Catalog-based file search and restore
Search based on file name, type, size, etc
10:00 Snapshot
File
11:00 Snapshot
12:00 Snapshot
Searchable
catalog
DPX
Application & Volume Recovery - Instant Access

Map to any snapshot in seconds
Readable/writeable image
Rapid return after corruption, deletion, etc.
NetApp FAS
Application
G:\
Data is LIVE!
10:00 Data Image
11:00 Data Image
Mapping
request
Application Data
12:05
12:00 Data Image
DPX
G:\
12:12
12:10
8:00
Repair Hardware
Failure on
Application Server
Select
desired
Recovery
Point
Map Server
to SnapShot.
Server is
back on-line!
Scheduled downtime of
Server to resync secondary
storage to primary storage
6
Page 5 - 3
Server Recovery - Bare Metal Recovery

Restores the entire system image
Supports dissimilar hardware recovery
Migrates from virtual to physical
Master Server not required for BMR
NetApp FAS
1. CD Establishes
communication
DPX Recovery
CD or ISO image
10:00 Data Image
11:00 Data Image
12:00 Data Image
2. Copies
data
12:05
Server HD Failure
Occurs
12:20
Replace Hard Drive

& Boot from
DPX BMR CD
12:25
12:32
12:40
Select
desired
Recovery
Point
Recover
Server Image
Reboot server
and restore
complete!
7
Application & Server Recovery - Instant Virtualization

Instantly creates bootable VM for RTO of minutes
No immediate data migration, only mapping
Use for recovery, DR testing, development, etc.
Supports P2V and V2V
NetApp FAS
VM of
Application
Creates VM
automatically
Backup
VMware ESX
10:00 Data Image
11:00 Data Image
12:00 Data Image
Bootable VM
Single Pane of Glass

Page 5 - 4
Application & Server Recovery - Full Virtualization

(RRP)
Creates VM, VMDK and VMX files
Brings VM online prior to migrating data
Seamless P2V, V2V migration of data in background
NetApp FAS
VM of
Application
1. Create VM
VMware ESX
10:00 Data Image
4. Storage
Vmotion
migrates
g ates disks
ds s
2. Boot off snap

g
11:00 Data Image
12:00 Data Image
3. Background
migration of data
to datastore
VMDK
VMX
Datastore
Site Recovery - Integrated Disaster Recovery

Simplified, integrated disaster recovery
Thin replication for bandwidth reduction
DPX
SnapMirror
DR Site
DPX
Recovery via
Snapshots,
Virtualization
DPX
Central Recovery
Management
10
Page 5 - 5
Agentless Recovery of VMs

VMs
Instant VMDK Restore
Instant VM Restore
VMDK
Creates a new VM from snapshot

No physical data transfer
DPX
Agentless
Backup
Full VM Restore
NetApp Snapshots
VMDK
Restores VMDK files from snapshot

Full VMDK Restore
VMDK
VMDK
Creates a new VM with full VMDKs

VM available for use instantly using
Instant VM Restore;
Data copy in background
Restores VMDK files from snapshot

VMDK available for use instantly using
Instant VMDK Restore;
Uses storage relocation
11
Module Objectives
Describe the various recovery options for data,
applications, volumes, servers and sites that form part
of the DPX Advanced Recovery Suite.
12
Page 5 - 6
Module 6 - Restoring Files using DPX
R t i
Restoring
Fil
Files using
i
DPX
Module Objectives
Perform File Level Restores using the DPX Advanced
Recovery
Page 6 - 1
DPX Restore (Windows)

Since the data structure on the secondary is an image file, a
restore job maps the file(s) to be restored to the blocks in the
image before copying the blocks to the restore destination
This allows for file level restore to original or new location, but
also additional functionality, all of which should be considered
for recovery purposes
In order to restore a file using the Catalog, File History option
must have been enabled on the backup (default is enabled)
Even with File History disabled, it is still possible to restore
individual files and folders
File Recovery
Ability to perform file-level restores from snapshots
Catalog-based file search and restore
Search based on file name, type, size, etc
10:00 Snapshot
File
11:00 Snapshot
12:00 Snapshot
Searchable
catalog
DPX
Page 6 - 2
Handling File History

File-level recoveries can be achieved using the File History
information in the Catalog
Enabled
E bl d by
b d
default
f lt
Disabling File History speeds up the backup process

Instant Access (IA) can be used to restore files when
File History option is disabled
Defining an DPX Restore Job - Source

To restore a file or
folder, select the
file or folder to be
recovered
To restore an
image or an entire
volume, select the
snapshot to be
recovered
Instant Access
(IA) might be a
better option and is
required if file
history is disabled
Page 6 - 3
Defining an DPX Restore Job - Destination

The destination can be:
The
Th original
i i l llocation
ti
An existing folder on *any* DPX client
node
File system must be the same as
that of the backed up data eg NTFS
A new folder on *any* DPX client node
Right-click on the destination
volume/folder and select Create
New Directory
DPX Restore Options and Scheduling

Restore jobs must also
be saved before running
Restores can also be

scheduled in exactly the
same way as backups
Source / Destination
Options (e.g. overwrite
existing files) can be set
here
Page 6 - 4
File restore with NDMP file history disabled

Attempting to browse a snapshot with
NDMP file history disabled will prompt
to browse the data (files) from the
actual snapshot (instead of DPX
Catalog)
Clicking OK will create a temporary

mount point in the
<SSPRODIR>\mount directory on the
selected proxy server
IA mapping
File restore with NDMP file history disabled

The mountpoint is automatically added and the filesystem is ready for
browsing and selection and you can continue your file level restore as
usual
Mount point and disk will be gone as soon as you leave the Restore
window in the DPX console
10
Page 6 - 5
Lab Exercise
Lab 6-1: Performing DPX

Restores
Duration: 15 mins
11
Module Summary
Perform File Level Restores using the DPX Advanced
Recovery
12
Page 6 - 6
Module 7 - DPX Instant Access
DPX IInstant
t tA
Access
Module Objectives
Explain the DPX Instant Access feature
Configure and use Instant Access to perform volume
mapping in order to recover data, applications,
volumes and servers in DR scenarios
Page 7 - 1
DPX Instant Access- Main Uses

Provides rapid read/write access to virtual volume images
of server disks, Oracle, SQL Server, Exchange and other
applications
As an alternative to Restore for File or Folder Recovery
Application Recovery - As part of the process for Single
Object Restore of Exchange and Sharepoint data*
Temporary Volume Recovery
Testing and Development, particularly with larger
volumes,
volumes as there is no data restoration
IA is the underlying feature used for Instant Virtualization
functionality (described in a later presentation)
* Requires separate applications
3
File Recovery using DPX Instant Access

NetApp Secondary
Storage
Windows Server Source

Local Disk
Block-level backups
9 am
D:\MyFile.txt
10 am
Copy
File(s)
Data is LIVE!
M:\
11:15 am
File Deletion /
Corruption on Server
11 am
11:20
11:22
11:25
Select
desired
Recovery
Point
Map new drive

to SnapShot.
Copy File(s)
from IA drive
M:\ to D:\
Have
additional
drive (M:)
on-line!
File(s) back
on-line!
Page 7 - 2
Volume Recovery using Instant Access

NetApp Secondary
Storage
Windows Server Source

Local Disk
9 am
E:\
F:\
10 am
E:\
FlexClone
Data is LIVE!
11 am
11:15 am
Failure on
Application Server
11:20
Select
desired
Recovery
Point
11:22
Repair Hardware
Map Server
to SnapShot.
Server is
back
on-line!
8:00 PM
Scheduled
downtime of Server
to resync secondary
storage to primary
storage
DPX Instant Access - How is it done?

Go to Restore > Advanced Recovery
Expand the node to the desired Snapshot (Recovery Point)
MAP:
MAP
iSCSI map the selected
drive to a location of your
choice.
Alternate Secondary
Node:
iSCSI map the selected drive
from a location of your choice
when an Alternate Secondary is
available
Page 7 - 3
Instant Access
The MAP function allows for the iSCSI mapping to be created on any Windows
node in the Enterprise and Drive information translated by DPX.
Node List
Select the Node to which the
drive will be mapped to
Can be any node in the DPX
Enterprise
iSCSI Initiator must be
running on this node
Mount Point List

Select the available logical
drive
the selected
d i on th
l t d node
d
that will contain the
contents of the iSCSI map
Network attached drives
will show up as available,
DO NOT select them
Instant Access
An Informational message confirms the mapping as soon as it completes.
The snapshotted E: drive from the node SQL is

now live and has as target the M: drive
contained in the selected snapshot
This data is read/writable while mapped and all

changes made to this drive are contained in a
LUN created by DPX as part of the iSCSI
operation. The original snapshot is not
modified (it is read-only).
Page 7 - 4
Instant Access
The M: drive
now points to
the selected
snapshot on the
Secondary
It appears as a
local drive to
Windows users
and applications
It is a block-level
device (iSCSI
LUN). Its not a
(file level) CIFS
share.
Instant Access
Un-mapping the
iSCSI drive
Restore
>Advanced
Recovery for
SnapVault screen
Right-click on the
node that has the
mapping and
select Show
mapped Drives
Select the drive
letter, and click
Unmap
10
Page 7 - 5
Instant Access
Lets assume the E: drive, which houses the SQL database
and logs dies on the SQL server. To perform a recovery
using IA the following steps should be followed:
iSCSI map the
th E:
E drive
d i tto point
i t tto the
th latest
l t t snapshot
h t using
i
the DPX Management Console
Replace the broken drive, and reformat it as F:
Do an Advanced Recovery restore of the latest snapshot
taken of the E: drive using the DPX software and throttle the
restore not to impact the IA operation
At the end of the restore job, the F: drive should be
recovered to the point in time of the latest snapshot. The E:
d
e will now
o house
ouse add
t o a information.
o at o Att tthis
s po
drive
additional
pointt
schedule downtime of the SQL database
With the database down, do a xcopy (or other incremental
copy) command from E: to F:
Unmap the iSCSI drive
Change F: to E: and start the SQL database
11
Lab Exercise
Lab 7-1 Performing Instant

Access
Duration: 15 mins
12
Page 7 - 6
Module Summary
Explain DPX Instant Access
Configure and use Instant Access to perform volume
mapping in order to recover data, applications,
volumes and servers in DR scenarios
13
Page 7 - 7
Module 8 - DPX Application Protection Overview
DPX Application
A li ti
Protection Overview
Exchange and SQL
Module Objectives
Explain how DPX interfaces with Servers running MS
Applications - Exchange, SQL and SharePoint
Discuss how DPX interacts with these applications in
clustered configurations
Identify the tools and options available when protecting
MS Applications
Page 8 - 1
Overview
Uses Microsoft VSS framework to perform consistent
backups of supported Microsoft applications
Quiesce;
Q i
f
freeze;
and
d th
thaw
No application specific agents to be installed
Automatically detects the location of application
related data files and logs that need to be protected
All databases are internally translated by DPX to be
Exchange and SQL aware snapshots of volumes that
host the database and logs
iSCSI Initiator Requirements

Required only for restores and verification
Not required
q
for performing
p
g backups
p
Windows 2008 iSCSI initiator is pre-installed but not
enabled - as a service in Windows
In earlier versions of Windows, the latest iSCSI initiator
package needs to be downloaded from Microsoft and
installed
Page 8 - 2
Requirements - Volumes Hosting Logs &

Databases
Logs and database files can be hosted in

separate volumes
When protecting Exchange/SQL
databases, DPX intelligently detects and
identifies volumes that host the database
and log files
Other Considerations - Backup Frequency

Since only 250 snapshots can be stored, hourly
backups may be infeasible if retaining for greater than
10 days
Concentrating your backups during the peak hours
can help generate more meaningful recovery points
Example:
1 every h
hour b
between
say. 1
1- 4PM (4 snapshots)
t
h t )
2 for 4 hours on either side say. 9 AM and 11 AM & 6
PM and 8 PM (4 snapshots)
Page 8 - 3
Other Considerations - Cluster Failover Support
If the shared resources fail, the next backup job will

automatically
t
ti ll detect,
d t t follow
f ll
the
th resource and
d perform
f
the backup.
It will not redo a baseline backup if the base has
already been performed once.
Other Considerations - Application Verification for

Recovery Points
Application verification options are node based
Set in the Configure > Enterprise window
Uses IA mapping
Runs after the backup job completes
Verification can be deferred
Runs consistency check with the programming
equivalent of ESEUTIL for Exchange
For SQL, the three options: Verify Table,
Catalog, and Allocations can be specified
Allows to use a separate verification node
Verification node must have the same
version of Exchange/SQL running
Verification node must have iSCSI initiator
Page 8 - 4
Application Verification - Manual Verify via Console

Expand the Exchange/SQL
instance
Right click on the backup
instance in the DPX Restore
screen
Select Verify
The LUN will be mounted and
the database is checked
A separate job is created for
the verify asking to run/run
and monitor or cancel
Application Verification - Manual Verify via Console
Runs a separate (verify)

job and catalogs it
Job name consists of
odv+[epochtime]
Entries can be found for a
preparation script and the
actual verify
10
Page 8 - 5
Other Considerations - Application Verification for

Recovery Points
To check if verification
completed
l t d successfully:
f ll
Refresh the Restore tab
Expand the
Exchange/SQL instance
Verify the point in
recovery snapshot
thatt
h t th
was verified
11
Module Summary
Explain how DPX interfaces with Servers running MS
Applications - Exchange, SQL and SharePoint
Discuss how DPX interacts with these applications in
clustered configurations
Identify the tools and options available when protecting
MS Applications
12
Page 8 - 6
Module 9 - DPX Exchange Protection
DPX E
Exchange
h
P
Protection
t ti
Module Objectives
Explain
p
how DPX interfaces with Exchange
g servers
List the requirements for using DPX in an Exchange
environment
Identify the options available when protecting
Exchange databases
Configure and use the DPX Exchange Mailbox
Recovery (EMR) utility to recover individual mailboxes
or emails
Page 9 - 1
Lesson 1
DPX Exchange Protection

Overview
DPX Exchange Protection

Uses Microsoft VSS framework to perform consistent
backups
No application specific agents to be installed
Automatically detects the location of application
related data files and logs that need to be protected
All databases are internally translated by DPX to be
Exchange aware snapshots of volumes that host the
database and logs
Page 9 - 2
Exchange in DPX Management Console

Automatically creates a virtual object, EXCH
Selecting the EXCH object includes:
Backup of all Exchange databases
Backup of all Exchange logs
Requirements - Windows & Exchange Support

Latest versions of Microsoft Exchange are
supported
Supports various versions of Microsoft Exchange
Server on numerous Windows platforms including
2008 x64 and 2008 R2 x64
Whilst it is always recommended to stay up to date
with the Exchange / Windows service packs,
always check the Syncsort DPX Compatibility
Matrix before implementing changes
Page 9 - 3
Requirements - Permissions
The DPX CMAgent service account must be a DOMAIN ADMIN
user account with full access to the Exchange database
The Domain controller is queried for information during an
Exchange database recovery and the recoveries will fail without
DOMAIN ADMIN privileges
This requirement is only for recovery purposes
Other Considerations - Log Truncation

Transaction logs help to maintain the consistency and
integrity of databases
DPX allows the option to truncate or not truncate
Exchange transaction logs
By default, Exchange logs are truncated automatically
To configure truncation:
Go to Backup > Advanced Recovery
Click Set Source Options
Open Application tab
Page 9 - 4
Other Considerations - Point in Time Recovery

There are two types of Exchange Recoveries:
a) Up to the minute Recovery
b) Point in time Recovery
Up to the minute Recovery is applicable only if the following two conditions are met:
(i) You are recovering the latest recovery point on the Exchange Server.
(ii) You have the transaction logs for all transactions that occurred since the latest DPX
backup job.
All other forms of Exchange recoveries
can only be point in time in nature. A point
in time recovery in Exchange is defined as
recovering the database back to the state
it was at the time of the backup job
job.
To edit this option, the Point in time
Recovery option must be set in the Set
Destination Options dialog.
Other Considerations - Snapshots from

Active/Passive nodes in DAG & CCR Setups
For both CCR and DAG setups, DPX protects Exchange
databases from the active node.
Protects the most recent active copy of Exchange and
not reliant on successful log transport and replication
DPX can backup from just the active copy or all the
passive copies.
Selecting a Database for your backup job requires
that this server contains the active copy of the
database at this specific server both during browse
and backup.
Selecting the EXCH object under the virtual node in
your backup job: Protects all active copies in all
client nodes discovered at the time of the backup
job.
10
Page 9 - 5
Lesson 2
Installing DPX Exchange

Mailbox Recovery (EMR)
11
Exchange Mailbox Recovery (EMR) Overview
DPX Exchange Mailbox Recovery (EMR) is an

application which
which, in conjunction with DPX Instant
Availability, allows quick and easy MS Exchange data
recovery including:
The ability to login to both the running Exchange DB
and the DB from an DPX Recovery Point
simultaneously.
Search and/or recover, mail, mail attachments, inboxes
and folders from the backup copy to your live
environment with zero downtime and no unnecessary
data restores.
12
Page 9 - 6
EMR Installation Requirements

System Requirements:
Intel Pentium-class processor
1024 MB RAM minimum
200 MB for the installation needed
Microsoft Messaging API (MAPI)
Required for DPX Exchange Mailbox Recovery (EMR)
Microsoft .NET Framework 2.0
DPX Client needs to be installed on the EMR host
13
EMR - Supported Microsoft Versions

Supported versions:
Microsoft Exchange: 2003, 2007 and 2010**
on Windows
Wi d
2003 (also
( l x64)
64) and
d 2008 ((also
l x64)
64)
Exchange 2007 Cluster Continuous Replication (CCR) is supported
with DPX Advanced Recovery.
Exchange 2010 DAG supported with DPX Advanced Recovery.
Windows version supported to run the EMR utility are: Windows
2000/2003/2008/XP P
Pro/Vista
allll 32
32-bit
64-bit
/Vi
bi and
d 64
bi versions
i
Always check the DPX Compatibility Matrix for current Supported
Versions
**EMR 6.1 required for Exchange 2010 support with DPX 3.4.1 or higher
14
Page 9 - 7
EMR - Installation
The DPX Exchange Mailbox Recovery Program (EMR) is a
separate utility that needs to be installed.
Installation ISOs can be downloaded from the Syncsort
MySupport website.
A separate license is required at additional cost
It needs Microsoft .NET Framework 2.0.(50727) installed and
will install it for you if not present
No reboot is needed after installation / patching
Can change license from menu or by replacing file after
installation
15
DPX Application Install Downloads

Available on Syncsort Support website
16
Page 9 - 8
EMR License File

The EMR license is issued to run the application on a specific machine
(physical or virtual) and is processor / processor step tied.
To obtain a license, you will need to:
run the License Utility (www.syncsort.com/software/bex/licenseutility.zip) on the
machine that will host EMR.
The utility outputs a text file which needs to be sent to Syncsort Licensing in
order to obtain the license file.
If you need to migrate EMR to run on another machine, you will need to
repeat this process and obtain a new license.
Note If EMR is to run on a virtual machine in an environment that includes
clustered hosts of different processor types/steps,
types/steps then Syncsort licensing
will need a license output file with the VM running on each type of host, with
a reboot in between.
Otherwise, a license violation will occur and EMR will not run in the event of
say a VMotion migration to a host of a different processor type /step.
17
EMR - Permissions
In Exchange Server 2000/2003/2007, the permission that
controls whether or not any mailbox can be copied to is
Full Mailbox Access
Access.
You must have Full Mailbox Access set to "Allow" in order
to copy to a mailbox other than the one you logged in
under.
18
Page 9 - 9
EMR - Important to know

PST files do not support HTML message bodies
HTML message bodies are converted to text or text with HTML tags
After copying or moving a message using Outlook, and later restore that
same item with DPX Exchange Mailbox Recovery, the message may be
duplicated. The message ID numbers differ between DPX Exchange
Mailbox Recovery and the Exchange Server
New mailboxes on the Exchange Server are not visible within DPX
Exchange Mailbox Recovery until someone logs on to the mailbox with
Outlook or a message is delivered (or copied) to the mailbox. Until then
there is no physical mailbox, only directory information
19
Lesson 3
Restoring Messages Using

Exchange Mailbox
Recovery
20
Page 9 - 10
Recovery Scenario EMR with Instant Availability

Scenario - An email user has accidentally deleted an email and
emptied the deleted items folder. How can we quickly recover the
lost item?
Assuming that regular Exchange backups have been taken and DPX
EMR is installed and licensed on the Master Server, the recovery steps
would be:
1.
2.
3.
4.
5.
6.
7.
Use DPX IA Mapping on the desired Recovery Point, to map a drive to a

Windows server. Say drive K: on the Master Server
On the Master Server, launch DPX EMR
For Source data, specify the relevant Exchange mailbox and logs from the
mapped drive K:
For Destination, specify either the mailbox in question, or All mailboxes.
Navigate to the users inbox in Source Pane and find the missing email.
Drag and Drop this email onto the users Inbox in the Destination Pane (Live
Exchange)
The Recovery is complete
21
Recovery Scenario with EMR with IA - Step 1

Use DPX IA Mapping on the desired Recovery Point, to map a drive to a Windows
server. Say drive K: on the Master Server
22
Page 9 - 11
Recovery Scenario with EMR with IA - Steps 2 & 3
Launch DPX EMR
Select your Source

Database Files - in this
example from the
Mapped K: drive
Select your Source Log

Files.
they are
Fil
If th
configured to a separate
location, you may need
to create another IA
mapping for these too.
23
Recovery Scenario with EMR with IA - Step 4

Select your
Target Exchange
Server and
User(s)
You will need Full
Access
Permissions to all
mailboxes to
which you want to
recover data
24
Page 9 - 12
Recovery Scenario with EMR with IA - Steps 5 & 6
Select user,
inbox, mail or
attachment
Drag and Drop

the email to the
Users live Inbox
25
EMR Additional Functions - Search

You can search for
emails or
attachments
You can Preview
messages during
search session and
Save Report of
search session
results
Multiple Source
search sessions can
be run concurrently
26
Page 9 - 13
Recovery Scenario - EMR - Export features
EMR also features

th ability
the
bilit tto E
Exportt allll
mailboxes or the
search result
messages from the
source data store
(DPX Backup) as
message or text files
Go to Tools, Export
27
Lesson 4
Troubleshooting Exchange
Backups and Restores
28
Page 9 - 14
Allow Database to be Overwritten

Exchange flag to avoid accidental and unintentional
recoveries
Exchange
E h
2007 and
d 2010
Database restores require this setting to be checked
Else restore job fails
Required to enable this

option when restoring
the entire database
29
High Change Rate: Likely Causes

There were genuinely a large number of changes
Change rate in database servers is usually higher
th that
than
th t off the
th file
fil servers
The backup job reran as a base snapshot
This can happen if the change journal detects any
inconsistencies or an unclean shutdown (For
example: a hard reset of the server)
If every recovery point is large, an online
defragmentation of the databases may be scheduled
If only some recovery points are large, a periodic reindexing of the databases may be scheduled
30
Page 9 - 15
Exchange Object Not visible in Backup

Selection
Exchange VSS Write Service must be running
In a new Exchange installation, the Exchange VSS
W it Service
Writer
S i iis iinstalled
t ll d b
butt it iis sett tto "M
"Manual"
l"
Startup Type
Set the Startup Type to "Automatic" and start this
service
Exchange VSS Writer Service account
Check to see if the Microsoft Exchange VSS Writer
Service account matches the CMagent Account.
Account
If window does not show the Exchange object, make
sure both the Writer Service and the CMAgent Service
are running with an Exchange administrator account
that has local administrator access as well
31
Lab Exercise
Lab 9-1: Performing Application

Recovery Exchange
Duration: 30 mins
32
Page 9 - 16
Module Summary
Explain how DPX interfaces with Exchange servers
List the requirements for using DPX in an Exchange
environment
Identify the options available when protecting
Exchange databases
Configure and use the DPX Exchange Mailbox
Recovery (EMR) utility to recover individual mailboxes
or emails
33
Page 9 - 17
Module 10 SQL and SharePoint Protection
DPX SQL and SharePoint

Protection
Phil Kilburn / Marco Derks

Senior DPX Consultants
EMEA Professional Services
Module Objectives
Explain how DPX interfaces with Microsoft SQL and
SharePoint
List the requirements for backing up SQL machines
Discuss the various methodologies used to restore
SQL and SharePoint data
Identify limitations and other considerations in backing
up and restoring a SQL server
Discuss protection of SharePoint servers using DPX
Module 10 - Data Recovery - Applications - SQL & SharePoint
Page 10 - 1
Lesson 1
DPX SQL Protection Overview
Supported Versions
Various versions of Microsoft SQL Server on
numerous Windows platforms including 2008 x64
and
d 2008 R2 x64
64 are supported
t d
Whilst it is always recommended to stay up to date
with the SQL / Windows service packs, always
check the DPX Compatibility Matrix before
implementing changes
Page 10 - 2
Requirements - Permissions
Service account requirements:
A local system account with full administrative access to the database (OR)
A windows login account with administrative access to the local
system/cluster and SQL
Uses Microsoft VSS SQL writer service to backup the

database at the block level. Since the SQL writers
need to talk to SQL Server using exclusive VDI APIs,
the SQL writer account must also be running with the
same user
Requirements - Authentication Mode and Recovery

Model
Authentication Mode
SQL provides Windows Authentication and SQL Server
Authentication security modes
DPX mandates
d t Windows
Wi d
Authentication/Mixed
A th ti ti /Mi d Mode
M d since
i
the
th
VSS writers are utilized during the backup
Recovery Model
Recovery models are designed to control transaction log
maintenance. Three recovery models exist: simple, full, and
bulk-logged
DPX will work successfully with all models. The popular models
p and full
however are simple
The 'full recovery model' provides the administrator with the
greatest flexibility in restoring from unintentional/malicious
database transactions, but additional logging results in
Maintenance plans for truncation of logs
The simple recovery model eliminates the need for separate
maintenance for transaction logs
Page 10 - 3
Requirements - Number of Databases per SQL Server

Since DPX backup jobs are done through the
Microsoft Volume Shadow Copy Service, it is a
Microsoft limitation that you create a backup of fewer
than 35 databases at the same time.
This limitation is constrained by the number of
available threads for the Microsofts VSS framework
while taking a snapshot. Disregarding this guideline
y lead to VSS or VDI errors during
g a backup.
p
may
Please refer to the Microsoft KB for further
information:
http://support.microsoft.com/kb/943471/en-us
Requirements - Multiple Instances of SQL
Microsoft 2000/ 2005 / 2008 supports multiple

instances of SQL Server running concurrently on the
same server. A server can have one default instance
and many named instances. Each instance of the SQL
Server has its own set of system and user databases
that are not shared between instances.
t e se
ect e y o
p ete y
DPX ca
can be used to e
either
selectively
or co
completely
backup databases across these instances in the
database.
Page 10 - 4
Other Considerations - Maintenance Plans

DPX backup jobs never truncate transaction logs.
VSS framework constrains backup applications
based on it from truncating logs at this time.
Customers are strongly recommended to setup
database maintenance plans to perform periodic
truncation and/or log backup that truncates
truncates.
Lesson 2
Restoring SQL using IA

Mapping
10
Page 10 - 5
Restore Scenario - Use IA Map and Attach Database

1. Create the required IA map of the snapshot that contains the database
files (.mdf and .ldf) to the SQL server
2 Copy the appropriate database files from the IA map to the active
2.
database drive and folders
3. Use SQL Server Management Studio to attach the database
11
Restore Scenario - Use IA Map and Attach Database

4. The database is now available for access
5. On completion, Unmap the IA drive
12
Page 10 - 6
Lesson 3
Restoring SQL using an

Alternate Method
13
Restore Scenario - Alternate Method

Determine the database name(s) from the original
server you want to restore
Restored server will need hard drive resources large
enough to accommodate all restored databases
The databases will be created on the destination
server after the restore
Database and log file path names will default to MSSQLs default data path
Allows to select a different location of the restored
database
14
Page 10 - 7

1. Create a directory on the
data drive where the
database and log files are
being restored
For example D:\Restore\db

and D:\Restore\logs
2. On the DPX Restore

window, drill down in the
pane. Select the
Sources p
server, instance, restore
point date, and then drill
down to choose the
databases to restore
15

3. On the Destinations pane, drill
down into the server and
instance yyou wish to restore
to. Select Original if you wish
to restore back to the same
server
4. Click on the Set Destination
Options, and set MSSQL with
Replace to Yes. Then set
MSSQL New Location and
Q New Location Logs
g to
MSSQL
the disk and directory created
in Step1
5. Save and run your job
16
Page 10 - 8
Lesson 3
Performing SQL Point-InTime Restores
17
Restore Scenario - Point in Time Restores

Two main processes are required for successful SQL
Server point in time restores: Backup and Restore
Backup operations
Use a SQL Server Maintenance Plan to backup (and truncate)
transaction logs to disk.
Set up DPX backup of this disk together with the regular SQL backup
jobs.
Delete the transaction log backups that have been safely backed up via
DPX.
Restore operations
Restore the SQL database from the snapshot that was created
immediately prior to the required point in time.
Use Instant Access to map the snapshot created immediately after the
required point in time to the SQL server. This mapped snapshot will
provide transaction logs that can be used for point in time restores.
Use the required transaction logs and the necessary SQL Server
utilities to roll forward the database to the necessary point in time.
18
Page 10 - 9
Restore Scenario - Backup Operations

Set up a SQL Server Maintenance Plan that backs up
(and truncates) transaction logs to disk. This is done
y using
g Microsoft SQL Server Management
g
Studios
by
Maintenance Plan Wizard.
1. In DPX, set up backup jobs of that disk together with
the regular SQL backup jobs.
2. If the transaction logs are backed up to a location that
is on a volume which the SQL server uses for data or
log storage, no further steps are needed to explicitly
back up the logs. The regularly scheduled SQL
backup jobs will also backup the transaction logs.
19
Restore Scenario - Backup Operations

3. If the transaction logs are being backed up to a
location that is on a volume which is not used by the
SQL server for data or log storage,
storage this volume will
have to be explicitly selected in an DPX backup job.
4. Delete the transaction log backups (to disk) that have
been safely backed up via the DPX backup jobs.
Note - Transaction log backups that have also been backed up by
a DPX backup job can be deleted from the file system. This is
achieved through a set of pre-job and post-job scripts that record
the time of a successful VSS snapshot/backup, and then delete
all transaction log backups that are older than the recorded time
20
Page 10 - 10
Restore Scenario - Restore Operations

To accomplish a
point in time
restore,
esto e, tthe
e SQ
SQL
database Recovery
Model must be set
to Full during the
time of the backup
task.
Database
D t b
Properties, Options
21
Restore Scenario - Restore Operations (contd)

5. The restored database must be set to a standby state so
that the transaction logs can be played forward
Add a new String Value named SNAPSQLSTBY with a value of Y in the
registry of the target node to which the database is being restored to
HKEY_LOCAL_MACHINE\Software\Syncsort\BackupExpress\<SQLServer>\0
The database must be restored to the original location

22
Page 10 - 11

6. Restore the SQL
database from the
that ran
snapshot
p
immediately prior to the
point in time that you
wish to restore to.
Go to the Restore
screen within the DPX
Management Console,
expand the SQL server
in question and right
click on the SQL
database that you wish
to restore.
23

7. Use the Instant Access feature to map the volume
containing the transaction logs. The mapped volume
should be the first snapshot that ran after the required
point in time of the SQL client that you are restoring.
The mapped snapshot will provide transaction logs
that can be used for point in time restores.
24
Page 10 - 12

8. Use the required transaction logs and the
necessary SQL server utilities to roll forward the
database to the desired point in time
time. This process
is illustrated by the following screenshots.
25
26
Page 10 - 13
27
28
Page 10 - 14
29
30
Page 10 - 15
31
Lesson 4
SharePoint Protection
32
Page 10 - 16
SharePoint - Support
DPX supports backups and recoveries of SharePoint 2007/2010 standalone and SharePoint farm configurations through Advanced
Recovery SnapVault.
Supported Operating Systems and Applications SharePoint support
include:
Microsoft Office SharePoint Server 2007/Windows SharePoint Services
3.0
Microsoft Office SharePoint Server 2010/Microsoft SharePoint
Foundation 2010
Granular search and object recovery using DPX SPOR
Stand-alone and farm configurations of SharePoint
Windows 2003 platforms: x86, R2 x86, x64, and R2 x64
Windows 2008 platforms:
x86,
f
86 R2
2 x86,
86 x64,
6 and R2
2 x64
6
SQL Server 2008, SQL Server 2008 R2, SQL Server 2005, and SQL
Server 2000 (Clustered and Non-Clustered) platforms:
Whilst it is always recommended to stay up to date with the SQL /
Windows service packs, always check the Syncsort DPX Compatibility
Matrix before implementing changes
33
SharePoint - Configuration
While a SharePoint installation can run on a single
server, it is much more common to see a single
SharePoint application deployed on a number of
different servers in what is called a farm
configuration.
The servers in a SharePoint (server) farm, that is,
front-end web servers, application servers, and
p
y distinct
database servers,, will often perform
very
tasks that fulfill unique SharePoint requirements. It is
the combination of these different server types
working together that provide the full set of
SharePoint functionality.
34
Page 10 - 17
SharePoint - Standalone Configuration

Client Computer with
Browser
ISAPI ASP.
NET
HTTP Request
OLEDB
HTML Pages
Web Server
(IIS)
Windows
SharePoint
Services
SQL Server
While a SharePoint installation can run on a single server, it is much

more common to see a single SharePoint application deployed on a
number of different servers in what is called a farm configuration.
The servers in a SharePoint (server) farm, that is, front-end web
servers, application servers, and database servers, will often perform
very distinct tasks that fulfill unique SharePoint requirements. It is the
combination of these different server types working together that
provide the full set of SharePoint functionality.
35
SharePoint - Farm Configuration

Load Balanced Front End Servers
User requests
through web
browser
Web Servers
Dedicated
Search Server
1
Dedicated
Search Server
2
Clustered / Non Clustered Database Servers

Content
Database
Server 1
Content
Database
Server 2
Config and
Admin Content
Databases
Server 3
36
Page 10 - 18
SharePoint - Backup Physical and Virtual Nodes

Servers in the SharePoint farm appear defined as nodes in the DPX
enterprise.
DPX will display all SharePoint dependant applications
applications, including SQL
databases and SharePoint Index files, within the physical node
structure.
The SharePoint application appears in a virtual node, in a separate
DPX virtual node group called the SharePoint_Group.
37
SharePoint - SharePoint Component
38
Page 10 - 19
SharePoint - Control Nodes

Establishing DPX SharePoint Control Nodes
SharePoint server is referred to as a node
one or more nodes designated as Control node
Must have at least one physical node that acts as a control
node for all SharePoint applications
Control node is a front-end server that DPX uses to control all
browse, backup and restore activities.
Can be an front-end server that has SharePoint VSS writer
enabled.
Can be automatically designated if DPX detects SharePoint
VSS writer enabled on the server.
Configuring Automatic Failover Functionality for SharePoint
Farms
If you have multiple front-end servers in a SharePoint farm, you
can configure automatic SharePoint control node failovers.
39
SharePoint - Automatic Failover

To configure automatic failovers:
Click on the SharePoint applications virtual node icon to display the
Edit Node pane for that virtual node.
Edit the configuration of that virtual node, as follows:
Select the Yes radio button that appears next to the Enable Automatic
Failover of Control Node feature on the Edit Node pane, to activate
failover functionality for this SharePoint application.
If you wish to designate a primary DPX SharePoint control node, click
the Control Node for Backup drop-down box, and then click on the DPX
SharePoint control node that you want to select for this purpose.
40
Page 10 - 20
SharePoint - SharePoint Object Recovery

DPX Advanced Recovery for SharePoint also offers SharePoint Object Recovery
(SPOR). This feature utilizes DPX Instant Availability to easily recover
SharePoint items from dismounted or backed up SharePoint databases.
41
SharePoint - Benefits of SharePoint Object Recovery

Provides copy, search, and analysis functionality for individual items,
including documents, lists, libraries, folders, or entire SharePoint
sites.
Lets administrators find, recover, and restore SharePoint server
objects. DPX SPOR reads content database backups directly, letting
system administrators quickly locate individual items for restoration,
and minimizing the need for a stand-by recovery server.
Perform a direct restore to any SharePoint server, and there are no
same-server constraints on any restore activities. DPX SPOR can
restore objects to any Windows-supported file system as well.
Reads the backed up content database files (.MDF,
( MDF .NDF,
NDF and .LDF)
LDF)
and makes that data available through various DPX recovery
mechanisms. You can read or export one or more items to a selected
Windows workstation/server using Instant Availability volumes, or
you can perform a full restore through the DPX management console.
42
Page 10 - 21
Module Summary
Explain
p
how DPX interfaces with Microsoft SQL and
SharePoint
List the requirements for backing up SQL machines
Microsoft SQL and SharePoint
Identify limitations and other considerations in
backing up and restoring a SQL server
Configure and perform backups of SharePoint servers
43
Page 10 - 22
Module 11 - DPX Oracle Protection
DPX O
Oracle
l P
Protection
t ti
Module Objectives
Explain how DPX interfaces with Oracle
List the requirements for backing up Oracle
Databases
Oracle and SharePoint servers
Page 11 - 1
Oracle - Support
DPX supports Oracle on Windows, Solaris, and Linux
(RedHat, SLES, CentOS)
Provides auto-discovery of Oracle database instances
Backup of Oracle databases or tablespaces residing
on drives or mount points at local machines
Restore of Oracle tablespaces that are in either online
or offline mode
Restore
off iindividual
R t
di id l Oracle
O
l files
fil
DPX Bare Metal Recovery disaster recovery for Oracle
nodes
Oracle - Support (contd)

Instant Availability of Oracle backup instances
Quick Restore using Instant Availability mapping
Database cloning on an alternate node which
involves recovery by way of Instant Availability
RMAN Cataloging
* See the compatibility matrix for supported Operating Systems and Hardware
http://www.syncsort.com/ProductsServices/DPX/SystemRequirementsandCo
mpatibility.aspx
Page 11 - 2
Oracle - Considerations
DPX Advanced Recovery backups and restores for Oracle are executed from the DPX
Management Console
Oracle must be running in ARCHIVELOG mode during backup and restore
The Oracle archive destination variable must be set to a specific location, not the
default. The following example shows a setting for a specific location on UNIX/Linux:
alter system set log_archive_dest_1='location=/db/DB1_arc';
archive log list;
alter system switch logfile;
TNS Listener process must be running for all operations
iSCSI Initiator
that
I iti t mustt be
b installed
i t ll d for
f all
ll operations
ti
th t require
i Instant
I t t Availability,
A il bilit
including RMAN cataloging
On each Oracle node, after DPX has been installed, OracleConfig must be run from
the DPX Command Prompt
Oracle - Configuration
Run OracleConfig:
From Windows, open an
DPX C
Command
dP
Promptt and
d
run the command
run-java
OracleConfig
From UNIX/Linux, navigate
to the DPX bin directory and
run the command
run.java OracleConfig
Fill in the required

information and
Save
Page 11 - 3
Oracle - Backup
On the DPX Advanced Recovery source tree, the Oracle object will
appears as a yellow disk.
The Oracle database or the tablespace can be selected for backup.
Oracle - RMAN Management

If the backup source job option Oracle RMAN Cataloging Control is set to
Yes, a completed DPX backup of Oracle is cataloged in RMAN as well
as in DPX.
Page 11 - 4
Oracle - Archive Logs

When backing up Oracle, DPX requires that Oracle is run in ARCHIVELOG mode.
This option controls whether to keep or delete the archive logs (generated during
backup) once a DPX job completes. Archive logs generated during regular
database operation are not affected by this option.
Oracle - Restore Methods

In DPX, there are four methods for restoring Oracle data:
Method
Description
Logical View
Restore:
Regular
This is the default view that appears when you open the Restore
window in DPX. It is the default method for DPX Advanced Recovery
restores, transferring data over the network. It is also the most
limited method.
Logical View
Restore:
Quick Restore
This option performs an Instant Availability mapping, thereby making

Oracle data, archive logs, and control file quickly available.
Logical View
Restore:
Cloning
This option clones an Oracle database on an alternate node by way

of Instant Availability. In contrast, Regular Oracle restore does not
use Instant Availability, and Quick Restore, though it uses Instant
Availability, does not actually recover a database.
Physical View
Restore
With this method, all backed up Oracle data files, control file,
parameter file, and archive logs are available for individual selection,
but no Oracle application level processing is done by DPX.
10
Page 11 - 5
Oracle - Restore Methods

Regular Mode Restore
Basic restore of database/tablespace
from the logical / physical view
perspective.
Can restore the database to the latest
point in time.
Quick Restore
Advanced restore in which an Oracle
DBA can leverage RMAN to perform
more granular or point in time
restores
Clone Database
Restore creates Oracle instance to
another database server. User will be
required to supply
ORACLE_HOME location
ORACLE Username and Instance
Password
11
Module Summary
E l i h
Explain
how DPX interfaces
i t f
with
ith Oracle
O
l
List the requirements for backing up Oracle
Databases
Oracle
O
l and
d SharePoint
Sh
P i t servers
12
Page 11 - 6
Module 12 - DPX Bare Metal Recovery
DPX Bare
B
M t l Recovery
Metal
R
(BMR)
Module Objectives
Explain the process of recovering a server using DPX
Bare Metal Recovery (BMR)
Explain the role played by different components of an
DPX Enterprise in recovering servers
Describe the various options available during the
BMR process
Page 12 - 1
What is BMR?
DPX Bare Metal Recovery (BMR) is a disk-based disaster
recovery feature that enables administrators to quickly and
easily restore the entire system for an individual computer,
including:
The operating system,
Point-in-time backed up data
MS Exchange, SQL Server and Oracle applications if
applicable.
During the BMR Process, DPX Master Server
plays no part.
S
It doesnt even need to be running!
Only the NetApp Secondary Storage that holds the backup
of the server to be recovered (and the BMR ISO) is used
3
Server Recovery via DPX Bare Metal Recovery

NetApp Secondary
Storage
Primary
9 am
Block-level backups
backups of Server Image
10 am
11am
11:30
11:35
11:42
11:50
Replace Hard
Drive &
Boot from DPX
Bare Metal
Recovery CD
Select
desired
Recovery
Point
Recover
Server Image
Reboot
server and
restore
complete!
11:15 am
Server HD Failure
Occurs
11 am
Page 12 - 2

The Syncsort support website offers several versions
of the BMR ISO, with either a Linux kernel or a
Windows Vista/winpe kernel
See Knowledge base article A004748 for all details
between the different versions
New versions contain latest drivers of new HBAs
available on the market (if included WinPE)
When booting from the image, additional drivers can
be added
5

https://www.syncsort.com/support/BEX/DPX/
Page 12 - 3
Lesson 1
Bare Metal Recovery of

Windows Nodes
DPX Bare Metal Recovery - Windows

Using DPX Bare Metal Recovery in Windows
environments involves:
Booting your bare machine from the BMR CD or ISO
Access the DPX SnapVault Secondary containing your
DPX Bare Metal Recovery backups
Selecting your desired backup instance and volumes
for restoration
Page 12 - 4

For Windows, the BMR node must have at least 1024
MB of memory
The full system Advanced Recovery backup needs to
have a successful backup of the BMR! object
For Windows, dissimilar hardware is supported*
*similar CPU type

! Depending on DPX version, this can also be referred to as the ExpressDR object

For Windows nodes, DPX Virtualization:
Could be used as an alternative to DPX BMR for
recovering a physical or virtual machine to a virtual
machine
Easily and automatically perform Physical to Virtual
(P2V) and Virtual to Virtual (V2V) restores through
DPX Management Console without BMR involved
Physical or virtual machines can be recovered in
minutes using DPX Instant Virtualization (covered in a
separate section later)
10
Page 12 - 5
Lesson 2
Bare Metal Recovery of

Linux Nodes
11
Bare Metal Recovery - Linux

For Linux, the source node and bare node (target)
must have at least 1024 MB of memory
The Linux DPX Bare Metal Recovery ISO
For Linux, DPX Bare Metal Recovery to dissimilar
hardware is supported*
* check latest compatibility guide
12
Page 12 - 6
Bare Metal Recovery - Linux

When Special drivers are needed:
DPX Bare Metal Recovery installs required drivers.
Most are installed automatically from the DPX Bare
Metal Recovery CD. However, if a required driver is not
contained on the DPX Bare Metal Recovery CD, you
must install it from a floppy, a CD, or USB storage
Open Command Prompt session
Copy needed drivers
Use rmmod, depmod and modprob to get the driver
loaded (see manual DPX, Bare Metal Recovery
Guide, chapter 4.3 for further specifications)
13
Lesson 3
Bare Metal Recovery

Wizard
14
Page 12 - 7
Bare Metal Recovery (booting from winpe iso)

After booting
from BMR CD,
choose your
k b d
keyboard
layout.
Next, we can
add drivers,
view and collect
logs and send
logs per e-mail.
15
Bare Metal Recovery (BMR configuration)

Boot the primary server from a Syncsort provided CD to rebuild the
server from an SV snapshot on the Secondary
Available
Snapshot(s)
on the
Secondary
16
Page 12 - 8
Bare Metal Recovery (BMR configuration, contd)
Boot Disk (C:)

Application Disk (D:)
Optionally select the non-boot disk

partitions that should be restored as
part of the Bare Metal Recovery job.
17
Bare Metal Recovery (BMR configuration, contd)

Also cluster volumes
can be restored.
Restored disk will be
verified directly after
restore has finished.
E-mail can be sent with
notification when
recovery is done.
Optionally select the
non-boot disk partitions
that should be restored
as part of the Bare
Metal Recovery job.
18
Page 12 - 9
Bare Metal Recovery

After the data
transfer completes,
reboot the machine.
machine
The machine is
recovered to the
timestamp of the
selected snapshot.
19
Troubleshooting BMR
You can capture and transmit the DPX Bare Metal
Recovery diagnostic logs by doing the following:
Invoke GetSystemsInfo dialog by
clicking the Send email
notification when finished
checkbox before restore, or by
clicking the email logs tab at the
top of the user interface. The
Sender/Recipient Information
dialog appears.
Bare node needs to be able to
connect to SMTP server
specified
Click Send. DPX Bare Metal
Recovery accumulates diagnostic
logs and sends them to e-mail
recipient
20
Page 12 - 10
Lab Exercise
Lab 12-1: Performing Bare Metal

Recovery
Duration: 20 mins
21
Module Summary
Explain the process of recovering a server using DPX
Bare Metal Recovery (BMR)
Explain the role played by different components of an
DPX Enterprise in recovering servers
Describe the various options available during the
BMR process
22
Page 12 - 11
Module 13 - DPX Virtualization
DPX Virtualization
Vi t li ti
Module Objectives
Explain the advanced recovery options provided by
DPX using virtualization techniques
Configure and use the following DPX Advanced
Recovery alternatives to file restore in order to
recover data, applications, volumes and servers in DR
scenarios:
Instant Virtualization (IV)
Full Virtualization (FullV or FV)
Rapid Return to Production (RRP)
Page 13 - 1
Lesson 1
DPX Virtualization
Overview
Virtualization Overview
Recover an entire server as a virtual machine
Source machine can be a physical or virtual machine
Recovered machine is always a virtual machine
Different from DPX Bare Metal Recovery
Benefits:
High Availability of Clients
Exchange server backed up using DPX
Exchange server fails
Restore the entire server, within minutes, using virtualization
Clone servers for testing purposes
Oracle
DBA wants to run queries
O
Create a VM from the latest backup snapshot using IV
Perform the queries and delete the IV virtual machine
Zero footprint, zero impact to production environment
Physical to Virtual Migration
Zero impact to production (source) machines
Page 13 - 2
Virtualization Types
Instant Virtualization
Servers can be accessed in minutes from backup
snapshots
Uses IA mapping functionality to create RDM Luns
Full Virtualization
Restores the backup snapshots as a virtual machine
Creates the .vmdk files (not RDM Luns)
Used to convert the IV machine (RDMs) to a
production VM (VMDKs)
Uses vMotion to create the permanent .vmdk files
5
Windows Server
(Source for Backup)
NetApp Secondary
Storage
Block-level backups
ESX Host
9 am
Create VM in ESX
10 am
VM Boots
Server is Live
and Running
as a VM!
Automatic IA mapping
of the drives on the
source machine
11:15 am
Failure on
Server
11:20
Select
desired
Recovery
Point
11 am
11:25
Perform Instant
Virtualization.
Server is back
on-line, running
as a VM!
6
Page 13 - 3
Virtualization Process
Two Step Process
Backup the source node using DPX Advanced
R
Recovery
jjob
b iincluding
l di th
the BMR! object
bj t
This backup can be used to create a VM on the Virtual
Controller (vCenter Server or ESX Host) using either of
the two previously mentioned Virtualization methods:
No Data is restored; uses IA and Raw Device
Mapping (RDM)
Full Virtualization (FV)

Data from backed up node is restored to the
created VMs vmdk files
Back Up Job Requirement for Virtualization

The BMR object must be included in the backup to perform any
type of DPX virtualization recovery
*Depending
on DPX version,
BMR object is also referred
to as ExpressDR
Page 13 - 4
Lesson 2
Defining a Virtualization
Job
Creating a Virtualization Restore Job
*Depending
on DPX version,
BMR object is also referred
to as ExpressDR
10
Page 13 - 5
Creating a Virtualization Restore Job

There are 6 definition steps in a Virtualization job creation wizard:
1. VM Details - (VM name, hostname, and whether full or instant
virtualization
i t li ti
2. Host the ESX(i) or VC (IP, user ID, password)
3. Resources ESX(i) resources to allocate to new VM
4. Network Information static or dynamic for VM
5. Virtualization Options Locate the virtualization ISO image on the
datastore for initial boot of the VM
6. Summary view all entries and make changes, if needed.
11
Virtual Machine Details: Instant Virtualization
Name displayed on the

vSphere console; not the
system name
Virtual machine
(
(system)
) name
12
Page 13 - 6
Virtual Machine Details: Full Virtualization
13
VMware Host Login
A VMware vCenter or
licensed ESX/ESXi server
Account with
administrative rights
14
Page 13 - 7
Resources
15
Network Information
16
Page 13 - 8
Virtualization Options
Copy the virtualization ISOs to
the target ESX server
L
Location
ti off the
th ISOs:
ISO
$SSPRODIR\misc
17
Job Summary
18
Page 13 - 9
Running a Virtualization Restore Job

When the job is run, DPX retrieves the data from the BMR
object backup and uses this to create a VM
Virtualcenter client
shows VM creation
in real time
19
Running a Virtualization Restore Job

During the IV process
DPX strips out all
hardware information
from the OS
configurations and
injects the virtual
hardware information
for the new VM.
This means that any
server physical or
virtual - (with a
supported OS) can be
virtualized in this way
20
Page 13 - 10
Creates an iSCSI map of data stored on the source instance
to the virtual node
No data is restored / transferred to the virtual machine and
therefore the VM does not require any .vmdk space on the
virtual controllers datastore (a small amount of space will
be used to record changes while mapped).
Changes made to the mapped drive do not affect the
backed up data
data, which is part of a read only snapshot
stored on the NetApp Secondary Storage.
Requires that an iSCSI initiator is enabled on your virtual
controller (ESX Server)
21
Instant Virtualization and BMR: The Differences

Customers can use either DPX Instant Virtualization or DPX Bare Metal Recovery
to quickly perform P2V or V2V recovery for Windows machines
Bare Metal Recovery
(Need to do the following step by step)
(Configure all the following through management

console in the beginning and then the following will
be processed automatically)
1.
Create a VM through VMware software
2.
3.
4.
5.
6.
need to know configurations for the VM (number

of disks, size of each disks, etc.)
Boot the VM from BMR CD / USB /

Network
Restore the OS information from backup
image
p
Reboot the VM and OS is booted up
IA map the backup image to the ESX
Server and create a virtual disk
Attach the VM created with the disk
(BMR can be used for P2V and V2P for
Windows only; BMR can be used for P2P
and V2V for Windows, Solaris and Linux)
1.
Create a VM from management console
no need to know the configurations for the VM
This will automatically perform:
Boot the VM from WPE located in master server

IA map the backup image to the ESX Server and create a
virtual disk
Attach the VM created with the disk
(IV can be used for P2V and V2V for

Windows only; IV can not be used for P2P or
V2P)
22
Page 13 - 11
Lab Exercise
Lab 13-1: DPX Instant

Virtualization
Duration: 20 mins
23
Lesson 3
Rapid Return to Production
24
Page 13 - 12

Converts IV machine into a full production VM
Creates VMDK files from RDM Luns
Seamless migration of data in background using
Storage vMotion
NetApp Secondary
Storage
VM of
Application
1. Create VM
10:00
Data
10 00 D
t Image
I
VMware ESX
4. Storage
4
VMotion
migrates disks
2. Boot off snap
10:15 Data Image
10:30 Data Image
3. Background
migration of data
to datastore
VMDK
VMX
Datastore
25

Creates a full production VM from an existing VM
created by IV with zero downtime
RRP makes the new production VM available for use
in minutes, while DPX transfers data in the
background using VMware Storage VMotion
RRP is particularly useful when you have used IV to
create a test environment that is ready for production
production.
When migrating a temporary, test VM to a permanent
VM, RRP can save many hours, or even days in the
case of large data transfer over a slow connection.
26
Page 13 - 13
Considerations for Virtualization

Virtualization is supported for DPX Windows clients running
Windows 2003, Windows2008, or Windows 2008 R2
Virtualization is supported for DPX non-Windows clients running
Redhat Enterprise Linux 5.x, SUSE Linux Enterprise Server
(SLES) 10.x/11.x, and CentOS 5.x
Virtual machines are created using BMR object
Virtualization ISOs must be copied to a datastore on the target
ESX server
Requires either a licensed VMware ESX(i) server or a
VirtualCenter virtual controller
A virtual machines minimum memory requirement is 512 MB
27
Considerations for Virtualization (contd)
VMotion (live migration of a virtual machine from one

physical
h i l host
h t to
t another)
th )
Supported for Full virtualization jobs, not for Instant
virtualization jobs.
Machines should not be manipulated through VMotion
during backup or restore operations.
VMware
Raw D
Device
Mapping
VM
R
i M
i
(RDM) iis only
l supported
t d
for Instant virtualization
28
Page 13 - 14
RRP for IV Hosts VMs
There are two methods RRP uses to create the full

production
d ti
VMs:
VM
Relocation (Migration)
Used if the VM is in On state when the RRP job
starts
Cloning
Cl i
Used if the VM is in the Powered Off state when
the RRP job starts
29
RRP for IV Hosts VMs
30
Page 13 - 15
RRP Wizard
Launch the RRP
Wizard from the DPX
Management
Console, Restore >
Advanced Recovery
screen
Follow the prompts
and enter the
required information
31
RRP Wizard
VMware vCenter server
Account with
administrative rights
32
Page 13 - 16
RRP Wizard
Only VMs created using IV

are displayed
33
RRP Wizard
At the next screen,
choose the Datastore
where production VM
will reside
reside.
34
Page 13 - 17
RRP Wizard
At the Summary screen, check all information is correct and if all is good, then
Finish, when you will be asked if you want to run the job now
35
RRP Running the Job

When the RRP Job is launched:
The VM is reconfigured and
its data relocated from the
RDM LUNs of the IVd VM
to vmdk virtual disks of a
full production VM.
The process can be seen
real time in the VI Client
NB: The VMs power state
cannot be changed during the
RRP process. (The power
options are inactive in VI
Client). Shutting down within
the OS would fail the RRP job
36
Page 13 - 18
RRP - On Completion
VM configuration after DPX IV
After the RRP Job
completes:
The Mapped RAW
LUNs for the VM
have been
converted to Virtual
Disks (.vmdk)
VM configuration after DPX RRP
The LUNs coming

from the NetApp
secondary will be
pp
unmapped
The VM has now
been put into /
returned to
production
37
Lab Exercise
Lab 13-2: Rapid Return to

Production
Duration: 20 mins
38
Page 13 - 19
Lesson 4
DPX Full Virtualization
39
DPX Full Virtualization

Creates a new virtual machine which contains a duplicate of
the functional volumes
R t
Restores
each
h partition
titi
off the
th jjobs
b source iinstance
t
tto it
its own
disk volume on the new virtual machine during Virtualization
Restore job
Virtual machines created through the Full Virtualization
method require at least as much disk space on the target
virtual controller datastore as the combined size of all the
backups source disks.
This is the combined actual disk sizes, not the volumes
defined on these disks
Ex. If you have a 200G drive with a 40G C: on it, you would
need 200G, initially, to restore C:
The unused space can be reclaimed later using VMware tools
40
Page 13 - 20
Full Virtualization Types

Full Virtualization with RRP
Combines IV and RRP
Only VMFS datastores are supported
Full Virtualization (without RRP)

perform IV ((no RDM Luns))
Does not p
Creates the VMDKs directly
VMFS and NFS datastores are supported
41
Full Virtualization With RRP
42
Page 13 - 21
Full Virtualization Without RRP
43
Full Virtualization Requirements

The following criteria are required for FV:
VMware ESX 4.0
4 0 or higher
Storage Vmotion license
Destination datastore: VMFS
NFS is supported only for Full Virtualization (without RRP)
Align Virtual machine File System is checked by

default (recommend)
44
Page 13 - 22
Delete VM/VMDK Wizard

IV machine creates RDM Luns
Deleting the IV machine from vSphere
console DOES NOT delete associated
FlexClones on the NetApp storage
system
Use Delete VM/VMDK Wizard
CAUTION: Wizard allows to delete any
VM, not just those created by DPX
45
Delete VM/VMDK Wizard

Using the Delete wizard:
For an IV machine, all the RDM Luns associated with
th VM will
the
ill b
be removed,
d FlexClones
Fl Cl
on the
th Netapp
N t
Storage System deleted, and the VM will be deleted
from the datastore
For a regular VM, all associated disks on the datastore
will be deleted, and the VM will be removed from the
inventory
46
Page 13 - 23
Module Summary
Explain the advanced recovery options provided by
DPX using virtualization techniques
Configure and use the following DPX Advanced
Recovery alternatives to file restore in order to recover
data, applications, volumes and servers in DR
scenarios:
Full Virtualization (FullV)
47
Page 13 - 24
Module 14 DPX Agentless VM ware Protection
DPX Agentless
A
tl
VM
VMware
Protection
Module Objectives
Explain the DPX Agentless VMware backup and
recovery feature
Configure and use the following DPX Agentless
recovery alternatives to protect VMware virtualized
environments:
Instant
I t t VM Restore
R t
Full VM Restore
Full VMDK Restore
Module 14 DPX Agentless VMware Protection
Page 14 - 1
Lesson 1
Agentless VMware
Protection Overview
DPX Agentless VMware Backup

Designed specifically for highly efficient and reliable
protection of VMware virtual machines
Agentless No DPX agents (client) are installed on
the VMs
Uses VMware vStorage APIs for Data Protection
(VADP)
Uses Virtualization Proxy Servers to backup the VMs
Also referred to as Proxy-Based backup
Page 14 - 2
Agentless Proxy Servers

LAN or SAN backup
Auto load balancing for faster backups
Multi-threaded
Back up multiple VMs (or VMDKs) in a single job
Virtual Proxy
VMs
NetApp Secondary
Load
Balancing
Physical Proxy
SAN
LAN
SAN
Benefits of Proxy-Based Backups

Significant Performance Improvements
Incremental backups utilizing the Change Block Tracking
(CBT) mechanism allow for faster backups,
backups reduced network
traffic, and reduced storage requirements
Simplified administration
No backup software to maintain on VMs
Auto-discovery and protection of new and modified VMs
Automatic discontinuing of protection for deleted VMs
Supports most operating systems
Multiple recovery options
Entire VM
Individual VMDKs
File recovery, using LUN mapping and file system copy
Page 14 - 3
Proxy-Based vs Guest-Based
Agentless VMware Backup
Advanced Recovery
a.k.a. Proxy-Based Backup
a.k.a. Guest-Based Backup
Agent installed only on proxy

servers
Agent installed on each VM that

needs to be protected
Data protection of all VMs but no

application protection
Recommended when protecting

applications like Exchange, SQL,
SharePoint or Oracle
SharePoint,
IMPORTANT: Both these VM data protection types

are tightly integrated and can be deployed/used in a
single DPX data protection system (DPX Enterprise)
Lesson 2
Performing Agentless
Backups
Page 14 - 4
Installation Requirements
vSphere 4.0 or later on hosts
An DPX release supporting Agentless VMware Backup
(DPX 4.0
4 0 or llater)
t )
At least one proxy server
64-bit Windows or Linux machine
Physical or virtual
Physical Proxy required for SAN-based
infrastructure
Recommended to have multiple proxy servers
iSCSI initiator enabled
On the ESX server hosting the restored VM
On the target node for VMDK Instant Access
Installation Requirements
Additional Requirements
vCenter administrative privileges
VMware Tools installed on each VM that needs to be
protected
Virtual hardware version 7+ on each VM that needs to
be protected
10
Page 14 - 5
Configuring Agentless Backups

Add a vCenter Node to the Enterprise
Configure VMware backup proxy server(s)
Define an Agentless VMware backup job
11
Adding a vCenter Node

Similar to adding a regular Node to the DPX
Enterprise
Access
A
M
Method:
th d VMWARE
Recommended to create a dedicated node group
Change
Access
Method to
VMWARE
Add portt
and user /
password to
vCenter
server
12
Page 14 - 6
Configuring VMware Backup Proxy Servers

Node must be installed as a
Virtualization Proxy Server
Sets
S t the
th Virtualization
Vi t li ti Proxy
P
Server to Yes in the
configuration window
Enabled, by default, for the
Master Server
By default,
default DPXautomatically
chooses proxy servers or you
can set it at Backup >
Agentless VMware> Other
Tasks
13
Defining an Agentless VMware Backup Job

Select
Source VMs
and your
destination
NetApp
Storage
System
volume(s)
14
Page 14 - 7
Defining an Agentless VMware Backup Job

Set Proxy Servers
Step 2
Set Proxy per
Job
Step 1
Node
Configuration page
Step 3
Choose correct
server
15
Lab Task
Lab 14-1: Performing Agentless

Backup
Duration: 20 mins
16
Page 14 - 8
Lesson 3
Agentless VMware
Restores
17
Agentless VMware Restores

Simple, wizard-driven recoveries
Types of Restores:
Instant VM Restore
Full VM Restore
Full VMDK Restore
18
Page 14 - 9
Instant VM Restore
Creates a new VM from the snapshot
Restores to original or alternate ESX host
Uses iSCSI LUN mapping
Restored disks attached as RDM LUNs to the new VM
VMs
Restored VM
NetApp Snapshots
DPX Agentless
Backup
ESX host
19
Full VM Restore
Creates a new VM with VMDKs from the snapshot
Restores to original or alternate ESX host
Physical data is transferred
Uses Instant VM Restore, internally, for immediate
availability of the VM
Data copy (VMDK creation) in the background
Restored VM with VMDKs
VMs
VMDK
NetApp Snapshots
DPX Agentless
Backup
VMDK
ESX host
20
Page 14 - 10

Restores via mapping VMDK file(s) to original or
alternate VM
Uses iSCSI LUN mapping
Theory of Operation
Creates a temporary LUN on the NetApp secondary
Maps the LUN to the target host
Attaches the LUN to the target VM as an RDM disk
VMs
Restored VMDK
VMDK
NetApp Snapshots
DPX Agentless
Backup
21
Full VMDK Restore

Restores VMDK file(s) to original or alternate VM
Physical data is transferred
Uses Instant VMDK Restore, internally, for immediate
availability of the data
Then uses Storage vMotion to convert the attached
LUNs to flat VMDKs
VMs
Restored VMDK
VMDK
NetApp Snapshots
DPX Agentless
Backup
22
Page 14 - 11
Agentless VMware Recoveries - Summary

Restore Type
Restore
Source
(Backup
Type)
Restore
Target
DPX
Required
on
Restore
Target
Requires
iSCSI Initiator
enabled
On
Host
On
VM
Storage
Relocation
Used
Instant VM
Restore
Agentless
VMware
ESX
Server
No
Yes
No
No
Full VM
Restore
Agentless
VMware
ESX
Server
No
Yes
No
Yes*
Instant VMDK
Restore
Agentless
VMware
VM
No
Yes
No
No
Full VMDK
Restore
Agentless
VMware
VM
No
Yes
No
Yes*
* Used in most cases, otherwise Cloning is used

23
Lesson 4
Performing Agentless
VMware Restores
24
Page 14 - 12
Defining an Agentless Restore Job

From Restore, Agentless VMware, click
on AgentlessVMware Restore Wizard
25
Agentless Restore Type
26
Page 14 - 13
VMware Restore Wizard - Source

Depending on the restore type, selectable options in the
right pane vary
27
VMware Restore Wizard - Target
Options provided will vary if a VMDK Instant Access type of

restore is being performed
28
Page 14 - 14
VMware Restore Wizard Target Datastore

This step is not displayed if restore destination is Original
Location
29
VMware Restore Wizard Virtual Machine Options

This step is not displayed if restore destination is
Original Location
30
Page 14 - 15
VMware Restore Wizard Job Information

Optionally, specify any pre- and/or post job scripts
31
VMware Restore Wizard Job Schedule and

Summary
32
Page 14 - 16
Lab Task
Lab 14-2: Performing Agentless

Restores
Duration: 20 mins
Lab 14-3: Using Delete VM Wizard

Duration: 10 mins
33
Module Summary
Explain DPX Proxy-Based (agentless) backup and
recovery feature
Configure and use the following DPX Agentless
recovery alternatives to protect VMware virtualized
environments:
Instant VM Restore
Full
Restore
F ll VM R
t
Full VMDK Restore
34
Page 14 - 17
Module 15 - DPX Disaster Recovery Overview
DPX Di
Disaster
t R
Recovery
Overview
Module Objectives
Upon completion of this module you will be able to:
Discuss DPX Integrated Disaster Recovery Features
Discuss the importance of DPX Alternate Secondary
destinations
Perform DPX recoveries from a NetApp SnapMirror
destination
Explain DPX +Tape features to archive backup data to
tape
Page 15 - 1
DPX Solution Integrated Disaster Recovery

Two DR options:
D2D2D (using NetApp SnapMirror)
D2D2T (Archive to Tape)
DPX Backup
NetApp SnapMirror
WAN
LAN
DPX Clients
Exchange, SharePoint, SQL,
VMware
VM
NetApp FAS
Backup
Targett
D2D B
k T
SAN
DPX
Master
optional
NetApp FAS
DR Target
DR Site
Any Primary Disk
EMC, HP, IBM - or DAS
optional
Tape Archive
Instant / Full
Virtualization
Lesson 1
DPX Integrated Disaster

Recovery: D2D2D
Page 15 - 2
DPX D2D2D Protection Using SnapMirror

Uses NetApp SnapMirror technology to replicate data
from SnapVault Secondary to SnapMirror Secondary
Requires SnapMirror license from NetApp
Configured using NetApp System Manager (or CLI),
outside of DPX
NetApp Storage System Requirements

License requirements (on SnapVault Secondary and
SnapMirror Secondary):
SnapVault Secondary License
SnapMirror License
NetApp iSCSI License
NetApp FlexClone License
The SnapVault destination volume at the secondary and the
SnapMirror destination volume at the DR site must have the
same capacity
Page 15 - 3
Configuring SnapMirror
Recommended to use SnapMirror Relationship Create
Wizard in the NetApp System Manager console
Invoking SnapMirror
Submitted through console or NetApp management
console (outside of Syncsort)
Can be submitted via post-job script upon job completion
or after a dummy job using rsh
If using asynchronous A-SIS, recommended to snapmirror
Scheduled via snapmirror.conf
U
sy
c o ous s
ap
o
<UKN>
synchronous
snapmirror
Commands:
snapmirror initiailize
snapmirror update
Page 15 - 4
Snapmirror operations
snapmirror initialize
request start of initial transfer
Usage:
snapmirror initialize -S [<srcfiler>:]<srcpath>]
[<dstfiler>:]<dstpath>
snapmirror update
forces snapmirror update of snapmirror destination
Usage:
snapmirror update -S
S [<srcfiler>:]<srcpath>]
[<dstfiler>:]<dstpath>
Note: srcpath and dstpath are <volname> or
</vol/volname/qtreename>
Restoring from Alternate Secondary Nodes

SnapMirror Secondary must have been added
Sync must have completed
DPX allows to perform an IA mapping and BMR from
Alternate Secondary Nodes
10
Page 15 - 5
Restoring from Alternate Secondary Nodes

DPX Management Console will specify the restore
data is coming from an alternate destination
11
Lab Task
Lab 15-1: Restoring from

Alternate Secondary
Duration: 20 mins
12
Page 15 - 6
Lesson 2
DPX Integrated Disaster

Recovery: D2D2T
13
DPX +Tape (D2D2T)

Performs and catalogs additional backup from a diskbased backup target to tape media (D2D2T)
DPX NDMP Backups can be used to create a backup of
the most recent DPX snapshot residing on the NetApp
FAS system to tape
Allows data to be archived offsite for compliance or DR
purposes and have much longer retention periods without
impacting disk capacity
14
Page 15 - 7
DPX NDMP Backup Job Definition Source

Backup Jobs are created in the
DPX Management Console under:
Backup
Backup > NDMP
NDMP
Multiple snapshots can be
incorporated in one NDMP Backup
Select the DPX Snapshots with .0
for the most recent backup
snapshot
15
DPX NDMP Backup Job Definition Destination

The destination will be an NDMP Device Server,
usually a tape device connected directly to the
NetApp Storage System
Considerations for NDMP Backup Destination:
NDMP devices do not support file level backups.
For best throughput, attach the NDMP device directly
to the NetApp secondary storage
Eliminates
between
Eli i t the
th need
d ffor network
t
k ttraffic
ffi b
t
the NetApp storage and the tape device
16
Page 15 - 8
DPX NDMP Backup Job Definition Backup Type

If an NDMP Device Server, the type of backups should
be dump as opposed to smtape.
17
DPX NDMP Restores

The Restore is a two step process (KB A002103):
Restore the snapshot to a NetApp volume from tape
Manually map the volume to a host via iSCSI
Now, you can access the file system structure and
data
* We will be discussing DPX NDMP Restores from tape in more detail in a later module
18
Page 15 - 9
Module Summary
Disc
Discuss
ss alternate secondary
secondar destinations and their
importance
Explain the process to restore DPX backup data from a
NetApp SnapMirror destination
Explain DPXs integration with NetApp SnapMirror
technology to provide a disaster recovery solution
Explain DPX +Tape feature to archive backup data to
tape
19
Page 15 - 10
Module 16 - DPX Tape Archiving
DPX T
Tape A
Archiving
hi i
Module Objectives
Configure
g
Tape
p Devices and Libraries for use with
DPX
Configure Backup-to-Disk Devices
Configure Media Management
Discuss the use of NDMP backups for D2D2T
protection
Discuss Recovery Scenarios
Page 16 - 1
Lesson 1
Device Configuration
DPX Archiving to Tape

The Tape option requires additional configuration for the
backup destination devices.
This can be devices of type:
Tape - Physical or Virtual Tape Library or standalone tape
devices / autochangers
DISKDIRECTORY
Required for catalog backups
The main configurations needed are:
Device Clusters and/or Tape Libraries
Media Pools
Media
Page 16 - 2
Device Clusters
A Device is any tape or disk drive used as the
destination for a backup
A Device Cluster is a set of devices of same media
type
Even a single Device must be defined within a Device
Cluster
A Tape Library or VTL is considered a logical device
cluster
Device Clusters
Device
Clusters
Jukebox
SAN
Jukebox
Device
Cluster
Type
Page 16 - 3
Device Types
Stand-alone tape drive
Tape library (jukebox) or VTL requires extra
installation of changer and slot range
SAN-attached devices also require special
configuration to allow resource sharing
Backup-to-Disk devices require special configuration
Device IDs - Tape

Syncsort does not develop Device Drivers
Therefore, DPX uses only the Operating System or
Vendor Device Drivers
Device IDs are given by the Operating System eg.
nrst0a
(NetApp)
\\.\tape1
(Windows)
Tapes must support variable length and extended
filemarks
Page 16 - 4
Device IDs - Robots

Windows
Use detect -i for installation
Must disable Windows OS Driver (Except if iSCSI)
Driver looks like \\.\sync_sa0
NetApp
Use sysconfig m to identify robotic arm
Driver looks like mc0
Robotic Changer Config

Can be configured in three ways:
Device
D i C
Configuration
fi
ti Wi
Wizard
d
DPX Auto-configuration Wizard
Manually
Create the jukebox, and specify the slot range and
changer driver
Configuring Slot Range
Using Slots = Data Tapes
Cleaning Slots = Cleaning Tapes
Slot Numbering Starts at 0
10
Page 16 - 5
Using Drive Serial Numbers

Unique IDs define the relationship between the O/S
(Device ID) and the tape drive location in the Jukebox
(Device Number)
Use manual methods for older types of tape libraries
Media will not unload with mismatched Device
Numbers/Device IDs
11
Using Drive Serial Numbers

Device Mapping - the
process of assigning
logical device names
to a physical device
(via Manufacturers
Serial Number) when
device shifting has
been detected
Device Number Set in Jukebox

Device ID Set by OS
Implemented via
Wizard (always) or
through Management
Console (selectable)
12
Page 16 - 6
Jukeboxes directly attached to NetApp Systems

When Jukeboxes are attached directly to NetApp
Storage Systems, Syncsort and 3rd Party utilities
cannot be used to discover configuration information
information.
Here native NetApp command line utilities must be
used.
For Medium Changer
Sysconfig m
storage
show
mc
t
h
For Tape Devices
Sysconfig t
storage show tape

13
Medium Changer
Command: sysconfig - m
displays tape library information
e g Device ID
e.g.
Command: storage show mc
provides the following information:
Media changer/library make and

model
Media changer/library PPN
Media changer/library serial
number
Media changer/library Fibre
Channel WWN
Media changer/library alias name
14
Page 16 - 7
Configuring Medium Changer in DPX

Commands to run
on the filer
command
co
a dp
prompt
o pt
before configuring
a Jukebox:
sysconfig m
storage show mc
sysconfig
fi tt
storage show tape
15
Tape Drives
The sysconfig -t command displays device and configuration
information for each tape drive on the system.
16
Page 16 - 8
Tape Drives (Cont)

Command: storage show tape
Provides the following information:
Tape drive PPN
Tape drive make and model
Serial number of the tape drive
Tape drive Fiber Channel WWN
Tape drive alias name
17
Configuring a Jukebox Tape Drive in DPX
18
Page 16 - 9
Device Troubleshooting
There are some Syncsort and 3rd Party utilities that can be used to
aid / troubleshoot Device configuration:
Syncsort
Detect Command line utility that scans the SCSI bus (including
Fibre Channel) and is used as an aid to configuration and
troubleshooting of libraries and tape devices
JITest - command line utility for testing robotic arm
3rd
functionality
Party
Tar - Tool on most UNIX and LINUX which can be used to write data to
tape. It is useful for testing tape devices. Tar is not capable of reading or
restoring data written to tape by DPX
NTBackup - included with most versions of Windows and can be used to
test tape drive functionality.
MTX - open source utility for testing robotic arm functionality

19
Lab Exercise
Lab 16-1 Configuring Tape

Devices
Duration: 20 mins
20
Page 16 - 10
Lesson 2
Media Management
21
Tape Flexibility
DPX writes in SIDF (System Independent Data Format)
tape format
Allows any-to-any backup and restore*
Data from any node can be written to any device
server during backup
Data written by any device server can be restored
using any other device server
The data must be restored to the original operating
and file system type
* This does not include NAS nodes
22
Page 16 - 11
Media Management
For a Media to be recognized by DPX it must first be
labeled with a given VOLSER (Volume Serial Number)
Media Pools must have available media for jobs to run
Jobs automatically select an appropriate Media from
the specified Media Pool
Media need to be added to the Media Pools
Labeling will write information in the beginning of the
Tape, including the VOLSER of this media
23
Media Pools and Media

Media pool is a set
of media of the
same type
Media
Pools
Each media volume

identified by a
unique VOLSER"
(Volume Serial
Number)
VOLSER may b
be
specified manually,
or it can be the
same as the
barcode
Media
Volumes
VOLSER
(Volume
Serial
Number)
Media Status
24
Page 16 - 12
Media Management (contd)

VOLSERs can be added to media pools in three ways:
1. Manually adding them to a Media Pool through the
Management Console
2. Labeling Barcoded Tapes manually through the
Management Console
3. Assigning Barcoded Jukebox Media to a Media Pool
(on-the-fly labeling will happen when first used)
25
1. Manually adding Volsers to a Media Pool

Select Configure / Media in the Management Console
Select on Add Media
Use only if the media does not have barcodes (small
libraries or stand alone tape drives)
The media is then labeled through the Device Control
Window using an available VOLSER from a specified
Media Pool
26
Page 16 - 13
2. Labeling Barcoded Tapes

Open the Jukebox through the Device Control
Window
Drag-and-drop VOLSERs onto the tape drive(s)
The VOLSERs will be added to the specified Media
Pool
27
3. Assigning Barcoded Jukebox Media to a Media Pool

Media must have barcodes
Use Add Media button in Device Control and select
the Pool to assign the media to
Drag the media to the Pool
Media will be automatically labeled during a
backup/duplicate job if needed
28
Page 16 - 14
Alternate Media Pools

Any Media Pool may have one or more Alternate
Pools sometimes known as a Scratch Pool (they
do not have to be called Scratch)
Scratch )
When the Media Pool is out of tapes, an empty tape
from the Alternate Pool will be allocated
When the data on the VOLSER expires out of the
catalog,
catalog it can go back to the Scratch Pool or stay in
the new pool (based on parameter setting)
29
Media Pools
Media must be added to a Media
Pool in one of the aforementioned
y or backups will fail ((unable to
ways
find a free tape)
Labeling brand-new tapes require
checking Ignore Read Error in the
Option pull-down menu in the
Device Control window
Overwriting existing tapes (tapes that
already have labels) require checking
Ignore Volser option in the Option
pull-down menu in the Device Control
window
30
Page 16 - 15
Life of a Tape
Before tapes are labelled, they
have a NEW status
When tapes are first labeled
labeled, but
before they are used, they have
EMPTY status.
After being used by a backup,
they have APPENDABLE
status.
When end-of-tape (EOT) is
reached tapes have status
reached,
FULL
Once all the jobs on a tape have
expired, tapes go back to
EMPTY
31
EOT
Life of a Tape (cont.)

New
Label Tape
at beginning
p with 80 Bytes
y
g
g ((VOLSER))
EOT
New Tape:
VOLSER
Empty
First Backup, expires in 7 days

7 Days
Appendable
VOLSER
Partition 1
Retention:
7 Days
Partition 2
Retention:
30 Days
Partition 3
Retention:
14 Days
FULL
. 2nd backup 30 days, 3rd backup 14 days

EOT
Retention:
EOT
VOLSER
Partition 1
32
Page 16 - 16
Life of a Tape (cont.)

After 7 days
14 Days
FUL
LL
Retention:
FULL
30 Days
EO
OT
Retention:
Partition 3
EOT
VOLSER
Partition 2
After 14 days
VOLSER
Partition 2
Retention:
30 Days
EMPTY
EOT
VOLSER
After 30 days, goes back to Alternate Media Pool (Scratch).
33
Cleaning Tapes
Jukebox drive cleaning-on-demand
A cleaning tape will be mounted automatically when
the drive requests it
The cleaning slot must be presented to the software,
and not reserved by the jukebox
34
Page 16 - 17
Lab Exercise
Lab 16-2 Performing Media

Management
Duration: 20 mins
35
Lesson 3
NDMP Backups
36
Page 16 - 18
What is NDMP?
Open standard protocol (TCP/IP-based) for networkbased backup
Allows for backup/restore of NAS devices that do not
allow for a backup agent to be installed. E.g. NetApp
filers
Runs in place of proprietary backup agent
NDMP Client/Deamon:
reads
data
Cli t/D
d and
d sends
d d
t
NDMP Server: writes data to secondary storage device
37
NDMP Tape Format

Does not use System Independent Data Format (SIDF)
like DPX Device Servers
Since NDMP Nodes are not running the DPX Agent,
the backup and restore functionality is limited
NDMP Backups / Restores can only be written locally
or to an APM node
Tape Mode Restore not supported
38
Page 16 - 19
Nibbler
Nibbler (APM) allows communication between DPX
and NDMP-enabled NAS devices
NAS Device must be running NDMP version 3 or
higher*
*NDMP version 4 is required if this NetApp filer is also

used
(Secondary
Storage).
d and
d ARSV destination
d ti ti
(S
d
St
)
39
NDMP Backups
Four Supported NDMP Backup Configurations
Local Backup
Data is backed up to a Tape Library/Tape Drive(s)
attached locally (SCSI of FC) to the filer.
Three-way Backup
Data is backed up to a Tape Library/Tape Drive(s)
attached to another filer.
Filer-to-Server Backup
ata iss backed
bac ed up to a Tape
ape Library/Tape
b a y/ ape Drive(s)
e(s)
Data
attached to a server.
Server-to-Filer Backup
Data residing on a open systems server is backed up to
a Tape Library/Tape Drive(s) attached to a filer.
40
Page 16 - 20
NDMP Backups
LAN
Tape Library
NDMP
NAS
Unix,
Linux or
Windows
NDMP
NAS
SCSI
NDMP
NAS
SCSI
Local Backup
Remote (3-way) Backup
Filer to Server Backup
Tape Library
Tape Library
Server to Filer Backup
41
NDMP Backups
NDMP Server to filer only supports file system

b k
backups
API database backups are not supported
42
Page 16 - 21
NDMP Backup Methods

Two Methods of Backing up NetApp Data
dump (Default)
Proxy server communicates with
the filer using NDMP, and issues
a dump command to the selected
tape drive(s)
Appropriate for file backup and restore
smtape (SnapMirror-to-Tape)
Proxy server communicates with the filer using NDMP, and issues
a snapmirror store command to the selected tape drive(s)
Appropriate for whole volume recovery (including all snapshots)
Note: SnapMirror License may be required on filer backed up
(Ontap 6.5)
The Backup Method is selected when the node is added to the DPX
Enterprise, but can be changed later
43
NDMP Backup Methods (contd)

The dump backup method
First creates a snapshot of the selected volume(s)
Backs up only this snapshot
Allows backup to directory level
Allows individual file restore
The smtape backup method
p volume(s)
( ) and associated snapshots
p
Backs up
together
Does not allow single file recovery
Used for disaster recovery, when snapmirror is not
available
44
Page 16 - 22
Defining a NDMP Backup

In the Management
Console, select
Backup,
p, NDMP
Select the Source
Folder level
(requires ONTAP
6.4.2+)
Select the Destination
Select Options and
Schedule
45
NDMP Backup Source Options

NDMP File History Handling
Disable File History
Process File History on NDMP Client
Process File History on Master Server
Enable NDMP Server Logging
Yes/No
Additional NDMP Environment
Any non-standard (vendor-specific) settings
46
Page 16 - 23
NDMP File History

File History Merged
Into DPX Catalog
DPX Master Server

Unix / Windows / Linux
NDMP Session
Initiates Backup
NAS Appliance
ID C
File History Info Written

Back to NDMP Client
SORT!
Backup Data Written

in Dump Format
Tape
Library
Dump File History
Sorted and Manipulated
Easy, point and click restores
DPX has the fastest FH processing
Records data for each file backed up
FH can impact individual file searches for

restores
47
Defining a NDMP Restore

In the Management Console, select Restore, NDMP
Select the Filer/Folder/File to be restored (FH enabled)
Select the Restore Destination (must be an NDMP
Node)
Select Options and Schedule (if applicable)
48
Page 16 - 24
NDMP Restore Destination Options

NDMP Recover Mode
Extract: requires scan through every tape
Direct*: mounts only tapes needed
Yes/No
Enables non-standard functionality
* Must be supported by vendor

49
NDMP Backup Limitations

No file exclusions
A job can contain multiple source paths
paths, but only one
destination per source node
No backup verification
"Catalog mode" restores only: tape mode restore is not
available
NDMP restores must be to NDMP nodes
If FH is enabled, the catalog space requirements are the
same as for standard backups
50
Page 16 - 25
Troubleshooting NDMP Backups

Ensure NDMP is enabled on the filer and that the latest
version is running
ndmpd
d d status
t t
ndmpd on
ndmpd version 4
*These are ONTAP commands; NDMP version 3 is needed for NDMP
functionality, but NDMP version 4 is needed on appliances that are used
as ARSV destination volumes.
Make sure the root password is correct
51
Troubleshooting NDMP Backups

Problem: A NDMP job appears to hang
The reporting of NDMP backups is very limited
sysstat 1 (This will show disk-read and tapewrite statistics every 1 second (ONTAP only)
The job may be cataloging. Monitor CPU activity on the
DPX master server and NDMP client node. If either the
Data
Manager process (datmgr
or ssdatmgr.exe)
D t M
(d t
d t
) or
NDMP file history module (ndmph or ssndmph.exe) are
consuming CPU, it shows that the job is cataloging.
52
Page 16 - 26
Lab Exercise
Lab 16-3 - NDMP Backups and

Restores
Duration: 20 mins
53
Lesson 4
Performing BMR from Tape
54
Page 16 - 27
Restore from Tape - BMR Restore from a NDMP

dump
The BMR functionality can be performed from a NDMP
dump backup after the data has been restored from
tape to a volume on the Filer with a few steps
* The BMR component must have been selected at the
time of backup for BMR to function.
55

dump
As long as the NDMP dump backup has not expired
from the catalog yet, restoring the data to the point
where BMR can read it,
it is not difficult.
difficult These
procedures only apply if your Filer node was defined
as NDMP type 'dump' at the time of your backup.
Note: The procedure here assumes that your NDMP
backup was done with File History enabled (default
g) If for some reason File History
y was disabled,,
setting).
then you will need to restore all of the data that the
backup contains. With File History enabled, you can
selectively restore only those QTrees that you are
interested in, saving time and space
56
Page 16 - 28

dump
Perform a NDMP backup, selecting $LATEST within the
desired volume. This will backup the latest snapshot within
the volume to go to tape.
57

dump
An example here
shows: a backup
of /vol/axatmp that
has been backed
up via NDMP.
To restore from
tape: select the
Restore -> NDMP
tab.
Selectively select
the QTrees to be
restore.
The next slide will
discuss the
destination of
where the tape
data is being
restored to.
58
Page 16 - 29

dump
1. Create a new volume on your Filer to restore the data
that was backed up from tape
2 Restore
2.
R t
QT
QTree data
d t from
f
tape
t
through
th
h the
th GUI
3. Create a snapshot for BMR to read data from

4. Run BMR and point it to the volume created in Step
1 (above).
5. Once restore is complete, manually remove the
restored data.
We will now look at each of these steps in more detail
59

dump
1. Create a new volume on your Filer to restore data
Create a new volume on your Filer where the host's
QTree data will fit. It is strongly suggested that you create
a new volume for your restore as eventual cleanup is
much simpler.
Alternately you can choose another volume to restore
yyour data to that is not the original/source
g
volume. Do not
use the original volume as the restore and snapshot
process may interfere with your existing live backups.
60
Page 16 - 30

dump
2. Restore QTree data from tape
In the DPX Management Console go to Restore->NDMP. Drill down to
the NDMP backup you are interested in
in. Select the individual QTrees you
need.
QTree names from DPX may take forms similar to:
[JobName]NodeName@1AB4E84B837E26D739E86A3758E371A7
[JobName]NodeName@{6C666CA2}
[JobName]NodeName@APPS_
It is important to restore all of the QTrees with a particular
[JobName]NodeName
pair.
APPS_ QTree
is
[J
bN
]N d N
i The
Th APPS
QT
i very important
i
t t as this
thi
contains ExpressDR metadata.
Once you have chosen the QTrees you are interested in restoring,
choose the destination to be the root of the destination volume (identified
above). Run the restore job, and wait for the restore to complete
61

dump
A new volume
has been
created on the
filer:
/vol/sv_restore
Restore QTree
data from tape
through the
GUI
Run and
Monitor the
Restore Job
62
Page 16 - 31

dump
Wait for the restore job to complete.
63

dump
3. Create a snapshot for ExpressDR to read data from
Once the restore is complete, you will need to create a snapshot for
ExpressDR to read data from. This can be done either though the
NetApp OnTap Filerview web application, or via the OnTap
command prompt.
You must create a snapshot in the destination volume above that is
similar in form to:
SSSV_JobName.0
Where "JobName" is the same as the "JobName" from the QTree
example above (the ending character is a zero)
The next slide will discuss the steps in creating a snapshot.
64
Page 16 - 32
Restore from Tape - BMR Restore from a NDMP dump

Steps to create a snapshot:
1. To change to advanced mode
priv set advanced
2 To create a snapshot
2.
Syntax: snap create <destination volume> <SSSV_JobName.0>
e.g.: snap create sv_restore SSSV_rkktmp.0
3. To list and confirm the new snapshot creation:
Syntax: ls /vol/<destination volume>/.snapshot
e.g.: ls /vol/sv_restore/.snapshot
65

dump
4. Once the snapshot is complete, you can run BMR and
point it to the destination volume. It will find the Node
QTrees you
y restored,,
Name / Job Name as indicated in the Q
and the data of the snapshot will be the date you created it
(today).
5. After you have completed the restore, you will need to
manually remove the restored data.
If you created a new volume for this restore task, then the
easiest way to clean up will be to "offline" your volume and
then "destroy" it. This can be done either via the OnTap
web interface, or the command line interface.
66
Page 16 - 33
DPX +T
+Tape
Recovery Scenarios
IA Map
Lesson 5
Performing Instant Access

from Tape
68
Page 16 - 34
Restore from Tape - Manual IA Map from a NDMP

dump
Manual Instant Availability(IA) is the ability to iSCSI-map a
QTree to a Windows node. To perform a Manual IA Map
from a NDMP dump, one must first restore the data from
tape back onto a volume of the filer.
Note: the procedures here assume that your NDMP backup
was done with File History enabled (default setting). If for
some reason File History was disabled, then you will need
to restore all of the data that the backup contains. With File
sto y e
ab ed, you ca
ect e y restore
esto e o
y tthose
ose
enabled,
can se
selectively
only
History
QTrees that you are interested in, saving time and space.
e.g. Only restoring one logical drive if multiple drives were
backed up.
69

dump
Perform a NDMP backup, selecting $LATEST within the
desired volume. This will backup the latest snapshot within
the volume to go to tape.
70
Page 16 - 35

dump
An example here
shows: a backup
of /vol/axatmp that
has been backed
up via NDMP.
To restore from
tape: select the
Restore -> NDMP
tab.
Selectively select
which QTree to
restore.
The next slides
will discuss how
to determine
which QTree
corresponds to
which logical drive
that was backed
up.
71

dump
Run the restore job and wait for the job to complete.
In our example, the restore job is restoring to a new volume on the filer:
e.g.: /vol/sv_restore
72
Page 16 - 36

dump
After the restore job has completed, the QTrees can be seen from
the filer command line:
The command shown below is to display the restored QTrees
Syntax: ls /vol/<destination volume of the restored data>
e.g.: ls /vol/sv_restore
*Please make sure the advanced privileges are set:
priv set advanced
73

dump
Using the restored QTree, one can manually IA Map the BEXIMAGE.RAW that corresponds to the logical drive
of the server to be recovered.
It can be difficult to determine which logical drive pertains to which QTree.
One can use the BMR_info.txt located in the ExpressDR folder of the filer to see which partition pertains to
which QTree.
Another alternative is to run a snap discoverdisks command from the backed up node through the
DPX Command Prompt
E.g. On the backed up node: Go to Start-> All Programs -> DPX Command Prompt
Syncui
c s <ip address of backed up node> sssnap
snap discoverdisks
Below shows the output of snap discoverdisks. The Serial # should be noted for each logical drive.
74
Page 16 - 37

dump
Before the BEXIMRAGE.RAW can be shared to a Windows host via
the iSCSI protocol, a LUN backed by a snapshot that contains the file
needs to be created first.
You must create a snapshot in the destination volume above that is
similar in form to:
SSSV_JobName.0
Where "JobName" is the same as the "JobName" from the QTree
example above (the ending character is a zero)
The next slide will discuss the steps in creating a snapshot.
75

dump
Steps to create a snapshot:
1) To change to advanced mode
priv set set advanced
2) To create a snapshot
Syntax: snap create <destination volume> <SSSV_JobName.0>
e.g.: snap create sv_restore SSSV_rkktmp.0
3) To list and confirm the new snapshot creation:
Syntax: ls /vol/<destination volume>/.snapshot
e.g.: ls /vol/sv_restore/.snapshot
76
Page 16 - 38

dump
Each logical drive contains a BEXIMAGE.RAW which will act as the source for the iSCSI
target.
The command below will show how to display the BEXIMAGE.RAW for a logical
drive
Syntax: ls /vol/<destination volume>/<QTree name>
e.g.: ls /vol/sv_restore/[rkktmp]BEX321CLIENT@{942AF2B5}
e.g.: ls /vol/sv_restore/[rkktmp]BEX321CLIENT@{FC2BAA72}
77

dump
In this example, the snapshot SSSV_rkktmp.0 is created on the volume
sv_restore.
To create a LUN that is now backed by this snapshot
snapshot, one would use
the lun create command:
lun create b <snapshot_lun_path> -o noreserve <lun_path>
This command will create a lun with name <lun_path> backed by the
file <snapshot_lun_path> that is contained in a snapshot.
In our example this command will look like the following:
lun create b
/vol/sv_restore/.snapshot/SSSV_rkktmp.0/[rkktmp]BEX321CLIENT@{942
AF2B5}/BEXIMAGE.RAW o noreserve /vol/sv_restore/restorelun
78
Page 16 - 39

dump
The command below will display the luns on the filer
Syntax: lun show
The output below will display the newly created lun
Output: /vol/sv_restore/restorelun
/vol/sv restore/restorelun
79

dump
In order to share this LUN to a Windows server, the Microsoft iSCSI Initiator
needs to be installed on the Windows server. This software can be downloaded
from www.microsoft.com/downloads. The software is already packaged into
Windows 2008 machines and can be started through Services
Services.
80
Page 16 - 40

dump
After installing the iSCSI
initiator on the Windows
server, make a note of
the initiator node name,
which can be found
from the iSCSI Initiator
Properties Window
(started from
Control Panel ->
iSCSI Initiator).
) This
initiator node name is
used to create the
iSCSI initiator group
(igroup) on the filer.
81

dump
To create the initiator group on the filer, issue the command:
igroup create i t windows <initiator_group_name> initiator_node_name>
with <initiator_group_name> the name of the iSCSI (-i option) initiator group created on the filer,
and <initiator_node_name> the node to be added to this group.
e.g.: igroup create i t windows rkkIAMAP iqn.1991-05.com.microsoft:bex321client.appgroup.loc
The igroup show command shows the existence of the group rkkIAMAP containing our node after
successfully completing the igroup create command.
command
e.g.: igroup show rkkIAMAP
82
Page 16 - 41

dump
The next step would now be to add the LUN created earlier to this
newly created initiator group.
This is done by issuing the lun map command from the filer:
Syntax: lun map <lun_path> <initiator_group_name>
e.g.: lun map /vol/sv_restore/restorelun rkkIAMAP
83

dump
On the client machine where the mapping was made, go into Disk Management
and Rescan Disks.
84
Page 16 - 42

dump
After rescanning the disks, the new disk needs to be brought online for browsing.
85

dump
The IA Map was made back to the node that was backed up. The F:\ volume is
the mapped LUN.
86
Page 16 - 43
Manual IA Map from an NDMP dump Restore from

Tape
After the files are recovered,
make sure to log off the map.
g
->
Select the Targets
Disconnect
87

dump
Then on the filer, issue the following commands to bring the lun offline and destroyed
Syntax: lun offline <lun_path>
e.g.: lun offline /vol/sv_restore/restorelun
Syntax: lun destroy <lun_path>
e.g.: lun destroy /vol/sv_restore/restorelun
These two commands will delete the LUN on the filer. After the LUN is deleted, also delete the snapshot
created used to create the LUN, by issuing the following command on the filer:
Syntax: snap delete <volume_name> <snapshot_name>
e.g.: snap delete sv_restore SSSV_rkktmp.0
The volume where the QTree was restored can be destroyed as well if the restore operation has been
completed.
88
Page 16 - 44
Module Summary
Config
Configure
re Tape De
Devices
ices and Libraries for use
se with
ith
DPX
Configure Backup-to-Disk Devices
Configure Media Management
Discuss the use of NDMP backups for D2D2T
protection
Discuss Recovery Scenarios
89
Page 16 - 45
M odule 17 - DPX Catalog M aintenance
DPX C
Catalog
t l
M
Maintenance
i t

Senior DPX Manager Consultants
Module Objectives
E
Explain
l i th
the iimportance
t
off th
the DPX C
Catalog
t l
Administer / maintain DPX Catalog
Discuss the DPX Catalog maintenance procedures
Catalog Report
Catalog Condense
Catalog Backup, including configuring a
S
C O
de ce and
a d media
ed a
DISKDIRECTORY
device
Catalog Restore and Master Server recovery options
Remove all traces of an existing job from the catalog and
free up disk space on NetApp Secondary volume
Module 17 - DPX Catalog Maintenance
Page 17 - 1
The DPX Catalog

Central database for DPX solution
Proprietary, flat-file database
Heart of the enterprise
Collection of files / folders located on the DPX Master
server
...\DPX\db
...\DPX\sched
...\DPX\cat
Requires regular maintenance and backup
The DPX Catalog (contd)

Every time you perform a backup or make a configuration
change to your Enterprise, the catalog is updated
In particular, a backup job updates the catalog with
information identifying the contents of every snapshot
being stored and, if File History is enabled, every file
backed up. This information is crucial during restores.
A jobs Retention Period defines how long that its
information stays in the catalog. When a job reaches the
end of its Retention Period (the expiration date)
date), all relevant
catalog objects must be updated to reflect this change.
Because the catalog is so vital to DPX, it needs to be
properly maintained. To maintain the catalog, you should
regularly perform essential Catalog operations.
Page 17 - 2
The DPX Catalog Cont.

All essential Catalog operations can be accessed via the
Catalog main menu option in the DPX Management
C
Console.
l
Catalog Menu - Job Functions
Page 17 - 3
Edit Catalogued Job Instance

Retentions period can be changed per instance
Manual Expiration Catalogued Jobs
Right Click
Note: Multiple job instances can be selected using Ctrl+Click or Shift+Click

Page 17 - 4
DPX Catalog Maintenance
Condensing Catalog
When a job is expired (either manually or when its
retention period is reached), it is only marked for
deletion in the catalog.
Likewise when an object is manually deleted.
The actual purge happens when condensed.
Maintaining Catalog
Catalog protection
Catalog recovery
Catalog Condense
Condense is the primary catalog maintenance operation
and it should be performed on a regular basis. Once a day
is recommended. The catalog condense essentially
performs these main functions:
Deletes the recovery points that are no longer required
Reduces the size of the catalog
When run, backups that have passed their retention period
are removed from the catalog and their snapshots from
secondary storage (for File Level backups, any media used
by the job will have their status updated
updated, allowing reuse and
recycling).
Deletes db files associated with expired jobs/tasks and any
objects manually removed from the Enterprise
10
Page 17 - 5
Catalog Condense Configuration
Create / Edit
Schedule
Run or Run
and Monitor
11
Scheduling Catalog Condense
Recommended to run
Catalog Condense on
a daily basis
Recommended to run
before scheduled or
manual Catalog
backup
12
Page 17 - 6
DPX Catalog Protection

Because of the importance of the Catalog to all DPX operations, it is
recommended that its protection be given a high priority.
The process for DPX Catalog protection is summarized as follows:
1. The catalog will initially be backed up to disk directories on the
master server. A disk directory is a file on a server which has the
characteristics of a tape, including a volser (Volume Serial Number).
2. The disk directories are backed up to the SnapVault Secondary
whenever the master server is backed up.
Note: It is recommended that the disk directories be set up on a
volume separate from
the DPX core operating system drives ((such as
f
on the D: drive for Windows). Separating the disk directories from
system drives may mitigate risks of single device failure. It will also
help prevent the catalog backup from interfering with the storage of
the live DPX Catalog database.
13
DPX Catalog Protection (contd)

There are four major tasks for initially setting up catalog
protection in an DPX environment.
S t up a DiskDirectory
Set
Di kDi t
D i and
Device
d media
di on th
the M
Master
t S
Server
Schedule a daily Catalog Condense
Schedule a daily Catalog Backup to a Disk Directory
Schedule a daily Master Server Backup to the SnapVault
Secondary Filer
Note: As part of this deployment, the catalog condense,

catalog backup,
backup and master server backup must be scheduled
to run daily. The backup administrator can reschedule them to
suit the needs of his or her own Enterprise at a later time.
Only through this method can you be sure that consistent
catalog backups will be available for future restores.
14
Page 17 - 7
Create Device Cluster

1. On the Master server,
create a directory to serve
as the destination for the
catalog backups. This
should ideally be on a
separate volume from the
DPX installation volume.
Eg E:\Catbackups
2. Go to Configure->Devices
3. Select Enterprise and click
Add Device Cluster
4. Add the Device Cluster
Name and ensure Device
Type is DISKDIRECTORY
5. Click on Add to create the
Cluster
15
Create Device
1. Click on the newly
create Device Cluster
and Click on Add
Device
2. Supply the Device
Name
3. For Logical Node
Name, add the name of
the server on which
you created directory
in step 1
4. For Device ID add the
yy
you created
directory
earlier
5. Click on Add to create
the Device
16
Page 17 - 8
Create DISKDIRECTORY Media Pool & Media

1.
Go to Configure Media and click on Add

Media Pool
2.
Supply a suitable name eg Catalog and

ensure Type is DISKDIRECTORY
Click on Add to create the Media Pool
3.
To Create Media
1.
2.
3.
4.
5.
6.
Select Media Pool and click on Add

Media Volume
Add a capacity (this is a nominal figure
and has no bearing on actual capacity
Maximum passes is also not applicable
to disk media so can be any figure
Volume Serial Number This will be the
VOLSER of the 1st tape created
Number Volumes How many tape to
create. VOLSER supplied above will
increment by 1 for each new media
volume.
Finally, click on Add to create the Media
Volumes
17
Configure DISKDIRECTORY Media (Complete)
Media Volumes
created and are now
ready to use
18
Page 17 - 9
Configure and Schedule Catalog Backup

Once a DiskDirectory device and media have been
created on the Master Server, to fully protect the
catalog against loss or corruption Catalog Protection
needs to be configured. To do so:
Schedule a daily Catalog Condense (Choose a time
when no backups are scheduled to run)
Schedule a daily Catalog Backup to a Disk Directory
for some time after the Condense (allow time for
Condense to finish)
Schedule a daily Master Server Backup to the
SnapVault Secondary Filer
19

Go to Catalog>Backup
O l Destination
Only
D ti ti iis
required. Select Device
and Media Pool created
for this purpose
These jobs can be
scheduled just like any
other job.
Recommended
R
d d to
t
schedule a daily Catalog
Backup to follow the
scheduled Condense
20
Page 17 - 10

Once the Daily Catalog Backup to DiskDirectory has
been configured and Scheduled, a Daily SnapVault
Backup of the Master Server should also be
Scheduled.
This provides 2 layers of protection for the critical
Catalog data.
The ability to quickly and easily restore the Catalog in
the event of database corruption or to restore files from
jobs that have expired from the catalog.
The Ability to recover the entire Master server and its
catalog in the event of server / volume loss.
21
Catalog Backup - Alternative Method

As stated previously, the DPX Catalog is just a collection of
files stored on the Master server in the following folders:
...\BEX\db
\BEX\db
...\BEX\sched
...\BEX\cat
As such, these folders can be manually (or via a scheduled
script) copied to an alternative location, which can then be
backed up using an DPX Advanced Recovery backup and
used to recover the Catalog
in the ffuture.
C
Note: The CMAgent Service should be stopped when
copying Catalog folders as there will are open Catalog files
whilst the service is running
22
Page 17 - 11
Catalog Maintenance and Recovery Scenarios

Recovering an DPX installation & catalog volume
(say. D:)
Recovering an DPX Master Server
Recovering corrupt catalog, db or sched files.
Completely removing all references of a job from the
catalog and its data from secondary storage
23
Recovery Scenarios
If you have lost the volume that contained the original
DPX Master server installation, and the catalog: (D:
volume is lost.)
lost )
Repair / replace the servers disks and then use DPX
IA to recover the D: drive from the Advanced Recovery
backup.
If you have lost the entire Master server
Repair / replace the servers
server s disks and then use BMR
to recover all drives from the Advanced Recovery
backup.
24
Page 17 - 12
Recovery Scenarios
Catalog Corruption - If some or all of the files within the DPX Master
server install location are corrupt or missing.
\BEX\cat,
\BEX\cat
\BEX\db,
\BEX\sched
Option 1.
Restore Catalog from the backup of the last known good recovery point
Option 2.
If you have taken a manual copy of the catalog folders and have this
location included as part of an AR backup
backup, use DPX Instant Availability
to map a drive of the last known good recovery point of this copy.
Stop the CMAgent Service on the Master Server and copy the cat, db
and sched folders to the live catalog location
Restart the CMAgent Service
25
Recovery Scenarios
You wish to remove all traces of a job from the
catalog, including the base snapshot from the
secondary destination volume in order to free up
space.
Go to Catalog->Job Functions
Expire all instances of the job
Delete the job definition
Run
Catalog
Condense
R aC
t l C
d
26
Page 17 - 13
Lab Exercise
Lab 17-1 Performing Catalog

Maintenance
Duration: 25 mins
27
Module Summary
Explain the importance of the DPX Catalog
Administer / maintain DPX Catalog
Discuss the DPX Catalog maintenance procedures
Catalog Report
Catalog Condense
Catalog Backup, including configuring a
DISKDIRECTORY device and media
Catalog Restore and Master Server recovery
options
Remove all traces of an existing job from the
catalog and free up disk space on NetApp
Secondary volume
28
Page 17 - 14
Module 18 - DPX Change Journal
DPX Ch
Change J
Journall
Module Objectives
Explain the function of the client change journal
Describe the various components of the change journal
Perform simple tasks related to change journal
troubleshooting scenarios
Page 18 - 1
Change Journal Overview

What is the Change Journal?
Low level driver that keeps track of changed blocks on
di k and
disk
d provides
id thi
this iinformation
f
ti att runtime
ti
off the
th
backup job
Modifying the Change Journal
Only for re-base of a volume
Issues with the journal should be handled with
assistance
off supportt
i t
Architecture & Components

BexWinCJ
Kernel mode volume filter driver
BexWinCJFlt
Windows/system32/drivers
Kernel Mode File System Minifilter Driver
JournalDll
User-mode library
JournalCli
Command line utility
ChangedBlocks
User-mode change journal library
CJ Recovery Feature
Page 18 - 2
Filter Driver
The filter driver keeps track of blocks that change on the volume being protected
Tracking info is stored in bitmap format in file named with format CJ_x where x
will be the incarnation no. in increasing order
These CJ bitmap files are kept on the corresponding volume being protected under the
repository folder named Backup Express Journal Depository
Each bitmap file stores bitmap
representing changed blocks info over
certain period of time
This time info is stored in CJs
metadata file named cjrepo in its
repository folder
This cjrepo file or CJ_x bitmap files
are internal to CJ and not supposed to
be accessed or changed by anybody
else
Filter Driver
First instance of a backup job copies all the allocated
blocks from the volume
This
Thi is
i referred
f
d as B
Base R
Recovery P
Point
i t
After the first instance job, tracked block info is used
to identify and transfer only changed blocks during
backup job.
If CJ had
any bl
blocks
h d nott missed
i
d tracking
t
ki
k since
i
llastt
backup job instance then only changed blocks are
transferred.
This is referred as Incremental Recovery Point
Page 18 - 3
Drivers
BexWinCj.sys
BexWinCjFlt.sys
Located in <Windows path>\system32\drivers
directory
CJ Registry Entries
CJ registry entries - If properly configured, you will
find all BexWinCj settings in the following location:
HKLM / System
S t
/ CurrentControlSet
C
tC t lS t / Services
S i
/
BexWinCj
HKLM / System / CurrentControlSet / Services /
BexWinCjFlt
NOTE: The registry variables have details about the
Journal State
State, location of the driver files and other CJ
book-keeping.
Page 18 - 4
Change Journal Folders

Hidden Files and Folders under the
root of all volumes being protected
\Backup Express Jobs
Database of all DPX backup
jobs run on that volume of the
server
\Backup Express Journal

Depository
Contains all journaling
information related to the
volume
Used to store checkpoint files at
p jjob
the end of everyy backup
\Backup Express Change

Journal
Must enable show hidden files and
Folders to view these folders
Debug Trace
CJ driver takes 2 levels of debug
Basic (critical / error messages)
Advanced (Informational / Alert)
Enabled by appended d 3 or d 5 to SSSNAP module
10
Page 18 - 5
Forcing a Base
Use syncui command line interface to disable/enable
cj on a given volume to force a base
syncui
c s <ClientServerName> sssnap
snap disablecj D:
snap enablecj D:
quit
11
Module Objectives
Explain the function of the client change journal
Describe the various components of the change journal
Perform simple tasks related to change journal
troubleshooting scenarios
12
Page 18 - 6
Module 19 - DPX Design & Advanced Configuration
DPX D
Design
i
Considerations and

Senior DPX Consultants
Module Objectives
Explain how to architect a complete block level solution
using a combination of NetApp and Syncsort technologies
Explain some of the design concepts that need to be taken
into consideration when planning an DPX implementation
Discuss remote seeding
Explain the Design Considerations of an DPX Enterprise
Discuss issues around Network Security and Firewalls with
DPX
Manage users in an DPX Enterprise
Module 19 - DPX Advanced Design and Configuration Topics
Page 19 - 1
Lesson 1
DPX Design Considerations
DPX Advanced Recovery Best Practices Guide

https://www.syncsort.com/support/kb/A004001.htm
Install, Configure, Patch

Filer / XR Server Configuration
Backups and Restores
Testing: Restore, Snapshot Verify, ExpressDR
Tertiary Data Protection
Remote Site Considerations
Firewall
DPX Administrator Accounts
Reporting
Page 19 - 2
SnapVault / OSSV
There are some restrictions imposed by the NetApp
Secondary device that impacts the way that one
should create the DPX backup jobs
Each volume is limited to 250 snapshots*
Each filer is limited up to 500 volumes*
* Refer to NetApp documentation for the latest limits
Defining DPX and OSSV Backup Jobs

Restriction: Limit of 250 Snapshots per Volume
Each volume on the secondary is limited to 250
snapshots, and each DPX job creates a snapshot at
the conclusion of the job.
Each DPX SV backup job has a Snapshot Retention
associated with it.
That implies that the maximum retention (in days) of a
given SV relationship is limited to:
250
Number of times the job runs per day
Page 19 - 3
Defining Backup Jobs

Restriction: Limit of 500 Volumes per Controller*
Since each DPX backup job writes to a volume on the
secondary, this restriction would limit the number of
DPX backup jobs that can be defined to have a single
filer as a secondary to 500
If each job backs up 10-15 servers, this restriction
would limit one to 5000
5000-7500
7500 servers that would use
the filer as a secondary
* depends on the version of ONTAP
SnapVault Summary
Each DPX Backup Job should have as destination a
single volume on the filer
The destination volume can also be used by other
backup jobs to take advantage of de-duplication
Jobs should be defined and scheduled not to overlap
to the extent that the number of concurrent SnapVault
transfers exceed the allowed number
Page 19 - 4
Advanced Protection Guidelines

Pre-Implementation:
Ensure the client machines have the latest Microsoft
updates
Ensure that all Microsoft VSS (Volume Shadow Copy
Service) Hot Fixes have been deployed
Perform chkdsk operations on all volumes that will be
backed up using ARSV (Knowledge Base Article A003817)
Ensure optimal network performance between Master
Server, Clients and Destination Filer(s)
Confirm Master Server, Clients and Destination Filer(s) can
resolve all hostnames and use appropriate network paths
Advanced Protection Guidelines

Post-Implementation:
Keep DPX updated/patched
Use BEXCHKDSK and NOT CHKDSK for source volumes
(KB Article A003819)
Utilize the Snapshot Verifier utility as outlined in
Knowledge Base article A003945 to periodically verify
OSSV Backups.
10
Page 19 - 5
Remote Seeding
Used to backup nodes at remote sites and consists of the
following major steps:
Perform an Express
p
Image
g Backup
p of Source volume on
remote node
Transport the Media
Restore the Image to a temporary node
Define and save a OSSV or Advanced Server Job
Prepare the change journal
Run the first base
Run
R iincrementals
t l ffrom the
th remote
t server
Usually Remote seeding requires Syncsort Professional
Services implementation
11
Remote Seeding
Remote Site
Central Location
DPX Client
Seeding Node
SV Base Backup
Image Backup
Image Restore
Remote Device Server

Device Server
12
Page 19 - 6
Generic Storage Template - Definitions

On average a backup environment contains many
servers distributed over many local and remote sites
Th St
The
Storage Template
T
l t defines
d fi
groupings
i
off servers
based upon the Recovery Time Objective and the
Recovery Point Objective of each server in that group
The Storage Template consists of four components
(or groups):
One Main Site, which contains the Syncsort DPX
Master Server
One D/R site, which mirrors the Secondary Server(s)
from the Main Site
Many to None Medium Sized Sites
Many to None Small Sized Sites
13
Generic Storage Template - Small Site

Site Layout
1-3 Servers (OSSV primaries only)
Non-application
pp
Servers ((or acceptable
p
application
pp
downtime)
Data Recovery Requirements
RTO: long acceptable data recovery time (data and
application if applicable)
RPO: less frequent backups
No Instant Availability functionality required
No BMR functionality required
t a secondary
seco da y seed
g via
a tape
Initial
seeding
Only supported for Syncsort Agents
Requires a tape drive local to primary and secondary sites
Site Role
Source for SnapVault Data to Medium or Large Site
14
Page 19 - 7
Generic Storage Template - Medium Site

Site Layout
3 to 10 Servers (OSSV/SV primaries, one OSSV/SV
secondary)
Application Servers
RTO: short acceptable data recovery time (data and
applications)
RPO: more frequent backups
Instant Availability functionality required
ExpressDR functionality required
t a Seco
da y Seeding
Seed g via
a Tape
ape [Requires
[ equ es local
oca tape
Initial
Secondary
drive]
Site Role
Destination for Local OSSV/SV Data
Destination for Small Site(s) SnapVault Data
SnapMirror Source for Large Site
15
Generic Storage Template - Large Site

Site Layout
Many Servers (OSSV/SV primaries)
At least one SV Secondaryy (Nearstore)
(
)
Application Servers (including DPX Master Server)
RTO: short acceptable data and application recovery time
RPO: more frequent backups
Instant Availability functionality required
ExpressDR functionality required
Robotic Tape device for data archival purposes
Site Role
Destination for local OSSV/SV data
Destination for Medium Site(s) SnapMirror data
Archival of OSSV/SV/SM/DPX Catalog Data to Tape
SnapMirror Source for D/R site
16
Page 19 - 8
Generic Storage Template - Disaster recovery Site

Site Layout
At least one SV Secondary (Nearstore)
Site Role
SnapMirror Destination for Large Site
Note:
A DPX Enterprise will contain one Large Site, and may
contain several Small and Medium Sites. The Master
Server is local to the Large Site.
17
Generic Storage Template

Data Transfer Method: SnapVault
Medium A
Small A
MS
UNIX
FAS2040
WIN
/vol/SA
/vol/MA
Data Transfer Method: SnapMirror

Large
UNIX
UNIX
FAS3160
UNIX
WIN
SM Vols
/vol/Ljb0
/vol/Ljb1
...
D/R Site
FAS2040
UNIX
Filer
UNIX
UNIX
WIN
WIN
Filer
Filer
Secondary Volume
Name Uniqueness
Important
DPX Supports Remote
Seeding of Secondary
SM Vols
TAPE
Note: DPX supports SnapMirror to Tape
Data Transfer Method: NDMP Backup (dump)

18
Page 19 - 9
Lesson 2
DPX Advanced
Configuration
19
Backup Job Source Options
20
Page 19 - 10
Backup Job Source Options
21
Backup Job Source Options - Source Options

Task Data Transfer Retry Count
Controls the number of checkpoint retries of an
i t
interrupted
t d backup
b k
job.
j b
Task Retry Intervals (Min.)
Controls the frequency of checkpoint retries of an
interrupted backup job.
Throttle
Enter a value in KB/s (kilobytes per second) to
serve as the
bandwidth
th maximum
i
b d idth allowed
ll
d for
f data
d t
transfer between source server and destination
server. Default 0 is maximum bandwidth.
22
Page 19 - 11
Backup Job Source Options - Source Options

Resolution Auto Cancel Interval (Min.)
In attempts to retry a failed snapshot attempt, if the retry
is unresponsive,
unresponsive then DPX initiates job auto-cancel
auto cancel after
this interval.
Resolution Retry Count
Determines how many times to retry a failed point in
recovery attempt.
Wait Interval Between Retries (Min.)
Determines the time to wait between retry attempts for a
failed point in recovery attempt.
Data Transfer Auto Cancel Interval (Minutes)
-If a job does not get an indication of "active" status
during the data transfer phase of the job, then a job
cancellation is initiated after this interval.
23
Backup Job Source Options Source Applications Options

Covered in
Application
Recovery
Modules
24
Page 19 - 12
Backup Job Source Options - Pre- and Post- Scripts

Set scriptname@hostname
in the job options, allows
you any functionality you
can script
Copy the script to
DPX/sched/scripts on the
client where it will run
The only requirement is
that the script be
executable on the client
that it is placed.
25
Backup Job Source Options Source NDMP Options

NDMP File History
Disable
Process on client
Process on Master
(yes/no)
Controls the routing of NDMP
server generated log
messages to the job log file
env1name=value, etc
Use the Help button to see
reserved variable names that
must not be used.
26
Page 19 - 13
Restore Job Source Options
27
Restore Job Destination Options

Covered in
Application Recovery
Modules
28
Page 19 - 14
E-mail / SMTP Notification

Also set in Configure > Enterprise
Administrator Email Address
SMTP Host Name
SMTP Port No.
29
SNMP Configuration
Also set in Configure > Enterprise
Configure hosts to receive traps
MIB files in SSPRODIR\misc ((bex_mib.hp
_
p and bex_mib.nov)
_
)
30
Page 19 - 15
E-mail Notification
Set in Configure > Default > Backup > Report
Enter email addresses for To:, CC:, and BCC fields
Customize the subject line with standard variables
%RC (J
(Job
bR
Return
t
Code)
C d )
%JOBNAME
%JOBID
%JOBTYPE
31
Authentication Modes
Set in the Configure > Enterprise screen
Two Authentication Modes:
Native
N ti (default
(d f lt mode)
d )
LDAP
32
Page 19 - 16
LDAP Authentication
Authenticates users against an LDAP Server
Provides better security and centralized user
managementt
Supports Microsoft Active Directory (AD) and
OpenLDAP (Linux)
Windows 2003, Windows 2008, Windows 2008 R2
33
LDAP Authentication
Default Port
Uses Port 636
1-20 unicode
characters
34
Page 19 - 17
LDAP Authentication: Settings

Bind DN
Bind Distinguish Name: name used for authentication
of connection to the LDAP server
Uses simple bind
SASL and anonymous bind are not supported
For AD or LDAP, specify a fully distinguished name in
LDAP form
For AD, Principal Name format can also be used
(<username>@<domain>)
Base DN
Base Distinguish Name: specifies where users and
groups are located
In AD, default location is the Users folder in the domain
(cn=Users, dc=<Domain>)
35
LDAP Authentication: Settings

Username Attribute
36
Page 19 - 18
LDAP Authentication: Best Practices

Provide the BaseDN carefully for proper searching of
users
If SSL is
i nott used,
d username/password
/
d will
ill be
b sentt in
i
clear text to the LDAP server
For logins, use the same Username Attribute
specified in the Configure > Enterprise settings
If the LDAP username attribute is changed the user
has to be provisioned again into DPX
DPX checks the LDAP user status periodically
If the user is removed or disabled GUI will display an
error message and the user has to restart GUI and
login again
37
User Administration
DPX has the ability to create users other than the
sysadmin user
Th
These
users (or
( sub-administrators)
b d i i t t
) can be
b assigned
i
d
the authority to manage specific node groups, device
clusters, media pools and jobs
Creating new users varies depending on the
Authentication Mode: Native or LDAP
LDAP Mode:
Native Mode:
Username and
Password are required
Only Username is
required
38
Page 19 - 19
User Administration
To create a new user,
select Configure,
Administrators and Add
Administrator
[Native Mode]Set a
username and password
[LDAP Mode] Specify
the username configured
in the LDAP/AD
Assign resources to the
admin (node groups,
groups
devices, jobs, jukeboxes,
media)
Assign privilege classes
to the admin
39
Firewall Support
Out-of-the-box, DPX randomly allocates as
many TCP ports as needed.
40
Page 19 - 20
Firewall Support (contd)

For Auto update functionality:
DPX Server * tcp-> DPX Client 9202 tcp (autoupdate control
comm.)
DPX Server * tcp-> DPX Client 9104 tcp (autoupdate data
transfer)
Backup functionality:
DPX Client * tcp -> DPX Server 6123 tcp
DPX Client * udp -> DPX Server 6123 udp
DPX Client * udp -> DPX Server 6124 udp
e * tcp -> DPX C
e t 6123
6 3 tcp
DPX Se
Server
Client
DPX Server * tcp -> DPX Client 10000 tcp
DPX Server * tcp -> DPX Client 15660 tcp
DPX Server * tcp -> DPX Server 10000 tcp
41
DPX Firewall Support

If using Virtualization
DPX Client * tcp -> master server 6123 tcp

DPX Client * udp -> master server 6123 udp
DPX Client * udp -> master server 6124 udp
Master server * tcp -> DPX Client 6123 tcp
ESX VM 68 udp -> Virtualization proxy 67 udp (DHCP/BOOTP)
Virtualization proxy 67 udp -> ESX VM 68 udp (DHCP/BOOTP)
ESX VM * udp -> Virtualization proxy 69 udp (TFTP transfer)
Virtualization proxy * udp -> ESX VM * udp (TFTP transfer)
p -> DPX Server 3260 tcp
p
ESX VM * tcp
Master server * tcp -> DPX Server 10000 tcp
DPX Client * tcp -> ESX VM 10000 tcp
Virtualization proxy * tcp -> DPX Server 10001 tcp
Protection
42
Page 19 - 21

0-65535
The default is for the cmagent process to dynamically
allocated
ll
t d ports
t ffor DPX processes and
d NDMP data
d t
connections
To Limit the ports
Edit registry string value SSICMAPI
Set -pfd (Port Forwarding) option to y for using only
the
th single
i l CMAgent
CMA
t portt (default=6123)
(d f lt 6123)
This feature helps in dealing with firewalls
43

Append pfd y to the string
44
Page 19 - 22
DPX Software is made up of several different
modules/processes
It uses a set of configuration parameters for each
module to enable detailed configuration / tuning
Two ways to retrieve/set parameters
Configuration text entries/files or Windows Registry
45
Configuration Parameters
In Windows, product-specific Information held in Registry Key:
HKLM/Software/Syncsort/BackupExpress/HOSTNAME/0
SSPRODIR = Install
Directory
SSICMAPI =
Communication
Parameters for Cmagent
46
Page 19 - 23
Configuration Management in the Management

Console
From the Configure Enterprise, right click on a node
and select Manage Configuration. Note the warning!
47
Configuration Management in the Management

Console
For each DPX module, advanced parameters can be set /
changed from here.
It is highly recommended that any changes to these
parameters
t
b
be made
d only
l under
d guidance
id
from
f
S
Syncsort
t
Support personnel
48
Page 19 - 24
Lab Task
Lab 19-1 Managing DPX Users

D ti
Duration:
20 mins
i
49
Module Objectives
E
Explain
plain ho
how to architect a complete block le
level
el sol
solution
tion
using a combination of NetApp and Syncsort
technologies
Explain some of the design concepts that need to be
taken into consideration when planning an DPX
implementation
Configure remote seeding
Understand
U d t dD
Design
i C
Considerations
id ti
off an DPX
Enterprise
Manage users in an DPX Enterprise
Discuss issues around Network Security and Firewalls
with DPX
50
Page 19 - 25
Appendix A - NSB Reporter
NSB R
Reporter
t
Module Objectives
Describe the value of Syncsort NSB Reporter
Explain the main features of NSB Reporter
Install and configure the NSB Reporter Agent on a
Windows Master Server
Read and use the data collected from NSB Reporter
Set up and schedule automatic reporting per e-mail
Find the general logs that could give you indications if
an issue comes up
Appendix 1 - NSB Reporter
Page A - 1
What is Syncsort NSB Reporter?

A separately-licensable web-based reporting utility
Runs an agent on the NSB Master Server
Interface provides statistics, trending, forecasts and
raw tabular information
Provides backup statistics, as well as OS statistics
(memory / CPU) and disk utilization
NSB Reporter - Key Features

Storage and Assets
Capacity planning, Forecasting and trending
Ch
Chargeback
b k
Reporting
Pre-defined and Customized reporting, Scheduled
reports to email or publish
User and File Analysis
User Usage, Rules Engine to find specific files
Performance
Monitoring, Alerting and Notification and Server
consolidation
Page A - 2
NSB Reporter - Installation Requirements

Reporter Server Requirements
Windows OS w/ a minimum of 2GB RAM, (recommended
3GB) and between 150MB - 1 GB free disk
Note: cannot be the same machine as the NSB Master
Server
IP address and MAC address needed for license by default
you have a 30 day evaluation license for a pre-set number
and type of resources
Master Server Agents Available
Windows 2000, 2003, XP
Solaris
7,8
S
8 and 9
Linux RedHat 7.2, 7.3, 8 and 9
IBM AIX 4.3 and above
HP-UX 11
Tru64 40F, 50, 51, 51a, 51b
5
NSB Reporter - Architecture
10 Additional
3rd Party Licensed
Interfaces
Page A - 3
When you start

Open Console in browser on port 9000
Ad i password
Admin
d in
i text
t t file
fil in
i installation
i t ll ti
directory
di
t
admin:admin
default on setup to be changed from Administration
part - user
edit admin user
Exclude MySQL dbase from anti-virus to prevent
corruption in the db
You can use a 30-day trial period to test basic
functionality choice when installing
Initial set up
When running with reporter backup
licenses, you only need to install
Reporter Agent on your master server default setting in Reporter will add node
into Reporter Environment
If not already visible, add Master server
as a normal specific OS node first
Select from 'Choose Type' - OS Windows
if y
your master server is windows
Add - fill out and add node
Select from 'Choose Type' - 'Backup
Syncsort BEX' - fill out details and click
save
Page A - 4
Adding Hosts and NSB Master Server

You first add
the master
server as a
node
Later you
add the
Master
Server as a
Backup
Device same menu,
but Backup
Syncsort
BEX
Adding a Master Server as normal host

Adding master server as normal
host - the license is a normal
license - not the backup
p license
Click on Edit to get back to this
configuration screen
Click on Agent to get to the
several configurable resources
10
Page A - 5
Configuration Master
Adding master
server as a backup
d i
device
Provide installation
directory, username
and hostname.
11
Configuration Master (contd)

Add NSB Master details:
Installation Directory or
SSPRODIR
sysadmin and
password
Resolvable server
name as resource
name
Set Monitor
Monitor Backup
Server to On
12
Page A - 6
Managing - Next steps

Product Overview and Configuration
E-mail reporting set up
Set backup window time frame
Create new users - 2 types, administrators and users
(users cannot see Administration field)
13
Set up E-mail reporting

Check the Server Setup\Server tab in the
Administration menu and set SMTP host and address
sending reports
Reports can be attachments or imbedded into the Email
14
Page A - 7
Set up E-mail reporting (contd)

Pre-defined reports available (Quick + Enterprise
Reports)
C t
Customizable
i bl reports
t possible
ibl (My
(M Reports)
R
t )
Scheduling of reports to be made and send
15
Set up E-mail reporting (contd)

E-mail reporting done when scheduling
Create and save report
Schedule it
At recipient to the scheduled report
Test sending report
16
Page A - 8
Force collection start

Collection can take up from 5 to 15 minutes
depending on how busy the client node is
Click on HOSTS and select the desired node
Click on storage tab and back on the console tab to
force collection start
Nodes can be set to join the environment upon
installation
17
Agents upgrade
Upgrading Agents from the Management Console;
administration, upgrade agents, select all agents,
click save
save,
No need to upgrade clients seperately, manually
Status of upgrade shown in: mode push report in
upper right corner of same page, F5 to refresh
18
Page A - 9
Master Server Console View

Helps to know how
to consolidate space
and predict storage
outages
19
Backup Console
Status Links
Historical View of
Master Server
Node name, JobID, amount of MB backed up, throughput

20
Page A - 10
NSB R
Reporter
t 4
4.8
8
Modules and Troubleshooting
Reporter Services and Modules overview

There are a total of seven services you should see. Six of
these services reside on the NSB Reporter Server, and the
final one resides on the NSB Reporter Agent.
BEXReporterAgent
Agent-side ONLY, no dependencies in order to run
BEXReporterCollector
Server-side only. Controls servers agent and the
Reporters Collector service, controls communication
between the Reporter server and the Reporter Agents.
Depends on MySQL
BEXReporterEventReceiver
Controls and delegates events and SNMP traps. This
service depends on the Collector and MySQL to run
22
Page A - 11
Reporter Services and Modules overview (contd)

BEXReporterMaintenance
Handles scheduling and policy pushing to agents.
Depends
epe ds o
on tthe
e Event
e t Receiver
ece e a
and
d MySQL
ySQ to be
running in order to run
BEXReporterPoller
Will go through and report from all devices that need to
be polled (SNMP traps only, not http data). Depends on
the MySQL service
BEXReporterWebService
Runs the Tomcat web server. No dependencies. If
M SQL service
MySQL
i iis nott running,
i
llogin
i page will
ill reportt a
Cannot Connect to database error
MySQL
MySQL backend that the NSB Reporter runs on. This
service must be started first
23
Reporter Services and Modules overview (contd)

NSB Reporter is based on 29 modules that work
independently of each other to gather information
about the agents and their sub-agents.
sub agents
The Backup Module (mod.sys.backup.Backup_1.0)
This module is found in the systemic directory. If a
backup sub-agent is enabled, this module will be
turned online, and will be responsible for gathering of
backup data
data.
Note, this does not have to be online server-side in
order for this module to work properly agent-side.
24
Page A - 12
Troubleshooting NSB Reporter - Example 1

Backup device is set up correctly, but still no data
Check the backup log by clicking on the traffic light
icon, and clicking on the backup module. Look for any
obvious errors, such as unknown file (bad pathname to
the backups install path) or invalid password. If this is
the case, go to the monkey wrench ( ) page, check
the path and/or re-enter the password and save the
g
p have been
configuration.
Also,, make sure that backups
running (note: you may have to wait anywhere
between 5 minutes to an hour for data to roll in, it
depends on the size of the environment).
25
Troubleshooting NSB Reporter - Example 2

Web Page does not appear
Make sure you entered in the address correctly (should
be http://<hostname>:9000)
Make sure that the WebService is still running.
If the service starts and immediately stops, the port
(9000) may already be in use. Change the port
number by opening the following file <install
path>\conf\server.xml.
path>\conf\server xml Search for all instances of the
number 9000 and change it to any number you wish.
Restart the server, and then open the page on
http://<hostname>:<new port number>.
26
Page A - 13
Troubleshooting NSB Reporter - Logs

Locations - all logs will be located in the following
locations
Reporter
R
t S
Server <install
i t ll
path>/webapps/BEXReporter/logs
Reporter Agent - They will be in their respective
module folders, either in:
<install path>/systemic
<install path>/administrative
The
Th Kernel
K
l log
l is
i llocated
t d iin <install
i t ll
path>/Kernel.log
27
Troubleshooting NSB Reporter - Logs (contd)

Names
Backup - mod.sys.backup.Backup.log
File Analysis - mod.sys.fa.FileAnalysis.log
Rules - mod.adm.rules.Rules.log
Collector - mod.adm.collect.Collector.log (only on the
Reporter Server)
Poller - Poller.log (only on the Reporter server)
Maintenance - Maintenance.log (only on the Reporter
Server)
Event Receiver - EventReceiver.log (only on the
Reporter Server)
Core/Kernel - Kernel.log
28
Page A - 14
Module Summary
Describe the value of NSB Reporter
Explain the main features of the product.
Install and configure the NSB Reporter Agent on a
Windows Master Server
Read and use the data collected from NSB Reporter
Find the general logs that could give you indications if
an issue comes up
29
Page A - 15
Appendix B - OSVV with NSB
NSB NetApp
N tA
Ad
Advanced
d
Integration
Module Objectives
Understand NetApp OSSV agents in more detail
Install NetApp OSSV agents for clients unsupported by
NSB Advanced Client
Use NetApp OSSV backup and recovery features
Understand the differences between NetApp OSSV
Agents and NSB Advanced Client
Appendix 2 - OSSV with NSB
Page B - 1
NetApp OSSV agent

Complete BLI backup solution can be defined using a
combination of OSSV and ARSV
NetApp provides OSSV agents on most operating
systems that Syncsort does not support
HPUX
AIX
Linux (non-LVM enabled)
Same BLI based scheme backup, but different agent
and restore functionality
Using NetApp OSSV

Syncsort manages the NetApp OSSV (very similar to
Filer-to-Filer SnapVault)
Requires proper licensing from NetApp
SnapVault Secondary License
SnapVault Primary License for Unix / Linux
NSB License for SnapVault Manager (capacity-based)
OSSV agent download available from
http://now.netapp.com (requires login)
Page B - 2
Installation & Configuration

1. Download latest OSSV agent from NetApp site for
your platform
2. Install the agent
Default install locations on Unix & Linux
/usr/snapvault
3. Configure the agent to allow access from the
destination filer
4. Add the server as an NDMP node (set access
method to NDMP)
Installation & Configuration

Access
Method
set to
NDMP
Supply
additional
NDMP
parameters
SnapVault
Primary
license
needed
Page B - 3
OSSV Backup Job Definition

Defined via the Backup > Advanced Recovery
SnapVault Window
Source selection must be made at the volume or qtree
level.
Issues a snapvault start in the background
Limitations:
Note: Node level selection is not available
There is no filtering of partitions. The management
console will also show you partitions that are not
available for BLI.
OSSV Backup Job Definition Screenshot
Partition
level
No filter
ineligible
partitions
Page B - 4
OSSV Backup Job Definition Troubleshooting
Some mount points

may not be eligible
for backup, but will
still be selectable
OSSV Backup Considerations

Syncsort NSB is simply managing the SnapVault relationship
between NetApp OSSV and NetApp secondary.
Job failures performed through NSB will likely be reproducible
through snapvault command line console
Run the SV secondary command:
snapvault start S <source server>:<source partition> /<destination
volume>/<qtree_name>
e.g.
snapvault start S linuxossv:/opt
sv_secondary:/vol/linuxossv/opt_qtree
10
Page B - 5
OSSV Restore
Restore of one object at a time
File
Folder
Partition or volume
Restoring multiple files requires selecting the parent
folder object of that file
Issues a snapvault restore operation in the
background
11
Snapshot Contents
There are differences between NetApp OSSV agent vs.
Syncsort ARSV agent:
Change Journaling
Images stored
Functionality
Advanced Recovery functionality (IA, BMR, IV, FullV) is
only available in NSB Advanced Client.
Application aware agents are only available in NSB
Advanced Client.
By storing the contents as a RAW disk image instead of
copied filesystem, NSB Advanced Client is able to
accomplish Advanced Restore tasks like IA, BMR, and
Virtualization
12
Page B - 6
Snapshot Contents (OSSV vs. ARSV agents)

By storing the contents as a RAW disk image instead of copied filesystem,
NSB agent is able to accomplish Advanced Restore tasks like IA, BMR, and
Virtualization
OSSV
NSB
Copied
Filesystem
Raw disk
image
13
Module Summary
Understand NetApp OSSV agents in more detail
Install NetApp OSSV agents for clients unsupported by
NSB Advanced Client
Use NetApp OSSV backup and recovery features
Understand the differences between NetApp OSSV
Agents and NSB Advanced Client
14
Page B - 7

StudentGuide v1.4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

StudentGuide v1.4

Uploaded by

Copyright:

Available Formats

NSB Installation, Configuration,

Syncsort Global Education Services

NSB Installation, Configuration, and Management

Module 00 - Course Agenda

For use by Syncsort and its Authorized Training Partners only

Syncsort Global Education Services

NSB Installation, Configuration, and Management

Complete the Pre-Assessment

Module 00 - Course Agenda

For use by Syncsort and its Authorized Training Partners only

Syncsort Global Education Services

NSB Installation, Configuration, and Management

Module 00 - Course Agenda

NSB Partner Education Learning Path

Selling the NSB

Sales Discovery and

Pre-Sales SE: Accreditation

Post-Sales SE: Certification

Deliveries available through

(3) 4-Hour Sessions

NSB Installation, Configuration and

For use by Syncsort and its Authorized Training Partners only

Syncsort Global Education Services

NSB Installation, Configuration, and Management

Validate Your Knowledge, Prove Your Skills

Targets Sales and Pre-Sales

Targets Post-Sales and All Technical

Latest on the NSB Solution

Module 00 - Course Agenda

For use by Syncsort and its Authorized Training Partners only

Syncsort Global Education Services

Module 01 - NSB Solution Overview

Discuss the NSB solution

Module 01 - NSB Solution Overview

For use by Syncsort and its Authorized Training Partners only

Syncsort Global Education Services

Module 01 - NSB Solution Overview

The NSB Solution

* Traditionally known as BEX / Backup Express

Module 01 - NSB Solution Overview

For use by Syncsort and its Authorized Training Partners only

Syncsort Global Education Services

Module 01 - NSB Solution Overview

NSB Solution Topology

D2D Backup Target

Any Primary Disk

Target disk and tape,

Module 01 - NSB Solution Overview

Module 01 - NSB Solution Overview

For use by Syncsort and its Authorized Training Partners only

Syncsort Global Education Services

Module 01 - NSB Solution Overview

Module 01 - NSB Solution Overview

One Solution for Multi-Tiered Data Recovery

Module 01 - NSB Solution Overview

For use by Syncsort and its Authorized Training Partners only

Syncsort Global Education Services

Module 01 - NSB Solution Overview

Supported Technologies (contd)

Storage Area Networks

For use by Syncsort and its Authorized Training Partners only

Syncsort Global Education Services

Module 01 - NSB Solution Overview