HP StorageWorks P9000 Replication Manager Software User Guide Part number: TB584-96023 Eighth edition: April 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 ............
Setting up information sources ........................................................... 51 About information sources .......................................................................................................... Registering information sources ................................................................................................... Registering information sources workflow ...............................................................................
About user roles and wizards ............................................................................................... Adding users ..................................................................................................................... Changing user permissions .................................................................................................. Setting up resource groups ........................................................................................................
Creating a remote path ..................................................................................................... Setting up pool volumes ........................................................................................................... About pool volumes .......................................................................................................... Storage system types and volume requirements (pools) ..........................................................
Create copy pair workflow ................................................................................................ About copy pair configuration definitions ............................................................................ About configuration definition file formats ..................................................................... About creating copy pair configuration definitions ................................................................ Copy pair configuration conditions .....
Confirming distribution hosts .............................................................................................. Creating and managing workflows ........................................................................................... About workflows .............................................................................................................. Saving workflows .............................................................................................................
Alert settings and volume switching .............................................................................. Advanced operations and corresponding P9000 RAID Manager commands ........................... Monitoring and managing storage systems using virtual command devices ..................................... About virtual command devices .......................................................................................... Prerequisites for virtual command device configurations ..................
Monitoring pair status using refresh settings ......................................................................... Checking the copy pair status ..................................................................................... About copy pair status checks ..................................................................................... Copy pair status check workflow ..................................................................................
Viewing storage system information (mainframe systems) .............................................................. 292 Viewing storage system information (open systems) ...................................................................... 293 Viewing information about LDKCs belonging to a storage system (mainframe systems) ...................... 293 14 Managing My Copy Groups ......................................................... 295 My Copy Groups management functions ..............................
Testing alert settings ................................................................................................................ Editing alert settings ................................................................................................................ Marking alerts as completed .................................................................................................... Deleting alert settings .......................................................................................
Viewing a preview of the warning banner .................................................................................. 340 Editing a warning banner ........................................................................................................ 341 Deleting a warning banner ...................................................................................................... 341 21 Managing resource groups ...........................................................
About the Restore Replica Wizard ...................................................................................... Restoring the latest application replica (simple restore) .......................................................... Restoring an application replica from the Replica History ....................................................... Restoring an SQL Server replica to a remote site ...................................................................
Subscription service .......................................................................................................... Documentation feedback ................................................................................................... Related information ................................................................................................................. Product references ............................................................................................................
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 Parameters for backup server calculations .................................................................. 63 2 User roles .............................................................................................................. 81 3 Pair definition and replica operations ........................................................................ 81 4 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. NOTE: If Replication Manager is installed without a license (or the existing license expires), only basic pair configuration functions will be available. This mode of operation provides key functions in support of Device Manager Server software. For more information, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software User Guide.
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. Related topics • Understanding the console layout, page 37 Architecture and components Replication Manager works in conjunction with programs such as Device Manager, HP StorageWorks P9000 for Business Continuity Manager Software and P9000 mainframe agent.
• 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. Installing Application Agent on both servers allows Replication Manager to create and restore replicas between the primary volume on the database server and the secondary volume on the backup server. • Storage system: An external storage device (HP StorageWorks XP disk array storage system) connected to a host.
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 StorageWorks 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 prerequisite environment for pair management. It also includes quick references to typical operations performed using Replication Manager. The following topics are included in this chapter: Initial setup After Replication Manager has been installed on a management server, you must configure initial settings needed to begin Replication Manager operations.
• The primary and secondary volumes are recognized individually from the hosts. • The serial numbers for all storage systems managed by Device Manager are unique. TIP: For open systems, Replication Manager acquires configuration information maintained by Device Manager servers that function as information sources.
• If replicating datasets between sites, allocate the same name of the datasets to these sites • If route lists and command devices are managed with BCM, allocate datasets of BCM configuration files The following BCM setup operations need to be performed: • Identify DADIDs and prefixes used by Replication Manager and specify them as initialization parameters for BCM Agent • Set up route lists and command devices to achieve either of the following: • To retrieve or monitor C/T Delta with Replication Manager
Confirming the prerequisite environment The following conditions need to be met before Replication Manager can be used. For more information, see HP StorageWorks 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 4, page 51 This module discusses how to register information sources in Replication Manager. Chapter 5, page 67 This module discusses how to perform volume discovery, which is a prerequisite for defining and managing copy pairs. Chapter 6, page 79 This module discusses how to specify user account settings and permissions to restrict the scope of operations allowed for each user.
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 427 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: Allows you to check alerts or edit alert settings. Alerts 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 the Help button 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 430 or “Display formats used when no pertinent information is available” on page 443.
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 IP Address 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 277 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 49
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 StorageWorks 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. 2. Prepare the information that is necessary for adding a Device Manager server as an information source. Ensure that you have the following Device Manager server information: • 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 55 first.
6. Click the OK button to register the instance of HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent. A confirmation dialog box with information about the new instance is displayed. 7. Review the information and click the Confirm button. Upon successful registration, a completion dialog box is displayed. 8. Click the Close button to finish registration.
Replication Manager version 6.1 (6.1) 6.2 (6.2) P9000 for Business Continuity Manager Software version 6.3 (P9000 mainframe agent version) 6.4 (6.3) (6.4) 6.5 (7.0) 6.6.0 (7.1.0) 6.1 6.2 6.3 6.4 7.0 7.0.1 7.1.0 1 2 2, 3 2, 3, 4 2, 3, 4, 5 2, 3, 4, 5 2, 3, 4, 5 1 1 3 3, 4 3, 4, 5 3, 4, 5 3, 4, 5 1 1 1 4 4, 5 4, 5 4, 5 1 1 1 1 5 5 5 1 1 1 1 1 1 6 1 1 1 1 1 1 1 Legend: 1. 2. No restrictions.
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.
5. Specify the Application Agent information you prepared in step 1. TIP: When you add multiple information sources at one time, you can quickly complete the registration process by deferring the acquisition of configuration information from the instances of Application Agent. To do this, clear the Acquire the application configuration managed by the Application Agent during the registration check box. 6. Click OK to register the instance of Application Agent.
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. You can also set the following options: 6.
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.
Related topics • Adding an instance of Application Agent, page 57 • Setting Application Agent options, page 58 • Removing instances of Application Agent, page 353 User Guide 65
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.
• Restrictions for adding volume ranges for volume scans, page 71 • Deleting a volume range from a volume range list, page 71 • Restrictions for deleting volume ranges, page 71 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.
Restrictions for adding volume ranges for volume scans The following are restrictions when volume ranges are added: • 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.
Performing a volume scan To perform a volume scan: 1. Display the list of disk configuration definition files managed by Replication Manager. For details, see “Displaying disk configuration definition files” on page 75. 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 70. 4. Select the target hosts for disk list distribution.
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. TIP: Uncheck this check box when you want to skip disk list distribution when creating the disk list. 7. Click the OK button.
Editing disk configuration definition files You can edit a disk configuration definition file by adding or deleting volume ranges in the volume range list. You can also select or deselect target hosts for disk list distribution. 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.
2. Expand the object tree, and then select a host under Hosts. The host-name subwindow appears. 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 77 • Reviewing unpaired LDEV list, page 78 Reviewing paired LDEV list To review the paired LDEV list: 1.
• Reviewing paired DEVN list, page 76 • Reviewing paired LDEV list, page 77 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.
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.
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 2 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.
TIP: If the association between a logged in user and a resource group is changed, the change is applied the next time the user logs in. Device Manager versus Replication Manager resource groups As of 7.1.0, Device Manager and Replication Manager use separate resource groups. If you have not registered a license for Replication Manager and assigned user permissions, only resource groups that can be referenced according to the settings of Device Manager are eligible for display or modification.
Example of resource groups The following figure shows an example of resource groups. 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. For details on how to add resources in the new resource group, see the following: • Adding hosts to a resource group, page 88 • Creating resource groups, page 87 Related topics • About resource groups, page 85 Adding hosts to a resource group You can add hosts as resources to existing resource groups.
To add storage systems to 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 a resource group under Resource Groups. The resource-group-name subwindow appears. 3. On the Storage Systems page, click Add Storage Systems. The Add Storage Systems - resource-group-name dialog box appears. 4. Select the storage systems you want to add, and then add them.
Relationships between resource groups and user permissions The following figure shows the relationships between resource groups and user permissions. 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, which is the resource group in which all hosts are automatically registered.
2. Expand the object tree, and then select a resource group under Resource Groups. The resource-group-name subwindow appears. 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.
Setting up authorities
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.
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. If the copy groups are arranged in a row The secondary volume of the copy group displayed on the left is the primary volume of the copy group displayed 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. If a 3DC multi-target configuration is used In a 3DC multi-target configuration that uses the delta resync function, the copy group displayed on the right of the upper line branches to the right, and this copy group is displayed as being connected to the one on the lower line.
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.
• Setting up pool volumes, page 116 Storage system setup functions The following table shows the functions for setting up storage systems, 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 Resources Storage Systems Y Y Y Legend: Y: Can be executed with this permission. Prerequisite settings for replicating volumes The following figures show the task flow for specifying prerequisite settings required before replicating volumes. Flow of specifying the settings required before replicating volumes Setting up V-VOLs Replication Manager supports creation of V-VOLs on storage system configurations.
About creating V-VOLs Replication Manager supports creation of V-VOLs on storage system configurations. This function is only supported for XP24000/XP20000 or HP StorageWorks P9500 storage systems. After creating V-VOLs, it is necessary to assign LUNs to them in order to create copy pairs. Assignment of LUNs should be done using Device Manager. Replication Manager provides a wizard for creating V-VOLs and associating them with volume pools.
Permitted V-VOL operations based on CVS installation The operations that can be performed on V-VOLs depend on whether CVS (Open Volume Management) has been installed. V-VOLs can be added or deleted from an existing V-VOL group only when CVS has been installed. The following table lists the conditions and restrictions when creating V-VOL groups: NOTE: The maximum number of V-VOLs on an HP StorageWorks P9500 storage system are not restricted based on CVS installation.
Related topics • About creating V-VOLs, page 108 • About the Create V-VOL Wizard, page 109 Creating V-VOLs To create V-VOLs: 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. Under the Pools tab, display the V-VOLs tab. 5. Click Create V-VOLs.
15. On the 3. Setup V-VOLs page, assign LDEV numbers to the V-VOLs by selecting the Specify start number of V-VOL(s) check box and specifying the start numbers of CU and LDEV. If the Specify start number of V-VOL(s) check box is not selected, the CU:LDEV of the V-VOLs will be automatically assigned during the creation. If the specified number is an LDEV number being used as a non-representative LDEV of a LUSE in Device Manager, V-VOL creation may fail. 16. Click Next. The 4. Confirm page is displayed. 17.
Related topics • About Add Command Devices Wizard, page 113 About command devices A command device is necessary in order for P9000 RAID Manager (a prerequisite product for Replication Manager) to communicate with storage systems. Replication Manager allows you to set up command devices in open systems if the storage system type is XP12000/XP10000/SVS200, or XP24000/XP20000.
NOTE: To link Replication Manager with the Device Manager agent running on a VMware ESX 4.x or ESXi 4.x guest OS, make sure that the Device Manager Agent and the Device Manager are version 7.0.1 or later. About Add Command Devices Wizard Replication Manager includes an Add Command Devices Wizard for registering volumes as command devices.
5. Add command devices as instructed by the wizard. The added command devices are displayed in the Open subwindow.
The following table lists whether you can specify a remote path depending on a combination of the local and remote storage systems.
Creating a remote path To create a remote path: 1. From the Explorer menu, select 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. 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.
• An open system is being used. • The storage system type is XP12000/XP10000/SVS200 or XP24000/XP20000. • 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 117.
Requirement XP12000/ XP10000/ SVS200 XP24000/ XP20000/ HP P9500 Encrypted and non-encrypted volumes cannot coexist N Y Legend: Y: This requirement applies. N: This requirement does not apply.
3. Click the Open link. The Open subwindow appears. 4. On the Pools page, click Create Pool. The Create Pool Wizard starts. 5. Create a pool as instructed by the wizard. The added pool is displayed in the Open subwindow. Related topics • About pool volumes, page 116 • Storage system types and volume requirements (pools), page 117 • Pool usage threshold values, page 274 Setting up journal groups Continuous Access Journal uses journal volumes as volume copy buffers.
Storage system types and volume requirements (journal) Volumes that meet the requirements listed here are displayed as candidate volumes in Replication Manager.
N: This requirement does not apply.
Speed of Line* 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 122 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.
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.
Setting up storage systems
9 Customizing monitoring parameters The best practice is to customize Replication Manager before starting operations. 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.
Copy pair status An alert is sent when a copy pair achieves a specified status. This condition can be specified for an individual copy pair or for a copy group. For example, you can specify this 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.
Alert completion Alerts are automatically marked as Completed according to the criteria in the following table. Table 6 Alert completion conditions Monitored condition Completion criteria • Pool usage for each pool • Journal usage for each journal group • License usage When current usage is less than or equal to the usage (%) specified for the alert.
TIP: Note the following: • The best practice is to configure alert settings before starting Replication Manager operations either during initial setup or during re-configuration. If you set alerts or edit alert settings, HP recommends that you perform a test before starting operation to make sure that the alerts are sent normally. See “Testing alert settings” on page 313 for more information.
Launching the Create Alert Setting Wizard You can launch the Create Alert Setting Wizard from the following locations on the web interface depending on the monitored target: • • • • Copy Groups tab Pools tab JNLGs tab Copy Licenses tab To launch the Create Alert Setting Wizard, click Create Alerts in the Application area.
3. To select copy groups from a list, select the check boxes of the copy groups for which you want to set monitoring conditions and click Create Alerts. If the information about copy groups for which you want to set monitoring conditions is already displayed, simply click Create Alerts. The Create Alert Setting Wizard starts with the 1. Introduction page displayed. If you select the Don’t show this message again check box, the 1.
3. Select the check boxes of the copy pairs for which you want to set monitoring conditions, and then click Create Alerts. The Create Alert Setting Wizard starts with the 1. Introduction page displayed. If you select the Don’t show this message again check box, the 1. Introduction page will not be displayed when the Create Alert Setting Wizard starts subsequently. 4. Read the wizard page, and then click Next. The 2. Select Monitoring Type page appears. 5.
3. To select copy groups from a list, select the check boxes of the copy groups where you want to set monitoring conditions, and click Create Alerts. If the information about copy groups where you want to set monitoring conditions is already displayed, just click Create Alerts. The Create Alert Setting Wizard starts with the 1. Introduction page displayed. If you select the Don’t show this message again check box, the 1.
5. On the JNLGs page, select the check boxes of the journal groups where you want to set monitoring conditions, and then click Create Alerts. The Create Alert Setting Wizard starts with the 1. Introduction page displayed. If you select the Don’t show this message again check box, the 1. Introduction page is not displayed when the Create Alert Setting Wizard starts subsequently. 6. Read the wizard page, and then click Next. The 2. Select Monitoring Type page appears. 7.
5. On the Pools page, select the check boxes of the pools where you want to set monitoring conditions, and then click Create Alerts. The Create Alert Setting Wizard starts with the 1. Introduction page displayed. If you select the Don’t show this message again check box, the 1. Introduction page is not displayed when the Create Alert Setting Wizard starts subsequently. 6. Read the wizard page, and then click Next. The 2. Select Monitoring Type page appears. 7.
5. Under the Copy Licenses tab, select the check boxes of the copy types where you want to set monitoring conditions, and then click Create Alerts. The Create Alert Setting Wizard starts with the 1. Introduction page displayed. If you select the Don’t show this message again check box, the 1. Introduction page is not displayed when the Create Alert Setting Wizard starts subsequently. 6. Read the wizard page, and then click Next. The 2. Select Monitoring Type page appears. 7.
8. Confirm the settings that will be applied, and then click Confirm. The 6. Finish page appears. 9. Click Finish. The settings specified in the wizard are registered in the list of alert settings. To view this list, from the Explorer menu, choose Alerts and then Alerts.
2. Use the message IDs in the event log to identify the date and time when an individual pair management server (host) started or ended the pair status collection. The following table lists message IDs that are output when copy pair status collection starts or ends: Message ID Type of system When the pair status collection is started When the pair status collection is ended Open system KAVN00123-I KAVN00124-I Mainframe system KAVN00126-I KAVN00127-I 3.
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 not expired. In this case, take either of the following actions: • Disable the retention of unnecessary data, or shorten the retention period. • Lengthen the refresh interval for management information.
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 80 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.
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. The wizard can be launched from this list to delete or modify existing volume pairs.
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. Selecting an Unpaired LU • If the LU is an internal volume to which an external volume is mapped, the host I/O suppression mode is enabled. • Replication Manager is not aware of the pair management server that is identifying the associated subsystem command device.
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 144 About copy pair configuration definitions, page 146 About creating copy pair configuration definitions, page 147 Creating pairs and pair groups, page 151 Editing pair names, page 152 About filtering candidate volumes, page 153 Selecting multiple candidate volumes, page 153 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, when such a configuration is used by the storage system's volume replication functionality. 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 149. 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.
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 The storage system satisfies both the following conditions: Continuous Access Synchronous, Continuous Access Journal 1. The storage system must be different from the primary storage system. 2. The storage system must be either XP12000/XP10000/SVS200, XP24000/XP20000, or HP P9500. • Volumes are stored using the same prefix, DADID, and host. • Volumes selected do not span multiple storage systems. • Volumes must not be reserved by another workflow.
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 153. 5. Click Add. The selected volumes are assigned as secondary volumes and the defined copy pair is displayed in the Pair List pane. Repeat this operation for each pair group you create. You can click the 6.
4. If you are renaming multiple copy pairs, select a suffix start number. 5. Click Refresh. The new pair name is displayed in the Pair List pane in the Edit Pair Name dialog box. 6. Click OK. The pair name is updated in the Copy Group pane on the 3. Group Management page. Related topics • Associating pair groups with copy groups, page 158 About filtering candidate volumes When defining pairs you can specify filtering criteria to filter the list of candidate volumes for easier volume selection.
• About filtering candidate volumes, page 153 • Creating pairs and pair groups, page 151 Defining copy groups This module discusses information about copy groups and tasks for defining copy groups: • • • • • • About copy groups, page 154 About assigning CTGID/JNLGID for copy pairs, page 154 Configuring open and mainframe consistency groups, page 155 About HORCM instances, page 156 Creating copy groups, page 156 Associating pair groups with copy groups, page 158 About copy groups A copy group consists of
a pair group to a copy group). In order to change a CTGID/JNLGID, it is necessary to delete and recreate the copy pair. TIP: Take note of the following: • CTGID/JNLGIDs are independent among storage systems. Replication Manager assigns a new ID on the storage system if the storage system of the new copy group is different from that of the original copy groups.
When configuring existing pairs 1. Confirm the mainframe and open Cnt Ac-S pairs share the same CTGID. 2. Open the Pair Configuration Wizard for the mainframe pairs and specify the Enable Open/MF CTG option in the Edit Group dialog box (3. Group Management page). 3. Using the Change Pair Status Wizard, split the mainframe Cnt Ac-S pairs and then resync them with the Assign CTG option enabled (3. Select Pair Operation page).
To create a copy group: 1. Perform the following steps if you are creating a copy pair configuration definition from a saved workflow: 1. 2. From the Explorer menu, choose Tasks and then choose Workflows. A list of saved workflows is displayed. 2. Select a saved workflow and click the Edit Workflow button. On the 3. Group Management page of the Pair Configuration Wizard, select a pair group, and then click the Create Group button. The Create Group dialog box appears. 3.
Associating pair groups with copy groups To associate pair groups with a copy group: 1. If you are creating a copy pair configuration definition from a saved workflow, perform the following: 1. From the Explorer menu, choose Tasks and then choose Workflows. A list of saved workflows is displayed. 2. 2. Select a saved workflow and click Edit Workflow. On the 3. Group Management page of the Pair Configuration Wizard, select the pair group to be associated with the copy group. 3.
Creating a container with multiple copy groups (mainframe systems) To create a container with multiple copy groups: 1. Select a volume without a copy pair configuration and launch the Pair Configuration Wizard. For details on how to launch the Pair Configuration Wizard, see “Launching the Pair Configuration Wizard” on page 142. 2. Create a pair group and associate it with a copy group. When performing the association, specify the consistency group ID and journal group ID.
Defining multi-target and cascade configurations This module discusses information about multi-target and cascade configurations and procedures for creating them.
Requirements for the copy type when creating a multi-target configuration 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 Business Copy Y N Y Y Y Snapshot N Y Y Y Y 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 grou
Permitted topologies for cascade and multi-target configurations The following restrictions apply when creating cascade or multi-target configurations or deleting copy groups in cascade or multi-target configurations: • When creating a cascade configuration, it is necessary to first create a higher-level copy group.
Unsupported configuration The cascade destination contains multiple copy groups. Requirement for configuration Alternative configuration to implement requirement To create a backup of only some volumes. Create CTGs in the cascade source according to the cascade destination copy groups. Pairs in the cascade source must belong to any CTG.
2. To create a multi-target configuration, select a primary volume, and then click the Add Group button. To create a cascade configuration, select a secondary volume, and then click the Add Group button. 3. For each pair group, define a list of copy pairs that you want to include in the pair group. 4. On the 3. Group Management page, create a copy group and assign a pair group to the copy group. 5. Repeat the operations for creating a copy group and assigning a pair group to the copy group.
units. Tasks are created automatically when you set up a copy pair or copy group using the wizard-based GUI. For example, if you create copy groups A and B, which constitute a multi-target configuration, and copy groups C and D, which constitute a cascade configuration, Replication Manager generates two tasks, each on a copy group basis, for each workflow.
• Executing: Indicates that the task is executing. • Cancel: Indicates that the task was cancelled. • Failure: Indicates that the task failed. When you select Failure, an error window appears. Read the message in the error window. • Success: Indicates that the task was successful. • Warning: Indicates that the system timed out while waiting for the task to finish processing. When you select Warning, an error window appears. Read the message in the error window.
About task types (mainframe systems) The following are task types displayed for mainframe systems: • modify file (create): Adds a pair definition to a copy group definition file. This type of task only creates or edits a copy group definition file. It does not create the defined pair. • modify file (delete): Deletes a pair from a copy group definition file. This type of task only deletes or edits a copy group definition file. It does not delete the defined pair.
2. To edit a single task, click the associated icon. To edit multiple tasks, select the check box of each task you want to edit and click Edit Tasks. The Edit Task(s) dialog box appears. 3. Specify the following options on the Task Options tab: Execution Request Time Modify Pair Configuration File Only (Do not create Pair) check box 4. Executes the task at a specified date and time. Specifies whether to create a pair or only modify the P9000 RAID Manager configuration definition file.
3. Enable the Modify Pair Configuration File Only (Do not create Pair) option if you do not wish to create the pairs. This option is always enabled during mainframe pair configuration since only pair configuration definition can be performed by Replication Manager. Mainframe copy pairs are not created by Replication Manager upon completion of pair configuration definition. 4.
2. Select the check boxes of the tasks you want to cancel, and then click Cancel Tasks. The Cancel Tasks dialog box appears. 3. Confirm the tasks that will be canceled, and then cancel them. The information in the Status and Execution Request Time columns for the tasks displayed in the Tasks subwindow is refreshed.
configuration, Replication Manager distributes the copy group list created during pair configuration to these distribution targets. The following two types of copy group definition file distribution are possible: • Normal distribution: Distribution of copy group definition file from the user-selected BCM or P9000 mainframe agent host to the target BCM or P9000 mainframe agent host. The copy group definition file is distributed to all hosts that satisfy the distribution prerequisites.
• The primary and secondary DADIDs defined in the copy group definition file at the origin must be defined in the copy group definition file at the destination. • The disk configuration definition files must already be distributed to the distribution destination host before the copy group definition files can be distributed. • The distribution destination BCM or P9000 mainframe agent host has required access permissions.
CAUTION: There are no recovery measures available to recover the latest copy group definition files once all the copies of the files have been replaced with old files. This situation can be avoided by excluding the primary hosts of any old copy group definition files from being the target primary host.
TIP: For situations such as when storage system resources and host applications are managed by different administrators, the work status can be saved as a workflow at any point during copy pair creation 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.
Related topics • About workflows, page 173 Editing workflows You can edit a workflow that was temporarily saved before it was completed in the Pair Configuration Wizard. When editing an unfinished workflow, you can restart the Pair Configuration Wizard from the step when the workflow was saved. You can also edit a workflow after pair configuration is completed (that is, a workflow for which Finish is displayed in Steps).
2. Select the check boxes of the workflows you want to delete, and then click Delete Workflows. 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.
TIP: You cannot edit user-specified parameters such as copy group name, port number and instance number after the copy pair configuration definitions are created using the Pair Configuration Wizard. If these parameters need to be edited, it is necessary to manually modify the copy pair configuration definitions outside of Replication Manager. A number of conditions can affect the copy pair configuration definition settings.
• The startup mode values of BCM Agent initialization parameters must be set to EDIT (default value is MONITOR). If a configuration definition is updated or copy pair status is changed when the startup mode value is MONITOR, a BCM Agent error will occur. TIP: If you want to use an IPv6 connection or SSL communication between Replication Manager and BCM, IHS must be set up. For details about setting up IHS, refer to the HP StorageWorks P9000 for Business Continuity Manager Software documentation.
Editing copy groups by associating new pair groups To edit an existing copy group by associating new pair groups: 1. In the Hosts view, Storage Systems view, or Pair Configurations view, display information about the copy group for which you want to edit the copy pair configuration definition. For details on the Hosts view, Storage Systems view, and Pair Configurations view, see the following: 2.
13. To view the list of tasks, from the Explorer menu, choose Tasks and then Tasks. A list of tasks is displayed in the Tasks subwindow. Related topics • Associating pair groups with copy groups, page 158 Conditions for copy types to be displayed (open systems) The copy types displayed in the Copy Type drop-down list differ depending on the storage system type or the copy types set to existing copy groups.
2. 3. 4. Displayed if a secondary volume is selected. This information is not displayed when a primary volume is selected. This copy type is displayed when the selected volume is the primary volume, and is not displayed when the selected volume is the secondary volume. Not supported on HP Storage Works P9500 Disk Array.
2. In the displayed subwindow, select a copy group. Alternatively, make sure that copy group information is displayed, and then click the Pair Management button. The Pair Configuration Wizard starts with the 1. Introduction page displayed. 3. Read the wizard page, and then click the Next button. The 2. Pair Association page appears. The copy topology (configuration of the related copy groups) to which the copy group belongs is displayed in the Copy Topology pane. 4. On the 2.
To specify a copy type for a copy group: 1. In the hosts view or pair configurations view, display information about the copy group for which you want to edit the copy type. For details on displaying copy group information, see the following: 2. • Viewing copy group information in the Hosts view (open systems), page 288 • Viewing copy group information in the Pair Configurations view (open systems), page 287 Select a copy group with pairs in simplex status. 3.
To edit copy group settings TIP: If you want to edit copy group settings for a new copy group (during pair configuration), start at step 5. 1. In the hosts view or pair configurations view, display information about the copy group for which you want to edit copy group settings. For details on displaying copy groups, see the following: 2.
Even if the copy group settings are not edited when creating copy groups (using the relevant configuration definition file), the inherited options are still used for copy group configuration. The only exception when the inherited options are not used is for copy groups of copy type Cnt Ac-J for which the EXCTG ID, Super DKC or ArbCmdDevice option values are specified.
Copy type Option name Displayed items Default value Protect Mode Permit, Protect Protect Preset Mode No value, Normal, Cnt Ac-J. This is displayed only if the selected copy group has CTGID. No value Business Copy Legend: * : By default the check box is not checked. However if the user is editing an already existing group, then the state of the check box is the same as that while the group is saved or created. This option applies only to XP24000/XP20000 storage systems.
To delete a copy group: 1. In the Hosts view, Storage Systems view, or Pair Configurations view, display information about the copy group for which you want to edit a copy pair configuration definition. For details on the Hosts view, Storage Systems view, and Pair Configurations view, see the following: 2.
TIP: In mainframe systems, you cannot delete all pairs that are in an existing copy group. This restriction prevents deletion of copy groups with distribution relationships. For details of conditions that disrupt copy group linkage, see “Conditions that disrupt copy group distribution relationships” on page 172. To delete copy pairs from a copy group: 1.
Importing existing configuration definition files To import existing copy group configuration definition files: 1. Confirm the following prerequisites: 1. 2. 2. Ensure the file specification format is one of the Device Manager agent supported formats. Verify that the parameters in the configuration definition file satisfy the settings restrictions for each parameter.
• When new copy pairs are added to a pre-existing configuration definition file that has mixed formats, Replication Manager determines the format for the new copy pairs using the server.agent.rm.pairDefinitionForm property in the Device Manager agent server.properties file. The preexisting format parameters are left as is. After modification, both HORCM_LDEV and HORCM_DEV formats are supported in the same configuration definition file.
Copy pair operation options that can be set for each copy type Copy type Copy pair operation create Continuous Access Synchronous Continuous Access Asynchronous or Continuous Access Journal Business Copy Snapshot Copy Pace Y Y Y Y Fence Level Y Y N N JNLG ID(P) N Y1 N N 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
2. When performing create of a snapshot, the Split option becomes deactivated (grayed out) and is automatically applied by default. Option items for copy pair operations (mainframe systems) The option items for a copy pair operation differ depending on the copy type. The following table shows the option items that can be set for each copy type.
Copy Type Copy Pair Operation Option Values delete Cnt Ac-A Cnt Ac-J Description BC If the value is On, a CTG is applied to the target pairs.
Display details of direction option and synchronization option Operation target is copy group Operation target is copy pair or C/T Group Direction Synchronization Direction Synchronization - Copy type Continuous Access Synchronous Forward(*), Reverse - Present copy direction (#) (Forward or Reverse) (not activated)(*) Continuous Access Asynchronous Blank(*), Forward, Reverse Blank, Flush(*), Purge Blank (not activated)(*) Flush(*), Purge Continuous Access Journal Blank(*), Forward, Reverse
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 split The copy direction of the pair when re-synchronization is performed. Forward, Reverse Note: This option cannot be specified if the operation target is a copy pair or a C/T Group.
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 off 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.
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 8.
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.
Copy pair state Business Copy Continuous Access Synchronous Continuous Access Asynchronous Error (HOLDER) -- -- -- resync resync restore restore delete delete resync resync resync restore restore restore delete delete delete Split (SW) -- -- -- Split (HOLD)* -- -- -- resync resync resync restore restore restore delete delete delete Deleting -- -- -- Suspending -- -- -- split split split delete delete delete -- -- split split split delete delete de
--: Indicates that the copy pair status cannot be changed. *: This is the copy pair state when a 3DC multi-target configuration is used. 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 Continuous Access Journal n/a -- -- The same primary volume is shared1 The same primary volume is not shared2 split split delete delete split split split delete delete delete split split split delete delete delete split split split delete delete delete Simplex -- -- -- create Unknown -- -- -- -- Copy pair state Copying (Reverse) Pair (Full) Pair (PAIR or PFUL) Pair -- -- -- Legend: 1. 2. 3.
Pair statuses to which the pair status can be changed (when the target is a single or multiple copy pairs) Snapshot Copy pair state Business Copy Continuous Access Synchronous Continuous Access Asynchronous Error (PSUE) resync restore delete resync restore delete Error (HOLDER)3 -- Error in LUSE The Same Primary Volume Is Shared1 The Same Primary Volume Is Not Shared2 Continuous Access Journal n/a delete resync delete resync restore delete resync delete -- -- -- -- -- -- -- -- resy
delete: Indicates that the copy pair can be dissolved. split: Indicates that the copy pair can be split. create: Indicates that a copy pair can be created. --: Indicates that the copy pair status cannot be changed. TIP: If copy pairs with types that differ are selected, you cannot change the copy status. 1. 2. 3. This column lists the selectable copy pair statuses when the copy group to which the selected copy pair belongs contains copy pairs that have the same primary volume.
Details of copy group or copy pair statuses Business Copy Continuous Access Synchronous Continuous Access Asynchronous Continuous Access Journal Copying (Resync-R) Delete Delete Delete Delete Split (HOLD) - - - Error (HOLDER) - - - Delete Split (HOLTRNS) - - - Delete Split (NODELTA) - - - Resync Delete Resync Delete TIP: The operation that can be selected is determined based on the copy directions of the definition and entity and on the pair status.
About Change Pair Status Wizard Replication Manager includes a Change Pair Status Wizard for changing the status of copy pairs. You can use this wizard to change the copy pair status on a copy pair or copy group basis. The wizard displays the available operations and options in drop-down lists based on the copy type and copy pair status. TIP: Note the following: • When the wizard finishes processing, a task is automatically registered for each copy group.
To launch the Change Pair Status Wizard using the icon: 1. 2. Display the information about the volume included in a copy pair whose status you want to change or display the information about the host or configuration definition file where you want to change the status of copy pairs. Click the icon of the copy pair whose pair status you want to change. To launch the Change Pair Status Wizard using the Change Pair Status button: 1.
6. Set the operation (Pair Operation) and options to change the pair status and click Next. The 4. 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 then click the Next button. 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 the Next button. The 3. Select Pair Operation page appears. 5.
• When performing operations on EXCTGs (mainframe systems), page 201 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 287 or “Viewing information about copy groups belonging to a copy pair configuration definition” on page 286. 2.
6. Set the operation (Pair Operation) and options to change the pair status, and then click the Next button. The 4. 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.
5. Confirm whether the pair is in Pair status. 6. On the Tasks window, verify task has completed by checking if the task status is Success. Related topics • About copy pair status, page 201 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 11 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 5 Takeover workflow Figure 6 Takeback workflow 232 Managing pair life cycle
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 7 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 Operation takeover-recovery (recreate) P9000 RAID Manager Description Option Command Option None n/a Copy Pace -c size Fence Level Recovers the P-VOL and S-VOL to the Pair(PAIR) status when the P-VOL is in the Simplex(SMPL) status and the S-VOL is in the Split(SSWS) status. 1. pairsplit -R 2. pairsplit -S 3. paircreate Note: Options in Option column apply to paircreate only.
The following figure shows an example of a configuration in which SVPs are used as virtual command devices. Because this configuration eliminates the need for connecting a command device to the pair management server, you can install Device Manager Agent and P9000 RAID Manager on the management server, allowing it to double as a pair management server.
Figure 9 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 257. 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 257. 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.
Copy group information is acquired using SVPs using the instance of Device Manager agent and P9000 RAID Manager on the management server. See “Setting up an SVP as a virtual command device ” on page 238 for more information. NOTE: Although copy groups defined in storage can be managed through virtual command devices, use of a Virtual Command Device server is not supported. Prerequisites for copy group configurations defined in storage The following requirements apply to copy groups defined in storage.
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 basis and journal volume usage on a copy group 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, since copy pairs that are not managed by pair management servers exist. In this case, copy pair information is acquired from the databases of Device Manager servers registered as information sources, after the databases have been refreshed by executing the Device Manager refresh function from Replication Manager.
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 in which all copy pairs are managed by pair management servers, specify the refresh settings to 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, the configuration definition file does not exist.
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. From this point, during manual refreshing, information is acquired 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 on how to display this information, see “Viewing information about copy groups belonging to a host” on page 287 or “Viewing information about copy groups belonging to a copy pair configuration definition” on page 286. 2.
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.
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 alert notification. You can get notification 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 261 • Checking copy pair configuration (perspective of specific volume), page 262 • Checking copy pair configuration (perspective of specific copy group), page 263 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 condition can be specified for an individual copy pair or for a copy group. For example, you can specify this condition for a copy group so that an alert is sent when an 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 269. • “Checking status of copy pairs for a volume in a storage system” on page 269. Related topics • Copy pair status check workflow, page 268 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.
For details on how to check performance of remote copies, see the following: • “Checking buffer usage (pools and journal groups)” on page 275. • “Checking buffer usage (sidefiles and journal volumes)” on page 275. • “Checking write delay time (C/T Delta) for each copy group” on page 273. Checking performance workflow (remote copies) The following figure shows the flow of tasks for checking the performance of remote copies.
Copy progress display Copy pair status Copy type • Business Copy • Snapshot • Continuous Access Synchronous • Continuous Access Asynchronous • Continuous Access Journal error suspend copying sync simplex CP CP or BM CP CP -- BM BM CP BM -- BM BM CP -- -- Legend: CP: Copy progress (copy pair matching rate) BM: Differential-bitmap matching rate --: Not displayed TIP: Depending on the copy pair state of the primary volume, the copy progress (copy pair matching rate) and differential-bitmap
To check the write delay time (C/T delta) for each copy group: 1. Select a host or pair management server. From the Explorer menu, select Resources and then Hosts, select Resources and then Pair Configurations, or select Shared Views and then Sites. Select the host or pair management server that contains the copy group whose C/T delta you want to check. If you have selected a host, click the Refresh Hosts button to refresh the information when necessary. 2.
Checking buffer usage (pools and journal groups) To check the usage of the buffers (pool volumes or journal volumes) for each pool or journal group: 1. Select a storage system. From the Explorer menu, either select Resources and then Storage Systems or select Shared Views and then Sites. Select the storage system that contains the copy pair whose buffer usage you want to check, and the appropriate platform (mainframe or open systems).
5. Check the detailed usage information for buffers (sidefiles and journal volumes). In the copy group summary, if you click the sidefile usage link or journal volume usage link, you can view the following types of information: Sidefile usage (Continuous Access Asynchronous): In the primary volume column, the sidefile usage is displayed on a consistency group basis.
• About aggregation rules for protection status, page 278 • Excluding objects from data protection status monitoring, page 279 About data protection status The protection status display allows quick identification of the cases shown in the table. Table 15 Protection status Status Icon Description Normal The latest replica is current (the last scheduled replica was successful). Warning The latest replica is older than expected (the last scheduled replica was unsuccessful).
About aggregation rules for protection status The Applications view consists of three levels: application (Microsoft Exchange or SQL Server), the servers running the application, and the storage groups (Exchange 2003/2007), information stores (Exchange 2010), or database instance (SQL) allocated to each server. To simplify monitoring, a series of status labels are applied to each level in the structure.
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. To avoid this situation, administrators can exclude objects from monitoring by excluding the individual information sources.
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.
Related topics • Viewing copy pair configuration definition information, page 263 Viewing a list of copy pairs associated with a task You can view the list of copy pairs associated with a task, in order 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. A list of tasks is displayed in the Tasks subwindow. 2.
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.
• List of CUs (for storage systems that do not support LDKCs) • List of journal groups • List of licenses for each copy type Related topics • Viewing storage system information (open systems), page 293 • Viewing storage system information (mainframe systems), page 292 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 cop
Viewing copy group information in the Pair Configurations view (mainframe systems) To view copy group information (mainframe systems): 1. From the Explorer menu, choose Resources and then Pair Configurations. The Pair Configurations subwindow appears. 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.
• Viewing copy group information in the Hosts view (open systems), page 288 • Viewing copy group information in the Hosts view (mainframe systems), page 288 Viewing copy group information in the Hosts view (mainframe systems) To view copy group information (mainframe 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. On the Prefixes page, select a prefix.
To view information about a pair management server: 1. From the Explorer menu, choose Resources and then Pair Configurations. The Pair Configurations subwindow appears. 2. Expand the object tree, and then select a pair management server under Pair Configurations. The information about the selected pair management server is displayed in the pair-management-server-name subwindow.
Viewing information about volumes belonging to a storage system You can display the following information about the volumes belonging to a storage system for each platform (mainframe or open systems): • Volume (LUN or DEVN) summary The LUN information (such as the mount point and capacity) or DEVN information (such as the serial number and emulation type) is displayed.
TIP: Volumes that are currently locked by a task are marked with the icon. When you put the cursor over a locked entry in the LDEV column, the following information is displayed indicating the name of the task: LU (Reserved by workflow: workflow-name) Related topics • Reviewing paired LDEV list, page 77 Viewing LDEV information To view LDEV information: 1. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 2.
Viewing LUN information in the Storage Systems view (open systems) To view LUN information: 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 LUNs page, select a LUN. The information about the selected LUN is displayed in the LUN-name subwindow.
• Viewing individual storage system information, page 285 • Viewing information about CUs belonging to a storage system (mainframe systems), page 290 Viewing storage system information (open systems) To view storage system information (open systems): 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.
2. Expand the object tree, and then select a storage system under Storage Systems. The storage-system-name subwindow appears. 3. Click the Mainframe link. The Mainframe subwindow appears. 4. On the LDKCs page, select an LDKC. The information about the selected LDKC is displayed in the LDKC-name subwindow.
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 297 • Deleting V-VOLs, page 297 • Deleting multiple V-VOLs, page 297 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 the Delete Cmd Devices button.
• About remote paths, page 114 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 about how to perform these deletions, see “Deleting tasks” on page 170 and “Deleting workflows” on page 175. • 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 117. 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 274. 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 116 • Pool usage threshold values, page 274 Managing journal groups This module describes tasks for managing journal groups: • Editing journal groups, page 303 • Deleting journal groups, page 303 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.
16 Managing sites This chapter describes tasks for managing sites: About site administration In a complex replication environment, storage systems could 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 96 • Adding storage systems to a site, page 97 • Adding pair management servers to a site, page 98 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 310 • Deleting multiple sites, page 310 Related topics • Removing hosts from a site, page 308 • Removing pair management servers from a site, page 309 • Removing storage systems from a site, page 308 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 125 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 125 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 the Delete Alerts button. 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 license key 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 317 • Viewing license information, page 318 User Guide 319
Managing licenses
19 Managing users and permissions Replication Manager provides role-based user access control capabilities to secure protection processes and recovery operations for critical data assets and mitigate the risk of unauthorized operations. To achieve stringent access control and operational efficiency, multiple users can be allocated access to functions on the basis of role in the organization.
N: Cannot be used with this permission. 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.
Viewing individual user information You can display the following information for individual users: • 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.
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. 2. • 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, page 326 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.
• About users, permissions, and roles , page 79 • Viewing a summary of user permissions, page 327 • Changing user permissions, page 84 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.
Permissions Admin (user management) permission Admin, modify, or view (Replication Manager management) permission Viewing user profiles Y Y 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.
2. Click Edit Profile. The Edit Profile - user-ID dialog box appears. 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.
• • • • About user authentication, page 332 Linking to an external authentication server, page 333 Changing the user authentication method, page 334 Using an external authorization server (authorization groups), page 334 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.
• The accounts of users who are currently logged in can be locked; however, a user cannot lock his or her own account while logged in. • 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 StorageWorks P9000 Replication Manager Software Configuration Guide.
3. In the list of users, select the check boxes of the users whose accounts you want to unlock and click Unlock Users. The Unlock Users dialog box appears. 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.
Related topics • Changing the user authentication method, page 334 Linking to an external authentication server To link to an external authentication server: 1. On the Replication 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 StorageWorks 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.
2. In the Add Groups - domain-name dialog box, register the authorization group that will use the P9000 Command View AE Suite products. 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.
3. Click Change Permission. The Change Permission - group-name dialog box appears. 4. Select the permissions to be specified for the authorization group for each application and click OK to save the settings. Deleting an authorization group To delete an authorization group: 1. In the Explorer menu, choose Administration and then Users and Permissions. 2. In the navigation area, expand the Groups object tree and select domain-name. The domain-name subwindow appears. 3.
20 Managing security This chapter describes tasks for managing security: About security settings For tighter login security, you can specify security options. Replication Manager provides security functions that allow you to perform the following: • Set password conditions to prevent users from specifying easy-to-guess passwords. • Enable automatic locking of user accounts for which successive login attempts have failed.
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 340 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 CAUTION: The display of resource group information is dependent on the presence of a Replication Manager license. See “Device Manager versus Replication Manager resource groups” on page 86 for more information. Resource groups can be managed only by users with the Admin (Replication Manager management) permission.
Permissions Function Admin Modify View Adding storage systems to a resource group Y N N Removing storage systems from a resource group Y N N Adding users to a resource group Y N N Removing users from a resource group Y N N 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.
4. Edit and update the group information. The group information displayed in the Resource Groups subwindow is refreshed. Related topics • About resource groups, page 85 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.
2. Expand the object tree, and then select a resource group under Resource Groups. The resource-group-name subwindow appears. 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.
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.
• Deleting multiple resource groups, page 348 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. Expand the object tree, and then select a resource group under Resource Groups. The resource-group-name subwindow appears. 3. Click Delete Group. The Delete Group - resource-group-name dialog box appears. 4.
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 353 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 296. For details on how to manually clear the alert settings, see “Deleting alert settings” on page 315.
3. Select the check boxes of the Device Manager servers you want to delete, and then click the Remove DevMgrs button. 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 355
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 11, 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 11 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 12 Backup and restore operations Related topics • Creating an application replica, page 376 • Restoring the latest application replica (simple restore), page 383 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 13 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.
• To restore a renamed SQL Server database, be sure to detach the database before doing the restoration. If you attempt to restore the database without detaching it, the restore will not execute 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 389.
• When using Snapshot, check the free capacity of the data pool during the restore. You should periodically check the data pool and increase the capacity as necessary. • 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.
Defining consistency groups and P9000 RAID Manager It is important to consider how backup and restore operations are performed when defining consistency groups, especially if you plan on performing partial database restorations. For SQL Server databases When restoring individual databases: Define one consistency group to one database so that each database is in a separate consistency group.
Exchange data and requirements The following are the types of Exchange data subject to backup using Replication Manager. Table 17 Types of data subject to backup (Exchange) Database subject to backup Files subject to backup Data files (Exchange Server information store) Exchange Server 2003/2007 storage group Exchange Server 2010 information stores Extension *.edb *.stm (not used in Exchange Server 2007) Transaction log files *.log Checkpoint files *.
SQL Server data and requirements The following are the types of SQL Server data subject to backup using Replication Manager. Backed-up databases differ depending on the option specified in the Create Replica Wizard.
databases. If the system database to be backed up is specified as the destination, when the system database is restored from the secondary volume, the SQL Server error log files are also restored. As a result, the contents of the error log files return to the state they were before the backup, and consequently the error log information generated after the backup will be lost. • Store tempdb on a different volume from the one used to store a user database to be backed up.
Figure 15 Metafile allocation If the database server is in a cluster configuration using Microsoft Cluster Service and metafiles are stored in a storage system volume, a secondary volume can be used to restore the metafiles when the cluster server fails over. 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.
Software that should not be used during replica operations There are several tools and applications that can interfere with replica operations and should not be run while performing backups and restores. Applications that use the primary or secondary volumes can prevent P9000 RAID Manager from operating properly, interfere with mount/unmount operations, and cause data inconsistencies.
Figure 17 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 18 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 19 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 384. 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. Instead, the actual roll-forward operation must be performed using Management Studio after completing the restore operation.
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 383 starting at step 5.
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. In the Replica History tab of the SQL Server subwindow, select the replica created before the failure occurred and click Delete Replicas. 8. Use the disk management function to mount the primary volume connected to the database server. 9. Start SQL Server on the database server.
NOTE: The DAG feature is exclusive to Exchange Server 2010. For more information, see “About Database Availability Groups (DAGs)” on page 388. Figure 22 Sample DAG configuration The following operations apply to DAG configurations: • As an initial operation, you should perform a backup (a full copy that represents a baseline). After completing the backup, Exchange Server automatically transfers the updates of transaction log files and applies them to the passive nodes. • The 2.
• After restoration, you must execute the seed function to change the status of the Exchange Server 2010 replication function to normal. • If you perform a restoration without using the seed function, the Exchange Server 2010 replication function to be restored will be stopped, but the seeding will not be performed. After the restoration, you must perform seed processing and restart the Exchange Server 2010 replication manually.
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. Transaction logs can be applied to databases in the loading status and standby status using Management Studio.
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 22 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 23 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 25 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 277. 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 409.
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 314 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 411 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 the Export button. 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 411 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 411 416 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 a 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. Related topics • Viewing the operation mode, page 418 • About operation modes, page 418 Expanding journal group capacity To expand capacity of a journal group: 1. From the Explorer menu, choose Resources and then Storage Systems.
• Editing journal groups, page 303 420 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.
Product references This manual follows the conventions shown in Table 25 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 Asynchronous Continuous Access Asynchronous • Continuous Access XP Asynchronous • Continuous Access XP Extension • XP Continuous Access Asynchronous 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
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 433. Restrictions related to web browsers The following restrictions apply when performing operations in a web browser: • Do not use the web browser toolbars, menu bars, link bars, or buttons to perform Stop, Go To, Refresh, or other operations. The only operations that can be successfully performed are printing windows and resizing fonts from the menu bar.
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.
In the pair configurations view, configuration definition information, including the information about the copy pairs in simplex status, is displayed based on what is defined in the configuration definition file. However, for Replication Manager to be able to manage existing copy pairs, the following conditions must be satisfied: • A P9000 RAID Manager configuration definition file must be present.
Configuration in which copy groups containing copy pairs in simplex status and a configuration definition file exist (open systems) In this example, copy groups containing copy pairs in simplex status and a configuration definition file exist. In the example, in the Hosts or Storage Systems view, volumes 5:11 and 4:88, which belong to copy group CG.CntAc-A01, are displayed in the Paired list, and volumes 6:11 and 5:88, which belong to copy group CG.CntAc-A02, are displayed in the Unpaired list.
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 when two configuration files define an opposite relationship of primary and secondary volumes for the same copy group 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 6.0 1 2 2, 3 2, 3, 4 2, 3, 4, 5 2, 3, 4, 5, 6 2, 3, 4, 5, 6, 7, 8 6.1 1 1 3 3, 4 3, 4, 5 3, 4, 5, 6 3, 4, 5, 6, 7, 8 6.2 1 1 1 4 4, 5 4, 5, 6 4, 5, 6, 7, 8 6.3 1 1 1 1 5 5, 6 5, 6, 7, 8 6.4 1 1 1 1 1 6 6, 7, 8 7.0 1 1 1 1 1 1 7, 8 7.0.1 1 1 1 1 1 1 8 7.1.0 1 1 1 1 1 1 1 Legend: 1. 2. No restrictions.
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 Name of the storage system to which the secondary volume belongs n/a 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.
When multiple Replication Manager servers manage the same information source In configurations where multiple Replication Manager servers manage the same information source (DevMgr / BCM), the servers cannot simultaneously monitor and manage pairs. If different servers 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.
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.
Indicates that no value is specified for the configuration information managed by Replication Manager Before this information can be displayed, a value must be specified for the information in Replication Manager. (This does not apply to hyphens contained in license information.) Blank Indicates that Replication Manager acquired blank information from the information source. (Unknown icon) or Unknown (For the summary copy pair status, the Unknown icon is displayed.
Display format of copy type Display format in Web client Copy type BC Business Copy 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 445
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 276 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.
RAID Manager instance normally resides on one server (one node). If two or more nodes are run on a single server (e.g., for test operations), it is possible to activate two or more instances using instance numbers. Also referred to as the P9000 RAID Manager instance. host storage domain A group defined in Device Manager that is used to strengthen the security of volumes in storage systems.
(P9000 mainframe agent) Software used to acquire information about mainframe system hosts and storage systems. In conjunction with P9000 mainframe agent, Replication Manager monitors configuration and status information about copy pairs created using PPRC. MCU Main Control Unit MFA P9000 mainframe agent MIB (Management Information Base) A database that defines the structure of information used by SNMP.
by prefix, so Replication Manager uses this prefix as a unique name to identify copy group definition files created by HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent. P-VOL (primary volume) The source volume that is copied to another volume using the volume replication functionality of a storage system. property files Generic term for the files that define the Replication Manager operating environment.
S-VOL (secondary volume) The copy destination volume of two volumes that are associated in a copy pair by a storage system volume replication functionality. SNMP Simple Network Management Protocol SSD Solid State Drive SSL Secure Sockets Layer storage system An external storage device (storage system) connected to a host. summary pair status By displaying only the summary status for the copy pairs in each copy group, Replication Manager allows users to quickly check copy pair status.
Snapshot 460 Glossary Software used to duplicate volumes in a single storage system. Snapshot duplicates differential data in a data pool. The secondary volume is a virtual volume that consists of the primary volume and the differential data. By duplicating only the differential data, Snapshot can copy data in a very short time as well as reduce the capacity required of the volume used for duplication. For more information, see the Snapshot manuals.
Index A access control users and permissions, 79 accounts adding users, 83 automatic locking, 339 changing passwords, 323, 329 locking, 330 removing users, 325, 326 unlocking, 331 advanced options force-split, 228 swap, 228 takeover, 227 takeover-recovery (recreate), 228 takeover-recovery (resync), 228 agent user script, 391 alerts and volume switching, 233 automarking, disabling, 155, 315 changing, 314 completion, 127 conditions for, 125 copy license usage threshold, 126 copy pair status, 126 deleting, 315
cache, 121 candidate volumes, 118, 121 capacity, 118, 148, 290 expanding journal group, 419 licensed, 318 cascade configuration defining, 163 limitations, 163 permitted topologies, 162 Change Pair Status Wizard about, 220 advanced options, 226 basic options, 226 checkpoint files, 370 class, 160 CLI copy pair status, 245 refreshing configuration information, 252 command device adding, 113 defined, 112 deleting, 299 editing, 298 Conceal Secondary Volumes option, 60 configuration definition file, 147 importing
copy pair about, 144, 190 add to workflow, 178 and copy groups, 129 associated with a task, 283 checking, 263 checking (specific volume), 262 checking configuration definitions, 261 checking, about, 260 configuration definitions, 146 copy groups belonging to, 286 deleting related pairs, 300 editing, 181 monitoring, 264 monitoring (alerts), 265 prerequisites for mainframe, 177 refresh interval, 136 refreshing manually (My Copy Groups), 250 refreshing status, 245 saving, 174 states, 208 status, 201, 213 statu
drmumount command, 400 E Edit Group window, 170, 185 email, 265, 311 emergency license key, 317, 318 emulation type, 290 event log about, 407 data retention, 137 exporting, 413 viewing list of files, 408 exauth.
information stores, 406 restoring, 380 IP address, 53, 54, 288, 349, 351, 439 IPv6, 34, 54, 351 J JNLG, 122, 123, 303, 414 expanding journal group capacity, 419 journal groups about, 119 adding, 123 deleting, 303 editing, 303 expanding capacity, 419 journal volume usage, 414 wizard, 122 journal usage exporting, 414 exporting for each copy group, 414 K KAVN00123-I, 136 KAVN00124-I, 136 KAVN00126-I, 136 KAVN00127-I, 136 L last distributed time, 173 last refresh, 249, 250, 257 LDAP, 79, 332 LDEV, 148, 249,
P9000 mainframe agent adding an instance, 54 editing an instance, 351, 353 sample configurations, 24 P9000 RAID Manager, 23 command devices, 111, 112 pair configuration association, 181 copy group requirements, 154 creating, 151 deleting, 187 editing by associating, 179 prerequisites (mainframe), 149 unsupported, mainframe, 162, 452 wizard, about, 141 Pair Configuration Wizard launching, 142 unsupported configurations, mainframe, 162, 452 Pair Configurations view, 287 pair management copy groups defined in
remote paths about, 114 conditions, 114 creating, 114, 116 deleting, 301 editing, 299 managing, 299 wizard, 115 remote_MU, 357 replica generation, 157 replicas about, 357, 374, 375 check status workflow, 405 concealing secondary volumes, 60 configuration requirements, 369 create (workflow), 374 creating, 364, 376 data protection status, 277, 278 data types, 369 generations, 148, 357 information stores, 380 mounting/unmounting, 404 precautions, 360, 374 prerequisites, 33 Read disable option, 33 resources, 40
sites about, 94 adding, 95 adding storage systems, 97 deleting, 309, 310 editing, 307 hosts, adding, 96 hosts, removing, 308 pair management servers, 98, 309 removing storage systems from, 308 set up, 94 viewing, 307 viewing (individual), 307 Snapshot, 116, 160 snapshot image, 271 SNMP email, 259 Monitoring Resource Utilization (Pools and Journal Groups), 274 SNMP trap, 125, 259, 311, 407, 410 SP-VOL, 144 speed, 121 split, 213 Split (SSWS), 227 Split (SWSS), 226, 228 SQL Server database status, 389 distribu
users adding, 83 adding to resource group, 89 authentication method, 332, 333, 334 authorization method, 334 deleting, 326 deleting(Deleting Users), 325 list, 322, 323 logging in/out, 34 login window, 340 password, changing, 323, 329 permissions, 79 profiles, editing, 328 profiles, viewing, 328 removing (from resource group), 346 V V-VOLs and CVS installation, 109 conditions for adding, 108 creating, 108, 110 deleting, 297 deleting multiple, 297 deleting, conditions, 297 managing, 297 prerequisites, 108 wi
