Replication Manager

SQL Server /


(Chung_YounTae@emc.com)

CLARiX SnapView
SQL Server
Replication Manager SQL Server
/

/


migration
Disaster Restart/Recovery

to map out and coordinate the activities that will be involved

to create, maintain, and change the implementation as the

business needs change

to understand the technologies and the associated business

processes

to create and deploy scripts that automate these activities

Reporting

Reporting

Exchange
EMC RTO

1.8 %

BCV /

ATA

22.2 %

24

108

60 GB

100.0 %

CLARiX SnapView
SQL Server
Replication Manager SQL Server
/

EMC CLARiX /

MirrorView/
Synchronous

SnapView
Point-in-Time Replicas
Snapshots
Full Binary Replicas
BCVs
Instant Recovery

SAN Copy

Inter-Array Data Mobility

Full / Incremental Copy

Synchronous
Remote Replication
Solution for
Disaster Recovery

MirrorView/
Asynchronous

Low-Cost and LongDistance Mirroring

Consistency Groups

SnapView: 2

Full Image Copy

SnapView CLARiX

;

8 each
Full Image
Copy: BCV (Business
Continuance Volume)

:
SnapView

BCV

Clone
Production
Information
Snap

Snapshot

Logical Point-in-Time View

BCVs: Full Image Copies

Establish , BCV

Can be used to restore or replace
source in event of hardware or
software error
/
BCV
8
BCV
RAID

Full Image Copies

BCV
BCV
BCV
BCV
BCV
BCV
BCV
BCV

Clone
Production
Information

BCV
Fracture
log
Sync
incremental
copy / restore




: split

10

0
0
0
0
0

0
0
0
0
0

0
0
0
0
0

0
0
0
0
0

0
0
0
0
0

0
0
0
0
0

0
10 1

0
0
0
0
0

0
0
0
0
0

0
0
0
0

A B
Source

10
0
0
0
0

0
0
0
0

0
0
0
0

Fracture Logs

AB
BCV1

AB
BCV2

A B
BCV3

 : Logical Point-in-Time
Views

Logical Point-in-Time View

LUN 8

BCV
LUN 80
(8x + 8x
(BCV + 8x BCV ))

Snapshot
Snapshot
Snapshot
Snapshot
Snapshot
Snapshot
Snapshot
Snapshot
Snap
Production
Information

SnapView Copy-on-FirstWrite

Block C in the Reserved LUN

now reflects the change that the
production application made and
the pointer is updated to point to
the Reserved LUN for Block C

Source LUN
Block A
Production Host

Block B
Updated
Block C
Block D

0
0
0
0
0

0
0
0
0
0

10
0
0
0
0

0
0
0
0
0

Reserved LUN
Original
Block C

SP Memory
Block A
Block B

Block C
Block D

Secondary Host

CLARiX SnapView
SQL Server

Replication Manager SQL

Server /

The Dependent I/O Concept

write
write

A logical dependency, not a time dependency

DBMS

Dependent Write Consistency

Disk Mirroring Technologies

Database Data Ahead of Log
Problem
HOST
Begin transaction
Begin split of mirrors
Data page to be destaged
Update log
Data page written
Split completes
DBMS Buffer

STD Data Vol.

Mirror

2-DATA

2-DATA

STD Log Vol.

Mirror

DATA

1-LOG

Data
Ahead
of Log

Dependent Write Consistency

EMC Symmetrix Enginuity Consistency Assist

Database Logging Control Functions

restartable/recoverable

SQL Server

Virtual Device Interface VDI

Oracle

Put database in hot backup mode

Take database out of hot backup mode

Sybase

Quiesce hold/quiesce release

DB2

Suspend/resume

SQL Server 2000 Virtual

Device Interface

Microsoft SQL Server

Server-less split-mirror

3rd-party VDI
(e.g., TimeFinder, SnapView)
online
accessible
Meta-data
Checkpoint quiesce

VDI

LUN
LUN
LUN(
)
SNAPSHOT

My_DB

BCV
Other_DB

The Basic Database Cloning

Process
1.

While application is alive; production in process

Set up disk and other resources

2.

Enable database logging control function

3.

Copy the Data using CLARiX technology

4.

Disable database logging control function

5.

Restart the database on another host/storage,

and use the copy of the database

Cloning a Database With

SnapView Snapshots

Secondary host

Production host
2

Enable database logging

control function
SQL Server

SQL Server

Hold I/O or Hot

Backup Mode (in)
Release I/O or Hot
Backup mode (out)
4 Disable database logging
control function

Allocate storage to the

Snap cache & create
the Snapshots

Activate the Snap

sessions

Perform a Host rescan or

reboot the system

Restart the database

Cloning a Database With SnapView

BCVs
2

Production host
3

Establish the mirror

relationship. Wait for
Synchronization.

Secondary host

Enable database logging

control function
SQL Server

SQL Server

Hold I/O or Hot

Backup Mode (in)
Release I/O or Hot
Backup mode (out)

Fracture (split) the

Snapclones

Assign clones to remote

host storage group

Perform a Host rescan or

reboot the system

Restart the database

Create the clone group

5 Disable database logging

control function

LUN

LUN

Dual access to same data

Copy on first write

BCV

LUN

fracture (split)

Mixed disk type performance implications (Fibre & ATA)

CLARiX SnapView
SQL Server

Replication Manager SQL

Server /

Replication Manager

, ,

On-demand

6:00 a.m.

1

12:00 p.m.
2

Warehouse

6:00 p.m.

12:00 a.m.

Mount

Oracle
Exchange
SQL Server
UDB


UFS
VxFS
NTFS
HFS
JFS
VxVM
HP LVM
AIX LVM
Sun LVM
PowerPath Volume
Manager (Solaris)

Microsoft VSS
Symmetrix
TimeFinder/Mirror
TimeFinder/Snap
CLARiX
SnapView Business Continuance Volumes (BCVs)
SnapView snapshots
SAN Copy
HP StorageWorks
Clones

Windows 2000, 2003

Solaris
HP-UX
AIX

Replication Manager
Console

Replication Manager Server

Local Area Network

Replication Manager Clients

LEGATO AAM
MSCS
VCS
HACMP
Sun Cluster
HP/Service Guard

Replication Manager: SQL

Server Agent

SQL
SQL




sysadmin
Username & password


SQL Virtual Device Interface

 Mount

mount
(
)/
/
On-demand mount

Recovery
Database is open Read / Write
Transaction Log file backups
cannot be applied
Any uncommitted transactions are
rolled back
No Recovery
Database is unusable in an
intermediate, non-recovered state
Uncommitted transactions are not
rolled back
Useful for running a script to apply
several transaction log file backups
to recover database to a specific
point in time
Standby
Database is opened Read Only
Transaction log file backups can be
applied
File Systems Mount Only
Only the file systems are mounted

Replication Manager: SQL

4
Recovery
No Recovery
Standby
File Systems
No Recovery

Replication Manager Value

Proposition

, ,