Replication Manager SE PDF

Replication Manager SE
Version 3.0.0
USER GUIDE
P/N 300-001-654
REV A04
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.emc.com
Copyright 2005 EMC Corporation. All rights reserved.

Printed May, 2005
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.
Trademark Information
ii
Replication Manager SE User Guide
Contents
Preface............................................................................................................................. ix
Chapter 1
Introduction
Replication Manager SE Overview ................................................1-2
Determining your Replication Goals .............................................1-3
Repurposing ...............................................................................1-3
Backup and Recovery................................................................1-4
Disaster Restart ..........................................................................1-4
Copies of Replicas......................................................................1-4
General Functionality.......................................................................1-5
Understanding Storage Options..............................................1-5
Supported Applications............................................................1-6
Making the Transition to Replication Manager.....................1-8
Supported Replications....................................................................1-9
Clones ..........................................................................................1-9
Snapshots ....................................................................................1-9
SAN Copy .................................................................................1-10
Snaps versus Clones ................................................................1-15
Chapter 2
Before You Begin

Hardware and Software Requirements .........................................2-2
Required Hardware and Connectivity ...................................2-2
Install Patches and Service Packs ............................................2-2
Required Software for CLARiiON Arrays .............................2-3
Required Software for RMSE Hosts ........................................2-3
Verifying Your Configuration .........................................................2-4
Installing Prerequisite Software on RMSE Hosts and the
CLARiiON Array ..............................................................................2-7
iii
Contents
Managing RAID Groups, LUNs, and Storage Groups................2-8

Configuring RAID Groups.......................................................2-8
Creating LUNs and Binding Them to RAID Groups ...........2-9
Assigning LUNs to the Storage Groups...............................2-10
Preparing CLARiiON Drives for Snapshot Replications..........2-12
Preparing CLARiiON Arrays for Full and Incremental
SAN Copy Replications .................................................................2-14
Install SAN Copy Software on the CLARiiON(s)...............2-15
Zone SAN Copy Ports ............................................................2-15
Create a SAN Copy Storage Group ......................................2-17
Connect the SAN Copy Storage Group to the Remote
CLARiiON ................................................................................2-18
Chapter 3
Installing RMSE
Installation Overview.......................................................................3-2
Installing RMSE .........................................................................3-2
Upgrading Previous Versions of RMSE to RMSE 3.0.0 ........3-3
Modifying or Removing RMSE ...............................................3-4
Installing RMSE in a Microsoft Cluster Server Environment ....3-5
Overview of MSCS Support.....................................................3-5
Installing RMSE on MSCS ........................................................3-6
Upgrading from RMSE 2.1.5 and 2.2.0 on Cluster Nodes ...3-8
Chapter 4
Getting Started
Components of RMSE ......................................................................4-2
Starting RMSE Explorer...................................................................4-3
Launching RMSE .......................................................................4-3
RMSE Explorer Menu Bar ........................................................4-5
RMSE Explorer Tree Panel .......................................................4-5
RMSE Help ........................................................................................4-8
RMSE Help Types......................................................................4-8
Using the RMSE Help Viewer .................................................4-9
Chapter 5
Working with RMSE Servers

Adding RMSE Servers to Your Managed Environment .............5-2
Adding RMSE Servers ..............................................................5-3
Viewing and Modifying Individual Server Properties................5-5
Changing the Java Path ............................................................5-5
Changing the Log Level ...........................................................5-6
Viewing a List of All Virtual Nodes in the Cluster...............5-6
iv
Contents
Viewing and Modifying Server-Wide Properties ........................ 5-8

Changing the Clone Synchronization Rate ........................... 5-8
Changing the Automatic
Refresh Rate ............................................................................... 5-8
Displaying Information From a Disconnected Server ................ 5-9
Chapter 6
Using Jobs to Create Replicas

Working with Jobs............................................................................ 6-2
Creating a Job ............................................................................ 6-2
Running a Job .......................................................................... 6-11
Cancelling a Running Job ...................................................... 6-12
Scheduling a Job...................................................................... 6-12
Modifying a Job....................................................................... 6-15
Deleting a Job........................................................................... 6-16
Copying a Replica .......................................................................... 6-17
Chapter 7
Configuring RMSE Storage and Applications

Discovering Storage ......................................................................... 7-2
Adding Storage ......................................................................... 7-2
Modifying Storage Properties ................................................. 7-3
Discovering LUNs .................................................................... 7-5
Discovering Applications................................................................ 7-6
Chapter 8
Working with RMSE Replicas

Viewing Replica Properties............................................................. 8-2
Expiring Replicas ............................................................................. 8-3
Expiring a Replica Automatically........................................... 8-3
Expiring a Replica on Demand ............................................... 8-3
Mounting a Replica.......................................................................... 8-4
Mount Host Requirements for MSCS Cluster....................... 8-7
Restoring a Replica .......................................................................... 8-8
Restoring a Replica to an MSCS Cluster.............................. 8-11
Using CLARiiON Protected Restore .................................... 8-12
Restoring Replicas from Tape Backups....................................... 8-13
Contents
Chapter 9
Troubleshooting RMSE
Viewing Results in Logs ..................................................................9-2
Routine Maintenance .......................................................................9-3
Cleaning Up Resources Affecting the LUN Limit ................9-3
Backing Up RMSE Configuration Data..................................9-4
Common Problems and Solutions..................................................9-5
RMSE Event Messages ...................................................................9-13
Appendix A
Microsoft Exchange Procedures

Configuring Exchange Hosts ........................................................A-2
Exchange Data Layout .............................................................A-2
Configuring Exchange 2000/2003 Production Hosts..........A-2
Configuring Exchange 5.5 Production Hosts .......................A-5
Configuring Exchange Mount Hosts .....................................A-6
Configuring Exchange Mount Hosts for Consistency
Checking Only ..........................................................................A-8
Creating Exchange 2000/2003 Replicas .......................................A-9
Support for VSS on Exchange 2003........................................A-9
Exchange 2000/2003 Data Objects in the Job .......................A-9
Planning for Recovery ...........................................................A-10
Hot-Split Replication on Windows 2000 .............................A-10
Replicating Exchange 2003 with VSS...................................A-12
Exchange 2000/2003 Offline Replication ............................A-13
Detecting Data Corruption....................................................A-14
Exchange 2000 Log Truncation as Part of Replication ......A-15
Creating Exchange 5.5 Replicas ..................................................A-16
Exchange 5.5 Online Replications Using Hot Split............A-16
Exchange 5.5 Offline Replication .........................................A-17
Check Database Consistency with ESEFILE Utility ..........A-17
Truncate Logs to Help Manage Exchange Backups ..........A-17
Exchange 5.5 Mailbox Recovery...........................................A-18
Mounting Exchange 5.5, 2000, and 2003 Replicas ....................A-19
Recovering Exchange 2000/2003 Data ......................................A-20
Selecting Full or Partial Restores..........................................A-21
Restore Considerations ..........................................................A-21
Restoring Exchange 2000/2003 Replicas on
Windows 2000 .........................................................................A-22
Restoring Exchange 2003 VSS Replicas ...............................A-24
Restoring an Exchange 2003 SAN Copy Replica
to a Cluster...............................................................................A-26
Restoring Exchange 2003 VSS Replicas from Tape ............A-27
Exchange 2000/2003 Mailbox Recovery .............................A-32
vi
Contents
Recovering Data From Individual Exchange 2003

Mailboxes ................................................................................ A-33
Recovering Exchange 5.5. Data .................................................. A-38
Restore the Exchange 5.5 Database ..................................... A-38
Mounting Exchange 5.5 for Mailbox Recovery ................. A-39
Using Exchange Scripts ............................................................... A-40
Appendix B
SQL Server Procedures

Configuring the SQL Server 2000 Environment .........................B-2
SQL Server Prerequisites..........................................................B-2
Backing Up SQL Server Including VDI Metadata Files ......B-3
Mounting and Restoring SQL Server 2000 Replicas ..................B-4
Mounting SQL Server Replicas ...............................................B-4
Restoring SQL Server Replicas................................................B-5
Restoring Individual SQL Server Databases.........................B-7
Restoring a SQL Server SAN Copy Replica to a Cluster... B-11
Using SQL Server VDI Snapshot Functionality ........................B-13
Restore Steps in Detail............................................................B-13
Using SQL Server Scripts .............................................................B-15
General Guidelines for SQL Server Scripts .........................B-15
Sample Replication Script ......................................................B-16
Appendix C
NTFS Procedures
Creating NTFS Replicas ................................................................ C-2
NTFS Replication Operation .................................................. C-2
Mount Host Requirements for NTFS Volume Replicas...... C-2
NTFS Mount and Restore Functions ..................................... C-3
Windows Host System Layer Concepts ...................................... C-4
Windows Host Data Layer Concepts .................................... C-4
Windows Logical Volume Manager Concepts..................... C-5
Using NTFS Volume Scripts ......................................................... C-6
Index ............................................................................................................................... i-1
vii
Contents
viii
Preface
As part of an effort to improve and enhance the performance and capabilities

of its product line, EMC from time to time releases revisions of its hardware
and software. Therefore, some functions described in this guide may not be
supported by all revisions of the software or hardware currently in use. For
the most up-to-date information on product features, refer to your product
release notes.
If a product does not function properly or does not function as described in
this guide, please contact your EMC representative.
Replication Manager
SE User Guide
Information
This guide describes how to install, configure, and operate

Replication Manager SE in the CLARiiON storage arrays
environment.
Adobe Acrobat Reader is required to view the online version of the
guide. You can download Acrobat Reader for free at www.adobe.com.
Purpose of This Guide
This guide describes how to install, configure, and use RMSE

storage-management and data-protection software to protect the
following mission-critical applications on your CLARiiON storage
array:
SQL Server databases on Windows 2000 and Windows

Server 2003
Exchange 2003, Exchange 2000, and Exchange 5.5 mail databases

on Windows 2000
Exchange 2003 on Windows Server 2003
NTFS file systems on Windows 2000 and Windows Server 2003
ix
Preface
Audience
This guide is intended for use by storage administrators, database

administrators, and operators to learn the basic operation of the
RMSE software. Readers of this guide are expected to be familiar with
the following topics:
Related
Documentation
Operation of application software used in conjunction with RMSE

Operation of all operating systems on hosts attached to RMSE
Hardware and software components of the storage arrays that are
part of your storage environment
Any third-party software that you use with RMSE, such as
volume managers
Related RMSE documentation includes:
Replication Manager SE Release Notes, which are delivered with the

product CDs and describe critical and late-breaking information
about the product.
Replication Manager SE Quick Start Guide, which is delivered with

the product CDs and describes the step-by-step installation and
configuration of Replication Manager SE on a production host
and mount host. The Guide also describes simple tests to perform
to verify that the installation was successful.
For specific information about supported applications, operating

systems, high-availability environments, volume managers, and
other supported software, refer to the Replication Manager SE Support
Matrix on http://powerlink.emc.com.
Another related EMC enterprise storage publication is the EMC
Support Matrix, available on the Web. Go to this page:
http://www.emc.com/horizontal/interoperability
Choose the link to the EMC Support Matrix.

Conventions Used in
This Guide
EMC uses the following conventions for notes and caution notices.
A note presents information that is important, but not hazard-related.
CAUTION
A caution contains information essential to avoid damage to the
system or equipment. The caution may apply to hardware or
software.
Preface
Typographical Conventions
EMC uses the following type style conventions in this guide:
AVANT GARDE
Keystrokes
Palatino,
bold
Palatino,
italic
Dialog box, button, icon, and menu items in text

Selections you can make from the user interface,
including buttons, icons, options, and field
names
New terms or unique word usage in text
Command line arguments when used in text
Book titles
Courier,
italic
Arguments used in examples of command line

syntax.
Courier
System prompts and displays and specific

filenames or complete paths. For example:
working root directory [/user/emc]:
c:\Program Files\EMC\Symapi\db
Courier,
bold
irccd -h
Where to Get Help
User entry. For example:
Options in command line syntax
For questions about technical support, call your local sales office or
service provider.
If you have a valid EMC service contract, contact EMC Customer
Support at:
United States: (800) 782-4362 (SVC-4EMC)
Canada:
(800) 543-4782 (543-4SVC)
Worldwide:
(508) 497-7901
Follow the voice menu prompts to open a service call and select the
applicable product support.
If you are located outside the North America, call the nearest EMC
office for technical assistance.
xi
Preface
Sales and Customer

Support Contacts
For the list of EMC sales locations, please access the EMC home page
at:
http://www.emc.com/contact/
For additional information, including how to find RMSE updates and
related software, refer to the EMC Powerlink website at:
http://powerlink.emc.com
Your Comments
xii
Your suggestions will help us continue to improve the accuracy,

organization, and overall quality of the user publications. Please send
a message to doc_comments@emc.com with your opinions of this
guide.
1
Invisible Body Tag
Introduction
Replication Manager SE (RMSE) creates disk replicas of your

mission-critical information on EMC CLARiiON storage arrays.
RMSE creates replicas of this data simply and quickly by automating
many of the important procedures related to data replication. This
chapter, which introduces RMSE and explains the benefits it offers,
includes the following sections:
Replication Manager SE Overview .................................................1-2

Determining your Replication Goals ..............................................1-3
General Functionality ........................................................................1-5
Supported Replications .....................................................................1-9
RMSE makes your work easier by allowing you to focus your

attention on the replication management tasks, not on the software
that performs those tasks.
Introduction
1-1
Introduction
Replication Manager SE Overview

Replication Manager SE makes it easy for you to create point-in-time,
disk-based replicas of databases or file systems residing on your
existing storage arrays.
RMSE can create replicas of information stored on EMC CLARiiON
storage arrays in the following Windows 2000 or Windows Server
2003 environments:
Microsoft SQL Server databases
Microsoft Exchange databases
NTFS volumes
With RMSE you can:
Create point-in-time replicas of production data in seconds.

Replicas can exist on the same array as the production data, or
on a remote array using SAN Copy.
Facilitate quick, frequent, and non-disruptive backups from

replicas.
Mount replicas to alternate hosts to facilitate offline processing

(for example, decision-support services, integrity checking, and
offline reporting).
Mount multiple replicas on the same mount host.
Restore deleted or damaged information quickly and easily from

a disk replica.
Set the maximum number of replicas for replication jobs so that

replication storage is freed automatically by expiring replicas.
RMSE 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.
1-2
Introduction
Determining your Replication Goals

Replication Manager SE offers many different methods of creating a
replica. Some of these methods create a replica on the same storage
array as the source data, others create a replica on another array
connected using SAN Copy. This section helps you decide the best
technologies to use for replicas based on your goals.
When you create a replica by configuring a job, there are certain
configurable components that alter:
How the application is quiesced
Where the replica resides
The duration of the replica
How often a new replica is created
Whether or not additional processing occurs before, during, or

after the replica has been created
This section offers some guidelines that can help you determine the
best settings to use when you plan to create replicas for different
purposes.
Repurposing
If you plan to use the data in your replica to carry out another
function (such as reporting, analysis, or data mining) without
impacting the production instance of the application, you should
consider using the following settings:
Mount the replica to an alternate host (if possible).
Use a mount recovery method that allows you to start up the

application (so you can access the data) in either a read/write or
read only mode.
Use post-replication scripts to start the processing that you plan

to conduct on the replica.
These settings reduce the stress on the production instance and the
production server. They also allow you the freedom to access (and
possibly manipulate) the data to complete your repurposing task
without affecting your production data.
Determining your Replication Goals
1-3
Introduction
1
Backup and
Recovery
Disaster Restart
Copies of Replicas
1-4
If you plan to use the data in your replica to create a backup and
potentially restore that backup at a later time, you should consider
using the following settings:
Consider creating a replica rotation that allows you to preserve a

certain number of replicas.
If you are backing up to tape, you should mount the replica, copy
any metadata needed for recovery, and use RMSEs ability to start
a backup script automatically.
Use a mount recovery method that is appropriate for the type of

backup you are performing.
Validate the data (for example, by running ESEUTIL on an

Exchange replica) before you run the backup.
Mount the replica as read-only.
If you plan to use the data in your replica to restart your application
after a disaster, you should consider using the following settings:
Choose a SAN Copy replication so that the replicated data is

located in a different physical location than the production data.
Mount the replica and verify the validity of the replicated data.
Ensure that the replica includes all the data that you will need to
restart the application after a disaster occurs.
If you want to create multiple copies of an already existing replica,

consider using the following settings:
Use the Copy Job functionality to create a copy of an existing

replica.
See other sections to determine other settings based on the

suggested usage of this replica.
Introduction
General Functionality
RMSE provides replication jobs to designate the production data to be
replicated, and define the associated replication actions to perform on
this data. For each job, you can define a unique replication process.
Each job specifies how to:
Handle the production data before and after replication.
Manipulate the replica after it has been created.
Automatically expire the replica after the maximum number of

replicas for that job has been exceeded.
You can schedule replication jobs to run on a regular basis, or you can
start a replication job on demand. Replication jobs cause only
minimal interruption to the information systems that manage the
production data.
There are several reasons to use RMSE to create replicas of
production data, including:
Source for data backups
Decision-support processing
Data protection (source for restore)
Also, the jobs can run pre- and post-replication scripts to perform
user-specified actions prior to replication, and after the replication
completes.
Understanding
Storage Options
Replication Manager SE can create replicas of data stored on any of

the following CLARiiON storage arrays:
CLARiiON CX700 series
On these CLARiiON arrays, RMSE can take advantage of clone,

snapshot, and SAN Copy functionality. When you create a replica
using clone functionality, you make an exact copy of the data onto a
separate LUN or disk. When you create a snapshot replica, the data is
stored as a copy on first write to disk-based cache memory. Snapshots
1-5
Introduction
1
only store the information from changed tracks, so they use a
minimum of cache storage space on the CLARiiON array.
Clones should be used for long-term storage or storage of more
critical data, while snapshot replicas can be used effectively for
short-term data storage and working copies of the data.
Replication Manager SE also supports EMC SAN Copy software,
which allows you to move data from one CLARiiON array to another
CLARiiON array. For more information about SAN Copy
functionality, refer to SAN Copy on page 1-10.
Supported
Applications
This section describes supported Replication Manager SE database

applications and the types of information that can be replicated. Refer
to the Replication Manager SE Support Matrix on Powerlink for
updated information and specific service pack and operating system
information.
All replicated data must reside on a supported CLARiiON storage array.
Microsoft Exchange
This section summarizes RMSEs support for Microsoft Exchange.

See Appendix A, Microsoft Exchange Procedures, for more detailed
information about using Microsoft Exchange with RMSE.
Exchange versions supported:

Exchange 2003, Exchange 2000, Exchange 5.5
Objects that can be replicated in a job:

One or more storage groups (Exchange 2003/2000)
Information store or directory store (Exchange 5.5)
Exchange 5.5, 2000, and 2003 replicas on Windows 2000 can be

hot-split (online) or offline.
Exchange 2003 replicas on Windows Server 2003 can be online or

offline. Volume Shadow Copy Service (VSS) is used to perform
the online replicas.
Exchange 2003/2000 objects that can be restored:

One or more storage groups (databases and log files)
One or more databases
Exchange 5.5 objects that can be restored:

Information store, directory store, or both
1-6
Introduction
Microsoft SQL Server
This section summarizes RMSEs support for Microsoft SQL Server.

See Appendix B, SQL Server Procedures, for more detailed information
about using Microsoft SQL Server with RMSE.
SQL Server version supported:

Microsoft SQL Server 2000 (32-bit)
Objects that can be replicated in a job:

One or more SQL Server databases that reside on the same
LUN, or across multiple LUNs
Objects that can be restored:

Complete database (including transaction logs)
Filegroup
RMSE works with the Microsoft SQL Server Virtual Device Interface
(VDI) to make replicas of SQL Server databases. Data and logs are
replicated in the same job. Filegroup replications are not supported;
the complete database must be replicated.
NTFS Volumes
RMSE can create replicas and initiate and control mounts and restores
of NTFS volumes. Mount and restore options include:
Mounts on an alternate mount host to the same location as the

production host
Mounts on an alternate mount host to a new location (determined

by adding an alternate drive letter and optionally path
information to the beginning of the path name)
Mounts to the original production host in a new location

(determined by an alternate drive letter and optionally path
information to the beginning of the pathname).
See Appendix C, NTFS Procedures, for more detailed information

about using RMSE with NTFS volumes.
1-7
Introduction
1
Making the
Transition to
Replication
Manager
RMSE provides an easy-to-use, streamlined interface for creating and

managing Windows-based Exchange and SQL Server database
replications. However, if you need a more enterprise-wide solution,
consider making the transition to Replication Manager.
Replication Manager provides all of the functionality of RMSE plus
the following additional features and enhancements:
Replications on both Symmetrix and CLARiiON arrays
Replications on Solaris, Linux, HP-UX, AIX, and Windows

production hosts
Replications of Oracle and IBM UDB databases in addition to

Exchange and SQL Server
Management of user accounts and associated privileges
These additional features and enhancements combine to make a

compelling case for making the transition from RMSE to Replication
Manager. To learn more, contact your sales representative.
1-8
Introduction
Supported Replications
Before we describe how to plan for replicas, it is important to
understand a little bit about the types of EMC CLARiiON replications
that RMSE supports: Clone, Snapshot, and SAN Copy.
Clones
Clone replicas are full, exact copies of production data created using
SnapView clones. Since they are complete copies of source LUNs,
clones can be an effective means of storing critical data for long
durations.
Snapshots
CLARiiON SnapView provides another method of creating different

types of copies of source LUNs on a CLARiiON array. The method is
commonly referred to as snapshots. Unlike a clone, which is an actual
copy of a LUN, a snapshot is a virtual point-in-time copy of a LUN.
RMSE determines the point in time to start a snapshot session. The
snapshot session keeps track of how the source LUN looks at a
particular point in time. SnapView includes the ability to roll back, or
restore, a SnapView session.
Snapshots are comprised of data that resides on the source LUN and
on the snapshot cache. The data on the source LUN that has not been
modified since you started the session is not copied. The data on the
snapshot cache consists of copies of the original source LUN data that
have been modified since you started the session. The snapshot
appears as a LUN to hosts, but does not reside on a disk like a
conventional LUN.
During a snapshot session, the production host is still able to write to
the source LUN (logical unit) and modify data. When this occurs, the
software stores a copy of the original data in the snapshot cache. This
operation is referred to as copy on first write and occurs only once for
each chunk of data that is modified on the source LUN.
As the session continues and additional I/O modifies data chunks on
the source LUN, the amount of data stored in the snapshot cache
grows. If needed, you can increase the size of the snapshot cache by
adding more LUNs. Refer to the EMC SnapView Version 2.X for EMC
Navisphere 6.X Administrators Guide for more information on the
allocation of snapshot cache LUNs.
1-9
Introduction
1
Important: An adequate number of snapshot cache LUNs is essential since
the CLARiiON software terminates sessions if the snapshot cache runs out of
space. This could result in the loss of replications.
By using CLARiiON snapshots as an alternative, or a complement to

CLARiiON clones, RMSE lets you pick the right replication
technology for your needs.
SAN Copy
RMSE supports EMC SAN Copy functionality for creating a replica of

data on a separate CLARiiON storage array. This functionality is
supported on arrays equipped with SAN Copy software, sold
separately.
EMC SAN Copy software is a storage-system-based data-mover
application that uses a Storage Area Network (SAN) to copy data
between storage systems. Since SAN Copy runs on the storage
systems, this eliminates the need to move data to and from the
attached hosts and reserves host processing resources for users and
applications. Since the host is not involved in the copy process, and
the data migration takes place on the SAN, the copy process is much
faster than the LAN-based, host-involved copy process.
Before you can use RMSE to create SAN Copy data replications, you
must first properly zone your CLARiiON storage arrays. Once zoned,
you can then configure SAN Copy on your arrays using Navisphere
Manager. Navisphere Manager is an easy-to-use, Web-based
management tool that allows you to configure your CLARiiON
arrays for SAN Copy.
For more information on how to use Navisphere Manager, refer to the
EMC SAN Copy Version 2.X for EMC Navisphere 6.X Administrator's
Guide.
You can create the following types of SAN Copy replicas:
Full SAN Copy replicas of CLARiiON LUNs onto a CLARiiON

