Replication Manager Foundations

Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved.
Introduction to Business Continuity
© 2006 EMC Corporation. All rights reserved.
Welcome to Introduction to Business Continuity. This section introduces Business Continuity

Solutions. It starts with a basic definition, then shows the business requirements for Business
Continuity, followed by the history of Data Protection as a key component to Business Continuity.
The AUDIO portion of this course is supplemental to the material and is not a replacement for the
student notes accompanying this course.
Replication Manager Foundations - 1

Course Objectives
Upon completion of this course, you will be able to:
y Explain the concept of Business Continuity
y List the benefits of Business Continuity regarding
expenses incurred as a result of downtime
y Explain how EMC uses Local and Remote mirroring in its
storage methodologies to maintain data protection
© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 2
The objectives for this course are shown here. Please take a moment to read them.

What is Business Continuity

y Business Continuity is the preparation for, response to,
and recovery from an application outage that adversely
affects business operations
y Business Continuity Solutions addresses systems
unavailability, degraded application performance, or
unacceptable recovery strategies
Business Continuity remains at the top of every executive’s priority list. Yet executives find
themselves in a financial tug-of-war between business continuity solutions and other projects,
competing for limited resources. Fundamental to business continuity is the need to understand an
organization’s practices relative to the protection, availability and usability of data.

Why Business Continuity

Lost Productivity Know the downtime costs per Lost Revenue
• Number of employees hour, day, two days... • Direct loss
impacted * hours out * • Compensatory payments
hourly rate • Lost future revenue
• Billing losses
• Investment losses
Damaged Reputation Financial Performance
• Customers • Revenue recognition

• Suppliers • Cash flow
• Financial markets • Lost discounts (A/P)
• Banks • Payment guarantees
• Business partners • Credit rating
• Stock price
Other Expenses
Temporary employees, equipment rental, overtime
costs, extra shipping costs, travel expenses...
There are many factors that need to be considered when calculating the cost of downtime. A
formula to calculate the costs of the outage should capture both the cost of lost productivity of
employees and the cost of lost income from missed sales.
The Estimated average cost of 1 hour of downtime = (Employee costs per hour) *( Number of
employees affected by outage) + (Average Income per hour).
Employee costs per hour is simply the total salaries and benefits of all employees per week,
divided by the average number of working hours per week.
Average income per hour is just the total income of an institution per week, divided by average
number of hours per week that an institution is open for business.

Business Continuity – Obstacles of Availability
Disaster (<1% of Occurrences)

Natural or man made
Flood, fire, earthquake
Contaminated building
Unplanned Occurrences (13% of

Occurrences)
Failure
Database corruption
Component failure
Human error
Planned Occurrences (87% of Occurrences)

Competing workloads
Backup, reporting
Data warehouse extracts
Application and data restore
Source: Gartner, Inc.

Elevated demand for increased application availability confirms the need to ensure business
continuity practices are consistent with business needs.
Interruptions are classified as either planned or unplanned. Failure to address these specific outage
categories seriously compromises a company’s ability to meet business goals.

Cost of Downtime Per Hour By Industry
Investments
Manufacturing
Telecom
Banking
Transportation
Retail
Insurance
$0 $100,000 $200,000 $300,000 $400,000
Source: AMR Research
The selection of a business continuance solution includes many factors, but the most important
factor is typically the cost to invest in the solution. This cost can encompass hardware, software,
floor space, people, time, etc.
To put into perspective the cost to invest in a business continuance solution, it is important to
understand the loss of revenue for downtime. AMR Research put together a chart based on
category of industry (see slide) to demonstrate the dollars of revenue lost per hour of system
downtime. A business continuance solution is an insurance policy for the protection of your data.
Is losing or compromising the integrity of your company’s critical information a risk you are
willing to take?
EMC’s Technology Solutions (TS) organization is made up of experts who understand 24x7x365
continuous availability, and the use of EMC systems and software to achieve it. They address
information storage needs from a strategic perspective, and focus on the business requirements and
the application of storage technology to address those requirements. EMC’s consultants use a
framework of proven processes and industry-leading best practices and methodologies. This
framework addresses all phases of an enterprise solution, and ensures a consistent and effective
process for creating an information-centric infrastructure.

Business Continuity Starts with Data Protection

y Local Mirroring is a method for protecting data by
maintaining the data on two mirrored volumes within the
same storage unit
y Remote Mirroring is a method for protecting data by
maintaining the data on two mirrored volumes, with the
volumes residing in different storage units
Without the Data there is no Recovery!
The technique that EMC has embraced for data protection is to use multiple copies of data. This is
not a new idea. What EMC has brought to the table is new and unique, intelligent storage
methodologies that can: replicate data locally within storage arrays, or across distances between
storage arrays; facilitate and enable parallel access to data instances; allow users to perform
various workloads without conflict; and change the time, effort, risk, and complexity of remote
business resumption dramatically.

Data Protection with Disk Mirroring
Standard Disk
Mirrored Disk
1991
Remote Mirror
1994
Before Mirroring, the entire drive would be allocated for data and, used by the operating system or
application, and be unprotected in the event of a failure.
Disk Mirroring introduced a technique in which data is simultaneously written to duplicate disks.
If one of the disks fails, the system or application can continue without any loss of data or
disruption in service.
First introduced by EMC, Remote Mirroring extended the Data Protection across Storage
Subsystems protecting against a drive and subsystem failure. If a drive failed, access was only
available on the secondary storage subsystem.

Multiple Mirrors - Multiple Uses

1995
1995 High
High Availability
Availability Disaster
Disaster
Dual
Dual Remote
Remote Restart
Restart
Mirrors
Mirrors
Storage Array A Storage Array B
Application
Application Backups
Backups
1997
1997 Application
Application Development
Development
Dynamic
Dynamic Disk
Disk Data
Data Warehouse
Warehouse Extract
Extract
Point-
Point-in-
in-Time Recovery
Recovery Testing
Testing
Mirrors
Mirrors copy
2001
2001
Enterprise
Enterprise Database
Database Integrity
Integrity
Reporting
Reporting
Consistency
Consistency Quality
Quality Assurance
Assurance
Point-
Point-in -Time Point-
Point-in-
in-Time Data
Technology
Technology Data Warehouse
Warehouse Load
Load
copy copy
2004
2004
Database
Database Integrity
Integrity
Asynchronous
Asynchronous Extended
Extended Distance
Distance
Remote
Remote Changes Consistent Optimized
Optimized Bandwidth
Bandwidth
Image
Replication
Replication
Dual Remote Mirroring offered local protection, as well as the extended protection across storage
subsystems. This offered local protection against a drive failure, so access to data was not required
to span the secondary storage subsystem.
Dynamic Disk Mirroring introduced a technique in which a special disk device is dynamically
mirrored to a mirrored disk pair and split for business operations.
Enterprise Consistency Groups introduced the ability to have a restartable point of consistency
image across platforms.
Asynchronous Remote Replication introduced a method of ensuring a consistent, recoverable, and
restartable remote copy of production data at all times, over extended distances, with no host
application impact.

