Professional Documents
Culture Documents
3pAR SRM Configuration
3pAR SRM Configuration
2
for VMware vCenter Site Recovery
Manager User Guide
Abstract
HP 3PAR Storage Replication Adapter 5.5.2 for VMware vCenter Site Recovery Manager (HP 3PAR SRA) is an integration
component that communicates with HP 3PAR StoreServ to execute specific storage and HP 3PAR Remote Copy functions needed
for VMware vCenter Site Recovery Manager operation. This document provides relevant information for installing and configuring
the HP 3PAR SRA. This document also provides relevant information for the HP 3PAR Remote Copy Software configuration so
that the HP 3PAR SRA can execute specific HP 3PAR Remote Copy functions to build, manage, test and execute disaster
recovery.
Contents 3
1 Introduction
VMware vCenter Site Recovery Manager (SRM) is a management and automation product that
helps build, manage, test, and execute disaster recovery plans for a VMware virtual infrastructure.
The HP 3PAR storage system, as the storage component in a VMware virtual infrastructure, holds
virtual machine information for a protected site/location and recovery site/location. HP 3PAR Site
Recovery Adapter (SRA) is an important integration component that communicates with HP 3PAR
StoreServ to execute specific storage and HP 3PAR Remote Copy functions needed for VMware
vCenter Site Recovery Manager operations.
4 Introduction
2 VMware vCenter Site Recovery Manager overview
VMware vCenter Site Recovery Manager works as a plug-in component for VMware vCenter and
integrates its functionality in VMware vCenter.
5
The VMware vCenter Site Recovery Manager communicates with HP 3PAR Remote Copy Software
for storage replication through the HP 3PAR SRA. The HP 3PAR SRA provides information about
Remote Copy volume groups that exist in HP 3PAR StoreServ to Site Recovery Manager. The Site
Recovery Manager identifies datastores and RDM devices in the Remote Copy volume group (also
referred to as consistency groups). These datastores and RDM devices have corresponding virtual
volumes in the Remote Copy volume group and replicates between the protected site and the
recovery site.
7
4 HP 3PAR SRA installation and configuration prerequisites
HP 3PAR SRA is packaged in MSI format and installed onto the host where VMware vCenter Site
Recovery Manager is installed.
HP 3PAR SRA requires the following companion packages to be installed on the host before
installation:
VMware Site Recovery Manager 5.0, 5.1, or 5.5
In an SLD configuration with three HP 3PAR StoreServ Storage systems (A, B, and C),
AB is configured in synchronous mode, AC in asynchronous periodic mode, and
BC is the standby link in asynchronous periodic mode. Then, SRM/SRA must be
configured between AC only, implying that StoreServ A is configured in the protected
site and StoreServ C is configured in the recovery site.
NOTE: HP 3PAR SRA installation adds the SRA\3PARInServ folder to VMware vCenter Site
Recovery Manager storage folder (for example, C:\Program Files (x64)\VMware\VMware
vCenter Site Recovery Manager\storage) and TPDSrm.exe is the adapter driver
program that is invoked by VMware vCenter Site Recovery Manager.
NOTE: HP 3PAR SRA and SRM must be installed on the same host.
2. Click I Agree to acknowledge the User License Agreement, and click Next to continue.
3. Click Next to start installation at the default path.
4. After the installation is complete, restart the VMware vCenter Site Recovery Manager service
to ensure that HP 3PAR SRA is recognized by SRM.
NOTE: This package can only be installed under the existing VMware vCenter Site Recovery
Manager installed path. No other installation location is provided as an option.
Verifying installation
To verify the installation of HP 3PAR SRA 5.5.2:
1. Click Start Control PanelPrograms and Features.
2. Verify that HP 3PAR SRA Software Version 5.5.2 appears in the Currently installed programs
column.
NOTE:
An HP 3PAR Remote Copy Software license is required on the HP 3PAR StoreServ.
HP 3PAR SRA 5.5.2 supports SLD Remote Copy environment on HP 3PAR OS 3.1.2 MU3
P16 or later MUs and HP 3PAR OS 3.1.3 or later.
HP 3PAR SRA supports mixed (RCIP Async [Periodic] and RCFC Sync) configuration.
NOTE: When using Peer Motion to perform data migration, the Remote Copy configurations
and SRM setup must be reestablished with the new array after migration. For more information
about re-establishing Remote Copy configurations, see the HP 3PAR Peer Motion Manager User
Guide or HP 3PAR Remote Copy Software User's Guide.
Present the virtual volume to the ESX(i) host (i.e. create a VLUN).
It is assumed that ESX(i) host(s) are already connected to the HP 3PAR storage system
and configured per the recommendations in the VMware ESX Servers Implementation
Guide. Create a VLUN for the ESX(i) host(s) corresponding to the virtual volume. For more
information, see the HP 3PAR OS VMware ESX Server Implementation Guide.
NOTE: HP recommends that all LUNs used by VMware Virtual Machines should form a protection
group to be failed over together during test and recovery, and be part of a single Remote Copy
group and synchronized with the target Remote Copy group.
A VLUN is not created for the recovery site ESX(i) host(s) for the replicated virtual volume. The
failover process creates necessary VLUNs for the recovery site ESX(i) host(s) for all replicated virtual
volumes that are part of a failover plan.
11
Installing, configuring, and verifying the configurations on HP 3PAR storage
system
1. Verify the correct version of HP 3PAR Operating System with the appropriate licensed features.
This operation must be performed on both the protected site and the recovery site.
root@inodee2022:~# showversion
Release version 3.1.1
Patches: None
root@root@inodee2022:~# showlicense
License key was generated on Tue Jul 26 11:15:47 2011
2. Verify the HP 3PAR storage system details on the protected and recovery sites.
root@inodee2022:~# showsys
---------------(MB)----------------
3. Create a user on the HP 3PAR storage system on the protected and recovery sites.
NOTE: When you present LUNs to the ESXi host using Persona 11 at the recovery site,
system stops responding while executing the Rescan All function. Hence, you must remove all
LUN exposures of the Remote Copy group member on the recovery site, except the Peer
Persistence configuration to the host with Persona 11, to prevent any delayed response
during the ESXi rescan.
5. Create Common Provisioning Groups (CPGs) to be used during virtual volume creation on the
protected and recovery sites.
Configuring Remote Copy with IP between the protected and recovery sites
HP 3PAR Remote Copy Software provides the capability to copy virtual volumes from the protected
site HP 3PAR storage system to the recovery site HP 3PAR Storage system.
Ensure that the HP 3PAR storage system hardware is set up appropriately for creating a Remote
Copy configuration between the protected site and recovery site.
NOTE: SRM works with a Remote Copy setup using IP or Fibre Channel connectivity. This document
describes the steps required to configure Remote Copy with IP. For more information about
implementing Remote Copy over Fibre Channel, see the HP 3PAR Remote Copy Software User's
Guide.
root@inodee2023:~# startrcopy
Link Information
root@snodec242:~# startrcopy
Configuring Remote Copy with IP between the protected and recovery sites 15
Status: Started, Normal
Link Information
Group Information
Group Information
NOTE: If applicable, create additional Remote Copy groups and add virtual volumes.
root@inodee2023:~# showrcopy
Target Information
Link Information
Group Information
root@snodec242:~# showrcopy
Target Information
Link Information
Group Information
Configuring Remote Copy with IP between the protected and recovery sites 17
7 Configuring VMware vCenter Site Recovery Manager and
HP 3PAR SRA
The VMware vCenter Site Recovery Manager plug-in is installed and enabled by the vCenter Plug-in
Manager (Plug-insManage Plug-ins...).
NOTE: For more information about configuring VMware vCenter SRM, see the VMware vCenter
Site Recovery Manager documentation.
IMPORTANT: Ensure that both vCenter servers are configured with each other and can be
accessed from the respective sites.
NOTE: If you do not specify any filtering condition, then SRA discovers all the Remote
Copy groups in the array.
User name of the HP 3PAR storage systemThe user name that HP 3PAR SRA uses to
connect to the storage system
Password of the HP 3PAR storage systemThe user password that HP 3PAR SRA uses to
connect to the storage system.
You must also enable the array pair between HP 3PAR StoreServ Storage systems A and C as
shown below.
Figure 2
TPDSrm.exe removecertTo delete the accepted HP 3PAR StoreServ certificate from the
cache memory.
If you have configured an SLD remote copy environment with three HP 3PAR StoreServ Storage
systems (A, B, and C), where AB is configured in synchronous mode, AC in asynchronous
periodic mode, and BC is the standby link in asynchronous periodic mode. SRM/SRA is
configured between HP 3PAR StoreServ Storage systems A and C, then HP 3PAR SRA requires
that you accept and validate the HP 3PAR StoreServ Storage SSL certificate for the primary and
secondary HP 3PAR StoreServ Storage systems on both the Protected and Recovery sites.
NOTE: You must accept the certificate when the link between A and C is UP.
For example, HP 3PAR StoreServ A and SRM Server 1 are part of the protected site. HP
3PAR StoreServ B and SRM Server 2 are part of the recovery site. In SRM Server 1, you
must accept and validate the HP 3PAR StoreServ A and HP 3PAR StoreServ B certificates.
Perform a similar procedure for SRM Server 2.
Test
This option performs nondisruptive recovery operations.
SRM communicates with HP 3PAR SRA using the remote storage information obtained during the
discovery process. SRA creates snapshots of the Remote Virtual Volumes, and presents them to the
recovery ESX server. During this recovery process, the VMs continue to run at the production site
(protected site). You can verify that the VMs are running at the recovery site.
Clean Up
Perform the Cleanup operation after you have verified that the VMs are running at the recovery
site (using the Test operation). SRA does a cleanup (unpresent and delete) of the previously created
snapshots.
Recovery
Perform a recovery operation by shutting down the VMs at the protected site (Site A), and recover
those VMs at the recovery site (Site B).
Planned migrationSRM shuts down the VMs at protected site and unmounts the Datastores.
SRA changes the status of the source Datastores to read-only, and then creates the snapshots
of the source device. SRA reverses the replication direction and swaps the read/write
relation between the Datacenters. SRM then rescans the Datastores at the recovery site, and
restarts the VMs.
NOTE: Later, the snapshots taken at the protected site (before failover) will be used for restore
replication operation by SRA. Restore replication is restoring the VMs to the original
state by discarding the recent changes made at the recovery site. You cannot perform this
operation from the SRM GUI. However, you can run the following SRM commands, sequentially,
to perform this operation:
prepareRestoreReplication
restoreReplication
Disaster recoveryIf the protected Datacenter is unavailable due to any disasters or failures,
then you must run the SRM recovery plan to start up the VMs at the recovery site. The SRA
recovery process is similar to planned migration, except for the snapshot creation operations
performed at the protected site.
For SLD configurations:
23
Consider the following scenarios where A is the Primary System, C the Asynchronous Periodic
Backup System, and B the Synchronous Backup System, and SRM/SRA is configured between HP
3PAR StoreServ Storage systems A and C.
All the links are up:
SRM initiates the data transfer from A to C through HP 3PAR SRA. After the sync is complete,
SRA stops the RC groups between AB and also between AC. Then SRA initiates failover
at C so that C becomes the Failover System and takes the role of the Primary System.
AC link is down:
HP 3PAR SRA initiates the data transfer from B to C.
After the sync is complete, SRA stops the RC groups between AB. Then SRA initiates failover
at C so that C becomes the Failover System and takes the role of the Primary System. Also
see the Limitations of SLD configuration (page 38) section.
AB link is down:
When the AC link is up:
SRM initiates the data transfer from A to C through HP 3PAR SRA. Once the sync is complete,
SRA stops the RC groups between AC. SRA then initiates a failover at C so that C becomes
the Failover System and takes the role of the Primary System.
When AC link is down:
Depending on the situation, either B or C will have the most current data since the synchronous
link between AB is down. In such a scenario, as per the design, HP 3PAR SRA does not
initiate any data transfer from B to C. With the available data, C becomes the failover system
and takes the role of the primary system.
CAUTION: If C does not contain the most current data then any data replicated to B that is
not replicated to C is discarded.
BC link is down:
When AC link is up:
SRM initiates the data transfer from A to C through HP 3PAR SRA. Once the sync is complete,
SRA stops the RC groups between AB and also between AC. SRA then initiates failover
at C so that C becomes the failover system and takes the role of the primary system.
When the AC link is down:
HP 3PAR SRA will not initiate the data transfer between BC, because the BC standby link
is not available for data transfer. SRA stops the RC groups between AB. SRA then initiates
failover at C. With the available data, C becomes the Failover System and takes the role of
the Primary System.
CAUTION: If C does not contain the most current data and any data replicated to B that is
not yet replicated to the C is discarded.
Reprotect
Perform the reprotect operation to configure protection in the reverse direction (from Site B to Site
A), as a preparation for failback to the original state. The SRA operations are similar to the planned
migrations, and deletes the earlier snapshots that were created during failover from Site A to Site
B.
For SLD configurations, the reprotect operation requires that the remote copy links between the
new primary and both the targets to be up. If the array C is the new primary system and if the links
25
9 HP 3PAR SRA for the VMware SRM 5.5 utility
HP 3PAR SRA supports the command line interface TPDSrm.exe. VMware vCenter Site Recovery
Manager requests are sent via a Perl script command.pl in the HP 3PAR SRA installed directory.
The Perl script internally processes the data to an XML file and spawns an instance of TPDSrm.exe
to process the XML file. The XML file is removed once TPDSrm.exe returns to command.pl.
The HP 3PAR Storage Replication Adapter for VMware SRM 5.5 utility supports the following
options:
Syntax
To obtain current version number of the SRA:
TPDSrm.exe <-v>
To remove all test snapshots from the specified HP 3PAR Storage system:
TPDSrm.exe cleansnaps <-sys StorageSystemName -user UserName -pass
Password [-loglevel Num]>
To view all state cached on local system:
TPDSrm.exe viewstate
To remove a particular state cached for a Remote Copy group on the specified HP 3PAR
storage system on local system:
TPDSrm.exe cleanstate <-sysid StorageSystemID> <-rcgroup RCGroupName>
To view or modify log file setting information:
TPDSrm.exe log [-size LogSize] [-cnt Num]
Options
-v
Show version information.
cleansnaps
Remove any snapshot created for test failover on the HP 3PAR Storage system.
-sys <StorageSystem>
The HP 3PAR storage system name or IP address to connect.
-user <UserName>
The HP 3PAR storage system user name.
-pass <Password>
The HP 3PAR storage system password.
-loglevel <Num>
Optional. Overrides the default output message level using a numeral from 1 to 5. The
default is 3 (1-error, 2-warning, 3-info, 4-verbose, 5-trivia).
viewstate
View the local disaster recovery state cache information. Only prepareFailover and
failover states are be available.
-rcgroup <RCGroupName>
The Remote Copy group name.
log
View or modify the current log size limit and the maximum number of log history files to
maintain.
-size <LogSize>
Specify the log file size limit (in MB). The default is 2 MB.
-cnt <Num>
Specify the maximum log history files besides the latest log file to maintain. The default
is 20 histories.
27
10 Partial licensing
The HP 3PAR SRA supports partial licensing facility to purchase license based on the capacity used
on the storage array. This feature is available if you have HP 3PAR OS 3.1.2 MU2, or later.
The following features are available with the partial license:
InForm Suite
Remote Copy
Thin Copy Reclamation
Transparent Failover
Virtual Copy
The following features are available with the regular license:
Adaptive Optimization
Domains
Dynamic Optimization
InForm Suite
Management Plug-In for VMware vCenter
Peer Motion
Recovery Manager for Exchange
Recovery Manager for Microsoft Hyper-V
Recovery Manager for Oracle
Recovery Manager for SQL
Recovery Manager for VMware vSphere
Remote Copy
System Reporter
System Tuner
Thin Conversion
Thin Copy Reclamation
Thin Persistence
Thin Provisioning
VDS Provider for Microsoft Windows
Virtual Copy
Virtual Lock
VSS Provider for Microsoft Windows
NOTE: SRA 5.5.2 supports partial licensing only with HP 3PAR OS 3.1.2 MU2, or later.
28 Partial licensing
11 HP 3PAR SRA 5.5.2 SRM vs HP 3PAR Remote Copy state
diagram
getrcopy
getrcopy
29
Table 1 Remote Copy failover from Site A to Site B (continued)
Site A Role
After HP Site B Role
3PAR after HP 3PAR
Execution System System HP 3PAR OS
State SRM Command Site Command Command Command Description
getport
setrcopygroup
failover
getrcopy
31
Table 4 Remote Copy sync from Site A to Site B
Site B Role
Site A Role after HP
After HP 3PAR
Execution 3PAR System System HP 3PAR OS
State SRM Command Site Command Command Command Description
33
Additional protection to the data on the recovery Storage System. HP 3PAR SRA will take a
snapshot of the devices on the recovery storage system of the SRM before failover for optional
restore purpose. The snapshot name will have the following prefix:
SRM_TARGETBK_RO_<VVID>.
Support of Dynamic Access Group. The concept of Dynamic Access Group support is to expose
LUNs only to the specified HBA initiators provided by SRM. Any exposure of the participating
LUNs made to other initiators not on the requested list will be removed. This feature is always
enabled.
Multiple Remote Copy groups in one protected group is not recommended. HP 3PAR SRA will
log a warning to user if multiple instances of such configurations are detected during the Test
or Recovery operation since this might be an indication that VMs are using virtual volumes
from different Remote Copy groups.
The re-protect operation requires at least one Remote Copy link to be running for the intended
storage pair to be up. If a recovery operation is performed as part of the failback process
when all Remote Copy links are down, additional manual steps are required on the storage
system before the user can re-protect the data.
1. On the original protected storage system, run the command showrcopy groups <RC
group name>
If the group role is not Primary-Rev, continue with SRM Reprotect; otherwise, go to
step 2.
2. Run the following command to change Remote Copy role:
setrcopygroup reverse local current <RC group name>
NOTE: You need not perform these manual steps if the Primary Array is up and if you have
validated the HP 3PAR StoreServ SSL certificate for both the Primary and Secondary HP 3PAR
StoreServ Storage systems on both the primary and recovery sites. For more information on
validating SSL certificates, see Validating HP 3PAR StoreServ Storage SSL certificates (page
21).
If a failover operation is unsuccessful, make sure to clean up the local disaster state cache.
Otherwise, the subsequent SRM operations will fail.
On both the protected and recovery sites where HP 3PAR SRA is installed, issue the following
command:
TPDSrm viewstate
34 Special notes
3. Issue the removetask d <TaskID> command to remove the task detail.
4. Rerun the SRM operation again.
If you have multiple failed virtual volumes in the group, you may need to repeat steps 1
through 4 for all volumes.
showrcopy
Group Information
As displayed in the above result, the virtual volume id 1741 is same between the primary and
secondary volumes in the same RC group. In an RC Group, none of the virtual volumes should
have the same virtual volume ID.
35
If you see this issue, do the following to resolve this issue:
Process 1
1. Identify all serial ID numbers on Primary_array and Secondary_array by running the
showrcopy command in HP 3PAR CLI interface.
Sample output:
Primary_array Secondary_array
Group Information
In the sample set of replications seen above, the serial ID 1741 is used on both
arrays.
2. Stop the replication between Primary_array and Secondary_array by running the
stoprcopygroup <group_name> command in HP 3PAR CLI interface for RC
groups that have the same serialIDs used by source and target devices.
3. Destroy the target device (Secondary Virtual volume) TestVV_Sec.1 with serialID
1741 on Secondary_array.
4. Recreate the target device TestVV_Sec.1 on Secondary_array. The Secondary_array
assigns a new serialID automatically. This new serialID, one above the largest serialID
currently used by Secondary_array. For example, if the highest current serialID on
Secondary_array is 400, the new device TestVV_Sec.1 assigned is serialID 401.
5. Ensure that the serialID of the new device TestVV_Sec.1 is not used by any device
on Primary_array.
6. Re-establish the replication relationship between device TestVV_Pri.1 on Primary_array
and device TestVV_Sec.1 on Secondary_array.
IMPORTANT: This solution destroys the designated target devices only. Do not
make any changes to the source devices. However, if it is not possible to achieve
uniqueness of serialIDs between the two Arrays, it might be necessary to recreate
the source devices. To recreate source devices safely, migrate the data to new storage
devices before the source (Primary_array) device is destroyed.
Process 2
Create a series of small volumes that are sufficient to bring the serialIDs list out of sync
between the two Sites. For example:
1. Ensure that Primary_array has serialIDs starting from 250.
2. Ensure that Secondary_array has serialIDs starting from 240.
3. Create 30 to 40 small volumes or devices on Primary_array to use all the indexes
from 250 to 280.
4. Delete these small volumes or devices which also delete these serialIDs.
NOTE: The next serialID on Primary_array would be 281 and thus preventing any
duplication.
36 Special notes
Support for multiple array pair configuration
HP 3PAR SRA supports multiple array pair configurations. Different remote copy groups from the
array pairs can be part of a single recovery plan or separate recovery plan.
NOTE:
If a remote copy group has virtual volumes that are not participating in datastore creation and
if these virtual volumes are exposed to a different host, then there are chances of data
corruption.
You must make sure that all virtual volumes in remote copy group are participating in datastore.
The virtual volumes in a remote copy group that are not participating in datastore creation
must not be presented to a host.
If the virtual volumes participating in an SRM configuration are exposed using a virtual volume
set, any virtual volume member in this set, not used by SRM in the same protected group loses
connectivity to the LUN after a failover.
In the event of a failover, if the participating virtual volumes and hosts are part of vv set and
host set respetively, then the LUNs are exposed using vv set and host set features.
If the participating virtual volumes and host are not part of vv set and host set features, then
the LUNs are exposed individually to the ESX(i) hosts.
NOTE: If the commands are executed from the command prompt, the SRM GUI might not
reflect the latest status.
For SLD Remote Copy groups, after restore replication , only the remote copy group between
AC will be started automatically by SRA. Once Restore Replication is complete, you must
38 Special notes
manually start the remote copy group between AB before you proceed with any other SRM
operations.
During the reprotect operation, SRA triggers delta resync operation from CA and CB,
where C is the new primary system after failover. If the SRM recovery operation was performed
when either AB or BC or both the remote copy links are down, then as per the remote
copy behavior, reprotect operation triggered by SRM through SRA will initiate a full copy from
CB only (from CA delta resync will be initiated).
SRM recovery operation initiated at C will do a delta sync from B to C and then initiate the
failover operation at C. When the AC link is down, under certain conditions, as per the
remote copy behavior, the data transfer from BC will go into full-sync mode during SRM
recovery operation at C.
Workaround: When all the remote copy links are UP, run the SRM Test operation at least once
before executing the disaster recovery at C when the AC link is down to avoid BC
going to FULL SYNC.
HP 3PAR documentation
Table 6 Documentation list
For information about: See:
Supported hardware and software platforms The Single Point of Connectivity Knowledge for HP Storage
Products (SPOCK) website:
http://www.hp.com/storage/spock
Using the HP 3PAR Management Console (GUI) to HP 3PAR Management Console User's Guide
configure and administer HP 3PAR storage systems
Using the HP 3PAR CLI to configure and administer HP 3PAR Command Line Interface Administrators Manual
storage systems
Installing and maintaining the Host Explorer agent in order HP 3PAR Host Explorer Users Guide
to manage host configuration and connectivity information
Creating applications compliant with the Common HP 3PAR CIM API Programming Reference
Information Model (CIM) to manage HP 3PAR storage
systems
Migrating data from one HP 3PAR storage system to HP 3PAR-to-3PAR Storage Peer Motion Guide
another
Configuring the Secure Service Custodian server in order HP 3PAR Secure Service Custodian Configuration Utility
to monitor and control HP 3PAR storage systems Reference
Using the CLI to configure and manage HP 3PAR Remote HP 3PAR Remote Copy Software Users Guide
Copy
Identifying storage system components, troubleshooting HP 3PAR F-Class, T-Class, and StoreServ 10000 Storage
information, and detailed alert information Troubleshooting Guide
Installing, configuring, and maintaining the HP 3PAR HP 3PAR Policy Server Installation and Setup Guide
Policy Server HP 3PAR Policy Server Administration Guide
HP 3PAR 7200 and 7400 storage systems HP 3PAR StoreServ 7000 Storage Site Planning Manual
HP 3PAR 10000 storage systems HP 3PAR StoreServ 10000 Storage Physical Planning
Manual
HP 3PAR StoreServ 10000 Storage Third-Party Rack Physical
Planning Manual
Installing 7200 and 7400 storage systems and initializing HP 3PAR StoreServ 7000 Storage Installation Guide
the Service Processor HP 3PAR StoreServ 7000 Storage SmartStart Software Users
Guide
Maintaining, servicing, and upgrading 7200 and 7400 HP 3PAR StoreServ 7000 Storage Service Guide
storage systems
Troubleshooting 7200 and 7400 storage systems HP 3PAR StoreServ 7000 Storage Troubleshooting Guide
Maintaining the Service Processor HP 3PAR Service Processor Software User Guide
HP 3PAR Service Processor Onsite Customer Care (SPOCC)
User's Guide
Backing up Oracle databases and using backups for HP 3PAR Recovery Manager Software for Oracle User's
disaster recovery Guide
Backing up Exchange databases and using backups for HP 3PAR Recovery Manager Software for Microsoft
disaster recovery Exchange 2007 and 2010 User's Guide
Backing up SQL databases and using backups for disaster HP 3PAR Recovery Manager Software for Microsoft SQL
recovery Server Users Guide
Backing up VMware databases and using backups for HP 3PAR Management Plug-in and Recovery Manager
disaster recovery Software for VMware vSphere User's Guide
Installing and using the HP 3PAR VSS (Volume Shadow HP 3PAR VSS Provider Software for Microsoft Windows
Copy Service) Provider software for Microsoft Windows User's Guide
Best practices for setting up the Storage Replication HP 3PAR Storage Replication Adapter for VMware vCenter
Adapter for VMware vCenter Site Recovery Manager User Guide
Troubleshooting the Storage Replication Adapter for HP 3PAR Storage Replication Adapter for VMware vCenter
VMware vCenter Site Recovery Manager Site Recovery Manager Troubleshooting Guide
Installing and using vSphere Storage APIs for Array HP 3PAR VAAI Plug-in Software for VMware vSphere User's
Integration (VAAI) plug-in software for VMware vSphere Guide
HP 3PAR documentation 41
Typographic conventions
Table 7 Document conventions
Convention Element
Bold monospace text Commands you enter into a command line interface
System output emphasized for scannability
WARNING! Indicates that failure to follow directions could result in bodily harm or death, or in
irreversible damage to data or to the operating system.
CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.
Required
Indicates that a procedure must be followed as directed in order to achieve a functional and
supported implementation based on testing at HP.
43