clone on a remote storage array, and Full SAN Copy replicas of an
existing replica located on a CLARiiON onto a remote CLARiiON
storage array
Incremental SAN Copy replicas of CLARiiON LUNs onto a

CLARiiON snapshot on a remote storage array
Each of these types of SAN Copy replicas are described in detail in

the following sections.
1-10
Introduction
Full SAN Copy
When you create a Full SAN Copy replica or a SAN Copy replica of
an existing replica, RMSE uses a CLARiiON LUN as the source. Then,
RMSE performs the following steps automatically:
1. Creates a copy of the source disk (SnapView Snapshot on
CLARiiON). RMSE performs this step to reduce the amount of
time that the application must be quiesced. Once the snapshot has
been created, the application can come back online.
2. Creates a Full SAN Copy replica on a CLARiiON Clone located
on a remote CLARiiON storage array using the new Snapshot as
the source. See Figure 1-1 for an illustration of this process.
Figure 1-1
Creating a Full SAN Copy Replica on a Remote CLARiiON

To support a Full SAN Copy replica, you must include SnapView Snapshots
on the source storage array, along with enough CLARiiON LUNs on the
target storage array to hold the replica.
1-11
Introduction
1
Target
Source
3
2
Target
Production
Host
SAN
Snap
Target
CLARiiON Array
(SAN Copy Storage System)
Figure 1-2
CLARiiON Array 2
How Full RMSE SAN Copy Replications Work
RMSE quiesces the application on the production host.
RMSE creates a snapshot of the production data source.
RMSE enables the application on the production host.
RMSE performs the SAN Copy to the destination LUN

(Target), with the snapshot as the source.
The target device is cataloged as the replica.
The snapshot is discarded after the SAN Copy
replication.
RMSE supports replications using SAN Copy sessions between two

CLARiiON storage arrays. At least one of the storage arrays must be running
SAN Copy software.
Incremental
SAN Copy
When you create an incremental SAN Copy replica, the source data
must be located on a source LUN in a CLARiiON storage array.
RMSE performs the following steps automatically:
1. Checks to see if a previous replica has been created by the job. If
not, an Incremental SAN Copy session will be created to a remote
CLARiiON clone and the SAN Copy session will be marked to
start tracking changes in order to create an incremental copy in
1-12
Introduction
the future. If the job has previously created a replica, then the
changes will be updated on the same remote clone that was
previously used.
2. The clone will be immediately duplicated onto a SnapView
Snapshot. The snapshot will be used as the replica to protect the
integrity of the target LUN in case of future incremental replicas.
See Figure 1-3 for an illustration of this process.
Figure 1-3
Creating an Incremental SAN Copy Replica on a Remote CLARiiON

To support an incremental SAN Copy replica, you must include CLARiiON
LUNs on the target storage array to hold the incremental SAN Copy data,
along with enough SnapView Snapshots also on the target storage array to
hold the replica itself.
1-13
Introduction
2
Target
Source
5
Production
Host
Snap Monday
Snap Tuesday
SAN
1
Session
Snap Wednesday
CLARiiON Array
Figure 1-4
CLARiiON Array 2
How Incremental RMSE SAN Copy Replications Work
RMSE creates an Incremental SAN Copy session on the

SAN Copy storage system.
RMSE quiesces the application on the production host.
RMSE marks the data to be replicated in the Incremental

SAN Copy session.
RMSE enables the application on the production host.
If this is the first replica, it will be a full copy to the

destination LUN (Target), with the point in time image as
the source. Subsequent replicas will be incremental copies
of the point in time image as marked in step 3 above.
For Incremental SAN Copy sessions, the source CLARiiON array must be
running SAN Copy software.
See Creating a Job on page 6-2 for information on creating Full and
Incremental SAN Copy replicas, and Preparing CLARiiON Arrays for
Full and Incremental SAN Copy Replications on page 2-14 for
information about how to configure your hosts and storage arrays to
support EMC SAN Copy.
1-14
Introduction
Snaps versus Clones
Depending on your application needs, you can create clones,

snapshots, or a combination of both. In general, you should use
clones for large amounts of data that change frequently, and snaps for
data that is more static. Clones always require the same amount of
disk space as the source LUN. Snapshots, on the other hand, only
require enough snapshot cache space to support the data that has
changed on the source LUN (typically 10 to 20 percent of the source
LUN size, but will vary depending on how much data has changed).
Also, clones typically take longer to create than snaps. However,
snapshots may have a bigger impact on performance due to the
amount of potential data copies required to synchronize the snapshot
cache. This is especially true for source data that changes frequently.
EMC does not recommend using RMSE to create snaps of Exchange replicas.
Doing so may impact the performance of the production databases.
Refer to the EMC SnapView Version 2.X for EMC Navisphere 6.X
Administrators Guide for more information on the trade-offs between
clones and snapshots.
1-15
Introduction
1-16
2
I
Before You Begin
This chapter lists the basic requirements, restrictions, and

configuration guidelines for using RMSE to work with Clone,
Snapshot, and SAN Copy replications on the EMC CLARiiON array.
It includes the following subjects:
Finding Current
Information and
Updates
Hardware and Software Requirements ..........................................2-2

Verifying Your Configuration...........................................................2-4
Installing Prerequisite Software on RMSE Hosts and the
CLARiiON Array ...............................................................................2-7
Managing RAID Groups, LUNs, and Storage Groups .................2-8
Preparing CLARiiON Drives for Snapshot Replications ...........2-12
Preparing CLARiiON Arrays for Full and Incremental
SAN Copy Replications...................................................................2-26
The most up-to-date information about RMSE software is posted on

the EMC Powerlink website. We recommend that you download the
latest information, as well as any updates to the software or
associated utilities, before you start the RMSE software for the first
time.
To access EMC Powerlink, use the following link:
http://powerlink.emc.com
Before You Begin
2-1
Before You Begin
Hardware and Software Requirements

For specific information about supported applications, operating
systems, high-availability environments, volume managers, and
other supported software, refer to the Replication Manager SE Support
Matrix on Powerlink.
Required Hardware
and Connectivity
The following storage and connectivity hardware components are

required for any implementation of RMSE:
One or more supported CLARiiON array(s):

You can configure any of these arrays to perform the following
tasks in conjunction with RMSE:
Create replicas using CLARiiON SnapView software
Mount those replicas to alternate hosts
Restore information from those replicas
Install Patches and

Service Packs
Fibre connectivity between the RMSE host and the CLARiiON

array(s) (direct connect or through switched fibre connections)
Depending on the version of Windows and the applications you are

running, there may be OS and application patches and service packs
that you need to install on the RMSE server.
1. Refer to the Replication Manager SE Support Matrix on
http://powerlink.emc.com.
2. Obtain the required patches from the manufacturers website and
install.
2-2
Before You Begin
Required Software
for CLARiiON Arrays
Replication Manager SE supports the following CLARiiON software:
FLARE Release 14
FLARE Release 16
Refer to the Replication Manager SE Support Matrix for the latest

information on minimum required software for the CLARiiON array.
Required Software
for RMSE Hosts
The following software must be installed on all RMSE production

and mount hosts:
EMC Solutions Enabler.
EMC PowerPath (can be Utility Kit PowerPath).
EMC Navisphere Agent.
EMC NaviCLI, including Navisphere Classic and Navisphere

Java.
EMC Admsnap.
Java 2 Runtime Environment.
For dynamic disk support on Windows 2000, VERITAS VxVM is

required.
On Windows 2000, .NET Framework 1.1 is required if RMSE

Explorer is being installed. The RMSE installation wizard checks
to see if .NET Framework is present and installs it if necessary.
Hardware and Software Requirements
2-3
Before You Begin
Verifying Your Configuration

Replication Manager SE provides a helpful utility, the RM Config
Checker, to automatically verify that your software, storage arrays,
and clients are properly configured for use with RMSE. The RM
Config Checker offers a quick and easy method for verifying your
configuration. EMC recommends that you run the RM Config
Checker before starting RMSE for the first time, and after any
software or hardware updates.
EMC Solutions Enabler (SymmAPI) must be installed in order for RM
Config Checker to perform array discovery.
Installing RM Config
Checker
To install the RM Config Checker:

1. Insert the RMSE distribution CD in the CD-ROM drive. The
RMSE welcome screen appears.
2. Select Install RM Config Checker.
3. Follow the RM Config Checker installation wizard prompts.
Running RM Config
Checker
To run RM Config Checker:

1. Select Start > Program Files > RMConfig Checker > RM Config
Checker. The RM Config Checker interface appears.
2. Select Action > Register Storage to register the storage arrays to
be checked.
2-4
Before You Begin
3. When the Register Storage window appears, click Add a new

storage array.
Figure 2-1
Register Storage Dialog Box
4. When the Add Storage window appears, enter:

The serial number of the CLARiiON array.
The IP address for SP A.
The IP address for SP B.
User name and password of an administrator account to
access the CLARiiON array.
Figure 2-2
Add Storage Dialog Box
5. Click OK to save and close Add Storage window.
Verifying Your Configuration
2-5
Before You Begin
2
6. Select Action > Run to check the configuration.
You may see a number of command prompt windows appear
during a discovery or configuration check. This is normal, and
these extra windows will close at the conclusion of the discovery
or check.
Figure 2-3
Config Checker Results
7. Select File > Save Results to save an ASCII copy of the RM

Config Checker results. The results list which tests have passed
and failed, and how to remedy failures.
Tests Performed by RM
Config Checker
RM Config Checker performs four groups of tests: client resident

software excluding CLARiiON-specific packages, client resident
software including CLARiiON-specific packages, CLARiiON-array
resident software, and CLARiiON environmental/setup issues.
For the complete list of all tests that RM Config Checker performs, see
the readme_testinfo.txt file that is installed with the utility.
2-6
Before You Begin
Installing Prerequisite Software on RMSE Hosts and the CLARiiON

Array
The Replication Manager SE Quick Start Guide provides step-by-step
instructions on how to install the required software on RMSE hosts
and the CLARiiON array, and how to configure the CLARiiON array
for use with RMSE. The Quick Start Guide is included in your CD kit,
and is available as a PDF document in the Docs subdirectory of RMSE
(\Program Files\EMC\Replication Manager SE\Docs, by default).
Installing Prerequisite Software on RMSE Hosts and the CLARiiON Array
2-7
Before You Begin
Managing RAID Groups, LUNs, and Storage Groups

This section provides information about:
Configuring RAID
Groups
Configuring RAID groups
Creating LUNs and binding them to RAID groups
Assigning LUNs to the storage groups
In order to configure a CLARiiON array for clone replications using

RMSE, you must create a storage group and assign LUNs to the
appropriate storage group. Perform the following steps:
1. Plan replica storage needs. Consider the following questions:
What data should RMSE replicate?
How large is this data?
How frequently should RMSE replicate this data?
What type of replication best suits these storage needs?
2. Manage RAID groups and LUNs according to your plan.
3. Create storage groups and assign LUNs to the appropriate
storage group.
You can set up RAID groups on the CLARiiON array by following
the steps outlined in the EMC Navisphere Manager Version 6.X
Administrators Guide.
In general, the process to create a RAID group is as follows:
1. Using the Navisphere Manager software, open the Enterprise
Storage dialog box and click the Storage tab.
2. Right-click the icon for the storage system on which you want to
create the RAID group and select Create RAID Group.
Here you can specify the following characteristics of the RAID
group:
RAID group ID
Number of disks in the RAID group
RAID type (RAID 0,1,1/0,3,5)
If you want to specify exactly which spindles to use or specify
other features of the RAID group, click the Advanced button.
2-8
Before You Begin
Creating LUNs and

Binding Them to
RAID Groups
When you store data on a CLARiiON array, the basic unit of storage
is the LUN. RMSE therefore has set the granularity for replicas at the
LUN level as well. This means that you should size the LUNs you
plan to use for clone replicas to exactly the same size as the LUNs you
plan to replicate.
If you have installed VERITAS Logical Volume Manager, granularity is at the
disk level within the volume group level, and all disks in the volume group
are replicated.
Once all the desired RAID groups have been created, you must then
create (or bind) LUNs to the RAID groups as follows:
1. Using the Navisphere Manager software, in the Enterprise
Storage window, click the Storage tab.
2. Right-click the array and select Bind LUN.
3. In the Bind LUN dialog box, click Advanced. You can then
specify the following characteristics of the LUN:
RAID type (choosing from those RAID groups created earlier)
Disk selection method (Automatic or Manual)
Number of disks in the LUN (based on guidelines for RAID
groups)
LUN ID
Element size
Rebuild priority
Verify priority
Service processor ownership
Number of LUNs to bind
It is important to create enough LUNs of the correct size, in the
proper RAID groups to support all the clone replicas of existing data
that you intend to create. See the EMC Navisphere Manager Version 6.X
Administrators Guide for more information about working with
LUNs.
2-9
Before You Begin
2
Assigning LUNs to
the Storage Groups
Once you have created the LUNs that you need for data storage of the
replicas that you plan to make, you must add the LUNs to storage
groups. You will need:
One storage group for LUNs that RMSE can use to create replicas.
Storage groups for each production host (these may already

exist).
Storage groups for each mount host to use (if mounting to a

different host).
You can create storage groups on the CLARiiON array by following

the steps outlined in EMC Navisphere Manager Version 6.X
Administrators Guide.
Creating the RMSE
Storage Group
Before using RMSE, you must use Navisphere to create an RMSE

specific storage group, regardless of the type of replication you will
perform. This storage group is critical to RMSE operation and must
not be deleted. If you are using RMSE for clone and SAN Copy
replications, you must also populate the RMSE storage group with
the appropriate number of LUNs, and each LUN must be the same
size as the source LUN.
Although the RMSE storage group is required in order to perform snapshot
replicas, you do not have to populate the storage group with LUNs if only
performing snapshots.
In general, to create and populate this storage group, follow these

steps in Navisphere:
1. In the Enterprise Storage dialog box, click the Equipment or
Storage tab.
2. Right-click the icon for the storage system on which you want to
create the storage group and select Create Storage Groups.
Specify a storage group name. Although RMSE imposes no
restriction on the name, keep in mind that storage group
names are case-sensitive.
Choose whether LUNs are shared (usually only in clustered
environments).
Add all the LUNs that RMSE is authorized to use for making
replicas of your production data.
Do not connect any hosts to this storage group.
2-10
Before You Begin
If you are using RMSE in a clustered environment, the RMSE storage group is
shared by all nodes within that cluster.
Creating Storage
Groups for Production
Hosts
If you are building a new CLARiiON system, you need to configure

storage groups to define which hosts have access to which sets of
data. In most systems, each production host has access to its own set
of production data, and the LUNs that hold that data reside in that
hosts storage group. By connecting the host to that storage group,
you effectively give the host access to the data on the CLARiiON
array. Refer to the steps in the previous section for information on
how to create a storage group. RMSE requires that each host see only
one storage group per CLARiiON array.
Usually, only one host is attached to each storage group, except in the
case of some clustered implementations.
Creating Storage
Groups for Mount
Hosts
If you plan to mount to a different host, you must create a storage

group for each mount host and add at least one LUN to each of these
storage groups. RMSE automatically populates these storage groups
with the appropriate LUNs after the replicas have been created and
before they are mounted to the mount host.
You may need to reboot the host in order to make the LUNs visible.
2-11
Before You Begin
Preparing CLARiiON Drives for Snapshot Replications

EMC offers two software applications that allow you to create and
manage CLARiiON snapshots: SnapView and Navisphere Manager.
SnapView is a storage-system-based software application that allows
you to create a copy of a LUN by using either clones or snapshots.
Navisphere Manager is a centralized storage-system management tool
for configuring and managing CLARiiON storage systems.
When configuring clone storage, the storage administrator needs to
preallocate dedicated clone LUNs in Navisphere (for example, 2 GB
clone LUNs for each 2 GB LUN). This step is not required when
configuring snapshots. Instead, the administrator must do the
following in Navisphere:
Figure 2-4
2-12
Decide which LUNs are snapshot candidates.
Verify that existing Snapshot cache space exists.
Dedicate enough free LUNs in the Snapshot cache to support the

associated replications. Keep in mind that each source LUN
requires a Snapshot cache LUN on the same SP.
If you plan to use SAN Copy, or choose the option to discard

changes to a clone replica when it is mounted, you are in effect
creating temporary snapshots and should plan on increasing your
Snapshot cache accordingly.
Snapshot Cache LUNs in Navisphere
Before You Begin
Snapshot cache LUNs are shown as either allocated or free in

Navisphere:
Allocated The cache LUN has one or more snapshot sessions

associated with a single source LUN.
Free The cache LUN is not currently associated with any

snapshot sessions for any LUN.
For example, in Figure 2-4, the snapshot cache for storage processor B
(SP B cache) contains 18 LUNs. Five of the 18 total LUNs are currently
being used for snapshot sessions. Five percent of the total cache
storage is being used.
See the EMC SnapView Version 2.X for EMC Navisphere 6.X
Administrators Guide for more information on setting up cache LUNs,
and creating and managing snapshots.
If you attempt to mount, unmount, or restore a replica that has a
session that has been deleted on Navisphere, RMSE informs you that
the replica is no longer valid. At this point, you must expire the
replica.
Important: The frequency at which the original source data changes directly
affects how much cache space is required. If the Snapshot cache fills up to the
point where no cache space is available, the CLARiiON array removes the
session and frees up the data, thus invalidating the replica associated with
the snapshot.
Preparing CLARiiON Drives for Snapshot Replications
2-13
Before You Begin
Preparing CLARiiON Arrays for Full and Incremental SAN Copy

Replications
RMSE can create exact replicas of production data that has been
copied from one CLARiiON array to another CLARiiON array using
EMC SAN Copy software.
RMSE only supports SAN Copy between CLARiiON storage systems.
The term SAN Copy storage system refers to any CLARiiON array that
has SAN Copy software installed. At least one of the storage systems
participating in a Full SAN Copy session must be a SAN Copy
storage system. For Incremental SAN Copy sessions, the source
CLARiiON array must be the SAN Copy storage system.
Complete the following tasks to ensure that the storage systems meet
the requirements for SAN Copy support:
For Full SAN Copy replications, install SAN Copy software on at
least one of the CLARiiON storage systems. For Incremental SAN
Copy replications, install SAN Copy software on the source
CLARiiON array.
Zone the storage systems according to the recommendations in
the EMC SAN Copy Version 2.X for EMC Navisphere 6.X
Administrator's Guide. Also, see the example provided in Zone
SAN Copy Ports.
Use Navisphere to create a SAN Copy storage group on the array
that does not have SAN Copy installed. If both arrays have SAN
Copy installed, you need to create a SAN Copy storage group on
both arrays.
Assign the SAN Copy storage group to the initiator ports of the
remote CLARiiON array. This storage group is used by RMSE to
make LUNs visible to the CLARiiON array; it does not contain
any LUNs.
Verify that at least one LUN is visible to the mount host from the
target array.
Verify that the RMSE Storage Group has been created on the
target array with the appropriate number of LUNs.
2-14
Before You Begin
Verify that there is sufficient snapshot cache space available on

the source array, and in the case of incremental SAN Copy, on the
target array.
See Figure 2-5 for an illustration of these configuration guidelines.
Host 2
Storage
Group
Host 1
Storage
Group
Production
Host
(Host 1)
SAN
EMC
Replication
Storage
CLARiiON Array 1
Figure 2-5
Install SAN Copy

Software on the
CLARiiON(s)
EMC RM
SANCopy
SG
Mount
Host
(Host 2)
EMC
Replication
Storage
CLARiiON Array 2
RMSE SAN Copy Configuration Example
For Full SAN Copy replications, install SAN Copy software on at

least one of the CLARiiON arrays. If SAN Copy software is installed
on only one CLARiiON, we recommend that it be installed on the
source array. However, for the best performance during replication
and restore, we recommend installing SAN Copy on both
CLARiiONs.
For Incremental SAN Copy replications, you must install SAN Copy
software on the source CLARiiON array.
Zone SAN Copy

Ports
SAN Copy ports must be correctly zoned so that SAN Copy can have
access to those systems. Figure 2-6 on page 2-16 illustrates the
recommended SAN Copy zoning method for CLARiiONs that
contain 2 ports (0, 1) per SP.
Preparing CLARiiON Arrays for Full and Incremental SAN Copy Replications
2-15
Before You Begin
0
0
SP A
SP A
1
SAN
1
EMC RM
SANCopy
SG
0
0
SP B
SP B
1
1
CLARiiON Array 1
Figure 2-6
CLARiiON Array 2
SAN Copy Zoning Example

Zone
CLARiiON Array 1 Port
CLARiiON Array 2 Port
SP-A Port 0
SP-A Port 0
SP-A Port 0
SP-B Port 0
SP-B Port 0
SP-A Port 0
SP-B Port 0
SP-B Port 0
SP-A Port 1
SP-A Port 1
SP-A Port 1
SP-B Port 1
SP-B Port 1
SP-A Port 1
SP-B Port 1
SP-B Port 1
As noted previously, this example applies to CLARiiONs that have

two ports per SP. In this case, the recommended zoning method is to
have eight zones to connect CLARiiON Array 1 and CLARiiON
Array 2. If your CLARiiON has 4 ports per SP, you can set up a
similar zoning strategy by configuring additional zones using the
additional ports.
2-16
Before You Begin
If MirrorView is installed on either CLARiiON, the highest port will be

reserved for use with MirrorView, regardless of whether your CLARiiON
arrays SPs have two or four ports. For example, if your CLARiiON array has
MirrorView installed, and the arrays SPs have two ports, you should not
create and use zones 5-8 for SAN Copy (see Figure 2-6, SAN Copy Zoning
Example).
Once the CLARiiON arrays have been properly zoned, use

Navisphere to perform an Update Connections on the SAN Copy
CLARiiON(s).
See the SAN Copy Zoning Requirements section of the EMC SAN Copy
Version 2.X for EMC Navisphere 6. X Administrators Guide for more
information.
Create a SAN Copy

Storage Group
In order to give RMSE access to SAN Copy sessions, you must first
use Navisphere to create a SAN Copy storage group. The SAN Copy
storage group is used to make LUNs visible to the SAN Copy storage
system; it does not contain any LUNs. The CLARiiON array where
this storage group resides depends on the following:
If both CLARiiON arrays have SAN Copy software installed,

create the SAN Copy storage group on both CLARiiON arrays.
If only one CLARiiON array has SAN Copy installed, create the
SAN Copy storage group on the CLARiiON array that does not
have SAN Copy software.
The SAN Copy storage group must have the following name:
EMC RM SANCopy SG
The SAN Copy storage group must be named exactly as shown. In order for
the remote array to have access to the SAN Copy storage group, you must
assign the ports of the remote CLARiiON to it.
Do not associate a host with this storage group.
Preparing CLARiiON Arrays for Full and Incremental SAN Copy Replications
2-17
Before You Begin
2
Connect the SAN
Copy Storage
Group to the
Remote CLARiiON
In Navisphere, configure the SAN Copy connection of the EMC RM

SANCopy SG storage group to the remote CLARiiON by selecting
the ports that were zoned for SAN Copy. For each remote port, use
the Advanced option to select the local ports that were zoned for
SAN Copy.
This step ensures communication between all RMSE production and mount
hosts and the CLARiiON arrays involved in the SAN Copy. It does not need
to be repeated for each host.
2-18
3
Invisible Body Tag
Installing RMSE
This chapter describes how to install and upgrade RMSE for all of
your data replication needs. It includes the following sections:
Installation Overview ........................................................................3-2