Business Continuity Objectives

Drivers Objectives
Downtime is expensive: an average company
incurs more than $1 million of revenue loss Continuous availability
per hour of downtime
(Source: Meta Group)
Documented business continuity

Expanded regulatory requirements processes, controls, and test
(SOX, HIPAA, SEC, etc.) results required for defined
records
Global business processes 24-hour application-availability

(Supply Chain, Customer Service, etc.) expectations
Application consolidations: 75% of downtime Increased business impact of

occurrences are caused by poor technology application outage driving
in the network and application infrastructure increased availability
(Source: IDC)
expectations
Direct customer and partner

Web-enabled applications
impact driving increased
(customer and supply-chain interfaces)
availability expectations
Strong recovery programs must be built upon careful analysis of business processes and all
supporting components, from the hardware, software, network, data center, and other facilities that
comprise the IT environment.
Organizations must first establish a comprehensive Business Continuity Plan, which supports the
Business Continuity Objectives. The plan should address the issues customers are facing, some of
which are increasing regulatory pressure for improved Business Continuity capabilities required
by standards and government organizations; understanding complexity of application
interdependencies and determining information flows; leveraging new technologies that promise
higher levels of protection; and maintaining the plan to accommodate changes in IT infrastructure
and new business requirements.

Meeting our Objectives with

Business Continuity Solutions
PowerPath
Legato AAM
Legato Legato CoStandby SRDF Family
Server AAdvanced MirrorView
NetWorker
Celerra Replicator
Legato RepliStor
TimeFinder Family
SnapView Multi-site
Remote
Celerra SnapSure Processing Increasing
Remote distance
Backup Recovery Information Automatic improves
All critical data processing protection
Quick, accurate, resumption:
Platform Frequent, predictable safe at remote
consistent, location “lights out”
Storage, switch, recovery
and server nondisruptive
protection backups
Local Remote
Time y Availability y Distance

No matter what level of availability a business demands, EMC can help meet that demand with a
range of solutions. EMC’s wide range of solutions allow you to align the technology to business
needs, as follows. Platform solutions ensure that repairs can be made with minimal disruption to
the business. Backup/recovery solutions offer streamlined backup processes and technologies
mapped to business needs, including Legato NetWorker, backup to disk, CLARiiON Disk Library,
ADIC, other tape solutions, assessments, and data classifications. Remote information solutions
allow replication of critical data to secondary sites. Remote protection solutions enable nearly
instant restart capabilities, even if a site is lost. Multi-site processing solutions provide not only
instant restart capability, but continuous mirroring at multiple locations (for three or more sites at
longer distances).

Business Continuity is a Core EMC Competency

y In-depth knowledge and experience
– Information management
– Mission critical environments
– BC planning and technology
y Disciplined and proven methodology

y Ability to provide objective site & platform roadmaps and
recommendations
y Commitment to customer satisfaction
y Strategic alliances and partnerships
EMC has been, and is, the recognized industry leader providing the highest level of recovery
capabilities and business continuance solutions in the world today.

Course Summary
Key points covered in this course:
y The concept of Business Continuity
y Benefits of Business Continuity regarding expenses
incurred as a result of downtime
y How EMC uses Local and Remote mirroring in its storage
methodologies to maintain data protection
These are the key points covered in this training. Please take a moment to review them.

Replication Manager Foundations
© 2006 EMC Corporation. All rights reserved.
Welcome to Replication Manager Foundations.

The AUDIO portion of this course is supplemental to the material and is not a replacement for the
student notes accompanying this course. EMC recommends downloading the Student Resource
Guide from the Supporting Materials tab, and reading the notes in their entirety.
These materials may not be copied without EMC's written consent.
EMC believes the information in this publication is accurate as of its publication date. The
information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC
CORPORATION 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.
Use, copying, and distribution of any EMC software described in this publication requires an
applicable software license.
EMC is a registered trademark, and SRDF, and TimeFinder are trademarks of EMC Corporation.
All other trademarks used herein are the property of their respective owners

Replication Manager Foundations

Upon completion of this module, the student will be able to:
y List EMC’s Replication Manager family of products
y Describe Replication Manager’s functionality for both
Replication Manager and Replication Manager SE
y Describe Replication Manager’s architecture for both
Replication Manager and Replication Manager SE
y List the applications supported by Replication Manager
as per the support matrix
y Describe Replication Manager product family’s benefits
The objectives for this course are shown here. Please take a moment to read them.

What is the Replication Manager Family

y Simplifies and automates the creation, management, and
usage of disk-based replications
y Covers from entry-level to enterprise
y Supports the needs of both storage savvy personnel and
storage novices
y A complete “grow-as-you-go” product portfolio
The Replication Manager family is a portfolio of replication management products designed to

manage EMC’s various replication products, whether they are local or remote replicas.
They all dramatically simplify the usage and management of disk-based replicas. The products
range from mid-tier entry-level products to full enterprise-class. There are products for those with
sophisticated storage expertise, and products for those who are application focused rather than
storage experts.
Perhaps one of the most useful features is that the products are part of a family that can “grow as
you go”, with upgrade paths and licensing.

Why Replication Manager

y Data loss has business impact
– Employee productivity
– Revenue loss
– Damage to business reputation
y Data corruption and loss are at best unpredictable

y EMC Software solutions (Replication Manager) minimize
impact
– Fine RPOs
– Short RTOs
Replication Manager addresses the issues facing business today by readying them for potential
data loss, whether it be in the form of data corruption or physical failure of hardware. These types
of disasters can have a devastating impact on the day-to-day operations of a business as data
loss/corruption at a minimum, will slow down processes which results in a loss of revenue.
To counter these types of extended outages, Replication Manager allows you to create multiple
replicas throughout the business day with minimal, if any, impact on the production environment.
This results in the ability to finely tune the Recovery Point Objectives in stated service level
agreements. Couple that with the ability to instantly restore data from disk-based replicas, and you
achieve much better Recovery Time Objectives than legacy solutions could ever offer.
These advantages can be realized in both the enterprise arena with Replication Manager, as well as
in the Small-to-Medium/Commercial space through the use of Replication Manager SE, both of
which we will discuss in this module.

