HP P9000 Replication Manager Software User Guide Part number: TB584-96037 Tenth edition: November 2011
Legal and notice information © Copyright 2010-2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Preface .............................................................................................. 19 1 Introduction ..................................................................................... 21 About Replication Manager ....................................................................................................... Example of a replication environment .................................................................................... Replication Manager features ............
Pair configurations subwindow ............................................................................................. Pair configurations subwindow ............................................................................................. Structure of the Pair Configurations view ................................................................................ Applications subwindow .....................................................................................................
6 Setting up authorities ........................................................................ 83 Adding users and assigning permissions ...................................................................................... About users, permissions, and roles ..................................................................................... About user roles .................................................................................................................
Adding command devices ................................................................................................. Setting up remote paths ........................................................................................................... About remote paths .......................................................................................................... Conditions for specifying remote paths ................................................................................
Launching the Pair Configuration Wizard ............................................................................ Limitations for launching the Pair Configuration Wizard .................................................. Pair configuration definition workflow ........................................................................................ Defining copy pairs and pair groups ......................................................................................... About copy pairs .................
About distributing copy group definitions ............................................................................. Example of copy group definition distribution scenario .................................................... Prerequisites for distribution destination hosts (copy group definitions) ............................... Conditions for changing copy group distribution primary host .......................................... Conditions that disrupt copy group distribution relationships ............
Takeover operation .................................................................................................... Swap operation ......................................................................................................... Force-split operation ................................................................................................... Takeover-recovery operations (resync and recreate) ........................................................ Advanced recovery use cases .............
Checking copy pair configuration (perspective of specific copy group) .............................. Viewing copy pair configuration definition information .......................................................... Viewing information about a configuration definition file (open systems) ............................ Viewing prefix information (mainframe systems) ............................................................. Monitoring pair status ...............................................................
Viewing copy group information in the Hosts view (open systems) ........................................... Viewing information about pair management servers ................................................................... Viewing information about prefixes belonging to a host (mainframe systems) .................................. Viewing information about volumes belonging to a host ...............................................................
Removing applications from a site ............................................................................................. Deleting sites ......................................................................................................................... Deleting individual sites .................................................................................................... Deleting multiple sites ................................................................................................
Using an external authorization server (authorization groups) ................................................. 346 20 Managing security ....................................................................... 349 About security settings ............................................................................................................. Functions for setting security ..............................................................................................
Replica data types and configuration requirements ...................................................................... Software that should not be used during replica operations .......................................................... About creating application replicas ........................................................................................... Create application replica workflow ...................................................................................
About system maintenance ....................................................................................................... Functions for Replication Manager maintenance ................................................................... Explorer menu items for Replication Manager maintenance ................................................... About operation modes ........................................................................................................... Viewing the operation mode ....
Glossary .......................................................................................... 465 Index ...............................................................................................
Figures 1 Two site configuration in an open system .................................................................... 25 2 Example system configuration in a mainframe system (using HP StorageWorks P9000 for Business Continuity Manager Software) ..................................................................... 26 3 Example system configuration in a mainframe system (using P9000 mainframe agent) ..... 27 4 Example system configuration managing copy pairs and application replicas .................
Tables 1 Pair management server configurations ...................................................................... 34 2 Parameters for backup server calculations .................................................................. 67 3 User roles .............................................................................................................. 85 4 Pair definition and replica operations ........................................................................ 85 5 Pair operations ...............
Preface This document describes how to use the HP StorageWorks P9000 Replication Manager software.
Preface
1 Introduction This chapter provides an overview of Replication Manager features and architecture. It also provides an introduction to supported system configurations and an operations roadmap. About Replication Manager Replication Manager is a business continuity management framework that allows you to centrally configure, monitor, and manage in-system or remote business continuity products, for both mainframe and open environments.
Replication Manager features Replication Manager provides the following features to assist storage administrators: • • • • • Centralized management of a replication environment Integrated database backup management Visual representation of replication structures Monitoring and immediate notification of error information Modification of replication structures NOTE: If Replication Manager is installed without a license (or the existing license expires), only basic pair configuration functions will be availa
Modification of replication structures Replication Manager provides capabilities to configure additional copy pairs as business operations expand and improve performance by expanding buffer capacity for copying volumes. You can also change pair states manually after error recovery. Using the wizards provided in the GUI, you can set up pairs while visually keeping track of complex replication structures.
manage the hosts by registering the instance of HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent installed on each host in the local and remote sites as an information source. • Database and backup servers: To manage database replicas, the system requires two servers: a database server that manages the primary volume, and a backup server with the secondary volume.
Figure 1 Two site configuration in an open system User Guide 25
Figure 2 Example system configuration in a mainframe system (using HP StorageWorks P9000 for Business Continuity Manager Software) 26 Introduction
Figure 3 Example system configuration in a mainframe system (using P9000 mainframe agent) User Guide 27
Figure 4 Example system configuration managing copy pairs and application replicas Replication Manager operations roadmap The following figure shows the flow of tasks during system configuration, operation, and maintenance.
TIP: If you want to change the system configuration or the Replication Manager settings during operation, you should back up the database before and after making any changes. For details on system configuration, system maintenance, and database backup, see the HP P9000 Replication Manager Software Configuration Guide.
Introduction
2 Getting started This chapter describes initial settings needed to begin Replication Manager operations and procedures for setting up the prerequisite environment for pair management. It also includes quick references to typical operations performed using Replication Manager. Initial setup After Replication Manager has been installed on a management server, you must configure initial settings needed to begin Replication Manager operations.
Ensure that all of the conditions below are satisfied for open systems: • The requirements (microcode and system configuration) for Business Copy or Continuous Access or other required storage system volume replication functions must be satisfied. For details about the requirements and the configuration procedures, see the storage system documentation for the applicable storage system model.
• About setting up storage systems, page 107 Setting up the prerequisite environment (mainframe systems) To manage mainframe pairs, you must first set up storage systems using Remote Web Console. It is also necessary to configure mainframe hosts for BCM operation and set up BCM definition files. Depending on the copy types to be configured, different storage system setup operations need to be performed with Remote Web Console.
SQL Options tab (SQL Server only): • SQL instance • If a backup server is used, it should also be configured in the same way as the database server (except for the Replica Options tab). • For a cluster configuration, Shared Data Path is set in the Cluster Options tab of the Setup Application dialog box. • Consult “About concealing/revealing replica volumes” on page 64 and “Precautions for replica operations” on page 372 for additional requirements and information.
Name 1:M (one-to-many) N:M (N-to-many) N:N (N-to-N) Description A configuration in which the same configuration definition file that defines the primary volume on the primary site is managed by a single server, and the configuration definition file that defines the secondary volume on the secondary site is managed by multiple servers. A combination of the N:1 and 1:M configurations.
2. Enter the Group Name. 3. Select the Site and Server Name for the primary and secondary pair management servers. (Select Others for storage systems that are not assciated with a site.) 4. Select or specify an Instance number. (You must provide a UDP Port if you specify an instance number.) 5. Click Add to register the pair management server combination that manages the configuration file. 6. To delete one or more entries from the Pair Management Server List, select them and click Delete. 7.
Identifying a pair management server associated with a copy group You can determine the pair management server associated with a copy group by putting the cursor over a copy pair in any topology display (such as My Copy Groups). Confirming the prerequisite environment The following conditions need to be met before Replication Manager can be used. For more information, see HP P9000 Replication Manager Software Configuration Guide.
2. Enter a user ID and password. When you log in to Replication Manager for the first time, you must use the built-in default user account and then specify Replication Manager user settings. The user ID and password of the built-in default user account are as follows: User ID: System Password: manager (default) If Replication Manager user settings have already been specified, you can use the user ID and password of a registered user to log in.
Operations Descriptions Chapter 5, page 71 How to perform volume discovery, which is a prerequisite for defining and managing copy pairs. Chapter 6, page 83 How to specify user account settings and permissions to restrict the scope of operations allowed for each user. Chapter 7, page 95 How to organize resources such as hosts and storage systems into logical sites for easier management, and identify frequently monitored resource groups.
Getting started
3 Replication Manager console This chapter describes the Replication Manager console and its main features. This chapter also provides descriptions of various functional views available in the Replication Manager console. Understanding the console layout Replication Manager provides a simple, easy-to-use, centralized management console for monitoring and visualizing volume replication configurations and status information. The following example is an illustration of Replication Manager console layout.
• Restrictions related to web browsers, page 439 Global tasks bar area The global tasks bar area contains menus and action buttons for Replication Manager functions, and also contains information about the logged-in user. A triangle icon is provided to show or hide the Explorer and Dashboard menus. Global tasks bar area menu items Menu Explanation Close Closes the window, but does not log the user out from Replication Manager and other active P9000 Command View AE Suite products.
Explorer menu items Menu item Explanation Displays resources such as application servers or hosts, storage systems, and pair management servers managed by Replication Manager. • Hosts: Displays information about the hosts managed by Replication Manager (hosts view). Resources • Storage Systems: Displays information about the storage systems managed by Replication Manager (storage systems view).
Menu item Explanation Tasks: Displays the tasks scheduled for copy pairs. Tasks Workflows: Displays the workflow generated for copy pairs. Alerts Alerts: Allows you to check alerts or edit alert settings. User Profile: Allows you to check or edit user information. Settings License Info: Sets the Replication Manager license information. Refresh Setting: Allows you to update the information managed by Replication Manager and set the interval for updating the information.
Dialog box A dialog box is a pop-up window displayed when an action button is clicked. The window displayed when a specific action button is clicked is called the action-name dialog box. Clicking Help in a dialog box displays the online help page that describes the items displayed in the dialog box. Functional views Replication Manager provides three functional views that display pair configurations and the status of the replication environment from different perspectives.
Hosts subwindow Structure of the Hosts view The figure below shows the structure of the Hosts view with the list of hosts as the starting point. The subwindow changes according to the hierarchy displayed in this structure.
Storage Systems subwindow The Storage Systems subwindow lets you view storage systems containing paired volumes and the copy licenses registered for each storage system. For details on the meanings of the icons, see “Icons representing the management target” on page 442 or “Display formats used when no pertinent information is available” on page 455.
Displays the types of the storage systems. Storage System Type For mainframe systems, you can identify the type of a storage system only when the storage system is registered in the Device Manager server and that server is registered as an information source. If you cannot identify the type, the storage system family is displayed (from among XP1024/XP128, XP12000/10000/SVS200, and XP24000/ 20000). Displays the copy types for which licenses are registered in open systems or mainframe systems.
Pair configurations subwindow The Pair Configurations subwindow lets you view pair management servers with copy pair definitions (P9000 RAID Manager configuration definition file) and related information. Pair Management Servers Pair Management Server Displays the name of the pair management server that issues instructions to storage systems to perform a copy pair operation.
Information Source Displays the name (nickname) of the Device Manager server, instance of HP StorageWorks P9000 for Business Continuity Manager Software, or instance of P9000 mainframe agent. Pair configurations subwindow Structure of the Pair Configurations view The figure below shows the structure of the Pair Configurations view with the list of copy pair configuration definitions as the starting point. The subwindow changes according to the hierarchy displayed in this structure.
TIP: For mainframe pair configurations, the tree structure of the pair configurations appears differently for copy groups within containers and copy groups that are not. • For copy groups not within a container, the copy group nodes are displayed directly under the prefix nodes and the node name of the copy groups is consistent with the dataset names.
Applications Item Description Application Displays Exchange or SQL. Displays the status icon that represents the current state of protection. Data Protection Status See “About data protection status” on page 288 for a list of icons and their meanings. Applications subwindow Structure of the Applications view The figure below shows the structure of the Applications view with the list of applications (Exchange or SQL) as the starting point.
User Guide 53
Replication Manager console
4 Setting up information sources Before you can use Replication Manager to manage resources, you must register an information source. In open systems, this information source is the Device Manager server. In mainframe systems, this information source is either HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent.
TIP: If you register Device Manager servers, you can configure links for invoking the Web client instances of registered Device Manager servers from Replication Manager. You can register links to the servers in the Go menu of the global tasks bar area. You can set the link by executing the hcmdslink command on the management server. For details on this command, see the HP P9000 Replication Manager Software Configuration Guide.
Adding a Device Manager server TIP: Only a user who has the Admin permission can add a Device Manager server. To add a Device Manager server: 1. Ensure that you have the following information: 2. • IP address or host name • Protocol to be used for communication with Replication Manager software (HTTP or HTTPS) • Port number (the server.http.port value in the server.
Adding an instance of HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent CAUTION: If you have an HP StorageWorks P9000 for Business Continuity Manager Software environment where multiple BCM instances have overlapping copy group or disk configuration definition files, see “When multiple BCM instances have overlapping configuration definition files” on page 59 first.
8. Click Close to finish registration. The information about the instance of HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent is displayed in the BC Manager / Mainframe Agent. Once an instance of BCM is registered, Replication Manager loads the configuration information associated with the BCM for the purposes of scanning the volumes as described in “About mainframe volume discovery” on page 71.
Replication Manager version 6.6.1 (7.1.1) 6.7.0 (7.2) 6.1 6.2 6.3 6.4 7.0 7.0.1 7.1.0 7.1.1 7.2 1 1 1 1 1 1 1 1 8, 9 1 1 1 1 1 1 1 1 1 Legend: 1. 2. No restrictions. The following functions are not supported: • Management and distribution of disk configuration files using volume scans • Copy pair definitions • Changing of copy pair statuses • SSL communication with BCM-Agents (IHS) 3. 4. Basic Hyper Swap is not supported for XP12000/XP10000/SVS200 or XP24000/XP20000.
About application discovery Application discovery is the process by which Replication Manager identifies the resources associated with an application server and the backups server where the replicas are to be stored. Once an instance of Application Agent is registered and the pair configuration (primary and secondary volumes) set up, the discovery process proceeds and the resource information is collected or refreshed.
6. Click OK to register the instance of Application Agent. A confirmation dialog box with information about the new instance is displayed. 7. Review the information and click Confirm. Upon successful registration, a completion dialog box is displayed. 8. Click Close to finish registration. The information about the instance of Application Agent is displayed.
5. In Target Instance of the Server Options tab, set up the HORCM instances managing the primary and secondary volumes. You can choose existing HORCM instances or specify the HORCM number and the type (primary or secondary). NOTE: Database and backup servers require the setting of RAID Manager Installation path for each node.
8. The Replica Options tab can be used to set the following: • For database servers: Protection Status Options (to set the status of old replicas to “Critical”), Replica Task Options (to define the behavior when a task fails), and Email Options (for notification of task status).
cause a conflict when mounted on the backup server. Conversely, such volumes must be revealed (made visible again) before their associated copy pairs or groups can be deleted. NOTE: Before creating a new HORCM instance and copy groups, set up Application Agent on the database server with the Refresh application configuration when finishing the setup selected in the Server Options tab of the Setup Application Agent dialog box.
Parallel verification count and number of backup servers The parallel verification count controls the number of hosts that can perform backup verifications simultaneously. The default value is 1, meaning that when executing a backup for one backup server with multiple database servers at the same time, all concurrent backups remain in standby until the backup for each database server is finished.
2. Calculate the time necessary to back up a database using this formula: DB_BACKUP_TIME = {(IS / IS_VERIFY) * IS_NUM + (LOG_NUM / LOG_VERIFY)} * SG_NUM + RESYNC_TIME NOTE: Because the variables IS_VERIFY and LOG_VERIFY are highly dependent on server and storage I/O performance, actual values are difficult to obtain. For best results, use the assumed values supplied. 3.
Parameter Description Notes LOG_VERIFY Verification performance of the transaction log file (per second) Depends on the performance of the storage and the server.A value of 7 per second is assumed for the calculation. RESYNC_TIME Time required to re-synchronize the pair to back up per database server (seconds) You must supply this value. Depends on the performance of the storage and the server.
The operation may take several minutes.
Setting up information sources
5 Discovering volumes Before you can use Replication Manager to define or manage copy pairs, it is necessary to discover volumes. As a result of this discovery process, Replication Manager identifies a list of volumes that can be used for pair definition. This chapter describes how to discover volumes. Discovering volumes (open systems) Open systems volumes are discovered by refreshing configuration information after registering an information source.
2. Replication Manager uses this information to perform a series of scans to locate the volumes that can be used for pair configuration. 3. Replication Manager identifies the disk configuration and stores the list to the disk configuration definition file. TIP: Although Device Manager provides common functions for Replication Manager operations, BCM is the sole source for mainframe information.
Example volume scan procedure Types of volume scans Replication Manager uses one of three available scanning methods to discover mainframe volumes: Local scan (Gen'ed) This method discovers volumes recognized by the mainframe host within a specified DEVN/VOLSER range. Local scan (Non Gen'ed) This method discovers volumes within a specified storage system and LDEV range. As a prerequisite, a local scan (Gen'ed) must be performed on the scan target storage system.
• Deleting a volume range from a volume range list, page 75 • Restrictions for deleting volume ranges, page 75 Adding a volume range to a volume range list To add a volume range to the volume range list: 1. Display the list of disk configuration definition files on the Disk Configs tab in the BC Manager / Mainframe Agent subwindow. For details on how to display disk configuration definition files, see “Displaying disk configuration definition files” on page 79. 2.
• Overlapping volume ranges cannot be specified. • When Non Gen'ed scan or Remote scan is selected, a starting number of Dummy DEVN that would cause the value of Dummy DEVN to exceed FFFF during the volume scan cannot be specified. Deleting a volume range from a volume range list To delete a volume range from a volume range list: 1. Display the list of disk configuration definition files on the Disk Configs tab in the BC Manager / Mainframe Agent subwindow.
2. Select a disk configuration definition file. 3. Set the volume range for the scan. For details, see “Adding a volume range to a volume range list” on page 74. 4. Select the target hosts for disk list distribution. For details, see “Selecting targets for disk configuration distribution” on page 78. 5. Check the information and click OK to begin the volume scan. The scanning process may take some time.
Example disk list distribution scenario Prerequisites for distribution destination hosts (disk configuration definitions) HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent hosts (with disk configuration definition files) must satisfy the following conditions to be distribution destination candidates: • The DADIDs of the distribution destination candidate host are the same as the origin of distribution.
Conditions Whether volume has been added to a pair* Copy type Volume type Information displayed when no restrictions apply to resource groups Information displayed when restrictions apply to resource groups Only the DADID of the volume added to the pair is displayed. Only the DADID of the volume added to the pair is displayed.
5. To delete a distribution target, deselect the check box for the candidate distribution host. TIP: The copy group definition file will not be distributed if you deselect a host registered as a distribution target. 6. To distribute the disk configuration definition file when the disk list is created, select the Distribute the disk config when creating the list check box. (Uncheck this check box when you want to skip disk list distribution.) 7. Click OK.
To edit a disk configuration definition file: 1. From the Explorer menu, choose Administration and then Information Source. The Information Source subwindow appears. 2. Expand the object tree, and select BC Manager / Mainframe Agent. The BC Manager / Mainframe subwindow appears. 3. Click the Disk Configs tab. The list of disk configuration definition files managed by Replication Manager are displayed in the Disk Configs tab. 4.
3. Under the DEVNs tab, select the Paired tab. The paired DEVN list is displayed. This list also displays copy types associated with established copy pairs. 4. Review the information in the paired DEVN list. Related topics • Reviewing unpaired DEVN list, page 81 • Reviewing unpaired LDEV list, page 82 Reviewing paired LDEV list To review the paired LDEV list: 1. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 2.
Reviewing unpaired LDEV list To review the unpaired LDEV list: 1. From the Explorer menu, choose Resources and then Storage Systems. The Hosts subwindow appears. 2. Expand the object tree, and then select a storage system under Storage Systems. The storage-system-name subwindow appears. 3. On the CUs tab, select a control unit number. The CU-number subwindow appears. 4. Under the LDEVs tab, select the Unpaired tab. All Mainframe volumes located on the storage system are listed. 5.
6 Setting up authorities Before you can use Replication Manager, you must specify user account settings and permissions to restrict the scope of operations allowed for each user. Replication Manager controls access by using resource groups that restrict accessible ranges, and user management roles that restrict user operations. To control access to Replication Manager resources, you need to create resource groups and associate users with resources. This chapter describes how to configure access control.
Permissions and management roles In addition to the built-in account (user ID: System), there are permissions that grant access to all Replication Manager functions. Permissions can be allocated in any combination, but are broad in nature and do not control access to individual functions. The following table groups the permissions into two categories known as management roles.
are fixed and cannot be customized.The user roles and their capabilities are shown in the following table. Table 3 User roles User Role Description Storage administrator Responsible for all replication tasks, including resource allocation (S-VOLs). Copy pair administrator Responsible for all replication tasks, except resource allocation. Application administrator Responsible for data protection of applications, but cannot change pair configurations.
Basic (mainframe and open) Advanced (open only) Role Create Delete Application operator Resync/split Restore Takeover Swap Force-split Takeover-Recovery X TIP: In most cases, assignment of the roles determines whether a function can be performed by disabling the control or button on a given window (for example, by dimming the Create button). For some functions, the controls may not be displayed at all.
Role Launch Pair Configuration Wizard (Allocate S-VOLs) Launch “Edit Workflow” window (Define Copy Groups) Launch Change Pair Status Wizard (Create/delete copy pairs, restore copy pairs) Launch Restore Replica Wizard Application Administrator Disabled Disabled Enabled1 Enabled Disabled Disabled Enabled1,2 Disabled Application Operator Legend: 1. 2. Create/delete operation is not available; restricted operations are not listed on the Operations field of the Change Pair Status Wizard.
Changing user permissions You can specify the permissions required to use a specific P9000 Command View AE Suite product for each registered user. To allow existing P9000 Command View AE Suite product users to also use Replication Manager, you must grant Replication Manager management permissions to those users.
Setting up resource groups Replication Manager controls access by using resource groups that restrict the range of resources that can be accessed by users. To control access to Replication Manager resources, you need to create resource groups and associate users with resources. About resource groups A resource group is a collection of applications or sites that are grouped together and associated with specific users to restrict the resources that users can access.
Creating resource groups To create resource groups: 1. From the Explorer menu, choose Administration and then Resource Groups. The Resource Groups subwindow appears. 2. Click Create Group. The Create Resource Group dialog box appears. 3. Register the information about the resource group you want to create. The created resource group is displayed in the Resource Groups subwindow. 4. Add resources to the resource group.
• Adding hosts to a resource group, page 91 • Creating resource groups, page 90 Related topics • About resource groups, page 89 Adding hosts to a resource group You can add hosts as resources to existing resource groups. TIP: You cannot register the same host in more than one resource group. In addition, you cannot add hosts to the All Resources group (where all hosts are registered automatically). To add hosts to a resource group: 1. From the Explorer menu, choose Administration and then Resource Groups.
4. Select the storage systems you want to add, and then add them. The added storage systems are displayed on the Storage Systems page. Related topics • About resource groups, page 89 • Removing storage systems from a resource group, page 358 Adding users to a resource group You can add users to existing resource groups. To permit a user to access all resources, register the user in the All Resources group. You can also register a single user in multiple resource groups other than the All Resources group.
Adding applications to a resource group You can add hosts/applications as resources to existing resource groups. TIP: You cannot register the same host/application in more than one resource group. In addition, you cannot add hosts/applications to the All Resources group (where all hosts are registered automatically). To add hosts/applications to a resource group: 1. From the Explorer menu, choose Administration and then Resource Groups. The Resource Groups subwindow appears. 2.
3. On the Applications page, click Add Hosts. The Add Hosts - resource-group-name (Applications) dialog box appears. 4. Select the hosts/applications you want to add, and then add them. The added hosts/applications are displayed on the Applications page.
7 Organizing resources In Replication Manager you can organize resources such as hosts and storage systems into logical sites for easier management. You can also designate frequently monitored resource groups as My Copy Groups. This chapter describes different ways to organize resources. About resources Resources are entities managed by Replication Manager. These include application servers, storage systems, and pair management servers that constitute the replication environment.
Setting up sites Sites allow you to manually group resources under one name for easier management. You can define your own site and register resources such as hosts and storage systems. Grouping of resources into logical sites is especially useful when you have remote sites. Although you can define logical sites with any combination of resources, managing many resources from the web interface is easier when logical sites are created based on the resources of actual sites.
Adding sites To add sites: 1. From the Explorer menu, choose Shared Views and then Sites. The Sites subwindow appears. 2. Click Add Site. The Add Site dialog box appears. 3. Enter information about the sites you want to add, and then add them. The added sites are displayed in the Sites subwindow.
4. After sites have been added, specify the resources for the sites.
To add hosts to a site: 1. From the Explorer menu, choose Shared Views and then Sites. The Sites subwindow appears. 2. Expand the object tree, and then select a site by clicking on the site name in the Site List. The site-name subwindow appears. 3. Click the Hosts link. The Hosts subwindow appears. 4. Click Add Hosts. The Add Hosts dialog box appears. 5. Select the hosts you want to add, and then add them. The added hosts are displayed in the Hosts subwindow.
Adding pair management servers to a site You can add pair management servers to existing sites. After pair management servers have been added, the copy pair configuration definitions managed by the servers can be accessed from the nodes under the site. For open systems, if you need to use, as a pair management server, a host that has already been added to a site, you must add the host to the site again as a pair management server.
3. Click the Applications link. The Applications subwindow appears. 4. Click the link for the desired application server. The Hosts list is displayed. 5. Click Add Hosts. The Add Hosts dialog box appears. 6. Select the hosts you want to add, and then add them. The added application servers are displayed in the Hosts list.
• Explorer menu items for My Copy Groups management , page 307 • My Copy Groups management functions, page 307 Examples of My Copy Groups The following figure shows a display example of My Copy Groups. Display example of My Copy Groups If the copy groups registered in My Copy Groups have a multi-target configuration or cascade configuration, the relationships among the copy groups are displayed as described below.
In this example, the secondary volume of Copy Group_A is the primary volume of Copy Group_B and Copy Group_C. If a single copy group is connected to multiple copy groups The secondary volume of the multiple copy groups on the left is the primary volume of the single copy group on the right. In this example, the secondary volume of Copy Group_A and Copy Group_B is the primary volume of Copy Group_C.
In this example, the secondary volume of Copy Group_C is used as the primary volume of Copy Group_D, the copy type of which is Business Copy. Example (2) In this example, the secondary volume of Copy Group_A is used as the primary volume of Copy Group_D and Copy Group_E, both of which have the Business Copy copy type. Example (3) In this example, the primary volume of Copy Group_A is also used as the primary volume of Copy Group_D and Copy Group_E, both of which have the Business Copy copy type.
Creating My Copy Groups To create My Copy Groups: 1. From the Explorer menu, choose My Groups and then My Copy Groups. The My Copy Groups subwindow appears. 2. Click Edit My Copy Groups. The Edit My Copy Groups dialog box appears. 3. In the list, select the copy groups you want to display in My Copy Groups. 4. Click OK to update My Copy Groups. The information displayed in the My Copy Groups subwindow is refreshed.
Organizing resources
8 Setting up storage systems You can use Replication Manager to replicate volumes or change copy pair definitions. It is necessary to configure prerequisite settings before replicating volumes. You can specify the prerequisite settings centrally from Replication Manager, for many storage systems across multiple sites. This chapter describes the tasks for preparing the replication environment and setting up storage systems.
NOTE: For mainframe systems: Depending on the copy types to be configured, some of the storage system setup operations need to be performed with Remote Web Console. For details, see the HP P9000 Replication Manager Software Configuration Guide.
TIP: Each function can be used only for the resources in resource groups associated with the user. Explorer menu items for setting up storage systems The following table shows the Explorer menu items that are related to setting up storage systems, user permissions (Replication Manager management), and whether the items can be executed with the indicated permissions.
Flow of specifying the settings required before replicating volumes Setting up V-VOLs Replication Manager supports creation of V-VOLs on storage system configurations. This function is only supported for XP24000/XP20000 storage systems. You can create V-VOLs and associate them with volume pools, using the Create V-VOL wizard. For details on how to create V-VOLs, see “Creating V-VOLs” on page 112 About creating V-VOLs Replication Manager supports creation of V-VOLs on storage system configurations.
V-VOL limits The maximum number of V-VOL groups that can be created for each storage system is 65,280. For XP24000/XP20000 storage systems, the maximum number of V-VOLs in a V-VOL group is 1024. For HP StorageWorks P9500 storage systems, the default maximum number of V-VOLs that can be created at one time with the Create V-VOL Wizard is 900. (Exceeding this limit will fail with the error RPM-01014.) To increase this value, you must modify the server.http.entity.maxLength property in the server.
Conditions CVS has been installed CVS has not been installed Number of P-VOLs that can be added (in the Select Primary LDEV-Target LDEVs window) No limit 1 Number of Snapshot copy generations (in the Primary LDEVs-Count of Snapshot window) 1024 1 (inactive) About the Create V-VOL Wizard Replication Manager includes a Create V-VOL Wizard for creating V-VOLs and associating them with volume pools.
2. Expand the object tree, and then select a storage system under Storage Systems. The storage-system-name subwindow appears. 3. Click the Open link. The Open subwindow appears. 4. Under the Pools tab, display the V-VOLs tab. 5. Click Create V-VOLs. The Create V-VOLs Wizard is launched. 6. On the 1. Setup V-VOL Group page, specify the parameters of the V-VOL Group (Parity Group). NOTE: Steps 7 and 8 only apply to XP24000/XP20000 storage systems.
17. Review all parameters of the V-VOLs and click Confirm. The 5. Finish page is displayed. TIP: The time taken to complete this operation depends on the count and size of the primary LDEVs, and the specified Count of Snapshot. For five 1 GB primary LDEVs, it takes approximately 20 minutes. For one 1 GB primary LDEV and 1024 snapshots, it takes approximately 40 minutes. This operation can take longer when a large number of primary LDEVs are selected. 18.
Related topics • • • • About the Add Command Devices Wizard, page 116 Setting up command devices, page 114 Editing command devices, page 310 Deleting command devices, page 311 Storage system types and volume requirements (command devices) Volumes that meet the requirements listed here are displayed as candidate volumes in Replication Manager.
About the Add Command Devices Wizard Replication Manager includes an Add Command Devices Wizard for registering volumes as command devices. The wizard provides the following functions: • Filters for narrowing down the volumes to be registered as command devices • List of candidate volumes that can be registered as command devices • List of newly configured command devices Launching the Add Command Devices Wizard To launch the Add Command Devices Wizard: 1.
Setting up remote paths If you use Continuous Access Asynchronous, Continuous Access Synchronous, or Continuous Access Journal to replicate volumes, you must set up a logical path (called a remote path) to link the MCU (or primary DKC) of the local storage system to the RCU (or secondary DKC) of the remote storage system. You can set up a remote path by starting the wizard that is available under the Remote Paths tab of the storage systems view.
Whether to specify a remote path depending on a combination of storage systems Remote storage system Local storage system XP512/ XP48 XP1024/ XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 HP P9500 XP512/XP48 N N -- -- -- XP1024/XP128 N N N N -- -- N* Y Y Y -- N* Y Y Y -- N* Y Y Y XP12000/ XP10000/ SVS200 XP24000/ XP20000 HP P9500 Legend: Y: A remote path can be specified. N: A remote path cannot be specified.
2. Expand the object tree, and then select a storage system under Storage Systems. The storage-system-name subwindow appears. 3. Click the Open link. The Open subwindow appears. 4. Under the Remote Paths tab, click Create Path. The Create Remote Path Wizard starts. 5. Follow the instructions provided by the wizard to create a remote path. The remote path you created is displayed in the Open subwindow.
• A license has been registered for the copy type being used (Snapshot). For a volume to be used as a pool volume, the volume must meet the applicable requirements for the storage system type. For information on volume requirements for storage system types, see “Storage system types and volume requirements (pools)” on page 120. For each pool, you can specify the threshold value for pool usage to determine when the status changes to the warning status.
Legend: Y: This requirement applies. N: This requirement does not apply. About the Create Pool Wizard Replication Manager includes a Create Pool Wizard for registering pool volumes.
5. Create a pool as instructed by the wizard. The added pool is displayed in the Open subwindow. Related topics • About pool volumes, page 119 • Storage system types and volume requirements (pools), page 120 • Pool usage threshold values, page 286 Setting up journal groups Continuous Access Journal uses journal volumes as volume copy buffers. You must set up journal groups before creating Continuous Access Journal volume pairs.
Storage system types and requirements for using volumes as journal volumes Requirement XP12000/ XP10000/ SVS200 XP24000/ XP20000 HP P9500 Maximum number of volumes per journal group 16 64 64 Emulation type OPEN-V OPEN-V OPEN-V Not a paired volume Y Y Y Path is not set Y Y Y Not a pool volume Y Y Y Not a journal volume Y Y Y Not a command device Y Y Y Not a LUSE volume Y Y Y Not a V-VOL Y Y Y Guard not specified Y Y Y Not an HIHSM reserved volume Y Y Y Not an O
Items permitted for journal options Journal Group on the Primary Side (Master) Item Initial Active Stop Other than Active or Stop Journal Group on the Secondary Side (Restore) Active Stop Other than Active or Stop Inflow Control Y N Y N N N N Data Overflow Watch Time Y N Y N N N N Path Watch Time Y N Y N N Y N Forward Path Watch Time Y N Y N N N N Use of Cache Y N Y N N Y N Speed of Line Y Y Y N Y Y N Delta Resync Failure Y N Y N N N N Legend:
Delta resync Failure* The items marked with an asterisk (*) are not displayed for HP P9500 storage systems. Related topics • Launching the Create Journal Group Wizard, page 125 Create journal group workflow The following figure illustrates the workflow for creating journal groups. Launching the Create Journal Group Wizard To launch the Create Journal Group Wizard: 1. In the Explorer menu, choose Resources and then Storage Systems. The Storage Systems information is displayed in the Navigation area. 2.
Adding journal groups To add a journal group: 1. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 2. Expand the object tree, and then select a storage system under Storage Systems. The storage-system-name subwindow appears. 3. Click the Open link. The Open subwindow appears. 4. On the JNLGs page, click Create JNLG. The Create Journal Group Wizard starts. 5. Create a journal group as instructed by the wizard.
9 Customizing monitoring parameters You can customize Replication Manager by configuring alert notification settings, refresh intervals, and data retention periods. You can set up alerts to monitor thresholds for copy pair status, performance metrics and copy license usage. You can also configure refresh intervals at which the latest storage system information is applied to the Replication Manager database and retention periods for data items such as received alerts, write delay time, and event logs.
Copy pair status An alert is sent when a copy pair or copy group achieves a specified status. For example, you can specify a condition for a copy group so that an alert is sent when an error status is detected. In this case, an alert is sent indicating the copy pairs of the group that are in error status. When all the constituent pairs attain Completed status, the copy group is given the Completed status.
Monitored condition Completion criteria Write latency time (C/T delta) The write latency time must be less than or equal to the time specified by the user for the alert to be completed. Copy pair status When the status of the copy pair transitions out of the state specified for the alert. Copy group status When all of the pairs contained in the copy group are marked Completed. (Even if the status of pairs in the copy group changes again, the copy group alert remains Completed.
You can configure the following monitoring types depending on the resource type of the monitored target: • Pair Status Monitoring: You can set alerts to monitor pair status when the resource type of the monitored target is a copy pair or copy group type. • Performance Monitoring: You can set alerts to monitor performance information when the resource type is a copy group, pool, or journal group type.
• About the Create Alert Setting Wizard, page 129 Setting the copy pair status monitoring conditions for each copy group To set the conditions for monitoring copy pair status on a copy group basis: 1. If you intend to use SNMP traps to send alerts, first load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About MIB definition files” on page 422. 2.
Setting the copy pair status monitoring conditions for each copy pair To set the conditions for monitoring copy pair status on a copy pair basis: 1. If you intend to use SNMP traps to send alerts, load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About MIB definition files” on page 422. 2.
Setting performance monitoring conditions for each copy group To set the performance monitoring conditions on a copy group basis: 1. If you intend to use SNMP traps to send alerts, load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About MIB definition files” on page 422. 2. Display the information about the copy groups where you want to set monitoring conditions.
Setting performance monitoring conditions for each journal group To set the performance monitoring conditions on a journal group basis: 1. If you intend to use SNMP traps to send alerts, load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About MIB definition files” on page 422. 2. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 3.
Setting performance monitoring conditions for each pool To set the performance monitoring conditions on a pool basis: 1. If you intend to use SNMP traps to send alerts, load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About MIB definition files” on page 422. 2. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 3.
Setting monitoring conditions for copy license usage To set monitoring conditions for copy license usage: 1. If you intend to use SNMP traps to send alerts, load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About alert management” on page 323. 2. From the Explorer menu, select Resources, and then Storage Systems. The Storage Systems subwindow appears. 3.
Adding monitored targets To add a monitored target: 1. Select the resources you want to add as monitoring targets, and then click Create Alerts. The Create Alert Setting Wizard starts with the 1. Introduction page displayed. 2. Read the wizard page, and then click Next. The 2. Select Monitoring Type page appears. 3. Select the monitoring type you want to use, and then click Next. The 3. Select Alert Setting page appears. 4.
For details on how to refresh copy pair status, see “Refreshing the copy pair status automatically for each information source” on page 262. Related topics • About refreshing copy pair status, page 257 Calculating the copy pair status refresh interval You should set refresh intervals values such that copy pair status refresh operations have minimal impact on management servers and pair management servers.
About data retention periods Data retention periods can be set for the following types of data items: • • • • • • Received alerts Write delay time (C/T delta) Event log data Sidefile and journal volume usage Pool volume usage (open systems) Tasks TIP: If the total number of data items (including alerts, C/T delta, event logs, sidefile, journal volume usage, and pool volume usage, but excluding tasks) exceeds 30,000,000, some of the old data might be deleted even if the retention period for the data has no
2. Click the icon of the type of data whose retention period you want to edit. The Edit Data Retention - data-type-name dialog box appears. 3. Edit and update the data retention period settings. The data retention period settings displayed in the Data Retention subwindow are refreshed.
10 Managing pair life cycle Replication Manager allows you to specify copy pair configuration definitions in open systems in which the storage system type is XP12000/XP10000/SVS200 or XP24000/XP20000 and in mainframe systems where the storage system type is XP12000/XP10000/SVS200 or XP24000/XP20000. Replication Manager also allows you to change the copy pair status in both open systems and mainframe systems.
Permissions Function Admin Modify View Viewing a list of tasks Y Y Y Editing tasks Y Y N Deleting tasks Y Y N Canceling tasks Y Y N Viewing a list of workflows Y Y Y Editing workflows Y Y N Deleting workflows Y Y N TIP: Based on the Modify permission, you can also assign user roles that have greater granularity and give you more control over the tasks that users can perform. See “About user roles” on page 84 for more information. Legend: Y: Can be used with this permission.
Legend: Y: Can be executed with this permission. About the pair management wizards Replication Manager provides two pair management wizards. The Pair Configuration Wizard is provided for the creation and editing of copy pair configuration definitions. The Change Pair Status Wizard allows you to change the copy pair status.
Pair configuration workflow The following figure illustrates the workflow for pair configuration. Launching the Pair Configuration Wizard You can launch the Pair Configuration Wizard from the following locations on the web interface: • Unpaired LUN List: The Unpaired LUN list does not include copy pairs. The wizard can be launched from this list to configure new volume pairs. • Paired LUN List: The Paired LUN list includes copy pairs.
NOTE: The term LUN (Logical Unit Number) only applies to open systems. For mainframe systems, the analogs are LDEV (Logical Device) and DEVN (Device Number). Method for launching the wizard Conditions when the wizard cannot be launched • The LU is a command device or a remote command device. • The LU has been reserved by another workflow. • The LU is a virtual volume.
Method for launching the wizard Conditions when the wizard cannot be launched • A copy group that belongs to the same cascade has been reserved by another workflow. • At least one of the selected volumes does not belong to the same copy group. • A copy group in the same cascade contains pairs of multiple copy types. • Replication Manager is not aware of the pair management server (on either the primary or secondary side) that manages copy groups belonging to the same cascade.
Defining copy pairs and pair groups This module discusses how copy pair configuration definitions are created and tasks for defining copy pairs and pair groups: • • • • • • • About copy pairs, page 147 About copy pair configuration definitions, page 149 About creating copy pair configuration definitions, page 150 Creating pairs and pair groups, page 154 Editing pair names, page 155 About filtering candidate volumes, page 156 Selecting multiple candidate volumes, page 157 About copy pairs A copy pair is a
• Secondary volume (S-VOL): The destination volume to which the contents of the primary volume are copied. • Secondary-primary volume (SP-VOL): The volume located in the middle of a cascade configuration. A secondary-primary volume is both the secondary volume in an upper-level copy pair and the primary volume in a lower-level copy pair.
About copy pair configuration definitions Copy pair configuration definitions are generated when a new copy group is created. Pre-existing copy pair configuration definitions can also be imported into Replication Manager. New copy pair configuration definitions are created and edited using the Pair Configuration Wizard.
About configuration definition file formats New configuration definition files (HORCM configuration files) can be generated in either HORCM_LDEV format or HORCM_DEV format. Replication Manager allows you to specify the format for new configuration definition files using the server.agent.rm.pairDefinitionForm and server.agent.rm.cuLdevForm properties in the Device Manager agent server.properties file.
on permitted copy types for copy pair configuration definitions for different storage system types, see “Storage system conditions for pair configuration definition” on page 152. TIP: Use the latest versions of the storage system's microprogram and P9000 RAID Manager.
Prerequisites for pair configuration (mainframe systems) The following items need to be verified before performing mainframe pair configuration operations: • Ensure that a disk configuration definition file for the volumes to be used as the P-VOL and S-VOL of the copy pair has been created using Replication Manager or from a volume scan by HP StorageWorks P9000 for Business Continuity Manager Software.
• Replication Manager must recognize the command device in the storage system. • Multiple volumes that belong to different storage systems must not be selected. Conditions for primary volumes that can be added (mainframe systems) The primary volumes that are displayed the Candidate List pane on the 2.
Copy type Candidate storage system Business Copy The storage system is the same as the primary storage system The storage system satisfies both the following conditions: Continuous Access Synchronous, Continuous Access Journal • • • • Volumes Volumes Volumes Volumes • The storage system must be different from the primary storage system. • The storage system must be either XP12000/XP10000/SVS200, XP24000/XP20000, or HP P9500. are stored using the same prefix, DADID, and host.
3. Click Apply. The filtered list of candidate volumes is displayed on the Result tab. 4. From the displayed tree structure on the Results tab, select the candidate volumes that you want to assign as the primary volume or secondary volumes for the new copy pairs. You can select multiple volumes on the Result tab. For details, see “Selecting multiple candidate volumes” on page 157. 5. Click Add or Add All.
To override the automatic pair names generated during pair configuration: 1. On the 3. Group Management page of the Pair Configuration Wizard, select the copy pair(s) to be renamed from the Pair List. You can select multiple copy pairs for renaming at the same time. 2. Click Edit Pair Name. The Edit Pair Name dialog box appears. 3. In the Pair Name Setting pane, specify the new pair name for the selected pair. 4. If you are renaming multiple copy pairs, select a suffix start number. 5.
Selecting multiple candidate volumes Replication Manager identifies a list of candidate secondary volumes using the filtering criteria specified on the Criteria tab under the Candidate List pane. These candidate volumes are grouped and displayed as nodes in a tree structure on the Results tab. By selecting the parent node of a group, you can select up to 100 candidate volumes in a single operation.
operation such as changing the copy pair status on a copy group, you can change the copy pair status of all copy pairs in the copy group in a single operation. Mainframe copy pairs can be grouped into two types of copy groups for maintaining data consistency during replication. Copy groups can be defined without a container, in which case data consistency is maintained per copy group. Copy groups can also be defined with a container, where each container consists of multiple copy groups.
• The CTG option is available only when the prerequisite product versions are later than appropriate version, so that Device Manager agent/P9000 RAID Manager can accept CTG option for local copy. • Pairs created with the At-Time Split option (-m grp) and pairs created without this option must not be mixed in the same group defined in the P9000 RAID Manager configuration file.
Replication Manager identifies available HORCM instance numbers and displays the smallest number of available instance as the default HORCM instance when creating a new copy group. Depending on availability of instances, the displayed instance number is updated automatically when you change the primary or secondary pair management server. The server.agent.rm.exclusion.instance parameter in the Device Manager agent server.
6. Click OK to create a new copy group. The created copy group is displayed in the Copy Group pane. 7. Click Next to continue creating the copy pair configuration definition or click Save to temporarily save the workflow. TIP: If you need to stop the wizard before the copy pair configuration definition is completed, the incomplete definition can be temporarily saved as a workflow, and then worked on again when the wizard is restarted.
5. Click Apply. The copy pairs belonging to the associated pair group are displayed in the Pair List pane. TIP: For mainframe pair configuration, copy pairs displayed in the Pair List are aggregated per CTGID/JNLGID. When there are multiple IDs assigned for the container, copy groups will be promoted to the container. 6. Click Next. The tasks that correspond to specific copy groups are displayed on the 4. Task Management page.
copy group or container cascaded with the initial copy group or container (cascade destination group). The following are supported combinations of copy groups and containers when defining cascade configurations: • If the target group is a local copy group, it can only be combined with a following group that is a remote copy group. • If the target group is a local copy group container, it can be combined with a following group that is a remote copy group container.
There are some requirements for copy types of the pair groups that can be added in multi-target or cascade configurations, to be compatible with the copy type of the original pair group. In this case, the copy type of the pair group to be connected by the Add Group operation must satisfy these requirements to be compatible with the copy type of the original pair group. For details on copy type requirements, see “Copy type requirements for pair configuration definitions” on page 164.
Copy type of the pair group to be connected by group addition Copy type of the original pair group Business Copy Snapshot Continuous Access Synchronous Continuous Access Asynchronous Continuous Access Journal Continuous Access Synchronous Y Y N N Y Continuous Access Asynchronous Y Y N N N Continuous Access Journal Y Y N N N Legend: Y: This type of pair group can be connected. N: This type of pair group cannot be connected.
Unsupported configuration Requirement for configuration Alternative configuration to implement requirement None None Pairs in the copy group use the same S-VOL. There are different types of copy pairs in the same copy group. The storage systems for the primary volumes in the same copy group are different. The storage systems for the secondary volumes in the same copy group are different. The cascade configuration consists of a container and a copy group.
Limitations when performing 3DC configuration pair operations (mainframe systems) The following limitations and resolutions are to be noted when performing 3DC configuration pair operations: • When operating Delta Resync, it is necessary to switch the direction of Continuous Access Synchronous in advance. Because Replication Manager does not switch the direction automatically, it is necessary to switch the direction manually. • The Force option cannot be added when executing Delta Resync.
Scheduling and managing tasks This module discusses information about tasks and procedures for scheduling and managing tasks: • • • • • • • • About tasks, page 168 About task statuses, page 169 About task types (open systems), page 169 About task types (mainframe systems), page 170 Scheduling tasks, page 171 Viewing a list of tasks, page 173 Canceling tasks, page 173 Deleting tasks, page 173 About tasks A task is a type of operation, such as changing the status of a copy pair or creating a copy pair or co
TIP: For situations such as when storage system resources and host applications are managed by different administrators, the work status at any point during copy pair creation by a wizard can be saved as a workflow and passed from one administrator to the next. In this case, a new task is generated when the wizard finishes and the saved workflow is overwritten. Because associated tasks have an execution order, a task that must be executed prior to another task is known as a prerequisite task.
• create: Creates a copy pair. This operation does not edit the configuration definition file. • split: Splits a copy pair. This operation does not edit the configuration definition file. • resync: Re-synchronizes data from the primary volume to the secondary volume. This operation does not edit the configuration definition file. • restore: Re-synchronizes data from the secondary volume to the primary volume. This operation does not edit the configuration definition file. • delete: Dissolves a copy pair.
Scheduling tasks You can edit the execution schedule or copy pair settings for tasks registered either during pair configuration or at the completion of Pair Configuration Wizard processing. The Execution Request Time options can be configured to determine if the task should be executed immediately or at a scheduled date and time. For open systems, you can also specify the settings to only modify the P9000 RAID Manager definition (HORCM configuration file) without creating pairs.
Cancel status. You cannot edit tasks that have other status conditions or that were registered at the completion of Change Pair Status Wizard processing. NOTE: When invoked for multiple tasks (Pair Configuration Wizard - open systems only), the behavior of drop-down lists, check boxes, and radio buttons varies depending on what (if any) values the tasks have in common. When the tasks have values that differ: • Drop-down lists start with an empty value, followed by common values that can be selected.
Viewing a list of tasks The Task List displays the tasks related to operations performed on copy pairs that are registered when the Pair Configuration Wizard or the Change Pair Status Wizard completes an operation, or when a copy pair associated with a remote path is deleted. The maximum number of tasks is 1,000. In this list, you can check information such as the task type (type of copy pair operation), execution status, and owner.
To delete tasks: 1. From the Explorer menu, choose Tasks and then Tasks. The Tasks subwindow appears. 2. Select the check boxes of the tasks you want to delete, and then click Delete Tasks. The Delete Tasks dialog box appears. 3. Confirm the tasks that will be deleted, and then delete them. The tasks are deleted from the Tasks subwindow.
Example of copy group definition distribution scenario Prerequisites for distribution destination hosts (copy group definitions) HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent hosts must satisfy the following conditions to be copy group distribution destination candidates: • A copy group definition file with the same copy group name must exist on the distribution destination BCM or P9000 mainframe agent host.
Conditions that disrupt copy group distribution relationships Copy group linkage is disrupted if either of the following conditions occur: • The distribution relationship of the primary side DADID and secondary side DADID used by the copy group is deleted • The primary host of the copy group is deleted from the information source If either of the conditions occur, the relevant copy group cannot be a distribution target.
Related topics • About distributing copy group definitions, page 174 Creating and managing workflows This module describes tasks for creating and managing workflows: • • • • • About workflows, page 177 Saving workflows, page 177 Viewing a list of workflows, page 178 Editing workflows, page 178 Deleting workflows, page 179 About workflows A workflow is a series of tasks associated with the creation of a copy pair or copy group.
TIP: A user with the Modify permission can inherit a workflow from another user only when the workflow has been saved on the 3. Group Management or 4. Task Management wizard page. A workflow saved on the 2. Pair Association wizard page can be edited only by the user who saved the workflow.
2. Select the check box of a workflow you want to edit, and then click Edit Workflow. TIP: A workflow that was saved in a step prior to the Pair Configuration Wizard (3. Group Management) page cannot be edited or deleted. Therefore, if you click either of these buttons, an error message (RPM-00451) appears. A workflow that was saved in the Pair Configuration Wizard (3. Group Management) page or later can be edited or deleted.
Managing copy pair configuration definitions This module describes tasks for managing copy pair configuration definitions: • • • • • • • • • • About editing copy pair configuration definitions, page 180 Adding copy pairs (completed workflow), page 181 Editing copy groups by associating new pair groups, page 182 Editing copy groups by associating new copy pairs, page 185 Editing copy groups by setting copy type, page 186 Editing copy group settings, page 187 Deleting copy groups, page 190 Deleting copy pair
CAUTION: Observe the following precautions: • While a copy pair configuration definition is being edited, do not use storage system operation management software to perform operations on a volume, copy group, or copy pair specified in that definition. Doing so might cause errors when Replication Manager executes tasks. • If you have specified the instance number in the server.agent.rm.exclusion.instance property of the server.
as when the associated task is in execution ready status or has failed). You can edit the completed workflow created upon completion of the Pair Configuration Wizard. To add copy pairs to a completed workflow: 1. In the Explorer menu, choose Tasks and then Tasks. A list of tasks is displayed in the Tasks subwindow. 2. Select the task associated with the pair configuration you want to edit. 3. Click Cancel Tasks. 4. Confirm the cancel operation in the confirmation dialog and cancel the task.
5. Define a list of copy pairs that you want to include in the pair group, by selecting the primary and secondary volumes in the Candidate List pane. For details on how to define copy pairs, see “Creating pairs and pair groups” on page 154. The defined copy pairs are displayed in the Pair List pane. 6. Repeat steps 4 and 5 to create additional pair groups. You can click the areas. 7. icon or the icon to expand the Candidate List and Pair List display Click Next. The 3. Group Management page appears.
When you add a new copy group to existing copy groups, copy types to be displayed differ depending on the copy types of the volumes selected in Copy Topology. The following tables show the correspondence between the copy type of the selected volume and the copy types to be displayed.
Copy type of the pair group to be connected by group addition Business Copy Continuous Access Synchronous Continuous Access Asynchronous Continuous Access Journal Copy type of selected volume Continuous Access Synchronous Primary Y N N Y Secondary Y N N Y Continuous Access Asynchronous* Primary Y N N N Secondary Y N N N Primary Y Y N N Secondary Y Y N N Continuous Access Journal Legend: Y: Displayed. N: Not Displayed. *: Not supported on HP StorageWorks P9500.
6. Click Next. The 3. Group Management page appears. The created pairs are displayed on the 3. Group Management page. 7. Click Next. A new task that correspond to the copy group is displayed on the 4. Task Management page. The Pair Operations field for the associated task displays the status "modify file + create". 8. Click Next. The 5. Confirm page appears. 9. Confirm the configuration definition and tasks for the copy pairs you have specified, and then click Confirm. The 6. Finish page appears.
6. Select a copy type from the Copy Type drop down list. CAUTION: Pair configuration can fail if the specified copy type is different from the one configured when pair configuration file was created. 7. Click OK. The copy type assigned to the copy group is displayed in the Copy Topology pane. TIP: The copy type of the edited copy group cannot be edited after a copy type is assigned.
5.
Copy type Option name Displayed items Default value Integer values from 0 to 3 Mirror ID Continuous Access Journal Continuous Access Synchronous Continuous Access Asynchronous Note: If you want to concurrently use Continuous Access Journal and Continuous Access Synchronous copy groups in a 3DC Cascade or 3DC Multi-target configuration, you cannot specify a value of 0 for Mirror ID.
The EXCTG options are available on the Edit Group window, when multiple CTGIDs exist on the Continuous Access Journal copy group. These options enable consistency to be maintained among multiple CTGIDs. The following table lists the EXCTG options available: Option name Displayed item Description Enable EXCTG among multiple CTGIDs Check box EXCTG ID No value or 0 to 3 Secondary Storage Systems All secondary storage systems that belong to the container are displayed.
3. Read the wizard page, and then click Next. The 2. Pair Association page appears. The copy topology (configuration of the related copy groups) to which the copy group belongs is displayed under Copy Topology. 4. To delete a copy group, click the Delete Group button under Copy Topology. The dialog box for confirming deletion appears. 5. Click Next. The 3. Group Management page appears. The deleted pairs are displayed under Pair List. 6. Click Next. In the Task List on the 4.
2. In the displayed subwindow, select a copy group. Alternatively, make sure that copy group information is displayed, and then click Pair Management. The Pair Configuration Wizard starts with the 1. Introduction page displayed. 3. Read the wizard page, and then click Next. The 2. Pair Association page appears. The copy topology (configuration of the related copy groups) to which the copy group belongs is displayed under Copy Topology. 4.
2. Perform a storage system refresh to load configuration definition files into Device Manager and Replication Manager. Refresh all the storage systems associated with both P-VOL and S-VOL. Refreshing of storage systems can be performed in the following ways: • Manually refreshing storage systems in Replication Manager. For details, see “Refreshing configuration information manually for each storage system” on page 269.
Performing pair operations This module describes supported pair operations and procedures for changing copy pair status: • • • • About copy pair operations, page 194 About copy pair states, page 212 About changing copy pair status, page 217 Confirming copy status during task execution, page 232 About copy pair operations You may need to perform operations that change the copy pair status (such as splitting and re-synchronizing copy pairs), when errors occur in managed resources or when you backup data.
Copy type Copy pair operation Continuous Access Synchronous Continuous Access Asynchronous or Continuous Access Journal Business Copy Snapshot JNLG ID(S) N Y1 N N No Copy Y Y N N Pool ID N N N Y Quick Split N N Y N Read disable (secondary) N N Y Y Split N N Y N2 N Y Y Option Assign CTG for AtTime Split N Assign CTG Y N N N CTGID Y Y Y Y Copy Pace N N Y Y Force Suspend Y Y N N Quick Split N N Y N Secondary Mode Y Y N N Copy Pace Y Y Y
Copy pair operation options that can be set for each copy type Copy Type Copy Pair Operation Option Values split Quick Split Force Cnt Ac-S On, Off(*) On, Off(*) -- Y Cnt Ac-A -- Y Cnt Ac-J -- Y Description BC Y Y If the value is On, the status will be changed to Split immediately. If the value is Off, the status will be changed to Split after all the updated data in the P-VOLs are copied.
Copy Type Copy Pair Operation Option Values Quick Restore restore delete Cnt Ac-S On, Off (*) -- Cnt Ac-A -- Cnt Ac-J -- Description BC Y Force On, Off (*) Y Y Y Y Overwrite ONLINE target volume On, Off (*) Y Y Y Y Force On (*), Off Y Y Y -- If the value is On, the status will be changed to Pair immediately. If the value is Off, the status will be changed to Pair after all the updated data in the S-VOLs is copied to the P-VOLs.
Operation target is copy group Operation target is copy pair or C/T Group Direction Synchronization Direction Synchronization Continuous Access Asynchronous Blank(*), Forward, Reverse Blank, Flush(*), Purge Blank (not activated)(*) Flush(*), Purge Continuous Access Journal Blank(*), Forward, Reverse Blank, Flush(*), Purge Blank (not activated)(*) Flush(*) Copy type Legend: *: Default value -: Option is not displayed #: If there are different directions in the selected pair, Replication Mana
Details of copy pair operation options (mainframe systems) Copy type: Cnt Ac-S Pair command Options Item specified Specifiable values Default value Remarks Forward: The SUSPOP status is set so that the copy direction after re-synchronization is from the primary site to the secondary site. Direction The copy direction of the pair when re-synchronization is performed. Forward, Reverse Forward Note: This option cannot be specified if the operation target is a copy pair or a C/T Group.
Pair command Options Item specified Specifiable values Default value Remarks on: A copy pair is created even when the S-VOL (or P-VOL when Reverse is specified) is online. Overwrite ONLINE target volume Whether to create a copy pair when the copy destination volume is online. on, off off off: A copy pair is not created if the S-VOL (or P-VOL when Reverse is specified) is online.
Copy type: Cnt Ac-A/Cnt Ac-J Pair command Options Item specified Specifiable values Default value Remarks Forward: The SUSPOP status is set so that the copy direction after re-synchronization is from the primary site to the secondary site. Direction The copy direction of the pair when re-synchronization is performed. Reverse: The SUSPOP status is set so that the copy direction after re-synchronization is from the secondary site to the primary site.
Pair command Options Item specified The operation is performed on a volume basis. The command is executed for all pairs regardless of their status. Specifiable values Default value Remarks SELECT(ALL),VOLUNIT is specified in the BCM command. The command is also executed for pairs whose status is not available for the command. The command is executed on a pair basis even though execution by group is possible.
Pair command restore Options Item specified Force The operation is performed on a volume basis. The command is executed for all pairs regardless of their status. Specifiable values on, off Default value Remarks SELECT(ALL),VOLUNIT is specified in the BCM command. The command is also executed for pairs whose status is not available for the command. The command is executed on a pair basis even though execution by group is possible.
Pair command Options Item specified Specifiable values Default value Remarks Secondary Mode Whether to permit writing to the S-VOL after the split operation. Read Only, Read Write Read Only The values Read Only and Read Write are displayed in this order. Quick Resync Whether to immediately perform re-synchronization. force The operation is performed on a volume basis. The command is executed for all pairs regardless of their status.
Pair command Options Item specified Specifiable values Default value Remarks on: A copy pair is created even when the S-VOL (or P-VOL when Reverse is specified) is online. Overwrite ONLINE target volume delete (No Option) Whether to create a copy pair when the copy destination volume is online. on, off - - off off: A copy pair is not created if the S-VOL (or P-VOL when Reverse is specified) is online.
The copy pair status can be displayed at various levels: for example, for an individual copy group, or for the type of volume replication functionality (the copy type). The status of the copy pair within that grouping that has the most serious (highest priority) status is referred to as the summary pair status. The priority of copy pair statuses, starting from the most serious, is as follows: 1. 2. 3. 4. 5. 6.
Conditions for determining copy pair status 1/3 (for Continuous Access Asynchronous, Continuous Access Synchronous and Continuous Access Journal) Copy pair state of the primary volume Copy pair state of the secondary volume Invalid Error (PSUE or HLDE) Error (SUSPER) Error (SUSPCU) Error (HOLDER) Error (PDUB) Split (PFUS) Split (SWAPPING) Invalid error error error error error error error suspend Error (PSUE or HLDE) error error error -- -- error error -- Error (SUSPER) error err
Conditions for determining copy pair status 2/3 (for Continuous Access Asynchronous, Continuous Access Synchronous and Continuous Access Journal) Copy pair state of the secondary volume Copy pair state of the primary volume Split (NODELTA) Split (SUSPOP) Split (HOLD) Split (PSUS or HOLD) Split (CHKJNL) Split (HOLDTRNS) Split (PSUS or HOLD) Invalid error suspend suspend suspend copying copying copying Error (PSUE or HLDE) -- -- -- error -- -- error Error (SUSPER) error error error
Copy pair state of the secondary volume Copy pair state of the primary volume Split (NODELTA) Split (SUSPOP) Split (HOLD) Split (PSUS or HOLD) Split (CHKJNL) Split (HOLDTRNS) Split (PSUS or HOLD) Simplex (SMPL) or Simplex (SIMPLEX) error suspend error suspend error error copying Unknown error suspend suspend suspend copying copying copying Legend: --: Not applicable Conditions for determining copy pair status 3/3 (for Continuous Access Asynchronous, Continuous Access Synchronous and
Copy pair state of the primary volume Copy pair state of the secondary volume Deleting (COPY or PAIR) Suspending (COPY or PAIR) Copying (COPY) or Copying (Pending or Resync) Deleting (COPY or PAIR) copying copying Suspending (COPY or PAIR) copying Copying (COPY) or Copying (Pending or Resync) Pair (PFUL) Pair (PAIR or PFUL) Pair (PAIR or PFUL) or Pair (DUPLEX) Simplex (SMPL) or Simplex (SIMPLEX) Unknown copying copying copying copying copying copying copying copying copying copying
Copy pair state of the primary volume Copy pair state of the secondary volume Invalid Error (PSUE or HLDE) Error (SUSPER) Split (SUSPVS) Split (SUSPOP) Split (PSUS or HOLD) Suspending or Deleting (TRANS) Error (PSUE or HLDE) error error error suspend -- suspend copying Error (SUSPER) error error error suspend suspend suspend copying Split (SUSPVS) suspend error error suspend suspend suspend copying Split (SUSPOP) suspend -- error suspend suspend -- copying Split (PSUS
Copy pair state of the primary volume Deleting (COPY or PAIR) Copying (COPY) or Copying (Pending or Resync) Copying (RCPY) or Copying (Resync-R) Pair (PAIR or PFUL) Pair (PAIR or PFUL) or Pair (DUPLEX) Simplex (SMPL) or Simplex (SIMPLEX) Unknown Split (SUSPVS) copying copying copying sync sync error suspend Split (SUSPOP) -- copying copying sync sync error suspend Split (PSUS or HOLD) copying copying copying sync sync error suspend Suspending or Deleting (TRANS) copying copy
for Business Continuity Manager Software), Device Manager, and by storage system operation management software (such as Remote Web Console). The following tables show the correspondence between the copy pair states in Replication Manager and the copy pair statuses of various products, classified by open systems and mainframe systems.
Copy pair state Copy pair status in Device Manager Copy pair status in P9000 RAID Manager Copy pair status in Remote Web Console BC/Snapshot/Cnt Ac-S/Cnt Ac-A/Cnt Ac-J PAIR PAIR Pair (PFUL)8 Copy type PFUL Cnt Ac-A Simplex (SMPL) Simplex SMPL SMPL BC/Snapshot/Cnt Ac-S/Cnt Ac-A/Cnt Ac-J Unknown Unknown -- -- -- Legend: --: Not applicable BC: Business Copy Cnt Ac-S: Continuous Access Synchronous Cnt Ac-A: Continuous Access Asynchronous Cnt Ac-J: Continuous Access Journal 1.
Copy pair state Copy pair status in HP StorageWorks P9000 for Business Continuity Manager Software Copy pair status in Remote Web Console Copy type Suspend BC/Cnt Ac-J Error (HOLDER) HOLDER Hlde Cnt Ac-J Split (SWAPPING) SWAPPING Suspended Cnt Ac-S/Cnt Ac-A/Cnt Ac-J Suspended Cnt Ac-S/Cnt Ac-A/Cnt Ac-J Split BC Split (SUSPOP) SUSPOP Split (SUSPOP) Split (SUSPVS) SUSPVS V-Split BC Split (NODELTA) NODELTA Hold Cnt Ac-J Split (HOLD) HOLD Hold Cnt Ac-J Split (CHKJNL) CHKJNL Hold
TIP: As of Replication Manager version 6.3, mainframe pair status information can be obtained using Device Manager (without HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent installed). Detailed pair state information for mainframe pairs in Device Manager is equivalent to the information for open systems pairs shown in Table 9.
About changing copy pair status Replication Manager allows you to change the copy pair status in open and mainframe systems. Pair status change operations may be necessary to resume copy operations after recovery from an error or unexpected pair status changes. For open systems, you can perform the split, resync, restore, create and delete operations when the storage system type is XP12000/XP10000/SVS200 or XP24000/XP20000.
Pair status conditions where the pair status can be changed (1/2) (when the target is a copy group) Copy pair state Error (PSUE) Error (HOLDER) Error in LUSE* Split (Full) Split (SW) Split (HOLD)* Split Business Copy Continuous Access Synchronous Continuous Access Asynchronous split split split resync resync resync restore restore restore delete delete delete -- -- -- split split resync resync restore restore delete delete split split split resync resync resync restor
Copy pair state Continuous Access Synchronous Continuous Access Asynchronous -- -- split split split resync resync resync restore restore restore delete delete delete split split split resync resync resync restore restore restore delete delete delete split split split resync resync resync restore restore restore delete delete delete -- -- -- split split split resync resync resync restore restore restore delete delete delete Business Copy split Copying
TIP: Notes about pair status transitions: • If a selected copy group includes a copy pair whose copy pair state is Error (PSUE) or Error in LUSE, the state of all copy pairs is assumed to be Error (PSUE). • If a selected copy group includes copy pairs whose copy pair states differ, all copy pair statuses to which each copy pair can be changed are displayed as candidates.
Snapshot Copy pair state Deleting Suspending Copying Copying (Reverse) Pair (Full) Pair (PAIR or PFUL) Pair Simplex Unknown The same primary volume is shared1 The same primary volume is not shared2 Continuous Access Journal split split split resync resync resync restore restore restore delete delete delete split split split resync resync resync restore restore restore delete delete delete split split split resync resync resync restore restore restore delete del
1. 2. 3. This column lists the selectable copy pair statuses when the copy group contains copy pairs that have the same primary volume. This column lists the selectable copy pair statuses when the copy group does not contain copy pairs that have the same primary volume. This is the copy pair state when a 3DC multi-target configuration is used.
Snapshot Copy pair state Split (SW) Split (HOLD)3 Split Deleting Suspending Copying Business Copy Continuous Access Synchronous Continuous Access Asynchronous split split resync resync restore The Same Primary Volume Is Shared1 The Same Primary Volume Is Not Shared2 Continuous Access Journal split split split split resync resync resync resync restore restore restore restore restore delete delete delete delete delete delete -- -- -- -- -- -- split split split spl
Snapshot Copy pair state Pair Simplex Unknown Business Copy Continuous Access Synchronous Continuous Access Asynchronous split split resync resync restore The Same Primary Volume Is Shared1 The Same Primary Volume Is Not Shared2 Continuous Access Journal split split split split resync resync resync resync restore restore restore restore restore delete delete delete delete delete delete -- -- -- -- -- -- split split split split split split resync resync resync
Details of copy group or copy pair statuses Business Copy Continuous Access Synchronous Continuous Access Asynchronous Continuous Access Journal Invalid - - - - Simplex (SIMPLEX) - - - - Unknown - - - - Split Split Split Split Delete Delete Delete Delete Split Split Split Split Delete Delete Delete Delete Resync/Restore Resync/Restore Resync/Restore Resync/Restore Delete Delete Delete Delete Resync/Restore Resync/Restore Resync/Restore Resync/Restore Delete D
TIP: The operation that can be selected is determined based on the copy directions of the definition and entity and on the pair status. The Resync option or the Restore option is displayed for pair operations depending on whether the FORWARD or REVERSE option is specified when the SUSPEND status is set. For Business Copy copy type, this check is not performed and you can select both the Resync and Restore options.
TIP: Note the following: • When the wizard finishes processing, a task is automatically registered for each copy group. You cannot edit these tasks because the copy pair status is changed immediately. However if the processing takes time, you can check the task execution result later. • You can register a maximum of 100 workflows and a total of 1,000 tasks, including the tasks for creating and editing copy pair configuration definitions and changing the copy pair status.
To launch the Change Pair Status Wizard using the Change Pair Status button: 1. Display the information about the group or container containing the copy pairs whose status you want to change. 2. Select the check boxes of the target copy pairs whose status you want to change, and then click Change Pair Status. Related topics • About Change Pair Status Wizard, page 226 Changing the copy pair status for each copy pair To change the status of a single copy pair: 1.
6. Set the operation (Pair Operation) and options to change the pair status and click Next. The Confirm page appears. CAUTION: Please check the following before confirming the pair status change operation: • Before a Split operation is performed, ensure that I/O processing for the primary volume is not being performed because this operation might result in incomplete data in the secondary volume.
2. Click the icon of the copy group or container that contains the copy pairs whose pair status you want to change. The Change Pair Status Wizard starts. 3. Read the wizard page and click Next. The 2. Select Copy Pairs page appears. 4. For open systems, select the check boxes of the copy pairs whose status you want to change in the Pair List pane, and then click Next. The 3. Select Pair Operation page appears. 5. For mainframe systems, perform the following operations on the 2.
Changing the copy pair status for multiple copy pairs (batch operation) To change the status of multiple copy pairs: 1. Display the information about the group containing the copy pairs whose status you want to change. For more information, see “Viewing information about copy groups belonging to a host” on page 299 or “Viewing information about copy groups belonging to a copy pair configuration definition” on page 298. 2.
6. Set the operation (Pair Operation) and options to change the pair status, and then click Next. The Confirm page appears. CAUTION: Please confirm the following before confirming the pair status change operation: • Before a split operation is performed, ensure that I/O processing for the primary volume is not being performed because this operation might result in incomplete data in the secondary volume.
6. On the Tasks window, verify task has completed by checking if the task status is Success. Related topics • About copy pair status, page 205 Advanced pair operations and recovery scenarios In addition to the basic pair operations (such as split and resync), the Change Pair Status Wizard supports several advanced operations for open system pairs.
CAUTION: Take note of the following points: • Advanced operations can be performed per copy group or per copy pair. • Because the copy pair status cannot be retrieved in the event of a failure, it is not confirmed prior to executing an operation. (Under normal circumstances, copy pair status confirmation is required and is performed by the Device Manager agent.) In this instance, an error message is created based on the information sent from the agent and is output for the Change Copy Pair Status task.
Swap operation This operation is used to switch work from the primary site to the secondary site. When you execute this operation, the primary volume and secondary volume for the copy pair are switched. The swap procedure is as follows: 1. Using the Change Pair Status Wizard, create a swap Change Copy Pair Status task for the target copy group or copy pair. 2. Check the Task List window to confirm that the status of the task is Success. 3. Check the copy pair status in the Pair Configurations view. 4.
takeover-recovery operation depend on the options specified, so you must check the copy pair status and select the options accordingly. The table below lists the options for the takeover-recovery operation and the status of the target copy pairs. Table 12 Operations and target copy pair states for takeover-recovery Operation Description Target copy pair state P-VOL S-VOL takeover-recovery (resync) Switches and synchronizes the primary and secondary volumes.
Scenario Procedure using the Change Pair Status Wizard Workflow reference Ending maintenance on the primary site work server To switch an application to the primary site, execute an advanced swap operation. The secondary site volume becomes the secondary volume and the primary site volume becomes the primary volume. Takeback: 3 Performing maintenance on the primary site storage To switch an application to the secondary site, execute an advanced swap operation.
Scenario Procedure using the Change Pair Status Wizard Workflow reference Primary site damage (loss of primary site data) To switch the application to the secondary site, execute an advanced takeover operation. The status of the secondary volume on the secondary site is changed to Split (SSWS). Takeover: 1 Recovery from primary site damage Reconstruct the copy pair from the secondary volume by executing a takeover-recovery (recreate) operation.
Figure 6 Takeover workflow Figure 7 Takeback workflow User Guide 239
NOTE: The takeback flowchart assumes that a configuration definition file exists. If no pair configuration definition file exists for the copy pair, or if a configuration file exists but is unavailable, you must use the Pair Configuration Wizard to recreate a pair configuration definition file. (The configuration definition file might not exist if it has been lost or the LDEV number has been changed.
Figure 8 Alert settings and volume reversal Alerts set for copy group CG1 are not valid for the copy group CG1 with reversed primary and secondary volumes. If you reverse the primary and secondary volumes for copy group CG1, the alerts set for copy group CG1 become valid once again. NOTE: When primary and secondary volumes are reversed, the copy group name is the same both before and after the reversal.
Change Pair Status Wizard P9000 RAID Manager Operation Command Option Option Read disable (secondary) -m noread Assign CTG for At-Time Split1 -m grp Assign CTG2 -fg fencelevel 3DC -nocsus Copy pace -c size Secondary Mode split -rw pairsplit Force Suspend -P Quick Split -fq quick Copy pace resync -c size pairresync Quick Resync -fq quick For local copy: Copy pace1 -c size For local pairs only: Quick Restore1 restore -fq quick pairresync -restore n/a delete Force Delete pair
Change Pair Status Wizard P9000 RAID Manager Description Operation takeover force-split Option Command None Performs S-VOL takeover. Timeout for data transfer Specifies a timeout value for an S-VOL takeover. horctakeover -S None Performs P-VOL takeover. horctakeover -l n/a Execute these commands in the following order: n/a None swap Copy Pace takeover-recovery (resync) Option None Copy Pace Redirects copying, retaining the current copy pair state.
This module includes the following topics: • • • • • About virtual command devices, page 244 Prerequisites for virtual command device configurations, page 246 Setting up an SVP as a virtual command device , page 247 Using a Virtual Command Device server, page 248 Performing user authentication for replica operations, page 249 About virtual command devices Command devices are used to send P9000 RAID Manager commands between the pair management server and a storage system.
Figure 9 Configuration using SVP as virtual command device NOTE: If the SVP is used as the virtual command device, there is no need to set up a Virtual Command Device server or command device. However, command processing using the SVP takes significantly longer, so we recommend using a Virtual Command Device server for large-scale configurations. The following figure shows a Virtual Command Device server configuration.
Figure 10 Configuration with Virtual Command Device server Prerequisites for virtual command device configurations The following requirements apply to virtual command device configurations.
Target Prerequisite Storage system The serial numbers of the storage systems managed by the Device Manager server must be unique. P9000 RAID Manager 01-25-xx/xx or later must be installed (Device Manager agent is not necessary), and the relay (P9000 RAID Manager) instance must have been started.
2. Specify the IP address of the SVP in the HORCM_CMD section of the HORCM configuration file. 3. Add copy groups to the HORCM configuration file. 4. Execute the raidcom -login command on the server managing the HORCM configuration file. 5. Perform a storage refresh from Device Manager. 6. Follow the procedure for “Refreshing configuration information manually for each information source” on page 269. The new copy groups are displayed in the Copy Groups table of the Hosts view.
7. Follow the procedure for “Refreshing configuration information manually for each information source” on page 269. The new copy groups are displayed in the Copy Groups table of the Hosts view. Once these steps are complete, you can perform pair operations using the new resources. Performing user authentication for replica operations When performing replica operations using command devices and P9000 RAID Manager authentication is enabled, you must execute the OS commands described in this procedure: 1.
4. Confirm that user authentication was successful. Make sure the P9000 RAID Manager authentication files were created using the same account names (with which authentication was performed) as the user names contained in the file names that execute the commands. Example authentication file of local system account: C:\HORCM\usr\var\host01_SYSTEM_53038 Example authentication file of user account for executing Application Agent service: C:\HORCM\usr\var\host01_Administrator_53038 5.
• Set the value of the hdvmagtif.PollingInterval property of the agentif.properties file to 60 or higher. After changing these properties, restart the services of the P9000 Command View AE Common Component. Monitoring and management of copy groups defined by device group Copy groups defined by device group enable you to manage the LDEVs in a storage system as a single entity, allowing operations to be performed in batch mode. NOTE: As of release 7.1.
NOTE: Although copy groups defined by device group can be managed through virtual command devices, use of a Virtual Command Device server is not supported. Prerequisites for copy group configurations defined by device group The following requirements apply to copy groups defined by device group. Target Prerequisites • The management server has been discovered as a pair management server in Replication Manager on the pair management server.
To recover from this condition, go to the database server (file server) and repeat the following steps for all of the pair volumes that are targets of Application Agent processing: 1.
2. 3. 4. Select the process of Application Agent (the process with the name starting with “drm”) in the Image Name column of the Processes tab. Click End Process. Open the trace log file of Application Agent and confirm the P9000 RAID Manager process name output to the last record of the log. The path of the file is: Installation-destination-of-Application Agent\DRM\log\drm_pp_traceX.log 5. 6. Select the process of P9000 RAID Manager in the Image Name column of the Processes tab. Click End Process.
11 Refreshing management information Replication Manager management information (configuration information and copy pair status information) can be manually refreshed at any time or automatically refreshed at preset refresh intervals. This chapter describes ways to refresh configuration information and copy pair status information. About refreshing management information To maintain Web client operability, Replication Manager has its own database for storing information about managed resources.
TIP: When refreshing copy pair statuses, the sidefile usage on a copy group and journal volume usage basis are included as target buffer usages of the refresh operation.
Explorer menu items for refreshing management information The following table shows the Explorer menu items that are related to refreshing management information, user permissions (Replication Manager management), and whether the items can be executed with the indicated permissions.
TIP: If copy pairs have been defined using storage system operation management software such as Remote Web Console, there is no configuration definition file (because there are copy pairs that are not managed by pair management servers). In this case, you should execute the Device Manager refresh function from Replication Manager. This will allow the pair information to be acquired from the refreshed databases.
Refreshing copy pair statuses data flow (open systems) The following figure shows the flow of data when copy pair statuses are refreshed in open systems. Refreshing copy pair statuses data flow (mainframe systems) The following figure shows the flow of data when copy pairs are refreshed in mainframe systems.
Disabling the Device Manager refresh function In open systems where all copy pairs are managed by pair management servers, you should prevent the Device Manager refresh function from executing during a manual refresh. If this function is used to refresh copy pair statuses, processing time increases. TIP: If copy pairs have been defined using storage system operation management software such as Remote Web Console, no configuration definition file exists.
4. Select the Do not execute a Device Manager refresh operation during a manual refresh operation check box, and then apply the new settings. The settings specified in the Monitoring Setting subwindow are updated. Thereafter, a manual refresh acquires information from the Device Manager agent on each pair management server (not from the database of the instance of Device Manager on the management server).
Refreshing copy pair statuses manually for each copy group To refresh copy pair statuses manually on a copy group basis: 1. Display the information about the copy group for which you want to refresh copy pair statuses. For details, see “Viewing information about copy groups belonging to a host” on page 299 or “Viewing information about copy groups belonging to a copy pair configuration definition” on page 298. 2. Click Refresh Copy Group or Refresh Copy Groups to start a refresh operation.
Continuity Manager Software or P9000 mainframe agent that is an information source. You can also disable periodic refreshing. To refresh the copy pair status automatically for each information source: 1. From the Explorer menu, choose Settings and then Refresh Setting. The Refresh Setting subwindow appears. 2. Click the Monitoring Setting link. The Monitoring Setting subwindow appears. 3. Click the icon of the information source from which you want the copy pair status to be acquired automatically.
2. Click the Monitoring Setting link. The Monitoring Setting subwindow appears. 3. Click the link that has the name of the Device Manager server that is an information source to which the pair management server belongs. The Device-Manager-server-name subwindow appears. 4. Click the icon of the pair management server from which you want the copy pair statuses to be acquired automatically. The Edit Interval of Refresh Pair Status - pair-management-server-name dialog box appears. 5.
TIP: The configuration might be updated often if both settings are enabled. Therefore HP recommends that if you want to enable the periodic update setting, you disable the automatic update setting. When automatic refreshing of configuration information is enabled, Replication Manager regularly checks whether Device Manager servers registered as information sources have refreshed their storage systems configurations.
TIP: If you refresh configuration information on a storage system basis, or if you refresh configuration information when the information stored in the Replication Manager database is newer than the information stored in the Device Manager server database, the Device Manager refresh function is executed first. For details on the Device Manager refresh function, see HP P9000 Command View Advanced Edition Suite Software Help or HP P9000 Command View Advanced Edition Suite Software CLI Reference Guide.
Data flow when configuration information is refreshed in mainframe systems The following figure shows the flow of data when configuration information is refreshed in mainframe systems.
Refreshing configuration information automatically (using the refresh settings) To minimize effects on operation, determine the refresh interval and start time carefully so that configuration information is refreshed while machine use is not heavy. You can also disable periodic refreshing if the configuration does not change.
3. Click the icon of the information source where you want to acquire configuration information automatically. The Edit Interval of Refresh Configuration - information-source-name dialog box appears. 4. Set and apply a refresh interval and refresh start time. The settings in the Configuration Setting subwindow are applied. From this point, configuration information is automatically refreshed based on the applied refresh settings.
NOTE: In an open system, pool information and journal group information will sometimes fail to be refreshed after a pair management server is restarted (Error code: RPM-01618). If this problem occurs, first refresh the statuses of the copy pairs in copy groups that were created using volumes in the target storage system, then refresh the pool or journal group information.
12 System monitoring Replication Manager provides multiple ways to monitor the operating status of the replication environment. You can monitor frequently viewed copy groups, check pair statuses, pair configurations, and the performance of remote copies. This chapter describes the different types of system monitoring functions supported by Replication Manager. About system monitoring Replication Manager allows you to perform the following types of system monitoring functions.
Monitoring resource utilization You can monitor the usage ratio of buffers (pools and journal groups) and receive alerts by email or SNMP traps based on the predefined thresholds. If you are an administrator, you can add volumes to the buffers using Replication Manager. Monitoring copy license usage You can monitor the used capacity and copy license usage percentage for each copy product in complex replication environments.
Checking copy pair configurations Replication Manager provides multiple ways to check copy pair configurations. For details on how to check copy pair configuration, see: • Checking copy pair configuration definitions, page 273 • Checking copy pair configuration (perspective of specific volume), page 274 • Checking copy pair configuration (perspective of specific copy group), page 275 Copy pair configuration check workflow The following figure shows the flow of tasks for checking copy pair configurations.
2. Expand the object tree nodes. Expand the tree nodes for the pair management server in the navigation area. 3. Check the copy pair configuration. Check the copy groups defined in the configuration definition file or the copy group definition file (prefix). When you select a copy group, you can view a list of copy pairs belonging to the copy group.
2. Select a volume. In the displayed list, select the volume (LUN or DEVN) where you want to check the copy pair configuration to display information. For a storage system that connects to mainframe systems, before selecting the volume, select the applicable LDKC and CU for the model. 3. Check the copy pair configuration. In the list of copy pairs related to the selected volume, check the copy pair configuration.
2. Expand the object tree, and then select a pair management server under Pair Configurations. The pair-management-server-name subwindow appears. 3. Select a configuration definition file. The information about the selected configuration definition file is displayed in the configuration-definition-file-name subwindow.
Monitoring pair statuses using alerts You can monitor pair statuses using alerts. Alerts can be sent when a specific copy pair enters a preset status. Alert conditions can be specified for an individual copy pair or for a copy group. For example, you can specify an alert is sent when a given error status is detected. In this case, an alert is sent when any of the copy pairs belonging to the copy group enters the error status.
Icons representing the relationship between a volume and a copy group Replication Manager uses icons representing volumes and copy groups and icons representing direction to indicate the relationship between a volume and a copy group. The following table lists and describes the icons that represent the relationship between a volume and a copy group: Icons representing the relationship between a volume and copy group Icon Description Indicates a primary volume.
Icon Description There is another copy pair connected in the cascade format to the copy pair's primary volume. There is another copy pair connected in the cascade format to the copy pair's secondary volume.
Checking the copy pair status Replication Manager provides multiple ways to check copy pair statuses: • “Checking status of copy pairs associated with volumes belonging to a host” on page 281. • “Checking status of copy pairs for a volume in a storage system” on page 281. Related topics • Copy pair status check workflow, page 280 About copy pair status checks Replication Manager provides multiple ways to check copy pair status.
Checking status of copy pairs associated with volumes belonging to a host To check the copy pair status for a volume of a host: 1. Select a host. From the Explorer menu, either choose Resources and then Hosts or choose Shared Views and then Sites. Select the host that contains the copy pair whose status you want to check. 2. Select a volume. In the displayed list, select the volume (LUN or DEVN) included in the copy pair whose status you want to check.
3. Check the copy pair statuses. In the list of copy pairs related to the selected volume, check the copy pair status, copy pair state, and copy progress for each pair.
Replication Manager can also be used to monitor asynchronous remote copying performed using Continuous Access Asynchronous or Continuous Access Journal. Write delay time or consistency time delta (C/T delta) can be monitored to acquire transfer delay status from volume replication facilities. You can display the transfer delay state between the primary and secondary volumes for each copy group.
• “Checking write delay time (C/T Delta) for each copy group” on page 285. Checking performance workflow (remote copies) The following figure shows the flow of tasks for checking the performance of remote copies.
Copy pair status Copy type • Continuous Access Asynchronous • Continuous Access Journal error suspend copying sync simplex BM BM CP -- -- Legend: CP: Copy progress (copy pair matching rate) BM: Differential-bitmap matching rate --: Not displayed Related topics • About copy pair status, page 205 • Viewing copy progress, page 285 Viewing copy progress To confirm copy progress, select a copy group on the Pair Configurations view or click the link on the My Copy Groups page.
4. Check the C/T delta. Use the copy group summary to check the C/T delta. For open systems, the difference between the data write times for the primary and secondary volumes is displayed. For mainframe systems, the difference between the secondary-volume consistency time and the current time is displayed for each consistency group. 5. Export the C/T delta history. If necessary, export the C/T delta history to a CSV or HTML file by clicking Export History.
Checking buffer usage (sidefiles and journal volumes) TIP: If you have registered the target copy group as one of your My Copy Groups, you do not need to use the following procedure. Instead, see “Refreshing copy pair statuses manually for My Copy Groups” on page 262. To check the usage of buffers (sidefiles and journal volumes) for each copy group: 1. Select a host or pair management server.
within the licensed capacity of each copy product. Additional licenses are required when the target volumes for pair configuration exceed the licensed capacity. You can view and monitor the used capacity and copy license usage percentage for each copy product to prevent license expiry. You can configure alerts to get notifications when copy license usage reaches a particular threshold or exceeds the licensed capacity.
Status Excluded Icon Description The object has been excluded from monitoring. Only displayed at the lowest level (information stores). When an object is excluded, the status of the object is not aggregated to the upper layer. Related topics • Checking the status of application replicas, page 417 • About aggregation rules for protection status, page 289 • Data protection status example, page 289 Data protection status example The following example illustrates how to interpret the status display.
Figure 11 Agreggation example (Exchange 2003/2007) Related topics • Checking the status of application replicas, page 417 • About data protection status, page 288 • Data protection status example, page 289 Excluding objects from data protection status monitoring During a maintenance operation, the protection status for a specific object could be intentionally set to Critical. In this case, aggregating the status would disturb status monitoring.
The status of the object changes to Excluded and is not aggregated to the upper layer. The latest replica is also ignored.
System monitoring
13 Managing resources This chapter describes different methods for managing resources. Resource management functions The following table describes the resource management functions, user permissions (Replication Manager management), and whether the functions can be used with the indicated permissions.
Permissions Function Admin Modify View Viewing copy pair configuration definition information Y Y Y Viewing information about copy groups belonging to a copy pair configuration definition Y Y Y Legend: Y: Can be used with this permission. N: Cannot be used with this permission. TIP: Each function can be used only for the resources in resource groups associated with the user.
• Viewing copy pair configuration definition information, page 275 • Structure of the Pair Configurations view, page 50 Viewing a list of copy pairs associated with a task You can view the list of copy pairs associated with a task to confirm copy status before or during task execution or to investigate the pair configuration or status of a selected copy group. To view the list of copy pairs associated with a task: 1. In the Explorer menu, choose Tasks and then Tasks.
TIP: For storage systems discovered by Device Manager, the storage system names displayed by Replication Manager on the Storage Systems subwindow are consistent with the storage system names in Device Manager. Any changes made to the storage system names in Device Manager are reflected in Replication Manager after a configuration refresh.
Viewing individual host information You can display the following information about individual hosts: For open system hosts: • List of volumes (LUNs) belonging to the host The volumes that constitute copy pairs (other than volumes in simplex status) are displayed in the Paired list, and the volumes that do not constitute copy pairs (including volumes in simplex status) are displayed in the Unpaired list.
Related topics • Viewing storage system information (open systems), page 304 • Viewing storage system information (mainframe systems), page 304 Viewing information about copy groups belonging to a copy pair configuration definition You can display the following copy group information belonging to a configuration definition: • Copy group summary • List of copy pairs belonging to a copy group • Copy group relationships Related topics • Viewing copy group information in the Hosts view (open systems), page 300
2. Expand the object tree, and then select a pair management server under Pair Configurations. The pair-management-server-name subwindow appears. 3. Select a prefix. The prefix-name subwindow appears. 4. Select a copy group. The information about the selected copy group is displayed in the copy-group-name subwindow.
3. On the Prefixes page, select a prefix. The prefix-name subwindow appears. 4. Select a copy group. The information about the selected copy group is displayed in the copy-group-name subwindow. Related topics • Viewing copy group information in the Pair Configurations view (mainframe systems), page 298 Viewing copy group information in the Hosts view (open systems) To view copy group information (open systems): 1. From the Explorer menu, choose Resources and then Hosts. The Hosts subwindow appears.
Viewing information about prefixes belonging to a host (mainframe systems) You can list the prefix information of mainframe hosts. The copy group information defined in the copy group definition files (prefixes), such as the copy type and summarized copy pair status, can then be checked. To view prefix information: 1. From the Explorer menu, choose Resources and then Hosts. The Hosts subwindow appears. 2. Expand the object tree, and then select a host under Hosts. The host-name subwindow appears. 3.
Related topics • Viewing LUN information in the Storage Systems view (open systems), page 303 Viewing information about CUs belonging to a storage system (mainframe systems) You can display the following information about the CUs used in mainframe storage systems: • CU summary The capacity of each CU is displayed. • List of volumes (LDEVs) belonging to a CU Information such as the serial number and capacity is listed for each volume. To view CU information: 1.
3. Click the Mainframe link. The Mainframe subwindow appears. 4. On the LDKCs page, select an LDKC. The LDKC-name subwindow appears. 5. Select a CU. The CU-name subwindow appears. 6. Select an LDEV. The information about the selected LDEV is displayed in the LDEV-name subwindow. LDEV display format The LDEV number is displayed in hexadecimal, as explained below. If the LDEV number is a single-digit number, a leading zero is added (0A for example) so that it will be displayed as a 2-digit number.
Viewing LUN information in the Hosts view (open systems) To view LUN information (open systems): 1. From the Explorer menu, choose Resources and then Hosts. The Hosts subwindow appears. 2. Expand the object tree, and then select a host under Hosts. The host-name subwindow appears. 3. Click the LUNs tab and then the Paired tab, and then select a volume. The information about the selected volume is displayed in the LUN-name subwindow.
TIP: Take note of the following: • Volumes that are currently locked by a task are marked with the icon. When you put the cursor over a locked entry in the Port/Host Group/LUN column, the following information is displayed indicating the name of the task: LU (Reserved by workflow: workflow-name) • Clicking Filter on the LUNs tab displays the Filter - Paired LUN List dialog box or the Filter - Unpaired LUN List dialog box.
Managing resources
14 Managing My Copy Groups This chapter describes tasks for managing My Copy Groups. My Copy Groups management functions The following table shows the My Copy Groups management functions, user permissions (Replication Manager management), and whether the functions can be used with the indicated permissions. Permissions Function Admin Modify View Viewing my copy groups Y Y Y Editing my copy groups Y Y Y Legend: Y: Can be used with this permission.
Checking My Copy Groups You can view My Copy Groups to check information such as the registered copy groups and the number of copy groups for each copy type. Each copy group functions as a link to the window that displays the detailed information of the copy group. However, the link is enabled only when you have access permissions for the pair management server (host) on which the copy group is defined. The access permissions you have depends on which resource groups are associated with you.
15 Managing storage systems This chapter describes tasks for managing storage systems. Managing V-VOLs This module describes tasks for managing V-VOLs: • Conditions for deleting V-VOLs, page 309 • Deleting V-VOLs, page 309 • Deleting multiple V-VOLs, page 309 Conditions for deleting V-VOLs The following restrictions apply when a V-VOL is deleted: • The V-VOL to be deleted must not be part of a pair configuration. • It is necessary to check whether the V-VOL to be deleted exists.
TIP: Any unselected V-VOLs in the same parity group as the V-VOLs selected for deletion are also listed in the Delete V-VOLs window. NOTE: For an HP StorageWorks P9500 storage system (regardless of CVS installation) only one V-VOL can be created in a single Parity Group. Therefore, if you delete a V-VOL, the Parity Group containing the V-VOL is also deleted.
Deleting command devices To delete command devices: 1. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 2. Expand the object tree, and then select a storage system under Storage Systems. The storage-system-name subwindow appears. 3. Click the Open link. The Open subwindow appears. 4. On the Cmd Devs page, select the check boxes of the command devices you want to delete, and then click Delete Cmd Devices.
• About remote paths, page 117 About deleting remote paths Remote paths can be deleted by performing the following operations: • Deleting the associated copy pair. Using this operation, you delete the copy pair that uses the remote path that you want to delete. By default, this method deletes the configuration definition file that defines the copy pair. You can also specify an option to only release the pair (placing the copy pair in simplex status) while retaining the configuration definition file.
A copy pair that is reserved for performing other copy pair operations cannot be deleted. You must first delete the applicable tasks and workflows. For details, see “Deleting tasks” on page 173 and “Deleting workflows” on page 179. • The copy pair of mainframe volumes exist: The copy pair specified by HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent cannot be deleted using Replication Manager.
Editing pools You can edit pool information (pool volumes and pool options) about existing pools. For details about the conditions that must be satisfied, see “Storage system types and volume requirements (pools)” on page 120. For details about pool usage threshold values that can be specified as an option for changing to warning status, see “Pool usage threshold values” on page 286. CAUTION: Once you have set volumes in a pool, you can no longer remove those volumes from the pool.
Related topics • About pool volumes, page 119 • Pool usage threshold values, page 286 Managing journal groups This module describes tasks for managing journal groups: • Editing journal groups, page 315 • Deleting journal groups, page 315 • Expanding journal group capacity, page 316 Editing journal groups You can edit journal group information (journal volumes and journal group options).
4. On the JNLGs page, select the check boxes of the journal groups you want to delete and click Delete JNLGs. The Delete Journal Groups dialog box appears. 5. Confirm the journal groups that will be deleted, and then delete them. The journal groups are deleted from the Open subwindow. Related topics • About journal groups, page 122 • Editing journal groups, page 315 Expanding journal group capacity To expand capacity of a journal group: 1.
16 Managing sites This chapter describes tasks for managing sites. About site administration In a complex replication environment, storage systems can be located at many sites. In such cases, you can create logical sites whenever necessary by grouping resources. Grouping resources based on the actual sites simplifies resource management because you can then use a graphical user interface for management.
Site management functions The following table describes the site management functions, user permissions (Replication Manager management), and whether the functions can be used with the indicated permissions.
Explorer menu Permissions Submenu Menu command Admin Modify View Shared Views Sites Y Y Y Legend: Y: Can be executed with this permission. Viewing a list of sites To view a list of registered sites, from the Explorer menu, choose Shared Views and then Sites. A list of registered sites is displayed in the Sites subwindow. Viewing individual site information You can display information about individual sites.
4. Edit and update the site information. The site information displayed in the Sites subwindow is refreshed. Related topics • Adding hosts to a site, page 98 • Adding storage systems to a site, page 99 • Adding pair management servers to a site, page 100 Removing hosts from a site To remove hosts from a site: 1. From the Explorer menu, choose Shared Views and then Sites. The Sites subwindow appears. 2. Expand the object tree, and then select a site under Sites. The site-name subwindow appears. 3.
Removing pair management servers from a site To remove pair management servers (hosts) from a site: 1. From the Explorer menu, choose Shared Views and then Sites. The Sites subwindow appears. 2. Expand the object tree, and then select a site under Sites. The site-name subwindow appears. 3. Click the Pair Configurations link. The Pair Configurations subwindow appears. 4.
The following topics are included in this module: • Deleting individual sites, page 322 • Deleting multiple sites, page 322 Related topics • Removing hosts from a site, page 320 • Removing pair management servers from a site, page 321 • Removing storage systems from a site, page 320 Deleting individual sites To delete a single site: 1. From the Explorer menu, choose Shared Views and then Sites. The Sites subwindow appears. 2. Expand the object tree, and then select a site under Sites.
17 Managing alerts This chapter describes tasks for alert management. About alert management Replication Manager can send an alert when a monitored target, such as a copy pair or buffer, satisfies a preset condition. The conditions that can be set include: thresholds for copy pair statuses, performance information, and copy license usage. You can specify a maximum of 1,000 conditions.
TIP: Each function can be used only for the resources in resource groups associated with the user. Related topics • About alert settings, page 127 Explorer menu items for alert management The following table shows the Explorer menu items that are related to alert management, user permissions (Replication Manager management), and whether the items can be executed with the indicated permissions.
Includes the resource from which each alert was issued and information about the detected event (copy pair status, performance information, or copy license usage). The maximum number of alerts is 1,000. • List of alert settings Includes the notification conditions such as the alert action (email or SNMP trap) and item being monitored (copy pair status, performance information, or copy license usage threshold). The maximum number of alert settings is 1,000.
Editing alert settings To edit alert settings: 1. From the Explorer menu, choose Alerts and then Alerts. The Alerts subwindow appears. 2. On the Alert Setting List page, click the icon of the alert whose settings you want to edit. The Edit Alert Setting - alert-name dialog box appears (where alert-name is the name of the alert whose icon you clicked). 3. Edit and update the alert notification conditions and monitoring targets. The alert settings displayed in the Alerts subwindow are refreshed.
• About alert settings, page 127 Deleting alert settings To delete alerts: 1. From the Explorer menu, choose Alerts and then Alerts. The Alerts subwindow appears. 2. On the Alert Setting List page, select the check boxes of the alerts you want to delete, and then click Delete Alerts. The Delete Alert Settings - alert-name dialog box appears. 3. Confirm the alerts that will be deleted, and then delete them. The alerts are deleted from the Alerts subwindow.
Managing alerts
18 Managing licenses This chapter describes tasks for license management. About licenses Licenses must be registered for the storage systems managed by Replication Manager. The following table describes the types of license keys. Types of license keys Type Description Permanent A license key required to use a product permanently. Permanent license keys are provided for each storage system that is to be managed by Replication Manager.
Explorer menu items for license management The following table shows the Explorer menu items that are related to license management, user permissions, and whether the items can be executed with the indicated permissions. Explorer menu Permissions Submenu Menu command Admin (user management) Admin, modify, or view (Replication Manager management) Settings License Info Y Y Legend: Y: Can be executed with this permission.
Related topics • About licenses, page 329 • Viewing license information, page 330 User Guide 331
Managing licenses
19 Managing users and permissions Replication Manager provides role-based user access control to secure protection processes and recovery operations and mitigate the risk of unauthorized operations. To achieve stringent access control and efficiency, multiple users can be allocated access to functions on the basis of their role in the organization. User permissions can be assigned for different categories such as Storage Administrator, Database/Server Administrator and Super User (RepMgr Administrator).
Explorer menu items for user management The following table describes the Explorer menu items that are related to managing users, user permissions, and whether the menu command can be executed with the indicated permissions. Explorer menu Permissions Submenu Menu command Admin (user management) permission Admin, modify, or view (Replication Manager management) permission Administration Users and Permissions Y N Legend: Y: Can be executed with this permission.
• User profile (information such as the user ID and full name) • List of permissions specified for each P9000 Command View AE Suite product To view the information for an individual user: 1. From the Explorer menu, choose Administration and then Users and Permissions. The Users and Permissions subwindow appears. 2. Expand the object tree, and then select a user ID under Users. Information about the user with the selected user ID is displayed in the user-ID subwindow.
Changing user roles To change the roles assigned to users: 1. From the Explorer menu, choose Administration and then User Roles. The User Roles subwindow appears. TIP: As with other menus under Administration, only users with Admin permission can access this window. The “User Roles” table lists all users with access to Replication Manager. • When no user role is assigned, the “Role” field is empty and the user is equivalent to the “Storage Administrator” role (with no restrictions).
3. Click Edit Profile. The Edit Profile - user-ID dialog box appears. 4. Edit and update user information. The user information displayed in the user-ID subwindow is refreshed. If the new user information is not applied immediately to the list of users in the Users subwindow, you can click Refresh Tree to refresh this information in the navigation area.
Deleting multiple users TIP: Do not delete the user account that is used for communication between Device Manager agents and the Device Manager server (default: HaUser). To delete multiple users: 1. From the Explorer menu, choose Administration and then Users and Permissions. The Users and Permissions subwindow appears. 2. Expand the object tree, and then select Users. The Users subwindow appears. 3.
• Viewing a summary of user permissions, page 339 • Changing user permissions, page 88 Viewing a summary of user permissions You can display summarized information about all P9000 Command View AE Suite products that have been installed. The displayed information includes the number of registered products and the number of users. To view a summary of user permissions: 1. From the Explorer menu, choose Administration and then Users and Permissions. The Users and Permissions subwindow appears. 2.
Permissions Admin (user management) permission Admin, modify, or view (Replication Manager management) permission Editing user profiles Y Y Changing user passwords Y Y Function Legend: Y: Can be used with this permission. Explorer menu items for user profile management The following table describes the Explorer menu items that are related to user profile management, user permissions, and whether the items can be executed with the indicated permissions.
3. Edit and update user information. The user information displayed in the User Profile subwindow is refreshed. If the new user information is not applied immediately to the list of users in the Users subwindow, you can click Refresh Tree to refresh this information in the navigation area.
• Changing the user authentication method, page 346 • Using an external authorization server (authorization groups), page 346 About account locking To prevent unauthorized individuals from logging in, you can set the system to automatically lock user accounts when invalid passwords are entered a specified number of times in succession.
• By default, the built-in account (user ID: System) cannot be locked. To enable locking of this builtin account, edit the user.conf file on the management server. For details about the user.conf file, see the HP P9000 Replication Manager Software Configuration Guide. • In P9000 Command View AE Suite products, you cannot change the lock status of a user that logs in by linking to an external authorization server because such an account has not been registered in the P9000 Command View AE Suite products.
4. Confirm the users whose accounts you want to unlock, and then unlock the accounts. The lock statuses of the users displayed in the Users subwindow are refreshed. NOTE: If you select a user account that is locked because no password has been set, the user account cannot be unlocked. If you set a password, the user account will be unlocked.
Linking to an external authentication server To link to an external authentication server: 1. On the Device Manager management server, specify settings for linking to an external authentication server. For details about requirements for an external authentication server and how to specify settings for linking to the server, see the HP P9000 Replication Manager Software Configuration Guide. 2.
Changing the user authentication method To change the method for user authentication: 1. From the Explorer menu, choose Administration and then Users and Permissions. The Users and Permissions subwindow appears. 2. Expand the object tree, and then select Users. The Users subwindow appears. 3. In the list of users, select the check boxes of the users for whom you want to enable or disable linkage to the external authentication server, and then click Change Auth.
Registering an authorization group To manage user accounts per authorization group, register authorization groups in the P9000 Command View AE Suite products. You cannot register only authorization groups that are already registered in the authorization server. You must first register authorization groups in the P9000 Command View AE Suite products, then register them in the authorization server. By default, All Resources is assigned to the authorization group as the resource group.
NOTE: The following restrictions apply. Permissions: When the Modify permission is granted to an externally authenticated group, detailed permissions (permission per operation provided by the User Role function) for users who belong to the group are set to the default value ("Storage Administrator") and cannot be changed. Resource Group: Users belonging to the externally authenticated group are assigned to the resource group All Resources, and this setting cannot be changed.
20 Managing security This chapter describes tasks for managing security. About security settings Replication Manager provides security functions that allow you to perform the following: • Set password conditions to prevent users from using easy-to-guess passwords. • Enable automatic locking of user accounts for which successive login attempts have failed. • Display a user-specified message (a warning banner) in the user login window at login time as a security measure.
Explorer menu items for setting security The following table shows the Explorer menu items that are related to setting security, user permissions, and whether the items can be executed with the indicated permissions. Explorer menu Permissions Submenu Menu command Admin (user management) permission Admin, modify, or view (Replication Manager management) Administration Security Y N Legend: Y: Can be executed with this permission. N: Cannot be executed with this permission.
The specified password conditions apply when new users are added or when passwords are changed. Because newly set conditions do not apply to existing user passwords, existing users can continue to log in to Replication Manager using their existing passwords, even if those passwords do not conform to the newly established conditions. To change password conditions: 1. From the Explorer menu, choose Administration and then Security. The Security subwindow appears. 2.
If you change the setting for the number of allowed login failures, the new setting does not apply retroactively to users who have already exceeded the new value or to user accounts that are already locked. For example, if you change the number of login failures from 5 to 2, a user account whose number of successive login failures is 3 remains valid. However, the account will be locked if the user's next login attempt fails. To change the settings for the automatic account locking function: 1.
Related topics • About warning banners, page 352 Editing a warning banner To edit a warning banner: 1. From the Explorer menu, choose Administration and then Security. The Security subwindow appears. 2. Expand the object tree, and then select Warning Banner under Security. The Warning Banner subwindow appears. 3. Click Edit Message. The Edit Message dialog box appears. 4. Edit and update the message that will be set up as a warning banner. Click Preview to display a preview in HTML.
Managing security
21 Managing resource groups This chapter describes the tasks for Resource Group management. About resource group management Resource groups can be managed only by users with the Admin (Replication Manager management) permission. Users other than the System built-in account can only use the resources in the associated resource groups, the configuration definition of those resources, and alerts.
Permissions Function Admin Modify View Adding applications to a resource group Y N N Removing applications from a resource group Y N N Legend: Y: Can be used with this permission. N: Cannot be used with this permission. Explorer menu items for resource group management The following table describes the Explorer menu items that are related to resource group management, user permissions (Replication Manager management), and whether the items can be executed with the indicated permissions.
Viewing a list of resource groups To view a list of registered resource groups, from the Explorer menu, choose Administration and then Resource Groups. Registered resource groups are listed in the Resource Groups subwindow.
3. On the Hosts page, select the check boxes of the hosts you want to remove, and then click Remove Hosts. The Remove Hosts - resource-group-name dialog box appears. 4. Confirm the hosts to be removed, and then remove them. The selected hosts are removed from the Hosts page. Related topics • About resource groups, page 89 • Adding hosts to a resource group, page 91 Removing storage systems from a resource group You can remove storage systems registered as resources from their resource groups.
To remove users from a resource group: 1. From the Explorer menu, choose Administration and then Resource Groups. The Resource Groups subwindow appears. 2. Expand the object tree, and then select either a resource group under Resource Groups or the All Resources group. The resource-group-name subwindow or the All Resources subwindow appears. 3. On the Users page, select the check boxes of the users you want to remove, and then click Remove Users.
NOTE: You cannot delete the default resource group All Resources, which is the group in which all resources are automatically registered. The following topics are included in this module: • Deleting individual resource groups, page 360 • Deleting multiple resource groups, page 360 Deleting individual resource groups To delete a single resource group: 1. From the Explorer menu, choose Administration and then Resource Groups. The Resource Groups subwindow appears. 2.
22 Managing information sources This chapter describes tasks for managing information sources. Viewing a list of information sources You can display a list of the Device Manager servers, instances of HP StorageWorks P9000 for Business Continuity Manager Software, instances of P9000 mainframe agent, or instances of Application Agent that are used as Replication Manager information sources. To view a list of information sources: 1. From the Explorer menu, choose Administration and then Information Source.
2. Expand the object tree, and then select Device Manager. The Device Manager subwindow appears. 3. Click the icon of the Device Manager server whose information you want to change. The Edit Device Manager - Device-Manager-server-name dialog box appears. 4. Edit and update the information about the Device Manager server. The information about the Device Manager server displayed in the Device Manager subwindow is refreshed.
Editing an instance of HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent To edit an instance of HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent: 1. From the Explorer menu, choose Administration and then Information Source. The Information Source subwindow appears. 2. Expand the object tree, and then select BC Manager / Mainframe Agent. The BC Manager / Mainframe Agent subwindow appears. 3.
• Removing instances of Application Agent, page 365 TIP: User-configured My Copy Groups and alert settings are not cleared automatically when you delete the information sources. For details on how to manually clear the relevant settings, see “Editing My Copy Groups” on page 308. For details on how to manually clear the alert settings, see “Deleting alert settings” on page 327.
3. Select the check boxes of the Device Manager servers you want to delete, and then click Remove DevMgrs. The Remove Device Managers dialog box appears. 4. Confirm the Device Manager servers you want to delete, and then delete them. The selected Device Manager servers are deleted from the Device Manager subwindow.
5. Confirm the instances of Application Agent you want to delete, and click Confirm. The selected agent instances are deleted from the Application Agent subwindow.
User Guide 367
Managing information sources
23 Managing application replicas This chapter describes how to manage application replicas using Replication Manager. About application replicas An application replica is a snapshot of an application server that is saved to a series of secondary volumes on an immediate or scheduled basis. As with copy pair management, the creation and management of application replicas is organized around tasks and storage assets. Replication Manager is used to create, manage, and (manually) restore replicas.
As shown in Figure 12, because there is a limit of three generations, the fourth generation must write over one of the preexisting volumes. In this case, the oldest volume (generation 1) is overwritten. Generations 5 and 6 follow the same pattern of overwriting the oldest, existing generation. Figure 12 Backing up multiple generations The order in which secondary volumes are used for backups does not change regardless of which generation you might decide to restore at some point in time.
Figure 13 Backup and restore operations Related topics • Creating an application replica, page 388 • Restoring the latest application replica (simple restore), page 395 About storage groups and information stores Storage groups are objects managed by Microsoft Exchange 2003/2007 to store databases. Multiple databases can be managed together because databases within the same group use a common transaction log.
Exchange 2010 does not use storage groups, therefore individual information stores are managed by Replication Manager. The following table lists which objects are eligible for Exchange replica operations.
Deleting copy groups used for replica operations When an attempt is made to delete a copy group that is in a HORCM instance used by Application Agent, the Pair Configuration Wizard task may fail with the error message KAVN02521-E (RPM-00527). If this occurs, first delete the HORCM instances from the Setup Application Agent dialog box on the database server and the backup server.
• Data files to be stored on a particular disk drive must belong to the same instance. Data files from different instances must not be stored on the same disk drive. Mount status of secondary volumes Unmount all secondary volumes before performing a backup or restore to a database server. Failing to do so may cause unpredictable results.
2. Back up database A only. The replica 2010/9/06 08:15:00 is created. The following figure shows the correspondence of the backup catalog and copy group. Figure 14 Correspondence of backup catalog and copy group When you back up database A only (as described in step 2), the replica 2010/9/06 08:15:00 is created, and the old backup information (replica 2010/8/31 07:14:00) about the copy group vg01,obj01 on database A is deleted from the backup catalog.
• The configuration file for an SQL Server database is added or deleted. • The configuration file for an SQL Server database is moved. • The name of a configuration file of an SQL Server database is changed. TIP: When rebooting a system that references a secondary volume (replica), be aware that the volume might be mounted automatically. Daylight savings time Daylight saving time involves adjusting the system time of the database server for certain time periods.
• On Exchange 2010 (which does not use storage groups), all information to be backed up must be mounted in advance. • You cannot back up storage groups extending across multiple database servers. • The recovery storage groups for Exchange Server 2003/2007 cannot be backed up. The files and folders that make up the restoration storage group must be placed on a different file system from the storage groups to be backed up.
Event Type: Warning Event Source: VSS Event ID: 12290 Description: Volume Shadow Copy Service warning: GetVolumeInformationW(\\?\Volume{XXXXXXXX-XXXX-XXXX-XXXX XXXXXXXXXXXX}\,NULL,0,NULL,NULL,[0x00000000], , 260) == 0x00000057. hr = 0x00000000. Event Type: Warning Event Source: VSS Event ID: 12290 Description: Volume Shadow Copy Service warning: GetVolumeInformationW(\\?\Volume{XXXXXXXX-XXXX-XXXX-XXXX XXXXXXXXXXXX}\,NULL,0,NULL,NULL,[0x00000000], , 260) == 0x00000001. hr = 0x00000000.
• • • • properly and the restored database might not be available. If this occurs, detach the database and restore it again. Make sure that all databases to be restored are ready. For information on the status of a database, see “About SQL database and service status” on page 401. A database with the Unconfirmed status is automatically removed and restored. If any of the databases to be restored are not ready, the process might fail.
• In a cluster environment, when restoring data in a physical node different from that used during backup, an Exchange virtual server that uses the same shared disk as that used during backup must be running. Replication Manager cannot restore data for an Exchange virtual server, such as one at a remote site, that uses a disk different from the one used during backup. • While restoring a replica, do not open the physical disk resource property of the cluster administrator screen.
When restoring individual databases: Define one consistency group to one database so that each database is in a separate consistency group. When restoring multiple databases: If you want databases to be restored together, place them in the same consistency group. NOTE: Define one consistency group as one group (dev_group) of P9000 RAID Manager configuration definition files so that there are never too many or too few copy groups.
Database subject to backup Exchange Server 2010 information stores Files subject to backup Extension data files (Exchange Server information stores *.edb Transaction log files *.log Checkpoint files *.chk Databases are backed up and restored in units of volumes, so the configuration of objects of an Exchange database has the following conditions: • The files to be backed up must all be placed on a RAID volume defined as a pair.
*: When a VDI metafile storage directory is registered in the SQL Options tab of the Setup Application Agent dialog box, the metafile is stored in the registered directory. The file name is backup-ID_database-ID.dmp. When default is selected for the VDI metafile storage directory, the metafile is stored in the directory that contains the file whose management number (file_id) for SQL Server in the database file is a minimum value. The file name is META_xxx.dmp.
• Databases that use the snapshot function cannot be backed up and restored by Replication Manager. If configured to back up a database snapshot, the backup will fail. When backing up an entire instance, first remove any database snapshots. • The service broker becomes disabled when databases are restored using Replication Manager.
For best results, store metafiles in a volume belonging to an SQL Server resource group so that, even if an SQL Server cluster resource fails over, the metafiles are failed over with the resource group. The following figure shows a sample location for metafiles in an active/standby (or active/passive) cluster configuration.
Windows Indexing Service (cisvc.exe) Observe the following precautions with the indexing service: • Confirm that the master combination of index service is not in use. File access by the index service and replica operations may cause a conflict that prevents the execution of a replica task. • Do not use a volume for backup and restore which is the save location of the index service catalog.
Figure 18 Create application replica workflow About the Create Replica Wizard Replication Manager includes a Create Replica Wizard for creating snapshots of application servers. The Create Replica Wizard provides the following functions: • Choose to create a new task or edit an existing one, and select target objects. • Set options including the rotation of target volumes, execution options, and mount options (for tape backups). • Schedule the execution of the task.
Creating an application replica To create an application replica: 1. From the Explorer menu, select Resources, and then Applications. The Applications subwindow appears. 2. Expand the object tree and select a server. The summary information for the selected server is displayed. 3. Select one or more application resources: storage groups (Exchange 2003/2007), information stores (Exchange 2010), or database instances (SQL Server) and click Create Replica. The Create Replica Wizard is launched. 4.
8. The 3. Set Schedule page is displayed. 1. 2. To create the replica immediately (without a recurring schedule) select Execute immediately. For scheduled replica creation (single or recurring), select Execute on schedule, choose a Schedule Type, and select the applicable calendar options. NOTE: Do not create a schedule that will cause a copy pair to re-synchronize.
• Point-in-time When backup data on an Exchange Server or SQL Server database server is restored, the database returns to the state at the point-in-time when the backup occurred. If the transaction logs from the time when the backup was executed up until the restore are stored on the primary volume, the uncommitted transactions can be applied using the roll-forward option. By applying the transaction logs after backup, the database is restored to a state immediately before the error occurred.
Figure 19 Flow of operation using transaction logs (Roll-forward) After the database is backed up from the primary volume to the secondary volume at point A, the database is updated at point B. If an error occurs in a data file on the primary volume at point C and then the database is restored from the secondary volume to the primary volume, the database returns to the state it was in at point A.
Figure 20 Restoring data in units of information stores by applying transaction logs (roll-forward) The prerequisites for this example are the same as for the previous scenario, plus the following: • Only the data files (*.edb and *.stm) in the information store are stored on the same drive. • The transaction log file on the primary volume is not destroyed (roll-forward is executable). • Storage group SG1 has been backed up from the primary volume to the secondary volume.
• Configurations in which only information store data files (*.edb and *.stm) to be restored individually are stored on the same LDEV • Configurations in which multiple information store data files within the same storage group are stored on the same LDEV You can restore all information stores stored on the same LDEV provided that you specify all the information stores. In this case, if you do not specify all information stores located on the same LDEV, the restore operation will fail.
NOTE: The following restrictions apply: • When restoring backup data in units of information stores, you must apply (roll forward) the transaction log at the time of restoration. • To restore backup data in units of information stores, you need at least three LDEVs for one storage group. If you are using Continuous Access as the volume duplication function, up to two LDEVs can be backed up for a single storage group. This means that you cannot restore backup data in units of information stores.
Restoring the latest application replica (simple restore) TIP: This operation is available when all the target resources can be restored from a single replica. If target resources are managed by multiple tasks/replicas, see “Restoring an application replica from the Replica History” on page 396. To perform a simple restore of the most recent replica: 1. If you are restoring a replica located at a remote site to the local site, run the Change Pair Status Wizard and split the copy group. 2.
8. Choose the Restore Mode. • Point-in-time Restore: Restores the replica and the transaction logs (without committing the outstanding transactions). • Roll-forward Restore: Restores the replica and then commits any outstanding database transactions stored in the transaction logs. NOTE: A roll-forward operation cannot be performed for SQL Servers from within Replication Manager.
3. Expand the object tree, and then select a database server. The Server summary window appears. 4. Open the Replica History tab to view a list of replicas. 5. Select a replica and click Restore Replica. The Restore Replica Wizard is launched. 6. Follow the procedure in “Restoring the latest application replica (simple restore)” on page 395 starting at step 5.
2. Use the disk management function to unmount the primary volume connected to the database server. 3. Stop SQL Server on the backup server. 4. Select the replica associated with the volume in step 2 from the Replica History and click Unmount Replica. 5. Select the copy group, start the Change Pair Status Wizard, and select create. 6. Select the copy group, start the Change Pair Status Wizard, and select swap. 7.
Using Database Availability Groups (DAGs) Replication Manager supports Exchange Database Availability Groups (DAGs). In a DAG configuration, data mirroring occurs between the DAG active node and passive nodes. (The target server can be an active or passive node.) NOTE: The DAG feature is exclusive to Exchange Server 2010. For more information, see “About Database Availability Groups (DAGs)” on page 400.
• You cannot simultaneously create the replica of the active and passive mailbox database copies. Wait until execution of the replica creation is finished for the first mailbox database copy before you begin create the replica of the other mailbox database copies. • When you restore a replica, the target mailbox database copy must be an active mailbox database copy. • A replica can be restored only to the Exchange Server 2010 server where the replica was created.
Related topics • Using Database Availability Groups (DAGs), page 399 About SQL database and service status When Replication Manager is used to restore data from a secondary volume to a primary volume, the status of the database becomes either loading or standby: • Loading status (loading) The database can neither be viewed nor updated. • Standby status (read-only) The database can be viewed, but not updated.
SQL Server database status User action Online Offline • • Roll-forward restore (loading)5 Loading Readonly Unconfirmed •1 • •2 Offline and Unconfirmed Loading and Unconfirmed •2 •2 Readonly and Offline Readonly and Unconfirmed Readonly, Offline, and Unconfirmed • •2 •2 Legend: • : Action permitted and database changes are allowed. o : Action permitted and no database changes allowed. x : Action not permitted. Notes: 1.
x : Action not permitted.
POST_PROC: Post-procesing specified by the user (after the backup command is issued). Table 23 Coding rules Applicable items Rules • The character code set must be ASCII. • Codes lower than 0x20 cannot be used, except for CR (0x0d), LF (0x0a), and TAB (0x09). Overall user script • The linefeed code must be LF (0x0a) or CR+LF (0x0d and 0x0a). • The length of a single line must not exceed 8 KB. • Do not execute a command that will display more than 2000 bytes of text.
NOTE: If command line execution from a user script times out, the task might remain in the Executing status. If this happens, perform the following procedure before re-creating the task: 1. Restart the Application Agent service. 2. Update the task information. 3. Revise the CMDLINE and TIMEOUT settings in the user script. Table 24 Script entries Entry name Meaning and specifiable values Multiple specification Omit LOCAL_BACKUP Specify YES.
Entry name Meaning and specifiable values Multiple specification Omit Not allowed Not allowed Allowed Allowed Specifies a command line to be executed. • If you want to specify an option, separate the command name and the option with a one-byte space character. • One command definition section must contain only one command line. • A maximum of 2048 characters can be specified on a command line. • A path or file name containing one or more spaces must be enclosed in double quotation marks (").
Entry name Meaning and specifiable values Multiple specification Omit Not allowed Allowed Not allowed Allowed Not allowed Allowed Not allowed Allowed Specifies the action to be performed in response to the return value of the executed command. Specifiable values are as follows: TERMINATE_NZ (default) Terminates script processing if a non-zero return value returns. IGNORE Continue processing whatever may be returned for a return value.
Environment variables The table below shows the Application Agent script environment variables that must be referenced by commands in the user post-processing section. These script environment variables can be referenced from the local server and the backup server. DRMENV_L_BACKUPID Backup ID of the local server. This environment variable is valid in the following cases: • The command is being executed in the local server. • The execution status of the parent command is normal.
Script text Explanation PARENT_STAT=NORMAL Execute only when the backup command is normal. Unmounting after an automatic mount If you specify the Automatically mount during the operation option while using the Create Replica Wizard, to automatically unmount the replica after the backup has been completed, you must execute the drmumount command. The Batch command file example demonstrates how to do this.
Preparing the user script and batch command file To prepare the script for execution from the Create Replica Wizard: 1. Save the user script file in any folder on the database server. You must supply this location in the Create Replica Wizard. 2. Save the batch command file in the directory C:\tmp on the backup server.
• SQL Server only: The database server must be set up with the default VDI Meta File Location in the SQL Options tab of the Setup Application Agent dialog box. • The backup server must be set as the tape backup destination by setting Replica Catalog Location in the Server Options tab of the Setup Application Agent dialog box. To save a replica to tape: 1.
• Select Execute pre/post jobs with Agent User Script and supply the path to a Script File located on the production server. TIP: If you set the Automatically mount during the operation option in the Create Replica Wizard, you should unmount the volume manually when the restore is complete. Command line tools Several command line tools to support tape operations are installed as part of Application Agent.
name containing space characters for the -f option, you must enclose the path name in double quotation marks ("). Return values are 0 for normal termination; any other value indicates an error. drmdbimport command The drmdbimport command imports, into a backup catalog, backup-information from a file that was exported by the drmdbexport command. Application Agent programs manage backup information based on copy groups, which are used as a key.
When the SQL Server replication function is used, the following requirements must be satisfied: • You must use the transaction replication type. • The name of the distribution database must be distribution, and only one distribution database can be created. • The subscription database must be restored separately from the system database (master, model, msdb), so the subscription database must be configured in a different volume than the system database.
Figure 26 Configuration of backup server for the publisher/distributor server (detail) Backing up the databases The publication database needs to be backed up at the same time as the distribution database. From the Select Target window of the Create Replica Wizard, select both the publication and distribution databases. Backing up the publication database transaction log Use Management Studio to back up the transaction log.
• For push subscription: use the publisher/distributor server. • For pull subscription: use the subscriber server. On the appropriate server, do the following: 1. Start the log reader agent. 2. Start the subscription agent. 3. Re-initialize the subscription, or remove and then recreate the subscription. Mounting and unmounting application replicas Replicas can be mounted or unmounted on the backup server as desired.
Checking the status of application replicas The status of application replicas is summarized in the Applications and Server subwindows. A set of icons represent how recent the replicas are, whether they have been created successfully, and so on. These icons are discussed in “About data protection status” on page 288. To check the data protection status of application replicas: 1. From the Explorer menu, choose Resources and then Applications. The Applications subwindow appears. 2.
2. Expand the object tree, and then select a database server. The Server summary window appears. 3. For Exchange 2003/2007, the Storage Groups tab allows you to view the storage groups associated with the server. For Exchange 2010, the Information Store tab allows you to view the information stores associated with the server. Clicking an object opens the Monitoring Setting window, which lists the information stores and Task ID links.
24 Handling errors This chapter describes error handling mechanisms supported by Replication Manager. About handling errors To monitor for errors occurring in a complex replication environment, you must acquire information that identifies the locations of errors. With Replication Manager, you can set alert conditions for monitoring entities such as copy pairs, copy groups, journal groups and copy licenses.
Event log management functions The following table shows the event log management functions, user permissions (Replication Manager management), and whether the functions can be used with the indicated permissions. Permissions Function Viewing a list of event log files Admin Modify View Y N N Legend: Y: Can be used with this permission. N: Cannot be used with this permission.
Icon Severity Description Error Indicates that the message describes an error related to the operation that was performed. Warning Indicates that the message shows a warning or confirmation for the operation that was performed or that is to be performed. Information Indicates that the message shows the processing status or result of the operation that was performed. Troubleshooting the replication environment For a diagram, see “Troubleshooting the replication environment workflow” on page 421.
NOTE: By default, alerts are automatically marked as completed when the pair leaves the monitored status. If the automarking feature has been disabled, the alert must be handled manually. See “Marking alerts as completed” on page 326 for more information. About MIB definition files You can check received SNMP traps using the MIB definition files provided by Replication Manager.
25 Exporting management information This chapter describes tasks for exporting management information. About exporting management information You can export Replication Manager management information to a file in CSV or HTML format. Using the exported file, you can determine the cause of an error, establish corrective measures, and analyze performance information. If necessary, you can edit the file or open it with another application program. You can export a maximum of 20,000 data items at a time.
Permissions Function Exporting event log files Admin Modify View Y N N Legend: Y: Can be used with this permission. N: Cannot be used with this permission. TIP: Each function can be used only for the resources in resource groups associated with the user.
3. Specify a time period for the information to be exported and the export format, and then export the information. The alert history is exported to a file. Related topics • About exporting management information, page 423 Exporting event log data To export event log data: 1. From the Explorer menu, choose Administration and then Event Logs. The Event Logs subwindow appears. 2. Click Export. The Export Event Logs dialog box appears. 3.
Exporting the history of journal volume usage for each copy group To export the history of journal volume usage on a copy group basis: 1. Display the information about the copy group whose journal volume usage history you want to export. For details on how to display this information, see the following: • • • • 2.
Related topics • About exporting management information, page 423 Exporting the history of pool volume usage To export the history of pool volume usage: 1. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 2. Expand the object tree, and then select a storage system under Storage Systems. The summary information for the selected storage system is displayed. 3. Click the Open link. The Open subwindow appears. 4.
• About exporting management information, page 423 428 Exporting management information
26 System maintenance This chapter describes the system maintenance functions supported by Replication Manager. About system maintenance In Replication Manager, system maintenance can be performed by changing the operation mode from normal to maintenance mode and managing the retention periods of data according to system configuration and operating status. Changing to maintenance mode disables monitoring operations during maintenance operations such as replacement of the storage system microprogram.
Explorer menu Permissions Submenu Menu command Admin Modify View Administration Maintenance Y N N Data Retention Y N N Legend: Y: Can be executed with this permission. N: Cannot be executed with this permission. About operation modes During storage system maintenance it may be necessary to disable Replication Manager monitoring functions. Thisn can be done by entering maintenance mode. Normal mode The default mode.
2. Click Change Mode. Either the Change Mode to Maintenance dialog box or the Change Mode to Normal dialog box appears. 3. Read the message, and then change the operation mode. The operation mode displayed in the Maintenance subwindow is updated.
System maintenance
27 Support and other resources Numerous support options are available. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
Conventions This guide follows the conventions shown in Table 26 to refer to HP StorageWorks P9000 products.
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: • Continuous Access Journal Continuous Access Journal • Continuous Access XP Journal • P9000 Continuous Access Journal • XP Continuous Access Journal This abbreviation is used when it is not necessary to distinguish the following products: Data Retention Utility • Data Retention Utility • LUN Security XP Extension • XP Data Retention Utility This abbreviation is used when it
Support and other resources
A Web browser This appendix provides information related to configuring web browsers and applicable restrictions. Configuring a web browser to use Web client With Replication Manager, you operate the Web client through a web browser.
5. In the Trusted Sites dialog box, register the URL for Replication Manager. TIP: Make sure that the URL you specify is in the following format: http://IP-address-or-host-name:port-number/ReplicationManager/ When using Internet Explorer 6.0 in an IPv6 environment, you cannot specify an IPv6 address as the Replication Manager URL. You must specify the host name. Examples: SSL not used: http://127.0.0.1:23015/ReplicationManager/ SSL used: https://127.0.0.
TIP: Please review the information in “Cautionary notes for Web client” on page 445. Internet Explorer Enhanced Security Configuration and Windows Server If you are using Internet Explorer on Windows Server 2003 or Windows Server 2008, be aware that Internet Explorer Enhanced Security Configuration (IE ESC) is enabled by default.
Web browser
B Icons This appendix provides a listing of icons and their descriptions. Icons for executing operations Clicking an icon for executing an operation displays a dialog box or wizard. The following table lists and describes the icons for executing operations: Icon Description Starts a wizard for changing the pair status. The icon is called Change Pair Status. Displays a dialog box for editing the settings. This icon is disabled when the settings cannot be edited. The icon is called Edit.
Icon Copy pair status Description suspend The copy pair is in the split status. copying The copy pair is under forward or backward copy processing. sync The copy pair is synchronized. simplex There is copy pair definition information, but there is no actual copy pair configuration. Replication Manager cannot determine the pair status due to any of the following reasons: unknown • The settings are set not to acquire copy pair statuses.
Icon Description Indicates a copy group container. Indicates a copy pair. Indicates a newly created copy pair. Indicates an edited copy pair. Indicates a deleted copy pair. Indicates a reserved copy pair. Indicates a hundred LUs. Indicates an LU. Indicates a reserved LU. Indicates an LDEV. Indicates a reserved LDEV. Indicates a root node in the site. Indicates a workflow. Indicates an Exchange root node of an application group.
Icons
C Exceptions This appendix provides information about complex system configuration scenarios. Cautionary notes for Web client Certain cautionary notes exist for the Web client.
• A P9000 RAID Manager configuration definition file must be present. If a copy pair is created using storage system operation management software (such as Remote Web Console) and there is no configuration definition file, configuration definition information is not displayed in the pair configurations view.
configurations view, information about both copy groups CG.CntAc-A01 and CG.CntAc-A02 is displayed. Example configuration in which two copy group definition files are used for the same copy group (for mainframe systems) In this example, the definition files applied during the day and at night (for backup operation) are used for the same copy group. In the example, in the Hosts view or Storage Systems view, two copy group names (CG.TCA01 and CG.
When the copy pair configuration is complex For a complex configuration, such as one in which a copy group has two primary volumes, copy group configuration information cannot be displayed when copy groups are displayed in list format, as they are in the pair configurations view.
Example of complex cascade configuration 2 Example of when two pairs in a cascade configuration are defined in the same copy group Restrictions when Replication Manager and Device Manager versions differ The following matrix defines features supported depending on the versions of Device Manager and Replication Manager. Replication Manager version Device Manager / Agent version 6.0 6.1 6.2 6.3 6.4 7.0 7.0.1 7.1.0 7.1.1 7.2 6.
Replication Manager version 6.0 6.1 6.2 6.3 6.4 7.0 7.0.1 7.1.0 7.1.1 7.2 7.1.1 1 1 1 1 1 1 1 1 1 10 7.2 1 1 1 1 1 1 1 1 1 1 Legend: 1. 2. No restrictions. The following functions are not supported: • License usage and alert settings • Remote path settings 3. The following functions are not supported: • V-VOL management • Deletion of copy pairs related to remote paths • HORCM_LDEV format output of configuration definition files 4.
When the displayed information depends on the system configuration In Replication Manager, displayed information might be limited by the system configuration. The following describes such limitations separately for open systems and mainframe systems. For open systems In open systems, if a Device Manager agent is not installed on a host, the IP address and mount point of the host cannot be obtained and therefore are not displayed.
Information whose display is limited Displayed information Sidefile usage rate on the secondary volume side (for Continuous Access Asynchronous) n/a Information about the secondary volume (DEVN) (hosts view) This information is not displayed in the list of DEVNs.
issue simultaneous processing requests to an DevMgr Agent or BCM Agent associated with an information source, there is a possibility for errors during DevMgr Agent or BCM Agent processing. In such configurations where Replication Manager is to be set up on both the local (operating) site and remote (standby) site in order to prepare for disaster recovery, HP recommends that the status of Replication Manager server on the standby site be set to maintenance mode.
Exceptions
D Display formats This appendix provides information on supported display formats. Display formats used when no pertinent information is available If no pertinent information is available, several items are displayed in Web client depending on the context: No object Indicates that Replication Manager cannot acquire the information because the information source does not exist. In this case, the connection with the information source must be re-established.
(Unknown icon) or Unknown (For the summary copy pair status, the Unknown icon is displayed. For the copy pair state, Unknown is displayed.) Indicates that Replication Manager cannot determine the pair status due to any of the following reasons (unknown): • The settings are set not to acquire copy pair statuses. • The configuration does not allow copy pair statuses to be acquired. • The configuration information has already been acquired, but the copy pair information has not.
Display format in Web client Copy type Cnt Ac-A Continuous Access Asynchronous Cnt Ac-S Continuous Access Synchronous Snapshot Snapshot Cnt Ac-J Continuous Access Journal Cnt Ac-J (3DC Delta Resync) Continuous Access Journal (when 3DC delta resync is supported) User Guide 457
Display formats
E Supported functions This appendix provides information on functions supported by Replication Manager.
Open Mainframe DevMgr Server DevMgr Agent BC Manager P9000 mainframe agent Y Y N Replication operation support functionality Changing copy pair statuses N Legend * - Only the pair definition function for creating a copy group definition file is supported. The creation of copy pairs is not supported. Related topics • Checking copy license usage, page 288 List of tasks supported for each storage system The tasks supported by Replication Manager depend on the storage system model.
Support for each storage system Upper row: open system Lower row: mainframe system Task Setting up command devices XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 N N Y Y Y N N N N Y N N Y Y Y N N N N Y N N Y Y Y N N n/a n/a n/a N N Y Y Y N N N3 N3 N3 N N Y Y Y N N Y4 Y4 Y4 Setting up remote paths Setting up pools Setting up journal groups Replicating volumes Creating and editing copying pair configuration definitions Checki
Support for each storage system Upper row: open system Lower row: mainframe system Task XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 N N Y Y Y N N n/a n/a n/a N N Y Y Y N N N N N Setting and managing alerts N N Y Y Y (Copy license usage) N N Y Y Y Changing the copy pair status N N Y Y Y (create, delete) N N Y5,6 Y5,6 Y5,6 Changing the copy pair status Y Y Y Y Y N N Y6 Y6 Y6 Setting and managing alerts (Performance informa
Support for each storage system Upper row: open system Lower row: mainframe system Task XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 Y Y Y Y Y N Y Y Y Y Detailed monitoring of and alert notification regarding individual copy pairs Y Y Y Y Y N Y Y Y Y Termination of monitoring during a planned outage Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Automatic re-sending of alerts Replication failure analysis Storing and exporting remote copy pe
6. 7. 8. This function can be used only when BC Manager is used. It cannot be used with P9000 mainframe agent. Continuous Access Journal and Continuous Access Synchronous are supported. No other remote copy or local copy functions are supported. Device Manager agent 6.4.0 or later must be installed on the host. Unsupported configurations (open systems) The following is a list of unsupported open systems pair configurations.
Glossary This glossary defines the special terms used in this document. Click the desired letter below to display the glossary entries that start with that letter. 3DC Multi-target configuration A configuration in which, in addition to the local site, a connection is established between a nearby remote site and a distant remote site and Continuous Access Synchronous and Continuous Access Journal are used to copy storage system volumes among the three sites (called a data center).
configuration definition file The text file which defines connected hosts and the volumes and groups known to the P9000 RAID Manager instance. Physical volumes (special files) used independently by the hosts are combined when paired logical volume names and group names are given to them. The configuration definition file establishes the correspondence between the physical volumes used by the hosts, the paired logical volumes and the names of the remote hosts connected to the volumes.
DAD (Device Address Domain) A DAD is a group of volumes that is managed by HP StorageWorks P9000 for Business Continuity Manager Software. Volumes are registered in a DAD during a volume scan (discovery) by HP StorageWorks P9000 for Business Continuity Manager Software. Depending on the type of volume scan, volumes are assigned the local DAD, Non Gen'ed DAD, or remote DAD attribute. DAD ID A name that identifies a DAD.
HORCM Instance The basic unit of P9000 RAID Manager software structure. Each copy of a P9000 RAID Manager on a server is a P9000 RAID Manager instance. Each instance uses a defined configuration file to manage volume relationships while maintaining awareness of the other P9000 RAID Manager instances. Each P9000 RAID Manager instance normally resides on one server (one node). If two or more nodes are run on a single server (e.g.
LU (Logical Unit) A volume created in a storage system - known as an LU (logical unit) in an open system. LUN (Logical Unit Number) A management number assigned to an LU in a storage system. A LUN is a number assigned to identify an LU for the port in the storage system to which the LU is connected, either by the port or by the host group assigned to the port. An open system host uses a LUN to access a particular LU.
paired volumes Denotes a primary and secondary volume pair linked by the volume replication functionality of a storage system. Also called a copy pair. In this manual, copy pair is sometimes written simply as pair. PPRC Peer-to-Peer Remote Copy prefix The prefix portion of a copy group definition file (prefix.GRP.copy-group-id) created by HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent.
SAN Storage Area Network SATA Serial ATA Snapshot Pool Object within a storage subsystem that provides storage regions to zero or more V-VOLs (made up of one or more LDEVs). SP-VOL (secondary-primary volume) The volume located in the middle of a cascade structure, when a cascade structure is used by the volume replication functionality of a storage system. Indicates the secondary volume in an upper level copy pair or the primary volume in a lower level copy pair.
on a volume means that the data can be restored, even if the primary volume has been damaged or destroyed. For more information, see the Business Copy manuals. Continuous Access Journal Software that asynchronously duplicates multiple volumes between storage systems. Continuous Access Journal temporarily stores differential data on a journal volume and then duplicates the data.
Index A access control users and permissions, 83 accounts adding users, 87 automatic locking, 351 changing passwords, 335, 341 locking, 342 removing users, 337, 338 unlocking, 343 advanced options force-split, 235 swap, 235 takeover, 234 takeover-recovery (recreate), 235 takeover-recovery (resync), 235 agent user script, 403 alerts and volume switching, 240 automarking, disabling, 159, 327 changing, 326 completion, 128 conditions for, 127 copy license usage threshold, 128 copy pair status, 128 deleting, 327
C C/T delta, 283, 423 alert settings, 127 checking for each copy group, 285 exporting history, 425 cache, 124 candidate volumes, 121, 124 capacity, 121, 151, 301 expanding journal group, 316 licensed, 330 cascade configuration defining, 167 limitations, 167 permitted topologies, 165 Change Pair Status Wizard about, 226 advanced options, 233 basic options, 233 checkpoint files, 382 class, 164 CLI copy pair status, 257 refreshing configuration information, 264 command device adding, 116 defined, 114 deleting,
copy pair about, 147, 194 add to workflow, 181 and copy groups, 131 associated with a task, 295 checking, 275 checking (specific volume), 274 checking configuration definitions, 273 checking, about, 272 configuration definitions, 149 copy groups belonging to, 298 deleting related pairs, 312 editing, 185 monitoring, 276 monitoring (alerts), 277 prerequisites for mainframe, 181 refresh interval, 138 refreshing manually (My Copy Groups), 262 refreshing status, 257 saving, 177 states, 212 status, 205, 217 statu
drmdbimport command, 413 drmdevctl command, 413 drmexcat command, 413 drmumount command, 412 E Edit Group window, 174, 188 email, 277, 323 emergency license key, 329, 330 emulation type, 301 event log about, 419 data retention, 138, 139 exporting, 425 viewing list of files, 420 exauth.
information sources about, 55 adding, 55 editing, 361 registering, 55 removing, 363 viewing, 361 information stores, 418 restoring, 392 IP address, 57, 58, 300, 361, 363, 451 IPv6, 37, 58, 363 J JNLG, 125, 126, 315, 426 expanding journal group capacity, 316 journal groups about, 122 adding, 126 deleting, 315 editing, 315 expanding capacity, 316 journal volume usage, 426 wizard, 125 journal usage exporting, 426 exporting for each copy group, 426 K KAVN00123-I, 138 KAVN00124-I, 138 KAVN00126-I, 138 KAVN0012
O open systems configurations not supported, 464 operation mode changing, 430 viewing, 430 P P-VOL, 147 P9000 mainframe agent adding an instance, 58 editing an instance, 363, 365 sample configurations, 24 P9000 RAID Manager, 23 command devices, 114 pair configuration association, 185 copy group requirements, 158 creating, 154 deleting, 191 editing by associating, 182 prerequisites (mainframe), 152 unsupported, mainframe, 165, 464 wizard, about, 143 Pair Configuration Wizard launching, 144 unsupported confi
prefixes belonging to a host (mainframe), 301 multiple (mainframe), 453 viewing (mainframe), 276 prerequisite tasks, 168 primary host, 175 R RADIUS, 83, 344, 345 RCU remote paths, 117 Setting up Remote Paths, 117 Read disable option, 33 recovery operations, 233 scenarios, 236 Recovery Point/Time Objectives (RPO/RTO), 21 refresh configuration information, 264 copy group, 232 for each information source, 262 for each pair management server, 263 for each volume, 261 host, 261 interval, 137, 139, 262, 268 inte
RPO, 21 RTO, 21 S S-VOL, 147 schedule about tasks, 168 copy pair configuration definitions, 149 Pair Configuration Wizard, 143 Scheduling Tasks, 171 task execution, modifying, 171 tasks, editing, 171 security user passwords, changing, 335, 341 users and permissions, 83 warning banner, 353 server.agent.rm.cuLdevForm parameter, 150 server.agent.rm.exclusion.instance, 159 server.agent.rm.
tasks associated and prerequisite, 168 canceling, 173 deleting, 173 editing, 171 list, 173 scheduling, 171 status, 169 technical support HP, 433 temporary license key, 329, 419 THP, 119 transaction logs, 382, 389, 401 transaction replication, 414 trusted, 437 U unlock user accounts, 343 unmanaged resources, 89 unpaired LUNs/DEVNs, 144, 154, 297, 304 unsupported configurations, 165, 464 URL, 437 usage rate, 121 user roles about, 84 and permissions, 86 and wizards, 86 changing, 336 users adding, 87 adding to
wizards Add Command Devices, 116 and user roles, 86 Change Pair Status, 226 Create Alert Settings, 129 Create Journal Group, 124 Create Pool, 121 Create Remote Path, 118 Create V-VOL, 112 Pair Configuration, 143, 144 pair management, 143 workflows creating, 168 deleting, 179 editing, 178 viewing, 178 write delay time, 271, 283, 285, 419 performance monitoring, 283 write snapshot, 119, 151, 283, 284 482