Installing RMSE in a Microsoft Cluster Server Environment......3-5
Installing RMSE
3-1
Installing RMSE
Installation Overview
This section explains the software that must be installed in your
environment and describes how to install RMSE so that you can
control the product from your desktop or server machine.
Installing RMSE
To install RMSE:
1. Log in as an administrator on the Windows machine where you
want to install RMSE.
3. Select Install RMSE. The RMSE installation wizard appears.
Click Next.
4. Follow the RMSE installation wizard prompts. You will be asked
for the following information:
Name and company name
Destination location
Complete or Custom installation
If you choose Custom, you have the option to install RMSE
Explorer (GUI) only. This may be a good choice for laptops, or
for systems that run operating systems that are not supported
by RMSE server, such as Windows XP.
Database location
The RMSE database stores information about replication jobs,
replicas, and the storage they use. By default, the database is
stored in the following location:
C:\Program Files\EMC\Replication Manager SE\Data
The RMSE database path cannot exceed 60 characters in length. In a
cluster environment, this limit applies to the actual directory path on
the cluster node, not the virtual directory path.
Since the entirety of RMSE configuration data is stored in this

database, you should strongly consider including the RMSE
database as part of your backup scheme. See Backing Up RMSE
Configuration Data on page 9-4 for more information.
3-2
Installing RMSE
It is recommended that you create a network share of this

RMSE database directory so that it is available from other
hosts on your network. That way, if network connectivity to
the RMSE Server is lost, you will still be able to browse to the
RMSE database directory and display the last known
configuration in RMSE Explorer. See Displaying Information
From a Disconnected Server on page 5-9 for more information.
Path to Java software
5. When the Ready to Install the Program panel appears, click
Install.
If another application uses the same control port or data port as RMSE,
you can change RMSEs default port values by clicking the Advanced
button in the Ready to Install the Program panel. In most cases, you will
not have to change these default port values. If you change the
default control port, be sure to use the new value when
connecting to the server (refer to Working with RMSE Servers on
page 5-1).
Upgrading Previous
Versions of RMSE to
RMSE 3.0.0
To upgrade earlier versions of RMSE to RMSE 3.0.0:

1. Log in as an administrator on the Windows machine where you
want to install RMSE.
2. Exit Replication Manager SE, and verify that no replications or
schedules are running.
4. Select Install RMSE. The RMSE installation wizard appears, and
states that it will update the installed version of Replication
Manager SE to version 3.0.0. Click Next.
5. A confirmation dialog box appears and asks you to confirm the
upgrade, and to verify that you have exited RMSE and that no
replications or schedules are running. Click Yes to proceed.
For information on upgrading earlier versions of RMSE running on
cluster nodes to RMSE 3.0.0, see Upgrading from RMSE 2.1.5 and 2.2.0
on Cluster Nodes on page 3-8.
Installation Overview
3-3
Installing RMSE
3
Modifying or
Removing RMSE
To remove or modify a component of RMSE software, or to remove

RMSE software completely:
1. Log in as an administrator.
2. Click Start and then select Settings > Control Panel.
3. In the Control Panel window, select Add/Remove Programs.
4. Select the operation you want to perform.
Modify Removes an installed component or adds a new
component.
Repair Reinstalls all previously installed components.
Remove Removes RMSE software. You have the option of
preserving the RMSE database. If you choose not to preserve the
database, perform the following steps in RMSE Explorer before
removing the software:
Remove all storage arrays
Expire all replicas
Delete all scheduled tasks
5. Follow the instructions on the screen to complete the chosen
operation.
3-4
Installing RMSE
Installing RMSE in a Microsoft Cluster Server Environment

Overview of MSCS
Support
Replication Manager SE (RMSE) supports Microsoft Cluster Server

(MSCS) running on Windows 2000 and Windows Server 2003. You
should be familiar with basic MSCS concepts such as cluster
resources and resource groups before installing and configuring
RMSE.
RMSE supports multi-node clusters using the active/passive model.
Note the following aspects of RMSE support for MSCS:
On Windows 2003, RMSE supports MSCS server clusters in an

environment of up to eight physical nodes for Microsoft
Exchange, and up to four physical nodes for SQL Server. On
Windows 2000, RMSE supports MSCS server clusters in an
environment of up to four physical nodes for both application
environments.
RMSE server software must be installed on all nodes of the

cluster. Only one of each type of application instance must be
present on each cluster node. For example, a node can have one
Microsoft Exchange instance and one SQL Server instance
installed, but can not have two instances of Microsoft Exchange
installed.
You only need to create one CLARiiON storage group, which will
be shared by all nodes in the cluster.
All nodes in the cluster share the same RMSE database. Therefore,
you only need to perform configuration tasks, such as
discovering storage and applications, on a single cluster node.
Replicas taken by the RMSE software which is running on the

MSCS cluster cannot be mounted back to the cluster. A separate
mount host that is not part of the cluster is required for mounting
the replica.
When running RMSE in a MSCS cluster environment, a separate

host, which can be the mount host but is not part of the cluster, is
required for job scheduling. Using RMSE Explorer, you can create
specialized schedules that reside on this non-cluster host, but run
replications remotely on the cluster production host. Refer to
Creating a Schedule in an MSCS Environment on page 6-15.
3-5
Installing RMSE
3
Installing RMSE on
MSCS
Pre-Installation Steps
for MSCS Support
RMSE allows you to install and configure the RMSE database as a

cluster resource (recommended), or to install the RMSE database to a
shared directory on the cluster. To provide the most complete failover
protection, it is recommended that you install the database as a
cluster resource using the instructions outlined in the Pre-Installation
Steps for MSCS Support section. If you choose not to install the
database as a cluster resource, and simply install it on a shared
directory, you can skip the pre-installation steps and proceed directly
to the Installation Steps for MSCS Support section.
1. Verify that the reverse DNS lookup is configured correctly in the
cluster domain. For each host or virtual instance to which you are
interested in connecting, run the following command:
nslookup <hostname/virtual instance>
Verify that the nslookup command resolves the IP addresses

correctly.
2. Open Cluster Administrator and connect to the cluster.
3. Create a resource group called Replication Manager SE
Database.
4. In this resource group, create the following resources:
IP Address resource (for example, RMSEIPAddress). Ensure you
have a valid IP address that belongs to the same subnet as the
physical cluster.
Network Name resource (for example, with the network name
RMSENetworkName). Make the Network Name resource
dependent on the IP Address resource. If prompted, select the
DNS registration must succeed and Enable Kerberos
authentication options.
Physical Disk resource (for example, L:\) for the cluster shared
disk where the RMSE database will reside. If it does not already
exist on the drive, you will need to create an empty directory, or a
directory that contains a valid RMSE database, such as
L:\RMSEDB.
File Share resource (for example, RMSEDB). Make the file share
resource dependent on both the Network Name resource and the
Disk resource. For the path field enter an existing directory on the
3-6
Installing RMSE
shared disk that you selected in the previous step. Click the
Permissions button and enable full control permissions to the
user who you want to grant access to the RMSE database share.
5. Bring the resource group online and verify that there are no
errors. In Windows Explorer, verify that you can open the path
\\RMSENetworkName\RMSEDB, where:
RMSENetworkName is the value of the Network Name resource,
and
RMSEDB is the value of the File Share resource.
This completes the pre-installation steps, and you can now proceed to
the section Installation Steps for MSCS Support.
Installation Steps for
MSCS Support
1. Install RMSE software on all cluster nodes.

2. When prompted for an installation location, select a path on the
local disk.
3. When prompted to specify the shared folder where setup will
install the Replication Manager SE database, enter:
\\RMSENetworkName\RMSEDB, where:
RMSENetworkName is the value of the Network Name resource,
and
RMSEDB is the value of the File Share resource.
4. Enter the user name, password, and domain name of the user that
you assigned permissions to when defining the File Share
resource in step 4 of the Pre-Installation Steps for MSCS Support
section.
5. Follow the remaining RMSE installation wizard prompts. Repeat
this procedure for all nodes in the cluster.
Once you have completed these steps, RMSE will support the
application on MSCS, and you can start RMSE Explorer and connect
to RMSE using the cluster name. See Creating a Schedule in an MSCS
Environment on page 6-15 for instructions on scheduling jobs in an
MSCS environment, and Restoring a Replica to an MSCS Cluster on
page 8-11 for restoring replicas in an MSCS environment.
3-7
Installing RMSE
3
Upgrading from
RMSE 2.1.5 and 2.2.0
on Cluster Nodes
If you are currently running RMSE 2.1.5 or RMSE 2.2.0 on cluster

nodes, the Installation Wizard automatically upgrades your
configuration to RMSE 3.0. Simply follow the instructions in
Upgrading Previous Versions of RMSE to RMSE 3.0.0 on page 3-3.
During the upgrade from RMSE 2.1.5 or 2.2.0 to RMSE 3.0.0, the Installation
Wizard asks you to specify if this is the first node in the cluster. RMSE
requires this information because the RMSE database must be upgraded on
only one node in your cluster. If you fail to select this option, the RMSE
database will not be migrated correctly and you will have to perform a
manual upgrade of the RMSE database.
When you start RMSE for the first time, you may notice that RMSE
Explorer displays clustered server information differently than in
previous releases. RMSE Explorer now displays clustered server
information cumulatively; it lists the applications, jobs, and storage
arrays that exist on all nodes belonging to that cluster. See Chapter 5,
Working with RMSE Servers for more information on how RMSE
Explorer displays information for clustered servers.
3-8
4
Invisible Body Tag
Getting Started
This chapter describes how to get started using RMSE for all of your
data replication needs. It includes the following sections:
Components of RMSE .......................................................................4-2

Starting RMSE Explorer ....................................................................4-3
RMSE Help..........................................................................................4-8
Getting Started
4-1
Getting Started
Components of RMSE
RMSE includes two software components that work together to
create replicas, mount those replicas, restore replicas, and schedule
replication and other tasks. The components are:
RMSE Server 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 RMSE host.
RMSE Explorer This is the user interface component that controls
the RMSE system from a supported Windows desktop machine or
server.
4-2
Getting Started
Starting RMSE Explorer

This section introduces Replication Manager SE Explorerthe
graphical user interface through which you perform all replica
management tasks. Using RMSE Explorer, you can:
Manage up to five RMSE servers and their associated

applications, storage, and replication jobs
Configure all application and storage arrays for replications
Create, run, and schedule replications
Mount, restore, and expire replicas
Before reading this section, you may want to perform the installation
steps outlined in the previous section. By configuring, installing, and
starting RMSE Explorer, you will be able to follow along on your
system while reading this section.
RMSE help provides in-depth information about the procedures and
interface elements outlined in this section. You can access these
specific help topics from RMSE Explorer by selecting Contents from
the Help menu. Refer to RMSE Help on page 4-8 for more information
about the RMSE online help system.
Launching RMSE
You can launch RMSE Explorer by selecting:

Start > Programs > Replication Manager SE > RM SE Explorer
The Replication Manager SE startup logo appears, followed by RMSE
Explorer, as shown in Figure 4-1 on page 4-4.
4-3
Getting Started
Figure 4-1
RMSE Explorer
The main areas of RMSE Explorer are described below.
Menu Bar Provides access to menus and commands for

RMSE.
Tree Panel Displays all managed objects, and allows you

to expand folders to and work with each application, job,
and storage array.
Target Panel Displays the contents of the selected item.
If RMSE server is not installed, you may be prompted to specify an RMSE

server to which to connect, and to enter a user name (or domain name\user
name) and password.
4-4
Getting Started
RMSE Explorer Menu

Bar
The RMSE Explorer menu bar provides access to the menu

commands. The RMSE Explorer menu bar is shown below.
The specific menu commands are listed next.
File The File menu includes:

Options Allows you to change server-wide options such as
the refresh rate and clone synchronization rate. For more
information, see Refreshing the RMSE Explorer Display on
page 4-7 and Changing the Clone Synchronization Rate on
page 5-8.
Exit Closes all RMSE Explorer windows and exits RMSE
Explorer.
Action The Action menu varies, based on the type of object

that is currently selected. For example, if a CLARiiON array is
selected, the Discover LUNs command is available. Likewise, if a
job is selected, the Schedule command is available.
View The View menu includes commands that allow you to

change how you view folder contents, in much the same way as
Windows Explorer. You can choose from the following views:
large icons, small icons, or list, or details view.
Help The Help menu includes commands that allow you to

access the RMSE online help viewer, and view RMSE copyright
and version information.
Some menus and commands appear only for specific views in the
active target panel.
RMSE Explorer Tree

Panel
The tree panel displays all of the objects that you can manage in the
RMSE environment, grouped according to type. You can expand
folders through these groups and their data to display details about
individual objects. The top-level object types include:
Managed Servers The top-level object that contains all

manageable objectsservers, applications, volumes, jobs, and
storage arrays.
RMSE Servers The clustered and standalone RMSE servers

that have been configured to work with RMSE. Each RMSE host
can manage up to five servers, including one virtual cluster
server.
4-5
Getting Started
Applications Contains a list of all applications that are

available to RMSE (Exchange, SQL Server, and Volumes).
Jobs Contains a list of all replication jobs and their associated

replicas and schedules.
CLARiiON Arrays Contains a list of all CLARiiON arrays

(and their associated LUNs) that have been configured to work
with RMSE.
Each of these top-level objects expands to reveal successive levels of

details, and additional manageable objects. When you expand
clustered servers in the RMSE Explorer tree panel, RMSE provides a
cumulative list of all manageable objects in the cluster. For example,
when you expand the Jobs folder for a clustered server, RMSE
displays all jobs that exist on each node in the cluster.
Figure 4-2 shows two versions of a sample tree panel. On the left, no
folders are expanded. On the right, all folders are expanded.
Figure 4-2
4-6
Sample Tree Panels
Getting Started
Tree Panel Actions
Most tasks available through the RMSE main menu can also be
performed through the context menu that appears when you
right-click an object in the tree panel. The content of the context menu
varies, based on the type of object you right-click.
Figure 4-3 shows the context menu for an individual storage array.
Figure 4-3
Sample Context Menu

The procedures in this guide that involve tree panel objects are usually
explained in steps that reference the right-click menu. In many cases, there
are multiple ways to perform the same procedure, such as using the
commands available in the menu bar.
Target Panel Actions
In the previous section, you learned that you can perform actions by
right-clicking objects in the tree panel. You can perform most of these
actions by right-clicking objects in the target panel as well.
Refreshing the RMSE

Explorer Display
To refresh the RMSE Explorer display manually:
Select Refresh from the View menu.
See Changing the Automatic Refresh Rate on page 5-8 for more
information on configuring RMSE to refresh the display
automatically.
4-7
Getting Started
RMSE Help
RMSE provides a comprehensive HTML-based Help system. RMSE
Help allows you to:
Receive background information on key RMSE concepts. This

information complements, but does not replace, the information
in this guide.
Obtain procedural information and explanations for dialog boxes

and windows that you are currently using.
Use What's This? help to display definitions of dialog box fields

and buttons.
There are several ways to access Help from RMSE Explorer.
RMSE Help Types
4-8
To view...
Select the...
Help table of contents
Contents command from the Help menu, or

press F1 and select the Contents tab.
Help index
Index command from the Help menu, or press F1

and select the Index tab.
Help full text-search
Search command from the Help menu, or press

F1 and select the Search tab.
Help for any dialog box control
What's This? help button on the dialog box, and

then select the control for which you want help.
RMSE Help consists of two main types of help topics: task help topics
and Whats This? help topics. Task help topics consist of how-to,
step-by-step procedures that provide explicit instructions on which
commands to choose, what to type in a dialog box, the options to
select in a dialog box, and so on. Whats This? help topics are concise
descriptions of window and dialog box components.
Getting Started
Using the RMSE Help

Viewer
Select Contents from the Help menu to display the RMSE help
viewer. The main components of the help viewer are shown in
Figure 4-4.
Search
Index
Toolbar
Table of
Contents
Topic
Book
Topic
Pane
Navigation
Pane
Figure 4-4
RMSE Help Viewer
The help viewer consists of a toolbar and two panes:
Navigation pane The frame on the left with a tabbed interface

that allows you to switch between the table of contents, index,
and full text search views. Displays the table of contents, the
index, or the full-text search feature (Search), depending on what
you selected the last time you displayed the help file.
Topic pane The frame on the right that displays help topics.
RMSE Help
4-9
Getting Started
4
Using the Help Table
of Contents
Figure 4-5
Click the Contents tab in the Navigation pane to display the table of
contents tree.
Help Table of Contents

To display a help topic using the Table of Contents
1. Click the Contents tab in the Navigation pane.

2. Double-click a book to expand the next lower level of topics and
books.
3. Click the topic that you want to display. The selected topic
appears in the Topic pane.
4-10
Getting Started
Using the Help Index
Figure 4-6
Click the Index tab in the Navigation pane to display the keyword
index.
Help Index
To find and display a help topic using the Index
1. Click the Index tab in the Navigation pane.

2. Scroll through the list of keywords, and click the desired keyword
to display the associated topic in the Topic pane.
You can also type the first few letters of a keyword for which you want to
search. The keyword list scrolls to the relevant keywords as you type.
RMSE Help
4-11
Getting Started
4
Using the Help Search
Figure 4-7
Click the Search tab in the Navigation pane to display the full-text
search feature.
Help Search
To find and display a help topic using Search
1. Click the Search tab in the Navigation pane.

2. Type the word or phrase for which you want to search in the Find
field and press ENTER (or RETURN). Matching topics appear in the
topics list, sorted by relevance.
3. Click the topic that you want to display from the search results.
The topic appears in the Topic pane.
For more information on how to use the online help system, see the
Using Help topics of RMSE Help.
4-12
5
Invisible Body Tag
Working with RMSE

Servers
This chapter describes how to use RMSE Explorer to effectively

manage one or more servers in your replication environment. It
includes the following sections:
Adding RMSE Servers to Your Managed Environment...............5-2

Viewing and Modifying Individual Server Properties .................5-5
Viewing and Modifying Server-Wide Properties ..........................5-8
Displaying Information From a Disconnected Server ..................5-9
5-1
Adding RMSE Servers to Your Managed Environment

Before creating a replication, you must first add one or more RMSE
Servers to your storage environment so that they can be managed in
RMSE Explorer. An RMSE Server can be the local machine, or any
other machine that is running RMSE server software.
If there are no RMSE Servers configured in RMSE Explorer, for
example, when you start RMSE Explorer for the first time, the default
Add Server panel appears.
Figure 5-1
5-2
Add Server Panel
Adding RMSE
Servers
Figure 5-2
To add one or more RMSE servers to your managed environment:

1. Right-click Managed Servers in the RMSE Explorer tree panel
and select Add server from the context menu. The Connect dialog
box appears.
Connect Dialog Box
2. Specify the name of the RMSE Server to which you want to

connect, and the user name and password of an account with
Administrator privileges on that host.
In a cluster environment, specify the cluster name in the Server field of
the Connect dialog box. RMSE Explorer will automatically display
applications, jobs, and storage arrays that exist on all nodes belonging to
that cluster. See Figure 5-6 on page 5-7 for help with locating the cluster
name in Microsoft Cluster Administrator.
3. Optionally, if you changed the default control port number

during installation, you need to select the different port number
link and specify that port number in the Select Port Number
dialog box.
Figure 5-3
Select Port Number Dialog Box
Adding RMSE Servers to Your Managed Environment
5-3
5
You can add up to five RMSE Servers to your managed environment,
including one Microsoft Cluster Server. RMSE saves this information
for you automatically, and displays all previously configured Servers
the next time you start RMSE Explorer.
You can distinguish standalone servers from clustered servers in
RMSE Explorer by the type of icon used in the tree panel.
Clustered
Server
Stand-alone
Server
Figure 5-4
Server Types in RMSE Explorer
In the figure above, notice that the clustered RMSE Server contains
multiple instances of the Microsoft Exchange application. For
clustered servers, RMSE displays information cumulatively; it lists
the applications, jobs, and storage arrays that exist on all nodes
belonging to that cluster.
The information that displays in the server summary is also
dependent on server type. For standalone servers, when you select
Managed Servers in the RMSE Explorer tree panel, and then select
View > Details, RMSE provides you with the name, Windows
platform, and the latest job status for that RMSE server. For clustered
servers, RMSE displays the cumulative job status of all nodes that
belong to the cluster.
The Managed Servers Detailed view is the default view when you start
RMSE.
5-4
Viewing and Modifying Individual Server Properties

RMSE Explorer allows you to view and, in some cases, modify the
properties of previously configured Servers. To view the properties of
an individual RMSE Server, right-click the desired Server in the
RMSE Explorer tree panel and select Properties from the context
menu.
The following RMSE Server properties are displayed:
RMSE Server name and type (software version)
Windows platform and version
Java path
Log level and advance log options
On clustered RMSE Servers, the additional information is also

displayed:
Changing the Java

Path
Username and password to use when connecting to the shared

RMSE database
List of virtual hosts in the cluster and their connection status
During installation, RMSE automatically detected your installation of

the Java Runtime Environment. If you make any changes to your Java
installation, or for any reason you need to change this path, you can
do so in the Server Properties page.
To change the Java path:
1. Right-click the desired Server in the RMSE Explorer tree panel
and select Properties from the context menu.
2. Enter the path to your Java Runtime Environment installation. By
default, the path will be similar to the following:
C:\Program Files\Java\j2re1.4.1_05\bin\
5-5
5
Changing the Log
Level
You can configure the severity of messages that are logged in the
RMSE log files, and the maximum size of the RMSE log directory.
To change the log level:
1. From the RMSE Explorer tree panel, right-click the RMSE server
2. On the General tab, select the desired log level:
None No messages are written to the log file.
Normal Only important messages are written to the log file.
Debug All messages are written to the log file.
3. Optionally, click the Advanced button to specify the maximum
log directory size (50-1000 MB).
Viewing a List of All

Virtual Nodes in the
Cluster
If you are running RMSE on a clustered server, you can use RMSE
Explorer to view a list of all virtual nodes in that cluster.
To view a list of all virtual nodes in the cluster:
1. From the RMSE Explorer tree panel, right-click the RMSE Server
2. Click the Cluster tab to view a list of all virtual nodes in that
cluster, as shown below.
Figure 5-5
5-6
Cluster Nodes in Server Properties
Notice that RMSEs list of cluster nodes is the same list you would
see if you expanded the clusters Groups directory in Microsoft
Cluster Administrator.
Cluster name to specify

when connecting to RMSE
Figure 5-6
Cluster Nodes in Microsoft Cluster Administrator
5-7
Viewing and Modifying Server-Wide Properties

You can also use RMSE Explorer to view and modify several
Server-wide configuration options. To view all Server-wide
configuration options, select Managed Servers in the RMSE Explorer
tree panel and then select File > Options.
The following Server-wide options can be changed:
Changing the Clone

Synchronization
Rate
Clone synchronization rate
Automatic refresh rate
RMSE allows you to adjust the clone synchronization rate for each
RMSE server that you have added to your replication environment.
The default synchronization rate is High. You may need to lower this
setting if you are using a lower-end CLARiiON model.
To change the clone synchronization rate:
1. Select Options from the File menu. The Options dialog box
appears.
2. On the Clone tab, select High (default), Medium, Low, or Default
next to the RMSE server for which you want to change the
synchronization rate. If you choose Default, RMSE will use the
synchronization rate that is specified in Navisphere for the clone
group.
Changing the
Automatic
Refresh Rate
To configure RMSE Explorer to refresh the display automatically:

1. Select Options from the File menu. The Options dialog box
appears.
2. On the Refresh tab, select the Refresh after every x minutes
option, and enter the desired refresh interval (1-10,000 minutes).
5-8
Displaying Information From a Disconnected Server

When you installed RMSE, Setup asked you to specify the directory
where the RMSE database will be stored. It is recommended that you
create a network share of this RMSE database directory so that it is
available from other hosts on your network. If for any reason
network connectivity to the RMSE Server is lost, and the RMSE
database is accessible from another host (via cluster or shared
directory), you can browse to the RMSE database directory and
display the last known configuration in RMSE Explorer.
To display the last known configuration of a disconnected server:
1. Right-click the disconnected cluster server
and select Browse
database from the context menu. The Browse Database dialog
box appears.
Figure 5-7
Browse Database Dialog Box
2. Enter the name and login information for the surrogate host
through which you want to display the latest configuration of the
disconnected Server. The surrogate host must have RMSE Server
software installed.
3. Enter the UNC path to the shared directory where the
disconnected RMSE Servers database resides in the Database
Path Folder field.
Displaying Information From a Disconnected Server
5-9
5-10
6
Invisible Body Tag
Using Jobs to Create