Replication Manager Family Portfolio

y Replication Manager/SE creates
local Exchange, SQL Server, and
filesystem replications on a
CLARiiON
y Replication Manager/ Remote
creates remote Symmetrix Replication Replication
replications for disaster restart Manager/SE Manager/Local
y Replication Manager/Local
manages local (within an array)
application-focused replications
for repurposing and rapid
recovery
EMC Replication Manager creates replicas of mission-critical information on disk arrays. The
product can create a replica on BCVs and VDEVs (in Symmetrix storage arrays), or LUNs and
snapshots (in CLARiiON storage arrays). Replication Manager creates replicas simply, quickly,
and automatically. In fact, it can automate all the important procedures related to data replication.
The Replication Manager family is made of two products:
y Replication Manager/SE for CLARiiON, Windows, and SQL/Exchange customers in the
commercial space
y Replication Manager/Local covers the Replication Manager/SE features plus UNIX,
Symmetrix, Oracle, and UDB
Note: Both Replication Manager/SE and Replication Manager/Local are application integrated
products.

Replication Manager/SE
y A simplified version of Replication Manager / Local focused on the
mid-tier supporting:
– CLARiiON only
¾ CX300, CX400, CX500, CX600, CX700
– Replication Manager SE for Celerra — Creates replicas of data on Celerra
storage arrays using a Windows-based solution similar to the CLARiiON
solution.
y Allows application-focused administrators to create, manage, and
restore replications of:
– Microsoft SQL Server databases
– Microsoft Exchange databases
– NTFS volumes
y Replication Manager/SE automatically controls the complexities
associated with creating, mounting, restoring, and expiring data
replicas.
Replication Manager/SE is a commercial version of the Replication Manager/Local product.

Replication Manager/SE makes it easy to create point-in-time, disk-based replicas of databases, or file systems,
residing on existing storage arrays.
RM/SE can create replicas of information stored on EMC CLARiiON storage arrays in the following environments:
y Microsoft SQL Server databases
y Microsoft Exchange databases
y NTFS volumes
With RM/SE, it is possible to:
y Create point-in-time replicas of production data in seconds
y Replicas can exist on the same array as the production data, or on a remote array using SAN Copy
y Facilitate quick, frequent, and non-disruptive backups from replicas
y Mount replicas to alternate hosts to facilitate offline processing (for example, decision-support services, integrity
checking, and offline reporting)
y Mount multiple replicas on the same mount host
y Restore deleted or damaged information quickly and easily from a disk replica
y Set the maximum number of replicas for replication jobs so that replication storage is made available
automatically
RM/SE automatically controls the complexities associated with creating, mounting, restoring, and expiring data
replicas. The RM/SE Explorer offers an easy-to-use interface to help the customer manage and control these replicas.

Replication Manager/Local
y Replication Manager/Local discovers, automates, and manages
local application-focused replications for repurposing and rapid
recovery
y Replication Manager can create replicas of information stored in the
following environments:
– Oracle databases
– UDB databases
– Microsoft SQL Server databases
– Microsoft Exchange databases
– UNIX file systems
– Windows NTFS
y Replication Manager can connect to storage arrays, such as:

– EMC Symmetrix arrays
– EMC CLARiiON arrays
Replication Manager/Local covers all the Replication Manager/SE features, plus support on Symmetrix with
TimeFinder family, UNIX platforms, and the Oracle and UDB applications.
Replication Manager/Local provides a single management point for multiple hosts being managed and is better suited
to more complex uses, such as repurposing.
EMC Replication Manager makes it easy to create point-in-time replicas of databases and/or file systems residing on
existing storage arrays. Replicas can be stored on Symmetrix BCVs, Symmetrix VDEVs, CLARiiON Clones, or
CLARiiON Snaps.
Replication Manager can also use SAN Copy to create replicas on a separate CLARiiON storage array.
Replication Manager can create replicas of information stored in the following environments:
y Oracle databases UDB databases
y Microsoft SQL Server databases Microsoft Exchange databases
y UNIX file systems Windows NTFS
The software has a client/server architecture. With Replication Manager, it is possible to:
y Create point-in-time replicas of production data in minutes
y Facilitate quick, frequent, and nondestructive backups from replicas
y Set the retention period or the maximum number of rotations for replicas to tell Replication Manager how to
determine when a replica should be expired
Replication Manager has a generic storage technology interface that allows it to connect to storage arrays, such as
EMC Symmetrix arrays and EMC CLARiiON arrays.

Replication Manager Family Masks the Complexity

Replication Manager Family
Applications: Provides:
Aware of information residing on replications
Hosts Operating System: y Discovery of hosts,
automatic applications, and storage
Filesystems: y Mount and unmount replicas
Faster access to information
to one or more hosts
Host I/O:
Association automatic y Navigation between storage,
host, and application
Drivers:
Masked from user process y Automation of the entire
Primary Disk Volumes: process and integration of
Simplifies discovery and grouping pre- and post-processes
Replication Disk Volumes: y Catalog information
Simplifies discovery and association
y Built-in scheduler
The software has a client/server architecture. With Replication Manager it is possible to:
y Create point-in-time replicas of production data in minutes
y Facilitate quick, frequent, and nondestructive backups from replicas
y Set the retention period or the maximum number of rotations for replicas to tell Replication Manager how to
determine when a replica should be expired
Replication Manager has a generic storage technology interface that allows it to connect to storage arrays, such as:
y EMC Symmetrix arrays
y EMC CLARiiON arrays
Replication Manager Family makes replication and recovery very simple. That simplicity comes from a top-down
implementation where the Replication Manager family can do a variety of things, such as discover, associate,
navigate, automate, catalog, and schedule all replication tasks. Working from the application all the way through the
volumes that are replicated, Replication Manager family simplifies this process with a wizard-driven interface.
The next slides will illustrate the following features from Replication Manager family, as well as its benefits:
y Automated Discovery
y Restore Replicas
y Process Automation
y Integrated Support

