IBM ProtecTIER Replication Overview

This presentation is stored on IBM Techdocs at the following url:

Nancy Roper http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRSxxxx

IBM Advanced Technical Skills

Run it in screenshow mode to see the animation.
nroper@ca.ibm.com Note that there are a few hidden charts.

2012 IBM Corporation

1
2012 IBM Corporation
 Agenda

Replication Concepts
Setting up Replication
Creating the Replication Grid
Setting up a Many to One Topology
Setting up a Many to Many Topology
Setting up a Replication Policy
Replication Schedule and Rate Limits
Disaster Recovery
Entering DR Mode
Failback and Exiting DR Mode

Note: Run this presentation in screenshow mode since it includes considerable animation

2 2012 IBM Corporation

 TS7650
Replication Concepts

3
2012 IBM Corporation
 Replication with ProtecTIER
ProtecTIER Manager

Backup Server Represented capacity

Primary Site
ProtecTIER
Gateway
TSM
Clients
Physical
capacity

Backup Server

4 2012 IBM Corporation

 Replication with ProtecTIER
ProtecTIER Manager

Backup Represented capacity

Server
Primary Site
ProtecTIER
Gateway
TSM
Clients
Physical
capacity

Backup
Server
TCP/IP Represented capacity
Secondary Site

ProtecTIER Physical
DR Gateway capacity
Backup
Server

5 2012 IBM Corporation

 Replication Benefits

Reduced Tape Handling Reduced Network Bandwidth

Costs since 3rd party
provider no longer required
No need for encryption for
tapes going offsite
costs due to deduplicated data
Faster Recoveries since replicated
tapes are already at the remote
site no need to wait for them to
be recalled

6 2012 IBM Corporation

 Replication Concepts High Level
Local ProtecTIER Replication is done by Volser Remote ProtecTIER

Replication Policy #1
A01 A02 A03 A01 A02 A03

If a volser is not listed in a

B01 B02 B03 replication policy, it doesnt
replicate

Replication Policy #2
C01 C02 C03 C01 C02 C03

Different Replication Policies can be

used for different volser ranges eg
different systems or backups or priorities

BUT duplicate volsers are a problem for backup applications

so ProtecTIER has an elegant solution using
Visibility Switching via The Shelf ..

7 2012 IBM Corporation

 Replication Concepts Visibility Switching and The Shelf
Local ProtecTIER Each ProtecTIER has a shelf where the Remote ProtecTIER
non-active copies of the tape are stored

After Replication, if the

A01 A02 A03 tapes are more likely to be
used at the primary site,
then leave the remote
copies on the remote shelf

B01 B02 B03 If the tapes are

more likely to be
used at the remote
site, then
ProtecTIER can
C01 C02 C03 work with the
backup application
to move them into
the remote library
automatically

Local Shelf Remote Shelf

A01 A02 A03

Tapes can also be moved manually. Its also C01 C02 C03
possible (but unusual) to keep both copies on
their respective shelf, or both in their respective
library

8 2012 IBM Corporation

 Replication Concepts More details
Local ProtecTIER Remote ProtecTIER

Replication Policy #1
A01 A02 A03 A01 A02 A03

B01 B02 B03

C01 C02 C03 Replication Policy #2 C01 C02 C03

Local volumes are Remote volumes are

read/write read only

Replication Parallelism: Network Failures

Up to 32 streams per cartridge Cartridge Replication retries for 7 days
Up to 128 cartridges simultaneously

9 2012 IBM Corporation

 Replication Initial Replication
Local ProtecTIER Remote ProtecTIER
Repository Repository
Initial save has to replicate
ALL data and metadata
(this could be very large)

Subsequent saves only have

to replicate the data that The PT folks have a tool
didnt de-dup called pt_net_perf_util
that checks the network
bandwidth and quality
Physical Replication Bandwidth is limited by:
Capacity of the Ethernet Connections on the ProtecTIER
Size of the customers comms pipe (usually the limiting factor)

10 2012 IBM Corporation

 Replication Populating the Remote ProtecTIER initially

Staged Side by Side Re-Imaged

Implementation This is sometimes used, This option does
but moving a system can not exist
This is the usual method be problematic

E01

Add one new backup each Install the remote system in There is no facility to create
week to allow time for the the local building initially for the remote ProtecTIER
initial backup to replicate better comms bandwidth image from tape

11 2012 IBM Corporation

 Creating the Replication Grid

12
2012 IBM Corporation
 Replication Manager and Grids