Replicas
This chapter describes how to create replicas using RMSE jobs. It

includes the following topics:
Working with Jobs..............................................................................6-2

Copying a Replica ............................................................................6-17
6-1
Working with Jobs

RMSE provides replication jobs to designate the production data to be
replicated, and to define the associated replication actions to perform
on this data. For each job, you can define a unique replication
process.
Each job specifies how to:
Creating a Job
Handle the production data before and after replication.
Select the storage that may be used for the replica.
Manipulate the replica after it has been created.
Automatically expire the replica after the maximum number of

replicas for that job has been exceeded.
To create a job:
1. Using RMSE Explorer, right-click an application object (such as
Volumes, Microsoft SQL Server, or Microsoft Exchange) and
select Create Job. The Create Job Wizard welcome screen appears.
Click Next.
6-2
2. Enter a name and description for the job.
Do not use the following characters in the job name:

&:<>"'/\*?|!
Click Next.
3. Select the replica type and maximum number of replicas.
Working with Jobs
6-3
6
RMSE automatically expires this job's replicas based on the
number that you specify in the Maximum Number of Replicas
field. If the number of replicas for this job reaches that number,
RMSE expires this job's oldest replica when it starts the next run
of the job. The default maximum number of replicas for a job is
two.
If you select the SAN Copy replica type, specify the target storage
array, and whether you want to create a Full or Incremental SAN
Copy replica. See Supported Replications on page 1-9 for more
information on the differences between Full and Incremental
SAN Copy, and Preparing CLARiiON Arrays for Full and
Incremental SAN Copy Replications on page 2-14 for more
information on configuring your RMSE storage environment for
EMC SAN Copy.
Click Next.
4. Select the application whose components you want to replicate,
and then mark each individual component that you want to
replicate.
For SQL Server replication jobs, if multiple databases reside on the same
source LUN, be sure to select all of the databases on that LUN.
Click Next.
6-4
5. For Exchange 2003 replicas, select a replica type.
Online Full creates and stores a complete copy of all the

storage group databases, transaction logs, and checkpoint files
while the Exchange server is online. It also truncates the
transaction log files up to the most recent checkpoint. If you
choose this option, RMSE mandates that you also select to
mount the replica and run ESEUTIL.
Online Copy creates and stores a complete copy of all the
storage group databases, transaction logs, and a checkpoint
file while the Exchange server is online. The transaction files
are not truncated.
Offline dismounts the Exchange storage group prior to the
replication and remounts them after the replica is created. The
transaction logs are not truncated.
WARNING
RMSE restores occur at the physical disk (LUN) level. Any other
data that resides on the disk will be overwritten. When restoring
Exchange and SQL Server replicas, make sure that you select all
databases for restore that reside on the affected disk (LUN).
Working with Jobs
6-5
6
6. Click Advanced on the Replication Options for Microsoft
Exchange panel to access Microsoft Exchange advanced options.
Figure 6-1
Exchange Advanced Options Dialog Box
By default, RMSE fails a Microsoft Exchange job if it detects any

of the following errors in the event log:
JET Read/Verify Error (-1018)
JET Page Not Initialized Error (-1019)
JET Disk I/O Error (-1022)
You can configure RMSE to bypass one or more of these errors
and continue with the replication by clearing the checkboxes of
the desired errors in the Exchange Advanced Options dialog box.
It is recommended that you always check for -1018 errors. If you
want to ignore all of these errors for the next run of the job only,
select Ignore all errors for the next run only.
During the initial run of a job, RMSE scans the entire Event log for the
selected -10xx errors. During subsequent runs of the job, RMSE scans the
Event log only from the point of time since the jobs last successful
replication.
Click OK to dismiss the Exchange Advanced Options dialog box,

and click Next to proceed with the Create Job Wizard.
6-6
7. For Exchange 2000 and 5.5 replicas, choose whether you want
RMSE to truncate the log files after the replication. Also, if you
want an offline copy of the Exchange storage groups or stores,
disable the Perform hot split (online) replication check box.
When the job runs:
Exchange 2000 storage groups will be dismounted during
replication and remounted at the end of the job.
Exchange 5.5 services will be stopped and then restarted.
Click Next.
8. Specify whether you want to mount the replica.
You must select the Mount replica option for all Exchange 2003 Online Full jobs. In addition, RMSE automatically runs ESEUTIL for Exchange
2003 jobs, and fails these jobs if ESEUTIL fails (see step 9).
You can mount the replica locally or on a remote host. On a

remote host, you can mount to the original location or to a new
location. If you mount locally (to the production host), you must
mount to an alternate location.
Working with Jobs
6-7
6
You can also use this panel to unmount the replica on job
completion, and to set the following mount options:
Read-only to prevent any changes to be made to the volume.
This option is available for both snapshot and clone replicas
on Windows 2003 only.
Read-write if you want to allow changes to be made to the
volume.
Read-write, discard changes on unmount if you want RMSE
to discard any changes that you make to the replica while its
mounted. Available for clone replicas only, this option
essentially creates a snapshot of the clone replica, and mounts
the snapshot instead of the clone. When mounted, the volume
can be changed, but the changes are discarded when the
volume is unmounted. You may need to allocate sufficient
snapshot cache space if you select this option. Refer to
Preparing CLARiiON Drives for Snapshot Replications on
page 2-12.
Even with this option enabled, Windows can make changes to the
disk signature, but RMSE will restore the original disk signature.
9. Click Advanced on the Mount Options panel to specify metadata

file and ESEUTIL options.
Figure 6-2
6-8
Advanced Mount Options Dialog Box
Microsoft requires that ESEUTIL be run when an Exchange 2003 VSS full
replica is created. The utility is run before logs are truncated. If ESEUTIL
fails, the logs are not truncated.
The Metadata Location field allows you to specify the location on

the mount host where you want RMSE to copy the metadata files
associated with SQL Server or Exchange 2003 VSS replicas. This
option is required if you plan to back up replicas to tape. See
Restoring Replicas from Tape Backups on page 8-13 for more
information.
The location of metadata files can only be specified for Exchange 2003
replications on Windows Server 2003, and for SQL Server replications (all
Windows versions).
If you chose to mount the replica to an alternate location, RMSE

displays this alternate path in the Metadata Location field.
Otherwise, this option is left blank by default, and RMSE will not
copy metadata files after it mounts the replica.
As part of Microsoft Exchange replication jobs, RMSE
automatically runs the ESEUTIL utility (ESEFILE utility on
Exchange 5.5) and fails the replication job if the ESEUTIL fails.
ESEUTIL checks the consistency of the Exchange databases. If the
ESEUTIL check fails, the replica is corrupt. By default, RMSE
searches for ESEUTIL in the Exchange install path and the system
path. You can choose to run ESEUTIL from a different location, or
choose to not run ESEUTIL on the replication, by changing the
options in this dialog box.
See the Whats This? help for more information on these options,
and Chapter 8, Working with RMSE Replicas, for information on
mount host requirements.
Click OK to dismiss the Advanced Mount Options dialog box,
and click Next to proceed with the Create Job Wizard.
Working with Jobs
6-9
6
10. Enter the names of the pre- and post-replication scripts to run on
the production host. If this job also mounts the replica, specify the
name of the post-mount script, and whether you want to fail the
replication job if the post-mount script fails.
11. Review the job summary.
Click Back if you want to make any changes to your

configuration. Otherwise, click Finish. If you want to schedule
the job, click Schedule. Refer to Scheduling a Job on page 6-12.
You have successfully created a replication job. The job will run at the
time you scheduled. You can also run the job on demand.
6-10
Running a Job
To run a replication job on demand:

1. In RMSE Explorer, expand the Jobs folder in the tree panel.
2. Right-click the job you want to run and select Run. You can
continue to work with RMSE Explorer while the job is running.
When you create a clone replica for the first time, a full establish is
performed, which can take a long time.
The progress window shows the status of the replication job.
Figure 6-3
Run Job Progress Panel

The replica is named according to the time when the job was started, not the
actual split time of the replica.
Working with Jobs
6-11
6
Viewing Job Status
Figure 6-4
Cancelling a
Running Job
You can view the current job status of running jobs (or last run status
for completed jobs) by selecting the Jobs folder in detailed view.
Viewing Current Job Status
To cancel a running job, click Cancel on the Run Job progress panel.
A request to cancel will not take effect if the operation has proceeded too far.
A message in the progress window informs you if the cancel request could
not be fulfilled.
Scheduling a Job
Schedules allow you to run replication jobs at a predetermined date

and time. Each schedule is associated with a specific job. To schedule
a job:
1. Click the Schedule button on the Summary panel of the Create
Job wizard, or right-click a specific job in the RMSE Explorer tree
panel and select Schedule.
6-12
In both cases, the Schedule Job dialog box appears:
Figure 6-5
Schedule Job Dialog Box
2. Name the schedule and indicate:

How frequently you want the job to run.
The time of day and a date range in which to run the job.
Do not use the following characters in the schedule name:
&:<>"'/\*?|!
See the Whats This? help for more information on the individual
fields of the Schedule Job dialog box.
Working with Jobs
6-13
6
Scheduling a Job on a
Remote Host
By default, RMSE creates the schedule on the host to which you are
currently connected. To create the schedule on a different host:
1. Follow the steps outlined in Scheduling a Job on page 6-12.
2. Click the here link near the top of the Schedule Job dialog box.
The Connect dialog box appears.
Figure 6-6
Connecting to a Remote Schedule Host
3. Enter the name of the desired remote schedule host. You will also
need to provide the name and password of a user with
administrative rights on that host. If you want to specify a
domain in addition to the user name, use the following format in
the Username field:
domain\username
RMSE records remote schedule (5045) events to the Windows Event
Viewer of the remote schedule host, not to the host on which the
replication job is run. See RMSE Event Messages on page 9-13 for more
information.
6-14
Creating a Schedule
in an MSCS
Environment
In order to provide the best failover protection, schedules for

replication jobs that run on a virtual cluster server must be stored on
and run from a remote host that resides outside of the cluster. This
scheduling host can be the mount host, or any other host that has
RMSE installed, as long as it is not part of the cluster.
To schedule a job in an MSCS cluster environment, follow the
instructions for scheduling a job on a remote host in the preceding
section. Remember to install RMSE on the scheduling host (the
remote host that is not part of the cluster).
Modifying a Job
To modify a job:
1. Expand the Jobs folder in the RMSE Explorer tree panel.
2. Right-click the desired job and select Properties to display the Job
Properties window. All options that you previously configured in
the Create Job Wizard can be modified in this dialog box. The
following example shows the General properties of an Exchange
replication job.
Figure 6-7
Job Properties Window
Working with Jobs
6-15
6
Deleting a Job
You must expire all replicas associated with a job before you can
delete the job.
To delete a job:
2. Right-click the specific job and select Delete. Verify that you want
to delete the job.
6-16
Copying a Replica
RMSE allows you to create specialized jobs (copy jobs) to copy a
replica to a different storage array using EMC SAN Copy software.
You can create a copy job of any existing Clone or Snap job.
To create a copy job:
1. Using RMSE Explorer, right-click the Jobs folder and select Create
Copy Job. Alternatively, you can right-click the job whose replica
you want to copy and select Create Copy Job. Regardless of
which method you choose, the Create Copy Job Wizard welcome
screen appears.
Click Next.
2. Enter a name and optional description for the copy job and click
Next.
Do not use the following characters in the job name:
&:<>"'/\*?|!
Copying a Replica
6-17
6
3. Select the CLARiiON storage array to which you want to copy the
replica, and specify the maximum number of replicas.
Click Next to continue.

4. Select the source job that you want to copy to the target array.
6-18
Also, choose whether RMSE should copy the oldest or latest

replica of the source job. You can also specify that RMSE run this
copy job every time the source replication job successfully
completes by selecting Run this copy job every time the source
job runs. (If the option is grayed out, it means there is already a
copy job associated with the selected source job.) Click Next to
continue.
5. Specify whether you want to mount the replica copy.
You can mount the replica locally or on a remote host, and you
can mount to the original location or to a new location. If
mounting to the production host, be sure to specify a new
location. You can also use the options in this panel to:
Mount the replica copy as read-write or read-only
Mount the replica copy as read-write, but discard changes to
the replica while it is mounted
Unmount the replica copy upon job completion
See the Whats This? help for more information on these options.
Click Next to proceed with the Create Copy Job Wizard.
6. Enter the names of any pre- and post-replication scripts that you
want to run on the production host. If this job also mounts the
replica, specify the name of the post-mount script, and whether
you want to fail the replication job if the post mount script fails.
Click Next to continue.
Copying a Replica
6-19
6
7. Review the job summary.
Click Back if you want to make any changes to your

configuration. Otherwise, click Finish. If you want to create a
schedule for the job, click Schedule. Refer to Scheduling a Job on
page 6-12.
A copy job can have its own schedule, but you should not schedule a copy job
to run at the same time as its source job.
Copy jobs use Full SAN Copy replications to copy existing Clone or Snap
replicas to a different storage array. You cannot create incremental copies
using copy jobs.
6-20
7
Configuring RMSE
Storage and
Applications
This chapter describes how to configure storage and applications for

use with RMSE. It includes the following topics:
Discovering Storage...........................................................................7-2
Discovering Applications .................................................................7-6
7-1
Discovering Storage
Adding Storage
To update RMSE Explorer so it displays newly added storage:

1. Right-click CLARiiON Arrays in the tree panel and select Add
Storage. The Add Storage Wizard welcome panel appears. Click
Next.
2. Indicate if you want RMSE to look for new storage arrays, or if
you want to enter the names of the storage arrays to add. Click
Next.
3. Specify the storage arrays that you want to add by entering their
names or selecting them from the Discovered Storage Arrays list.
Click Next to display the Add Storage Wizard configuration
panel.
Figure 7-1
Add Storage Wizard
4. Enter configuration information for the new array, including:

Login information.
Name of the CLARiiON storage group that you created
containing clone LUNs (refer to Creating the RMSE Storage
Group on page 2-10).
7-2
Performance options, including:

Maximum Snaps sets the maximum amount of
snapshot replications to dedicate to RMSE on this
CLARiiON array.
SAN Copy Session Throttle sets the I/O rate for a SAN
Copy session.
SAN Copy Link Utilization sets the bandwidth for
incremental SAN Copy sessions using either Fibre Channel
or IP network configurations.
If you want RMSE to find the LUNs on this array that were
allocated for this host, click Discover LUNs.
For more information on any of these options, see the Whats This?
help. Click Next to continue.
5. Examine the summary. Click Back if you want to make any
changes to your configuration. Otherwise, click Finish.
Modifying Storage
Properties
To modify storage properties:

1. Expand CLARiiON Arrays in the tree panel.
2. Right-click an individual array and select Properties. The Storage
Properties window appears.
Figure 7-2
Storage Properties Dialog Box

Discovering Storage
7-3
7
3. Make the desired changes to any of the following array properties
and click OK:
SP A and SP B IP addresses, and associated Clone LUN
storage group (General tab).
User name and password of the user as whom you want to
connect to the storage array (Login tab).
Performance options, including the maximum number of
snaps allowed for RMSE (Performance tab). This tab also
includes two SAN Copy performance options: SAN Copy
Session Throttle and SAN Copy Link Utilization. RMSE uses
these options to control the I/O rate for a SAN Copy session
and the bandwidth for incremental SAN Copy sessions using
either Fibre Channel or IP network configurations.
Figure 7-3
Storage Performance Options
See the Whats This? help for more information on individual

storage properties.
Do not make changes to the storage group or SP information until you
have prepared the new storage and expired any replicas on the old
storage.
7-4
4. Select the array and run Discover LUNs to update the RMSE
database.
Discovering LUNs
Whenever you add a storage array, or make changes to a storage

array (for example, moving LUNs between storage groups), you
should discover the LUNs on that array.
To discover LUNs:
1. Expand CLARiiON Arrays in the tree panel.
2. Right-click an individual array and select Discover LUNs. The
Discovered LUNs Progress panel appears.
3. When RMSE finishes LUN discovery, click OK.
Discovering Storage
7-5
Discovering Applications
To find applications, databases, volumes, or other objects that are not
listed in RMSE Explorer:
1. In RMSE Explorer, right-click Applications and select Discover.
The Discover Applications Wizard appears. Click Next.
2. Wait a moment while Explorer searches for new applications.
When the search is complete, all applications are listed.
Figure 7-4
Discover Applications Wizard
3. Select the check boxes of all applications that you want to

configure. By default, RMSE automatically selects applications
that are not yet configured.
4. Enter authentication information for the application. You need to
provide a user name (with domain if appropriate) and password.
For SQL Server, you also need to indicate the type of the account
with which you are logging in (SQL Server login account or
Windows domain account).
changes to your configuration. Otherwise, click Finish.
See the Appendices at the end of this guide for information on using
RMSE with Microsoft Exchange, SQL Server, and NTFS volumes.
7-6
8
Invisible Body Tag
Working with RMSE

Replicas
This chapter describes how to work with RMSE replicas. It includes

Viewing Replica Properties...............................................................8-2

Expiring Replicas ...............................................................................8-3
Mounting a Replica............................................................................8-4
Restoring a Replica ............................................................................8-8
Restoring Replicas from Tape Backups.........................................8-13
8-1
Viewing Replica Properties

To view replica properties:
1. Using RMSE Explorer, expand the job containing the replica
whose properties you want to view.
2. Right-click the replica and select Properties. The Replica
Properties screen appears.
Figure 8-1
Replica Properties Dialog Box
3. Select the General tab to view basic information about the replica,
such as the replica name (as a date), state, and replication type.
4. Select the History tab to display a time-stamped view of all past
activities associated with this replica, including replication,
mount, unmount, restore, expire, and import. If you want to filter
the list to show only the most important activities, click Show
Summary. To return to the complete list, click Show Details.
Alternatively, you can view an individual replicas job history by
selecting the replica in the RMSE Explorer tree panel while in
Details view. The replica history displays in the right target panel,
which can be resized to accommodate message length.You can
summarize the list of messages by selecting View > Show
Summary, and return to the full message list by selecting View >
Show Details.
8-2
Expiring Replicas
Expiring a Replica
Automatically
RMSE automatically expires a particular job's replicas based on the

number specified in that job's Maximum Number of Replicas field. If
the number of replicas for that job reaches the specified maximum
value, RMSE expires the job's oldest replica when it starts subsequent
runs of the job.
To adjust the maximum number of replicas for a job, allowing RMSE
to automatically expire that job's replicas:
2. Right-click the desired job and select Properties from the context
menu.
3. Select the Replication tab.
4. Enter a new value in the Maximum number of replicas field, or
use the up/down buttons to adjust the existing value. The default
maximum number of replicas is two.
Expiring a Replica
on Demand
Although RMSE automatically expires a particular job's replicas

based on the number specified in that job's Maximum Number of
Replicas field, you can also expire replicas on demand.
To expire a replica on demand:
2. Expand the job containing the specific replica you want to expire.
3. To expire a single replica, right-click the replica and select Expire.
To expire multiple replicas, select them from the target panel
(right side), then right-click and select Expire selection.
4. Verify that you want to expire the replica(s).
Expiring Replicas
8-3
Mounting a Replica
To mount a replica on demand:
1. In the RMSE Explorer tree panel, expand the job containing the
replica you want to mount.
2. Right-click a replica and select Mount. The Mount Replica dialog
box appears.
Figure 8-2
Mount Replica Dialog Box
3. Enter the name of the mount host and the mount path, or use the
down arrows to choose from the last five most recently used
mount hosts and paths. RMSE server software must be installed
and running on the mount host.
8-4
The following examples demonstrate where a replica of Z: would

be mounted, based on the value you specify for the Mount Path
field:
Mount at Value
Result
Requirements
X:\
X:\Zdrive
X: must exist. If Zdrive

already exists, it must be
empty.
X:\mnt1
X:\mnt1\Zdrive
X: must exist. If mnt1

already exists, it must be
empty. If mnt1 does not
exist, RMSE creates it. If
Zdrive already exists, it
must be empty.
Likewise, the following examples demonstrate where a replica of

a mount point on Z: called EXCHSG1 would be mounted:
Mount at Value
Result
Requirements
X:\
X:\Zdrive\EXCHSG1
X: must exist. If Zdrive

already exists, it must
be empty.
X:\mnt1
X:\mnt1\Zdrive\EXCHSG1 X: must exist. If mnt1
already exists, it must

be empty. If mnt1 does
not exist, RMSE creates
it. If Zdrive already
exists, it must be empty.
Production mounts of dynamic disk groups, and production mounts in a
cluster environment, are not supported.
When you mount the replica of a volume that is in a volume group, you
will mount all the volumes in the volume group, regardless of whether
they are part of the job.
4. Select one of the following mount options.
Mounting a Replica
8-5
8
Read-only to prevent any changes to be made to the volume.
This option is available for both snapshot and clone replicas
on Windows 2003 only.
Read-write if you want to allow changes to be made to the
volume.
Read-write, discard changes on unmount if you want RMSE
to discard any changes that you make to the replica while its
mounted. Available for clone replicas only, this option
essentially creates a snapshot of the clone replica, and mounts
the snapshot instead of the clone. When mounted, the volume
can be changed, but the changes are discarded when the
volume is unmounted. You may need to allocate sufficient
snapshot cache space if you select this option. Refer to
Preparing CLARiiON Drives for Snapshot Replications on
page 2-12.
Even with this option enabled, Windows can make changes to the disk
signature, but RMSE will restore the original disk signature.
5. Click OK to mount the replica. The progress window shows the

status of the replication job.
Figure 8-3
Mount Replica Progress Panel

RMSE saves the mount options that you specify and uses these options as the
default for the next on demand mount.
8-6
See the Appendices at the end of this book for specific mount
requirements for Exchange, SQL Server, and NTFS volumes.
Mount Host
Requirements for
MSCS Cluster
Replicas made by RMSE on an MSCS cluster cannot be mounted back

on any node of the cluster. They must be mounted on a host outside
of the MSCS cluster. It is recommended that you set up another
machine outside of the MSCS cluster to be the mount host and
scheduler host. The requirements for the mount host are the same as
those for the production host.
Mounting a Replica
8-7
Restoring a Replica
To restore a replica:
1. In RMSE Explorer, expand the job containing the replica you want
to restore.
2. Right-click the replica you want to restore and select Restore. The
Restore Wizard appears. Click Next.
Figure 8-4
Restore Wizard
WARNING
RMSE restores occur at the physical disk (LUN) level. Any other
data that resides on the disk will be overwritten. When restoring
Exchange and SQL Server replicas, make sure that you select all
databases for restore that reside on the affected disk (LUN).
8-8
3. Select the items you want to restore. The preceding example

shows the options for restoring an Exchange 2003 replica. The
Restore Wizard warns you if any logical entities are affected by
your selection (for example, if other databases, logs, or volumes
reside on the same LUN as the item you have selected).
If you select Yes, RMSE will select all affected entities for you
automatically.
4. If you are restoring an Exchange 2003 database on Windows 2003,
and you want to recover and mount the databases after the
restore, click Recovery Options. The Recovery Completion State
dialog box appears.
Select Recover and Mount databases and then click OK. For
more information on restoring Exchange databases, see
Appendix A, Microsoft Exchange Procedures.
Restoring a Replica
8-9
8
5. If you are restoring a SQL Server database, and want to change
the default recovery option, click Recovery Options. The
Recovery Completion State dialog box appears.
Figure 8-5
SQL Server Recovery Options
You can choose to leave the database:

Nonoperational to apply transaction logs
Operational to bring the database online
Read-only to apply transaction logs and check the database
state
You can also choose to restore only the filesystem. You will have
to manually attach the database if you choose this option.
For more information on restoring SQL Server databases, see
Appendix B, SQL Server Procedures.
6. Click Next to display the Completing the Restore Wizard panel.
8-10