Automated Discovery
Replication Manager Family automates the
Discovery
discovery process for:
y Hosts in the environment
y Type of operating system on each host
y Filesystems on each host
y Database(s) on each server
y Storage arrays that are available
y Available storage in each array
The automation behind the Replication Manager family is where the real value of this product is.
Auto-discovery of hosts, filesystems, operating systems, databases, and storage add to the value
Replication Manager provides. All replication processes are automated to allow for the scheduling
of events, including mounting replicas to alternate hosts, recovering from replicas, expiring
replicas, and initiating external backups.
The Replication Manager Family offers application transparency to hide the underlying
complexities associated with replicating complex databases. It insulates the user from needing to
know the inner workings of the database being replicated, and even how the underlying replication
technology is being deployed.
Dynamic Volume Mounting enables the mounting of replicas to alternate hosts automatically
based on replication policies set by the user. It provides operating system, filesystem, and database
awareness. Some benefits from automated discovery are the reduced complexity required to set up
and use replication, elimination of errors inherent in manual processes, and cataloging of all
information and changes when they occur.

Restore Replicas
y Restore replica back to production
– Disk to disk eliminates tape Restore in Minutes
– Restore the entire replica or
restore part of a replica such as:
¾ A single tablespace
¾ A single Exchange database
y Once a replica has been restored, the

Replication Manager agent can restart the
application using different methods
– Full Recovery, No Recovery, Standby Mode
y Test recovery on another server before
impacting production
One major feature of the Replication Manager family is its ability to facilitate a finer level of
granularity with restore. Now, users can browse a catalog of filesystems, databases, and
tablespaces for which they have replicas. The result is the ability to perform an instant restore
without the need to go to tape. This can eliminate hours in the recovery process and, depending on
the scenario, may allow the application to be restarted in minutes. This results in improved
recovery times, reduced effort, and improved data management.

Process Automation
Set up and execute your processes to best fit
your needs: Automated
y Schedule events
y Kick-off events through the GUI
y Integrate pre- and post-processes
y Mount to other RM clients
y Set expiration period for replicas
y Backup to tape
y Initiate recovery manually when needed
The automation of replication activities leverages the automated discovery capabilities of

Replication Manager family.
Process automation steps through whatever process is required to manage the replicas to meet the
business needs. Some benefits from process automation are improved IT scalability, decreased
manual errors, and the enabling of knowledgeable staff to focus on improving business processes
(NOT day-to-day movement of data).

Integrated Support Within the Replication Manager

Family
Applications Replication Technology
y Oracle y Microsoft VSS Integrated
y Exchange y Symmetrix
y SQL Server – TimeFinder/Mirror
– TimeFinder/Snap
y UDB
– SRDF/Synchronous
Filesystems and – SRDF/Asynchronous
Volume Managers – ECA (consistency)
y UFS y CLARiiON
– SnapView clones
y VxFS Clusters
– SnapView snapshots
y NTFS – SAN Copy y LEGATO AAM
y HFS y HP StorageWorks Clones y MSCS
y JFS y VCS
Operating Systems
y VxVM y HACMP
y Windows 2000, 2003
y HP LVM y Sun Cluster
y Solaris
y AIX LVM y HP-UX y HP Service Guard
y Sun LVM y AIX
y Linux
There is a wide variety of support required to enable a product to manage replicas in a

heterogeneous environment. This slide shows a list of the major components that are supported.

Why Customers use Replication Manager

y Console based management and control
– Transparent operations
– Logical view of production data and replicas
y Point-in-time, non-disruptive replicas

– Simultaneous with production
– No down time
y Alternate host format for offline processing

y Simplified recovery processing
y Interface independent of individual storage technology
y Multiple disk array capability
The Replication Manager family automates, simplifies, and manages disk-based replications. The
application provides a layer of transparency to underlying complexity. It insulates the user from the storage
environment, replication software being used, the type of server, the operating system, disk volumes, etc.
For the short-term, Replication Manager can be thought of as “media management for disk-based replicas”
and more. Replication Manager helps customers manage replicas as if they were tape cartridges in a tape
library unit. Replicas may be scheduled or created on demand, with predefined expiration periods and
automatic mounting to alternate hosts for backups or scripted processing. Individual user logins, with levels
of access security, ensure system and replica integrity.
In addition to these features, Replication Manager is designed to be much more. It is fully integrated with
many critical applications such as Oracle, Microsoft Exchange, etc.
With Replication Manager you can:
y Create point-in-time replicas of production data in seconds
y Facilitate quick, frequent, and non-disruptive backups from replicas
y Mount replicas to alternate hosts to facilitate offline processing (for example; decision-support services,
integrity checking, and offline reporting)
y Set the retention period for replicas to automatically free storage
Replication Manager automatically controls the complexities associated with:
y Creating and expiring storage mirrors
y Managing available storage in pools
y Mounting mirrors to alternate hosts

Lesson 2 – Replication Manager Architecture

Upon completion of this lesson, you will be able to:
y Discuss the Replication Manager Architecture
Components:
– Console
– Server Software
– Client Software
y Review the Component Communication Flow

– IRD
– IRCCD
The objectives for this lesson are shown here. Please take a moment to read them.

Architecture
y Replication Manager
architecture includes
the following three
components:
– Console
– Replication Manager
Server
– Replication Agents
Replication Manager architecture includes the following three components:

y Console
y Replication Manager Server
y Application Clients (also known as Replication Agents)
Because Replication Manager uses specialized agent software to communicate with the database
or file system that is being replicated, this architecture allows Replication Manager to easily
support additional databases and file systems as they become available.

Replication Manager Components

y Console
– Java based
y Server Software
– Replication Manager Daemon Console
(IRD)
– Policy Engine
– Replication Manager Database Server
y Client Software Software
– Client Control Daemon (IRCCD)
– Storage Services
Client
– Modular Agents
Software
The Console is the user interface for Replication Manager. It is a Java-based application that
allows you to access and control your storage resources; create, mount, and expire replicas; and
manage schedules locally or remotely. This component controls the Replication Manager system
from any Windows, Solaris, HP-UX, or IBM AIX desktop machine or server. The EMC
ControlCenter equivalent to the Replication Manager Console is called the user “Interface Tier”.
The Replication Manager Server processes all user requests and keeps track of all Replication
Manager-managed replicas in the embedded repository. There is no direct communication between
a Replication Manager Console and an application client. This component consists of core
software binaries, log files, and an embedded data repository containing configuration data that
describes each replica created and the storage associated with that replica. The server component
resides on the replication server host. The ControlCenter equivalent to the Replication Manager
server is called the “Infrastructure Tier”.

Console
Windows Replication Manager Server

