Professional Documents
Culture Documents
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
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
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
iii
Contents
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
iv
Contents
Chapter 6
Chapter 7
Chapter 8
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
vi
Contents
Appendix B
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
vii
Contents
viii
Preface
ix
Preface
Audience
Related
Documentation
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
Courier,
italic
Courier
Courier,
bold
irccd -h
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:
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
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
1
Invisible Body Tag
Introduction
Introduction
1-1
Introduction
NTFS volumes
1-2
Introduction
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:
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.
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:
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.
If you plan to use the data in your replica to restart your application
after a disaster, you should consider using the following settings:
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.
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:
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:
Decision-support processing
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
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
Microsoft Exchange
1-6
Introduction
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:
General Functionality
1-7
Introduction
1
Making the
Transition to
Replication
Manager
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
Supported Replications
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.
SAN Copy
1-10
Introduction
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
Supported Replications
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
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
Supported Replications
1-13
Introduction
2
Target
Source
5
Production
Host
Snap Monday
Snap Tuesday
SAN
1
Session
Snap Wednesday
CLARiiON Array
(SAN Copy Storage System)
Figure 1-4
CLARiiON Array 2
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
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.
Supported Replications
1-15
Introduction
1-16
2
I
Finding Current
Information and
Updates
2-1
Required Hardware
and Connectivity
2-2
Required Software
for CLARiiON Arrays
FLARE Release 14
FLARE Release 16
Required Software
for RMSE Hosts
EMC Admsnap.
2-3
Installing RM Config
Checker
Running RM Config
Checker
2-4
Figure 2-1
Figure 2-2
2-5
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
2-6
2-7
Configuring RAID
Groups
2-8
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
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.
2-10
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
Creating Storage
Groups for Mount
Hosts
2-11
Figure 2-4
2-12
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.
2-13
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
Host 2
Storage
Group
Host 1
Storage
Group
Production
Host
(Host 1)
SAN
EMC
Replication
Storage
CLARiiON Array 1
(SAN Copy Storage System)
Figure 2-5
EMC RM
SANCopy
SG
Mount
Host
(Host 2)
EMC
Replication
Storage
CLARiiON Array 2
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
0
0
SP A
SP A
1
SAN
1
EMC RM
SANCopy
SG
0
0
SP B
SP B
1
1
CLARiiON Array 1
(SAN Copy Storage System)
Figure 2-6
CLARiiON Array 2
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
2-16
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 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.
Preparing CLARiiON Arrays for Full and Incremental SAN Copy Replications
2-17
2
Connect the SAN
Copy Storage
Group to the
Remote CLARiiON
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:
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.
2. Insert the RMSE distribution CD in the CD-ROM drive. The
RMSE welcome screen appears.
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.
3-2
Installing RMSE
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
Installation Overview
3-3
Installing RMSE
3
Modifying or
Removing RMSE
3-4
Installing RMSE
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.
3-5
Installing RMSE
3
Installing RMSE on
MSCS
Pre-Installation Steps
for MSCS Support
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
3-7
Installing RMSE
3
Upgrading from
RMSE 2.1.5 and 2.2.0
on Cluster Nodes
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:
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
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
4-3
Getting Started
Figure 4-1
RMSE Explorer
4-4
Getting Started
Some menus and commands appear only for specific views in the
active target 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:
4-5
Getting Started
Figure 4-2
4-6
Getting Started
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
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.
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:
4-8
To view...
Select the...
Help index
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
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
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.
4-10
Getting Started
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
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
4-12
5
Invisible Body Tag
5-1
Figure 5-1
5-2
Adding RMSE
Servers
Figure 5-2
Figure 5-3
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
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
Java path
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
and select Properties from the context menu.
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).
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
and select Properties from the context menu.
2. Click the Cluster tab to view a list of all virtual nodes in that
cluster, as shown below.
Figure 5-5
5-6
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.
Figure 5-6
5-7
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
5-8
Figure 5-7
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.
5-9
5-10
6
Invisible Body Tag
6-1
Creating a Job
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
Click Next.
3. Select the replica type and maximum number of replicas.
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
6-5
6
6. Click Advanced on the Replication Options for Microsoft
Exchange panel to access Microsoft Exchange advanced options.
Figure 6-1
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).
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.
Figure 6-2
6-8
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.
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.
6-10
Running a Job
Figure 6-3
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.
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
6-12
Figure 6-5
See the Whats This? help for more information on the individual
fields of the Schedule Job dialog box.
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
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
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
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:
1. Expand the Jobs folder in the RMSE Explorer tree panel.
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.
6-18
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.
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
Discovering Storage...........................................................................7-2
Discovering Applications .................................................................7-6
7-1
Discovering Storage
Adding Storage
Figure 7-1
7-2
Modifying Storage
Properties
Figure 7-2
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
7-4
4. Select the array and run Discover LUNs to update the RMSE
database.
Discovering LUNs
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
7-6
8
Invisible Body Tag
8-1
Figure 8-1
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
Expiring a Replica
on Demand
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
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
Result
Requirements
X:\
X:\Zdrive
X:\mnt1
X:\mnt1\Zdrive
Result
Requirements
X:\
X:\Zdrive\EXCHSG1
X:\mnt1
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.
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.
Figure 8-3
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
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
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
8-10
Restoring a 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
8-12
The Appendices at the end of this book explain how to prepare for
and perform these restores.
8-13
8-14
9
Invisible Body Tag
Troubleshooting RMSE
Troubleshooting RMSE
9-1
Troubleshooting RMSE
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
Troubleshooting RMSE
Routine Maintenance
Cleaning Up
Resources Affecting
the LUN Limit
Routine Maintenance
9-3
Troubleshooting RMSE
9
Backing Up RMSE
Configuration Data
As part of your backup scheme, you should make regular backups of:
9-4
Troubleshooting RMSE
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
Possible Cause
Proposed Solution
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
9-5
Troubleshooting RMSE
9
Exchange Replications
Problem
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
Possible Cause
Proposed Solution
9-6
Troubleshooting RMSE
Snapshot Failures
Problem
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.
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
Proposed Solution
9-7
Troubleshooting RMSE
9
Mount Failures
Problem
Solution
9-8
Possible Cause
Proposed Solution
Troubleshooting RMSE
Mount Failures
(continued)
Possible Cause
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
Proposed Solution
Possible Cause
Proposed Solution
Possible Cause
Proposed Solution
Possible Cause
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
Proposed Solution
9-9
Troubleshooting RMSE
9
SnapCache Full
Problem
Possible Cause
Proposed Solution
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
Troubleshooting RMSE
Replication Failures
Problem
Possible Cause
Proposed Solution
Problem
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
Troubleshooting RMSE
9
Replication Failures
(continued)
Problem
Possible Cause
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
Troubleshooting RMSE
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
9-13
Troubleshooting RMSE
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
Event ID
Description
5020
Job name
5021
Job name
5022
5023
5024
5025
5026
5027
5030
5031
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
Event ID
Description
5045
Microsoft Exchange
Procedures
A-1
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
LUNs that are used for Exchange storage groups should only
contain data that is associated with that storage group.
The EDB and STM files must be on the same volume to ensure
that they will be replicated together.
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
A-3
A
5. Right-click Mailbox Store and select Properties.
Figure A-2
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
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.
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
A-5
A
Configuring
Exchange Mount
Hosts
The requirements for the mount host are the same as those for the
production host.
Configuring Exchange
2000/2003 Mount
Hosts
The mount host does not need the same Exchange server name as
the production Exchange server.
A-6
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
Use the same service account that was used originally and ensure
that permissions are set properly.
A-7
A
Configuring
Exchange Mount
Hosts for
Consistency
Checking Only
Exchange 2000:
eseutil /k /i dbname.edb
Exchange 5.5:
esefile /S dbname.edb
A-8
Exchange
2000/2003 Data
Objects in the Job
A-9
A
Planning for
Recovery
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
A-10
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
Limitations of the
Microsoft VSS Writer
A-12
Exchange
2000/2003 Offline
Replication
Exchange 2000/2003
Offline Replication
Steps
A-13
A
Detecting Data
Corruption
A-14
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.
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
RMSE can also perform the following tasks as part of the Exchange
5.5 job:
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
Check Database
Consistency with
ESEFILE Utility
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.
A-17
A
Exchange 5.5
Mailbox Recovery
A-18
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:
A-19
A-20
Selecting Full or
Partial Restores
To restore the entire contents of the job, select the top 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.
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 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>
A-22
Recovering Exchange
2000/2003 After
Restore Completes
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
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
If you are restoring from the most recent replica, you can choose to
restore:
A-24
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
A-26
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:
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
A-28
Restoring Exchange
Replicas from Tape
A-29
Figure A-4
Import Command
Figure A-5
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
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
Exchange
2000/2003 Mailbox
Recovery
A-32
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:
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.
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
A-34
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
A-36
A-37
Directory database
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.
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
A-39
A-40
B-1
SQL Server
Prerequisites
B-2
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.
B-3
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
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
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.
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:
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
How To Run
rmsqlrestore
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>
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
Description
Required:
-s
-f
-d
Database name.
-U
-P
-p
Optional:
-r
-u
-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
-lf
B-9
B
Table B-1
Description
-e
-v
Verbose mode.
-q
-l <log_dir>
-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
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.
e. Click OK to save the changes.
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
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
B-12
Restore Steps in
Detail
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
General Guidelines
for SQL Server
Scripts
Where:
<instance_name> is the name of the SQL instance to run against
<sql_query> is the SQL statement in transact SQL
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
B-16
NTFS Procedures
NTFS Procedures
C-1
NTFS Procedures
C-2
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
RMSE can initiate and control mounts and restores of NTFS. The
product can perform:
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.
C-3
NTFS Procedures
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 replicas that contain only one partition per
physical device.
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
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 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.
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.
C-5
NTFS Procedures
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
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
Replication Manager SE User Guide
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
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
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