changes to your restore settings. Otherwise, click Finish.
See the Appendices at the end of this book for specific restore
requirements for Exchange, SQL Server, and NTFS volumes.
Restoring a Replica
to an MSCS Cluster
Before restoring a clone or snapshot replica taken from the MSCS

cluster back to its source volume, you must enable protected restore
on the CLARiiON (see Using CLARiiON Protected Restore on
page 8-12). Other than that, restoring a clone or snapshot replica in a
cluster environment does not require any special consideration. You
should follow the same restore procedure as on a stand-alone server.
However, SAN Copy replicas require extra steps in order to be
restored correctly.
Restoring a SAN Copy

Replica to an MSCS
Cluster
When you restore a SAN Copy replica to an MSCS cluster, the restore
can fail and provide a message about a failed cluster disk resource.
This may occur because SAN Copy restore involves unmounting the
source volume, which, for some applications, may trigger their
cluster resource group to fail over. Failovers in the middle of an
RMSE SAN Copy restore operation will cause the restore to fail.
To circumvent this, you can take the source volume to be restored out
of the cluster resource group where it belongs, do the restore, and
then put it back into its cluster resource group after the restore is
completed. By taking the volume out of the cluster resource group,
the unmount of the volume will no longer be associated with the
failover of the resource group.
See the Appendices at the end of this book for detailed examples on
how to complete these SAN Copy restore steps for Exchange 2003
and SQL Server in MSCS.
Restoring a Replica
8-11
8
Using CLARiiON
Protected Restore
When you restore a replica on a CLARiiON storage array that has

Protected Restore enabled, RMSE automatically takes advantage of
the CLARiiON arrays protected restore feature. CLARiiON
Protected Restore protects the data on a clone during a reverse
synchronization (or restore) procedure by fracturing all other clones
in the clone group in order to protect them from corruption should
the reverse synchronization option fail.
In addition, since CLARiiON arrays with protected restore capability
allow writes to the source LUNs immediately, while the reverse
synchronization is taking place, the protected restore capability (if
enabled) also prevents writes to the source LUN from being written
to the clones that contain the replica while the reverse
synchronization (restore) is happening. This maintains the integrity
of the replica, but allows, in effect, an instant restore of the data on the
replica.
To take advantage of CLARiiON protected restore in RMSE, you only
need to enable it on the CLARiiON array. There is no setting to enable
protected restore in RMSE.
Protected restore is a configurable feature of clones, not of snapshots.
But the behavior you see when restoring a snapshot replica is like that
of a protected restore for clones. Control is returned quickly back to
the user while the restore happens in the background. The snapshot
replica is protected during the background restore process. This is
normal behavior for a snapshot replica; there is no setting on the
CLARiiON to enable or disable.
8-12
Restoring Replicas from Tape Backups

Your data management strategy may involve using third-party
software to create tape backups of replicas before they are
automatically expired by RMSEs rotation period. If a disaster occurs,
you may need to restore an Exchange 2003 or SQL Server 2000 replica
that is older than the replicas that your rotation allows. RMSE
provides methods for you to import these older replicas back into the
RMSE environment, where they can be mounted and restored like
any other RMSE replica.
The following types of replicas can be restored from tape backups:
Exchange 2003 VSS replicas on Windows 2003
SQL Server replicas on Windows 2000 and Windows 2003
The Appendices at the end of this book explain how to prepare for
and perform these restores.
Restoring Replicas from Tape Backups
8-13
8-14
9
Invisible Body Tag
This chapter offers some tips on troubleshooting RMSE. It includes

Viewing Results in Logs....................................................................9-2

Routine Maintenance.........................................................................9-3
Common Problems and Solutions ...................................................9-5
RMSE Event Messages ....................................................................9-13
9-1
Viewing Results in Logs

A new RMSE log is created for the first job of the day. Information is
appended to the log whenever a replica is created, mounted, restored,
and so forth during that day. The logs are located in:
Program Files\EMC\Replication Manager SE
\logs\client\erm_clientyyyy_mm_dd_hh_mm_ss.log
Where:
yyyy_mm_dd_hh_mm_ss indicates the time the log was created.
You can also find information about a job in the Applications event
log on the RMSE server.
For more information on configuring the severity of messages that
are logged in the RMSE log files, see Changing the Log Level on
page 5-6.
9-2
Routine Maintenance
Cleaning Up
Resources Affecting
the LUN Limit
You should periodically free RMSEs unused clone group items, to

prevent their number from approaching the CLARiiON arrays
maximum number of clone group items. To free clone group items,
follow these steps:
1. Make a note of all storage groups associated with RMSE on the
CLARiiON array.
2. In RMSE Explorer, expire unwanted replicas.
3. Run Navisphere. In the Enterprise Storage dialog box, click the
Storage tab.
4. Double-click the icon for the storage system for which the Clone
Group resides, and then double-click the SnapView icon.
5. Double-click the Clones icon.
6. Double-click the Clone Groups Name icon that contains the clone
you want to remove.
7. Right-click the clone you want to remove, and select Remove. A
Confirm: Remove Clone dialog box opens.
8. Click Yes to confirm the removal of the clone and then OK when
it is successful. The application removes the clone from the Clone
Group. This clone is now a conventional LUN and it no longer
counts against the clone and mirror limits.
When you use these LUNs again to create a replica of the same job, a
full establish of the mirror will occur.
Avoid cleaning up clone groups which have associated snaps.
Routine Maintenance
9-3
9
Backing Up RMSE
Configuration Data
As part of your backup scheme, you should make regular backups of:
The RMSE database. By default, the database is stored in the

following location:
Program Files\EMC\Replication Manager SE\Data
If you installed RMSE in a different location, you should back up

the Data directory in that location.
The RMSE servers windows\tasks folder or winnt\tasks folder

on the system root drive. This folder contains the file that stores
your scheduling information.
Verify that no RMSE operations are scheduled during the backup

period.
9-4
Common Problems and Solutions

Installation/Startup
Problem
I receive errors when uninstalling RMSE from Add/Remove

Programs in the Windows Control Panel.
Proposed Solution
Run the uninstall program directly from the RMSE CD. To do so, run
setup.exe from the RMSE CD and select Remove.
Problem
RMSE Explorer takes a significant amount of time to read in the data

when starting up.
Possible Cause
The RMSE database contains many entries, which may include

several failed replicas.
Proposed Solution
Routinely expire your failed replicas. If this problem persists, try

slowing the automatic refresh rate of RMSE Explorer as described in
the Refreshing the RMSE Explorer Display section of the
Replication Manager SE User Guide.
RMSE Explorer
Problem
The RMSE Explorer does not display the expected drive letters or
databases.
Possible Cause
You are connected to the local host, not to the RMSE production host
or virtual hosts.
Proposed Solution
Add the production host to your managed environment by

following the steps described in Adding RMSE Servers on page 5-3.
9-5
9
Exchange Replications
Problem
The ESEUTIL utility fails during Exchange replications.
Possible Cause
You are using a version of the ESEUTIL utility that is different than
the version of Exchange on the production host.
Proposed Solution
Verify that the ESEUTIL utility on the host matches the version of
Exchange version installed on the production host. Also, verify that
the ESE.DLL file exists in the same directory as the ESEUTIL utility.
Progress Window
Problem
The Progress window does not update or does not appear to be

functioning correctly.
Possible Cause
It could be caused by a TCP/IP timeout issue. RMSE enables

keep-alive packets on its TCP/IP connections. The default keep-alive
time is 2 hours. If you want to change this time, you must edit the
registry.
Proposed Solution
If it does not already exist, add the KeepAliveTime DWORD value

entry to the following registry location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcp
ip\Parameters
This value is in milliseconds, so a decimal value of 1200000 would be

equivalent to 20 minutes.
9-6
Snapshot Failures
Problem
Snapshots fail with an error similar to the following:

Unexpected Microsoft Volume Shadow Copy error. Restarting
the services: Microsoft Volume Shadow Copy service and
Replication Manager service may solve the problem. Please
make sure there are no operations in progress.
Proposed Solution
Run the RM Config Checker and verify that you have the required
hotfixes from Microsoft. Download and install the missing hotfixes
from the Microsoft website and restart RMSE.
Microsoft Volume Shadow Copy errors may also occur if your
system is unreasonably busy during a VSS replication. Verify your
workload, including CPU and memory usage. If necessary, close any
unnecessary applications before trying the replication again.
Stranded SAN Copy

Sessions
Problem
Full SAN Copy sessions exist on the SAN Copy storage system, even
though no RM SAN Copy replicas or restores are running. These
stranded SAN Copy sessions appear in Navisphere on the SAN
Copy storage system in one of the following name formats:
EMC-ERM-clariion-<clariion ID>_<RM snapshotname>
EMC-ERM-clariion-<clariion ID>_<device id>
For example:
EMC-ERM-clariion-APM00043085189_myhost-0010-040505012345
EMC-ERM-clariion-APM00043085189_0346
Possible Cause
The RM service was stopped while a SAN Copy was in progress,

and stranded the full SAN Copy sessions.
Proposed Solution
Delete these sessions using Navisphere on the SAN Copy storage

system.
9-7
9
Mount Failures
Problem
Mount of a replica fails with an error message similar to the

following:
000070: Attempt to mount file system G:\ has failed with
an error as follows:mount failure, see logs for more
details. /*e*/
Solution
Edit the list of mounted devices in the Windows Registry.

If you are not familiar with Windows Registry Editor, you should use it with
caution. If you make a mistake, your system may become unusable.
1. Click Start and then Run and type regedit.

2. Using regedit, perform the following changes:
Navigate to the registry key
HKEY_LOCAL_MACHINE\SYSTEM\MOUNTEDDEVICES
Look for drive entries that meet these criteria:

You are certain they are not mounted on the mount host
They include \dosDevices as a prefix
For example, if E:\ is not mounted delete the following entry:
\dosDevices\E:
Problem
CLARiiON replica mount fails with one or both of the following

errors:
000358: Replication object clone LUN 123 from source LUN
45 on CLARiiON APM00030700175 was not able to be made
visible as a host device on host myhost123 after a bus
rescan.
000034: Function getHostDevice failed with an error as
follows: No non-PowerPath host device could be found for
"APM00030700175:0123". Please consult the Release Notes
for a list of possible causes and resolution steps.
9-8
Possible Cause
Your mount host is not configured correctly.
Proposed Solution
Run the RM Config Checker to verify that the environment on the

mount host conforms to requirements. Take corrective actions to
ensure a clean run of the RM Config Checker. Retry the mount after
corrections have been made. Also, make sure you have read and
followed the instructions listed in the Pre-Installation Checklist in
Chapter 2 of the Replication Manager SE User Guide.
Mount Failures
(continued)
Possible Cause
Incorrect zoning or other SAN issues.
Proposed Solution
Using Navisphere, verify that you can export LUNs to the mount
host. First, add a LUN to the storage group of the mount host. Then,
use the appropriate OS utilities to rescan for SCSI devices. If the
mount host has never seen CLARiiON devices, rebooting the mount
host may be necessary to see the LUNs the first time.
Possible Cause
You are using an unsupported host bus adaptor (HBA).
Proposed Solution
The HBA in the host may not be supported by EMC on the

CLARiiON. Check the EMC Support Matrix at powerlink.emc.com.
You may need to upgrade to a more recent HBA.
Possible Cause
You are using an unsupported OS driver, or driver firmware, for

your host bus adaptor.
Proposed Solution
Consult the HBA manufacturer's website to determine the latest

EMC-approved firmware and OS driver and update if necessary.
Possible Cause
You host bus adaptor is configured incorrectly.
Proposed Solution
Each HBA has settings that may affect mounting of replications. If

you are using an Emulex HBA, make sure the exlcfg utility was run
with the --emc (dash-dash) option.
Possible Cause
You are using an older version of PowerPath.
Proposed Solution
Some older versions of PowerPath may not work. Consult the RMSE
Support Matrix, and if necessary, make sure you have the most recent
version of PowerPath installed.
Possible Cause
No snapcache available to mount "snap of clone" replica.

A "snap of clone" type mount was attempted, but the mount host
could not create the "disposable" snap that it was going to use to
mount because snapcache was not available.
Proposed Solution
Dedicate more free LUNs in the snapshot cache to support the

associated replication.
9-9
9
SnapCache Full
Problem
Snapshot sessions on the CLARiiON array are not being cleaned up

when they are no longer needed.
Possible Cause
RMSE creates persistent snapshot sessions on the CLARiiON array

when performing snapshot and SAN Copy operations. In some
circumstances, snapshot sessions may be left on the CLARiiON
array (for example, if you uninstall RMSE without expiring all
snapshot replicas). These sessions can consume array resources if
they are not removed.
Proposed Solution
Manually remove unused sessions from the CLARiiON array.

If you have completely removed RMSE software from all hosts, or if
you have expired every snapshot replica on every host, use
Navisphere to remove all RMSE snapshot sessions and snapshot
names. The RMSE naming convention is Host-LUN-Timestamp. An
example snapshot session is:
myhost-0010-040506112233
If you have not removed RMSE and you have valid snapshot
replicas, you can determine if there are any unused snapshot
sessions as follows:
1. Open RMSE Explorer and connect to a host that is connected to
the CLARiiON array.
2. Open the CLARiiON Arrays folder and expand the array you
are checking.
3. Select the Snapshot Sessions folder.
In the display panel, all the snapshot sessions for the host that
are associated with valid snapshot replicas are displayed. Do not
remove these snapshot sessions via Navisphere. However, any
other snapshot sessions and snapshot names on the CLARiiON
array that have the same host prefix may be removed.
4. Repeat these steps for each RMSE server.
9-10
Replication Failures
Problem
Replications fail with an event message similar to one of the

following:
000378 ERROR: You have exceeded the maximum number of
snapshot sessions allowed on CLARiiON APM00040500844
when attempting to perform a replication. Check if the
source LUN 0123 has reached its maximum number of
snapshot sessions allowed or if the array has reached
the maximum number of allowed snapshot sessions.
000377 ERROR: You have exceeded the maximum number of
snapshot devices allowed on CLARiiON APM00040500844 when
attempting to perform a replication. Check if the source
LUN 0123 has reached its maximum number of snapshot
devices allowed or if the array has reached the maximum
number of allowed snapshot devices.
Possible Cause
You have reached the maximum number of concurrent snapshots

that your CLARiiON model can handle.
Proposed Solution
Consult your CLARiiON documentation for the maximum number

of snapshots that may exist on the entire array, and on a per-LUN
basis. Check to see if you have exceeded either the per-CLARiiON or
per-LUN limitation. You will need to expire some older snapshot
replications (for the whole array or an individual LUN) if you have
exceeded any of these limits. You may have to adjust your
replication schedules to ensure you do not reach these limits
consistently.
Problem
Replications fail with an event message similar to the following:

000332 ERROR: The limit of 8 clones has already been
reached for source LUN 0123 on CLARiiON APM00040500844.
This replication cannot create another clone for this
source LUN.
Possible Cause
You have reached the maximum number of clones allowed per LUN
on your CLARiiON model. Check your CLARiiON documentation
for these limits for your CLARiiON model.
Proposed Solution
Expire some of the older clone replicas for the same source LUN and
retry your replication. You may have to adjust your replication
schedules to ensure you do not reach this limit consistently.
9-11
9
Replication Failures
(continued)
Problem
Replications fail with an event message similar to the following:

000357 ERROR: You have exceeded the maximum total number
of clones, sources and mirrors allowed on CLARiiON
APM00040500844 when attempting to perform a replication.
Possible Cause
You have reached the maximum number of clones allowed to

concurrently exist on your CLARiiON model.
Proposed Solution
Follow the steps below if you exceed the per-array clone limit:
1. Expire any replications that you can.
2. Start RMSE Explorer on the replication host.
3. Expand the CLARiiON Arrays folder.
4. Expand the folder that corresponds to the CLARiiON in the
000357 event message.
5. Record all LUNs that are NOT marked "(In Use)".
6. Bring up the Navisphere User Interface for the CLARiiON.
7. Expand the SnapView folder.
8. Expand the Clones folder.
9. Fully expand every clone group with the "EMC RM
Clonegroup" prefix.
10. Find the clones that have the LUN IDs that you have recorded in
the earlier step.
11. Right-click the clone for the clone LUN. If you are sure that this is
a LUN that was NOT marked "(In Use)" by RMSE Explorer,
select Remove.
12. Repeat the previous step for all LUNs that you recorded as NOT
"(In Use)".
Do NOT remove any clone groups with the "EMC RM
Clonegroup" prefix, even if they currently have no active
clones.
9-12
RMSE Event Messages

Using Windows Event Viewer, you can gather information about
RMSE problems by tracing the events that RMSE records to the
application log.
To open the Windows Event Viewer:
Select Start > Settings > Control Panel > Administrative Tools >
Event Viewer
From the Event Viewer console tree, select Application Log and look
for any events in which the Source is listed as Replication Manger SE
Server.
RMSE logs the following types of events to the Event Viewers
Application Log:
Error
A significant problem, such as loss of data or loss of functionality. For

example, if an on demand mount fails, an Error event will be logged.
Information
An event that describes the successful operation. For example, when

a replication completes successfully, an Information event will be
logged.
RMSE Event Messages
9-13
9
Table 8-1 lists and describes all RMSE events that are logged on the
production host. These events apply to both on demand and
scheduled operations.
Table 9-1
RMSE Production Host Events
Event ID
Description
Additional Information Logged
5020
Replication job completed successfully.
Job name
5021
Replication job failed.
Job name
5022
On demand mount successful.
Job name and replica name
5023
On demand mount failed.
5024
On demand unmount successful.
5025
On demand unmount failed.
5026
On demand expire successful.
5027
On demand expire failed.
5030
Restore operation succeeded.
5031
Restore operation failed.
Table 8-2 lists and describes all RMSE events that are logged on the
host from which the schedule is run. These events apply only to
scheduled replication jobs.
Table 9-2
9-14
RMSE Schedule Host Events
Event ID
Description
Additional Information Logged
5045
Scheduled replication failed.
Job history as part of the job
Invisible Body Tag
Microsoft Exchange
Procedures
RMSE can replicate, mount, and restore one or more Microsoft

Exchange 5.5, 2000, and 2003 storage groups. This section covers the
specifics of Microsoft Exchange support in RMSE, including:
Configuring Exchange Hosts ..........................................................A-2

Creating Exchange 2000/2003 Replicas .........................................A-9
Creating Exchange 5.5 Replicas ....................................................A-16
Mounting Exchange 5.5, 2000, and 2003 Replicas ......................A-19
Recovering Exchange 2000/2003 Data.........................................A-20
Recovering Exchange 5.5. Data .....................................................A-38
Using Exchange Scripts..................................................................A-40
A-1
Configuring Exchange Hosts

This section provides information on configuration prerequisites that
are required for Exchange hosts that you plan to use with RMSE.
Refer to the Replication Manager SE Support Matrix on Powerlink for
updated information on required service packs and supported
operating systems.
A-2
Exchange Data
Layout
It is best to arrange the data so that volumes used for Exchange data
do not share physical volumes with other data that is not associated
with Exchange. Isolating the data on a dedicated volume prevents
potential problems when you restore data from a replica to the
production Exchange server. If data other than that associated with
Exchange resides on the same physical volumes, you may
inadvertently restore data that you did not intend to restore.
Configuring
Exchange
2000/2003
Production Hosts
Verify that your Exchange configuration meets the following

prerequisites:
Microsoft Exchange 2003 on Windows 2003, or Microsoft

Exchange 2003, 2000 on Windows 2000. Make sure that you have
installed the required service packs and hotfixes for Microsoft
Exchange, Windows 2003, and Windows 2000.
LUNs that are used for Exchange storage groups should only
contain data that is associated with that storage group.
The Exchange storage group's system path and transaction log

must have the same location.
The EDB and STM files must be on the same volume to ensure
that they will be replicated together.
Transaction logs and database files must be located on different

devices.
Circular logging must be disabled.
For Exchange 2000, set the volumes page size to a multiple of

4096 bytes (4 KB).
Verifying Exchange
2000/2003
Prerequisites
To ensure that the Exchange system path and transaction log have the
same location, the EDB and STM files are on the same volume, and
that circular logging is disabled:
1. In the Start menu, select Programs, Microsoft Exchange, System
Manager.
2. Expand Servers, your server, and then right-click each storage
group. Select Properties.
Figure A-1
Exchange 2003 Storage Group Properties
3. Select the General tab, and verify that:

The transaction log and system path share the same location
Circular logging is disabled.
4. Click OK. Now expand this storage group.
A-3
A
5. Right-click Mailbox Store and select Properties.
Figure A-2
Exchange 2003 Mailbox Store Properties
6. Select the Database tab, and verify that the Exchange database
(*.edb) and Exchange Streaming database (*.stm) share the same
volume.
A-4
Configuring
Exchange 5.5
Production Hosts
Verify that your Exchange configuration meets the following

prerequisites:
Microsoft Exchange 5.5 on Windows 2000. Make sure that you

have installed the required service packs and hotfixes for
Microsoft Exchange 5.5 and Windows 2000.
The information store and the directory store should be on

different physical disks.
The transaction log paths and working paths must be on the same
physical disk as the databases.
The working paths and the transaction log paths must be the
same.
Transaction logs and stores must be located on different devices.
Circular logging must be disabled.
Set the volumes page size to a multiple of 4096 bytes (4 KB).
RMSE checks to ensure that the Exchange data and logs are located on
separate physical volumes. If data and logs reside on the same volume, the
system issues an error and will not replicate the data.
Disabling Circular
Logging
To ensure that circular logging is disabled, follow these steps:

1. In the Start menu, select Programs, Microsoft Exchange,
Microsoft Exchange Administrator.
2. Select the appropriate site and expand it.
3. Select Servers and expand it.
4. Click the appropriate server to highlight it, then Choose File >
Properties from the menu.
5. Click the Advanced tab and clear the Directory & Information
Store check box under Database Circular Logging.
A-5
A
Configuring
Exchange Mount
Hosts
This section describes general requirements for an Exchange mount

host, and specific requirements for Exchange 2003, 2000 and 5.5.
The following are general requirements for an Exchange mount host:
The requirements for the mount host are the same as those for the
production host.
To use a mount host as an Exchange server, and bring the

Exchange database online, you must configure the mount host to
have the same:
Version of Exchange server installed as the production
Exchange server.
Service pack level installed as the production Exchange server.
Organization name as that of the production Exchange server.
Be sure to follow all of these configuration guidelines if you plan
to mount the database to an alternate mount host and access the
data (for example, in the case of a mailbox recovery).
Configuring Exchange
2000/2003 Mount
Hosts
Note the following additional requirements for an Exchange

2000/2003 mount host if you want to bring the database online:
The Exchange environment on the mount host must have the

same storage structure (drive letter, path, and filenames) as the
production environment.
Once you set up the structure, you must dismount the
information stores (using Exchange System Manager) and delete
the volumes that you created on the mount host (using the Disk
Management utility). These dismount and delete steps must
occur before the mount host can be used the first time to mount a
RMSE replica.
The mount host must reside in a different Active Directory forest

than the production Exchange server.
The mount host does not need the same Exchange server name as
the production Exchange server.
Exchange storage groups on the production Exchange server and

the mount host must have the same:
Names
Transaction log location
System path locations
A-6
Log file prefixes
Each Exchange storage group on the mount host must contain the
same number and type of information stores as those on the
production host.
Each information store on the mount host must have the same:
Name as on the production Exchange server
Associated Public Folder tree as on the production Exchange
server
Exchange database as on the production Exchange server (for
example, the same file name, location, and file system drive
letter)
Exchange streaming database as on the production Exchange
server (for example, the same file name, location, and file
system drive letter)
Configuring
Exchange 5.5 Mount
Hosts
In addition to using the mount host for consistency checking or for

backups, the Exchange 5.5 mount host can be used for mailbox
recovery. (Do not use the Exchange 5.5 mount host for disaster
recovery; the directory store requires that the mount host NETBIOS
name be the same as that of the production host.)
To prepare the mount host for mailbox recovery:
When installing Exchange, select Create a New Site and specify