Console
LAN
LAN
Repository
Unix
SAN
SAN
Application Clients
The Application Clients are agents that manage specific objects such as databases and file systems.
The Replication Manager client software links to the storage array and manages that connection,
including the communication with it.
Replication Manager Architecture allows users to access the software from anywhere on the
network. The Replication Manager Console lets the customer control Replication Manager from
any Windows NT/2000/XP or UNIX workstation that has the console installed and has a TCP/IP
connection to the server and the hosts.
Storage Policy Plug-ins select the best mirrors for replicating a set of sources, while Storage
Service Plug-ins access arrays to identify and manipulate the storage.

Server Software
y The Replication Manager
Daemon or Service (IRD) controls
and coordinates replication and Replication
ReplicationManager
Manager
Daemon
Daemonor orService
Service
recovery activity for all the (IRD)
(IRD)
storage corresponding to its
registered clients and their
InfoSets
y The Policy Engine links Policy
PolicyEngine
Engine
Replication Manager with the
supported storage arrays Split
SplitMirror
Mirror
Technology
Technology Replication
Replication
y The Replication Manager such
suchas
as Manager
Manager
Timefinder,
Timefinder, Database
Database
Database is an embedded data Snapview (SOLID)
Snapview (SOLID)
repository that stores data about and
and
InfoSets, activities, and replicas HP
HPClones
Clones
The server software is installed on the server that controls replication activities and stores data
about each replica. The server software has three distinct components:
y Replication Manager Daemon controls and coordinates replication, expire, mount, and
recovery activity for all the storage corresponding to its registered clients and their InfoSets.
The Replication Manager Daemon handles all requests from the Console. The server verifies
the authentication of users logging in to the Replication Manager system, both from the
Console and the CLI.
y The Policy Engine links Replication Manager with the supported storage array technologies.
The policy engine is a dynamic library that links to the Replication Manager Daemon. The
policy engine is Storage Policy and works with the Storage Service on the client to determine
which mirror volumes to use for a replication. The Storage Policy plug-in uses an algorithm to
choose the best device, whether it is a clone or BCV, to use for the replication. The algorithm
attempts to maximize performance by choosing mirrors based on their position on the disk
adapters and whether they have been previously used in a cloning operation. The latter
situation marks the device as a candidate for incremental synchronization.
y The Replication Manager Database is an embedded Database that stores data about InfoSets,
activities, and replicas. The IRD daemon is responsible for maintaining the Database. The
Database holds information about replicas, activities, users, clients, etc., that Replication
Manager needs to run the application and maintain its existing state.

Client Software
y The Client Control Daemon or
Service (IRCCD) is the client
software’s central processing
module Client
ClientControl
Control
Daemon
Daemon(IRCCD)
(IRCCD)
y Storage Services software
manages the storage
relationships between the client
and the storage array where the
replica resides
Storage
StorageServices
Services
y Application Agents for each Symmetrix
supported information interface. Symmetrix
Data
DataBase
Base
Each agent is a separate Management
Management
executable, dynamically linked CLARiiON
CLARiiON File
FileSystems
Systems
and loaded with the Replication Agents
Agents
Manager at runtime (DBMS/FS)
(DBMS/FS)
StorageWorks
StorageWorks
The client software is installed on each host that participates in the replication process, including
hosts that manage production data and hosts that are used to mount replicas. The client software
also has three distinct components:
y Client Control Daemon (IRCCD) is the client software’s central processing module. It listens
for incoming connections from the Replication Manager Daemon and then handles and
coordinates all operations on the client.
y Storage Services software manages the storage relationships between the client and the storage
technologies used to create the replicas.
y Modular Agents for each supported information interface. Each agent is a separate executable,
dynamically linked and loaded with the replication daemon at run time. The agents provide the
intelligence to support the application or filesystem that will be replicated. Supported agents
are:
− Oracle
− SQL
− Exchange
− UDB
− NTFS
− Unix

Component Communication Flow

Console Application Server Application Client
(IRD) (IRCCD)
Replication
Replication Client
Manager Client
Manager Control
Control
daemon
daemon
(IRD)
(IRD)
Storage
Storage
Services
Services
Replication
Replication
Manager
Manager
Application
Application Replication
Replication
Console
Console Manager
Manager
Database
Database
(SOLID)
(SOLID) DBMS/FS/Agent
DBMS/FS/Agent
CLI
CLI Replication
Replication
Manager
Manager
Policy
Policy SYMAPI
SYMAPI
Engine
Engine
Steps that occur when a user requests a replica of an application:

1. IRD reads application information stored during ApplicationSet and activity creation from
SOLID.
2. IRD initiates a connection to the IRCCD on the appropriate client from the information
retrieved in step 1.
3. IRD passes this information on a start message to IRCCD with the application information.
4. The IRCCD loads the appropriate application agent plug in.
5. The IRCCD calls the agent plug in to do a discover called “getBrowseTree”. The browse
tree is a tree representing the application down to the file or raw device level. This
information is returned to the IRD.
6. For each file or raw device, the IRD calls the client to do a storage discover.
7. The client queries the storage agents in a round robin fashion until it finds one that can
resolve the storage. The details are sent back to the server.
8. The storage information is sent to the storage policy agent which selects an appropriate
technology based on the details and the pool selection.

Component Communication Flow

Console Application Server Application Client
(IRD) (IRCCD)
Replication
Replication Client
Manager Client
Manager Control
Control
daemon
daemon
(IRD)
(IRD)
Storage
Storage
Services
Services
Replication
Replication
Manager
Manager
Application
Application Replication
Replication
Console
Console Manager
Manager
Database
Database
(SOLID)
(SOLID) DBMS/FS/Agent
DBMS/FS/Agent
CLI
CLI Replication
Replication
Manager
Manager
Policy
Policy SYMAPI
SYMAPI
Engine
Engine
The Replication Manager client sends a prepare checkpoint command to the storage service agent,
which then issues the appropriate SYMAPI calls to establish the standard(s) and BCV(s). When
there are no more invalid tracks, the application agent will send a freeze request to the application
or, in the case of a filesystem, continue with the split. The storage agent is responsible for sending
the appropriate SYMAPI commands to split the standards from the BCVs. When the split is
complete, the application agent will send a thaw request to the application. Status updates are sent
from the Replication Manager client to the Replication Manager server, which forwards the
information to the Replication Manager Console.
The Replication Manager server receives notification that the replica has been successfully
completed and updates the SOLID Database with information about the replica.
The Replication Manager server passes the list of Symmetrix devices on to the Multi-BCV
Replication policy engine, which selects the BCV storage from the list of usable storage. The
multi-BCV replication policy engine uses built in pairing algorithms to pick the requisite number
of BCV volumes from the storage pool assigned to the activity. The Replication Manager server
updates the Solid database and communicates progress information to the Replication Manager
GUI application which updates the replica status window in the Console. The Replication
Manager server sends an execute replica command to the Replication Manager client on the
production host.

