Page 5 - Matrix recovery management Overview
1 Matrix recovery management Overview Matrix recovery management is a component of the HP Matrix Operating Environment that providesdisaster recovery protection for logical servers and for Matrix infrastructure orchestration services . Logical servers and Matrix infrastructure orchestration services...
Page 8 - Installation and configuration overview
2 Installing and configuring Matrix recovery management This chapter contains sections on Matrix recovery management installation prerequisites, networkingsetup, storage setup, logical server setup, Matrix recovery management configuration, export andimport operations, and DR Protection for IO servi...
Page 9 - Uninstalling Matrix recovery management; Use the Windows; Setting up Networking
NOTE: • It is assumed that networking and storage replication links are present between the Local Siteand the Remote Site. • When planning for disaster recovery solution using Matrix recovery management with VMwarehypervisor based IO services, proper planning is required to ensure the hosts at both ...
Page 10 - Setting up Storage; Storage server type
if you configure a logical server to use a different IP or subnet at each site in the Matrix recoverymanagement configuration. • When running on physical targets (VC hosted) or non VMware ESX virtual targets (VM hosted),Matrix recovery management does not ensure that logical servers use the same MAC...
Page 12 - General storage setup notes; Dynamic workload movement with CloudSystem; HP P6000 storage setup notes; HP P6000 Continuous Access Software documentation available at; HP P9000 storage setup notes
General storage setup notes • For information on storage setup of cross-technology logical servers (logical servers capableof being VC hosted or VM hosted), see: Dynamic workload movement with CloudSystem Matrix . • For a list of supported storage, see the HP Insight Management Support Matrix at htt...
Page 13 - HP 3PAR storage setup notes; setpassword
on HP P9000 RAID Manager Software to manage P9000 storage replication. HP P9000RAID Manager Software instances and configuration files must be configured to managevarious device groups that are configured in Matrix recovery management. For moreinformation, see the following: ◦ HP P9000 Cluster Exten...
Page 14 - Creating and installing a User Defined storage adapter; Overview
NOTE: After you install and configure Matrix recovery management at the Local Site, you must manually failover 3PAR remote copy groups to the Remote Site before attempting to configureinstall and configure Matrix recovery management at the Remote Site. For 3PAR periodic (asynchronous) remote copy, t...
Page 16 - Setting up Local Site logical servers; portability group; Setting up Remote Site logical servers
Multiple User Defined storage adapters Matrix recovery management supports multiple User Defined storage adapters to co-exist in aMatrix recovery management configuration. For each User Defined storage adapter type, you cancreate a new subdirectory and place your implementation of the three commands...
Page 17 - Dynamic workload movement with CloudSystem Matrix
Rescan storage using VM host management tools, for example, VMware Virtual Centeror Microsoft Hyper-V Management Console, to ensure that the VM host recognizes thefailed over storage. a. • The replicated disk on the Remote Site Hyper-V host must be configured with thesame drive letter that is assign...
Page 18 - Matrix recovery management GUI overview; Figure 2 Matrix recovery management home screen
Matrix recovery management GUI overview The home screen for the Matrix recovery management user interface includes tabs for configurationand administration tasks—see Figure 2 (page 18) . Figure 2 Matrix recovery management home screen Matrix recovery management user interface tabs • Home Information...
Page 19 - Matrix recovery management configuration steps; Figure 3 Configuration steps
Matrix recovery management configuration steps Figure 3 (page 19) illustrates the six-step Matrix recovery management configuration process. After the Matrix recovery management configuration process is completed at the Local Site, Matrixrecovery management must be configured at the Remote Site. To ...
Page 20 - Matrix recovery management export and import operations; replica IO service
6. From the Sites tab at the Remote Site, import the Local Site Matrix recovery management configuration. For more information, see “Matrix recovery management export and import operations” (page 20) . 7. Test the recovery logical servers. All imported Recovery Groups are in maintenance mode,allowin...
Page 22 - DR protection for IO services; “Creating and installing a User Defined storage; DR Protection of IO services configuration overview; “Configure OO workflow for optional
NOTE: • Recovery Groups can be imported one at a time only. You must repeat the import... → Select import file... procedure for each Recovery Group that you import. • If a Recovery Group in the exportconfig file has the same name as a Recovery Group at the importing site, it is not imported. If you ...
Page 23 - Configure IO properties
NOTE: • When you use Matrix recovery management to DR protect VMware ESX based IO servicesthat have been deployed from an IO template using an ICVirt template or a VM templateon the vCenter server at the Local Site, an ICVirt or VM template with same name mustbe available at the Remote Site before y...
Page 25 - primary IO service
For more information, see the HP Matrix Operating Environment 7.2 Infrastructure OrchestrationUser Guide available at http://www.hp.com/go/matrixoe/docs . Configure OO workflow for optional email notification You have the option to configure OO workflows to provide system administrators with automat...
Page 26 - Testing Recovery Groups; “Recover the CSV from
3 Testing and failover operations This chapter describes Recovery Group testing, planned failovers, and unplanned failovers usingthe Matrix recovery management Activate and Deactivate operations. Testing Recovery Groups There are two ways to test Recovery Groups: • Using Maintenance Mode to test ind...
Page 27 - A note about Microsoft Hyper-V Server failover:; Planned failover
4. Place the Recovery Group into Maintenance Mode at the Remote Site using the Enable Maintenance Mode button in the Matrix recovery management Recovery Groups tab. For logical servers, use the Logical Servers Activate operation in the Tools menu of the Visualization tab in Matrix OE visualization t...
Page 29 - Unplanned failover
3. Select each Recovery Group Set that you want to activate or click the check-box on the leftside of the banner of the Activate Recovery Groups at the Local Site window to select all of the Recovery Group Sets for activation. 4. Click Activate Recovery Groups to start the activation operation. A wi...
Page 31 - Dynamic workload movement with CloudSystem Matrix
4 Dynamic workload movement with CloudSystem Matrix This chapter explains how you can configure cross-technology logical servers that can be managedwith Matrix recovery management. The HP Matrix Operating Environment facilitates the fluid movement of workloads between dissimilarservers within a site...
Page 32 - Capabilities and limitations; NPIV
Capabilities and limitations Using the tools and procedures described in this chapter you can: • Configure and manage a logical server that can perform physical to virtual cross-technologymovements within the datacenter. • Configure and manage a DR Protected logical server that can be failed over ac...
Page 35 - Supported platforms; Prepare a logical server with a portable image.
both types of servers. The recovery site can have a physical/virtual combination also, or haveonly virtual machine hosts. Supported platforms The procedures for enabling movement between physical and virtual servers described in thischapter apply to physical servers, hypervisors, and workload operat...
Page 38 - “Setting a failover target type preference” (page 46); Configuring and managing portable OS images; Driver installation
NOTE: The Matrix recovery management Site configuration can be set up to preferentially activate the logical server on a physical server at one site and a VM host at the other site. Formore information, see “Setting a failover target type preference” (page 46) . Configuring logical servers for movem...
Page 39 - Portability groups
The command-line interface for PISA is described below. The options are mutually exclusive. PISA runs on supported versions of Windows only, and it requires that the user be a member ofthe Administrator user group. Usage: hppisa -h, -?, -help Show this information-e, -enable Enable the LSI driver-d,...
Page 41 - Defining cross-technology logical servers; Placing a logical server into a portability group; Portability Group
Figure 10 Selecting group members and targets Provide a name and optional description for the portability group. The name will be used fordefining logical servers. The set of Group Types is selected automatically based on the targetsinserted into the portability group. Valid combinations of targets ...
Page 43 - “Portability groups” (page; Storage definition; and
Logical servers can be made portable through techniques described in “Portability groups” (page 39) . NOTE: You must determine whether the provisioned operating system within a logical server performs as desired on a variety of platforms. If a logical server has never been active on a platformtype, ...
Page 44 - Moving between technologies; Unlike Move
When defining storage for a portable logical server, you must select SAN Storage Entry . For flexibility and movement between underlying technology types, storage must be presented to theWWNs tied to the Virtual Connect server profile, and storage must also be presented to any ESXVM hosts that are p...
Page 45 - Target attributes; Figure 18 Modifying logical server target attributes
Targets for a logical server are selected from that logical server's portability group. The portabilitygroup members are then further filtered based on resource availability, including CPU and memoryresources as well as network and SAN connectivity. NOTE: Networks in Virtual Connect must be named id...
Page 46 - Target type preferred
Moving between blade types For logical servers with target attributes, the logical server management software can identify morepossible targets when moving or activating a server. As with all cross-technology logical servers,you must ensure that the logical server can function appropriately on vario...
Page 48 - Limitations; Hyper-V support limitation for bidirectional configuration; mxsync; Minor issues; Firefox browser cannot be used for site export operations
5 Issues, limitations, and suggested actions This chapter lists issues and limitations for this release, categorized as follows: Limitations Limitations of the implemented functions and features of this release Major issues Issues that may significantly affect functionality and usability in this rel...
Page 49 - Lvm.DisallowSnapshotLun; Activation or deactivation job hangs
ESX configuration setting required for VMFS datastores of Matrix recoverymanagement managed logical servers to be visible at Remote Site Under the following conditions, Matrix recovery management requires a specific ESX configurationsetting to retain the signature of a VMFS datastore so it will be v...
Page 51 - Troubleshooting; “Configuration troubleshooting” (page 51); mxdomainmgr
6 Troubleshooting This chapter provides troubleshooting information in the following categories: • “Configuration troubleshooting” (page 51) • “Configuration error messages” (page 53) • “Warning messages” (page 56) • “Matrix recovery management Job troubleshooting” (page 57) • “Failover error messag...
Page 53 - Configuration error messages
• No configuration operation can be run Possible causes include: ◦ An Activate , Deactivate , or Import operation is in progress. ◦ Another configuration operation may be in progress • Unable to import Storage Management Servers as part of an import operation Possible causes include: ◦ The Storage M...
Page 56 - Warning messages; This section lists Matrix recovery management warning messages.
Unable to run Matrix recovery management operations because Matrix recovery management Job is in progress or another Matrix recovery management configuration operation is in progress. Error message If an Activate or Deactivate operation is in progress, no configuration operation is allowed, because ...
Page 57 - Matrix recovery management Job troubleshooting; conf
Warning: Matrix recovery management is quiesced. No new operations will be allowed. Warningmessage Matrix recovery management has been quiesced. All configuration buttons (Create, Edit, Delete, etc…) are disabled. Cause Wait for Matrix recovery management to be unquiesced. Action Warning: Unable to ...
Page 60 - Failover error messages
• Matrix recovery management job failed because of unlocatable logical server in Matrix OElogical server management. Possible causes include: ◦ A logical server managed by Matrix recovery management was removed from MatrixOE logical server management before it was unmanaged in Matrix recovery manage...
Page 61 - Cluster Extension XP\log; DR Protected IO serivces troubleshooting; “DR protection for IO
Matrix recovery management log files There are several log files available with detailed information that you can view to help identifythe sources of Matrix recovery management failover or failback problems: • For errors that occur during the initial Matrix recovery management configuration steps, v...
Page 62 - DR Protected IO services configuration troubleshooting; Failed to import an IO service
DR Protected IO services configuration troubleshooting In addition to the configuration issues addressed in this User Guide that are common to both logicalservers and IO services, the following configuration issues apply to IO services only: • Failed to get a list of IO services that can be included...
Page 63 - IO services configuration error messages
IO services configuration error messages Unable to get the IO service. Error message The IO service does not exist or Matrix recovery management failed to get the IO service informationfrom the Matrix infrastructure. Cause Check the Matrix recovery management and IO log files for more information on...
Page 64 - DR Protected IO services failover troubleshooting; Failed to activate IO service in a Recovery Group
DR Protected IO services failover troubleshooting In addition to the failover issues addressed in this User Guide that are common to both logicalservers and IO services, the following failover issues apply to IO services only: • Failed to activate IO service in a Recovery Group Possible Causes: ◦ St...
Page 65 - Support and other resources
7 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or softwa...
Page 66 - How to use your software technical support and update service; HP authorized resellers
With this service, Insight Management customers benefit from expedited problem resolution aswell as proactive notification and delivery of software updates. For more information about thisservice, see the following website: http://www.hp.com/services/insight . Registration for this service takes pla...
Page 67 - Matrix recovery management documentation; HP Insight Management Support Matrix; Typographic conventions; This document uses the following typographical conventions:
Matrix recovery management documentation For more information on Matrix recovery management, see the following sources: • HP Insight Management Support Matrix Provides Matrix recovery management support information along with other HP Insighthardware, software, and firmware support information. Avai...
Page 69 - The CSV is in the
A Recover the CSV from online pending state If you perform an activate operation at the remote site without taking the CSV offline at the localsite, you might see the following symptoms at the local site: • No storage information is available when navigating to the storage view in the WindowsFailove...
Page 70 - B Documentation feeback; when submitting your feedback.
B Documentation feeback Documentation feeback HP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any error, suggestions, or comments to Documentation Feedback( [email protected] ). Include the document title and part number, version number, ...
Page 71 - Glossary
Glossary bidirectionalfailover A Matrix recovery management feature that allows Recovery Group Sets to be activated ordeactivated at either the Local Site or the Remote Site. At any point in time there can be activatedand deactivated Recovery Group Sets at both sites. In the event of a disaster, or ...
Page 72 - Table 1 The Matrix recovery management configuration process
rehearsal, the Recovery Group and its corresponding logical servers and IO services can bebrought back under the control of Matrix recovery management. Matrixinfrastructureorchestrationservices Matrix infrastructure orchestration services (IO services) quickly provision infrastructure toautomaticall...