the exact same organization and site names. Do not join an
existing site.
Use the same service account that was used originally and ensure
that permissions are set properly.
Disable circular logging.
Move the information store databases files, transaction log path

and working path to the same location as on the production host.
Leave the directory store where it is or locate it on a drive that is
not used by the production host.
Stop the System Attendant service and its dependent services.
Delete the volumes used by the information store.
A-7
A
Configuring
Exchange Mount
Hosts for
Consistency
Checking Only
To mount the Exchange database for consistency checking only, you

do not need to install the complete Exchange server software on the
mount host. You need to install the Exchange System Management
Tools, or copy only the appropriate Exchange consistency checking
utility to the mount host:
For Exchange 2003, install the System Management Tools.
For Exchange 2000, copy eseutil.exe and ese.dll from the

production Exchange server to the mount host.
For Exchange 5.5, copy esefile.exe to the mount host.
The command syntax for checking the consistency of the Exchange

database is:
Exchange 2003 (checks consistency of the database files and logs):

eseutil /k /i dbname.edb
eseutil /k Enn
where Enn is the log prefix
Exchange 2000:
eseutil /k /i dbname.edb
Exchange 5.5:
esefile /S dbname.edb
A-8
Creating Exchange 2000/2003 Replicas

RMSE allows you to do the following on Exchange:
Create replicas of Microsoft Exchange 2000/2003 storage groups.
On Windows 2000, initiate and control hot split (online) or offline

replications of Microsoft Exchange 2000/2003 data at the storage
group level.
On Windows 2003, initiate and control Full, Copy, or offline

replications of Microsoft Exchange 2003 data at the storage group
level.
Before each replication occurs, RMSE:
Support for VSS on

Exchange 2003
Discovers the location of the data to replicate.
Identifies pathnames for all the data in the requested storage

groups.
Microsoft Volume Shadow Copy Service (VSS) coordinates with

business applications, backup applications, and storage hardware to
enable application-aware data management. VSS is the infrastructure
that enables RMSE to create application-aware replicas on Windows
Server 2003. During replication, RMSE coordinates with VSS and
Exchange 2003 to create a shadow copy or snapshot, which is a point
in time copy of the volumes that contain the data and logs for
Exchange storage groups.
RMSE coordinates with VSS and Exchange 2003 to quiesce the
input/output to the storage groups during replication, and then
resume the flow of data to the storage groups after the replication is
complete. During a restore, RMSE coordinates with VSS and
Exchange 2003 to recover the point in time shadow copy.
VSS is shipped only with Windows 2003; it is not supported on Windows
2000. Also, you cannot create a shadow copy with Exchange 2003 on a
Windows 2000 server.
Exchange
2000/2003 Data
Objects in the Job
The Exchange Administrator can configure a job to replicate one or

more storage groups. Exchange can have up to four storage groups
per Exchange server. Each storage group can contain between one
and five Microsoft Exchange 2000/2003 databases and the
accompanying logs for those databases.
A-9
A
Planning for
Recovery
If you want to restore at the storage-group level, Microsoft Exchange

2000/2003 storage groups must be arranged on physical volumes so
that each storage group uses separate physical volumes for the
Exchange data and the logs. If you want to restore individual
databases, each database must be stored on a separate physical
volume. This is because RMSE restores the entire volume.
RMSE checks to ensure that the Exchange data and logs are located on
separate physical volumes. If not, the system issues an error and will not
replicate the data.
It is also best to arrange the data so that volumes used for Exchange
data do not share physical volumes with other data that is not
associated with that storage group. Isolating Exchange data prevents
potential problems when you restore data from a replica to the
production Exchange server. The system path location and
transaction log location must be the same. The EDB and STM files
must be stored on the same physical volume of the storage array to
ensure that they will be replicated together.
CAUTION
If data other than that associated with Exchange resides on the
same physical volumes, you may inadvertently restore data that
you did not intend to restore.
Hot-Split Replication
on Windows 2000
RMSE automatically creates a physical copy of the Exchange

databases (mailbox stores) and transaction log files for the storage
groups that you select in RMSE.
The following steps illustrate Microsoft Exchange 2000 and 2003
hot-split replication processing on Windows 2000:
1. Extract the database and log paths from the production Exchange
server.
2. Discover the mirrors and establish them.
3. Create the replica.
4. Mount the replica to an alternate mount host.
5. Check the database consistency using ESEUTIL.
A-10
The production Exchange server remains available throughout the

entire replication. There is no disruption of the production Exchange
server during the replication process.
Microsoft strongly recommends that you check the Exchange database for
consistency after you create a replica. To check database consistency, select
the checkbox that mounts the Exchange storage group immediately after
creating the replica, and select the option to run ESEUTIL in order to check
the databases for consistency. The ESEUTIL process runs against one
database at a time in RMSE.
When you perform a hot-split replication of Microsoft Exchange 2000

or 2003 on Windows 2000, RMSE establishes the mirrors and creates a
replica that captures the data, logs, and Microsoft Exchange
checkpoint files for the selected storage group(s). When you create a
replica using the hot-split method, RMSE checks to ensure the page
size is set to a multiple of 4096 bytes or (4 KB) because that is the
standard page size that should be used to facilitate a hot-split of
Exchange data.
After RMSE completes the split, RMSE mounts and performs the
consistency check if you choose to do that as part of the job. Finally,
RMSE catalogs the replica by copying all relevant information to
RMSEs internal database; it catalogs the locations of the database
files, transaction log files, and the Exchange checkpoint files required
to restore or mount the Exchange data.
Exchange 2000 Log
Truncation
When you create a Microsoft Exchange 2000 replica, you can choose
to truncate the committed Exchange log files in a way similar to
Exchange backup procedures.
A-11
A
Replicating
Exchange 2003 with
VSS
Running ESEUTIL
If you are creating replicas of Exchange 2003 on Windows 2003,

RMSE will not use hot-split technology to quiesce the data. Instead,
RMSE uses VSS to perform a truly online replication. In an Exchange
2003/VSS environment, you can select Full or Copy as the replication
option:
Full RMSE replicates the storage group(s), transaction logs,

and checkpoint files, and then runs ESEUTIL automatically to
verify the consistency of the databases and logs. If ESEUTIL
completes successfully, RMSE instructs Exchange to truncate the
logs so that only changes that are uncommitted to the database
remain.
Copy RMSE replicates the storage group(s), transaction logs,

and checkpoint files in the same way as it does during a Full
option, however it does not truncate the logs. Running ESEUTIL
is optional for Copy replications, but recommended. Copy
replications are often intended for testing and diagnostic
purposes only.
If you select a Full replica that truncates transaction logs, Microsoft

requires that you mount the replica as part of the job, and run
ESEUTIL. If the mount fails for any reason (ESEUTIL or device errors,
etc.), the logs are not truncated and the replica fails.
need to install the Exchange Administration Tools on the mount host.
Limitations of the
Microsoft VSS Writer
A limitation in the Microsoft Exchange VSS Writer prevents two

Exchange 2003 replicas from running at the same time on the same
machine, even if they are replicating different storage groups.
Therefore, RMSE runs one replica at a time; subsequent replicas must
wait until the previous replica is completed.
Another limitation is that VSS prevents successful mounts and
restores when the root drive letter has mount points on it and they are
all included in a job. For example, if the log and system files are on
L:\, and the mailbox stores are on L:\SG1DBMP (where SG1DBMP is
a mount point), mounts and restores will fail.
A-12
Exchange
2000/2003 Offline
Replication
If you choose not to use hot-split functionality to create the replica,

RMSE performs an offline replication, including the following steps:
1. Discover the database files and log paths on the Exchange Server
on the production host.
3. Dismount the selected Exchange databases.
4. Creates the replica.
5. Remount the selected Exchange databases.
6. Mount the replica to an alternate mount host (if required).
7. Run ESEUTIL to verify database consistency.
Exchange 2000/2003
Offline Replication
Steps
In the case of an offline replication, RMSE initiates the replication

process and dismounts the selected storage groups. When a storage
group is dismounted, the Exchange service is stopped for databases
in that storage group. Before the dismount, Exchange flushes all
changes to that storage group from memory to the disk. After
Exchange finishes the flush operation, the database is in a consistent
state. All storage groups that are not part of the replication continue
to process transactions normally.
After Exchange establishes the devices that will create the replica,
RMSE dismounts the selected storage groups and creates the replica
that represents those storage groups and logs. When that operation is
completed, RMSE mounts the databases it has dismounted.
Offline replications remount the selected Exchange storage groups if RMSE
dismounted them. If the Exchange storage groups were unmounted before
the replication started, RMSE does not remount them after the replication is
complete. In that case, the Exchange administrator must remount the storage
groups manually.
A-13
A
Detecting Data
Corruption
Exchange writes the following errors to the Application Event log

when they occur:
-1018 The database tried and failed to verify information
about a particular page in the database.
-1019 Similar to a -1018 error but indicates that the accessed
page has returned an invalid page number (usually all zeros)
rather than an invalid checksum.
-1022 Indicative of major hardware problems, particularly
disk subsystem problems. If the database engine requests a
page from disk but instead receives an error from the I/O
subsystem, a -1022 error results.
RMSE searches the application event log for these errors every time a
replica is created. The first time the job runs, RMSE searches the
entire event log. During subsequent runs of the job, RMSE searches
the event log from the point of the last run of the job, unless the
Ignore all errors for the next run only option is selected.
These errors can cause RMSE to fail a replication task unless you specifically
instruct RMSE to ignore these errors. For more information about ignoring
Exchange errors, see page 6-6.
A-14
Exchange 2000 Log

Truncation as Part of
Replication
If you want to truncate your committed Exchange logs, you can do so

by selecting the Truncate Transaction Logs option when you create a
job.
To truncate Exchange logs, your job must:
Choose the Truncate Transaction Logs option.
Mount the replica to some valid mount host to check the integrity
of the databases and logs with ESEUTIL.
If you are using Exchange 2003 in a Windows 2000 environment then the
Truncate Transaction Logs option is not available, because RMSE cannot
truncate Exchange Logs in an Exchange 2003/Windows 2000 environment.
If you do choose to truncate committed Exchange logs, RMSE

automatically truncates Exchange log files for each storage group in
the job. If ESEUTIL fails to run successfully on any of the databases or
logs, then the entire job fails and the logs are not truncated.
When Exchange log files are truncated, the committed logs are
deleted, not moved.
CAUTION
If you do not choose to mount the replica and run ESEUTIL, RMSE
will issue a potential data loss warning message and then truncate
the logs. Data loss can occur if you do not run ESEUTIL to check
the consistency of the databases and logs. The loss can occur later
when you need to restore the database and you find that the
database on the replica is corrupt.
A-15
Creating Exchange 5.5 Replicas

RMSE can create the following types of Exchange 5.5 replicas:
Online using hot split functionality.
Offline by shutting down the services.
RMSE can also perform the following tasks as part of the Exchange
5.5 job:
Check database with ESEFILE.
Truncate logs to help manage Exchange backups.
When you create a job, you can choose to replicate the entire
Exchange 5.5 server or part of it including one or both of the
following:
Exchange 5.5
Online Replications
Using Hot Split
Directory Stores
Information Stores
When you create a Microsoft Exchange 5.5 replica, you can choose to
create the replica while Exchange remains online, without
interrupting normal Exchange processing.
RMSE performs the following steps:
1. Discovers the database files and log paths of the Exchange Server
stores on the production host.
2. Discovers the mirrors and establish them.
3. Creates the replica and splits the mirrors.
4. Mounts the replica to an alternate mount host.
5. Runs ESEFILE to verify database consistency.
A-16
Exchange 5.5
Offline Replication
If you choose offline replication to create the replica, RMSE performs

the following steps:
1. Discover the database files and log paths on the Exchange Server
on the production host.
3. Stop the appropriate service and its dependent services.
4. Create the replica and split the mirrors.
5. Restart only the services that RMSE stopped.
6. Mounts the replica to an alternate mount host.
7. Runs ESEFILE to verify database consistency.
Check Database
Consistency with
ESEFILE Utility

do not need to install the complete Exchange server software on the
mount host. You need to copy only the appropriate Exchange
consistency checking utility to the mount host. For Exchange 5.5,
copy esefile.exe from the production Exchange server to the
mount host.
Truncate Logs to
Help Manage
Exchange Backups
When you create an Exchange 5.5 replica, you can choose whether to
truncate logs committed to the Exchange database after the replica
has been created. Truncation is helpful when you are creating a
replica to backup the Exchange 5.5 database.
When you choose to truncate Exchange logs, you should also mount
the replica to some valid mount host to check the integrity of the
databases with ESEFILE. If ESEFILE fails to run successfully on any of
the databases, then the entire job fails and the logs are not truncated.
When Exchange log files are truncated, the committed logs are
deleted, not moved.
CAUTION
If you truncate Exchange logs but do not choose to mount the
replica and run ESEFILE, RMSE will issue a potential data loss
warning message, and then truncate the logs. Data loss can occur if
you do not run ESEFILE to check the consistency of the databases.
The loss can occur later when you need to restore the database and
you find that the database on the replica is corrupt.
Creating Exchange 5.5 Replicas
A-17
A
Exchange 5.5
Mailbox Recovery
In addition to using the mount host for consistency checking or for

backups, the Exchange 5.5 mount host can be used for mailbox
recovery. Do not use the Exchange 5.5 mount host for disaster
recovery; the directory store requires that the mount host NETBIOS
name be the same as that of the production host.
To prepare the mount host for mailbox recovery:
1. Install Exchange on the mount host as described above.
2. During the installation process, select Create a New Site and
specify the exact same organization and site names (do not select
Join an Existing Site).
3. Use the same service account that was used on the Exchange
production host and ensure that the permissions are set correctly.
4. Disable circular logging.
5. Move the information store database files, transaction log path,
and working path to the same location as on the production host.
Leave the directory store where it is or locate it on a drive that is
not used by the production host.
6. Stop the System Attendant service and its dependent services.
7. Delete the volumes used by the information store.
Now RMSE can mount an Exchange database to the mount host and
bring that Exchange database online.
A-18
Mounting Exchange 5.5, 2000, and 2003 Replicas

RMSE can initiate and control mounts of Microsoft Exchange 5.5,
2000, and 2003 replicas, including:
Mount a replica to an alternate host in the same location as on the

production host.
Mount a replica on an alternate host in a new location

(determined by adding an alternate root to the pathname).
Mount a replica on the production host in a new location

(determined by adding an alternate root to the pathname).
If mounting an Exchange 2003 replica for backup, copy the metadata to the
mount host as part of the job and back it up.
RMSE can mount a replica to an alternate host that may or may not
have Exchange Server installed.
It can perform:
Mounts of new replicas as part of the replication job.
On-demand mounts of existing replicas.
Although RMSE can mount a replica to an alternate location on the

production or mount host, alternate location mounts have a limited use.
These mounts can only be used to run ESEUTIL (or ESEFILE) to check the
database and logs for consistency. The databases cannot be brought online in
Exchange System Manager.
Mounting Exchange 5.5, 2000, and 2003 Replicas
A-19
Recovering Exchange 2000/2003 Data

There are a couple of different scenarios and methods for performing
Exchange recoveries. For example, you may need to recover a server
due to corruptions, perform a mailbox restore, or repurpose the
replica on a test system. Depending on the circumstance and the
version of Exchange, the recovery processes will vary greatly. Please
refer to Microsofts Exchange Server Disaster Recovery Operations Guide,
(available for download on www.microsoft.com) for your specific
version of Exchange. This guide provide details on each of the
possible recovery methods.
When you restore a Microsoft Exchange 2000/2003 replica, you can
choose to restore any of the following:
All storage groups in the replica
One or more storage groups from the replica
One or more databases from the replica
A Microsoft Exchange 2000/2003 replica includes a checkpoint file

(.chk) This file records the location in the transaction log files of the
last complete transaction that Exchange wrote to the database. If you
choose to perform a full restore of databases and logs, the checkpoint
file helps Exchange know where to start rolling the database forward.
If there is no.chk file, Microsoft Exchange 2000/2003 starts with the
oldest transaction in the log file.
A-20
Selecting Full or
Partial Restores
The restore dialog allows you to choose all or part of a replica to

restore. This section describes what will be restored if you make
certain selections on that panel.
To restore the entire contents of the job, select the top node of the
Replica tree.
To restore the entire contents of a storage group, select the top

node of that storage group.
To restore all the datafiles from all the databases in a storage

group, without restoring the log files, choose the Exchange
Database Files node under the selected storage group.
To restore the datafiles from a single database, without restoring

the log files for that database, choose the node associated with the
database you want to restore underneath the Exchange Database
Files node of the Replica Tree.
If you are attempting to restore a mailbox store that has been entirely deleted
from the Exchange system since the replica was created, you must first
recreate the specific mailbox store in Exchange before RMSE can restore the
data from that mailbox store.
Restore
Considerations
If your replica contains one storage group, and you choose to restore
the databases and the logs, the logs will overwrite any newer logs
created since the replica was created. That means your database will
represent the point in time when the replica was created.
If you want to preserve logs created before the replica, you should choose to
restore only the datafiles to prevent RMSE from restoring older logs over
newer logs.
If you want to restore at the storage-group level, Microsoft Exchange

storage groups must be arranged on storage volumes so that each
storage group uses separate physical volumes for the Exchange data
and the logs. If you want to restore individual databases, each
database must be stored on a separate physical volume.
Before you can recover an Exchange database that was created on one
server to a different server, you must select the checkbox This
database can be overwritten by a restore on the Database tab in the
Properties screen of the Exchange Server Manager.
A-21
A
The system path location and transaction log location must be the
same. The EDB and STM file must be stored on the same volume to
ensure that they will be replicated together.
CAUTION
If data other than that associated with the storage group resides on
the same physical volumes, you may inadvertently restore data that
you did not intend to restore or overwrite data that you did not
intend to overwrite.
Restoring Exchange
2000/2003 Replicas
on Windows 2000
When restoring Exchange replicas, the system must contain one or

more storage group(s) that are currently not in use.
RMSE only dismounts the Exchange databases that were selected for restore
before the restore operation occurs. The Exchange Administrator must
remount the databases after the restore is complete. See instructions below.
When you restore a Microsoft Exchange 2000/2003 replica, you can

choose to restore any of the following:
All storage groups in the job
One or more storage groups from the job
One or more databases from the job
When you are restoring just a database file, verify that the transaction
log files needed for recovery are present. An unbroken sequence is
required. To determine the minimum required range, run the
following ESEUTIL command against each database after the restore:
ESEUTIL /mh <database name>
Where Enn is the log prefix for the storage group.
A-22
Recovering Exchange
2000/2003 After
Restore Completes
If you choose to restore one or more databases without restoring the

transaction logs, perform the following steps in the order shown to
recover Exchange after the RMSE restore completes:
1. Dismount all databases in the storage group.
You must manually dismount any databases in the storage group that
were not restored, because RMSE only dismounts the databases that are
being restored. Exchange needs all of the databases dismounted so that
Exchange can roll the database forward.
2. Remove the .chk file from the system path folder. For a database
restore that does not restore the log files, the .chk file should be
moved or deleted after a restore, but prior to remounting the
databases or restarting the Exchange service.
3. If logs have been truncated and you are restoring a database from
an older replica, make sure the transaction logs sequence is
complete and that there are no gaps. Run the following ESEUTIL
command against each database after the restore:
ESEUTIL /ml Enn

4. Remount all databases in the storage group. This automatically
starts a soft recovery and applies the logs.
This will cause Exchange to apply all of the existing transaction logs
to the older database.
CAUTION
If you choose to restore a storage group, the restore will overwrite
any logs created since the replica was created. That means after the
restore, your storage group reflects the point in time when the
replica was created.
If you want to preserve logs created since the replica, you should
choose to restore only the databases, preventing RMSE from
restoring older logs over your newer logs.
A-23
A
Restoring Exchange
2003 VSS Replicas
On Windows 2003, RMSE coordinates with VSS and Exchange 2003

to restore the volumes that contain the databases and logs that you
have selected to recover. If you choose to restore just one database
from a storage group, RMSE takes all databases in the storage group
offline because no temporary restore directory is available in which
JET can play forward the logs. When restoring a VSS replication, you
must restore it to the same location on the server from where it
originated. Also, you cannot restore a VSS replication to a Recovery
Storage group. VSS will automatically delete the checkpoint file if it is
not needed.
Because restores are done at the physical disk (LUN) level, all other data on
the volumes are overwritten.
If you are restoring from the most recent replica, you can choose to
restore:
One or more storage groups
One or more databases
If you are restoring from an older replica, it is recommended that you

restore only at the storage group level. However, this means you will
lose any changes that occurred since this replica was created. If you
have copies of all the logs that you need to recover the database to the
current time, you can restore at the database level.
If you choose database level, there can be no gaps in the log generations.
To restore an Exchange 2003 VSS replica:

1. Mount the replica you plan to restore.
2. Run the following ESEUTIL command against the database and
streaming files:
ESEUTIL /mh <database_name>
3. Examine the output of the ESEUTIL command to determine

which log files you need in order to recover the Exchange
databases. Look for the "Logs Required" line in the output, which
should resemble the line in the following example:
Log Required: 66-68 (0x42-0x44)
A-24
In this example, to recover this database to the point-in-time of

the replica, you will need log files Enn00042.log through
Enn00044.log (Enn is the log prefix for the storage group). To roll
forward, you will need the complete sequence of logs beginning
at Enn00042.log through the highest generation currently on the
production machine. You may have to restore log files from more
than one backup to complete the range.
You should also verify the database and log signatures. Refer to
Microsofts Exchange 2003 documentation for more information.
4. Unmount the replica.

5. Restore the database. This step depends on your individual
restore needs:
a. If you are restoring the entire storage group (database and log
files) to the point-in-time of the backup, right-click the replica
in the RMSE Explorer tree panel and select Restore from the
context menu (see Restoring a Replica on page 8-8 for more
information). Once restored, use Exchange System Manager to
mount the databases in the storage group.
b. If you want to restore a storage group or a database to a
point-in-time beyond the backup, right-click the replica in the
RMSE Explorer tree panel and select Restore from the context
menu to restore the desired components (see Restoring a
Replica on page 8-8 for more information). Then copy or
restore the necessary log files to the log path used by the
storage group.
For example, if you determined in step 8 that the starting log
file is E0100042.log and the current log file on the production
volume is E0100100.log, you will need to restore every log
file in the sequence from E0100042.log through
E0100100.log.
To verify that the logs are all present and valid, run the
following command:
ESEUTIL /ml Enn
A-25
A
The Exchange 2003
VSS Restore Process
When you click Finish on the Restore Wizard, RMSE will begin the
restore. The following occurs:
1. RMSE dismounts all databases in the affected storage group.
2. RMSE works with the Exchange VSS Writer to restore the selected
volumes.
3. The Exchange VSS Writer deletes the checkpoint file, if necessary.
4. RMSE verifies that the required log files are present and displays
an error if any are missing.
5. RMSE makes sure that there are no gaps in the log generations. If
there are, RMSE displays an error.
6. If you chose to Recover and Mount Databases, RMSE uses
ESEUTIL to recover the databases and then mount the databases.
This step is only completed if there were no missing logs.
Restoring an
Exchange 2003 SAN
Copy Replica to a
Cluster
This procedure describes the restore of a SAN Copy Exchange 2003

replica on Windows Server 2003 in an MSCS environment.
1. Using Cluster Administrator, take the Exchange Resource Group
offline.
2. Remove the disk dependencies from the System Attendant
Resource for the Exchange storage groups and logs that you want
to restore:
a. Select Properties from the System Attendant Resource.
b. Click the Dependencies tab, and then Modify.
c. Select all the physical disk resources that you want to
restore.
d. Select the left-arrow (I) button to remove the resource
dependencies.
e. Click OK to save the changes.
3. Delete the same Physical Disk Resources from the Exchange
Resource Group.
4. Bring the System Attendant Resource online. This causes the
other disk resources to come online (IP address and network
name).
5. Restore the selected Exchange storage group(s) or database(s)
using RMSE.
A-26
6. Add the Physical Disk Resources back into the Exchange