Storage-Array Requirements
y Symmetrix Software Requirements:
– Microcode releases 5x66, 67, 69, and 70
y CLARiiON arrays supported:

– FC4700
– CX300
– CX400
– CX500
– CX600
– CX700
y To SAN Copy is need CLARiiON CX400 or above
y CLARiiON FLARE Releases 13 and 14 (Release 12

requires an RPQ)
Symmetrix
Replication Manager/Local supports the Symmetrix storage array and supported TimeFinder
replication technology. Replication Manager/Local supports TimeFinder/Mirror, TF/Snap, and
Enginuity Consistency Assist (ECA), so Enginuity Version 5x66 is the earliest supported version
of microcode.
Symmetrix Software Requirements - Replication Manager/Local supports microcode releases
5x66, 67, 68, 69, and 70.
CLARiiON
Replication Manager/Local supports CLARiiON storage arrays and SnapView, both BCVs and
snapshots. SAN Copy from a CLARiiON array to a CLARiiON array is supported. Note that in a
SAN Copy environment, at least one of the CLARiiON arrays must be a CX 400 or above.
Replication Manager/Local version 2.2 supports CLARiiON FLARE Releases 13 and 14 (Release
12 requires an RPQ).
Note: FLARE Releases 13 and 14 require some prerequisite firmware installed on the array (for
additional information, refer to the Replication Manager Matrix).
Replication Manager/local supports HPQ StorageWorks (for additional information, refer to the
Replication Manager Matrix).

Host Considerations – Client to use CLARiiON

y Install the following software on each Replication
Manager client:
– EMC Solutions Enabler (multithreaded)
– EMC CLARiiON Navisphere Agent
– EMC NaviCLI including Navisphere Classic and Navisphere Java
– EMC ADMSnap
y Modify the clarcnfg file

found in the:
– /var/symapi/config directory
(UNIX)
– C:\Program
Files\EMC\symapi\config\dire
ctory (Windows)
The RM user must install the following software on each client machine used for Replication
Manager, and configure the system to recognize the CLARiiON storage arrays.
y EMC Solutions Enabler 5.5 or greater
y EMC CLARiiON Navisphere Agent
y EMC NaviCLI including Navisphere Classic and Navisphere Java
y EMC ADMSnap
Also, when using CLARiiON storage, you must update the CLARiiON configuration file. This file
can be found in the /var/symapi/config directory (for UNIX) or C:\Program
Files\EMC\symapi\config\directory (for Windows).
The file should contain the serial number and the IP address or network name of each storage
processor (A and B) in three space-separated columns in the file. Make one entry for each of the
CLARiiON storage arrays that exist in your environment. Any comment lines should precede the
line containing the serial number.
This file can contain information about a single array, or information for a list of arrays (one per
line) if you have more than one in your environment.
A sample clarcnfg file is shown in this figure.

Three Levels of User Accounts

y ERM Administrator
– Has super user access to all Replication Manager functions
– Manages Users, Clients, and Storage
– Assigns privileges to Replication Manager Database Administrator and
Operator accounts
– Adds Hosts
y Database Administrator
– Defines ApplicationSets, Jobs, and Schedules
– Creates, mounts, restores, and expires Replicas
– Assigns privileges to Replication Manager Database Administrator and
Operator accounts
y Operator
– Runs Jobs and mounts Replicas
– Accesses Jobs and Replicas if granted access by the ERM Administrator
or Database Administrator
Each user with access to Replication Manager has their own individual user credentials (username and
password). Replication Manager defines access rights as three different roles that can be assigned to each
user:
y ERM Administrator
y Database Administrator
y Operator
Replication Manager allows users to access only the functions appropriate to their assigned roles.
ERM Administrator
The ERM Administrator has access to the storage configuration, storage resource allocation, and the
replication server operating environment. ERM Administrators also have access to all functions in the
Replication Manager environment, allowing them to affect all the functions of the software.
Database Administrator
The Database Administrator (DBA) has access to the database environment (or other information system
application). The DBA controls the operation of one or more database application(s) and is often
accountable for those databases. Database Administrators can also create replicas, run Jobs on those
replicas, restore replicas, and perform recovery operations on a database.
Operator
The Operator runs the Replication Manager software on a day-to-day basis and monitors Jobs and replicas
to ensure that the system runs smoothly. Operators carry out the Jobs designed by the ERM Administrator(s)
and Database Administrator(s).

User Accounts - Security Basics

y Separate login per user
y Some objects in the system are shared
– Hosts, storage
y Other logical objects belong to the user that created them

– ApplicationSets
– Jobs
– Replicas
– Schedules
y Access can be granted to other users

– Capabilities depend on their role
y Secure client mode

The Replication Manager Administrator login is used to define logins and passwords and assign Replication
Manager roles. It is a good idea to create two Administrator accounts, one for day-to-day administration
tasks, and the other in case the first account password is lost or the account is deleted. Access to these
accounts should be limited to a small number of people since the Administrator is the super user for
Replication Manager account.
Define a separate user login for every individual who will be using Replication Manager. Multiple logins
may share the same role. Separate logins protect the Replication Manager environment from unauthorized
use by keeping the login information to the person who owns the login, therefore:
y Objects, such as ApplicationSets, Jobs, Replicas, and Schedules created by a user can only be accessed
by the user unless another user is specifically granted access by the user or the Administrator. An
Operator role cannot own an object because the operator cannot define ApplicationSets and Jobs.
Operators can be granted access to objects by the Administrator or Database Administrator.
y Other objects can be shared. Examples include hosts and storage. All users, except the operator, have
access to hosts and storage unless specifically excluded by the owner.
y Secure mode requires users to enter valid user credentials in order to perform the secure operations
(listed below) with that client. If you start the client in Secure Client Mode, Replication Manager asks
for a domain name, user name, and password in order to:
− Run Pre-Replication
− Post-Replication Script
− Mount an Oracle database
− Select a program to run on the mount host
− Select a backup program to run on the mount host

