-
HP StorageWorks XPFast Recovery Solution
administration guide
XP128 XP1024
XP12000
product version: 2.02
first edition (September 2005)
part number: B9552-96004
This guide describes how to use the fast recovery solution with
Microsoft Exchange 2003.
Windows Server 2003
-
2 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
© Copyright 2005 Hewlett-Packard Development Company, L.P. All
rights reserved.
Hewlett-Packard Company makes no warranty of any kind with
regard to this material, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose.
Hewlett-Packard shall not be liable for errors contained herein or
for incidental or consequential damages in connection with the
furnishing, performance, or use of this material.
This document contains proprietary information, which is
protected by copyright. No part of this document may be
photocopied, reproduced, or translated into another language
without the prior written consent of Hewlett-Packard. The
information contained in this document is subject to change without
notice.
Product names mentioned herein may be trademarks of their
respective companies.
Hewlett-Packard Company shall not be liable for technical or
editorial errors or omissions contained herein. The information is
provided “as is” without warranty of any kind and is subject to
change without notice. The warranties for Hewlett-Packard Company
products are set forth in the express limited warranty statements
accompanying such products. Nothing herein should be construed as
constituting an additional warranty.
Printed in the U.S.A.
HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
first edition (September 2005) part number: B9552-96004
-
Contents 3
About this guide 7IMPORTANT: Software dependencies 7Prerequisite
information 8HP storage web site 8Helpful web sites 8HP technical
support 9HP sales and authorized resellers 9Document conventions
and symbols 10
Revision history 11Warranty statement 12
1 Overview 15FRS features 16
High availability using FRS 16FRS overview 17
Additional FRS capabilities 18Functional components 18Exchange
20HP FRS 20Volume Shadow Copy Service (VSS) 21HP VDS/VSS Hardware
Providers 23HP disk arrays 24
Contents
-
4 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
2 Configuration 25FRS configuration overview 26
Required hardware components 27Required software components
28Important general configuration notes 29Important performance
issues 30Important limitations 30
Configuration summary 31Configuration details 32
Configure production and recovery servers 32Configuring the
Command View XP management station and software
33Configuring the SVP server and software 35Configuring the disk
array 36Important Exchange 2003 configuration notes 41
3 Installation 43Installing RAID Manager Library and HP VSS HWP
44Installing FRS on recovery and production servers 45
Installing integrity checking components 47Enabling the FRS
license using AutoPass 48
Installing a permanent license before trial expiration
48Installing a permanent license after trial expiration 48Permanent
license installation 49Instance count check 51
Recovery server XML files 52Uninstalling FRS 53
4 Using FRS 55Using FRS 56
Opening FRS 56Using the main window 57Adding server instances
59Deleting server instances 60
Creating shadow copies 61Executing an FRS recovery 64
Deleting old point-in-time copies 68Recovery log analysis 69
-
Contents 5
Command line interface 70Available commands 71Example commands
74Command line error codes 77
5 Troubleshooting 79Troubleshooting 80
Checking logs 80Problems/solutions 80HP VSS HWP copies
intermittently fail or time out 83
FRS error messages 84FRS/Exchange backup error messages
84FRS/Exchange recovery error messages 86FRS/Exchange delete
point-in-time copy error messages 87
Glossary 89
Index 93
-
6 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
-
About this guide 7
About this guideThis guide provides information about
configuring and using HP StorageWorks XP Fast Recovery Solutions
(FRS) in a Microsoft Windows Server 2003 environment running
Exchange 2003. FRS enables quick recovery of Exchange storage
groups.
FRS combines LUN copy creation and database recovery features
for use with HP StorageWorks XP disk arrays. Using the Microsoft
VSS (Volume Shadow Copy Service), FRS creates and manages
recovery-ready copies of the production Exchange 2003 storage
groups to be used in the event of damage to a storage group. FRS
allows you to recover storage groups in minutes rather than the
hours typically required for a conventional restore from
backup.
Unless otherwise noted, the term disk array refers to the disk
arrays listed on the title page of this guide. For information
about the disk arrays, please refer to the owner’s manuals.
IMPORTANT: Software dependencies
This guide describes FRS behavior based on features implemented
in the latest disk array firmware and software versions. FRS may
not work if incompatible software versions are used. Check the
README file accompanying the software to verify that you have the
correct versions.
-
8 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003:
Prerequisite information
The instructions in this guide are intended for system
administrators who have the following skills and knowledge:
• A background in direct access storage device subsystems and
their basic functions
• Familiarity with XP and related disk array management software
such as CommandView and Raid Manager
• An understanding of VSS installation and configuration of the
secondary volumes within VSS
• Familiarity with the Windows Server 2003 operating system
• Familiarity with Exchange 2003 administration
HP storage web site
For the most current information about HP StorageWorks products,
visit:
http://h18006.www1.hp.com/storage/enterprisestorage.html.
For information about product availability, configuration, and
connectivity, contact your HP support representative.
Helpful web sites
For third party product information, see the following web
sites:
http://www.hp.com/go/storage
http://www.hp.com/support
http://h18006.www1.hp.com/storage/enterprisestorage.htmlhttp://www.hp.com/go/storagehttp://www.hp.com/support
-
About this guide 9
HP technical support
In North America, call technical support at 1-800-633-3600,
available 24 hours a day, 7 days a week.
Outside North America, call technical support at the location
nearest you. The HP web site lists telephone numbers for worldwide
technical support at: http://www.hp.com/support. From this web
site, select your country.
Collect the following information before calling:
• Technical support registration number (if applicable)
• Product serial numbers
• Product model names and numbers
• Applicable error messages
• Operating system type and revision level
• Detailed questions
For continuous quality improvement, calls may be recorded or
monitored.
HP strongly recommends that customers sign up online using the
Subscriber’s choice web site at http://www.hp.com/go/e-updates.
Subscribing to this service provides you with email updates on the
latest product enhancements, newest drivers, and firmware
documentation updates as well as instant access to numerous other
product resources.
HP sales and authorized resellers
To reach HP sales or find a local authorized reseller of HP
products, call 1-800-282-6672 or visit the HP How To Buy web
site:
http://welcome.hp.com/country/us/en/howtobuy.html
You can also find HP sales and resellers at http://www.hp.com.
Click Contact HP.
http://www.hp.com/support/http://www.hp.com/go/e-updateshttp://welcome.hp.com/country/us/en/howtobuy.htmlhttp://www.hp.com
-
10 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003:
Document conventions and symbols
Caution Indicates that failure to follow directions could result
in damage to equipment or data.
WarningIndicates that failure to follow directions could result
in bodily harm or death.
Table 1. Document conventions
Convention Element
Blue text (Figure 1) Cross-reference links
Bold Menu items, button names, key names, tab names, and group
box names
Italics Text emphasis and document titles
Blue underlined sans serif font (www.hp.com)
Web site addresses
-
About this guide 11
Revision historySeptember 2005 New guide released
-
12 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003:
Warranty statementHP warrants that for a period of ninety
calendar days from the date of purchase, as evidenced by a copy of
the invoice, the media on which the Software is furnished (if any)
will be free of defects in materials and workmanship under normal
use.
DISCLAIMER. EXCEPT FOR THE FOREGOING AND TO THE EXTENT ALLOWED
BY LOCAL LAW, THIS SOFTWARE IS PROVIDED TO YOU “AS IS” WITHOUT
WARRANTIES OF ANY KIND, WHETHER ORAL OR WRITTEN, EXPRESS OR
IMPLIED. HP SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OR
CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY,
NON-INFRINGEMENT, TITLE, ACCURACY OF INFORMATIONAL CONTENT, AND
FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow
exclusions of implied warranties or conditions, so the above
exclusion may not apply to you to the extent prohibited by such
local laws. You may have other rights that vary from country to
country, state to state, or province to province.
WARNING! YOU EXPRESSLY ACKNOWLEDGE AND AGREE THAT USE OF THE
SOFTWARE IS AT YOUR SOLE RISK. HP DOES NOT WARRANT THAT THE
FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET YOUR REQUIREMENTS, OR
THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED,
VIRUS-FREE OR ERROR-FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE
CORRECTED. THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE OF THE
SOFTWARE IS ASSUMED BY YOU. HP DOES NOT WARRANT OR MAKE ANY
REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF THE
SOFTWARE OR RELATED DOCUMENTATION IN TERMS OF THEIR CORRECTNESS,
ACCURACY, RELIABILITY, CURRENTNESS, OR OTHERWISE. NO ORAL OR
WRITTEN INFORMATION OR ADVICE GIVEN BY HP OR HP’S AUTHORIZED
REPRESENTATIVES SHALL CREATE A WARRANTY.
-
About this guide 13
LIMITATION OF LIABILITY. EXCEPT TO THE EXTENT PROHIBITED BY
LOCAL LAW, IN NO EVENT INCLUDING NEGLIGENCE WILL HP OR ITS
SUBSIDIARIES, AFFILIATES, DIRECTORS, OFFICERS, EMPLOYEES, AGENTS OR
SUPPLIERS BE LIABLE FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL,
CONSEQUENTIAL, PUNITIVE OR OTHER DAMAGES (INCLUDING LOST PROFIT,
LOST DATA, OR DOWNTIME COSTS), ARISING OUT OF THE USE, INABILITY TO
USE, OR THE RESULTS OF USE OF THE SOFTWARE, WHETHER BASED IN
WARRANTY, CONTRACT, TORT OR OTHER LEGAL THEORY, AND WHETHER OR NOT
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Your use of the
Software is entirely at your own risk. Should the Software prove
defective, you assume the entire cost of all service, repair or
correction. Some jurisdictions do not allow the exclusion or
limitation of liability for incidental or consequential damages, so
the above limitation may not apply to you to the extent prohibited
by such local laws.
NOTE. EXCEPT TO THE EXTENT ALLOWED BY LOCAL LAW, THESE WARRANTY
TERMS DO NOT EXCLUDE, RESTRICT OR MODIFY, AND ARE IN ADDITION TO,
THE MANDATORY STATUTORY RIGHTS APPLICABLE TO THE LICENSE OF THE
SOFTWARE TO YOU; PROVIDED, HOWEVER, THAT THE CONVENTION ON
CONTRACTS FOR THE INTERNATIONAL SALE OF GOODS IS SPECIFICALLY
DISCLAIMED AND SHALL NOT GOVERN OR APPLY TO THE SOFTWARE PROVIDED
IN CONNECTION WITH THIS WARRANTY STATEMENT.
-
14 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003:
-
Overview 15
1Overview
This chapter presents a technical overview of the HP
StorageWorks Fast Recovery Solution (FRS).
When you have read this chapter, you should have a functional
understanding of FRS that will prepare you to install it and use
it.
-
16 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
FRS featuresHP StorageWorks FRS provides these features:
• Supports HP StorageWorks XP disk arrays
• Provides fast recovery of large Microsoft Exchange 2003
storage groups
• Minimizes downtime from an Exchange corruption
• Independently recovers Exchange storage groups
• Supports multiple instances of production Exchange 2003
servers from a single FRS server (and a single Command View XP
workstation)
• Works with Microsoft Cluster Services
• Includes Command Line Interface (CLI) feature for FRS copy
creation and deletion of point-in-time copies
• Creates and maintains multiple point-in-time recovery LUNs
High availability using FRS
HP provides a total high-availability solution package from
high-end storage to software and support. Fast Recovery Solutions
is part of the high-availability offering, which includes:
• Servers and software
• Disk arrays
• HP StorageWorks Business Copy XP
• HP StorageWorks RAID Manager XP
• CommandView XP
• Fast Recovery Solutions
• Storage consulting services and post-sales total solution
support
-
Overview 17
FRS overview
FRS is a Windows server tool designed to enable fast recovery
when an Exchange storage group maintained on an HP disk array
becomes damaged.
The FRS life cycle can be summarized as follows:
• (1) The production server maintains production storage groups
or databases on specified production volumes of the disk array.
• (2) The FRS GUI runs on the recovery server. It captures
copies of the Exchange storage groups from the production volumes
and stores them on recovery volumes of the array. FRS creates,
maintains, and manages these “recovery-ready” copies.
• (3) When a data corruption occurs, the administrator uses the
FRS graphical user interface to replace the damaged storage group
or database with the most recent known good recovery-ready
copy.
Production Server w/FRS FRS Recovery Server
Disk Array
Secondary
(1) Use Production Server to storeproduction data on array
primary volume.
Copy
Recovery Data (read-only) is routinely available on the
secondary disk for data mining or transport.
(3) In the event of production data damage, restore primary data
from the secondary data using the FRS GUI on the Recovery
Server.
Restore
(2) Use FRS GUI on Recovery Server to copy production data to
secondary array volume.
Store
Primary
-
18 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Additional FRS capabilities
FRS can create and maintain copies of storage groups for
multiple production servers. The FRS user interface allows Exchange
instances to be added or deleted from FRS management at will.
FRS works with Microsoft clustering. Without compromising the
cluster or taking it offline, FRS provides quick database
recovery.
Database integrity checking is included in FRS. FRS interacts
with the Microsoft Exchange eseutil integrity checking tool for
Exchange to check database copies and recovered databases, ensuring
they are free of logical and physical corruption.
FRS performs both point-in-time and roll-forward recovery.
Functional components
The process of creating and managing recovery copies on the disk
array using FRS involves the following components:
• Exchange• HP FRS • Windows VSS Service• HP VSS Hardware
Provider• HP Disk Array System
-
Overview 19
ManagementApplication(s)
Microsoft Volume Shadow Copy Service
Hardware Provider(s)HP VSS Hardware Provider
HP FRS
Disk Array
ManagementApplication(s)
MS Exchange ManagementApplication(s)
HP FRS
Production Server Recovery Server
Microsoft Volume Shadow Copy Service
Hardware Provider(s)HP VSS Hardware Provider
-
20 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Exchange
Exchange runs on the Producton Server and writes data to primary
disk array volumes. FRS protects Exchange by creating and managing
shadow copies of Exchange storage groups.
Software components called “writers” interface with Exchange to
coordinate volume shadow copy creation. Some operating system
writers come with Windows, while others, such as the Exchange
writer, come with the application software.
Upon request from FRS for a shadow copy, the writer flushes the
application buffers and holds I/O to the application. It then
notifies the VSS hardware provider that it is ready for a shadow
copy, and the VSS HWP copies the production volume to a recovery
volume. When the copy is complete, VSS releases the application to
resume normal operation. This process ensures consistent data even
though the application is still running.
HP FRS
FRS consists of two sets of components: one set of production
server components, and a separate set of recovery server
components, including a graphical user interface. FRS as a whole is
referred to by Microsoft as a “requestor” application that requests
service from VSS.
The FRS GUI runs on the recovery server and provides user
control of FRS on the production server. You can use the FRS GUI to
make shadow copies of the data on the production LUNs, and use the
GUI to recover the complete dataset from a copy on the recovery
LUNs.
FRS on the production server interacts with the Windows VSS
service and HP Hardware Provider (HWP). When FRS requests it, this
service and provider combination coordinates with the writer and
application to create a volume shadow copy of the production data
on the production array LUNs.
The complete recovery-ready copy is placed on recovery array
volumes. FRS presents the recovery volumes to the recovery server
through VSS. This enables you to use the recovery server to archive
the recovery data to backup tapes at any time. In the event of
production data corruption, you
-
Overview 21
can use the FRS GUI to restore the production volumes from the
most recent data copy or another point-in-time copy on the recovery
volumes.
Volume Shadow Copy Service (VSS)
Microsoft’s VSS manages creation and maintenance of shadow
copies of production data for backup and recovery. This service
works under the control of the FRS interface and the Windows OS
file system services.
When directed by FRS, VSS coordinates with the writer and
hardware providers to enable shadow copying of production data to
the recovery volumes. The shadow copies contain static copies of
all files, such as databases, transaction logs, and checkpoint
files. Because VSS coordinates copying, the files are copied in a
defined state.
Copy terminology
Understanding how Microsoft VSS terminology corresponds to
standard IT industry terms for data copying makes it easier to
understand what VSS does. The following paragraphs explain the
terminology.
Microsoft generally refers to a VSS copy as a “volume shadow
copy.” When created using HP FRS and HWP, this type of copy is a
static replica of an original volume’s contents. It is keyed with a
GUID to allow identification of the parts of a shadow copy set that
span multiple volumes. Microsoft also refers to a VSS copy as a
“plex,” commonly known in the IT industry as a “split mirror.”
The shadow copies made on the XP array using VSS, FRS, and HWP
are always static, point-in-time copies.
-
22 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
VSS process flow
The following steps show the VSS process flow:
1. A Requestor application (FRS) initiates a Volume Shadow
Copy.
2. FRS requests that the Volume Shadow Copy service create a
shadow copy of a selected set of storage groups.
3. VSS tells the Writer and application to prepare for a shadow
copy. The Writer reports which LUNs to copy, flushes cache, and
holds I/O.
4. VSS tells the disk array through HP HWP to create a shadow
copy of the production storage volume.
5. VSS releases the writer application to resume normal
operations.
6. The Requestor (FRS) presents the recovery LUNs to the
recovery server using VSS, waits for normalization, runs integrity
checking, verifies backup integrity, truncates logs upon success,
and tells the writer that the backup was successful.
Disk Array
Requestor (FRS)
Application(Exchange)and Writer
Virtual Disk ServiceVSS Service
HP HWP
-
Overview 23
HP VDS/VSS Hardware Providers
Windows Server 2003 sees, partitions, mounts, and manages file
systems on the disk array using its own software providers. HP’s
Hardware Providers extend the array management capabilities of
Windows and its applications to include functions normally
performed using the disk array’s proprietary control software.
These functions include managing disk array LUNs and ports and
performing volume copy operations.
HP’s Business Copy (BC) application, which resides on the disk
array and is licensed in Command View XP, works with the VSS and
the HP HWP components to enable the array to make VSS shadow
copies. For functional purposes, you can think of BC as a part of
the hardware providers, even though it is installed separately.
For more information about the HP Hardware Providers, refer to
the HP XP Hardware Providers Administration Guide.
-
24 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
HP disk arrays
To use the XP array with VSS and HP HWP for backup and recovery,
you preconfigure it to contain a number of production volumes where
Microsoft Exchange stores original data. You also configure a set
of recovery volumes where volume shadow copies of the production
volumes are stored.
When FRS requests a shadow copy, VSS, the VSS HWP, and the XP
array work together to create a copy of the production volumes and
place it on the recovery volumes. The copy on the recovery volumes
is a point-in-time copy that is not sychronized to the
original.
If storage groups on the production volumes become damaged, FRS
can be used to perform a recovery. A recovery replaces the data on
the production volumes with a known-good copy from the recovery
volumes. This brings the recovered production database up to the
date and time of the recovery copy. Transaction logs may then be
replayed to bring the recovered production database fully up to
date.
-
Configuration 25
2Configuration
This chapter explains how to configure the Command View XP
workstation, the production and recovery servers, and the disk
array before you install FRS.
If you have not read Chapter 1 Overview to understand how FRS
works, HP recommends that you do so before attempting to install
and use FRS.
-
26 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
FRS configuration overview
The following figure shows a typical XP FRS configuration.
FRS Configuration Diagram XP
Production Server
CommandView
SVP
Recovery Server
Optional corporate LAN connections (TCP/IP)
FC SANFC SAN
FC SAN
Windows 2003Workstation
Private LAN
Disk Array
Optional
FCSwitch
P-VOL and S-VOL must besame size and emulation type.
LUNS
PVOL SVOL
LUN LUN LUN
LUN
LUN
CDEV
COMMAND VIEW STATION SOFTWARE:Command View XP, Business
Copy,Secure Manager, SNMP
PRODUCTION SERVER SOFTWARE:Windows 2003 Enterprise Server
SP1Microsoft Exchange 2003 SP1HP RAID Mgr Library XPHP XP VSS HWP
(VDS is optional)HP FRS
RECOVERY SERVER SOFTWARE:Windows 2003 Enterprise Server SP1HP
RAID Mgr Library XPHP XP VSS HWP (VDS optional)HP FRSExchange
eseutil.exe utilityExchange ese.dll library file
Firewall(Open between CV and FRS servers)
FCSwitch
FC SAN
-
Configuration 27
Required hardware components • HP StorageWorks Disk Array:
XP128, XP1024, or XP12000 with
Business Copy license and Secure Manager XP installed.
• Windows Command View XP management station with Windows Server
2003 or Windows Server 2000 SP4 for connecting to the array. A 2+
GHz CPU, 1 GB of memory, and 1 GB or more of disk space are
recommended. Command View XP must be installed and SNMP must
enabled.
• Production Server with Windows Server 2003 Enterprise Edition
with SP1. This server runs Exchange and manages storage and
retrieval of application data on the production volumes of the
array. Server specifications must meet minimum Microsoft OS
requirements.
• Recovery Server with Windows Server 2003 Enterprise Edition
with SP1. The recovery server contains the FRS GUI and manages the
array recovery volumes and recovery administration. Server
specifications must meet minimum Microsoft OS requirements.
• Fibre Channel Host Bus Adapters (HBAs) in each server for
connecting to the disk array via a Fibre Channel SAN.
• Fiber cables and fabric switch(es) to connect the hosts to the
array. (A fabric switch is optional; you can use direct connections
if you prefer. You can also use multiple switches in a multipathing
arrangement.)
• Ethernet network interface cards or built-in ports in each
server for connecting to Ethernet LANs.
A private LAN without a firewall is recommended between the CV
server, SVP, and the production and recovery servers. You may also
connect the servers to the corporate LAN; in this case a firewall
may be used, but it must be open between the servers if the
corporate LAN is their only means of communication. If you
experience shadow copy timeouts, the firewall is the likely
cause.
Important: The Windows Network Connections control panel
Advanced Settings must be set to list first the network that
provides communication between the FRS servers and the CV
server.
-
28 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Required software components
The following software is required to run HP XP FRS:
IMPORTANT NOTE: Correct software versions are crucial to
operation of FRS. Check the README file for required versions.
Command View XP management station software:• SNMP must be
enabled for SVP communication• Command View XP with Secure Manager
and Business Copy licenses• Access.txt file containing server IP
addresses
Production Server software:• Windows Server 2003 Enterprise
Edition with SP1 • HP SecurePath or HP XP DSM MPIO (if multipathing
is required) • Microsoft Exchange Server 2003 with SP1• HP RAID
Manager Library XP • HP XP VSS Hardware Provider (VDS HWP is
optional)• HP FRS
Recovery Server software:• Windows Server 2003 Enterprise
Edition with SP1• HP SecurePath or HP XP DSM MPIO (if multipathing
is required) • Java Runtime Environment 1.4.2 or later from Sun
Microsystems• Exchange eseutil.exe and ese.dll files in the HP FRS
installation
directory • HP RAID Manager Library XP • HP XP VSS Hardware
Provider (VDS HWP is optional)• HP FRS
Required Microsoft quick fixes (QFEs) for FRS serversThe
following list of QFEs (also called “hotfixes”) is subject to
change; check the README file or contact HP Support for the latest
list of QFEs required for FRS. QFEs must be obtained by downloading
from Microsoft.
-
Configuration 29
For QFEs not available on the Microsoft web site, contact
Microsoft support:
http://support.microsoft.com/contactus/?ws=support.
• KB903650 Extended maintenance mode fix for clusters
• KB891957 VSS hotfix
http://support.microsoft.com/?kbid=891957
• KB892514 Exchange hotfix
http://support.microsoft.com/?kbid=892514
• KB898790 Volume mount point hotfix for clusters
http://support.microsoft.com/?kbid=898790
Important general configuration notes
The following notes will help ensure a successful
configuration:• Production and recovery servers must be in the same
Ethernet domain
so that the DCOM communication process works between
servers.
• On the Command View XP workstation, set NIC binding so the LAN
connecting the production and recovery servers and the Command View
XP workstation has priority (listed first). Reboot the CV
server.
• Administrator privileges are required for all devices and
software. If you do not have administrator privileges, the software
and hardware will not communicate properly. Windows Authentication
is used with FRS to allow applications to share the Windows user
name and password.
• When configuring the array for HWP and FRS you must create a
host group specifically named SVOL and containing recovery LUNs.
(There must be only one SVOL host group on the array.) This host
group should not have any host paths to it.
• Production and recovery volumes must be the same type and
size. There must be at least as many recovery volumes as production
volumes.
• A command device LUN of 36 MB must be defined for each server
running HWP. This LUN cannot be used to store data.
• Port Security must be ON.
http://support.microsoft.com/contactus/?ws=supporthttp://support.microsoft.com/?kbid=891957http://support.microsoft.com/?kbid=891957http://support.microsoft.com/?kbid=892514http://support.microsoft.com/?kbid=898790
-
30 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Important performance issues
These issues can affect FRS performance:
• Excessive traffic on the Ethernet LAN.
• Viruses that slow down network traffic.
• A firewall that slows traffic between the servers hosting FRS
and the CV server. Any firewall must be open between these systems.
If you experience copy timeouts, the firewall is the likely
cause.
Important limitations• FRS supports only basic disk
configuration, not dynamic disks.• FRS supports multiple arrays of
the same model, but all arrays must be
managed using the same Command View XP workstation. • Only one
instance of FRS can run at one time on a server. Run only
one FRS GUI or CLI to prevent simultaneous commands from
different sources.
• FRS supports only a homogeneous disk array solution. If you
want to run FRS on an XP1024 and an EVA6000 disk array, for
example, you will need two mutually exclusive recovery servers—one
per disk array with no shared components.
• FRS does not support CVS volumes• Command devices must not be
configured as production or recovery
LUNs.
-
Configuration 31
Configuration summary
Before you install FRS, configure the array and the FRS servers
as follows:• Install and configure the FRS production server(s) and
recovery
server(s) with Microsoft Windows Server 2003 Enterprise Edition
with SP1. Install any required Microsoft quick fixes (QFEs)
also.
• Install JRE 1.4.2 or later from Sun on the recovery
server(s).• Establish SAN and LAN connectivity between all servers
and the disk
array. Any firewall must be open between the FRS production and
recovery servers, the CV management station, and the disk
array.
• If path redundancy is required, install HP SecurePath or HP XP
DSM MPIO on all production and recovery servers.
• On the production server, install and configure the Exchange
server software.
• On the Command View XP management station, install Secure
Manager XP and Business Copy XP licenses.
• List production and recovery server IPs in the Command View XP
management station access.txt file.
• List CV station IP on SVP snmpagt.exe manager page (if
required).• On the XP disk array, create at least two production
LUNs and present
them to the production server. Create a host group called “SVOL”
and create within that host group at least two recovery LUNs of the
same emulation type and size as the production LUNs.
• On the XP disk array, create command device LUNs and present
them to the production and recovery servers.
• Ensure databases or mailboxes within a given storage group all
reside on the same LUN, and ensure log files reside on the same LUN
as the associated databases or storage groups.
• Install HP RAID Manager Library software on production and
recovery servers.
• Install HP VSS Hardware Provider on production and recovery
servers. • Install HP FRS software on production and recovery
servers.• On recovery servers if Exchange is not installed, copy
the Exchange
eseutil.exe and ese.dll files to the HP FRS installation
directory.
-
32 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Configuration details
Configure production and recovery servers
The production server hosts Exchange and manages the production
LUNs on the disk array where Exchange production data is stored.
The recovery server hosts the FRS GUI and manages the array
recovery LUNs where copies are stored. Configure the servers as
follows:
Install Windows OS, Exchange, and other software:
1. If it is not already present, install the Windows Server 2003
Enterprise Edition OS with SP1 on the production and recovery
servers according to Microsoft’s installation instructions. Be sure
to install required Microsoft quick fixes (QFEs) listed in the FRS
README file.
2. Install JRE 1.4.2 or later from Sun Microsystems on the
recovery server.
3. If redundant servers are planned, install HP SecurePath or HP
XP DSM MPIO on all FRS servers according to the documentation.
4. Install Microsoft Exchange Server 2003 with SP1 on the
production server according to Microsoft’s instructions.
5. Copy the Exchange eseutil.exe and ese.dll files to the HP FRS
installation directory on the recovery server after installing FRS.
Without these files, integrity checking and copying fails.
Make SAN and LAN connections:
6. Connect the FRS production and recovery servers and the
Command View XP management station to an ethernet LAN. Any firewall
must be open between the FRS servers and the Command View XP
management station. Use a ping command to test communication.
7. Install Fibre Channel host bus adapter (HBA) cards, driver
software, and utility software onto the FRS production and recovery
servers according to the HBA manufacturer’s instructions. HP tested
drivers are available from your HP support representative.
8. Connect the servers to the disk array through the HBAs, using
either FC direct-connect or a fabric switch and SAN topology.
-
Configuration 33
Configuring the Command View XP management station and
software
Install and configure the Command View XP management workstation
with the Command View XP software as explained in the Command View
XP Installation Guide. SNMP must be enabled (see Windows Help).
Follow these additional Command View XP configuration steps:
1. Connect the Command View XP workstation to the SVP and the
FRS servers via an ethernet LAN (if this has not already have been
done).
2. In the access.txt configuration file in the following
location, enter the private IP addresses of the FRS production and
recovery servers:
drive\HPSS\dm\tomcat\webapps\hpstmgmt\WEB-INF\cvapi\config
(drive is the hard drive where Command View XP is
installed.)
For example, enter:
Localhost15.75.*.*15.106.*.*
Localhost is the Command View XP management station. Using
wildcards in the server addresses (*) provides any server in the
subnets 15.75 and 15.106 access to the array through Command View
XP. If you prefer to give access only to the FRS hosts, enter their
complete IP addresses without wildcards.
-
34 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
3. On the Command View XP workstation in the Windows Network
Connections control panel, select Advanced/Advanced Settings. In
the Advanced Settings display, set network bindings so that the LAN
Command View XP will use to access the production and recovery
servers appears first in the Adapters and Bindings/Connections
list.
Important: If you change network bindings, you must reboot the
CV station for the new setting to take effect
When you have completed the steps above, Command View XP should
have access to the production and recovery servers. At the CV
management station command line prompt you can use a ping command
to test access to all servers.
4. Enable Business Copy and Secure Manager licenses in Command
View XP as explained in the Command View XP User Guide.
-
Configuration 35
Configuring the SVP server and software
The HP service representative configures the SVP as part of disk
array installation, which may include the following SNMP agent
configuration steps.
This procedure gives the specified Command View XP management
station exclusive control of the array. If you need access to the
array from multiple CV XP stations, skip this procedure.
1. (HP representative only) On the SVP, open a command line
window.
2. (HP representative only) At the command prompt, type
snmpagt.exe to display a dialog window with a property sheet.
3. (HP representative only) From the manager page, enter the IP
address of the Command View XP management workstation.
4. (HP representative only) Reboot the SVP.
-
36 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Configuring the disk array
Configure the disk array as follows. Many of these steps repeat
what you may have already done when installing HP HWP; however,
additional steps are included near the end of the procedure; read
carefully.
Illustrations and instructions are for Command View XP 2.0.
Significant differences for Command View XP 1.8 are given in
parentheses.
1. Log into Command View as an administrator (the default
administrator user name and password is administrator).
2. Click Array Manager in the left panel and click the Device
Launcher tab (v1.8 click the Main tab and Overview tab).
3. Click the array name in the Device Name column to select the
array you want to access.
The array management window appears.
-
Configuration 37
4. Select LUN Manager in the left panel (v1.8 LUN and Volume
Management tab).
5. Configure the disk array Fibre Channel ports connected to the
production and recovery servers as follows:
Click on the Port tab. Choose the port from the Select a Port
drop down menu.
Use the Fabric and Connection drop down menus to set up the
port. Settings depend on how the array is connected to the servers.
See the following table for the meanings of selections.
-
38 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Click Set and a dialog pops up to confirm the change. Click OK.
The port list above shows the Connection in italics to indicate it
is pending.
Click Apply to confirm the port changes. A dialog asks you to
confirm. Click OK. A completion message pops up; click OK
again.
6. Click the LUN Manager tab to open the LUN management window.
You will use this window to configure LUNs.
Port Fabric and Connection settings
Fabric Parameter
Connection Parameter Provides
OFF FC-AL NL-port (private arbitrated loop) ON FC-AL NL-port
(public loop) for loop
connection to a switchON POINT-TO-POINT N-port (fabric port) for
connection to
a switchOFF POINT-TO-POINT Not supported
-
Configuration 39
7. In the LUN Manager window LU Path panel, right click on the
port connected to the VDS/VSS server(s) and select Add New Host
Group. The Add New Host Group window opens.
8. Create the host groups and set the Host Mode for the ports
connected to the production and recovery servers and click OK.
Create a host group of any name for the primary data volumes, and
create a host group named SVOL for the secondary volumes.
Important: The SVOL host group must not have any host paths.
These are established later when you install and configure FRS.
The Host Mode for Windows Server 2003 is 0C or 2C. Make sure
both servers use the same mode.
9. In the LUN Manager window, turn LUN security ON for the ports
connected to the production and recovery servers: Right click on
the port in the LU Path tree and select LUN Security ON. Click Yes
when the confirmation window appears, and click Apply. This applies
LUN security to the port, indicated by a key symbol on the port
symbol.
10. After enabling LUN security, add the production server HBA
WWNs to the production FRS host group ONLY: In the LU Path tree,
right-click the host group and select Add New WWN. In the pop-up
window, enter the New WWN and Nickname for the production server
HBA and click OK. DO NOT add host WWNs to the SVOL host group.
Assigning the production server HBA WWN to the production host
group associates that server with the group, allowing the server
access to the host group’s LUNs. Access to the SVOL host group for
the recovery server will be provided by the HP VSS HWP
configuration utility later when you install the FRS software.
-
40 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
11. In the LUN management window, create one Command Device LUN
(CDEV) of at least 36 MB (larger is OK but wastes space) for each
server. This LUN must be mapped to a port that is visible to the
server. The CDEV LUN is used for interpreting commands and cannot
be used for data.
To designate a LUN as a command device:
Right click on the LUN and select Command Device ON.
Command Device LUNs can be any number but are customarily
assigned a number near the end of the available range. You can use
a VSC volume for a Command Device, but do not use a LUSE
volume.
12. In the LUN management window, add LUNs to the new host
groups. For Exchange, you will need a minimum of two production
volumes: one for Mailstore (shared) and one for log files (storage
group level).
You must create at least the same number of identical recovery
LUNs to match the number of production LUNs. The recovery LUNs must
be the same emulation type (OPEN-3, OPEN-9 etc.) and the same size
in GB as the production LUNs. Recovery LUNs MUST be in a host group
named “SVOL”.
To add a LUN:
Click the LUN you wish to define in the right panel. Select an
LDEV in the lower right panel. Then click Add LU Path. A
confirmation dialog pops up; click OK and the LUN is added with a
path to the selected LDEV. Click Apply to confirm the added
LUN.
Windows limits LUNs to the range of 00 to FE, so be sure not to
use a LUN number above FE.
Windows 2000 requires a LUN 0 in order for LUNs greater than 7
to be recognized by the OS. Windows Server 2003 with SCSIPort
Miniport Driver requires a LUN 0 in order to recognize any
additional LUNs.
-
Configuration 41
Important Exchange 2003 configuration notes
FRS works within the limits of Exchange 2003. No more than five
databases per storage group and no more than four storage groups
per Exchange instance are supported.
FRS manages Exchange 2003 at the storage group level. The
following configuration rules apply:
• All databases within a storage group must reside on one LUN of
the HP disk array. Databases cannot be separated onto different
storage LUNs.
• The logs for each storage group must also reside on an HP disk
array LUN, and the logs and the checkpoint file must remain
together on the same LUN.
The LUN that the databases reside on and the LUN that the logs
reside on must NOT be the same LUN.
-
42 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
-
Installation 43
3Installation
This chapter covers installing, uninstalling, and licensing FRS.
You must use Administrator privileges for all hardware and software
to perform these tasks.
Before you install FRS, you must complete the server and array
configuration tasks presented in Chapter 2. If you have not yet
done so, go to Chapter 2 and complete those tasks now. A summary of
configuration is presented on page 31. Then return to this chapter
and follow the installation instructions.
-
44 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Installing RAID Manager Library and HP VSS HWP
Before you install FRS, install RAID Manager Library and the HP
VSS Hardware Provider as explained below:
Install HP RAID Manager Library software
1. Install the HP RAID Manager Library software on each
production and recovery server. See the RAID Manager Library
documentation if you need help with this task.
Install HP VSS Hardware Provider
2. Install HP’s XP VSS Hardware Provider on each production and
recovery server according to the HP StorageWorks XP HWP
Administration Guide.
-
Installation 45
Installing FRS on recovery and production servers
FRS is required on all servers participating in FRS. This
includes the recovery server and all production servers.
The installation steps for each production or recovery server
are nearly identical, except for the Custom Setup window:
1. Download FRS from the hp.com web site or open the FRS CD and
launch the ISScript8.Msi file. This will ensure that a script
engine is available for the installation process.
2. Click Next and read the license agreement.
3. Click “I accept” and click Next.
4. Click Install to install ISScript on the server.
5. When ISScript installation completes, click Finish.
hp.com
-
46 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
6. Launch the HP StorageWorks Fast Recovery Solution.msi file.
The installation wizard opens.
7. Click Next. The Custom Setup window opens.
8. Choose Change... to select a directory where the program will
be installed, or use the default location shown under Install
to:.
9. Select the type of server software you want to install:
To install on a PRODUCTION server: Click the Production Server
drop down menu, and select “This feature will be installed on local
hard drive”. Then click the Recovery Server drop down menu and
select “This feature will not be available.” The recovery server
icon is marked with an “X”, which means it is NOT being
installed.
To install on a RECOVERY server: Click the Recovery Server drop
down menu, and select “This feature will be installed on local hard
drive”. Then click the Production Server drop down menu and select
“This feature will not be available.” The production server icon is
marked with an “X”, which means it is NOT being installed.
-
Installation 47
10. Click Next.
11. Click Install. Installation begins.
12. When installation completes, click Finish.
13. Repeat the installation on all additional servers
participating in FRS. Be sure to select the correct server icon
each time and to deselect the unwanted icon so that it is marked
with an “X”.
Installing integrity checking components
For Exchange integrity checking to work, you must copy the
Exchange eseutil.exe and ese.dll files to the HP FRS installation
directory on the recovery server. These files are located in the
Exchange directory: c:\program files\exchsrvr\bin. If these files
are not present in the FRS directory on the recovery server, backup
fails.
-
48 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Enabling the FRS license using AutoPass
FRS offers a free trial license period of 60 days. When the
trial period is over, you must install a permanent license using
AutoPass within the FRS GUI in order to continue using FRS. The
procedure for starting the permanent licensing process is different
depending on whether your trial license has already expired or not.
Use one of the two procedures below to install the permanent
license.
Installing a permanent license before trial expiration
If you are installing a permanent license before the trial
license expires, a command line application called
ImportLicense.exe allows you to install the license:
1. Locate and double click the ImportLicense.exe executable file
to run it. The path to this file is
Start>Programs>Hewlett-Packard>HP StorageWorks Fast
Recovery Solution>Import Permanent License.
The AutoPass: Import Passwords screen displays.
2. Follow the procedure for “Permanent license installation” on
page 49.
Installing a permanent license after trial expiration
When you start the FRS GUI, a window notifies you how many days
remain before your trial version of the software expires.
If your AutoPass trial version license has expired, this message
appears:
1. Click Yes to install the license (or click No to exit
FRS).
2. Follow the procedure for “Permanent license installation” on
page 49.
-
Installation 49
Permanent license installation
Important: If you have multiple FRS instances, be ready to
import all license passwords for all instances in one session. If
you quit AutoPass while some licenses are still without passwords,
all licenses will fail, and AutoPass will have been overwritten and
disabled by the partial license file.
Use the following procedure to install the permanent
license:
1. When you click Yes on one of the preceding license
notification windows, the AutoPass: Import passwords window
opens.
2. Click the Browse button to locate the license file. The file
path shows in the file path text entry box.
3. Click the View file contents button to display the passwords
stored in the license file.
-
50 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
4. Click the password file in the display to highlight it (as
shown above).
5. Click Import to import the selected password file.
The message below indicates a successful password import.
6. Click OK. This completes permanent license installation.
Important: If you need to install multiple licenses, you must
repeat this process for each license password. It is not possible
to import multiple passwords at one time.
Also, be sure you have imported all licenses before closing
AutoPass. If some licenses are left without passwords, all licenses
will fail.
-
Installation 51
Instance count check
If you are running too many instances of FRS for the license you
own, you may receive a warning message. This message appears under
the following conditions:
• The recovery server is connected to a production server
running more than the licensed number of instances.
• A recovery server is connected to multiple production servers
and the total number of Exchange instances running are more than
the licensed capacity.
• The product is already running the maximum number of instances
when you try to add another instance by clicking Add Exchange
Server Instance from the File menu.
Contact HP if you need to add more instances to your
license.
-
52 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Recovery server XML files
FRS stores the recovery volume information in the form of XML
files. By default these files are created in the install directory.
It is not necessary to change the location of the XML files, but
should you wish to do so, you can place these files in a different
directory.
Important: If you change the location of the XML files after
snapclones have already been created, the FRS GUI will not be able
to find them, so HP recommends changing the location before you
create any snapclones.
The following procedure explains how to change the location of
this directory:
1. Start FRS on the recovery server by clicking
Start>Programs>Hewlett-Packard>HP StorageWorks Fast
Recovery Solution>FRS GUI.
2. Click the ShadowCopy menu and click Options.
The Options window containing the default location appears.
3. Click Browse, browse to a directory of your choice, and click
OK.
4. Click OK in the Options window to change the default XML file
path.
-
Installation 53
Uninstalling FRS
You can uninstall FRS in one of three ways: by using the FRS CD,
by using the Uninstall FRS shortcut, or by using the Windows
Add/Remove Programs feature in the Control Panel.
With each method, the uninstall script prompts you to remove
FRS.
To uninstall FRS with the CD:
Open the FRS CD. Click setup.exe to launch the uninstall script
and follow the prompts.
To uninstall using the Uninstall FRS shortcut:
Click Start>Programs>Hewlett-Packard>HP StorageWorks
Fast Recovery Solution>Uninstall FRS, and follow the
prompts.
To uninstall using Add/Remove Programs:
1. Click the Start menu, click Settings, click Control
Panels.
2. Open Add/Remove Programs.
3. Find the HP StorageWorks Fast Recovery Solution entry and
select it.
-
54 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
4. Click Remove to launch the uninstall script.
A confirmation window asks “Are you sure...”
5. Click Yes to remove FRS from the server. The removal process
takes a few minutes.
-
Using FRS 55
4Using FRS
The following items are explained in this chapter:
• Using FRS
• Creating shadow copies
• Executing an FRS recovery
• Using the command line interface
-
56 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Using FRS
You operate FRS from the graphical user interface that was
installed on the recovery server when you installed FRS. The
following pages explain how to open and use the FRS GUI to add and
delete servers, make shadow copies of production storage groups and
restore production storage groups and databases from shadow
copies.
Opening FRS1. On the recovery server, click Windows Start, and
select Programs.
2. Click Hewlett-Packard, click HP StorageWorks Fast Recovery
Solution, and click HP FRS GUI.
The FRS main window opens.
-
Using FRS 57
Using the main window
The following example shows the FRS main window after two
Exchange 2003 server instances have been added. Adding server
instances is explained later in this chapter.
-
58 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
To expand a server instance:
1. Click the plus symbol (+) next to a server instance in the
left panel of the main window. This displays the detail views of
the production storage groups and/or databases associated with that
server instance.
2. Click a storage group or database to display the location and
path of the LUN where it is stored in the right panel of the main
window.
-
Using FRS 59
Adding server instances
Add Exchange production server instances whose storage groups or
databases you want FRS to be able to copy and restore. The servers
must have FRS installed on them for the GUI to recognize them:
1. On the FRS main window, click the File pulldown menu and
click Add Exchange Server Instance.
The Add Server Instance window opens.
2. Enter the instance name in the “Enter Server Instance” box
and click OK.
The FRS main window opens and shows the new server instance.
-
60 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Deleting server instances
If you no longer need to use FRS with a particular server, you
can delete it from the FRS GUI. This does not affect the server
itself but only removes it from the list of servers available in
the FRS main window.
1. Click the server instance to highlight it.
2. Click File and click Delete Server Instance. A confirmation
window opens.
3. Click Yes to confirm your choice.
-
Using FRS 61
Creating shadow copies
The primary feature of FRS is creating shadow copies of
production LUNs. FRS then manages these copies. If a production
database is lost because of a failure or catastrophic event, FRS
restores the production database from a shadow copy.
To create shadow copies of production LUNs:
1. Click the production server instance, storage group, or
database you want to copy. The example below shows Exchange 2003
Server “N03” selected.
2. Click ShadowCopy in the menu bar, and select Create Shadow
Copy.
The Create shadow copy window opens.
-
62 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
3. Select the storage group to be copied and click Add. Repeat
as needed.
The storage group to be copied appears in the “Selected for
shadow copy” list, and the associated databases appear in the
“Files/Volumes selected for shadow copy” list.
-
Using FRS 63
4. Click Create at the bottom of the Create shadow copy window.
Storage group copying begins. The copy is placed on a volume in the
recovery storage group you identified when you installed FRS.
The Activity Log shows the stages of copying and their success
or failure, ending with a completion message.
5. When copying ends, click Close to close the window. FRS now
has a recovery-ready LUN containing the shadow copy of the storage
group or database. You can create shadow copies as often as
needed.
Troubleshooting copy failures:
If a copy fails, you may be able to troubleshoot the cause by
examining the copy activities shown in the Activity Log to see
which activities failed. Failed Exchange copies can often traced to
a failed integrity check performed automatically on the storage
group by the Microsoft Exchange eseutil.exe utility.
-
64 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Executing an FRS recovery
Use the Recovery feature to restore a production storage group
from an FRS shadow copy.
1. Click Recovery on the main window menu bar, and select
Roll-Forward Recovery or Point-in-Time Recovery.
Roll Forward Recovery
Use Roll Forward Recovery if the production storage group's
database(s) becomes damaged but the storage group's transaction
logs are known to be unaffected. This recovery method replaces the
production storage group's database LUN with the latest known-good
shadow copy but does not replace the production transaction log
LUN. During the recovery, Exchange replays the production logs to
fully restore the production databases up to the last logged
transaction prior to the point of failure. A Roll Forward Recovery
only works with the most recent Point-in-Time shadow copy.
Point-in-Time Recovery
Use Point-in-Time recovery if the production storage group's
transaction logs are damaged. This recovery method replaces the
production storage group and production logs with the point-in-time
copy that you select. A Point-in-Time recovery will cause you to
lose
-
Using FRS 65
all data created after the Copy Date and Copy Time of the
selected shadow copy.
After you select a recovery method, the Recover Storage Group
window opens and indicates the type of recovery in the window name.
The copies available for selection differ in this window depending
on whether you selected Roll Forward or Point-in-Time.
-
66 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
2. Click on the production storage group you want to recover in
the Select Storage Group panel.
A list of point-in-time shadow copies displays in the
Point-in-Time copies panel. The contents of the list depends on
whether you selected Roll Forward or Point-in-Time.
3. Click the point-in-time copy you want to use to restore the
production storage group.
Note: The point-in-time recovery dialog shows only the
point-in-time copies residing in the user specified xml file path.
If you want to see the point-in-time copies in other directories
you must change the xml file path to point to those
directories.
4. Select LUN Swap or Full Resync.
Full Resync replaces the production data on the production LUN
with the most recent copy from the recovery LUN by copying the data
back to its original location. For servers in a cluster, only Full
Resync is allowed.
LUN Swap reverses roles of the LUNs and turns the recovery LUN
into the production LUN, and the production LUN into a recovery
LUN. This is the fastest option, producing almost immediate
results. After a swap, you may need to create additional recovery
LUNs before you can make new shadow copies. For servers in a
cluster, LUN Swap is not allowed.
Caution When you select LUN Swap, the Delete Production Volumes
after swap checkbox is enabled. Selecting this checkbox deletes the
production volumes after the swap, which irreversibly deletes your
production data.
Important: Use swap only temporarily if your recovery LUNs
reside on less reliable external storage disks because these less
reliable disks become the production LUNs. To swap disks back
again, use Business Copy within Command View XP to create copies of
the current production LUNs in the original production disk group.
Then present the copied LUNs to the production server, assign drive
letters, and update the database and log path within Exchange.
Delete Selected Copy deletes the selected point-in-time copy
without waiting until after the recovery.
-
Using FRS 67
5. Click Start Recovery. The recovery process begins.
Progress of the recovery displays in the Activity Log panel.
6. When the log panel shows the recovery is finished, click
Close to close the window. Your recovered production LUN should now
be ready to use again.
-
68 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Deleting old point-in-time copies
Using the procedure below, you can delete old point-in-time
copies any time your pool of Point-In-Time copies grows too large.
HP recommends you delete the oldest copy first, followed by the
next oldest, and so on.
1. Click Recovery on the main window menu bar, and select
Point-in-Time Recovery.
2. Click on a production storage group in the Select Storage
Group panel.
A list of point-in-time shadow copies displays in the
Point-in-Time copies panel.
-
Using FRS 69
3. Click the point-in-time copy you want to delete, and click
Delete Selected Copy. FRS deletes the copy immediately.
4. Click Close when copy deletion is finished.
Recovery log analysis
If a recovery fails, analyze the Activity Log in the FRS GUI for
any failed activities.
-
70 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Command line interface
The following pages describe the FRS command line interface.
1. Change to the directory (cd) where FRS is installed. The
default location is C:\Program Files\Hewlett-Packard\HPFRS.
2. Type this command, and press Enter:
dir
A list of files and subdirectories in the hpfrs directory is
presented.
-
Using FRS 71
Available commands
Type C:\Program Files\Hewlett-Packard\HPFRS>hpfrscli /? to
see a listing of available FRS commands.
-
72 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Command usage
hpfrscli.exe
Microsoft Exchange Server:
addcopy Create a point-in-time copydelcopy Delete a
point-in-time copylistcopy List all point-in-time copies/? Displays
the current usage screen
Creating a point-in-time copy:
hpfrscli addcopy
/EXCHANGE
/SERVER=
/SG=
[/AUTOCLOSE={ON|OFF}]
[/OUTPUT=]
Deleting a point-in-time copy:
hpfrscli delcopy
/EXCHANGE
/SERVER=
/XMLFILE=
[/AUTOCLOSE={ON|OFF}]
[/OUTPUT=]
-
Using FRS 73
Listing the point-in-time copies:
hpfrscli listcopy
/EXCHANGE
/SERVER=
/SG=
[/AUTOCLOSE={ON|OFF}]
[/OUTPUT=]
/EXCHANGE: Connect to an Exchange Server Instance
/SERVER: Specifies the Server Instance name to be connected
to
/SG: Specifies the list of Exchange storage groups separated by
a comma
/XMLFILE: Specifies the XML filename (with path) of the
point-in-time copy
/AUTOCLOSE: If set to ON, automatically closes the activity
window on task completion. The default value is OFF. If set to OFF,
press Enter to close the activity window
/OUTPUT: [drive:][path] filename. Specifies the filename to save
the activity log
-
74 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Example commands
Three examples follow to demonstrate the addcopy, listcopy, and
delcopy commands.
Creating a copy
The following “addcopy” command creates a point-in-time copy of
a storage group (sg1) on a selected Exchange server instance
(phill).
C:\Program Files\Hewlett-Packard\HPFRS>hpfrscli addcopy
/exchange /server=phill /sg=sg1
The screen displays progress as the copy is made.
-
Using FRS 75
Listing copies
The following “listcopy” command lists point-in-time copies of a
storage group (sg1) on a selected Exchange instance (phill).
C:\Program Files\Hewlett-Packard\HPFRS >hpfrscli listcopy
/exchange /server=phill /sg=sg1
The following screen example shows the list of point-in-time
copies of storage group “sg1” on selected Exchange instance
“phill.”
-
76 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Deleting a copy
The following command deletes a copy of a selected XML file
(evs1_sg1_07-26-2005_09-20-31.xml):
C:\Program Files\Hewlett-Packard\HPFRS>hpfrs delcopy
/exchange /server=phill /xmlfile=C: \Program Files\
Hewlett-Packard\HPFRS\phill_sg1_08-30-2005_23-57-09.xml
The figure shows the deletion in progress.
-
Using FRS 77
Command line error codes
FRS CLI issues a return code indicating success or failure of
the operation performed. Upon failure, error codes are returned
indicating the type of failure. The following example shows a 0
code being returned, indicating a successful operation.
The return codes for the supported operations are:
[0] The operation displayed in the usage screen (create shadow
copy, delete point-in-time copy or listcopy) succeeded.
[1] The specified operations failed with a win32 error
[1001] Incorrect command line parameter entered by the user
[1002] Missing command line parameter entered by the user
[1003] Create shadow copy operation failed.
[1004] Delete point-in-time copy operation failed.
[1005] Listcopy operation failed.
-
78 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
-
Troubleshooting 79
5Troubleshooting
This chapter explains how to maintain Fast Recovery Solutions
(FRS) on an XP disk array and troubleshoot problems or error
messages.
-
80 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Troubleshooting
The following pages present typical problems and solutions as
well as suggested testing methods.
Checking logs
Checking event logs is often the first step when trying to
identify problems. Error messages in the logs may indicate the
problem.
• Check application event logs associated with Exchange, FRS,
and HP VSS Hardware Provider.
• Check Windows system event logs for DCOM misconfiguration
errors.
Common problems and solutions are also listed below.
Problems/solutions
The following problems and solutions may help you if you have an
issue with FRS or the associated systems and software.
FRS does not recognize LUNs
This is almost certainly a configuration problem. See Chapter 2
Configuration and look for the following most likely problems:
1. LUNs may not be properly set up for copying and recovery.
Production LUNs must be created, and an equal or greater number of
recovery LUNs of the identical size and emulation must also be
created.
2. The recovery LUNs may not be in a host group named SVOL on
the array, which is a requirement of HP VSS HWP.
3. Production server WWNs may not have been associated with
array ports. This is required for the array to recognize the
server.
4. LUN security may be off. LUN security must be ON for
production and recovery LUNs.
-
Troubleshooting 81
FRS runs but produces no results
If the FRS GUI runs and recognizes the recovery LUNs but will
not make shadow copies or perform recoveries, check the
following:
1. Ensure the HP Business Copy license and the HP VSS Hardware
Provider were installed and correctly configured.
A simple way to verify the HP VSS HWP is installed correctly, is
to see if it is running. At the command line, enter:
vssadmin list providers
Look for the HP VSS HWP in the resulting list.
2. Check Cluster Administrator and verify resources are
online.
3. Check that the Exchange server is online. Check that the
Exchange server can access the data LUNs via My Computer.
4. Check for mount points found under the FRS directory. All
databases under the selected storage group must be in a mounted
state.
5. Check configuration as explained in Chapter 2
Configuration:
(A) Check Command View XP server and FRS production and recovery
server connectivity and communication. Use the ping command to
check communication. If communication fails, check LAN priority in
the Network Connections control panel Advanced Settings window on
all servers, and also check Windows Distributed COM settings as
explained in Microsoft’s documentation.
(B) Production/recovery servers not connected to the SAN
correctly.
(C) Firewall between the Command View XP management station and
the production/recovery servers. If you are receiving shadow copy
timeout errors, this is the likely cause.
6. In order for the production and recovery servers and their
applications to communicate, the Windows DCOM distributed
communication process must be able to communicate among all
production and recovery servers. This requires that you be logged
into all FRS-related applications and all FRS servers (including
Command View XP) as an administrator and requires an open firewall
between servers. You can check for DCOM errors in the system event
logs.
-
82 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
7. Check the Command View XP management station for errors
associated with the array.
8. If Exchange copies fail because of a failed integrity check,
verify that eseutil.exe and ese.dll are installed on the recovery
server. Integrity checks will not work without them, and a failed
integrity check causes a failed copy.
9. The VSS Hardware Provider may not be able to make the copy
because it has run out of copy space. Return to the disk array to
create more shadow copy LUNs and then run the HP XP VSS Hardware
Provider Configuration Utility (in Windows
Start/Programs/Hewlett-Packard) to repopulate the configured
LUNs.
10. Supporting software may not be installed or configured
properly. Verify configuration and installation as explained in
chapters 2 and 3.
11. Use a process of elimination to determine which components
are not working. You can do this by testing components
individually:
• Test VSS by creating a shadow copy on a local drive using the
Windows Disk Management/Shadow Copy feature. See Windows Help for
instructions.
• Test array copy capability by using Business Copy to create
PVOL and SVOL pairs and copy the PVOL to the SVOL. See the HP
StorageWorks Business Copy User Guide for instructions.
• Bypass FRS and test VSS, HWP, and the array by using the
Microsoft vshadow utility available in the Microsoft VSS Software
Developer’s Kit to create snapshots. See the Microsoft
documentation for instructions. If you can create snapshots without
FRS, FRS may not be properly installed or configured.
-
Troubleshooting 83
HP VSS HWP copies intermittently fail or time out
If FRS sometimes works to create recovery copies and other times
it does not, the problem may be due to the time restriction on
snapshots. VSS allows only 30 seconds for the entire snapshot
process, including only 10 seconds for actually making the copy.
This narrow time window can cause any limitation in your system to
hamper successful snapshots. The following issues may affect
FRS/VSS performance:
• Firewall or LAN traffic slowing or preventing communication.
Reconfigure the firewall or LAN to increase throughput.
• Viruses slowing server operation. Check for and clean off
viruses.
• Production or recovery server or Command View station is too
slow. Use a faster CPU with plenty of memory.
• Inadequate privileges. Administrator privileges are required
in all applications and on all hardware used with HP VSS HWP.
• Writer application not configured according to best practices.
Consult the software manufacturer for recommended practices. For
example, keeping database files small by creating more rather than
larger files may speed up overall operation and database copying.
Saving transaction logs to a different volume than the database may
also speed up performance.
• Use VSS trace to locate errors in the snapshot process. See
the Microsoft website and Windows help for information about the
log and trace files.
-
84 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
FRS error messages
The following text explains application event log error
messages. For information about command line interface errors,
refer to “Command line error codes” on page 77.
FRS/Exchange backup error messages
Error:
Extended Maintenance Mode feature for Cluster Service is not
installed on node [Node name].You must install this update if you
want to be able to restore a backup on a cluster node. See KB
Article 903650 at
http://support.microsoft.com/default.aspx?scid=kb;en-us;903650
Explanation:
FRS cannot perform backup and restore operations on the cluster
node without the extended maintenance mode feature support. You
must download and install the specified KB Article before
attempting to initiate backup or restore operation in cluster
environments.
Error:
Failed to find extended maintenance mode support on node [Node
Name]
Explanation:
FRS failed to detect extended maintenance mode support on this
cluster node.
Error:
Integrity check failed for SG: [Storage Group Name], Path:
[Path]
http://support.microsoft.com/default.aspx?scid=kb;en-us;903650
-
Troubleshooting 85
Explanation:
FRS failed the integrity check for newly created shadow copy LUN
for the selected storage group. The possible cause could be a
corrupt database.
Error:
Backup failed; status: [Status]. Please disable the circular
logging for storage group [Storage Group Name]
Explanation:
FRS does not support backup of LUNs for storage groups with
circular logging enabled. You must disable the circular logging
feature for the logs on the Exchange server for the selected
storage group.
Error:
Backup failed; status: [Status]. Microsoft Exchange Writer
[Exchange Writer Name] is not stable.
Explanation:
FRS failed to complete the backup operation because the
Microsoft Exchange Writer state is not stable.
Error:
Pre-check conditions for backup failed; status: [Status]
Explanation:
This server is not configured as required (for example, SVP is
in modify mode or XP command device is not exposed to the
production and recovery servers). See the Configuration chapter of
this guide for instructions.
Error:
Error connecting to production server: [Server Name]; status:
[Status]
-
86 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Explanation:
The FRS client failed to connect to the production server.
Error:
Shadow copy creation failed; status: [Status]. Please refer
production server: [Server Name] for further details
Explanation:
The shadow copy operation failed. For additional information on
the details of the failure, check the production server event
logs.
FRS/Exchange recovery error messages
Error:
Extended Maintenance Mode feature for Cluster Service is not
installed on node [Node name].You must install this update if you
want to be able to restore a backup on a cluster node. See KB
Article 903650 at
http://support.microsoft.com/default.aspx?scid=kb;en-us;903650
Explanation:
FRS cannot perform backup and restore operations on the cluster
node without the extended maintenance mode feature support. You
must download and install the specified KB Article before
attempting to initiate backup or restore operation in cluster
environments.
Error:
Failed to find extended maintenance mode support on node [Node
Name]
Explanation:
FRS failed to find the extended maintenance mode support on this
cluster node.
http://support.microsoft.com/default.aspx?scid=kb;en-us;903650
-
Troubleshooting 87
Error:
Microsoft Exchange writer [Write name] is not stable;
status:[Status]
Explanation:
FRS failed to complete the recovery operation since the
Microsoft Exchange writer is not in stable state.
Error:
Unable to get the disk signature for production volume [Volume
Name]; status: [Status]
Explanation:
FRS failed to get the disk signature for the selected cluster
resource.
Error:
Unable to reset disk signature for device [Device Name]; status:
[Status]
Explanation:
FRS failed to reset the disk signature for the selected cluster
resource.
FRS/Exchange delete point-in-time copy error messages
Error:
Delete LUN [Lun identifier (CU: LDEV)] failed. Please delete it
manually from Command View station
Explanation:
FRS failed to delete the LUN associated with the selected
point-in-time copy. The user must delete the LUN manually from the
array.
-
88 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Error:
Delete volume mount point [Volume Mount Point] failed; status:
[Status]
Explanation:
FRS failed to delete the mount point for the production
volume.
Error:
Set mount point [Volume mount point] failed; status:
[Status]
Explanation:
FRS failed to set the mount point for the production volume (in
case of RESYNC option) and recovery volumes (in case of SWAP
option).
-
Glossary 89
Glossary
This glossary defines acronyms and terms used in this guide or
related to this product and is not a comprehensive glossary of
computer terms.
API Application Programming Interface, an interface that allows
a software application to connect to and work with a third party
software application.
BC HP StorageWorks Business Copy XP. Software that creates and
maintains local copies of data stored on the disk array. The copies
can be used for data duplication, backup, and local disaster
recovery.
clone A full copy of a volume, usable by an application.
cluster The concept of linking individual servers physically and
programmatically and coordinating communication between them so
they can perform common tasks.
CV HP StorageWorks CommandView, a browser-based interface that
allows management of an HP disk array.
differential copy A copy of a database consisting only of the
differences in the database since the last full copy.
disk array A RAID. A collection of disk drives within a cabinet
or multiple cabinets and including a controller and software
allowing drives to be ganged together in various configurations to
create virtual drives (LUNs).
EVA HP StorageWorks Enterprise Virtual Array.
-
90 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
failover Process that automatically shifts the workload from one
server in a cluster to another server in the event of a
failure.
FC Fibre Channel, a fiber optic interconnection standard
commonly used for storage area networks.
FRS HP StorageWorks Fast Recovery Solution.
FRS server The server where copies of the production database
are staged and managed. The FRS server runs the FRS GUI. Also known
as the recovery server.
GUI Graphical User Interface.
HBA Host bus adapter. The FC interface card that installs in a
host to connect the host to a fabric SAN.
HWP Hardware Providers. A collection of software that executes
on the host, a bus adapter, and the disk array to enable managing
and/or copying of array LUNs through the Windows OS and
applications.
LDEV Logical device. An LDEV is created when a RAID group is
divided into pieces according to a selected host emulation mode
(that is, OPEN-3, OPEN-8, OPEN-9, etc.). The number of resulting
LDEVs depends on the selected emulation mode. The term LDEV is
often used synonymously with the term volume.
LUN Logical unit number. A LUN results from mapping a SCSI
logical unit number, port ID, and LDEV ID to a RAID group. The size
of the LUN is determined by the emulation mode of the LDEV, and the
number of LDEVs associated with the LUN. For example, a LUN
associated with two OPEN-3 LDEVs has a size of 4,693 MB.
mirror Synonymous with “clone.”
MSA HP StorageWorks Modular Smart Array.
online backup Backup while Exchange services are still running.
There is no interruption in services for backup.
-
Glossary 91
production server Exchange 2003 server.
plex A Microsoft term denoting a full copy of data that has been
split off from the original and is no longer being updated.
Synonymous with “split mirror.”
production LUN The volume containing the active application
database. Known to Business Copy as a P-VOL.
P-VOL Primary volume. Typically the volume where application
data is stored.
RAID Redundant array of independent disks.
recovery LUN The volume containing the data copies used for
recovery. Known to Business Copy as an S-VOL.
recovery server FRS server. The server where copies of the
production database are managed.
SAN fabric The Fibre Channel hardware and cabling that connects
servers to storage devices in a Storage Area Network (SAN) is
referred to as a “fabric.” A fabric switch provides
automatically-switched connectivity between servers and storage in
the fabric.
shadow copy A Microsoft term describing a point-in-time copy of
an original volume. The original volume continues to change as the
process continues, but the shadow copy of the volume remains
constant.
SMA Storage Management Appliance. A PC built into the EVA Disk
Array. The SMA provides a direct interface into the disk array.
snapclone An HP EVA disk array term denoting a full copy of a
volume that becomes immediately usable by an application. Created
much faster than ordinary clones by taking a snapshot and updating
to a full copy in the background.
snapshot A generic term meaning a static point-in-time copy of a
volume, typically used for backup.
SNMP Simple Network Management Protocol.
-
92 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
split mirror A full copy of data that has been split off from
the original and is no longer being updated.
subsystem Synonym for “disk array” or “RAID.”
S-VOL Secondary volume. The volume that receives copies of
data.
SVP Service processor. A PC built into the HP XP Disk Array. The
SVP provides a direct interface into the disk array, and is used by
the HP service representative only.
volume Generic term for a number of physical disks or portions
of disks logically bound together as a virtual disk containing
contiguous logical blocks. Volume can also be software shorthand
for a mapped volume (Windows drive letter or mount point).
VDS Microsoft Virtual Disk Service, the Windows service that
manages storage through hardware providers.
volume shadow copy See “shadow copy.”
VSC Volume Size Configuration, a feature of HP disk arrays that
allows creation of logical volumes custom-sized according to user
requirements.
VSS Microsoft Volume Shadow Copy Service, the Windows service
that creates data copies. Works through HP HWP to make copies of
disk array volumes.
XP HP StorageWorks XP Disk Array.
-
Index 93
Index
Aabout this guide 7access.txt file 33addcopy command 72,
74adding server instances 59authorized resellers 9
BBusiness Copy
license 34
Ccommand line 70
addcopy 72, 74available commands 71delcopy 72, 76error codes
77examples 74listcopy 73, 75
Command ViewBC license 34configuration for HWP 33Secure Manager
license 34
Command View management station 27components 18
hardware 27software 28
conceptual overview, FRS 17configuration
disk array 36Fast Recovery 26important notes 29
conventions, document 10copy terminology 21creating shadow
copies 61
Ddeinstallation
FRS 53delcopy command 72, 76disk array 27
configuring 36overview 24
disk arraysrequirements 7supported 7
documentationconventions 10
Eerror codes, command line 77error messages 84
-
94 HP StorageWorks XP Fast Recovery Solution for Windows Server
2003: Administration Guide
Ffabric switch 27features, FRS 16fibre cables 27files
CommandView XP configuration 33firmware
required 7FRS
adding servers 59creating shadow copies 61installing 45main
window 57overview 20recovery 64starting 56
functional components 18
GGlossary 89glossary (copy terms) 21
Hhardware components 27HBAs 27hot fixes 28HWP overview 23
IInstallation 43
JJava Runtime Environment 28
Llicensing FRS