Resource Group using the Cluster Administrator.
7. Take the System Attendant Resource offline. Add the disk
dependencies back into the System Attendant Resource. To do
that, follow these steps:
a. Choose Properties from the System Attendant Resource.
b. Click the Dependencies tab and select Modify.
c. Select all the physical disk resources that you restored.
d. Click the right-arrow (J) button to add the resource
dependencies.
8. Bring the Exchange Resource Group online.
9. Mount the storage groups using the Microsoft Exchange System
Manager.
Restoring Exchange
2003 VSS Replicas
from Tape
Backing Up Exchange
Replicas to Tape
RMSE allows you to restore Exchange 2003 VSS replicas that were
backed up to tape using any backup software application.
This section explains how to:
Modify Exchange replication jobs in order to support tape backup

restores.
Import an Exchange replica from tape back into the RMSE

environment.
Restore the newly-imported Exchange replica to the mount host.
This procedure assumes that you have already created an Exchange

replication job that successfully creates a replica and mounts that
replica to the desired mount host. If you havent, see Chapter 6, Using
Jobs to Create Replicas, for information on how to create an Exchange
replication job.
1. In RMSE Explorer, right-click the Exchange replication job that
creates the replica that you want to back up to tape and select
Properties from the context menu.
2. Select the Mount tab of the Job Properties dialog box, and click
Advanced to access the Advanced Mount dialog box.
A-27
A
If you are creating a new replication job, these advanced mount options
are available by clicking Advanced in the Mount Options panel of the
Create Job Wizard.
Figure A-3
Advanced Mount Options Dialog Box
3. In the Metadata Location field, specify the directory path on the

mount host to which you want RMSE to copy Exchange metadata
files. Click OK to exit the Advanced Mount Options dialog box,
and click OK again to exit the Job Properties dialog box.
4. Create and mount the Exchange replica by right-clicking the
replication job in the RMSE Explorer tree panel and selecting Run
from the context menu.
5. Using your third-party backup software, back up all volumes of
the replica that reside on the mount host, along with all metadata
files located in the directory path you specified in the Metadata
Location field of the Advanced Mount Options dialog box (step 3
above).
A-28
Restoring Exchange
Replicas from Tape
1. In RMSE, run the Exchange replication job to create an extra,

temporary clone replica. RMSE requires this temporary clone
replica as a placeholder in order to successfully import the older
replica. The temporary clone replica must have the same
Exchange database names and paths as the replica that you want
to restore from tape backup.
2. Next, determine which type of restore you plan to perform. Are
you recovering just a database, or the entire storage group? Are
you restoring to the point-in-time of the backed up replica, or are
you planning to roll forward to another point-in-time?
a. If you plan to restore to the point-in-time of the backup, delete
any log files that exist in the log path of the mounted replica.
b. If you plan to roll forward to another point-in-time, save the
log files on the mounted replica. You will need these files
during the recovery phase.
3. In your third-party backup software, perform an in-place restore
of all volumes of the replica from tape to the mount host.
If volumes are mounted as mount points, should restore files for the
volume rather than the mount point, because the backup software may
not be able to restore the mount point correctly.
4. In your third-party backup software, restore the metadata files to

the mount host.
Before importing a replica, it is recommended that you create a manual
backup of the RMSE database. This will provide you with the option to
roll back the database if the import fails, and the RMSE database
becomes corrupted. Shut down the irccd process and copy the RMSE
database to a safe location before performing an import.
5. Right-click the temporary Exchange clone replica in the RMSE

Explorer tree panel and select Import from the context menu.
A-29
Figure A-4
Import Command
The Import dialog box appears, as shown below.
Figure A-5
Import Dialog Box
6. In the Import Path field, enter the path to the Exchange metadata
files. If you want to make sure RMSE does not automatically
expire the replica you are restoring from tape because of your
scheduled rotation, select Cannot be expired by rotation. Click
OK to start the import process.
A-30
Once RMSE successfully imports the replica, the timestamp of the

replica changes to the date of the replica that was backed up to
tape.
7. Run the following ESEUTIL command against the database and
streaming files:
ESEUTIL /mh <database_name>
8. Examine the output of the ESEUTIL command to determine

which log files you need in order to recover the Exchange
databases. Look for the "Logs Required" line in the output, which
should resemble the line in the following example:
Log Required: 66-68 (0x42-0x44)
In this example, to recover this database to the point-in-time of

the replica, you will need log files Enn00042.log through
Enn00044.log (Enn is the log prefix for the storage group). To roll
forward, you will need the complete sequence of logs beginning
at Enn00042.log through the highest generation currently on the
production machine. You may have to restore log files from more
than one backup to complete the range.
You should also verify the database and log signatures. Refer to
Microsofts Exchange 2003 documentation for more information.
9. In the RMSE Explorer tree panel, right-click the replica and select
Unmount from the context menu.
10. The next step depends on your individual restore needs, as
outlined in step 1.
a. If you are restoring the entire storage group (database and log
files) to the point-in-time of the backup, right-click the replica
in the RMSE Explorer tree panel and select Restore from the
context menu (see Restoring a Replica on page 8-8 for more
information). Once restored, use Exchange System Manager to
mount the databases in the storage group.
b. If you want to restore one database to the point-in-time of the
replica, but there are other databases in the storage group, you
will need to use a Recovery Storage Group. The procedure for
using a Recovery Storage Group is explained in white papers
available from Microsoft and EMC.
A-31
A
c. If you want to restore a storage group or a database to a
point-in-time beyond the backup, right-click the replica in the
RMSE Explorer tree panel and select Restore from the context
menu to restore the desired components (see Restoring a
Replica on page 8-8 for more information). Then copy or
restore the necessary log files to the log path used by the
storage group.
For example, if you determined in step 8 that the starting log
file is E0100042.log and the current log file on the production
volume is E0100100.log, you will need to restore every log
file in the sequence from E0100042.log through
E0100100.log.
11. Once you have recovered all of the log files, run the following
command to verify that all of the log files are present:
ESEUTIL /ml Enn
where Enn is the log prefix for the storage group.

12. Use the ESEUTIL utility to recover the database files, or use
Exchange System Manager to mount and recover the database
files.
Exchange
2000/2003 Mailbox
Recovery
If you want to perform a mailbox recovery from an existing replica,

follow these steps:
1. Try to recover the mailbox using the built-in Undelete feature
offered by Exchange. The default save time for undelete is 30 day,
but that can be increased to 90 days by the administrator. If you
are unable to retrieve the necessary Exchange information using
that method, proceed to step 2.
2. For Exchange 2003, use the Recovery Storage Group to recover
the mailbox. For more information, see Recovering Data From
Individual Exchange 2003 Mailboxes on page A-33.
3. Mount the replica to an alternate Exchange host.
a. Use the Microsoft Exchange 2000/2003 Mailbox Merge Wizard
(ExMerge.exe) to export the selected mailbox files from the
replica mounted on the alternate exchange host.
A-32
To make a mailbox (that resides within the replica) available to

the ExMerge Utility, it must be active and connected to a user
on the mount host. Also, the user running the ExMerge Utility
must have Receive as rights to the selected mailbox(es). Users
in the group Exchange Domain Servers are configured with
Receive as rights by default.
b. Follow the steps outlined in the wizard screens, select Extract
Data from an Exchange Server Mailbox, and provide the
requested information about the server, storage group, and
user. Remember the name and location of the personal folder
(.PST file) to which the data is exported.
c. Move the personal folder that you exported to the production
host.
d. Use the ExMerge Utility on the production host to import data
into an Exchange Server Mailbox. Again, provide the
requested information about the server, storage group, and
user. You will also be asked to specify the name of the personal
folder file that you exported to the production host.
The ExMerge Utility is available from the Microsoft Exchange
2000/2003 installation CD at \Support\Utils\I386\Exmerge. It
requires Windows to run successfully. For further requirements and
information, refer to the documentation that accompanies the
ExMerge Utility.
Recovering Data
From Individual
Exchange 2003
Mailboxes
You can use RMSE and the Exchange 2003 Recovery Storage Group
feature to recover data from individual mailboxes. In order to do this,
you will need to perform the following steps:
Create the recovery storage group.
Use RMSE to mount the replica.
Use the System Manager to copy or merge the mailboxes.
Delete the recovery storage group.
Use RMSE to unmount the replica.
A-33
A
Although you can create the recovery storage group on any Exchange
2003 server in the same administrative group, for performance
reasons Microsoft recommends that you create it on the production
host. If you decide to create the recovery storage group on another
host, that host must be setup up as an RMSE mount/backup host
with correct versions of software installed.
If the production host belongs to a cluster, you will have to create the
recovery storage group on an alternate mount host. You cannot mount
replicas back to the cluster. The same is also true if you are using dynamic
disks.
To recover data from individual Exchange mailboxes:

1. Before creating the recovery storage group, you need to create the
directories where RMSE will mount the replica and the recovery
storage group will find the databases, system files, and
transaction logs.
For example, if you plan to mount the replica to the production
host at the C:\RSGMounts alternate location, and your replica
contains the following:
M:\SG2\SG2DB1.edb
M:\SG2\SG2DB1.stm
M:\SG2\SG2DB2.edb
M:\SG2\SG2DB2.stm
M:\SG2Logs\Logs\E01.log, E01.chk, etc.
Where:
SG2 and SG2Logs are mount points, and
Logs is a subdirectory containing the transaction logs and system
files
You would create the following directories:
C:\RSGMounts\MDrive\SG2
C:\RSGMounts\MDrive\SG2Logs\Logs
These directories must be empty. The RMSE replica cannot be

mounted when creating the recovery storage group.
Even though the entire replica will be mounted, you do not have to
recover every database in the replica. You only create directories for the
databases that you will be recovering data from.
A-34
2. Using the Exchange System Manager, create a recovery storage

group by right-clicking the appropriate Exchange Server and
selecting New Recovery Storage Group.
3. The Recovery Storage Group Properties dialog is displayed.
Change the name of the recovery storage group as desired.
Modify the Transaction log location and System path location to
point to where the log files will be mounted. This is the log
directory you created in step 1. Click OK.
4. The recovery storage group is created and now you need to add
the databases you want to recover. Right-click the new recovery
storage group and select Add database to recover.
5. The Select database to recover dialog is displayed. Select one of
the databases that you want to recover and click OK. You can
only select one database at a time, so repeat steps 4 and 5 until all
of the appropriate databases have been selected.
You can only select databases from one storage group. On subsequent
iterations, the Select database to recover dialog will only show databases
from the storage group selected during the first iteration of this process.
6. Modify the Exchange database and Exchange streaming database

locations on the Database tab to point to where the database files
will be mounted. This is database directory you created in step 1.
Click OK.
7. Make sure the databases in the recovery storage group are
dismounted and the This database can be overwritten by a
restore option is selected.
8. Delete any files or subdirectories that you created in the alternate
mount location. For example, in step 1 you created
C:\RSGMounts\MDrive\SG2Logs\Logs. You need to delete the
Logs subdirectory. If SG2Logs had been a directory and not a
mount point, you would need to delete it also. An easier
approach is to delete C:\RSGMounts, if the directory is not in use.
9. From RMSE Explorer, right-click the replica from which you want
to recover data select Mount. Select the mount host (Host) and
the mount point used in step 1 (Mount at).
If you are mounting a clone or SAN Copy replica and want to
preserve its current state, select Discard changes to replica while
it is mounted. Click OK.
A-35
A
The use of CLARiiON snaps is not recommended for Exchange replicas
as any activity on the replica will impact the performance of the
production database.
10. When the replica is successfully mounted, you must change the
prefix of the log and system files. Open a command prompt
window and change to the directory where the log files are
mounted. Run the following DOS command:
ren Enn* R00*
For example, if the log prefix is E01, you will run: ren E01* R00*.
11. Perform a soft recovery of the database using the alternate mount
paths of the database, system and log files. To continue our
example, to recover the databases from step 1, open a command
prompt window and run:
C:\Program Files\exchsrvr\bin\eseutil /r R00 /i
/LC:\RSGMounts\MDrive\SG2Logs\Logs
/SC:\RSGMounts\MDrive\SG2Logs\Logs
/DC:\RSGMounts\MDrive\SG2
Where:
/L specifies the log path
/S specifies the system path
/D specifies the database path
It is important to run the command without any spaces after the

/L, /S, and /D options. If the alternate mount path has any spaces
in the name, enclose the path in double quotes.

12. Using the Exchange System Manager, right-click each recovered
database in the recovery storage group and select Mount Store.
The Database can be overridden by restore option must be
selected. Click Yes on the warning dialog that displays.
13. Once Exchange mounts the databases, you can recover data from
mailboxes using the System Manager. To recover mailbox data:
a. Select the Mailboxes node that displays when you expand the
database node.
b. The mailboxes for that database will display in the right-hand
panel. Select the mailboxes that you want to recover.
Right-click and select Exchange Tasks.
A-36
c. The Exchange Task Wizard displays. Click Next.

d. Select the Recover Mailbox Data option and click Next.
e. Select the appropriate Destination Mailbox Store and click
Next.
f. Depending on whether you want to merge the mailbox data or
copy the mailbox, select to either Merge Data or Copy Data
and click Next.
g. Schedule the task and click Next.
14. When you are done recovering mailboxes, use the Exchange
System Manager to dismount and delete each database in the
recovery storage group. Right-click each database and select
Dismount, then right-click and select Delete.
15. When all of the databases have been deleted, delete the recovery
storage group. Right-click the recovery storage group and select
Delete.
16. Make sure that nothing is accessing the mounted replica. Exit any
open command windows and close any Windows Explorer
sessions.
17. Using RMSE, unmount the replica.
A-37
Recovering Exchange 5.5. Data

When you restore a Microsoft Exchange 5.5 replica, you can choose to
restore any of the following:
Directory store (database and logs)
Directory database
Information store (databases and logs)
Information store databases (public and private)
All of the above
If you choose to restore an entire Exchange store (including the

transaction logs), RMSE restores the databases and related logs. The
restore will overwrite any logs created since the replica was created.
That means after the restore, your Exchange store reflects the point in
time when the replica was created.
Restore the
Exchange 5.5
Database
The first panel of the Restore Wizard allows you to choose all or part of a
replica and restore the part you select.
To restore the entire contents of the Exchange replica, select the

top node of the Replica tree.
To restore only the Directory Store database and the Information

Store databases, without the logs, choose those subfolders.
CAUTION
If data other than that associated with the storage group resides on
the same physical volumes, you may inadvertently restore data that
you did not intend to restore or overwrite.
To preserve the logs created since the time of the replica, restore only
the Information Store and/or Directory Store databases and not the
transaction logs.
A selective restore prevents RMSE from restoring older logs over newer logs.
A-38
After RMSE restores the data, you need to perform the following
steps:
1. Delete or rename the EDB.CHK file from the working path of any
stores that you restore.
2. Make sure the Directory Store service (MSExchangeDS) is
running, and make sure there are no gaps in the log generations.
3. If you restored the Information Store, access the Exchange bin
directory and enter the command isinteg -patch.
4. RMSE stops services for the Exchange database that is being
restored before the restore operation occurs. When the restore is
complete, the Exchange administrator should restore transaction
logs, then restart the stopped services (and dependent services) to
recover the database and resume on the system.
Mounting Exchange
5.5 for Mailbox
Recovery
If you want to perform a mailbox recovery from an existing replica,

follow these steps:
1. Follow the instructions to prepare the mount host, described in
Configuring Exchange 5.5 Mount Hosts on page A-7.
2. Use the Microsoft Exchange 5.5 Mailbox Merge Wizard
(ExMerge.exe) to export the selected mailbox files from the
replica mounted on the alternate Exchange host.
To make a mailbox available to the ExMerge Utility, it must be
active and connected to a user on the mount host. Also, the user
running the ExMerge Utility must have "receive as" rights to the
selected mailbox(es). Users in the group Exchange Domain
Servers are configured like this by default.
3. Follow the steps outlined in the wizard screens, select Extract
Data from an Exchange Server Mailbox, and provide the
requested information about the server, storage group, and user.
Remember the name and location of the personal folder (.PST
file) to which the data is exported.
4. Move the personal folder that you exported to the production
host.
5. Use the ExMerge Utility on the production host to import data
into an Exchange Server Mailbox. Again, provide the requested
information about the server, storage group, and user. You will
also be asked to specify the name of the personal folder file that
you exported to the production host.
Recovering Exchange 5.5. Data
A-39
Using Exchange Scripts

RMSE performs certain default actions on the host before and after
creating the Exchange replica, and after mounting the replica. You
can add your own custom actions to these default actions by
specifying them in Exchange scripts.
To use an Exchange script, you need to do the following:
1. Name the script and its location (by specifying the full path and
filename) while configuring the job in RMSE Explorer.
2. Ensure that the user account associated with the job can execute
all Exchange scripts that you plan to run on replicas created by
that job.
A script can be in any executable format (for example, .bat or
.exe). Scripts are not required. However, they can be helpful if
you need to perform some preparatory steps on the machine
before you create the replica, or if you want to perform some
clean up after the replica is created or mounted.
A-40
Invisible Body Tag
RMSE can protect SQL Server databases by creating and managing

replicas of SQL Server databases. This section covers the specifics of
Microsoft SQL Server support in RMSE, including:
Configuring the SQL Server 2000 Environment........................... B-2

Mounting and Restoring SQL Server 2000 Replicas .................... B-4
Using SQL Server VDI Snapshot Functionality.......................... B-13
Using SQL Server Scripts ............................................................... B-15
B-1
Configuring the SQL Server 2000 Environment

Before using RMSE with SQL Server 2000, ensure that the SQL Server
2000 environment is configured properly. The following checklist can
help you configure the environment to work with RMSE:
You should create a Database Maintenance Plan to coexist with
your scheduled replications. The plan should back up transaction
logs only. The plan should span the intervals between replications
to protect changes that occur between those replications. For
more information about creating a Database Maintenance Plan,
refer to your SQL Server documentation.
Specific SQL Server Service Packs are required. Refer to the
Replication Manager SE Support Matrix for specific SQL Server
version requirements.
SQL Server
Prerequisites
B-2
Verify that your SQL Server configuration meets the prerequisites

listed below. Refer to the Replication Manager SE Support Matrix on
Powerlink for updated information on required service packs and
supported operating systems.
Microsoft SQL Server 2000 (32-bit) on Windows Server 2003 and

Windows 2000. Make sure that you have installed the required
service packs and hotfixes for SQL Server, Windows 2000, and
Windows Server 2003.
SQL Server database and its transaction logs must be located on

disks in the same CLARiiON array.
Multiple SQL Server databases can exist in the same RMSE

replication job, with all databases residing on the same LUN, or
across multiple LUNs.
The SQL Server 2000 database must be online during replication.
The master, msdb, and model system databases should not be

located on the same device as user databases. Microsoft SQL
Server does not currently support using VDI and snapshot
technology to restore system databases.
Backing Up SQL
Server Including VDI
Metadata Files
The SQL Server VDI metadata files are required for a complete
backup of the SQL Server database. When you mount a replica, these
files are transferred to the mount host so that you can create a backup
to tape or other media.
RMSE can integrate with third-party backup software to create tape
backups of SQL Server replicas. The following procedure assumes
that you have already created a SQL Server replication job that
successfully creates a replica and mounts that replica to the desired
mount host.
1. In the tree panel, right-click the job whose replica you want to
back up to tape and select Properties.
2. Select the Mount tab, and then click Advanced. The Advanced
Mount Options dialog box appears.
3. In the Metadata location field, specify the directory path on the
mount host to which you want to copy SQL Server metadata files.
4. Mount the SQL Server replica.
5. Using your third-party backup software, back up all volumes of
the replica that reside on the mount host, along with all metadata
files located in the directory path you specified in the Metadata
location field.
Configuring the SQL Server 2000 Environment
B-3
Mounting and Restoring SQL Server 2000 Replicas

RMSE can:
Mount a SQL Server replica to an alternate host
Mount a SQL Server replica to the production host
Restore a replica over the original database
During a mount to an alternate host, EMC recommends that your mount host
meet certain configuration guidelines. These guidelines are described in
Mounting SQL Server Replicas, next.
Mounting SQL
Server Replicas
The RMSE can mount a replica to an alternate host, as long as that

host has:
SQL Server and RMSE software installed. (Optional, if you do not

intend to recover the database, SQL Server software is not
required.)
Production and mount host must have identical version of

Replication Manager Server software (irccd).
Identical operating system and volume manager as the

production host.
WARNING
If you want to use a SQL Server replica to recover a database, do not
attach the database to SQL Server while it is mounted. This modifies
the database and you may experience problems restoring the
database and applying transaction logs. Use the Read-write, discard
changes on unmount option if you need to attach the database to
SQL Server on the mount host. See Mounting a Replica on page 8-4.
RMSE can perform mounts:
B-4
On an alternate mount host to the same location as the production

host.
On an alternate mount host to a new location.
To the original production host in a new location.
Restoring SQL Server

Replicas
Note the following recommendations and restrictions when restoring

a SQL Server replica:
When choosing the SQL Server database to restore in the RMSE

Restore Wizard, make sure you mark for restore the SQL Server
database and all log files that reside on the same LUN.
In order to perform a full restore, you must detach the SQL Server
database. If the database is not detached when you request a
restore, RMSE detaches the database automatically. EMC
recommends that the database administrator detach the database
prior to a restore.
If you choose to restore a filegroup only, do not detach the

database. Also, make sure that you back up the transaction logs
before starting a filegroup restore.
There can be no open handles accessing any of the file systems

that contain database files that you plan to restore.
When the RMSE Restore Wizard is complete, use your backup

software to apply any existing transaction log backups and
recover the database manually.
You must restore all of the transaction log backups in
NORECOVERY mode. After the transaction log backups have
been restored, recover the database. Use SQL Server's Query
Analyzer to run the restore command with recovery:
RESTORE DATABASE database_name WITH RECOVERY
You cannot restore the master system database using RMSE. You
must manually copy the master database back into place by
following these steps.
1. Mount the replica.
2. Stop the SQL Server instance.
3. Copy the master.mdf and mastlog.ldf files from the replica
to the proper location on the production host.
4. Restart the SQL Server instance.
B-5
B
SQL Server
Restore Modes
The following section describes the SQL Server modes for restoring
replicas:
Filegroup Restores Allow you to restore a subset of the database
at filegroup granularity. RMSE performs restores at the volume level,
so if multiple filegroups reside on the same volume, the restore
operation will restore all file groups on that volume. Make sure you
select all filegroups that reside on the same volume.
Full Restores Allow you to restore the entire database instead of a
subset of the database.
EMC recommends that the Database Administrator detach the
database before performing a full restore.
When restoring SQL Server replicas, you must meet the following
prerequisites:
For a filegroup restore, you must put the database in Restrictive

mode and back up the transaction log.
You cannot perform a transaction log backup for a database using the
simple recovery model; therefore, filegroup restores are not supported
for databases using a simple recovery model. Only a full restore is
allowed with these databases.
There can be no open handles accessing any of the file systems

that contain database files that you plan to restore.
When you select a database for restore, RMSE automatically selects

all other databases that reside on that LUN for you. Similarly, when
you select a filegroup, RMSE automatically selects all other filegroups
on that LUN.
RMSE supports Recovery, No Recovery, Standby, and File System
restore modes when restoring a full database. Only No Recovery
mode is supported when restoring a filegroup or set of filegroups.
When in No Recovery mode, the database is unusable because it is in
an intermediate and non recovered state. No Recovery mode is useful
when the Database Administrator needs to restore one or more
transaction log backups.
In SQL Server, it is possible to restore many transaction log backups
one after the other. The intermediate restores are performed in No
Recovery mode and the last restore must be done in Recovery mode
to make the database usable again.
B-6
The last restore must be done in Recovery mode to make the database
usable again. If the database has been restored in RMSE using No
Recovery, Standby, or File System mode, then the Database
Administrator must recover the database manually after the restore is
complete.
Restoring Individual
SQL Server
Databases
RMSE includes a SQL Server restore utility called rmsqlrestore. The