Enable the Replication Manager function: TS7650 Hub can TS7620 Hub can
opt/dtc/install/ptconfig -activatePTRepMan have up to 12 spokes have up to 4 spokes

Replication Max 8 hubs (we have 3)

Grid #1 Max 24 repositories (we have 20)
Manager on a
ProtecTIER Node Topology Group
or
(typically a hub) Application Group
Max 1 grid total (a hub and its
spokes)

Max 8 hubs per grid

Replication Grid #1 Max 256 repositories per grid Grid #64
Manager on a
separate server
...
(You need an
RPQ for this)
Max 64 grids

13 2012 IBM Corporation

 Creating the Replication Grid

Note: the screen cams in the

rest of this presentation were
taken from more than one
replication environment so the
ProtecTIER names etc may not
match up from screen to screen

All nodes are capable of being a Replication

Manager. Best practice is to use one of the
hubs as the Replication Manager
Enable the function:
/opt/dtc/install/ptconfig -activatePTRepMan

14 2012 IBM Corporation

 Creating the Replication Grid

Error message likely

means ..
(1) You forgot to do the
Activate Replication
Manager command
(2) The port you asked for
isnt available

/opt/dtc/install/ptconfig -activatePTRepMan

Uses port 6202 and FTP

15 2012 IBM Corporation

 Creating the Replication Grid

Creating the grid is really quick

maybe 30 seconds

16 2012 IBM Corporation

 Creating the Replication Grid

Now try to make another grid ..

If the ProtecTIER Replication Manager is installed on a

ProtecTIER node, it can manage up to one grid with 24
repositories.

If ProtecTIER Replication Manager is installed on a

dedicated server (requires RPQ), it can manage up to 64
grids with 256 repositories in each grid.

17 2012 IBM Corporation

 Creating the Many to One Topology

18
2012 IBM Corporation
 Many-to-One Replication

First well add the repository to the Adding a repository to a grid

Grid, then well add the linkages takes about 5 minutes

19 2012 IBM Corporation

 Many-to-One Replication

Repeat the last

step till all your
repositories are
added to the grid.

20 2012 IBM Corporation

 Many-to-One Replication

Now add the hub /

spoke linkages .

21 2012 IBM Corporation

 Many-to-One Replication

22 2012 IBM Corporation

 Many-to-One Replication

Creating a hub / spoke

relationship takes 10-20
seconds

23 2012 IBM Corporation

 Many-to-One Replication

(the hub on this chart is gray because it is

down for unrelated reasons! This
screen cam was taken after-the-fact)

24 2012 IBM Corporation

 Many-to-One Replication

Click on the various repositories and

their details will show in the panel at
the right hand side

This is an example of a bigger Topology

Legend to explain color coding of topology

25 2012 IBM Corporation
 Creating the Many to Many Topology

26
2012 IBM Corporation
 Many to Many Replication

Well start with a 2-node many-to-many

topology and expand it to 4 nodes

27 2012 IBM Corporation

 Many to Many Replication

Add the 3rd node to the Replication manager

28 2012 IBM Corporation

 Many to Many Replication

Add the 4th node to the Replication manager

29 2012 IBM Corporation

 Many to Many Replication

Next well add the 3rd node to the topology

Add then well repeat and add

the 4th node to the topology

30 2012 IBM Corporation

 Many to Many Replication

31 2012 IBM Corporation

 TS7650
Replication Policy

32
2012 IBM Corporation
 Replication Policies V3.1

If visibility is enabled, then the replicated volumes

can be moved into the remote virtual library
automatically. If it is not enabled, then they will sit
on the remote shelf.

Note: the early charts in this sequence are from one ProtecTIER and
the later charts are from a different ProtecTIER, hence the replication
policy name and cartridge volsers change partway through
33 2012 IBM Corporation
 Replication Policies

Click on each replication policy

and the details about it will show
in the panel at the right

34 2012 IBM Corporation

 Replication Policies

Execute Policy means to run the

replication now even if youre not
in the scheduled timeframe

35 2012 IBM Corporation

 Replication Activities

36 2012 IBM Corporation

 Replication Backlog

37 2012 IBM Corporation

 Replication Activities

38 2012 IBM Corporation

 Replication Backlog

39 2012 IBM Corporation

 Replication Activities

40 2012 IBM Corporation

 Replication Activity - the Shelf

The drop-down box lets you see different

fields regarding the tapes on the shelf

41 2012 IBM Corporation

 Replication Activities

Aborting the Replication Policy stops

the replications that are currently
underway. However, if backups are
running, the policy will restart
To stop the replication policy altogether,
use disable on the drop down