Components of the Main Window
y The main window can be separated into distinct parts
The main window can be separated into the following distinct parts:
y Tree panel - Left panel containing a folder structure
y Content panel - Right panel with information about the selected element(s)
y Menu - Pull-down menus that can be used to start any task
y Toolbar - Buttons that can be used to start certain tasks
y Multiple Storage Array Icons - The console can display information about Symmetrix,
CLARiiON, and StorageWorks arrays all in the same screen
y Panel Controls - Buttons for splitting the content panel or tree panel vertically or horizontally
to display different information. You can also perform panel-based actions, search for specific
items in the window, get help, or close the panel from this control bar.
y Status Bar - Bar at the bottom of the screen that displays a lock icon for SSL, status messages,
server name, and port number in use
y Selection Checkboxes - Checkboxes next to each item in the tree Panel allow you to select one
or more items in that panel. The properties of selected items are displayed in the content panel.

Summary of Storage Process
Array
Discovery Right-click a Client node to discover arrays on a Client
Array Right-click a storage array node to configure

Configuration a storage array
Storage Right-click a storage array node to

Discovery discover storage on a storage array
Right-click a storage array node to Include

Include storage on a storage array Storage
Right-click a storage array node to Storage

Assign storage to a Storage Pool Pools
In summary, this is how the storage process configuration sequence occurs:

Right-click a storage array node to configure a storage array. Configure arrays when:
y You discover a new array
y Array information changes (for example, if you apply a new password)
Right-click a storage array node to discover storage on a storage array.
y Execute manual storage discovery when storage changes occur
y Automatic storage discovery occurs daily
Right-click a storage array node to include storage on a storage array
y Storage must be manually included if the Storage Eligibility checkbox is left blank on
installation
Right-click a storage array node to assign storage to a Storage Pool
y The Storage Pool must be created first
y You can no longer create a Storage Pool through the Assign Storage menu option

Operation Tasks Flowchart
Configuration Operations
Restore Replica
Create
Replica
ApplicationSet Mount Replica
Unmount Replica
Expire Replica
Run Job
Create Job
View Replica
• On Demand
• Scheduled
Replication Manager operations include replication configuration and replica-related operations.

Before a replication Job can be run, you define an ApplicationSet then create an Job.
The information decisions made during Define New ApplicationSet are:
y What to replicate (Unix and NTFS filesystems, Oracle, SQL, Exchange, and UDB databases)
y Name and description of the ApplicationSet
y Production host name
y Which users have access to the ApplicationSet
The process decisions made during Create Job are:
y How long to keep the replica
y How to manage the application during the replication process (Offline/Online)
y What pre and post replication scripts to run
y What storage to use, if necessary
y What to do with the replica after it is completed (mount, run a backup)
The next step is to run the Job to create the replica. Replicas can be scheduled or run on demand.
After the replica is created, you can perform any of the tasks listed in the Operations Box.

Consistent-Split Technology
y Consistent-Split assure a consistent copy after the split
y After restarting the application using the data, no part of
the data will be transactionally out of sync
y Replication Manager can take advantage of this
consistent-split technology to create consistent copies of
application data in the following environments:
– Oracle 8i and 9i in Windows or UNIX
– SQL Server 2000 in Windows 2000/2003
– NTFS File Systems
– UNIX File Systems
The latest Symmetrix storage arrays with TimeFinder software and consistent-split technology
enabled can ensure that the data stored on a BCV, after it is split from its standard, is a logically
consistent copy. This means that after restarting the application using this data, no part of the data
will be transactionally out of sync. That is because any transactions that were in progress, and not
yet committed, will be rolled back when the replica gets mounted or restored. That causes the
replica to be consistent for the point in time when it was created. This consistency is assured not
by the application, but by the hardware and TimeFinder software.
Replication Manager can take advantage of this consistent-split technology to create consistent
copies of application data in the following environments:
y Oracle in Windows or UNIX
y SQL Server 2000 in Windows 2000/2003
y NTFS File Systems
y UNIX File Systems
Note: If your ApplicationSet contains any Exchange or UDB applications, you will not be allowed
to select consistent split when you define the Job because consistent split must apply to all
applications in the ApplicationSet.

Lesson 3 – Replication Manager-SE

Upon completion of this lesson, you will be able to:
y Describe the key features and functionality of RMSE
y Explain the basic architecture of RMSE
The objectives for this lesson are shown here. Please take a moment to read them.

What is RMSE?
y Creates disk replicas of mission-critical information for customers
running Windows on EMC CLARiiON storage arrays
y Designed for the commercial customer space
– Customer installable
– Easy to use
Replication Manager SE is designed by EMC with the objective of easily creating point-in-time,
disk-based replicas of databases and/or file systems residing on CLARiiON storage arrays within a
windows 2000 and or Windows 2003 environment. RMSE can create replicas for applications
such as Microsoft SQL Server databases, Microsoft Exchange databases, and NTFS volumes - as
long as the information is stored on EMC CLARiiON storage arrays.
With RMSE, you can create point-in-time replicas of production data in seconds. These replicas
can exist on the same array as the production data, or on a remote array using SAN Copy. Another
important feature is the facilitation of quick, frequent, and non-disruptive backups from replicas.
RMSE also allows you to mount replicas to alternate hosts to facilitate offline processing, or
mount multiple replicas on the same mount host. Finally, RMSE allows you to restore deleted or
damaged information quickly and easily from a disk replica, as well as set the maximum number
of replicas for replication jobs so that replication storage is made available automatically.
The advantage that RMSE offers is that it automatically controls the complexities associated with
creating, mounting, restoring, and expiring data replicas. RMSE Explorer offers an easy-to-use
interface to help you manage and control these replicas.

Functionality
y RMSE provides replication jobs to designate the production data to be
replicated
Replication Manager SE provides replication jobs to designate the production data to be

replicated, and defines the associated replication actions to be performed on this data. For each
job, you can define a unique replication process and specify how to handle the production data
before and after replication. You can also select the storage that may be used for the replica, and
then manipulate the replica after it has been created. RMSE also allows you to automatically
expire the replica after the maximum number of replicas for that job has been exceeded.

Functionality (continued)
y Schedule replication jobs to run on a regular basis
RMSE’s functionality also allows you to schedule replication jobs to run on a regular basis.
Alternately, you can start a replication job on demand. These replication jobs cause only minimal
(if any) interruption to the information systems that manage the production data.
There are several reasons to use RMSE to create replicas of production data. These include using
the replicas as a source for data backups, using them for decision-support processing, and for data
protection, as a source for restore.
Users also have the ability to define pre- and post-replication scripts to perform user-specified
actions prior to replication, and after the replication completes.