rmsqlrestore utility lets you restore individual SQL Server
databases from a tape backup or mounted replica without
reverse-syncing the target device over the source device. It can restore
a database, filegroup, or file. The utility can restore to the original
database or to a new database. The SQL Server VDI metadata that
was created as part of the replication activity is required to restore a
database using rmsqlrestore.
Restoring an individual database from a mounted replica is
especially useful when you need to recover only one database and do
not want to overwrite an entire device, as would happen with a
normal RMSE restore.
How To Run
rmsqlrestore
Steps for Restoring

with rmsqlrestore
The rmsqlrestore utility is a command-line interface that you run

from a command prompt window on the RMSE client. rmsqlrestore
is installed on the client as part of the product installation.
The exact steps you need to take may differ from the following, but
the basic steps are:
1. Log on to the SQL Server system as a user with Administrator
rights.
2. Backup the SQL Server transaction log.
3. If restoring a database, take the target SQL Server database
offline. (For file or filegroup restore, the database must be online.)
4. If restoring a database, restore the database files (.ldf and .mdf)
from tape, or copy them from a mounted replica. You can copy
them over the original files or to a new location. (Does not apply
to file or filegroup restore.)
5. Open a command prompt window and cd to C:\Program
Files\EMC\rm\client\bin.
B-7
B
6. Run the rmsqlrestore command. Complete syntax and sample
commands are given in the syntax section following. The basic
command syntax is:
rmsqlrestore -s <SQLservername> -d <databasename>
-f <metadatafile> -r <recovery_type>
7. If necessary, apply transaction logs and recover the database.

Performing the File or
Filegroup Restore
Be sure you understand how restores of files and filegroups work in

SQL Server before proceeding.
1. Log on to the SQL Server system as a user with Administrator
rights.
2. Be sure the target SQL Server database is online.
3. Be sure that the transaction log is backed up.
4. Open a command prompt window and cd to
C:\Program Files\EMC\rm\client\bin.
5. Run the rmsqlrestore command. To restore two files, for
example, run:
rmsqlrestore -s <SQLservername> -d <databasename>
-f <metadatafile> -lf <logical_filename1>
-lf <logical_filename2> -r norecovery
To restore two filegroups, run:

rmsqlrestore
-s <SQLservername>
-d <databasename>
-f <metadatafile>
-lf <logical_filename1>
-fg <logical_filegroupname1>
-fg <logical_filegroupname2>
-r norecovery
Do not use quiet mode for a file or filegroup restore. You can use
-lf and -fg in the same restore command.
6. When rmsqlrestore displays the restore command that it is
about to run, verify with Y if it is correct.
7. When rmsqlrestore prompts, restore the files you are
recovering, enter Y to continue.
B-8
rmsqlrestore Command Syntax

Table B-1 lists the command syntax for the rmsqlrestore command.
Table B-1
rmsqlrestore Command Options

Option
Description
Required:
-s
SQL Server name including instance name

(host\instance).
-f
Metadata file name and location.
-d
Database name.
Connection Types(-E or -U)

-E
Trusted connection (default).
-U
SQL Server login ID.
-P
Clear text password (used with -U option).
-p
Encrypted password (used with the -U option).
Optional:
-r
Recover option - RECOVERY, NORECOVERY

(default), or STANDBY.
-u
Undo filename, required for STANDBY.
-m
Move file.
Option has two parameters:
logical_file_name and
operating_system_file_name
Pathnames must exist. Repeat option for each
file, including the log file. If you are restoring to
a new database name, use the -m option so
you do not overwrite the original files.
For example: -m logicalfilename
S:\existingdir\newfilename.m
df]
-fg
Filegroup to restore. Repeat option for each

filegroup.
-lf
Logical file to restore. Repeat option for each

logical file.
B-9
B
Table B-1
rmsqlrestore Command Options (continued)

Option
Description
-e
Displays encrypted password. Not used with

other parameters.
-v
Verbose mode.
-q
Quiet mode. Will not ask questions.
-l <log_dir>
Creates log files in the specified directory.
-h
Help
Examples:
To restore without applying logs using a trusted connection:
rmsqlrestore -s sql1\instance1 -d custinfo
-f C:\tempUndoDir\case120040926172920.bin
-r RECOVERY
To restore to a new database name and move files using a SQL login
and encrypted password:
rmsqlrestore -s sql1\instance1
-d custinfoTest
-f C:\tempUndoDir\custinfoTest120040926172920.bin
-r RECOVERY
-m custinfo_Data S:\custinfoTest.mdf
-m custinfo_Log T:\custinfoTest.ldf
-U sa -p 1EMC_4roJdyU5;x
To get the encrypted password:

rmsqlrestore -e unencrypted_password
command options are case sensitive.
Refer to the SQL Server Books Online for a description of the T-SQL
RESTORE command and its options.
B-10
Restoring a SQL
Server SAN Copy
Replica to a Cluster
This procedure describes the restore of a SQL Server 2000 SAN Copy
replica on Windows Server 2003 in a MSCS environment.
1. Using the SQL Server Enterprise Manager or Query Analyzer,
detach the database (to be restored).
2. Using the Cluster Administrator, take the SQL Server Resource
Group offline.
3. Remove the disk dependencies from the SQL Server Resource for
the databases and logs that you want to restore. To do that, follow
these steps:
a. Open the properties for the SQL Server Resource.
b. Click the Dependencies tab and select Modify.
c. Select all the physical disk resources that you plan to restore.
d. Click the left-arrow (I) button to remove the resource
dependencies.
4. Delete the same Physical Disk Resources from the SQL Server
Resource Group.
5. Bring the remaining Physical Disk Resources and Network Name
Resource online. Do not bring the SQL Server Resource online.
Start SQL Server as a non-clustered application:
a. Select Run from the Start menu, type cmd in the dialog, and
click OK.
b. For the default instance, enter:
net start MSSQLSERVER
For a named instance, enter:

net start MSSQL$<instance_name>
6. Using RMSE, restore the database in the appropriate recovery

mode.
7. Use the SQL Server Enterprise Manager to verify that the
database has been restored properly.
B-11
B
8. Stop the SQL Server service:
a. Select Run from the Start menu, type cmd in the dialog and
click OK.
b. For the default instance, enter:
net stop MSSQLSERVER
For a named instance, enter:

net stop MSSQL$<instance_name>
9. Using the Cluster Administrator, add the Physical Disk Resources

back into the SQL Server Resource Group. To do that, follow these
steps:
a. Open the properties for the SQL Server resource.
b. Select the Dependencies tab and click Modify.
c. Select the physical disk resources that are being added.
d. Click the right-arrow (J) button to add the resource
dependencies.
10. Click OK to save the changes.
11. Bring the SQL Server resource group online.
12. Recover transaction logs as needed.
B-12
Using SQL Server VDI Snapshot Functionality

SQL Server 2000 includes snapshot functionality. (In this context,
snapshot refers to Microsoft SQL Server VDI snapshot mode, not
CLARiiON snapshots or EMC snaps). Using snapshot functionality,
SQL Server can quickly create a point-in-time backup of a database,
which can be moved to alternate storage. When you are using the
snapshot mechanism, you should back up the transaction logs as part
of your regular maintenance tasks. Snapshot functionality allows you
to restore the database to a specific point in time. You should perform
snapshot backups frequently since they require fewer resources and
are less disruptive than offline backups.
Restore Steps in
Detail
To restore a database, use the following steps:

1. If you have transaction log backups to restore, restore the replica
containing a snapshot backup in No Recovery or Standby mode.
If you do not have transaction log backups to restore, restore it in
Recovery or Standby mode.
2. Apply transaction log backups, if they exist, and recover the
database manually. Transaction log backups are created
separately by the SQL Server database administrator. These
backups are sent to disk or tape and are not backed up by RMSE.
You should create a Database Maintenance Plan to coexist with your
scheduled replications. The Database Maintenance Plan should back up
transaction logs only. The plan should span the intervals between
replications to protect changes that occur between those replications. For
more information about creating a Database Maintenance Plan, refer to
your SQL Server documentation.
3. All of the last transaction log restores must be in No Recovery or

Standby mode. Use Microsoft SQL Server Query Analyzer to
recover each of the transaction logs separately, by running the
following command:
RESTORE LOG <dbname>
FROM DISK =<backup_filename>
WITH NORECOVERY;
Using SQL Server VDI Snapshot Functionality
B-13
B
4. If you restored with No Recovery or Standby, you need to recover
the database before it can be used. To do so, run the following
command:
RESTORE DATABASE <dbname> WITH RECOVERY
Where:
<dbname> is the name of the database.
After the database is recovered, it is impossible to apply any log backups
to roll forward the database.
B-14
Using SQL Server Scripts

creating the SQL Server database replica, and after mounting the
replica. You can add your own custom actions to these default actions
by specifying them in SQL Server scripts.
Using SQL Server

Scripts
To use a SQL script:

1. Name the script and its location (by specifying the full pathname)
while configuring the job in RMSE Explorer.
2. Ensure that the script will not take the database offline.
3. Ensure the script is owned by the SQL Server user and is
executable by the SQL Server user and group.
General Guidelines
for SQL Server
Scripts
The following guidelines can help you produce appropriate scripts

for SQL Server:
A script can be in any executable format (for example, .bat,

.exe).
To run transact-sql against the database, ensure it is in the

following format within the .bat file:
osql -E -S <instance_name> -Q <sql_query>
Where:
<instance_name> is the name of the SQL instance to run against
<sql_query> is the SQL statement in transact SQL
Using SQL Server Scripts
B-15
B
Sample Replication
Script
The sample in Figure B-1 is a basic prereplication script that prints the
database statistics before the replication occurs. Your scripts can add
any additional actions that you want to perform before replication.
osql /E /S <server_name> /d master /Q sp_helpdb
<database_name> /o c:\prescript.dat /w 600 /b
if ERRORLEVEL 1 goto FAILED
osql /E /S <server_name> /d <database_name> /Q
sp_helpuser /w 600 /b >> c:\prescript.dat
if ERRORLEVEL 1 goto FAILED
goto SUCCESS
:FAILED
echo An error occurred >c:/error.log
exit
:SUCCESS
echo The script finished successfully.
Figure B-1
Sample Replication Script
In the script shown in Figure B-1, replace <server_name> with the

name of the host and <database_name> with the name of the
database that you want to gather information about.
B-16
Invisible Body Tag
NTFS Procedures
RMSE can protect Windows-based (NTFS) file systems by creating

and managing replicas that contain the file system. This appendix
covers the specifics of NTFS support. It includes the following
subjects:
Creating NTFS Replicas ................................................................... C-2

Windows Host System Layer Concepts......................................... C-4
Using NTFS Volume Scripts ............................................................ C-6
NTFS Procedures
C-1
NTFS Procedures
Creating NTFS Replicas

RMSE can replicate software applications that store their data in
supported Windows-based (NTFS) file systems. The NTFS Agent
allows you to implement your own database or application
shutdown and startup scripts and allows you to support applications
and databases besides those specifically supported by RMSE.
Databases or applications that are good candidates for replication
and recovery include those that are:
C-2
Large and reside on supported storage.
Able to list all the filenames for the data.
Able to freeze the data, either by taking the application offline or

by some other means that ensures the data remains internally
consistent.
NTFS Replication
Operation
Without the use of any scripts, the file system remains mounted for
replication. The system flushes the file-system I/O buffer
immediately before splitting the mirrors to ensure that all changes
have been synchronized to disk.
Mount Host
Requirements for
NTFS Volume
Replicas
The requirements for the mount host for a volume replica are the
same as those for the production host.
If you are mounting a volume replica to the production server,
specify an alternate path so the mount does not fail due to the fact
that the production data is already mounted on that host in the
selected location.
NTFS Procedures
NTFS Mount and

Restore Functions
RMSE can initiate and control mounts and restores of NTFS. The
product can perform:
Mounts on an alternate mount host to the same location as the

production host.
Mounts on an alternate mount host to a new location (determined

by adding an alternate drive letter and optionally path
Mounts to the original production host in a new location

(determined by an alternate drive letter and optionally path
Restores from replicas to the production server.
RMSE can specify data from the replica to restore, subject to various
limitations as described in Restore Characteristics for Data in File
Systems on page C-5. Information stored using a Logical Volume
Manager (LVM) can be restored at volume-group granularity. Refer to
Windows Logical Volume Manager Concepts on page C-5.
Creating NTFS Replicas
C-3
NTFS Procedures
Windows Host System Layer Concepts

RMSE creates replicas at the device level. As a result, replication and
restore granularity depends on device layout. Therefore, it is
important to carefully lay out your devices so that they provide
adequate granularity for your applications during replication and
restore.
Windows Host Data

Layer Concepts
RMSE must replicate and restore each file system as a device. If datafiles
are placed directly on the devices, RMSE must replicate each
hypervolume.
The datafiles must reside on a supported CLARiiON storage array.
They can be placed either directly on the devices as viewed by the
host operating system or Logical Volume Manager (LVM), or they can
be placed within the file systems.
RMSE can create a replica of a single datafile if that datafile is

assigned directly to a single host device (physical volumes or
logical volumes).
RMSE creates a replica of the entire file system or logical volume

when datafiles reside within file systems or logical volumes.
RMSE can create replicas that contain only one partition per
physical device.
RMSE supports Windows mount points. If you mount an entire

NTFS drive as a subdirectory of another drive, you can create a
replica, and the selected mount point will be included in the
replica.
When you mount a replica that contains a Windows mount point similar to
that just described, it is important to ensure that the mount host has a drive
mounted to the drive letter where the mount point has been added. If that
drive does not exist on the mount system, the mount fails.
EMC recommends that you choose to mount all NTFS replicas as part of the
process of creating them.
C-4
NTFS Procedures
Replicating Partitions
or Logical Volumes as
Devices
If your datafiles are built directly on devices, RMSE replicates the

entire device or raw partition.
The software precisely replicates, and therefore restores, the data
specified in the job. However, if you build the database directly onto
logical volumes, granularity of the restore function is at the coarser
logical-volume-group level. Therefore, restore granularity becomes
the entire database, assuming one database per volume group.
For LVMs, granularity is at the volume-group level. Refer to Windows
Logical Volume Manager Concepts on page C-5.
Restore
Characteristics for
Data in File Systems
Restores reconstruct the entire file system, overwriting all the files in
that file system. Other restore characteristics include:
You cannot request individual files for restore because the whole
file system is restored.
The production file systems must be mounted at the start of the

restore.
The restore unmounts the file systems from the production server
to ensure the files cannot be accessed and to invalidate any
in-memory image of the file data on the host during the restore.
Individual files cannot be restored automatically, but you can mount a replica
to an alternate host, and then copy individual files manually.
Windows Logical
Volume Manager
Concepts
When you are replicating a file system that is located on a basic disk,
only one disk is affected. You can replicate, mount, and restore by
disk. RMSE handles volume groups in the following ways. All
devices in the volume group:
Are replicated.
Are imported when you mount the replica.
Are restored (when you restore the replica).
For example, if there are six file systems and 12 volumes in a volume
group, and you ask to restore just two file systems that use six
volumes, all of the volumes and file systems are restored. First, all of
the logical volumes are deported from the production data server;
after the restore, all of the volumes are imported to the production
data server.
Windows Host System Layer Concepts
C-5
NTFS Procedures
Using NTFS Volume Scripts

creating the NTFS volume replica, and after mounting the replica.
You can add your own custom actions to these default actions by
specifying them in NTFS volume scripts.
Custom scripts enable you to perform actions to ensure data
consistency for applications that store data in many interrelated files
or in a few very large files. (Refer to Creating NTFS Replicas on
page C-2 for more background information.)
For example, your pre-replication script could shut down your
application and your post-replication script could start up your
application or put your database or application into (and out of) an
Online Backup mode, if such a mode is available.
To use NTFS volume scripts, you need to do the following:
1. Specify the name of the script and its full pathname when you
configure the job in RMSE Explorer.
2. Do not assume the script will inherit any Windows environment
variables. Explicitly set PATH and any other environment
variables you might need in the script.
C-6
Index
A
applications
discovering 7-2, 7-6
supported 1-2
B
backing up RM/SE configuration data 9-4
C
circular logging
disabling in Exchange 5.5 A-5
CLARiiON storage array
assigning LUNs to storage groups 2-10
configuring LUNs 2-9
drive configuration, planning 2-8
preparing drives for snapshot replicas 2-12
preparing for SAN Copy replicas 2-14
RAID groups 2-8
RM/SE storage group 2-10
cleaning up 9-3
clones
time required for full establish 6-11
usage 1-6
cluster
mount host requirements 8-7
overview 3-5
prerequisites 3-5
RM/SE installation steps for 3-7
scheduling a job 6-15
SQL Server restore B-11
configuration, verifying 2-4
connecting to server 5-3
copy job 6-17

scheduling 6-20
D
datafiles
backing up as device C-4
Discard change to replica (mount option) 8-5
dynamic disks, support for A-9
E
EMC Replication Manager, transitioning to 1-8
Exchange
dismounting information stores A-6
mount host requirements A-6
mount host setup A-6
replica types 6-2, 6-5
restore backup from tape A-27
restore to cluster A-26
restoring replica A-20
supported versions 1-6
Exchange 2000/2003 A-1, A-2, A-9, A-10, A-13,
A-15, A-19, A-21, A-22, A-33, A-40
checking for consistency (ESEUTIL) A-11
log truncation A-11, A-15
pre- and postreplication scripts A-40
restore considerations A-21
selecting full or partial restores A-21
Exchange 5.5 A-17, A-24, A-38, A-39
creating replicas A-16
disabling circular logging A-5
Explorer
overview 4-5
refresh 4-7
i-1
Index
F
File menu, list of commands 4-5
H
Help
index, using 4-11
menu, list of commands 4-5
search, using 4-12
table of contents, using 4-10
viewer, using 4-9
hot split replication in Exchange 2000 A-10
I
import A-29
importing replicas A-29
installation
overview 3-2
N
NTFS
data layer concepts C-4
logical volume manager C-5
logical volumes C-4
partitions C-5
NTFS volumes
support for 1-7
J
job
cancelling 6-12
copy job 6-17
creating 6-2
defined 1-5, 6-2
deleting 6-16
modifying 6-15
running 6-11
scheduling 6-12
L
log truncation, Exchange 2000/2003 A-15
logical volume manager (LVM) C-4
logs 9-2
LUN 9-3
discovering 7-5
M
Microsoft Cluster Server (MSCS). See cluster.
Microsoft Exchange 2000/2003. See Exchange
2000/2003.
Microsoft SQL Server. See SQL Server
mount host
creating storage group for 2-11
i-2
mount host requirements

cluster 8-7
Exchange A-6
volume replicas C-2
mount points, support for in Windows C-4
mounting replicas 8-4
defined 1-5
troubleshooting 9-8
page size, setting

Exchange 2000 A-11
Exchange 5.5 A-2, A-5
partitions in Windows systems C-5
pre- and post-replication scripts
in SQL Server B-16
pre- and postreplication scripts
in Exchange 2000/2003 A-40
in SQL Server B-15
production host
creating storage groups for 2-11
protected restore 8-12
R
raw partitions C-5
refresh display 4-7
replicas 1-5
copying 6-17
creating 6-11
expiring 8-3
importing A-29
information recovery process 1-3
mounting 1-5, 8-4
properties 8-2
restoring 1-5, 8-8
restoring from tape 8-13
Index
SAN Copy 6-4

troubleshooting 9-11
Replication Manager/SE
backing up configuration data 9-4
components 4-2
connecting to server 5-3
database 3-4
Explorer 4-2, 4-5
general functionality 1-5, 6-2
help 4-8
installation 3-2
logs 9-2
menu bar 4-5
modifying installation 3-4
removing 3-4
server, defined 4-2
support matrix 2-1
supported applications 1-6
supported arrays 1-5, 6-2
replication types
clone 1-9
SAN Copy 1-10
snapshot 1-9
requirements
connectivity 2-2
hardware 2-2
patches and service packs 2-2
software 2-3
software required on hosts 2-3
restore
considerations, Exchange 2000/2003 A-21
Exchange backup from tape A-27
Exchange replica A-20
from tape 8-13
SQL Server replica B-5
restoring a replica 8-8
RM Config Checker 2-4
rmsqlrestore B-7, B-9
S
SAN Copy
creating replica 6-4
full 1-11, 2-15
incremental 1-12, 2-15
overview 1-10
storage group 2-17
troubleshooting 9-7
zoning 2-15
schedule
cluster 6-15
creating 6-12, 6-15
creating, in a cluster environment 6-15
SLQ Server
snapshot functionality B-13
SnapCache
troubleshooting 9-10
snapshots
preparing CLARiiON array for 2-12
usage 1-6
vs. clones 1-15
SQL Server
file restore B-8
filegroup restores B-6, B-8
full restores B-6
mount and restore functions B-4, B-6, B-7,
B-8
pre- and post-scripts B-16
pre- and postscripts B-15
restore to cluster B-11
restoring B-5
restoring with rmsqlrestore B-7
snapshots B-13
supported versions 1-7
storage
adding 7-2
modifying properties 7-3
storage arrays supported 1-5
T
tape backups 8-13
troubleshooting
backing up RM/SE data 9-4
cleaning up LUNs 9-3
Exchange replications 9-6
installation 9-5
mount failures 9-8
progress window 9-6
replications 9-11
RM/SE Explorer 9-5
SAN Copy 9-7
SnapCache full 9-10
snapshots 9-7
i-3
Index
startup 9-5
viewing logs 9-2
V
View menu, list of commands 4-5
VSS
support for in Exchange 2003 agent A-9
i-4

Replication Manager SE PDF

Uploaded by

Document Information

Original Description:

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

Replication Manager SE PDF

Uploaded by

Copyright:

Available Formats

Replication Manager SE

Copyright 2005 EMC Corporation. All rights reserved.

Replication Manager SE User Guide

Before You Begin

Replication Manager SE User Guide

Managing RAID Groups, LUNs, and Storage Groups................2-8

Working with RMSE Servers

Replication Manager SE User Guide

Viewing and Modifying Server-Wide Properties ........................ 5-8

Using Jobs to Create Replicas

Configuring RMSE Storage and Applications

Working with RMSE Replicas

Replication Manager SE User Guide

Microsoft Exchange Procedures

Replication Manager SE User Guide

Recovering Data From Individual Exchange 2003

SQL Server Procedures

Index ............................................................................................................................... i-1

Replication Manager SE User Guide

Replication Manager SE User Guide

As part of an effort to improve and enhance the performance and capabilities

This guide describes how to install, configure, and operate

Purpose of This Guide

This guide describes how to install, configure, and use RMSE

SQL Server databases on Windows 2000 and Windows

Exchange 2003, Exchange 2000, and Exchange 5.5 mail databases

Exchange 2003 on Windows Server 2003

NTFS file systems on Windows 2000 and Windows Server 2003

Replication Manager SE User Guide

This guide is intended for use by storage administrators, database

Operation of application software used in conjunction with RMSE

Related RMSE documentation includes:

Replication Manager SE Release Notes, which are delivered with the

Replication Manager SE Quick Start Guide, which is delivered with

For specific information about supported applications, operating

Choose the link to the EMC Support Matrix.

Replication Manager SE User Guide

Dialog box, button, icon, and menu items in text

Arguments used in examples of command line

System prompts and displays and specific

Where to Get Help

User entry. For example:

Options in command line syntax

(800) 543-4782 (543-4SVC)

Replication Manager SE User Guide

Sales and Customer

Your suggestions will help us continue to improve the accuracy,

Replication Manager SE User Guide

Replication Manager SE (RMSE) creates disk replicas of your

Replication Manager SE Overview .................................................1-2

RMSE makes your work easier by allowing you to focus your

Replication Manager SE Overview

Microsoft SQL Server databases

Microsoft Exchange databases

With RMSE you can:

Create point-in-time replicas of production data in seconds.

Facilitate quick, frequent, and non-disruptive backups from

Mount replicas to alternate hosts to facilitate offline processing

Mount multiple replicas on the same mount host.

Restore deleted or damaged information quickly and easily from

Set the maximum number of replicas for replication jobs so that

RMSE automatically controls the complexities associated with