HP 3PAR Recovery Manager 4.2.0 Software
for Microsoft Exchange 2007
User’s Guide
Abstract
This guide is designed for System Administrators and Microsoft Exchange Administrators who are responsible for backing up
Microsoft Exchange mailbox or public store databases and who understand Microsoft Exchange 2007.
HP Part Number: QL226-96078
Published: August 2011
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries
in the United States and other countries.
Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Microsoft Exchange 2007 is a trademark of Microsoft Corporation.
All other trademarks and registered trademarks are owned by their respective owners.
C Event Messages.....................................................................................102
6Contents
1 Introduction
Related Documents
(CLI) to configure and manage the HP 3PAR Storage System
configure and administer HP 3PAR Storage Systems
(CLI) for remote clients to install and configure Recovery
Manager
problems
Read the…For Information About…
HP 3PAR InForm OS CLI Administrator’s ManualUsing the HP 3PAR InForm OS Command Line Interface
HP 3PAR InForm Management Console HelpUsing the HP 3PAR InForm Management Console to
HP 3PAR InForm OS Concepts GuideAssigning the appropriate user roles and rights
HP 3PAR InForm OS CLI Administrator’s Manual
HP 3PAR InForm OS Command Line Interface ReferenceUsing the HP 3PAR InForm OS Command Line Interface
HP 3PAR InForm OS Messages and Operator’s GuideIdentifying HP 3PAR Storage System components and fixing
HP 3PAR InForm OS Concepts GuideUnderstanding the HP 3PAR Storage System and its features
Shadow copies using HP 3PAR VSS Provider Software for
Microsoft Windows
Typographical Conventions
The following typographical conventions are used in this guide:
Table 1 Typographical Conventions
ABCDabcd
ABCDabcd
ABCDabcd
ABCDabcd
ABCDabcd
HP 3PAR VSS Provider Software for Microsoft Windows
User's Guide
HP 3PAR InForm OS Configuration MatrixPlatform-specific release levels
To obtain a copy of this documentation, go to http://
www.hp.com/go/3par/, navigate to your product page,
click Support for your product, and then click Manuals.
Used for dialog box elements such as
titles and button labels.
output, and for text you are to enter.
output.
Used for variables in file names,
paths, and screen output, and
variables in user input.
ExampleMeaningTypeface
Enter your system name in the Value
box and click OK.
Found < 12 > 73G disks.Used for file names, paths, and screen
Enter cli at the Windows command
prompt.
cli% removevv VV1Used to contrast your input with system
Removing vv VV1.
[root@(systemID-nodeID)root]
To continue Enter your system
name ==> systemname
Related Documents7
NOTE:The InServ Storage Server has been rebranded as HP 3PAR Storage System. There are
instances in this document where screenshots and/or menu items and command output refer to the
HP 3PAR Storage System as InServ or InServ Storage Server.
Advisories
To avoid injury to people or damage to data and equipment, be sure to observe the cautions and
warnings in this guide. Always be careful when handling any electrical equipment.
WARNING!Warnings alert you to actions that can cause injury to people or irreversible damage
to data or the operating system.
CAUTION:Cautions alert you to actions that can cause damage to equipment, software, or data.
NOTE:Notes are reminders, tips, or suggestions that supplement the procedures included in this
guide.
8Introduction
2 Overview of Recovery Manager
System Requirements
General Requirements for Recovery Manager
•Microsoft Windows Server 2008 or 2008 R2
•Single processor with either 1.4 GHz (x64) or 1.3GHz (Dual Core)
•512 MB RAM
•32 GB hard drive space
•Virtual copy (snapshot) space must be available on HP 3PAR Virtual Volumes.
To create virtual copies on the base volume, you must allocate virtual copy space to the volume
itself when you create the base volume. For information on creating a base volume with virtual
copy capability, or assigning virtual copy space after the base volume is created, see the HP3PAR InForm OS Command Line Reference.
NOTE:For complete details on system configurations, see “Recovery Manager Layout” (page 13).
Components Required on the Exchange Server (Production Server)
•Microsoft Exchange Server
•HP 3PAR InForm OS Command Line Interface (CLI)
•HP 3PAR VSS Provider Software for Microsoft Windows
•Recovery Manager Agent component
Components Required on the Backup Server
•Microsoft Exchange Management Tools component
•HP 3PAR InForm OS Command Line Interface (CLI)
•HP 3PAR VSS Provider Software for Microsoft Windows
•Recovery Manager Backup Server component
Licenses Required on the HP 3PAR Storage Server
•HP 3PAR Virtual Copy Software
•HP 3PAR VSS Provider Software for Microsoft Windows
•HP 3PAR Recovery Manager Software for Microsoft Exchange
•HP 3PAR Remote Copy Software (Optional)
•HP 3PAR Virtual Lock Software (Optional)
NOTE:For platform-specific release levels, refer to the latest HP 3PAR InForm OS Configuration
Matrix. To obtain a copy of this documentation, go to http://www.hp.com/go/3par/, navigate
to your product page, click Support for your product, and then click Manuals.
Recovery Manager Requirements
•The Exchange datastores for which you are creating virtual copies must be online.
•The same level of software updates is required on all Exchange servers.
System Requirements9
•Microsoft Exchange System Management Tools must be installed on the backup server.
NOTE:If you are running a Single Copy Cluster (SCC) or a CCR (Cluster Continuous
Replication) on Windows 2008, the backup server needs to have the "Failover Clustering"
feature enabled to function properly.
•HP 3PAR VSS Provider 2.1.0 or higher Software for Microsoft Windows is required.
•Microsoft .Net Framework V3.5 or higher is required by VSS Provider.
•Visual C++ (2005 Redistributable) Runtime libraries (x64 or x86). You can install this
automatically by running the Setup.exe program provided with Recovery Manager for
Exchange.
There is a known issue for Recovery Manager for Exchange when running Setup.exe on
Windows 2008. If you have already installed the Visual C++ Runtime library, the install script
still asks you to install it. You can install it again or directly install it from the .msi file.
•For CCR configurations on two HP 3PAR Storage Systems, where both nodes are separated
by a long distance, two Recovery Manager for Exchange backup servers are required.
NOTE:For platform-specific release levels, refer to the latest HP 3PAR InForm OS Configuration
Matrix. To obtain a copy of this documentation, go to http://www.hp.com/go/3par/, navigate
to your product page, click Support for your product, and then click Manuals.
Running Recovery Manager on a Japanese OS
CAUTION:To be fully compatible with Recovery Manager, you must use English-language naming
conventions in your Exchange setup (for example, for domain names, instance and database
names, path names, and so on).
Recovery Manager does not function correctly when any language other than English is used, even
for areas in which Exchange itself supports Japanese characters.
•Exchange OS: Windows Server 2008 R2, Japanese OS
•HP 3PAR VSS Provider 2.1.0 Software
•HP 3PAR Recovery Manager Software for Microsoft Exchange 4.2
•HP 3PAR Storage System 2.3.1 or higher
NOTE:The Japanese OS does not support scheduling virtual copies using Task Scheduler. (In
other words, the functionality described in “Automating Tasks” (page 39) is not available in the
Japanese OS.)
Features Supported
•Exchange online virtual copy creation using Volume Shadow Copy Service
•Volume Shadow Copy Service “Full” backup type
•Virtual copy creation using HP 3PAR VSS Provider Software for Microsoft Windows
•Access to the HP 3PAR Storage System via the HP 3PAR Command Line Interface (CLI) for
Microsoft Windows
•Mount virtual copies on Windows hosts on which Recovery Manager is installed
•Mount virtual copies with read/write permissions
•Unmount virtual copies
•Delete virtual copies
10Overview of Recovery Manager
•Backup using HP Data Protector or Symantec NetBackup
•Restore from backup using HP Data Protector or Symantec NetBackup
•File Copy restore
•Volume restore
•Co-existence with autonomic groups (domain sets, volume sets, and host sets)
•Virtual copy creation of LCR databases where the active and passive copies both reside on
a single HP 3PAR Storage System.
•Virtual copy creation of CCR databases, where active and passive copies reside on a single
or dual HP 3PAR Storage System with single or dual Recovery Manager backup servers, where
the second backup server connects to a secondary HP 3PAR Storage System at the remote
site
•Virtual Lock of CCR storage groups and CCR virtual copies
•Recovery Manager GUI
•Recovery Manager CLI
•Virtual copy creation for local and remote Exchange servers
•Single Copy Cluster for Exchange 2007
•Host sets for Single Copy Cluster
•Centralized virtual copy management with multiple Exchange servers
•Cross–Windows-domain support
•HP 3PAR Remote Copy Software (in both synchronous and asynchronous periodic mode)
•Queueing of virtual copy creation and backup for different storage groups from the same
backup server
Features Not Supported
•VSS backup types “Incremental”, “Differential”, “Copy” and “Log”
•A single Exchange server spanning different HP 3PAR Storage Systems
•All backup tools excluding HP Data Protector and Symantec NetBackup
•Access to the HP 3PAR Storage System via SSH
•Creation of virtual copy on System Boot Volume
•Exchange CCR volumes in a Remote Copy volume group
•Cross HP 3PAR Storage System mounts (includes CCR dual HP 3PAR Storage System
configurations)
•VSS snapshot backup for SCR node
•Windows automount feature
•Date customization: Recovery Manager always displays dates in month/day/year format
Microsoft Volume Shadow Copy Service
Microsoft includes VSS (Volume Shadow Copy Service) in Windows to simplify the enterprise’s
storage environment. It provides a framework for creating a point-in-time copy of a single or multiple
volumes.
Microsoft Windows Server VSS works with the VSS-aware applications that are in use to determine
when a volume shadow copy (snapshot) can be made. (A snapshot is a virtual copy: a copy of
some data set, for example, a disk volume, at a point in time.) VSS then communicates with the
Features Not Supported11
operating system and applications and freezes I/O to the storage system to allow snapshot creation
(without the freeze function, data could become corrupted when the snapshot is taken because the
system might be in the middle of a task). Meanwhile, applications continue to run uninterrupted.
The original volume continues to change as the process continues, but the shadow copy of the
volume remains constant. VSS also gives permission to the backup application to access the volume
and back it up in its frozen state. The shadow copy volume is then used for the actual backup.
After VSS saves the shadow copy volume on the backup device, it deletes the shadow copy.
VSS coordinates between Requestors (backup applications such as Recovery Manager), Writers
(applications such as windows services like Exchange 2007) and Providers (components that create
the shadow copies).
Table 2 VSS Components
VSS Component DescriptionVSS Component
Requestor
Writer
Provider
Supported VSS Components
VSS components currently supported by HP 3PAR VSS Provider Software for Microsoft Windows
include:
•Requestor
Recovery Manager◦
◦Symantec NetBackup for Microsoft Windows
◦HP Data Protector for Microsoft Windows
•Writer - Microsoft Exchange 2007
The requestor is backup software that initiates the creation
of the shadow copy.
The writer is any application software that participates in
the shadow copy process and whose files and data are
included in the process.
The provider is the storage technology that does the actual
shadow copy.
12Overview of Recovery Manager
NOTE:For platform-specific release levels, refer to the latest HP 3PAR InForm OS Configuration
Matrix. To obtain a copy of this documentation, go to http://www.hp.com/go/3par/, navigate
to your product page, click Support for your product, and then click Manuals.
How VSS Works with Exchange
Figure 1 HP 3PAR VSS Provider Software for Microsoft Windows Operation Overview
1.The requestor (Recovery Manager) sends a command to the Volume Shadow Copy service to
take a shadow copy of the selected Exchange storage group.
If a previous request is still in process, Recovery Manager adds the new request to the request
queue.
2.The Volume Shadow Copy service communicates with the Exchange writer to flush the current
log file generation to disk and suspend any writes to the log files and to the .edb file. The
.stm file is not allowed to grow; however, read-only access is still allowed. Therefore, anything
that is already there can still be accessed from the client.
3.Volume Shadow Copy service communicates with the provider to initiate the shadow copy
process for the disk volumes that contain Exchange data. VSS talks to the writers and providers
to fix a point in time for the shadow copy to take place; it is the provider that actually does
the shadow copy.
4.The shadow copy typically takes less than a minute. Clients that use Microsoft Outlook in
cached mode do not notice any disruption. Clients of earlier versions of Outlook might see
the hourglass icon for several moments during the shadow copy process.
5.After the shadow copy is created, Volume Shadow Copy service communicates with the
Exchange writer to indicate that it can resume writing to disk.
6.The queues of the email transactions are written to the logs.
The shadow copy is now available to the requestor for backing up.
Recovery Manager Layout
Recovery Manager allows for many types of configuration, depending on your setup.
How VSS Works with Exchange13
Centralized Backup Configuration
A centralized backup configuration, as shown in Figure 2 (page 14), allows you to maximize the
resources and performance of the Exchange servers through off-host central control management
capabilities. A single backup server can remotely create virtual copies on multiple Exchange servers
and manage all virtual copies on the backup server.
This type of configuration is recommended if you need to manage multiple Exchange servers or
are in a clustered environment.
Figure 2 Centralized Backup Configuration
NOTE:The Exchange System Management Tools is required on the Recovery Manager Backup
Server for Exchange database for validation purposes. In addition, the Exchange Servers and the
Management Tools must use matched release and service pack versions.
NOTE:All the Exchange servers, including the Recovery Manager Backup Server component,
must be in the same Windows domain (unless you have configured Recovery Manager to use
multiple Active Directory domains).
Single Host Backup Configuration
A single host backup configuration, as shown in Figure 3 (page 15), allows you to manage virtual
copies locally on the Exchange server.
14Overview of Recovery Manager
Figure 3 Single Host Backup Configuration
CCR Backup Configuration
CCR configurations can be implemented at a single site or span multiple sites. When implemented
at a single site, a single backup server is utilized as shown in Figure 4 (page 15) and Figure 5
(page 16). For implementations that span multiple sites, two backup servers are required as shown
in Figure 6 (page 16). The command RMExch peer is used to specify the name of the peer backup
server for multiple sites. This command must be run in CCR configurations using two backup servers
and is not required for CCR configurations using only one backup server. See “Configuring Recovery
Manager” (page 22).
Figure 4 Single HP 3PAR Storage System, Single Site
Recovery Manager Layout15
Figure 5 Two HP 3PAR Storage Systems, One Site
Figure 6 Two HP 3PAR Storage Systems, Two Sites
Multiple Domain Backup Configurations
Multiple domain backup configurations, shown in Figure 7 (page 17), allow you to use one backup
server for multiple Active Directory domains. Keep in mind:
•All backup components (for example, the backup server, backup software client, and Remote
Copy target server) must be in the local domain.
•The production servers and the Windows hosts enabled for mounting virtual copies can be in
domains other than the local domain.
For more information about configuring multiple domain setups, see “Configuring Multiple Domains”
(page 24).
16Overview of Recovery Manager
Figure 7 Multiple Domains
Server Relationships
The following defines the roles and relationship between the server types:
Backup Server
The Backup Server plays a central control point for the Recovery Manager that controls and manages
the backup and restore on different Exchange servers.
Remote Copy Backup Server
Depending on the configuration, the Remote Copy backup server(s) manage synchronous and
asynchronous periodic Remote Copy virtual copies.
Exchange Servers
The Exchange Servers can be standalone servers or cluster virtual servers.
Connectivity
Both the Backup Server and Exchange Servers need to be connected to the same HP 3PAR Storage
System. To manage a CCR-enabled configuration from a single backup server for CCR nodes that
connect to two HP 3PAR Storage Systems within the same site; the backup server needs to connect
to two HP 3PAR Storage Systems with separate FC or iSCSI connections. The HP 3PAR Storage
Systems also need to be in the same active directory domain unless you have registered multiple
Active Directory domains.
Recovery Manager Layout17
3 Installation and Deinstallation
Upgrading to Recovery Manager for Exchange
Following are instructions for upgrading to HP 3PAR Recovery Manager Software for Microsoft
Exchange from version 2.2.4 through 3.0.2 to version 4.2.0.
NOTE:In Recovery Manager for Exchange, version 3.0.2, the installation directory has changed
from \Program Files\3PAR\vcdba\Exchange to \Program Files\3PAR\RM\Exchange.
To migrate from version 2.2.4 to 3.0.2, 4.1.0, or 4.2.0, deinstall Recovery Manager for Exchange,
install Recovery Manager for Exchange 3.0.2, 4.1.0, or 4.2.0, and move the Repository folder
from the old \vcdba\Exchange\Repository to the new \RM\Exchange\Repository
location.
Production Server
1.Deinstall Recovery Manager for Exchange. See “Deinstalling Recovery Manager” (page 20).
2.Install Recovery Manager for Exchange 4.2.0. See “Installing Recovery Manager” (page 18).
Backup Server
1.Backup the repository to a safe location, i.e. the folder Exchange\Repository and all
directories and files under it.
2.Deinstall Recovery Manager for Exchange. See “Deinstalling Recovery Manager” (page 20).
3.Install Recovery Manager for Exchange 4.2.0. See “Installing Recovery Manager” (page 18).
4.Move the Repository folder from the old \vcdba\Exchange\Repository to the new \RM\Exchange\Repository location.
5.Check to see that the old virtual copies can be seen from the GUI and re-register the Exchange
Server(s) if necessary.
Installing Recovery Manager
Before installing Recovery Manager, install the HP 3PAR Command Line Interface (CLI) for remote
clients. For details on installing the CLI, see the HP 3PAR InForm OS Command Line InterfaceReference. You must also install HP 3PAR VSS Provider Software for Microsoft Windows before
installing Recovery Manager for Microsoft Exchange. Install Recovery Manager for Exchange on
a host computer where Microsoft Exchange is running.
WARNING!Before installing Recovery Manager, create a backup of your repository data.
CAUTION:Back up your data before upgrading the Recovery Manager or all data will be lost.
See “Upgrading to Recovery Manager for Exchange” (page 18) for instructions on performing a
backup.
NOTE:HP recommends that you install the application directly from the system console.
To install Recovery Manager:
1.Log on as the System Administrator.
NOTE:In order to log in as the System Administrator, you must have Exchange server and
system administrator rights.
2.Insert the Recovery Manager CD into a CD-ROM drive.
18Installation and Deinstallation
3.Open a Windows Explorer window by clicking Start→All Programs→Accessories→WindowsExplorer.
4.Click the CD-ROM drive to expand the files.
5.Double-clickSetup.exe to launch the installation wizard
6.Click Next.
7.Agree to the license, then click Next.
8.Specify the installation directory for Recovery Manager.
NOTE:The Disk Cost button analyzes the amount of available storage space and compares
it to the amount required for the Recovery Manager installation.
9.Click Next to confirm the installation destination.
10. Specify the installation type for the local system.
•Recovery Manager Backup Server — Installs components required for local system to
perform centralized backup management.
•Recovery Manager Agent for Exchange Server — Installs components for local system to
be managed by the Recovery Manager Backup Server component installed server.
•All of above — Choose this option if you have a single host setup where the local system
manages its own virtual copies.
11. Click Next to confirm the local server selection.
12. Click Next to start the installation.
13. When the installation is completed, click Close.
After closing, the system configuration information is gathered and displayed in a text file
named RMECfgChk.txt. This information is useful for verifying whether all the required
components are present on the system.
14. If you are using a remote desktop session to install Recovery Manager, log off all connected
remote sessions after the installation is complete. The newly added environment variables then
go into effect.
Verifying the Installation
1.Log on as the System Administrator.
2.Click Start→Control Panel→Programs and Features.
3.Verify Recovery Manager appears under the Currently installed programs column.
Understanding the Registry
After Recovery Manager is installed successfully, some information is written into the registry
database under HKEY_LOCAL_MACHINE\SOFTWARE\3PAR\RM_Exchange.
CAUTION:DO NOT try to edit the registry key value unless asked by your local service provider
for support purposes.
NOTE:For tracking purposes, you will be asked to modify the value of the TraceLevel to a higher
number to record more detailed information to the log file.
The TraceLevel has the following values:
1 — Error messages logged
2 — Error and warning messages logged
3 — Error, warning, and informational messages logged
4 — Error, warning, informational and debug messages logged
5 — Error, warning, informational, debug and verbose messages logged
Verifying the Installation19
Editing the Registry
To edit registry data for Recovery Manager:
1.Click Start→Run.
2.Enter regedit in the Run window and click OK.
3.On the left-hand side of the registry window, click
HKEY_LOCAL_MACHINE→SOFTWARE→3par→RM_Exchange.
4.On the right-side of the window, double-click TraceLevel.
5.Modify the Value Data field and click OK to save the change.
Table 3 System Registry Values for Recovery Manager
ValueName
BackupTimeout
RCQueryTimer
The timeout value for the Symantec NetBackup
initialization process detection in minutes. This setting
is optional if the default is not appropriate.
Location of the GUI Log File (Java errors only).GUILog
Recovery Manager Installation path.InstallPath
Path to the GUI jar file.JarPath
The monitoring interval for remote copy progress on the
target server in minutes. This setting is optional if the
default is not appropriate.
Root path to the Recovery Manager repository.RepPath
Number of Trace files to keep before deleting.TraceHistory
The trace level for the log file:Tracelevel
1 — Error messages logged
2 — Error and warning messages logged
3 — Error, warning, and informational messages logged
4 — Error, warning, informational and debug messages
logged
5 — Error, warning, informational, debug and verbose
messages logged
The default value is 5.
The location where the log file resides.TraceLog
NOTE:See “Event Messages” (page 102) for descriptions of events and possible actions to
fix possible problems.
Environment Variables
Installation of Recovery Manager adds the full path to its executables and libraries to the system’s
PATH environment variable. If for some reason this has not been done, neither the GUI nor the CLI
will work. If this is the case, manually add the full paths for the bin and ext directories under
RM_Exchange to the PATH environment variable.
Deinstalling Recovery Manager
CAUTION:Back up your data before upgrading Recovery Manager or all data will be lost. See
“Upgrading to Recovery Manager for Exchange” (page 18) for instructions on performing a backup.
To deinstall Recovery Manager from Windows 2008:
1.Log on as the System Administrator.
20Installation and Deinstallation
2.Click Start→Control Panel→Programs and Features.
3.Select 3PAR Recovery Manager for Microsoft Exchange.
4.Click Uninstall.
NOTE:Removing the Recovery Manager installation will not remove the Recovery Manager
repository for virtual copy management.
Deinstalling Recovery Manager21
4 Configuring Recovery Manager
Configuring the Database
•Be sure to use Exchange files created on basic disks using the NTFS file system. Recovery
Manger does not support other types of file systems.
•Maintain a 1:1 relationship between storage groups and volumes:
Do not add more than one storage group plus its data files to a volume.◦
◦Do not add files from one storage group (including its data files) to multiple volumes.
◦Do not store non-Exchange data on volumes that store Exchange data files.
CAUTION:Be sure to maintain a one storage group:one volume relationship.
Configuring Recovery Manager
Installation Location
By default Recovery Manager installs in %SystemDrive%\Program Files\3PAR\RM\Exchange
Search Path
The Recovery Manager executables are stored in the directory you specify during installation.
Recovery Manager automatically adds the specified directory to the Windows environment variable
PATH; you can therefore issue Recovery Manager CLI commands from any directory.
Changing the Recovery Manager TCP/IP Port
The Recovery Manager listening service on each Recovery Manager Agent component installed
on the mailbox server and Recovery Manager backup server communicates through a TCP/IP port.
By default, Recovery Manager communications use port 9933. If port 9933 is available, no extra
port configuration is necessary.
If port 9933 is not available, you must change the Recovery Manager TCP/IP port.
NOTE:The TCP/IP port used by Recovery Manager for Exchange must be the same on all
associated hosts in the centralized backup configuration.
1.Select an available port. The valid TCP/IP port range is 1024 to 65535.
2.To set a new port number, issue the RMExch portconfig command.
For example, to change the port number to 9950:
RMExch portconfig -h spotted -p 9950
3.Restart the Recovery Manager for Exchange Agent service.
4.Repeat these steps for all associated hosts in the centralized backup configuration.
Configuring Exchange Server Policies
•To use the Recovery Manager GUI to set storage group policies, see “Using the Recovery
Manager GUI” (page 29).
•To use the Recovery Manager CLI to set storage group policies, see “Using the Recovery
Manager CLI” (page 51) for information about using the RMExch policy command.
22Configuring Recovery Manager
Configuring Mount Functionality
The Windows automount feature is not compatible with Recovery Manager. To ensure that the
Windows automount feature is disabled:
1.Open a command prompt (cmd) window.
2.Enter: diskpart
3.At the DISKPART prompt, enter: automount disable
4.Exit the command prompt window.
Configuring Recovery Manager for CCR
Recovery Manager for Exchange supports CCR.
•If your CCR configuration uses a single HP 3PAR Storage System, you can rely on a single
backup server. You do not need to perform any additional configuration steps.
•If your CCR configuration spans two HP 3PAR Storage Systems:
You require two backup servers: one connected to each HP 3PAR Storage System. One
◦
backup server acts as the backup server managed CCR active node, and the other acts
as the peer backup server managed CCR passive node. Both backup servers can execute
Recovery Manager CLI commands.
◦You must use the RMExch peer CLI command to configure the peer backup server as
described in “RMExch peer” (page 65).
◦To display the current configuration, use the RMExch peer display CLI command.
Configuring the Provider
You must use the provider's ProvCfg.exe utility to configure the provider to use the HP 3PAR
Storage System to which each backup server and Exchange production server connects. For more
information, see the provider's user guide.
•If your CCR configuration has one HP 3PAR Storage System, add only that one HP 3PAR
Storage System.
•If your CCR configuration has two HP 3PAR Storage Systems at one site, add both HP 3PAR
Storage Systems to your backup server.
•If your configuration has two HP 3PAR Storage Systems at two sites, add one HP 3PAR Storage
System to each backup server.
For the appropriate configuration diagrams, see “CCR Backup Configuration” (page 15).
Grouping Volumes into Autonomic Groups
You can group virtual volumes into autonomic groups (domain sets, volume sets, or host sets).
Domain Sets
If your Exchange configuration involves multiple storage groups that belong to different HP 3PAR
Virtual Domains, you can use domain sets to group these virtual domains into one HP 3PAR Storage
System domain set. This configuration enables you to use just one Recovery Manager backup
server to manage all your storage groups.
When working with domain sets, keep in mind the following:
•All hosts, users, and virtual volumes must belong to the same virtual domain.
•To mount a virtual copy or media backup to a server that is in a different virtual domain than
the domain in which it was created, you must use the CLI command RMExch mount -h.
•To create a Remote Copy group for a virtual volume that is in a user-defined domain, the
target virtual volume must be in the same user-defined domain.
Configuring Recovery Manager23
To configure domain sets, use CLI commands:
1.Ensure you are running HP 3PAR InForm Operating System Software 2.3.1 or higher.
2.Ensure you have access to all domains.
3.Create a domain set that contains all the virtual domains for all the storage groups.
4.Move the backup server to a domain within the domain set.
5.Create a Command Provisioning Group (CPG) belonging to the new virtual domain.
6.Create a virtual volume belonging to the CPG you just created.
7.Create a host belonging to the virtual domain.
8.Export the VLUN to the host.
9.On the Recovery Manager backup and production servers, set the user for the VSS provider.
10. Ensure the HP 3PAR Storage System connection is good.
Volume Sets
To configure volume sets:
•In a volume set, place one storage group and its log files.
NOTE:For more information on HP 3PAR Command Line Interface (CLI) commands, see the
HP 3PAR InForm OS Command Line Interface Reference. For more information on HP 3PAR
VSS Provider Software, see the HP 3PAR VSS Provider Software for Microsoft Windows User’sGuide.
•Do not place one volume in more than one volume set.
•Do not place unrelated volumes in a volume set.
Host Sets
You can configure your system with host sets and volume sets, or with host sets only.
Configuring Multiple Domains
Multiple domain configurations allow you to use one backup server for multiple Active Directory
domains. You can use a multiple-domain setup with any Recovery Manager for Exchange 2007
configuration.
All multiple domain configurations must follow these rules:
•All backup components (for example, the backup server, the backup software client, and the
Remote Copy target server) must be in the local domain.
•The production servers and the Windows hosts enabled for mounting virtual copies can be in
any domain; local or nonlocal.
For more information about Recovery Manager for Exchange configurations, see “Recovery Manager
Layout” (page 13). For an example multiple-domain configuration, see “Multiple Domain Backup
Configurations” (page 16).
Multiple Domain Requirements
Ensure your domain names follow Microsoft naming conventions for Active Directory and for fully
qualified domain names (FQDN). For more information, see Microsoft documentation on Active
Directory and FQDN naming conventions.
Registering Domains
You do not need to register the local domain. To register an additional domain:
24Configuring Recovery Manager
1.Use the Recovery Manager GUI or the RMExch RegisterDomain CLI command.
For more information, see “Registering Nonlocal Domains” (page 30) or “RMExch
RegisterDomain” (page 70).
2.If you used the CLI command to register the domain, refresh the GUI.
After you register a domain, the Recovery Manager GUI displays the FQDN of the registered
domain in the node tree pane. You can now add storage groups and Windows hosts to the
domain. For more information, see “Managing Domain Components” (page 25).
Modifying Domain Credentials
To modify the credentials stored for a domain, use the Recovery Manager GUI or the RMExchModifyDomain CLI command.
For more information, see “Modifying Domain Credentials” (page 31) or “RMExch
ModifyDomain” (page 63).
Unregistering a Domain
1.Remove all storage groups and Windows hosts from the domain.
Recovery Manager does not allow you to unregister domains that contain Recovery Manager
for Exchange components.
2.Unregister the domain using the Recovery Manager GUI or the RMExch UnRegisterDomain
CLI command.
For more information, see “Unregistering a Domain” (page 31) or “RMExch
UnRegisterDomain” (page 79).
Managing Domain Components
•To use the GUI to manage Recovery Manager operations on storage groups and Windows
hosts in nonlocal domains, use the same GUI procedures as you do for storage groups and
Windows hosts in the local domain.
For more information, see “Using the Recovery Manager GUI” (page 29).
•To use CLI commands to manage storage groups in nonlocal domains, use the same commands
as for storage groups in the local domain and use the -domain option to specify the domain
name.
For more information, see “Using the Recovery Manager CLI” (page 51).
If you do not specify a domain name when you issue a CLI command, Recovery Manager
attempts to execute the command in the local domain.
Configuring the Host Computer and the HP 3PAR Storage System
See the HP 3PAR InForm OS Concepts Guide and the HP 3PAR InForm OS CLI Administrator’sManual for information about configuring the controller nodes on the HP 3PAR Storage System to
communicate with the host computer.
Configuring the Host Computer and the HP 3PAR Storage System25
5 Configuring Backup Software
Overview
HP 3PAR Recovery Manager can be used with either Symantec NetBackup or HP Data Protector
to back up and restore the virtual copies created by Recovery Manager. Keep in mind:
•If you are using backup software in the backup environment, you will need to install a backup
master or client on the backup server.
•There should be two master servers containing your backup software for CCR configurations
that span two sites (and two HP 3PAR Storage Systems).
•If you are using a multiple-domain configuration, you must use Symantec NetBackup software.
NOTE:For information about the supported versions of Symantec NetBackup and HP Data
Protector, see the latest HP 3PAR InForm OS Configuration Matrix. To obtain a copy of this
documentation, go to http://www.hp.com/go/3par/, navigate to your product page, click Supportfor your product, and then click Manuals.
Before You Begin
Ensure that you have set up a storage unit for storing virtual copy backups. For more information,
see the documentation for the backup software you are using.
Configuring Symantec NetBackup
To set up your Symantec NetBackup software, see the Symantec NetBackup documentation.
To configure Symantec NetBackup to function with Recovery Manager for Exchange, set the
following parameters during the configuration process:
Clients
SettingBackup Policy Parameter
MS-Windows-NTPolicy type
Select the machine on which the Recovery Manager Backup
Server component is installed.
User backupType of backup
Activate all the time slots:Starting times for backups
• Modify Day: Mon
• Start Time: 12:00:00AM
• End Day: Sun
• End Time: 12:00:00AM
• Duration (days): 7
26Configuring Backup Software
NOTE:If the Windows Open File Backup option in NetBackup is enabled, the NetBackup client
takes additional temporary read-only (RO) and read/write (RW) snapshots on your base volumes.
After the backup process is complete, Windows displays this event message: Target LUN is
not a 3PAR Virtual Volume.
To deactivate this function, disable the Windows Open File Backup in NetBackup.
NOTE:If you plan on backing up multiple storage groups using NetBackup and Recovery
Manager for Exchange, you need a different policy for each storage group that will be backed
up at the same time. For example, if the first backup of Storage Group One has not finished yet,
in order for the backup of Storage Group Two to be performed correctly by Recovery Manager
for Exchange and NetBackup, it must use a different policy.
For more information on installing Symantec NetBackup, see Symantec NetBackup documentation.
Configuring HP Data Protector
Requirements
•HP Data Protector Software 6.2
•Data Protector patch for omnidl (Patch # DPWIN_00514)
•Each data list name (also known as the backup specification) must be unique across the entire
system
Setting Up the HP Data Protector Backup Specification
To use HP Data Protector with Recovery Manager, you must set up a default backup specification.
The backup specification specifies the default mount point and the necessary devices for tape
backup.
1.Open the Data Protector GUI.
2.Select Backup→Add Backup.
3.In the Create New Backup dialog box, select Blank_Filesystem_Backup and click OK.
4.Click Next (do not select any items).
5.Select the device that Data Protector is to use for backups.
6.Click Next until the Manual add... appears.
7.Click Manual add...
8.Select Windows filesystem and click Next.
9.Enter the appropriate client system, mount point, and description. HP recommends:
<server_used_as_backup_client>Client system
C:Mount point
defaultDescription
NOTE:Recovery Manager uses this information only to create a backup template. Recovery
Manager does not use the actual data entered.
10. Click Next until the Finish button is enabled.
11. Save the backup specification.
When you issue the RMExch backup command with the -dl option, use the name with
which you saved the backup specification (e.g., DPbackup) as the value of the -dl option.
Configuring HP Data Protector27
Setting Up HP Data Protector Cell Manager Access
To use HP Data Protector with Recovery Manager, you must enable the system accounts on the
registered client system to access the Data Protector Cell Manager.
1.Open the Data Protector GUI.
2.In the toolbar drop-down list, select Users.
3.Under the Users folder in the left pane, choose admin, and then choose SYSTEM.
4.In the Client system drop-down list on the General/Properties of the Data Protector User tab
in the right pane, select <Any>.
For more information on installing HP Data Protector, see HP Data Protector documentation.
Using Your Backup Software
•The default mount point for virtual copy backups is:
<system drive>:\3parSnapshot
•You must manually synchronize backups. If a backup expires in your backup software, you
must manually remove the backup from Recovery Manager. If you remove a valid backup
from Recovery Manager, you must manually remove it from your backup software.
•Recovery Manager does not track restore progress. You must use your backup software to
monitor restore progress.
•For more information about using CLI commands with your backup software, see RMExch
backup, RMExch deletebackup, RMExch listbackup, and RMExch restore in
“Using the Recovery Manager CLI” (page 51).
•For more information about using your backup software to back virtual copies up to media
or to restore virtual copies from media, see “Using the Recovery Manager GUI” (page 29).
Using Symantec NetBackup
•Symantec NetBackup software is case-sensitive. If you are using NetBackup, make sure all
information entered pertaining to the policy is supplied with the proper case.
•Any time you are using NetBackup to back up to media or restore from media, you can monitor
•To modify the timeout value for NetBackup software initialization, see “Understanding the
Registry” (page 19).
Using HP Data Protector
For each HP Data Protector backup you create, a postscript (.bat) file is created in the $DP_HOME\
bin folder (where $DP_HOME is the Data Protector install location; for example, C:\ program
files\Omniback.) This script cleans up after the associated backup is complete.
Note that Recovery Manager does not clean these postscripts. After a backup is complete (either
successfully or with failures), you can manually remove the associated postscript batch file if desired.
28Configuring Backup Software
6 Using the Recovery Manager GUI
This chapter provides instructions for using the HP 3PAR Recovery Manager Software Graphical
User Interface (GUI) to back up and restore storage groups.
Overview of the Recovery Manager GUI
Recovery Manager provides a Graphical User Interface (GUI) for backing up and restoring storage
groups at a point-in-time. The Recovery Manager GUI is a windows application, containing a menu
bar, a node tree pane, informational right pane, and a command log window. It provides the
capability to create, remove, mount, unmount, back up, and restore a virtual copy for a storage
group.
NOTE:The GUI is not available for the Recovery Manager Agent for Exchange Server installations.
Menu Bar
The menu bar consists of the following:
•Console menu - allows you to exit the GUI; register the server; and register, modify, and
unregister domains.
•Actions menu - allows you to access virtual copy functionality.
•Scheduled Tasks menu - provides access to the Task Manager.
•About menu - provides an About 3PAR Recovery Manager screen and access to other helpful
links, such as descriptions for event messages that may be generated during operation.
Node Tree Pane
The node tree pane presents the system’s Exchange server. When the Recovery Manager GUI
starts, it analyzes the servers’ domains, storage groups, mailbox information, and virtual copies,
then displays them graphically as a nested tree in the left pane.
Informational Pane
The informational pane displays detailed information about each item selected in the node tree
pane. If the pane’s contents exceed the pane’s width, a scroll bar appears at the bottom of the
pane.
Displaying Domain Information
The node tree pane displays the local domain and its components under the Local Domain node,
directly beneath the MS Exchange node.
If you have configured multiple Recovery Manager domains, the pane displays nonlocal domains
(named as their fully qualified domain names) and their components after the Local Domain node.
Displaying Server Information
Recovery Manager supports Local Continuous Replication (LCR) and Cluster Continuous Replication
(CCR). LCR- and CCR-enabled storage groups are marked with theandicons, respectively,
in the node tree pane. The LCR/CCR column in the informational pane show which storage group
is LCR- or CCR-enabled.
Overview of the Recovery Manager GUI29
Displaying Storage Group Information
To display information about a storage group, click the storage group name in the node tree pane.
In the informational pane, Recovery Manager displays detailed information about the selected
storage group, as described in Table 4 (page 30).
Table 4 Storage Group Information Columns
Updating the Information Displayed
You must manually update the information displayed in the Recovery Manager GUI when:
•You enable or disable LCR or CCR for a storage group.
•In a CCR setup, the active node and passive node pair are switched (for example, a failover
takes place).
To rescan the server:
1.Ensure that the storage group is in a healthy state.
For example, if you are rescanning the server after a failover, the storage group might remain
in the Initializing state for a few seconds.
Displays...Column...
The name of the information store.Store
The type of information store: Mailbox Store or Public StoreStore Type
The status of the data store: Mounted or UnmountedStatus
The location of the EDB (property store) file storeEDB File
2.Right-click the MS Exchange node and select Rescan Server Configuration.
Starting the GUI
To start the Recovery Manager GUI, double-click the 3PAR Recovery Manager for Exchange icon
on your desktop.
Stopping the GUI
To stop the Recovery Manager GUI, select Console→Exit from the menu bar. For more information,
see “Menu Bar” (page 29).
Managing Domains
Working with the Local Domain
•If you are using only the local Active Directory domain, the Recovery Manager GUI displays
all your Recovery Manager components under the Local Domain node.
•If you are using multiple domains, the GUI displays the Recovery Manager components related
to backups—as well as any storage groups and Windows hosts added to the local
domain—under the Local Domain node.
Recovery Manager automatically registers the local domain.
Registering Nonlocal Domains
To register a nonlocal Active Directory domain:
1.Make sure Recovery Manager for Exchange is configured for multiple domains.
For more information, see “Configuring Multiple Domains” (page 24).
2.Right-click the MS Exchange node and select Register Domain.
30Using the Recovery Manager GUI
Loading...
+ 89 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.