42 2012 IBM Corporation

 TS7650
Replication Schedule

43
2012 IBM Corporation
 Replication Schedule V3.1

Replication can run anytime. If backup is running at the same time,

the replication bandwidth will be constrained

Replication will run in the timeslots shown in color in the chart.

The replication controls in this chart apply to the

entire system, not just this one replication policy

44 2012 IBM Corporation

 Replication Centralized Schedule

45 2012 IBM Corporation

 TS7650
Replication Rate Limits

46
2012 IBM Corporation
 Replication Rate V3.1

47 2012 IBM Corporation

 ProtecTIER
Disaster Recovery

48
2012 IBM Corporation
 ProtecTIER Disaster Recovery

Suppose Dallas has

a site disaster and
needs to failover to
Tucson
Toronto

New York
Dallas

Tucson

49 2012 IBM Corporation

 ProtecTIER DR Mode Sign on to the Tucson ProtecTIER

Disable the Dallas ProtecTIER

50 2012 IBM Corporation

 ProtecTIER DR Mode

51 2012 IBM Corporation

 ProtecTIER DR Mode

The dotted red line indicates that

Dallas is no longer connected

52 2012 IBM Corporation

 Synchronized cartridges

(2) Look at the

ProtecTIER
replicated
cartridges to
(1) Look at your backup make sure
application to see which theyre in sync
cartridges are needed
for restore If theyre not in
sync, youll
have to choose
an earlier
backup

53 2012 IBM Corporation

 Backup Applications Single Domain vs Multiple Domain

Single Domain Backup Application Multiple Domain Backup Application

Knows about cartridges at all sites Only knows about cartridges at one site
Eg NetBackup, Legato, BRMS with NW Eg TSM, BRMS without NW feature, etc
Feature, etc

Backup Application Backup Application Backup Application

Failover / Failback and physical Failover / Failback has an extra

tape cloning are simpler step to load the Backup
because Backup Application at Application database that knows
remote site knows about the about the cartridges at the remote
tapes site

54 2012 IBM Corporation

 ProtecTIER Disaster Recovery

Dallas Tucson

Resolve the Disaster If needed, restore the Backup

Application Database
Restore the systems
Create scratch tapes for day
to day operations
Run Production as usual, with
backups going to the
ProtecTIER
55 2012 IBM Corporation
 ProtecTIER
Failback

56
2012 IBM Corporation
 Disaster / Failback Scenarios

DR Test DR with Primary PT DR with Primary PT

Repository Intact Repository Destroyed
with no Data Written
Spoke Hub Spoke Hub Spoke Hub

A01 A01 A01 A01 A01 A01

A02 A02 A02

E02 E01 E02 E01

Server Server Server

Simple restore test at Hub Restore at Hub Restore at Hub

ProtecTIER
Run there until Spoke Site Run there until Spoke Site
Failover and Failback with is available again is available again
no need to replicate any
cartridges Replicate New Tapes back Much bigger job to rebuild
to Spoke and mark R/W entire repository at Spoke

57 2012 IBM Corporation

 ProtecTIER Failback

When you are ready to

failback to the regular site,
start by moving the cartridges
that you want to replicate
back into the ProtecTIER
export slots

58 2012 IBM Corporation

 ProtecTIER Failback

Create a failback
policy to replicate
all your cartridges
back

Notice that a
failback policy
MUST replicate to
the shelf, not the
VTL

59 2012 IBM Corporation

 ProtecTIER Failback

Watch until all the

failback replication
activities are
complete before
you leave DR
mode and start
using the original
ProtecTIER again

60 2012 IBM Corporation

 ProtecTIER Failback

Exit DR mode and return to regular operations in Dallas

61 2012 IBM Corporation

 Recap

Replication Concepts
Setting up Replication
Creating the Replication Grid
Setting up a Many to One Topology
Setting up a Many to Many Topology
Setting up a Replication Policy
Replication Schedule and Rate Limits
Disaster Recovery
Entering DR Mode
Failback and Exiting DR Mode

62 2012 IBM Corporation

 Session Evaluations
ibmtechu.com/vp

Prizes will be
drawn from
Evals

63 2012 IBM Corporation

 Hindi
Hebrew

Gracias
Simplified
Chinese

Russian

Thank You Obrigado

English
Spanish

Arabic Brazilian Portuguese

Da n k e
Grazie German

M erci
Italian
Korean

French

Japanese
Tamil
Thai
Traditional Chinese

64 2012 IBM Corporation