Replication Manager SE Architecture

Console
Host GUI
Only
GUI
GUI
RMSE
Service
RMSE
Database
Source
LUNs
Replication Manager SE utilizes a peer-to-peer architecture, with no additional resource needed

for a server component. The graphic shows the components that make up the Replication Manager
SE application.
The first component is the RMSE Service, which is installed on the host as a part of the
installation.
The second component is the RMSE database, responsible for storing information about
replication jobs, replicas, and the storage they use. This is also a part of the install.
The Graphical User Interface can be installed on the same host or on a separate Windows machine
as a console. The RMSE User Interface is only supported, however, on Windows 2000
Professional, Server, Advanced Server, and Datacenter Editions; Windows 2003 Server Standard,
Enterprise, and Datacenter Editions; or Windows XP.

Peer-to-Peer Architecture
Production Host Mount Host
Mount (Network)
GUI RMSE RMSE
Service Service
RMSE
Database
Source Replica
LUNs LUNs
In this peer-to-peer model, all components are also installed on the mount host. The mount host
Graphical User Interface and Database may not be used unless a separate replication is being
performed from the mount host to another mount host.

RMSE Prerequisites
y Host software prerequisites
– Solutions Enabler
– PowerPath
– Navisphere Agent (on the C:\ drive)
– NaviCLI
– ADMSnap (on the C:\ drive)
– Java 1.4.1_02+ or any 1.4.2_xx
– .Net Framework (for Windows 2000 only)
y CLARiiON array prerequisites

– Navisphere Agent
– SnapView
– Access Logix enabled
– SAN Copy (if used)
RMSE has several application dependencies, such as Solutions Enabler, PowerPath, Navisphere
Agent, NaviCLI, Java Runtime Environment, Admsnap, and, in order to support dynamic, Veritas
Volume Manager is also required. On Windows 2000, the .NET Framework version 1.1 is required
for RMSE Explorer to function properly, which the RMSE installation wizard checks for, and
installs if necessary.
RMSE also has hardware requirements such as one or more of the supported CLARiiON storage
arrays, LAN connectivity between the components, and Fibre connectivity between the RMSE
hosts and the CLARiiON storage array, whether direct connect or through switched fibre
connections. With array hardware requirements also comes array software prerequisites such as
Navisphere Agent, SnapView, and Access Logix enabled, and SAN Copy, if it is to be used. For
the latest requirement listings and specific versions, please see the EMC support matrix.

RMSE Configuration - RMSE Explorer Console
Navigation Pane Details Pane
When the console is first opened, the navigation pane displays the containers that house your
manageable objects. The top-level object in this navigation pane is the RMSE Server, which
contains all manageable objects - the applications, jobs, and arrays. In most cases, the name
appears as “localhost”. If Microsoft Cluster Server is used, the name will appear as the virtual
server name of the cluster. You can expand folders through these groups and their data to display
details about individual objects. This will allow you to reveal successive levels of detail and
additional manageable objects.

RMSE Application Support Matrix
Replication Manager SE supports the following database applications for replication: Exchange
5.5, Exchange 2000, Exchange 2003, and SQL Server 2000. Replication Manager SE can mount
replicas on an alternate mount host, as well as back to the production host, and restore from
replicas created using Snaps and Clones. As always, for the most up-to-date information, check the
support matrix.

9 Check Your Knowledge

Which applications does Replication Manager SE support?
A. Oracle
B. Unix Filesystems
C. NTFS Filesystems
D. UDB/DB2
E. MS SQL Server
F. MS Exchange Server
Select the applications that Replication Manager SE supports. Pause the presentation before
continuing.

9 Check Your Knowledge

Which applications does Replication Manager SE support?
A. Oracle
B. Unix Filesystems
C. NTFS Filesystems
D. UDB/DB2
E. MS SQL Server
F. MS Exchange Server
The correct answers are C. NTFS Filesystems, E. MS SQL Server, and F. MS Exchange Server.

Course Summary
Key points covered in this course:
y Replication Manager Family Features
y Architecture
– Replication Manager
– Replication Manager SE
y Support Matrix by Version
These are the key points covered in this course. Please take a moment to review them.
This concludes the training. In order to receive credit for this course, please proceed to the Course
Completion slide to update your transcript and access the Assessment.

Replication Manager Foundations - Self Study

Uploaded by

Document Information

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

Replication Manager Foundations - Self Study

Uploaded by

Copyright:

Available Formats

Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved.

Introduction to Business Continuity

© 2006 EMC Corporation. All rights reserved.

Welcome to Introduction to Business Continuity. This section introduces Business Continuity

Replication Manager Foundations - 1

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 2

Replication Manager Foundations - 2

What is Business Continuity

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 3

Replication Manager Foundations - 3

Why Business Continuity

Damaged Reputation Financial Performance

• Customers • Revenue recognition

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 4

Replication Manager Foundations - 4

Business Continuity – Obstacles of Availability

Disaster (<1% of Occurrences)

Unplanned Occurrences (13% of

Planned Occurrences (87% of Occurrences)

Source: Gartner, Inc.

Replication Manager Foundations - 5

Cost of Downtime Per Hour By Industry

$0 $100,000 $200,000 $300,000 $400,000

Source: AMR Research

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 6

Replication Manager Foundations - 6

Business Continuity Starts with Data Protection

Without the Data there is no Recovery!

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 7

Replication Manager Foundations - 7

Data Protection with Disk Mirroring

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 8

Replication Manager Foundations - 8

Multiple Mirrors - Multiple Uses

Replication Manager Foundations - 9

Business Continuity Objectives

Documented business continuity

Global business processes 24-hour application-availability

Application consolidations: 75% of downtime Increased business impact of

Direct customer and partner

Replication Manager Foundations - 10

Meeting our Objectives with

Time y Availability y Distance

Replication Manager Foundations - 11

Business Continuity is a Core EMC Competency

y Disciplined and proven methodology

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 12

Replication Manager Foundations - 12

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 13

Replication Manager Foundations - 13

© 2006 EMC Corporation. All rights reserved.

Welcome to Replication Manager Foundations.

Replication Manager Foundations - 14

Replication Manager Foundations

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 15

Replication Manager Foundations - 15

What is the Replication Manager Family

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 16

The Replication Manager family is a portfolio of replication management products designed to

Replication Manager Foundations - 16

Why Replication Manager

y Data corruption and loss are at best unpredictable

© 2006 EMC Corporation. All rights reserved. Replication Manager Foundations - 17