HP XP7 Replication Manager User Guide Part number: TK981-96013 First edition: April 2014
Legal and notice information © Copyright 2010, 2014 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 ...............................................................................
Changing user permissions .................................................................................................. Setting up resource groups ......................................................................................................... About resource groups ........................................................................................................ Example of resource groups ..........................................................................................
Storage system types and volume requirements (pools) .......................................................... About the Create Pool Wizard ........................................................................................... Launching the Create Pool Wizard ...................................................................................... Adding pools .................................................................................................................. Setting up journal groups .....
About configuration definition file formats ..................................................................... About creating copy pair configuration definitions ................................................................ Copy pair configuration conditions .............................................................................. Prerequisites for pair configuration ...............................................................................
Deleting tasks .................................................................................................................. Distributing copy group definitions (mainframe) .......................................................................... About distributing copy group definitions ............................................................................. Example of copy group definition distribution scenario ....................................................
Changing the copy pair status for multiple copy pairs (batch operation) ............................ Confirming copy status during task execution ....................................................................... Advanced pair operations and recovery scenarios ................................................................ Takeover operation .................................................................................................... Swap operation ..............................................
Checking copy pair configurations ..................................................................................... Copy pair configuration check workflow ....................................................................... Checking copy pair configuration definitions ................................................................. Checking copy pair configuration (perspective of specific volume) ....................................
Viewing a list of storage systems ............................................................................................... Viewing a summary of storage systems ...................................................................................... Viewing DEVN information (mainframe systems) ......................................................................... Viewing individual host information ...........................................................................................
Viewing individual site information ............................................................................................ Editing sites ........................................................................................................................... Removing hosts from a site ....................................................................................................... Removing storage systems from a site .............................................................................
Locking user accounts ....................................................................................................... Unlocking user accounts .................................................................................................... About user authentication .................................................................................................. Linking to an external authentication server ..........................................................................
About application replicas ....................................................................................................... Managing generations (replica rotation) .................................................................................... About storage groups and information stores .............................................................................. Check replica configuration workflow ........................................................................................
Exporting the history of pool volume usage ................................................................................ 443 Exporting the history of sidefile usage ....................................................................................... 443 26 System maintenance ..................................................................... 445 About system maintenance .......................................................................................................
Example configuration in which two copy group definition files are used for the same copy group (for mainframe systems) ..................................................................................... When the copy pair configuration is complex ...................................................................... Example of complex cascade configuration 1 ................................................................ Example of complex cascade configuration 2 ........................................
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 XP7 mainframe agent) ......... 27 4 Example system configuration managing copy pairs and application replicas .................
Tables 1 Pair management server configurations ...................................................................... 33 2 Parameters for backup server calculations .................................................................. 61 3 User roles .............................................................................................................. 79 4 Pair definition and replica operations ........................................................................ 79 5 Pair operations ...............
Preface This document describes how to use the HP XP7 Replication Manager software.
Preface
1 Introduction This chapter provides an overview of Replication Manager features and architecture. It also provides an introduction to supported system configurations and an operations roadmap. About Replication Manager Replication Manager is a business continuity management framework that allows you to centrally configure, monitor, and manage in-system or remote business continuity products, for both mainframe and open environments.
Replication Manager features Replication Manager provides the following features to assist storage administrators: • • • • • Centralized management of a replication environment Integrated database backup management Visual representation of replication structures Monitoring and immediate notification of error information Modification of replication structures NOTE: If Replication Manager is installed without a license (or the existing license expires), only basic pair configuration functions will be availa
Modification of replication structures Replication Manager provides capabilities to configure additional copy pairs as business operations expand and improve performance by expanding buffer capacity for copying volumes. You can also change pair states manually after error recovery. Using the wizards provided in the GUI, you can set up pairs while visually keeping track of complex replication structures.
manage the hosts by registering the instance of HP StorageWorks P9000 for Business Continuity Manager Software or XP7 mainframe agent installed on each host in the local and remote sites as an information source. • Database and backup servers: To manage database replicas, the system requires two servers: a database server that manages the primary volume, and a backup server with the secondary volume.
Figure 1 Two site configuration in an open system User Guide 25
Figure 2 Example system configuration in a mainframe system (using HP StorageWorks P9000 for Business Continuity Manager Software) 26 Introduction
Figure 3 Example system configuration in a mainframe system (using XP7 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 XP7 Replication Manager Configuration Guide.
Introduction
2 Getting started This chapter describes initial settings needed to begin Replication Manager operations and procedures for setting up the prerequisite environment for pair management. It also includes quick references to typical operations performed using Replication Manager. Using the Help system The Replication Manager online help system is context-sensitive; when you click Help from within a window or dialog box in the Web client, information specific to the task you are performing displays.
You can also print information in topics by clicking the Print icon located in the top right of your Help window. Initial setup After Replication Manager has been installed on a management server, you must configure initial settings needed to begin Replication Manager operations. Initial settings configuration workflow The following figure shows the task flow of the initial configuration settings.
WARNING! N:M and 1:M configurations are intended for use in disaster recovery. N:M and 1:M configurations cannot be used to create or restore application replicas.
Figure 5 Example of redundant pair management server configuration Registering redundant pair management server nodes (while creating a copy group) You register the initial primary/secondary pair management servers when creating a new copy group from the Group Management page of the Pair Configuration Wizard: 1. Click Create Group. 2. Enter the Group Name. 3. Select the Site and Server Name for the primary and secondary pair management servers.
Registering redundant pair management servers manually If you are constructing the redundant pair management server configuration manually, be sure and do the following: 1. 2. 3. Use a RAID Manager command to change the configuration of the copy pair. Set up the HORCM configuration files so that each primary HORCM file has all secondary targets and vice versa. In the Storage System view of Replication Manager, select the storage system where the operations were performed and click Refresh Configuration.
• Prerequisite products for Replication Manager are installed and their environment settings are configured • Replication Manager is installed on the management server, and an environment is set up • If you plan to create replicas, make sure the Application Agent is installed on the database and backup servers • A Replication Manager license is set up Logging in and out To log in to Replication Manager: 1.
If you are logged in to another HP XP7 Command View AE Suite product, you can also start Replication Manager using the GO link for RepMgr displayed in the Dashboard menu. If you logged in to Device Manager from HP SIM, you can invoke Replication Manager software from Device Manager. In this case, you can perform the Replication Manager software operations permitted by the permissions of the user account that you used to log in.
Getting started
3 Replication Manager console This chapter describes the Replication Manager console and its main features. This chapter also provides descriptions of various functional views available in the Replication Manager console. Understanding the console layout Replication Manager provides a simple, easy-to-use, centralized management console for monitoring and visualizing volume replication configurations and status information. The following example is an illustration of Replication Manager console layout.
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 HP XP7 Command View AE Suite products.
Explorer menu items Menu item Explanation Displays resources such as application servers or hosts, storage systems, and pair management servers managed by Replication Manager. • Hosts: Displays information about the hosts managed by Replication Manager (hosts view). Resources • Storage Systems: Displays information about the storage systems managed by Replication Manager (Storage Systems view).
Menu item Explanation Tasks: Displays the tasks scheduled for copy pairs. Tasks Workflows: Displays the workflow generated for copy pairs. Alerts Alerts: Allows you to check alerts or edit alert settings. User Profile: Allows you to check or edit user information. Settings License Info: Sets the Replication Manager license information. Refresh Setting: Allows you to update the information managed by Replication Manager and set the interval for updating the information.
Dialog box A dialog box is a pop-up window displayed when an action button is clicked. The window displayed when a specific action button is clicked is called the action-name dialog box. Clicking Help in a dialog box displays the online help page that describes the items displayed in the dialog box. Functional views Replication Manager provides multiple views that display pair configurations and the status of the replication environment from different perspectives.
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 464 or “Display formats used when no pertinent information is available” on page 475. Storage Systems Storage System Displays the storage system name using the following format. Displays the types of the storage systems.
Structure of the Storage Systems view The figure below shows the structure of the Storage Systems view with the list of storage systems as the starting point. The subwindow changes according to the hierarchy displayed in this structure. Pair configurations subwindow The Pair Configurations subwindow lets you view pair management servers with copy pair definitions (RAID Manager configuration definition file) and related information.
Pair Management Servers Pair Management Server Displays the name of the pair management server that issues instructions to storage systems to perform a copy pair operation. Selecting the name opens either the pair-management-server-name subwindow (open systems) or pair-management-server-name subwindow (mainframe systems). IP Address Displays the IP address of the pair management server. If the host has both an IPv4 address and an IPv6 address, the order of the addresses displayed is IPv4 and then IPv6.
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 299 for a list of icons and their meanings. 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. The subwindow changes according to the hierarchy displayed in this structure.
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 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 hcmds64link command on the management server. For details on this command, see the HP XP7 Replication Manager Configuration Guide.
Adding a Device Manager server TIP: Only a user who has the Admin permission can add a Device Manager server. To add a Device Manager server: 1. Ensure that you have the following information: 2. • IP address or host name • Protocol to be used for communication with Replication Manager software (HTTP or HTTPS) • Port number (the server.http.port value in the server.
Adding an instance of HP StorageWorks P9000 for Business Continuity Manager Software or XP7 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.
Once an instance of BCM is registered, Replication Manager loads the configuration information associated with the BCM for the purposes of scanning the volumes as described in “About mainframe volume discovery” on page 65.
Adding an instance of Application Agent To add an instance of Application Agent: 1. Make sure you have the following information concerning the host where Application Agent has been installed: • Name of Application Agent identified by Replication Manager • Host ID. For a physical host (stand-alone), the IP address or host name of production server where the agent is running. (IPv4 and IPv6 addresses are supported.
Related topics • Setting Application Agent options, page 57 • Editing an instance of Application Agent, page 374 • Refreshing Application Agent, page 63 Setting Application Agent options After adding an instance of Application Agent, you must configure the options for the agent before the application discovery process can proceed. The options differ depending on whether the host is a database or backup server.
6. For cluster configurations, the Cluster Options tab is displayed. This tab sets the required Shared Data Path (location of the application configuration information used by Application Agent) and selects the Restore Mode (whether or not to keep cluster resources online).
Settings for virtual hosts and cluster configurations For the settings below, any settings applied to a physical host are automatically applied to all virtual hosts running on the physical host. This applies to cluster configurations as well.
Manual operation When a task has been created through the Pair Configuration Wizard with the Applications view, you can conceal or reveal volumes manually when adding or deleting pair groups. In the Edit Task[s] dialog box, go to the Pair Operation section of the Pair Setting tab. The Reveal Secondary Volumes option is is displayed when an attempt is made to delete a copy pair or group definition, and Conceal Secondary Volumes option is displayed for a creation operation.
Therefore, to execute the verification process in parallel and increase the performance, it is ideal to increase the number of FC ports connecting the server and storage and provide a configuration to enable multiple processing of I/O with respect to the disk.
Parameter Description Notes IS_NUM Number of information stores per storage group (Exchange Server 2007), or per database server (Exchange Server 2010/2013) You must supply this value. SG_NUM Number of storage groups to back up per database server (for Exchange Server 2010/2013, use a value of 1) You must supply this value. Because storage groups are not supported in Exchange Server 2010/2013, use a value of 1 in this case. DB_SERVER Number of database servers You must supply this value.
Refreshing Application Agent After updating an instance of Application Agent, you need to refresh the data. Replication Manager then retrieves the following information: • Application Agent component version • Parameters displayed on the setup windows To refresh the Application Agent data: 1. From the Explorer menu, choose Administration and then Information Source. The Information Source subwindow appears. 2. Expand the object tree, and then select Application Agent.
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.
1. 2. 3.
Example volume scan procedure Types of volume scans Replication Manager uses one of three available scanning methods to discover mainframe volumes: Local scan (Gen'ed) This method discovers volumes recognized by the mainframe host within a specified DEVN/VOLSER range. Local scan (Non Gen'ed) This method discovers volumes within a specified storage system and LDEV range. As a prerequisite, a local scan (Gen'ed) must be performed on the scan target storage system.
• Deleting a volume range from a volume range list, page 69 • Restrictions for deleting volume ranges, page 69 Adding a volume range to a volume range list To add a volume range to the volume range list: 1. Display the list of disk configuration definition files on the Disk Configs tab in the BC Manager / Mainframe Agent subwindow. For details on how to display disk configuration definition files, see “Displaying disk configuration definition files” on page 73. 2.
• Overlapping volume ranges cannot be specified. • When Non Gen'ed scan or Remote scan is selected, a starting number of Dummy DEVN that would cause the value of Dummy DEVN to exceed FFFF during the volume scan cannot be specified. Deleting a volume range from a volume range list To delete a volume range from a volume range list: 1. Display the list of disk configuration definition files on the Disk Configs tab in the BC Manager / Mainframe Agent subwindow.
2. Select a disk configuration definition file. 3. Set the volume range for the scan. For details, see “Adding a volume range to a volume range list” on page 68. 4. Select the target hosts for disk list distribution. For details, see “Selecting targets for disk configuration distribution” on page 72. 5. Check the information and click OK to begin the volume scan. The scanning process may take some time.
Example disk list distribution scenario Prerequisites for distribution destination hosts (disk configuration definitions) HP StorageWorks P9000 for Business Continuity Manager Software or XP7 mainframe agent hosts (with disk configuration definition files) must satisfy the following conditions to be distribution destination candidates: • The DADIDs of the distribution destination candidate host are the same as the origin of distribution.
Conditions Whether volume has been added to a pair* Copy type Volume type Information displayed when no restrictions apply to resource groups Information displayed when restrictions apply to resource groups Only the DADID of the volume added to the pair is displayed. Only the DADID of the volume added to the pair is displayed.
5. To delete a distribution target, deselect the check box for the candidate distribution host. TIP: The copy group definition file will not be distributed if you deselect a host registered as a distribution target. 6. To distribute the disk configuration definition file when the disk list is created, select the Distribute the disk config when creating the list check box. (Uncheck this check box when you want to skip disk list distribution.) 7. Click OK.
To edit a disk configuration definition file: 1. From the Explorer menu, choose Administration and then Information Source. The Information Source subwindow appears. 2. Expand the object tree, and select BC Manager / Mainframe Agent. The BC Manager / Mainframe subwindow appears. 3. Click the Disk Configs tab. The list of disk configuration definition files managed by Replication Manager are displayed in the Disk Configs tab. 4.
3. Under the DEVNs tab, select the Paired tab. The paired DEVN list is displayed. This list also displays copy types associated with established copy pairs. 4. Review the information in the paired DEVN list. Related topics • Reviewing unpaired DEVN list, page 75 • Reviewing unpaired LDEV list, page 76 Reviewing paired LDEV list To review the paired LDEV list: 1. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 2.
Reviewing unpaired LDEV list To review the unpaired LDEV list: 1. From the Explorer menu, choose Resources and then Storage Systems. The Hosts subwindow appears. 2. Expand the object tree, and then select a storage system under Storage Systems. The storage-system-name subwindow appears. 3. On the CUs tab, select a control unit number. The CU-number subwindow appears. 4. Under the LDEVs tab, select the Unpaired tab. All Mainframe volumes located on the storage system are listed. 5.
6 Setting up authorities Before you can use Replication Manager, you must specify user account settings and permissions to restrict the scope of operations allowed for each user. Replication Manager controls access by using resource groups that restrict accessible ranges, and user management roles that restrict user operations. To control access to Replication Manager resources, you need to create resource groups and associate users with resources. This chapter describes how to configure access control.
Permissions and management roles In addition to the built-in account (user ID: System), there are permissions that grant access to all Replication Manager functions. Permissions can be allocated in any combination, but are broad in nature and do not control access to individual functions. The following table groups the permissions into two categories known as management roles.
are fixed and cannot be customized.The user roles and their capabilities are shown in the following table. Table 3 User roles User Role Description Storage administrator Responsible for all replication tasks, including resource allocation (S-VOLs). Copy pair administrator Responsible for all replication tasks, except resource allocation. Application administrator Responsible for data protection of applications, but cannot change pair configurations.
Basic (mainframe and open) Role Advanced (open only) Resync / split / syncwait Restore Application administrator X X Application operator X Create Delete Takeover Swap Force-split Takeover-Recovery 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 Copy Pair Administrator Disabled Enabled Enabled Enabled Application Administrator Disabled Disabled Enabled1 Enabled Disabled Disabled Enabled1,2 Disabled Application Operator Legend: 1. 2.
Changing user permissions You can specify the permissions required to use a specific HP XP7 Command View AE Suite product for each registered user. To allow existing HP XP7 Command View AE Suite product users to also use Replication Manager, you must grant Replication Manager management permissions to those users.
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. Specifying a range of resources on which a user can perform operations prevents users from inadvertently performing operations on unmanaged resources. A user can be associated with multiple resource groups to increase the range of operations that he or she can perform.
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. You can then add resources to the resource group as desired.
• • • • • About resource groups, page 83 Adding hosts to a resource group, page 85 Adding users to a resource group, page 86 Adding storage systems to a resource group, page 85 Adding applications to a resource group, page 87 Adding hosts to a resource group You can add hosts as resources to existing resource groups. TIP: You cannot register the same host in more than one resource group. In addition, you cannot add hosts to the All Resources group (where all hosts are registered automatically).
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. The added storage systems are displayed on the Storage Systems page. Related topics • About resource groups, page 83 • Removing storage systems from a resource group, page 364 Adding users to a resource group You can add users to existing resource groups.
Adding applications to a resource group You can add hosts/applications as resources to existing resource groups. TIP: You cannot register the same host/application in more than one resource group. In addition, you cannot add hosts/applications to the All Resources group (where all hosts are registered automatically). To add hosts/applications to a resource group: 1. From the Explorer menu, choose Administration and then Resource Groups. The Resource Groups subwindow appears. 2.
3. On the Applications page, click Add Hosts. The Add Hosts - resource-group-name (Applications) dialog box appears. 4. Select the hosts/applications you want to add, and then add them. The added hosts/applications are displayed on the Applications page.
7 Organizing resources In Replication Manager you can organize resources such as hosts and storage systems into logical sites for easier management. You can also designate frequently monitored resource groups as My Copy Groups. This chapter describes different ways to organize resources. About resources Resources are entities managed by Replication Manager. These include application servers, storage systems, and pair management servers that constitute the replication environment.
Setting up sites Sites allow you to manually group resources under one name for easier management. You can define your own site and register resources such as hosts and storage systems. Grouping of resources into logical sites is especially useful when you have remote sites. Although you can define logical sites with any combination of resources, managing many resources from the web interface is easier when logical sites are created based on the resources of actual sites.
Adding sites To add sites: 1. From the Explorer menu, choose Shared Views and then Sites. The Sites subwindow appears. 2. Click Add Site. The Add Site dialog box appears. 3. Enter information about the sites you want to add, and then add them. The added sites are displayed in the Sites subwindow.
4. After sites have been added, specify the resources for the sites.
To add hosts to a site: 1. From the Explorer menu, choose Shared Views and then Sites. The Sites subwindow appears. 2. Expand the object tree, and then select a site by clicking on the site name in the Site List. The site-name subwindow appears. 3. Click the Hosts link. The Hosts subwindow appears. 4. Click Add Hosts. The Add Hosts dialog box appears. 5. Select the hosts you want to add, and then add them. The added hosts are displayed in the Hosts subwindow.
Adding pair management servers to a site You can add pair management servers to existing sites. After pair management servers have been added, the copy pair configuration definitions managed by the servers can be accessed from the nodes under the site. For open systems, if you need to use a pre-existing host as a pair management server (that is, you already added the host to the site), you must add the host to the site again as a pair management server.
3. Click the Applications link. The Applications subwindow appears. 4. Click the link for the desired application server. The Hosts list is displayed. 5. Click Add Hosts. The Add Hosts dialog box appears. 6. Select the hosts you want to add, and then add them. The added application servers are displayed in the Hosts list.
• Explorer menu items for My Copy Groups management , page 303 • My Copy Groups management functions, page 303 Examples of My Copy Groups The following figure shows a display example of My Copy Groups. Display example of My Copy Groups If the copy groups registered in My Copy Groups have a multi-target configuration or cascade configuration, the relationships among the copy groups are displayed as described below.
In this example, the secondary volume of Copy Group_A is the primary volume of Copy Group_B and Copy Group_C. If a single copy group is connected to multiple copy groups The secondary volume of the multiple copy groups on the left is the primary volume of the single copy group on the right. In this example, the secondary volume of Copy Group_A and Copy Group_B is the primary volume of Copy Group_C.
If a 3DC multi-target configuration further connects to other copy groups A 3DC multi-target configuration that uses the delta resync function can further connect to other copy groups that are managed by Business Copy (or Snapshot/Fast Snap). In this case, a volume in the 3DC multi-target configuration is used as the primary volume and the volumes displayed on the right are used as the secondary volumes. The following three examples illustrate this pattern.
Creating My Copy Groups To create My Copy Groups: 1. From the Explorer menu, choose My Groups and then My Copy Groups. The My Copy Groups subwindow appears. 2. Click Edit My Copy Groups. The Edit My Copy Groups dialog box appears. 3. In the list, select the copy groups you want to display in My Copy Groups. 4. Click OK to update My Copy Groups. The information displayed in the My Copy Groups subwindow is refreshed.
Organizing resources
8 Setting up storage systems You can use Replication Manager to replicate volumes or change copy pair definitions. It is necessary to configure prerequisite settings before replicating volumes. You can specify the prerequisite settings centrally from Replication Manager, for many storage systems across multiple sites. This chapter describes the tasks for preparing the replication environment and setting up storage systems.
For a list of available storage system setup functions and required user permissions (Replication Manager management), see “Storage system setup functions ” on page 102. NOTE: For mainframe systems: Depending on the copy types to be configured, some of the storage system setup operations need to be performed with XP7 Remote Web Console. For details, see the HP XP7 Replication Manager Configuration Guide.
• Create a new remote path • Add a remote port for an existing remote path. TIP: Each function can be used only for the resources in resource groups associated with the user. Explorer menu items for setting up storage systems The following table shows the Explorer menu items that are related to setting up storage systems, user permissions (Replication Manager management), and whether the items can be executed with the indicated permissions.
Flow of specifying the settings required before replicating volumes Setting up V-VOLs Replication Manager supports creation of V-VOLs on storage system configurations. This function is only supported for XP24000/XP20000 storage systems. You can create V-VOLs and associate them with volume pools, using the Create V-VOL wizard. For details on how to create V-VOLs, see “Creating V-VOLs” on page 106 About creating V-VOLs Replication Manager supports creation of V-VOLs on storage system configurations.
V-VOL limits The maximum number of V-VOL groups that can be created for each storage system is 65,280. For XP24000/XP20000 storage systems, the maximum number of V-VOLs in a V-VOL group is 1024. For HP P9500 or XP7 storage systems, the default maximum number of V-VOLs that can be created at one time with the Create V-VOL Wizard is 900. (Exceeding this limit will fail with the error RPM-01014.) To increase this value, you must modify the server.http.entity.maxLength property in the server.
XP24000/XP20000 Condition XP7 and P9500 CVS installed CVS not installed Number of primary volumes that can be added No limit No limit 1 Number of copy generations 65,280 1,024 1 (inactive) About the Create V-VOL Wizard Replication Manager includes a Create V-VOL Wizard for creating V-VOLs and associating them with volume pools.
2. Expand the object tree, and then select a storage system under Storage Systems. The storage-system-name subwindow appears. 3. Click the Open link. The Open subwindow appears. 4. Under the Pools tab, display the V-VOLs tab. 5. Click Create V-VOLs. The Create V-VOLs Wizard is launched. 6. On the 1. Setup V-VOL Group page, specify the parameters of the V-VOL Group (Parity Group). NOTE: Steps 7 and 8 only apply to XP24000/XP20000 storage systems.
17. Review all parameters of the V-VOLs and click Confirm. The 5. Finish page is displayed. TIP: The time taken to complete this operation depends on the count and size of the primary LDEVs, and the specified Count of Snapshot. For five 1 GB primary LDEVs, it takes approximately 20 minutes. For one 1 GB primary LDEV and 1024 snapshots, it takes approximately 40 minutes. This operation can take longer when a large number of primary LDEVs are selected. 18.
Related topics • • • • About the Add Command Devices Wizard, page 110 Setting up command devices, page 108 Editing command devices, page 320 Deleting command devices, page 321 Storage system types and volume requirements (command devices) Volumes that meet the requirements listed here are displayed as candidate volumes in Replication Manager.
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 v7.0.1 or later. About the Add Command Devices Wizard Replication Manager includes an Add Command Devices Wizard for registering volumes as command devices.
Related topics • About command devices, page 108 • About the Add Command Devices Wizard, page 110 • Storage system types and volume requirements (command devices), page 109 Setting up remote paths If you use Continuous Access Asynchronous, Continuous Access Synchronous, or Continuous Access Journal to replicate volumes, you must set up a logical path (called a remote path) to link the MCU (or primary DKC) of the local storage system to the RCU (or secondary DKC) of the remote storage system.
Whether to specify a remote path depending on combination of storage systems Remote storage system Local storage system XP512/ XP48 XP1024/ XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 HP P9500 HP XP7 XP512/XP48 N N -- -- -- -- XP1024/XP128 N N N N -- -- -- N1 Y Y Y Y -- N1 Y Y Y Y HP P9500 -- N1 Y Y Y Y HP XP7 -- -- Y Y Y Y XP12000/ XP10000/ SVS200 XP24000/ XP20000 Legend: Y: A remote path can be specified. N: A remote path cannot be specified.
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.
NOTE: As of Replication Manager 7.1.1, mainframe THP volumes are supported for the HP P9500. As of Replication Manager 8.0.0, mainframe THP volumes are supported for the HP XP7 platform. Replication Manager allows you to specify pools when all of the following conditions are satisfied: • An open system is being used. • The storage system type is XP12000/XP10000/SVS200, XP24000/XP20000, HP P9500, or HP XP7. • A license has been registered for the copy type being used (Snapshot/Fast Snap).
Requirement XP12000/ XP10000/ SVS200 XP24000/ XP20000/ HP P9500 HP XP7 Volume access attribute must be Read or Write Y Y Volume not reserved for Auto LUN Y Y Volume subject to cache residency Y Y The values Protect, Read Only, and Reject S-VOL are not specified for the attributes in Data Retention Utility.
Launching the Create Pool Wizard To launch the Create Pool Wizard: 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 Pools tab, click Create Pool. The Create Pool Wizard starts.
You can set journal volumes and journal groups by using a wizard on the JNLGs tab in the Storage Systems view. For details on how to add journal groups, see “Adding journal groups” on page 121. About journal groups Journal Groups are used to keep the journal data for asynchronous data transfer and must be set up before creating Continuous Access Journal volume pairs. Journal groups must be set in each storage system on both the primary and secondary side.
Requirement XP12000/ XP10000/ SVS200 XP24000/ XP20000 HP P9500 HP XP7 Not a LUSE volume Y Y Y Y Not a V-VOL Y Y Y Y Guard not specified Y Y Y Y Not an HIHSM reserved volume Y Y Y Y Not an On Demand volume Y N N N Not on the system drive N Y Y Y Status must be normal Y Y Y Y Not a THP VOL Y Y Y N Not a THP-pool VOL N Y Y Y If you edit the journal group, all volumes are in the same CLPR partition for the journal group Y Y Y Y Encrypted and non-encrypted v
Journal Group on the Primary Side (Master) Item Initial Active Stop Other than Active or Stop Journal Group on the Secondary Side (Restore) Active Stop Other than Active or Stop Data Overflow Watch Time Y N Y N N N N Path Watch Time Y N Y N N Y N Forward Path Watch Time Y N Y N N N N Use of Cache Y N Y N N Y N Speed of Line Y Y Y N Y Y N Delta Resync Failure Y N Y N N N N Legend: Y: This item can be specified. N: This item cannot be specified.
About the Create Journal Group Wizard Replication Manager includes a Create Journal Group Wizard for creating journal groups.
Launching the Create Journal Group Wizard To launch the Create Journal Group Wizard: 1. In the Explorer menu, choose Resources and then Storage Systems. The Storage Systems information is displayed in the Navigation area. 2. Expand a storage system, to open up the storage system information, and click Open. The storage system detailed information is displayed in the Application area. 3. In the JNLGs tab, click Create JNLG. The Create Journal Group Wizard starts.
Setting up storage systems
9 Customizing monitoring parameters You can customize Replication Manager by configuring alert notification settings, refresh intervals, and data retention periods. You can set up alerts to monitor thresholds for copy pair status, performance metrics and copy license usage. You can also configure refresh intervals at which the latest storage system information is applied to the Replication Manager database and retention periods for data items such as received alerts, write delay time, and event logs.
• • • • Alert retention, page 125 Alert limits, page 125 About the Create Alert Setting Wizard, page 126 About handling errors, page 435 Copy pair status An alert is sent when a copy pair or copy group achieves a specified status. For example, you can specify a condition for a copy group so that an alert is sent when an error status is detected. In this case, an alert is sent indicating the copy pairs of the group that are in error status.
Alert completion Alerts are automatically marked as Completed according to the criteria in the following table. Table 7 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 337 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.
2. Display the information about the copy groups for which you want to set monitoring conditions. TIP: The best way to access alert settings related to copy groups is with the Copy Groups tab of the Alerts Setting List of the Alerts subwindow. For more information, see “Viewing alerts and settings” on page 336. For details on how to display this information, see the following: • • • • 3.
Setting the copy pair status monitoring conditions for each copy pair To set the conditions for monitoring copy pair status on a copy pair basis: 1. If you intend to use SNMP traps to send alerts, load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About MIB definition files” on page 438. 2.
Setting performance monitoring conditions for each copy group To set the performance monitoring conditions on a copy group basis: 1. If you intend to use SNMP traps to send alerts, load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About MIB definition files” on page 438. 2. Display the information about the copy groups where you want to set monitoring conditions.
Setting performance monitoring conditions for each journal group To set the performance monitoring conditions on a journal group basis: 1. If you intend to use SNMP traps to send alerts, load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About MIB definition files” on page 438. 2. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 3.
Setting performance monitoring conditions for each pool To set the performance monitoring conditions on a pool basis: 1. If you intend to use SNMP traps to send alerts, load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About MIB definition files” on page 438. 2. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 3.
Setting monitoring conditions for copy license usage To set monitoring conditions for copy license usage: 1. If you intend to use SNMP traps to send alerts, load the MIB definition files into the software that will receive the traps. For the location of the Replication Manager MIB definition files, see “About alert management” on page 335. 2. From the Explorer menu, select Resources, and then Storage Systems. The Storage Systems subwindow appears. 3.
Adding monitored targets To add a monitored target: 1. Select the resources you want to add as monitoring targets, and then click Create Alerts. The Create Alert Setting Wizard starts with the 1. Introduction page displayed. 2. Read the wizard page, and then click Next. The 2. Select Monitoring Type page appears. 3. Select the monitoring type you want to use, and then click Next. The 3. Select Alert Setting page appears. 4.
Related topics • About refreshing copy pair status, page 267 Calculating the copy pair status refresh interval You should set refresh intervals values such that copy pair status refresh operations have minimal impact on management servers and pair management servers. The automatic refresh interval you specify should be greater than the time required for an individual pair management server to collect pair status. To calculate the interval for refreshing the copy pair status: 1.
• • • • • • Received alerts Write delay time (C/T delta) Event log data Sidefile and journal volume usage Pool volume usage (open systems) Tasks TIP: If the total number of data items (including alerts, C/T delta, event logs, sidefile, journal volume usage, and pool volume usage, but excluding tasks) exceeds 30,000,000, some of the old data might be deleted even if the retention period for the data has not expired.
Related topics • About data retention periods, page 135 User Guide 137
Customizing monitoring parameters
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 78 for more information. Legend: Y: Can be used with this permission.
Legend: Y: Can be executed with this permission. About the pair management wizards Replication Manager provides two pair management wizards. The Pair Configuration Wizard is provided for the creation and editing of copy pair configuration definitions. The Change Pair Status Wizard allows you to change the copy pair status.
Pair configuration workflow The following figure illustrates the workflow for pair configuration. Launching the Pair Configuration Wizard You can launch the Pair Configuration Wizard from the following locations on the web interface: • Unpaired LUN List: The Unpaired LUN list does not include copy pairs. The wizard can be launched from this list to configure new volume pairs. • Paired LUN List: The Paired LUN list includes copy pairs.
NOTE: The term LUN (Logical Unit Number) only applies to open systems. For mainframe systems, the analogs are LDEV (Logical Device) and DEVN (Device Number). Method for launching the wizard Conditions when the wizard cannot be launched • The LU has been reserved by another workflow. • The LU is a virtual volume. • If the LU is an internal volume to which an external volume is mapped, the host I/O suppression mode is enabled.
Method for launching the wizard Conditions when the wizard cannot be launched • A copy group that belongs to the same cascade has been reserved by another workflow. • At least one of the selected volumes does not belong to the same copy group. • A copy group in the same cascade contains pairs of multiple copy types. • Replication Manager is not aware of the pair management server (on either the primary or secondary side) that manages copy groups belonging to the same cascade.
Defining copy pairs and pair groups This module discusses how copy pair configuration definitions are created and tasks for defining copy pairs and pair groups: • • • • • • • About copy pairs, page 145 About copy pair configuration definitions, page 147 About creating copy pair configuration definitions, page 149 Creating pairs and pair groups, page 154 Editing pair names, page 156 About filtering candidate volumes, page 156 Selecting multiple candidate volumes, page 157 About copy pairs A copy pair is a
• Secondary volume (S-VOL): The destination volume to which the contents of the primary volume are copied. • Secondary-primary volume (SP-VOL): The volume located in the middle of a cascade configuration. A secondary-primary volume is both the secondary volume in an upper-level copy pair and the primary volume in a lower-level copy pair.
About copy pair configuration definitions Copy pair configuration definitions are generated when a new copy group is created. Pre-existing copy pair configuration definitions can also be imported into Replication Manager. New copy pair configuration definitions are created and edited using the Pair Configuration Wizard.
About configuration definition file formats New configuration definition files (HORCM configuration files) can be generated in either HORCM_LDEV format or HORCM_DEV format. Replication Manager allows you to specify the format for new configuration definition files using the server.agent.rm.pairDefinitionForm and server.agent.rm.cuLdevForm properties in the Device Manager agent server.properties file. (For detailed property file descriptions, see the HP XP7 Command View Advanced Edition Administrator Guide.
If you create a copy pair using XP7 Remote Web Console or other operation management software, no configuration definition file exists. Therefore, no configuration definition information is displayed in the Pair Configurations view.
(or exceeds the documented limits), an error occurs during task execution, even if the wizard finishes normally. Table 9 Number of generations possible with multi-target configuration Copy type Storage system Business Copy Fast Snap HP P9500 Snapshot 64 642 XP7 First layer: 3 XP24000/XP20000 Second layer: 21 -- -64 XP12000/XP10000/SVS200 -- Notes: 1. Cascading to second layer is not possible for mainframe pair configurations. 2.
If using a copy type, a remote path is set. If selecting an LU, it must not be associated with a device group. • LDEVs that are managed by RAID Manager and LDEVs that are managed by HP StorageWorks P9000 for Business Continuity Manager Software do not coexist.
Supported combinations of remote copy types and storage systems S-VOL P-VOL XP7 P9500 XP12000/XP10000/SVS200 XP24000/XP20000 XP7 Cnt Ac-S, Cnt Ac-J Cnt Ac-S, Cnt Ac-J Cnt Ac-S, Cnt Ac-J -- P9500 Cnt Ac-S, Cnt Ac-J Cnt Ac-S, Cnt Ac-J Cnt Ac-S, Cnt Ac-J Cnt Ac-S, Cnt Ac-J XP12000/XP10000/SVS200 Cnt Ac-S, Cnt Ac-J Cnt Ac-S, Cnt Ac-J Cnt Ac-S, Cnt Ac-A, Cnt Ac-J Cnt Ac-S, Cnt Ac-A, Cnt Ac-J XP24000/XP20000 -- Cnt Ac-S, Cnt Ac-J Cnt Ac-S, Cnt Ac-A, Cnt Ac-J Cnt Ac-S, Cnt Ac-A, Cnt Ac-J Le
• Volumes must not be journal volumes. Conditions for primary volumes that can be added (mainframe systems) The primary volumes that are displayed the Candidate List pane on the 2.
Copy type Candidate storage system Business Copy The storage system is the same as the primary storage system The storage system satisfies both the following conditions: Continuous Access Synchronous • The storage system must be different from the primary storage system. • The storage system must be either XP12000/XP10000/SVS200, XP24000/XP20000, HP P9500, or XP7.
5. In the Copy Topology pane, select the volume object and click Add Group. The Add Pair Group dialog box appears. 6. Specify a pair group name and copy type, and click OK to register the new pair group. The registered pair group is displayed in the Copy Topology pane. 7. Select a pair group in the Copy Topology pane. 8. Define a list of copy pairs to include in the pair group under Detail of pair-group-name pane. To define a copy pair: 1.
Editing pair names TIP: A pair name is generated automatically by the Pair Configuration Wizard. You have the option to override this name, but you cannot change the pair name once the pair has been created. The option to override the automatic pair name is supported only for open systems pair configurations. To override the automatic pair names generated during pair configuration: 1. On the 3. Group Management page of the Pair Configuration Wizard, select the copy pair(s) to be renamed from the Pair List.
Conditions No volumes selected. One or more volumes selected. A storage system containing the volumes in the DAD selected in the Disk List. A storage system that satisfies the condition described in (No volumes selected) and that contains the selected volumes. Information displayed when no restrictions apply to resource groups Information displayed when restrictions apply to resource groups All storage systems that satisfy either of the conditions on the left are displayed in the list.
Defining copy groups This module discusses information about copy groups and tasks for defining copy groups: • • • • • • • About copy groups, page 158 About assigning CTGID/JNLGID for copy pairs, page 158 Configuring open and mainframe consistency groups, page 159 About HORCM instances, page 160 Creating copy groups, page 160 Changing copy group names, page 162 Associating pair groups with copy groups, page 162 About copy groups A copy group consists of a number of copy pairs that have been grouped for ma
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. • For mainframe systems, Replication Manager allows you to specify EXCTG options to maintain consistency among multiple JNLGIDs in a Continuous Access Journal copy group.
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 Edit Workflow. On the 3. Group Management page of the Pair Configuration Wizard, select a pair group, and then click Create Group. The Create Group dialog box appears. 3. Specify the copy group name. 4.
Changing copy group names You can edit an existing copy group name using the Group Management screen of the Pair Configuration Wizard. To edit a copy group name: 1. Display the information about the desired copy group using the Host view or the Copy Group Configuration view. For details on how to display this information, see the following: 2. 3.
3. In the Copy Group pane, select the target copy group or container in the Copy Group field. TIP: When defining mainframe pair configurations, the copy groups listed in the Copy Group field are determined by the datasets allocated on the mainframe host. If you do not allocate the dataset or if Replication Manager does not retrieve this information, the related copy groups do not appear in the list. 4. For mainframe pair configuration, in the CTGID/JNLGID field, specify CTGID/JNLGID for copy pairs.
4. Create pair groups and associate them with the previously added copy groups. When applying the association, specify a consistency group ID or journal group ID. If the storage system and volume selected for the second copy pair configuration are the same as the storage system and volume selected for the initial copy pair configuration, specify a different CTGID/JNLGID from the CTGID/JNLGID specified first.
There are some requirements for copy types of the pair groups that can be added in multi-target or cascade configurations, to be compatible with the copy type of the original pair group. In this case, the copy type of the pair group to be connected by the Add Group operation must satisfy these requirements to be compatible with the copy type of the original pair group. For details on copy type requirements, see “Copy type requirements for pair configuration definitions” on page 165.
Legend: Y: This type of pair group can be connected. N: This type of pair group cannot be connected. Legend: Y: This type of pair group can be connected. N: This type of pair group cannot be connected. Legend: Y: This type of pair group can be connected. N: This type of pair group cannot be connected.
N: This type of pair group cannot be connected.
Related topics • Creating a 3DC multi-target configuration, page 168 • Limitations when performing 3DC configuration pair operations (mainframe systems), page 168 Limitations when performing 3DC configuration pair operations (mainframe systems) The following limitations and resolutions are to be noted when performing 3DC configuration pair operations: • When operating Delta Resync, it is necessary to switch the direction of Continuous Access Synchronous in advance.
• Creating copy groups, page 160 • Defining copy groups in a multi-target or cascade configuration, page 168 Using snapshot groups This module describes the use of snapshot groups: • • • • • • • About snapshot groups, page 169 Snapshot group requirements, page 170 Snapshot group configuration workflow, page 170 Creating a snapshot group, page 171 Viewing or modifying snapshot groups, page 172 Deleting a snapshot group, page 172 Migrating copy groups to snapshot groups, page 173 NOTE: Snapshot groups are o
• Because there is no pair/copy status assiociated with Snapshot/Fast Snap management, alerts and use of My Copy Groups do not apply. Instead, only FS pool usage monitoring applies. Related topics • Snapshot group requirements, page 170 • Creating a snapshot group, page 171 Snapshot group requirements Snapshot groups require the following: • The platform type must be Open. • The storage system must be HP P9500 or XP7. • Only Snapshot/Fast Snap snapshots can be registered in a snapshot group.
Creating a snapshot group This topic explains how to create a new snapshot group. CAUTION: Do not execute a task to create snapshot group pair and a task to create copy group pair simultaneously, or a duplicate CTGID error might occur. Prerequisites • Be sure you have enabled the user authentication mode for the command device using XP7 Remote Web Console. • Choose a pair managenent server as described in “Changing the pair management server for snapshot groups” on page 172.
4. Enter a name for the snapshot group and select FS (Snapshot Group) for the copy type. NOTE: You cannot specify the MU number. Although you can enable CTG, you cannot specify the CTGID. To display the CTGID that is automatically assigned from the Replication Manager GUI, you need to refresh the storage system information. 5. Define the necessary copy pairs and complete the wizard.
4. Specify Pair management server for snapshot group. 5. Click OK. 6. Check the displayed settings and then click Confirm. 7. Click Close when the completion dialog is displayed. 8. The pair management server displayed in the storage-system-name subwindow is updated.
• Immediate execution • Scheduled execution • Execution using CLI NOTE: If Replication Manager is not running when a task is scheduled to execute, the task will be executed as follows: • For tasks with an execution interval specified, the task is run at the next execution time after startup occurs. • For tasks without an execution interval, the task is run immediately after startup occurs.
Because associated tasks have an execution order, a task that must be executed prior to another task is known as a prerequisite task. If an execution problem occurs, error messages are displayed indicating when a prerequisite task has failed and the steps necessary to correct the problem. TIP: You need to re-create the task if all the following conditions are satisfied: • The port number, host group, or pair management server WWN was changed after the task was created.
• modify file: Creates or edits the RAID Manager configuration definition file. This operation does not create a copy pair. • modify file + create: Creates or edits the RAID Manager configuration definition file and creates a copy pair. This type also applies to creating a snapshot pair. • modify file + delete: Edits the RAID Manager configuration definition file and dissolves a copy pair. This type also applies to deleting a snapshot pair. • create: Creates a copy pair.
• distribute file: Distributes a copy group definition file. • change primary host: Changes the management host. • split: Splits a copy pair. This type of task is used to indicate both splitting of suspended pair and swapped pair. • resync: Re-synchronizes a copy pair. This type of task is used to indicate both re-synchronizing of suspended pair and swapped pair. • restore: Reverse synchronizes a copy pair by synchronizing data from the secondary volume to the primary volume. • delete: Deletes a copy pair.
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 RAID Manager configuration definition file. For mainframe tasks, this option is automatically selected and cannot be changed because mainframe pairs cannot created by Replication Manager. Update the task(s).
To make changes to one or more tasks on the 4. Task Management page: 1. To edit a single task, click the associated icon. To edit multiple tasks, they must be of the same copy type. Select the check boxes of the tasks you want to edit and click Edit Tasks. The Edit Task(s) dialog box appears. In this dialog box, you can set up execution options to modify pair creation. TIP: The Pair Setting tab is not displayed when editing tasks for mainframe systems. 2.
Viewing a list of tasks The Task List displays the tasks related to operations performed on copy pairs that are registered when the Pair Configuration Wizard or the Change Pair Status Wizard completes an operation, or when a copy pair associated with a remote path is deleted. The maximum number of tasks is 1,000. In this list, you can check information such as the task type (type of copy pair operation), execution status, and owner.
Deleting tasks You can delete tasks related to operations on copy pairs that were registered when the Pair Configuration Wizard or the Change Pair Status Wizard completed an operation, or when a copy pair associated with a remote path was deleted. You can only delete tasks that have the Cancel, Failure, Warning or Success status. When a task is deleted the task information is deleted from the repository. Resources reserved by a task are released when all the related workflows are deleted.
• Pre-distribution: Distribution of the latest copy group definition file from the current primary host to the copy group that will be the next primary host. The file can be distributed to only one userselected primary host (destination). This distribution occurs when the primary host is being changed and the copy group definition of the original primary host does not match the copy group definition of the new primary host.
• The copy group definition file must be previously distributed from the primary host by Replication Manager. (This implies a distribution relationship must already exist between the copy groups.) The following conditions occur when a copy group distribution primary host is changed: • Alert monitoring for the copy group by the previous primary host is stopped.
Confirming distribution hosts To confirm target distribution hosts and last distributed time: 1. Display the copy group information in the host or pair configurations view. For details on how to display this information, see “Viewing copy group information in the Hosts view (open systems)” on page 312. 2. Click the icon of the copy group for which you want to confirm target distribution hosts. The Distribution Hosts - copy group name window is displayed. 3.
• The tasks performed in the wizard might be divided between a storage system administrator who manages the storage system resources and an application server administrator who sets up the allocated resources according to the application. In this scenario, the storage system administrator can save the wizard current settings as a workflow so that the application server administrator can inherit the copy pair list that has been created.
To edit a workflow: 1. From the Explorer menu, choose Tasks and then Workflows. The Workflows subwindow appears. 2. Select the check box of a workflow you want to edit, and then click Edit Workflow. TIP: A workflow that was saved in a step prior to the Pair Configuration Wizard (3. Group Management) page cannot be edited or deleted. Therefore, if you click either of these buttons, an error message (RPM-00451) appears. A workflow that was saved in the Pair Configuration Wizard (3.
• About workflows, page 184 • Viewing a list of workflows, page 185 Managing copy pair configuration definitions This module describes tasks for managing copy pair configuration definitions: • • • • • • • • • • About editing copy pair configuration definitions, page 187 Adding copy pairs (completed workflow), page 189 Editing copy groups or snapshot groups by associating new pair groups, page 189 Editing copy groups or snapshot groups by associating new copy pairs, page 192 Editing copy groups by setting
CAUTION: Observe the following precautions: • While a copy pair configuration definition is being edited, do not use storage system operation management software to perform operations on a volume, copy group, or copy pair specified in that definition. Doing so might cause errors when Replication Manager executes tasks. • If you have specified the instance number in the server.agent.rm.exclusion.instance property of the server.
Adding copy pairs (completed workflow) After completing the initial pair configuration, you can add additional copy pairs to a copy pair configuration definition. This can be done only if all the associated tasks are in Ready status. You can edit the completed workflow created upon completion of the Pair Configuration Wizard. To add copy pairs to a completed workflow: 1. In the Explorer menu, choose Tasks and then Tasks. A list of tasks is displayed in the Tasks subwindow. 2.
3. Read the wizard page, and then click Next. The 2. Pair Association page appears. The copy topology to which the copy group or snapshot group belongs is displayed in the Copy Topology pane. 4. Create a pair group in the Copy Topology pane. 5. Define a list of copy pairs that you want to include in the pair group, by selecting the primary and secondary volumes in the Candidate List pane. For details on how to define copy pairs, see “Creating pairs and pair groups” on page 154.
• The copy type is Continuous Access Synchronous, and the secondary volume of the copy group that is the base for a multi-target configuration is selected. • The selected copy group has the same number of copy pairs as belong to a Continuous Access Journal copy group. • The storage system for the selected copy group differs from that for a Continuous Access Journal copy group.
Copy types that can be selected when a new copy group is added to existing copy groups Copy type of the pair group to be connected by group addition Business Copy Continuous Access Synchronous Continuous Access Asynchronous Continuous Access Journal Primary Y Y Y* Y Secondary N Y Y* Y Continuous Access Synchronous Primary Y N N Y Secondary Y N N Y Continuous Access Asynchronous* Primary Y N N N Secondary Y N N N Primary Y Y N N Secondary Y Y N N Copy type of sel
4. On the 2. Pair Association page, define volume pairs by selecting the primary and secondary volumes in the Candidate List pane. For details on how to define copy pairs, see “Creating pairs and pair groups” on page 154. You can click the areas. 5. icon or the icon to expand the Candidate List and Pair List display Click Add. The new volume pair is assigned to the copy group and displayed in the Pair List pane. 6. Click Next. The 3. Group Management page appears.
5. In the Copy Topology pane, click the copy type link (with copy type value "Unknown"). The Edit Copy Group window is displayed. 6. Select a copy type from the Copy Type drop down list. CAUTION: Pair configuration can fail if the specified copy type is different from the one configured when pair configuration file was created. 7. Click OK. The copy type assigned to the copy group is displayed in the Copy Topology pane.
5.
Copy type Option name Displayed items Default value Integer values from 0 to 3 Mirror ID Continuous Access Journal Continuous Access Synchronous Continuous Access Asynchronous Note: If you want to concurrently use Continuous Access Journal and Continuous Access Synchronous copy groups in a 3DC Cascade or 3DC Multi-target configuration, you cannot specify a value of 0 for Mirror ID.
The EXCTG options are available on the Edit Group window, when multiple CTGIDs exist on the Continuous Access Journal copy group. These options enable consistency to be maintained among multiple CTGIDs. The following table lists the EXCTG options available: Option name Displayed item Description Enable EXCTG among multiple CTGIDs Check box EXCTG ID No value or 0 to 3 Secondary Storage Systems All secondary storage systems that belong to the container are displayed.
TIP: Before you delete mainframe copy groups (with EXCTG specification) using the Pair Configuration Wizard, you should first delete all pairs using the Change Pair Status Wizard. When copy groups are deleted by CTG or pair units, the consistency of the EXCTG configuration is not guaranteed and task execution might fail. To delete a copy group: 1.
Deleting copy pairs from copy groups You can delete pairs from an existing copy group using the Pair Configuration Wizard. 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 183. To delete copy pairs from a copy group: 1.
• Creating pairs and pair groups, page 154 Importing existing configuration definition files To import existing copy group configuration definition files: 1. Confirm the following prerequisites: • Ensure the file specification format is is supported by Device Manager agent. 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 Option Continuous Access Synchronous Continuous Access Asynchronous Continuous Access Journal Business Copy Snapshot / Fast Snap Copy Pace Y Y Y Y N Fence Level Y Y Y N N Pool ID N N N N Y1 Pool ID (P) N N N N N Pool ID (S) N N N N N JNLG ID (P) N N Y N N JNLG ID (S) N N Y N N No Copy Y Y Y N N Split N N N Y2 N3 Quick Split N N N Y N Read disable (se
Copy type Copy pair operation Option Continuous Access Synchronous Continuous Access Asynchronous Continuous Access Journal Business Copy Snapshot / Fast Snap syncwait Timeout time N Y Y N N Force Delete Y Y Y N N Reveal Secondary Volumes Y Y Y N N takeover Data forward timeout time N Y Y N N swap takeover recovery (resync) Copy Pace Y Y Y N N Copy Pace Y Y Y N N JNLG ID (P) N N Y N N JNLG ID (S) N N Y7 N N No Copy Y Y Y N N delete takeover re
Copy types and maximum CTGID values Storage System Continuous Access Synchronous HP XP12000 Continuous Access Asynchronous Continuous Access Journal Business Copy N Snapshot / Fast Snap N NOTE: CTGID values start at 0. Also, the CTGID option cannot be specified for Delta Resync, Snapshot, or snapshot groups. Legend: N: Cannot be set. Option items for copy pair operations (mainframe systems) The option items for a copy pair operation differ depending on the copy type.
Copy Type Copy Pair Operation Option Values Secondary Mode Quick Resync Cnt Ac-S Read Only(*), Read Write On, Off(*) Y -- Cnt Ac-A Y -- Cnt Ac-J Y -- Description BC Y Y If the value is Read Only, the S-VOLs will be read only after the split operation is done. If the value is Read Write, the S-VOLs will be writable after the split operation is done. If the value is On, the status will be changed to Pair immediately.
TIP: When the YKRESYNC command is entered in BCM, you should specify either the FORWARD or REVERSE parameter. Whether you use the YKRESYNC FORWARD command to perform a Resync operation or use the YKRESYNC REVERSE command to perform a Restore operation depends on whether YKSUSPND FORWARD or YKSUSPND REVERSE was specified when the pair was suspended. You can also suspend a pair without specifying that a Resync or Restore operation will be performed.
Copy direction Present copy direction Value displayed in Direction option Forward + Reverse + No direction Forward Forward TIP: The Direction or Synchronization option should be specified, but not at the same time. The Direction option is available only when the copy type is Continuous Access Synchronous. For and Continuous Access Journal, both options are available.
Pair command 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.
Pair command Options Item specified Specifiable values Default value Remarks When specified: YKRECVER. When not specified: YKDELETE. delete force Whether to set the pair status to Simplex from the SVOL. on, off off The command cannot be used during a planned shutdown (during switching of the P-VOL and S-VOL). Note: The Force Delete option changes the status of the secondary volume to simplex, but does not affect the status of the primary volume.
Pair command Options Item specified Specifiable values Default value Remarks Flush: The copy pair is suspended after the data is synchronized. Purge: The copy pair is suspended at the moment that a suspend request is issued, even when there is data that has not been synchronized yet. Notes: Synchron-ization Force Whether to suspend the copy pair after the data is synchronized.
Pair command Options Force Item specified 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.
Pair command Options Item specified Specifiable values Default value Remarks When specified: YKRECVER. When not specified: YKDELETE. delete force Whether to set the pair status to Simplex from the SVOL. on, off The command cannot be used during a planned shutdown (during switching of the P-VOL and S-VOL). off Note: The Force Delete option changes the status of the secondary volume to simplex, but does not affect the status of the primary volume.
Pair command Options Item specified Specifiable values Default value Remarks on: A copy pair is created even when the S-VOL (or P-VOL when Reverse is specified) is online. Overwrite ONLINE target volume Whether to create a copy pair when the copy destination volume is online. Quick Restore Whether to immediately perform restoration. force The operation is performed on a volume basis. The command is executed for all pairs regardless of their status.
2. 3. 4. When a split operation is performed on Cnt Ac-A or Cnt Ac-J copy groups, if the value specified for the Direction option is different from the current copy direction, Synchronization cannot be specified. The default value displayed for the Secondary Mode option is the value defined for the copy group to which the target copy pair belongs. When a split operation is performed during I/O processing of the primary volume, it might result in incomplete data in the secondary volume.
Copy pair status categories Icon Copy pair status Meaning error An error occurred in the copy pair. suspend The copy pair is split. copying The copy pair is being copied in a forward or reverse direction. sync The copy pair is in a synchronized state. simplex Definition information for the copy pair exists, but the copy pair structure itself does not.
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) Split (SSWS) suspend error suspend/ error* suspend error error error -- Split (SUSPOP) suspend -- error error error -- -- suspend Split (HOLD) suspend -- error error error -- -- -- Split (PSUS or HOLD) suspend error error -- -- error error -- Suspending or Deleting (TRANS
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) Error (SUSPER) error error error error error error error Error (SUSPCU) error error error -- error error error Error (PDUB) -- -- -- error -- -- error Split (PFUS) -- -- -- error -- -- error Split (SSWS) copying suspend copying suspend copying copying copying Split (S
Conditions for determining copy pair status 3/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 Deleting (COPY or PAIR) Suspending (COPY or PAIR) Copying (COPY) or Copying (Pending or Resync) Invalid copying copying Error (PSUE or HLDE) error Error (SUSPER) Pair (PFUL) Pair (PAIR or PFUL) Pair (PAIR or PFUL) or Pair (DUPLEX) Simplex (SMPL) or Simplex (SIMPLEX) Unknown
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) Pair (PAIR or PFUL) or Pair (DUPLEX) copying copying Simplex (SMPL) or Simplex (SIMPLEX) copying Unknown copying Pair (PFUL) Pair (PAIR or PFUL) Pair (PAIR or PFUL) or Pair (DUPLEX) Simplex (SMPL) or Simplex (SIMPLEX) Unknown copying sync sync sync simplex sync copying copying copying copying copying simplex
Copy pair state of the primary volume Copy pair state of the secondary volume Invalid Error (PSUE or HLDE) Error (SUSPER) Split (PFUS) Split (SUSPVS) Split (SUSPOP) Split (PSUS or HOLD) Suspending or Deleting (TRANS) Deleting (COPY or PAIR) copying error error error suspend -- suspend copying Copying (COPY) or Copying (Pending or Resync) copying error error error suspend suspend suspend copying Copying (RCPY) or Copying (Resync-R) copying error error error suspend suspend s
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 Suspending or Deleting (TRANS) copying copying copying sync sync error copying Deleting (COPY or PAIR) copying copying copying sync sync error copying Copying (COPY) or Copying (Pending or Resync) copying copying copying sync sync error
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 RAID Manager Copy pair status in XP7 Remote Web Console Copy type BC/Snapshot/Cnt Ac-S/Cnt Ac-A/Cnt Ac-J PAIR PAIR Pair (PFUL)8 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 Snapshot: Snapshot/Fast Snap BC: Business Copy Cnt Ac-S: Continuous Access Synchronous Cnt Ac-A: Continuous Access Asynchronous Cnt Ac-J: Continuous Access J
Copy pair state Copy pair status in HP StorageWorks P9000 for Business Continuity Manager Software Error (SUSPER) SUSPER2 Copy pair status in XP7 Remote Web Console Copy type Suspended Cnt Ac-S/Cnt Ac-A 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
TIP: As of Replication Manager v6.3, mainframe pair status information can be obtained using Device Manager (without HP StorageWorks P9000 for Business Continuity Manager Software or XP7 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 12.
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.
• Changing the copy pair status for multiple copy pairs (batch operation), page 240 Pair status transitions (when the target is a copy group) The following table lists possible pair status transitions for each combination of copy pair state and copy type, when the target is a copy group.
Copy pair state Copying Business Copy Continuous Access Synchronous Continuous Access Asynchronous split split split resync resync resync restore restore restore delete delete delete -- -- split split split resync resync resync restore restore restore delete delete delete split split resync resync restore restore syncwait syncwait delete delete split split split resync resync resync restore restore restore delete delete delete split split split resync
--: 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.
Copy-on-Write Snapshot / Fast Snap FS (Snapshot Group) Copy pair state Split Deleting Suspending Copying Copying (Reverse) Pair (Full) Pair (PAIR or PFUL) Pair Simplex 230 Continuous Access Journal The same primary volume is shared1 The same primary volume is not shared2 split split split resync resync resync restore restore restore delete4 delete4 delete split split split resync resync resync restore restore restore delete4 delete4 delete split split split resync r
Copy-on-Write Snapshot / Fast Snap FS (Snapshot Group) Copy pair state Unknown Continuous Access Journal The same primary volume is shared1 The same primary volume is not shared2 split split split resync resync resync restore restore restore delete4 delete4 delete n/a -- Legend: 1. 2. 3. 4. This column lists the selectable copy pair statuses when the copy group contains copy pairs that have the same primary volume.
Pair statuses to which the pair status can be changed (when the target is a single or multiple copy pairs) Copy-on-Write Snapshot / Fast Snap 4 Copy pair state Error (PSUE) Error (HOLDER)3 Error in LUSE Split (Full) Split (SW) Split (HOLD)3 Split Deleting Suspending 232 Business Copy Continuous Access Synchronous Continuous Access Asynchronous split split resync resync restore Continuous Access Journal The Same Primary Volume Is Shared1 The Same Primary Volume Is Not Shared2 split spl
Copy-on-Write Snapshot / Fast Snap 4 Copy pair state Copying Copying (Reverse) Business Copy Continuous Access Synchronous Continuous Access Asynchronous split split resync restore delete The Same Primary Volume Is Not Shared2 split split split split resync resync resync resync resync restore restore restore restore restore delete delete delete delete delete split split split resync resync resync restore restore delete delete restore -- -- delete Pair (Full) Pair
restore: Indicates that the copy pair can be re-synchronized in reverse (from the secondary volume to the primary volume). 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. 4.
Details of copy group or copy pair statuses Business Copy Continuous Access Synchronous Continuous Access Asynchronous Continuous Access Journal Resync/Restore Resync/Restore Resync/Restore Resync/Restore Delete Delete Delete Delete Split (SWAPPING) Resync/Restore Resync/Restore Resync/Restore Resync/Restore Copying (Resync-R) Delete Delete Delete Delete Split (HOLD) - - - Error (HOLDER) - - - Delete Split (HOLTRNS) - - - Delete Split (NODELTA) - - - Split (SUSPVS)
TIP: When there are multiple pair statuses for the selected group or pair, the status is displayed if at least one pair is operable. 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.
Launching the Change Pair Status Wizard You can launch the Change Pair Status Wizard either using the Status button. icon or using the Change Pair 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.
5. For mainframe systems, perform the following operations on the Select Copy Pairs page to select specific types of copy pairs: 1. 2. 3. 4. On the Criteria tab, specify parameters for filtering the copy pairs. Click Apply. The Results tab displays the list of filtered copy pairs. On the Results tab, select the check boxes of the copy pairs whose status you want to change. Click Next. The Select Pair Operation page appears. 6.
when you select a copy pair, all the related copy pairs are displayed in a list. From this list, you can select the copy pairs whose status you want to change. 1. For copy groups or containers: Display the information about the host or configuration definition file where you want to change the status of copy pairs. For details on how to display this information, see “Viewing individual host information” on page 308 or “Viewing copy pair configuration definition information” on page 285.
12. ClickFinish. The settings specified in the wizard are registered as tasks. Check the Status column for the tasks to make sure that the pair status was changed successfully. To view the tasks, from the Explorer menu, select Tasks and then Tasks.
5. For mainframe systems, perform the following operations on the Select Copy Pairs page. To select specific types of copy pairs: 1. 2. 3. 4. On the Criteria tab, specify parameters for filtering the copy pairs. Click Apply. The Results tab displays the list of filtered copy pairs. On the Results tab, select the check boxes of the copy pairs whose status you want to change. Click Next. The Select Pair Operation page appears.
Confirming copy status during task execution To confirm copy status during task execution: 1. In the Explorer menu, choose Tasks and then Tasks. A list of tasks is displayed in the Tasks subwindow. 2. Select a task and click the copy group name hot link. The copy-group-name subwindow is displayed 3. Confirm the copy progress and whether the pair is in Copying status. 4. After several minutes, click Refresh Copy Group. 5. Confirm whether the pair is in Pair status. 6.
NOTE: For more information on the underlying functions used by the advanced operations, see “Advanced operations and corresponding RAID Manager commands” on page 252. The advanced operations are as follows: • • • • Takeover operation, page 243 Swap operation, page 244 Force-split operation, page 244 Takeover-recovery operations (resync and recreate), page 245 CAUTION: Take note of the following points: • Advanced operations can be performed per copy group or per copy pair.
The takeover procedure is as follows: 1. If the copy pair state is Unknown, a failure may have occurred. Check for failures outside of Replication Manager. 2. Using the Change Pair Status Wizard, create a takeover Change Copy Pair Status task for the target copy group or copy pair. 3. Check the Task List window to confirm that the status of the task is Success. 4.
The force-split procedure is as follows: 1. 2. If the primary volume cannot be written to, an RC circuit or secondary site failure might have occurred. Check for the following in Replication Manager: • An abnormal remote path status (possibly an RC circuit failure) • An Unknown copy pair status in the secondary volume (possibly a secondary site failure) Using the Change Pair Status Wizard, create a force-split Change Copy Pair Status task for the target copy group or copy pair. 3.
Advanced recovery use cases The following table lists the use cases for advanced recovery procedures and includes references to the diagrams in Figure 6 and Figure 7. Table 16 Advanced recovery scenarios and procedures Scenario Procedure using the Change Pair Status Wizard Workflow reference Performing maintenance on the primary site work server 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 storage failure (no loss of primary site data) To switch work to the secondary site, execute an advanced takeover operation. The secondary volume on the secondary site is changed to a writable Split (SSWS) status.
Figure 6 Takeover workflow Figure 7 Takeback workflow 248 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 8 Alert settings and volume reversal Alerts set for copy group CG1 are not valid for the copy group CG1 with reversed primary and secondary volumes. If you reverse the primary and secondary volumes for copy group CG1, the alerts set for copy group CG1 become valid once again. NOTE: When primary and secondary volumes are reversed, the copy group name is the same both before and after the reversal.
Change Pair Status Wizard RAID Manager Operation Command Option Read disable (secondary) Option -m noread To specify CTGID at the same time: -m grp CTGID Assign CTG for At-Time Split1 Otherwise use: -m To specify CTGID at the same time: -fg fencelevel CTGID Assign CTG2 Otherwise use: -fg fencelevel CTGID See the two previous options for specifying the CTGID.
Conditions for copy pair operations (basic versus advanced) Available copy pair operations depend on the storage system type and volume status. Basic operations The following operations and storage system configurations are not supported for basic operations: • A create or delete operation for a copy group defined in a device group. • The storage system type is XP24000/XP20000, HP P9500, or XP7 and the copy pair is a HAM copy pair.
Change Pair Status Wizard RAID Manager Description Operation Option Command Option None Execute these commands in the following order: n/a swap Copy Pace takeover-recovery (resync) None Copy Pace Redirects copying, retaining the current copy pair state. Recovers an S-VOL from the Split(SSWS) status and the P-VOL and S-VOL to the Pair(PAIR) status. 1. pairsplit 2.
• RAID Manager response time and virtual command devices, page 258 About virtual command devices Command devices are used to send RAID Manager commands between the pair management server and a storage system. Command devices use the FC link (known as an in-band connection). Virtual command devices allow you to perform the same operations using the LAN (known as an out-of-band connection).
The following figure shows a Virtual Command Device server configuration. The server connected to the actual command device is set as the virtual command device on each pair management server or application host. The Virtual Command Device server can be the same machine as the RAID Manager server. Figure 10 Configuration with Virtual Command Device server Prerequisites for virtual command device configurations The following requirements apply to virtual command device configurations.
Target Pair Management server Storage system Prerequisite Device Manager agent 7.1.0 or later and RAID Manager 01-25-xx/xx or later must be installed. The configuration definition file is in a format that is supported by Device Manager agent, and the RAID Manager instance must have started normally. The serial numbers of the storage systems managed by the Device Manager server must be unique.
To set up an SVP as a virtual command device: 1. Change the account used for execution of the Device Manager agent service to an account with Administrator permission. (The default is the LocalSystem account.) 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.
6. Perform a storage refresh from Device Manager. 7. If you using a remote Device Manager, follow the procedure for “Refreshing configuration information manually for each information source” on page 279. 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 RAID Manager authentication is enabled, you must execute the OS commands described in this procedure: 1. Start the RAID Manager instance that will be used by Application Agent: P9000-RAID-Manager-instance-location\etc\horcmstart P9000-RAID-Manager-instance-number 2.
Monitoring and management of copy groups defined by device group Copy groups defined by device group enable you to manage the LDEVs in a storage system as a single entity, allowing operations to be performed in batch mode. NOTE: As of release 7.1.
Prerequisites for copy group configurations defined by device group The following requirements apply to copy groups defined by device group. Target Prerequisites • The management server has been discovered as a pair management server in Replication Manager on the pair management server. (If performing discovery of copy groups defined by device group at a remote site, you also need to refresh the Device Manager configuration on the remote site.
raidvchkdsp –g Grp01 –d vol01 -v gflag Group PairVol Device_File Seq# LDEV# GI-C-R-W-S PI-C-R-W-S R-Time Grp01 vol01 Harddisk1 2332 3 D E E E E E E E E E – Proceed to step 2 only if the value of the GI attribute is D (INQUIRY is not allowed). 2. Release the INQUIRY of the primary volume as in this example: raidvchkset –g Grp01 –d vol01 -idb 3.
Installation-destination-of-Application Agent\DRM\log\drm_pp_traceX.log 5. 6. Select the process of RAID Manager in the Image Name column of the Processes tab. Click End Process. Unsupported copy group configurations defined by device group The following configurations are not supported: • The number of volumes differs between copy groups defined by device group. • The device name of a copy-pair target volume differs from that of a copy-pair source volume.
Managing pair life cycle
11 Refreshing management information This chapter describes ways to refresh configuration and copy pair status information. About refreshing management information To maintain operability, Replication Manager has its own database for storing information about managed resources.
If you change the replication configuration, make sure that you refresh the configuration information before you refresh the copy pairs.
Explorer menu Permissions Submenu Menu command Admin Modify View My Groups My Copy Groups Y Y Y Settings Refresh Setting Y Y N Administration Maintenance Y N N Legend: Y: Can be executed with this permission. N: Cannot be executed with this permission.
Copy pair statuses can be refreshed manually (from a subwindow) or automatically (at an interval preset in the refresh settings). Normally, refreshing takes anywhere from a few to tens of minutes total. However, if the Device Manager refresh function is used (because there are copy pairs not managed by pair management servers in open systems), refreshing can require anywhere from a few to tens of minutes for each storage system.
Refreshing copy pair statuses data flow (mainframe systems) The following figure shows the flow of data when copy pairs are refreshed in mainframe systems.
Disabling the Device Manager refresh function In open systems where all copy pairs are managed by pair management servers, you should prevent the Device Manager refresh function from executing during a manual refresh. If this function is used to refresh copy pair statuses, processing time increases. TIP: If copy pairs have been defined using storage management software such as XP7 Remote Web Console, no configuration definition file exists. Such copy pairs are not managed by pair management servers.
4. Select the Do not execute a Device Manager refresh operation during a manual refresh operation check box, and then apply the new settings. The settings specified in the Monitoring Setting subwindow are updated. Thereafter, a manual refresh acquires information from the Device Manager agent on each pair management server (not from the database of the instance of Device Manager on the management server).
Refreshing copy pair statuses manually for each copy group or snapshot group To refresh copy pair statuses manually on the basis of copy group or snapshot group: 1. Display the information about the desired copy group or snapshot group. For details, see “Viewing information about copy groups or snapshot groups belonging to a host” on page 311 or “Viewing information about copy groups belonging to a copy pair configuration definition” on page 309. 2.
Refreshing the copy pair status automatically for each information source In open systems, the refresh interval (the interval for collecting information) can be set either for each pair management server or for each Device Manager server that is an information source. In mainframe systems, the refresh interval can be set for each instance of HP StorageWorks P9000 for Business Continuity Manager Software or XP7 mainframe agent that is an information source. You can also disable periodic refreshing.
To refresh copy pair statuses automatically on a pair management server basis: 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 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.
For a local instance of Device Manager, this synchonization is always performed as needed (so there is no need for manual or scheduled refresh operations).
TIP: Replication Manager does not regularly check whether instances of HP StorageWorks P9000 for Business Continuity Manager Software or XP7 mainframe agent registered as information sources have refreshed their storage systems configurations. When a storage system managed exclusively by HP StorageWorks P9000 for Business Continuity Manager Software is refreshed, the information is provided by HP StorageWorks P9000 for Business Continuity Manager Software or XP7 mainframe agent.
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. NOTE: Only remote instances of Device Manager are displayed. The local instance of Device Manager is refreshed automatically.
To refresh configuration information automatically: 1. From the Explorer menu, choose Settings and then Refresh Setting. The Refresh Setting subwindow appears. 2. Click the Configuration Setting link. The Configuration Setting subwindow appears. 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.
2. Select a storage system and click Refresh Storage System. The configuration information displayed in the Storage Systems view subwindow is refreshed. For details, see “Viewing a list of storage systems” on page 307.
12 System monitoring Replication Manager provides multiple ways to monitor the operating status of the replication environment. You can monitor frequently viewed copy groups, check pair statuses, pair configurations, and the performance of remote copies. This chapter describes the different types of system monitoring functions supported by Replication Manager. About system monitoring Replication Manager allows you to perform the following types of system monitoring functions.
Monitoring resource utilization You can monitor the usage ratio of buffers (pools and journal groups) and receive alerts by email or SNMP traps based on the predefined thresholds. If you are an administrator, you can add volumes to the buffers using Replication Manager. Monitoring copy license usage You can monitor the used capacity and copy license usage percentage for each copy product in complex replication environments.
Checking copy pair configurations Replication Manager provides multiple ways to check copy pair configurations. For details on how to check copy pair configuration, see: • Checking copy pair configuration definitions, page 283 • Checking copy pair configuration (perspective of specific volume), page 284 • Checking copy pair configuration (perspective of specific copy group), page 285 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 configuration definition is displayed. Related topics • Viewing a list of copy pair configurations, page 306 • About configuration definition file formats, page 148 Viewing prefix information (mainframe systems) To view prefix information: 1.
you can specify an alert is sent when a given error status is detected. In this case, an alert is sent when any of the copy pairs belonging to the copy group enters the error status. TIP: Because you can receive alerts by way of email or SNMP traps, you can also monitor the replication environment without being logged on to Replication Manager.
Icons representing the relationship between a volume and a copy group or snapshot group Replication Manager uses icons to represent volumes, copy groups, and snapshot groups, along with arrow icons to indicate the relationship between a volume and a copy group or snapshot group. Icons representing the relationship between a volume and copy group or snapshot group Icon Description Indicates a primary volume. When a group of related volumes is displayed, the currently selected volume is highlighted.
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 291. • “Checking status of copy pairs for a volume in a storage system” on page 291. Related topics • Copy pair status check workflow, page 290 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.
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. Selecting the volume displays information about that volume. For mainframe systems, before selecting the volume, select the applicable LDKC and then the CU for the model. 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.
Monitoring performance of remote copies Replication Manager can monitor the usage ratio of buffers to avoid the overflow of the buffers and maintain data consistency. You can get notification through SNMP email, based on the predefined threshold. If you are an administrator you can add volumes to the buffers using Replication Manager. Replication Manager can also be used to monitor asynchronous remote copying performed using Continuous Access Asynchronous or Continuous Access Journal.
Checking the performance of remote copies TIP: You can check the performance of remote copies when system operation uses asynchronous remote copy functionality. See “About performance monitoring” on page 293 for more information. For details on how to check performance of remote copies, see the following: • “Checking buffer usage (pools and journal groups)” on page 297. • “Checking buffer usage (sidefiles and journal volumes)” on page 297.
rate is displayed according to the copy type or copy pair status. The following table lists the values displayed to indicate the copy progress.
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 Refresh Hosts to refresh the information when necessary. 2. Select a configuration definition file or prefix.
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 data protection status, page 299 Data protection status example, page 299 About aggregation rules for protection status, page 300 Excluding objects from data protection status monitoring, page 301 About data protection status The protection status display allows quick identification of the cases shown in the table. Table 20 Protection status Status Icon Description Normal The latest replica is current (the last scheduled replica was successful).
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 2007), information stores (Exchange 2010/2013), 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 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.
14 Managing resources This chapter describes different methods for managing resources. Resource management functions The following table describes the resource management functions, user permissions (Replication Manager management), and whether the functions can be used with the indicated permissions.
Permissions Function Admin Modify View Viewing copy pair configuration definition information Y Y Y Viewing information about copy groups belonging to a copy pair configuration definition Y Y Y Legend: Y: Can be used with this permission. N: Cannot be used with this permission. TIP: Each function can be used only for the resources in resource groups associated with the user.
• Viewing copy pair configuration definition information, page 285 • Structure of the Pair Configurations view, page 47 Viewing a list of copy pairs associated with a task You can view the list of copy pairs associated with a task to confirm copy status before or during task execution or to investigate the pair configuration or status of a selected copy group. To view the list of copy pairs associated with a task: 1. In the Explorer menu, choose Tasks and then Tasks.
Viewing a summary of storage systems You can display the following summary information for each storage system: • Storage system summary Information such as the storage system type and serial number is displayed. • List of platforms Information such as the license registration status of each copy type and the information sources is displayed for each platform (mainframe or open systems). To view a summary of storage systems: 1. From the Explorer menu, choose Resources and then Storage Systems.
For mainframe hosts: • List of volumes (DEVNs) 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 copy group definition files (prefixes) belonging to the host To view host information: 1. From the Explorer menu, select Resources and then Hosts. The Hosts subwindow appears. 2.
• Copy group summary • List of copy pairs belonging to a copy group • Copy group relationships Related topics • Viewing copy group information in the Hosts view (open systems), page 312 • Viewing copy group information in the Pair Configurations view (mainframe systems), page 310 Icons representing a copy topology Replication Manager uses icons to represent a copy topology. The following table lists and describes these icons. Icon Description Indicates a copy group or snapshot group.
• Viewing copy group information in the Hosts view (mainframe systems), page 311 Viewing copy group information in the Pair Configurations view (open systems) To view copy group information (open 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.
4. Select a copy group. The information about the selected copy group is displayed. Related topics • Viewing copy group information in the Pair Configurations view (mainframe systems), page 310 Viewing copy group information in the Hosts view (open systems) To view copy group information (open systems): 1. From the Explorer menu, choose Resources and then Hosts. The Hosts subwindow appears. 2. Expand the object tree, and then select a host under Hosts. The host-name subwindow appears. 3.
To view prefix information: 1. From the Explorer menu, choose Resources and then Hosts. The Hosts subwindow appears. 2. Expand the object tree, and then select a host under Hosts. The host-name subwindow appears. 3. On the Prefixes page, select a prefix. The information for the selected prefix is displayed in the prefix-name subwindow.
• CU summary The capacity of each CU is displayed. • List of volumes (LDEVs) belonging to a CU Information such as the serial number and capacity is listed for each volume. To view CU information: 1. 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 Mainframe link. The Mainframe subwindow appears. 4.
6. Select an LDEV. The information about the selected LDEV is displayed in the LDEV-name subwindow. LDEV display format The LDEV number is displayed in hexadecimal, as explained below. If the LDEV number is a single-digit number, a leading zero is added (0A for example) so that it will be displayed as a 2-digit number.
• Viewing information about volumes belonging to a host, page 313 Viewing storage system information (mainframe systems) To view storage system information (mainframe 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. Click the Mainframe link.
Viewing information about LDKCs belonging to a storage system (mainframe systems) You can display the following information about the LDKCs used in mainframe storage systems that support them: • LDKC summary The capacity of each LDKC is displayed. • List of CUs belonging to an LDKC The capacity of each CU is listed. To view LDKC information: 1. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 2.
Managing resources
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 319 • Deleting V-VOLs, page 319 • Deleting multiple V-VOLs, page 319 Conditions for deleting V-VOLs The following restrictions apply when deleting a V-VOL: • The V-VOL must not be part of a pair configuration. • The V-VOL must not have a path defined to any host.
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 P9500 or XP7 storage system (regardless of CVS installation) only one V-VOL can be created in a single Parity Group. Therefore, if you delete a V-VOL, the Parity Group containing the V-VOL is also deleted.
Deleting command devices To delete command devices: 1. From the Explorer menu, choose Resources and then Storage Systems. The Storage Systems subwindow appears. 2. Expand the object tree, and then select a storage system under Storage Systems. The storage-system-name subwindow appears. 3. Click the Open link. The Open subwindow appears. 4. On the Cmd Devs page, select the check boxes of the command devices you want to delete, and then click Delete Cmd Devices.
• About remote paths, page 111 About deleting remote paths Remote paths can be deleted by performing the following operations: • Deleting the associated copy pair. Using this operation, you delete the copy pair that uses the remote path that you want to delete. By default, this method deletes the configuration definition file that defines the copy pair. You can also specify an option to only release the pair (placing the copy pair in simplex status) while retaining the configuration definition file.
A copy pair that is reserved for performing other copy pair operations cannot be deleted. You must first delete the applicable tasks and workflows. For details, see “Deleting tasks” on page 181 and “Deleting workflows” on page 186. • The copy pair of mainframe volumes exist: The copy pair specified by HP StorageWorks P9000 for Business Continuity Manager Software or XP7 mainframe agent cannot be deleted using Replication Manager. Delete the copy pair with the software that was used to set up the copy pair.
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 114. 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 296. 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 113 • Pool usage threshold values, page 296 Managing journal groups This module describes tasks for managing journal groups: • • • • Editing journal groups, page 325 Deleting journal groups, page 325 Expanding journal group capacity, page 326 Editing a warning banner, page 371 Editing journal groups You can edit journal group information (journal volumes and journal group options).
3. Click the Open link. The Open subwindow appears. 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 your selections, and then delete them. The information in the display is updated. Related topics • About journal groups, page 117 • Editing journal groups, page 325 Expanding journal group capacity To expand capacity of a journal group: 1.
• About journal groups, page 117 • Storage system types and volume requirements (journal), page 117 • Editing journal groups, page 325 Changing the maximum number of initial copy activities The Maximum Initial Copy Activities limits the number of volumes that can be copied at one time during initial copy and resynchronization operations. NOTE: A new setting only applies to pairs created after the setting was changed, not to existing pairs. To change the maximum value: 1.
Managing storage systems
16 Managing sites This chapter describes tasks for managing sites. About site administration In a complex replication environment, storage systems can be located at many sites. In such cases, you can create logical sites whenever necessary by grouping resources. Grouping resources based on the actual sites simplifies resource management because you can then use a graphical user interface for management.
Site management functions The following table describes the site management functions, user permissions (Replication Manager management), and whether the functions can be used with the indicated permissions.
Explorer menu Permissions Submenu Menu command Admin Modify View Shared Views Sites Y Y Y Legend: Y: Can be executed with this permission. Viewing a list of sites To view a list of registered sites, from the Explorer menu, choose Shared Views and then Sites. A list of registered sites is displayed in the Sites subwindow. Viewing individual site information You can display information about individual sites.
4. Edit and update the site information. The site information displayed in the Sites subwindow is refreshed. Related topics • Adding hosts to a site, page 92 • Adding storage systems to a site, page 93 • Adding pair management servers to a site, page 94 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 334 • Deleting multiple sites, page 334 Related topics • Removing hosts from a site, page 332 • Removing pair management servers from a site, page 333 • Removing storage systems from a site, page 332 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 123 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.
Related topics • About alert settings, page 123 • Viewing alerts and settings, page 336 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.
3. Confirm the alerts that will be set as completed, and then set them as already read. The number of alerts displayed in the Completed/Not Completed column and Dashboard menu in the Alerts subwindow is updated. Related topics • About alert settings, page 123 Deleting alert settings To delete alerts: 1. From the Explorer menu, choose Alerts and then Alerts. The Alerts subwindow appears. 2.
Managing alerts
18 Managing licenses This chapter describes tasks for license management. About licenses Licenses must be registered for the storage systems managed by Replication Manager. The following table describes the types of license keys. Types of license keys Type Description Permanent A license key required to use a product permanently. Permanent license keys are provided for each storage system that is to be managed by Replication Manager.
Explorer menu items for license management The following table shows the Explorer menu items that are related to license management, user permissions, and whether the items can be executed with the indicated permissions. Explorer menu Permissions Submenu Menu command Admin (user management) Admin, modify, or view (Replication Manager management) Settings License Info Y Y Legend: Y: Can be executed with this permission.
Related topics • About licenses, page 341 • Viewing license information, page 342 User Guide 343
Managing licenses
19 Managing users and permissions Replication Manager provides role-based user access control to secure protection processes and recovery operations and mitigate the risk of unauthorized operations. To achieve stringent access control and efficiency, multiple users can be allocated access to functions on the basis of their role in the organization. User permissions can be assigned for different categories such as Storage Administrator, Database/Server Administrator and Super User (RepMgr Administrator).
Explorer menu items for user management The following table describes the Explorer menu items that are related to managing users, user permissions, and whether the menu command can be executed with the indicated permissions. Explorer menu Permissions Submenu Menu command Admin (user management) permission Admin, modify, or view (Replication Manager management) permission Administration Users and Permissions Y N Legend: Y: Can be executed with this permission.
• User profile (information such as the user ID and full name) • List of permissions specified for each HP XP7 Command View AE Suite product To view the information for an individual user: 1. From the Explorer menu, choose Administration and then Users and Permissions. The Users and Permissions subwindow appears. 2. Expand the object tree, and then select a user ID under Users. Information about the user with the selected user ID is displayed in the user-ID subwindow.
Changing user roles To change the roles assigned to users: 1. From the Explorer menu, choose Administration and then User Roles. The User Roles subwindow appears. TIP: As with other menus under Administration, only users with Admin permission can access this window. The “User Roles” table lists all users with access to Replication Manager. • When no user role is assigned, the “Role” field is empty and the user is equivalent to the “Storage Administrator” role (with no restrictions).
3. Click Edit Profile. The Edit Profile - user-ID dialog box appears. 4. Edit and update user information. The user information displayed in the user-ID subwindow is refreshed. If the new user information is not applied immediately to the list of users in the Users subwindow, you can click Refresh Tree to refresh this information in the navigation area.
Deleting multiple users TIP: Do not delete the user account that is used for communication between Device Manager agents and the Device Manager server (default: HaUser). To delete multiple users: 1. From the Explorer menu, choose Administration and then Users and Permissions. The Users and Permissions subwindow appears. 2. Expand the object tree, and then select Users. The Users subwindow appears. 3.
• Viewing a summary of user permissions, page 351 • Changing user permissions, page 82 Viewing a summary of user permissions You can display summarized information about all HP XP7 Command View AE Suite products that have been installed. The displayed information includes the number of registered products and the number of users. To view a summary of user permissions: 1. From the Explorer menu, choose Administration and then Users and Permissions. The Users and Permissions subwindow appears. 2.
Permissions Admin (user management) permission Admin, modify, or view (Replication Manager management) permission Editing user profiles Y Y Changing user passwords Y Y Function Legend: Y: Can be used with this permission. Explorer menu items for user profile management The following table describes the Explorer menu items that are related to user profile management, user permissions, and whether the items can be executed with the indicated permissions.
3. Edit and update user information. The user information displayed in the User Profile subwindow is refreshed. If the new user information is not applied immediately to the list of users in the Users subwindow, you can click Refresh Tree to refresh this information in the navigation area.
• Changing the user authentication method, page 358 • Using an external authorization server (authorization groups), page 358 About account locking To prevent unauthorized individuals from logging in, you can set the system to automatically lock user accounts when invalid passwords are entered a specified number of times in succession.
• By default, the built-in account (user ID: System) cannot be locked. To enable locking of this builtin account, edit the user.conf file on the management server. For details about the user.conf file, see the HP XP7 Replication Manager Configuration Guide. • In HP XP7 Command View AE Suite products, you cannot change the lock status of a user that logs in by linking to an external authorization server because such an account has not been registered in the HP XP7 Command View AE Suite products.
4. Confirm the users whose accounts you want to unlock, and then unlock the accounts. The lock statuses of the users displayed in the Users subwindow are refreshed. NOTE: If you select a user account that is locked because no password has been set, the user account cannot be unlocked. If you set a password, the user account will be unlocked.
Linking to an external authentication server To link to an external authentication server: 1. On the Device Manager management server, specify settings for linking to an external authentication server. For details about requirements for an external authentication server and how to specify settings for linking to the server, see the HP XP7 Replication Manager Configuration Guide. 2. Register the user IDs and passwords used by HP XP7 Command View AE Suite products in the external authentication server.
Changing the user authentication method To change the method for user authentication: 1. From the Explorer menu, choose Administration and then Users and Permissions. The Users and Permissions subwindow appears. 2. Expand the object tree, and then select Users. The Users subwindow appears. 3. In the list of users, select the check boxes of the users for whom you want to enable or disable linkage to the external authentication server, and then click Change Auth.
Registering an authorization group To manage user accounts per authorization group, register authorization groups in the HP XP7 Command View AE Suite products. You cannot register only authorization groups that are already registered in the authorization server. You must first register authorization groups in the HP XP7 Command View AE Suite products, then register them in the authorization server. By default, All Resources is assigned to the authorization group as the resource group.
NOTE: The following restrictions apply. Permissions: When the Modify permission is granted to an externally authenticated group, detailed permissions (permission per operation provided by the User Role function) for users who belong to the group are set to the default value ("Storage Administrator") and cannot be changed. Resource Group: Users belonging to the externally authenticated group are assigned to the resource group All Resources, and this setting cannot be changed.
20 Managing resource groups This chapter describes the tasks for Resource Group management. About resource group management Resource groups can be managed only by users with the Admin (Replication Manager management) permission. Users other than the System built-in account can only use the resources in the associated resource groups, the configuration definition of those resources, and alerts.
Permissions Function Admin Modify View Adding applications to a resource group Y N N Removing applications from a resource group Y N N Legend: Y: Can be used with this permission. N: Cannot be used with this permission. Explorer menu items for resource group management The following table describes the Explorer menu items that are related to resource group management, user permissions (Replication Manager management), and whether the items can be executed with the indicated permissions.
Viewing a list of resource groups To view a list of registered resource groups, from the Explorer menu, choose Administration and then Resource Groups. Registered resource groups are listed in the Resource Groups subwindow.
4. Confirm the hosts to be removed, and then remove them. The selected hosts are removed from the Hosts page. Related topics • About resource groups, page 83 • Adding hosts to a resource group, page 85 Removing storage systems from a resource group You can remove storage systems registered as resources from their resource groups. NOTE: You cannot remove storage systems from the All Resources group, which is the resource group in which all storage systems are automatically registered.
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. The Remove Users - resource-group-name dialog box appears. 4. Confirm the users to be removed, and then remove them. The users are removed from the Users page.
NOTE: You cannot delete the default resource group All Resources, which is the group in which all resources are automatically registered. The following topics are included in this module: • Deleting individual resource groups, page 366 • Deleting multiple resource groups, page 366 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.
21 Managing security This chapter describes tasks for managing security. About security settings Replication Manager provides security functions that allow you to perform the following: • Set password conditions to prevent users from using easy-to-guess passwords. • Enable automatic locking of user accounts for which successive login attempts have failed. • Display a user-specified message (a warning banner) in the user login window at login time as a security measure.
Explorer menu items for setting security The following table shows the Explorer menu items that are related to setting security, user permissions, and whether the items can be executed with the indicated permissions. Explorer menu Permissions Submenu Menu command Admin (user management) permission Admin, modify, or view (Replication Manager management) Administration Security Y N Legend: Y: Can be executed with this permission. N: Cannot be executed with this permission.
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. Expand the object tree, and then select Password under Security.
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 370 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
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 XP7 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 desired information. The display is refreshed to reflect your changes.
Editing an instance of HP StorageWorks P9000 for Business Continuity Manager Software or XP7 mainframe agent To edit an instance of HP StorageWorks P9000 for Business Continuity Manager Software or XP7 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.
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 304. For details on how to manually clear the alert settings, see “Deleting alert settings” on page 339. Related topics • About information sources, page 51 Removing information sources workflow The following figure shows the flow of tasks for removing information sources.
3. Select the check boxes of the Device Manager servers you want to delete, and then click Remove DevMgrs. The Remove Device Managers dialog box appears. 4. Confirm your selections, and then delete them. The information in the display is updated.
Related topics • Adding an instance of Application Agent, page 56 • Refreshing Application Agent, page 63 • Setting Application Agent options, page 57 Acquiring the latest configuration information (configuration refresh) Whether you need to refresh the configuration and synchronize the configuration information of Replication Manager and Device Manager depends on the source of the acquired information for managing the storage system: • When the source of the acquired information for managing the storage s
User Guide 379
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.
the same way that backup tapes are created and later re-used. This (default) behavior is determined by the Target Generation option located on the 2. Setup Options page of the Create Replica Wizard. When selecting a secondary volume for a backup, you can either manually select the volume you want or use the default. To have Replication Manager choose a secondary volume for you, you need to use the volume copy function.
Figure 13 Backup and restore operations Related topics • Creating an application replica, page 403 • Restoring the latest application replica (simple restore), page 410 About storage groups and information stores Storage groups are objects managed by Microsoft Exchange 2007 to store databases. Multiple databases can be managed together because databases within the same group use a common transaction log.
Exchange 2010/2013 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.
Mount points If different logical volumes are mounted in multiple mount points with a hierarchical relationship (such as M:\ and M:\MNT) do not specify a mount point that includes a lower level directory mountpoint (for example, M:\ in the above instance) as the target of replication. If this is done, the replica creation fails and the error message (KAVX0006-E, DRM-10062) is output.
Database and backup server time synchronization The database server time and backup server time should be set to the present time, or the task status related to replica management operation is not updated correctly. If the time zone of the database server and backup server is changed, from the Explorer menu, choose Administration and then Information Source. Choose the relevant server, and then click Refresh Agent to update the information.
SQL Server database instances and physical volumes Because SQL Server replicas operate on individual physical volumes, the object configuration of SQL Server databases must meet the following requirement: • 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.
data exists on the secondary volume.The following is an example of two objects (databases, storage groups, or information stores) stored in separate volumes: • Database A (copy group: vg01,obj01) • Database B (copy group: vg01,obj01) Use the following backup method to back up the databases: 1. Back up database A and database B concurrently. The replica 2010/8/31 07:14:00 is created. 2. Back up database A only. The replica 2010/9/06 08:15:00 is created.
• The configuration definition file for RAID Manager is changed (excluding changes made with Replication Manager). NOTE: After using a RAID Manager command to change the configuration of a copy pair, you should also execute a Refresh Storage System for the relevant storage system. For more information, see “Refreshing configuration information manually for each storage system” on page 279. • • • • • • • • The mount point (drive letter for Windows) is changed.
• Do not use LUN#0 as a secondary volume for the backup destination, or other disks may not be recognized. • To back up an SQL Server instance, the instance must be online. If an attempt is made to back up an instance when it is not running, the attempt will fail.
Event type: Warning Event source: ftdisk Event ID: 57 Event type: Warning Event source: disk Event ID: 51 Event type: Warning Event source: ntfs Event ID: 50 These messages are displayed because the secondary volume is temporarily hidden during the backup. They have no impact on the operation and can be ignored.
Event source : Virtual Disk Service Event ID : 1 Description : Unexpected error. Error code : 48F@02000018 Event type : error Event source : Disk Event ID : 15 Description : The Device XXXXXXXXXXXX is not the status that can be accessed.
• If the primary volume drive is being opened from an external computer, exit the application opening the drive. • The primary volume might have been opened by a memory-resident monitoring program. If this is the case, stop the monitoring program. • If Management Studio has been used to view the database to be restored, use Enterprise Manager to detach from the database or exit Management Studio before the restoration.
Figure 15 When the primary volume for BC and the primary volume for Cnt Ac-A are the same LDEV When using the configuration shown in Figure 15 to restore the paired volume for Business Copy, set the status of the paired volume for Continuous Access to SMPL or PSUS (SSUS). If you attempt to restore the pair volume for Business Copy with the status of a pair volume for Continuous Access PAIR, an error message indicating that the status of the copy group is invalid is displayed and the restore operation fails.
NOTE: Define one consistency group as one group (dev_group) of RAID Manager configuration definition files so that there are never too many or too few copy groups. For Exchange databases When restoring individual information stores: Define consistency groups to make each information store of data files (*.edb) in the same consistency group. In addition, define consistency groups to make the transaction log files and checkpoint files (*.log, *.chk) of each storage group in the same consistency group.
• The files to be backed up must all be placed on a RAID volume defined as a pair. • For Exchange 2007 servers, deploy the storage group taking into consideration that backups are conducted in units of volumes. If you deploy multiple storage groups in the same volume, you need to back up or restore these storage groups as one group. When backing up or restoring a storage group separately, deploy the storage group on a separate volume.
NOTE: You can still search for items using Outlook (cache mode). After you resume the Microsoft Exchange Search Host Controller service, the index operation is also resumed. However, it may take longer than usual for the status to change from Failed to Healthy and to enable email search. 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.
However, do not use the following characters:\ / : , ; * ? < > | “ • Do not use names in the following form for database data files: META_database-ID.dmp Where database-ID is a 10-digit number. • In a cluster environment, specify a user on each node for the owner of a database subject to backup. Local users with the same user name and password on different nodes are not considered to be the same user. Therefore, use a domain user account that is common to all nodes.
• Tracking of changes • Compressing backup database and transaction log • Compressing data The following functions are not supported for SQL Server 2012: • • • • • • • FILESTREAM data Capturing changed data Tracking of changes Compressing backup database and transaction log AlwaysOn failover cluster instance AlwaysOn Availability Groups Server Core Allocating files that comprise a database Do not place database files to be backed up in the same volume as files that will not be backed up.
For best results, store metafiles in a volume belonging to an SQL Server resource group so that, even if an SQL Server cluster resource fails over, the metafiles are failed over with the resource group. The following figure shows a sample location for metafiles in an active/standby (or active/passive) cluster configuration.
NOTE: Do not run RAID Manager commands while Replication Manager is executing replica operations. Windows Indexing Service (cisvc.exe) Observe the following precautions with the indexing service: • Confirm that the master binder of the index service is not operating. File access by the index service can conflict with file operations of Replication Manager, which can cause an error in the index service master binding or in replica creation or restore processing.
Figure 18 Create application replica workflow About the Create Replica Wizard Replication Manager includes a Create Replica Wizard for creating snapshots of application servers. The Create Replica Wizard provides the following functions: • Choose to create a new task or edit an existing one, and select target objects. • Set options including the rotation of target volumes, execution options, and mount options (for tape backups). • Schedule the execution of the task.
Creating an application replica To create an application replica: 1. From the Explorer menu, select Resources, and then Applications. The Applications subwindow appears. 2. Expand the object tree and select a server. The summary information for the selected server is displayed. 3. Select one or more application resources: storage groups (Exchange 2007), information stores (Exchange 2010/2013), or database instances (SQL Server) and click Create Replica. The Create Replica Wizard is launched. 4.
8. The 3. Set Schedule page is displayed. 1. 2. To create the replica immediately (without a recurring schedule) select Execute immediately. For scheduled replica creation (single or recurring), select Execute on schedule, choose a Schedule Type, and select the applicable calendar options. NOTE: Do not create a schedule that will cause a copy pair to re-synchronize.
• Point-in-time When backup data on an Exchange Server or SQL Server database server is restored, the database returns to the state at the point-in-time when the backup occurred. If the transaction logs from the time when the backup was executed up until the restore are stored on the primary volume, the uncommitted transactions can be applied using the roll-forward option. By applying the transaction logs after backup, the database is restored to a state immediately before the error occurred.
Figure 19 Flow of operation using transaction logs (Roll-forward) After the database is backed up from the primary volume to the secondary volume at point A, the database is updated at point B. If an error occurs in a data file on the primary volume at point C and then the database is restored from the secondary volume to the primary volume, the database returns to the state it was in at point A.
Figure 20 Restoring data in units of information stores by applying transaction logs (roll-forward) The prerequisites for this example are the same as for the previous scenario, plus the following: • Only the data files (*.edb ) 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) 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: When data files (*.
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 411. To perform a simple restore of the most recent replica: 1. If you are restoring a replica located at a remote site to the local site, run the Change Pair Status Wizard and split the copy group. 2.
8. Choose the Restore Mode. • Point-in-time Restore: Restores the replica and the transaction logs (without committing the outstanding transactions). • Roll-forward Restore: Restores the replica and then commits any outstanding database transactions stored in the transaction logs. NOTE: A roll-forward operation cannot be performed for SQL Servers from within Replication Manager.
3. Expand the object tree, and then select a database server. The Server summary window appears. 4. Open the Replica History tab to view a list of replicas. 5. Select a replica and click Restore Replica. The Restore Replica Wizard is launched. 6. Follow the procedure in “Restoring the latest application replica (simple restore)” on page 410 starting at step 5.
2. Use the disk management function to unmount the primary volume connected to the database server. 3. Stop SQL Server on the backup server. 4. Select the replica associated with the volume in step 2 from the Replica History and click Unmount Replica. 5. Select the copy group, start the Change Pair Status Wizard, and select create. 6. Select the copy group, start the Change Pair Status Wizard, and select swap. 7.
Using Database Availability Groups (DAGs) Replication Manager supports Exchange Database Availability Groups (DAGs). In a DAG configuration, data mirroring occurs between the DAG active node and passive nodes. (The target server can be an active or passive node.) NOTE: The DAG feature is exclusive to Exchange Server 2010/2013. For more information, see “About Database Availability Groups (DAGs)” on page 415.
• You cannot simultaneously create the replica of the active and passive mailbox database copies. Wait until execution of the replica creation is finished for the first mailbox database copy before you begin create the replica of the other mailbox database copies. • When you restore a replica, the target mailbox database copy must be an active mailbox database copy. • A replica can be restored only to the Exchange Server 2010/2013 server where the replica was created.
Replication Manager supports data backups and restores on a DAG configuration. Related topics • Using Database Availability Groups (DAGs), page 414 About SQL database and service status When Replication Manager is used to restore data from a secondary volume to a primary volume, the status of the database becomes either loading or standby: • Loading status (loading) The database can neither be viewed nor updated. • Standby status (read-only) The database can be viewed, but not updated.
SQL Server database status User action Readonly, Offline, and Unconfirmed Readonly • •1 • •2 •2 •2 • •2 •2 • •1 • •2 •2 •2 • •2 •2 • • Roll-forward restore (loading)5 Readonly and Offline Readonly and Unconfirmed Loading Offline (standby)4 Loading and Unconfirmed Unconfirmed Online Roll-forward restore Offline and Unconfirmed Legend: • : Action permitted and database changes are allowed. o : Action permitted and no database changes allowed. x : Action not permitted.
x : Action not permitted.
POST_PROC: Post-processing specified by the user (after the backup command is issued). Table 27 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 28 Script entries Entry name Meaning and specifiable values Multiple specification Omit LOCAL_BACKUP Specify YES.
Entry name Meaning and specifiable values Multiple specification Omit Not allowed Not allowed Allowed Allowed Specifies a command line to be executed. • If you want to specify an option, separate the command name and the option with a one-byte space character. • One command definition section must contain only one command line. • A maximum of 2048 characters can be specified on a command line. • A path or file name containing one or more spaces must be enclosed in double quotation marks (").
Entry name Meaning and specifiable values Multiple specification Omit Not allowed Allowed Not allowed Allowed Not allowed Allowed Not allowed Allowed Specifies the action to be performed in response to the return value of the executed command. Specifiable values are as follows: TERMINATE_NZ (default) Terminates script processing if a non-zero return value returns. IGNORE Continue processing whatever may be returned for a return value.
Environment variables The table below shows the Application Agent script environment variables that must be referenced by commands in the user post-processing section. These script environment variables can be referenced from the local server and the backup server. DRMENV_L_BACKUPID Backup ID of the local server. This environment variable is valid in the following cases: • The command is being executed in the local server. • The execution status of the parent command is normal.
Script text Explanation PARENT_STAT=NORMAL Execute only when the backup command is normal. Unmounting after an automatic mount If you specify the Automatically mount during the operation option while using the Create Replica Wizard, to automatically unmount the replica after the backup has been completed, you must execute the drmumount command. The Batch command file example demonstrates how to do this.
Preparing the user script and batch command file To prepare the script for execution from the Create Replica Wizard: 1. Save the user script file in any folder on the database server. You must supply this location in the Create Replica Wizard. 2. Save the batch command file in the directory C:\tmp on the backup server.
• SQL Server only: The database server must be set up with the default VDI Meta File Location in the SQL Options tab of the Setup Application Agent dialog box. • The backup server must be set as the tape backup destination by setting Replica Catalog Location in the Server Options tab of the Setup Application Agent dialog box. To save a replica to tape: 1.
• Select Execute pre/post jobs with Agent User Script and supply the path to a Script File located on the production server. TIP: If you set the Automatically mount during the operation option in the Create Replica Wizard, you should unmount the volume manually when the restore is complete. Command line tools Several command line tools to support tape operations are installed as part of Application Agent.
name containing space characters for the -f option, you must enclose the path name in double quotation marks ("). Return values are 0 for normal termination; any other value indicates an error. drmdbimport command The drmdbimport command imports, into a backup catalog, backup-information from a file that was exported by the drmdbexport command. Application Agent programs manage backup information based on copy groups, which are used as a key.
When the SQL Server replication function is used, the following requirements must be satisfied: • You must use the transaction replication type. • The name of the distribution database must be distribution, and only one distribution database can be created. • The subscription database must be restored separately from the system database (master, model, msdb), so the subscription database must be configured in a different volume than the system database.
Figure 26 Configuration of backup server for the publisher/distributor server (detail) Backing up the databases The publication database needs to be backed up at the same time as the distribution database. From the Select Target window of the Create Replica Wizard, select both the publication and distribution databases. Backing up the publication database transaction log Use Management Studio to back up the transaction log.
• For push subscription: use the publisher/distributor server. • For pull subscription: use the subscriber server. On the appropriate server, do the following: 1. Start the log reader agent. 2. Start the subscription agent. 3. Re-initialize the subscription, or remove and then recreate the subscription. Mounting and unmounting application replicas Replicas can be mounted or unmounted on the backup server as desired.
Checking the status of application replicas The status of application replicas is summarized in the Applications and Server subwindows. A set of icons represent how recent the replicas are, whether they have been created successfully, and so on. These icons are discussed in “About data protection status” on page 299. 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 2007, the Storage Groups tab allows you to view the storage groups associated with the server. For Exchange 2010/2013, 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.
Managing application replicas
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 437.
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 338 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 439 Exporting event log data To export event log data: 1. From the Explorer menu, choose Administration and then Event Logs. The Event Logs subwindow appears. 2. Click Export. The Export Event Logs dialog box appears. 3.
Exporting the history of journal volume usage for each copy group To export the history of journal volume usage on a copy group basis: 1. Display the information about the copy group whose journal volume usage history you want to export. For details on how to display this information, see the following: • • • • 2.
Related topics • About exporting management information, page 439 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 439 444 Exporting management information
26 System maintenance This chapter describes the system maintenance functions supported by Replication Manager. About system maintenance In Replication Manager, system maintenance can be performed by changing the operation mode from normal to maintenance mode and managing the retention periods of data according to system configuration and operating status. Changing to maintenance mode disables monitoring operations during maintenance operations such as replacement of the storage system microprogram.
Explorer menu Permissions Submenu Menu command Admin Modify View Administration Maintenance Y N N Data Retention Y N N Legend: Y: Can be executed with this permission. N: Cannot be executed with this permission. About operation modes During storage system maintenance it may be necessary to disable Replication Manager monitoring functions. This can be done by entering maintenance mode. Normal mode The default mode.
2. Click Change Mode. Either the Change Mode to Maintenance dialog box or the Change Mode to Normal dialog box appears. 3. Read the message, and then change the operation mode. The operation mode displayed in the Maintenance subwindow is updated.
System maintenance
27 Replication Manager CLI tools This chapter describes the CLI functions supported by Replication Manager. About the installation base path If the XP P9000 Command View AE Common Component is not installed under the installation directory of XP P9000 Command View AE suite products, you must set the HRPM_CLI_BASE_PATH environment variable to the actual installation path.
• The GetCTDelta command requires that the HP XP7 Command View AE Common Component services are running. • If the XP HP XP7 Command View AE Common Component is not installed under the installation directory of XP HP XP7 Command View AE suite products, you must set the HRPM_CLI_BASE_PATH environment variable. See “About the installation base path” on page 449 for more information. • GetCTDelta must be run on the management server. NOTE: Do not attempt to invoke multiple instances of GetCTDelta.
Output for the specified copy group (mainframe system managed by HP StorageWorks P9000 for Business Continuity Manager Software): [hostName=host-name prefix=prefix groupName=copy-group-name] [{hour=number-of-hours | day=number-of-days}] Parameter Description hostName Pair management server or host name. instanceNumber Instance number (cannot be specified with prefix). prefix Prefix (cannot be specified with instanceNumber). groupName Copy group name.
With parameters (open systems) GetCTDelta hostname=hcfg05 instanceNumber=1302 groupName=UR001 hour=10 Date / Time,Pair Management Server / Host,Configuration File / Prefix,Copy Group,CTG,C/T Delta Tue Jul 03 11:02:12 JST 2012,hcdg05,horcm1302.conf,UR001,,0 Tue Jul 03 11:04:08 JST 2012,hcdg05,horcm1302.conf,UR001,,0 With parameters (mainframe systems) GetCTDelta hostname=XX01 prefix=HRPM.TEST.
• The task CLI only supports tasks whose targets are open system copy pairs or copy groups. Mainframe system copy pairs and copy groups managed by HP StorageWorks P9000 for Business Continuity Manager Software or RAID Manager are not supported. Property settings Before starting task management operation using Replication Manager CLI, the properties of base.properties file shown below must be set. • base.rmi.
Getting information about tasks (GetTasks) The GetTasks command obtains information about tasks that have been created for execution by the CLI. The parameters enable you to specify a taskID for which you want information, retry interval, and number of times to confirm a task status change. If you specify a taskID, the return value enables you to confirm the task status. If you do not specify any parameters, all CLI tasks are displayed.
Output The information output by the GetTasks command is as follows: • Task ID • MF/Open • Host (Primary/Secondary). (A hyphen is displayed for the Host (Primary) information when a copy group is defined as a device group.) • Target • Copy Type • TaskType • Status • Creation Time • Execution Start Time • Execution End Time • Message • Detail Message Executing a task (ExecuteTask) The ExecuteTasks command executes a task that was created for execution by the Replication Manager CLI.
Managing tasks with scripts A task created using the Replication Manager GUI can be registered as a task to be executed using the CLI. By creating a user script to execute the task in conjunction with performing a quiesce operation, you can perform data backup linking with the application. By placing such a script on the management server, copy pair operations on each host can be managed collectively and the execution results confirmed from Replication Manager GUI.
set cmdRetVal=%errorlevel% if not "%cmdRetVal%"=="0" ( rem an error occur echo Error!! exit /b 1 ) rem Confirming the result of pair operation task call GetTasks.
Replication Manager CLI tools
28 Support and other resources Numerous support options are available. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
Conventions This guide follows the conventions shown in Table 30 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 Synchronous Continuous Access Synchronous • Continuous Access XP Synchronous • P9000 Continuous Access Synchronous • XP Continuous Access Synchronous 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 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
B Exceptions This appendix provides information about complex system configuration scenarios. Cautionary notes for the GUI display Certain cautionary notes exist for the GUI.
For open systems In the Hosts view or Storage Systems view, volumes to which paths have been specified are displayed in either the Paired or Unpaired list. The volumes constituting copy pairs are displayed in the Paired list and the other volumes are displayed in the Unpaired list. However, the volumes constituting copy pairs in simplex status are displayed in the Unpaired list, because they have been defined, but not yet created.
To view an example configuration in which two copy group definition files are used for the same copy group (for mainframe systems), see “Example configuration in which two copy group definition files are used for the same copy group (for mainframe systems)” on page 469.
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 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.
• Name of the storage system to which a secondary volume belongs TIP: It is assumed that each Device Manager server has been registered as an information source of Replication Manager and that the pair management servers and hosts have been registered in the Device Manager server at each site. For a diagram, see “Example configuration in which data is remotely copied between multiple sites (for open systems) ” on page 473.
Example configuration in which data is remotely copied between multiple sites (for open systems) 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.
When Replication Manager handles multiple prefixes (mainframe systems) Replication Manager allows you to confirm, define and operate copy pairs for multiple prefixes concurrently. On the Hosts or Storage Systems view you can confirm DEVNs and LDEVs without specifying or identifying the prefix. During pair configuration, Replication Manager prohibits selection of P-VOLs / S-VOLs from multiple prefixes on a mainframe host.
C 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 the GUI 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 GUI Copy type BC Business Copy Cnt Ac-A Continuous Access Asynchronous Cnt Ac-S Continuous Access Synchronous SS / FS Snapshot/Fast Snap FS (Snapshot Group) Fast Snap (for snapshot group pair) Cnt Ac-J Continuous Access Journal Cnt Ac-J (3DC Delta Resync) Continuous Access Journal (when 3DC delta resync is supported) About volume attributes Volume attributes are obtained from Device Manager and displayed in Replication Manager dialogs used to vie
Display formats
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).
cluster configuration In a Replication Manager operating environment, the term cluster configuration refers to a configuration that consists of an executing node and a standby node, each of which includes a duplicate management server. cluster software Software installed on management server nodes to boost overall availability by duplicating management servers as a cluster system. Available software depends on the OS that runs on the management server.
copy pair status A value that represents the status of a copy pair. Six status values are defined in Replication Manager: error, suspend, copying, sync, simplex, and unknown. Each status is indicated by an icon. The copy pair status is determined by the combination of the copy pair states of the primary and secondary volumes. Also called pair status. copy progress Progress status of the volume replication functionality executed by the storage system.
Manager Software to manage volumes to which no DEVNs have been assigned by the mainframe host. Emulation Type The types of LUs with varying attributes supported by the XP1024/XP128, XP12000/10000/SVS200 and XP24000/20000 series. Also referred to as Emulation Mode. Extended Consistency Group (EXCTG) An attribute for maintaining data integrity between the copy pairs contained in consistency groups. In principle, each copy group container is assigned this attribute.
a number of different sites. These programs provide information to Replication Manager and are called information sources. IP Internet Protocol iSCSI Internet Small Computer System Interface LAN Local Area Network LDAP Lightweight Directory Access Protocol LDEV (Logical DEVice) A volume created in a storage systemknown as an LDEV (logical device) in a mainframe system.
N:1 configuration A configuration in which multiple configuration definition files are managed by the primary volume server and one definition configuration file is managed by the secondary volume server. N:N configuration A configuration in which multiple configuration definition files are managed by both the primary volume server and the secondary volume server.
system. A command device must be set up in the storage system to enable the storage system to receive commands from RAID Manager. In an open system, Replication Manager uses the RAID Manager configuration definition files to modify copy pair configurations and to acquire configuration information. Copy pair modification processing, such as splitting and re-synchronizing copy pairs, is executed on the storage system by RAID Manager.
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. 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.
Index A access control users and permissions, 77 accounts adding users, 81 automatic locking, 369 changing passwords, 347, 353 locking, 354 removing users, 349, 350 unlocking, 355 advanced options force-split, 244 swap, 244 takeover, 243 takeover-recovery (recreate), 245 takeover-recovery (resync), 245 agent user script, 418 alerts and volume switching, 249 automarking, disabling, 159, 339 changing, 338 completion, 125 conditions for, 123 copy license usage threshold, 124 copy pair status, 124 deleting, 339
C C/T delta, 294, 439 alert settings, 123 checking for each copy group, 295 exporting history, 441, 449 cache, 120 candidate volumes, 115, 120 capacity, 115, 149, 313 expanding journal group, 326 licensed, 342 cascade configuration defining, 168 limitations, 168 permitted topologies, 167 Change Pair Status Wizard about, 236 advanced options, 242, 252 basic options, 242, 252 checkpoint files, 396 class, 165 CLI copy pair status, 267 refreshing configuration information, 274 command device adding, 110 defined
copy pair about, 145, 201 add to workflow, 189 and copy groups, 127 associated with a task, 307 checking, 285 checking (specific volume), 284 checking configuration definitions, 283 checking, about, 282 configuration definitions, 147 copy groups belonging to, 309 deleting related pairs, 322 editing, 192 monitoring, 286 monitoring (alerts), 286 prerequisites for mainframe, 188 refresh interval, 135 refreshing manually (My Copy Groups), 272 refreshing status, 267 saving, 184 states, 221 status, 214, 226 statu
drmumount command, 427 E Edit Group window, 181, 195 email, 286, 335 emergency license key, 341, 342 emulation type, 313 event log about, 435 data retention, 135 exporting, 441 viewing list of files, 436 exauth.
IPv6, 54, 375 J JNLG, 121, 325, 442 expanding journal group capacity, 326 journal groups about, 117 adding, 121 deleting, 325 editing, 325 expanding capacity, 326 journal volume usage, 442 wizard, 121 journal usage exporting, 442 exporting for each copy group, 442 K KAVN00123-I, 135 KAVN00124-I, 135 KAVN00126-I, 135 KAVN00127-I, 135 L last distributed time, 184 last refresh, 271, 272, 279 LDAP, 77, 356 LDEV, 149, 271, 316, 320, 471 Viewing LDEV Information (Mainframe Systems), 314 LDKC, 284, 291 Viewing
P9000 RAID Manager, 23 command devices, 108 pair configuration association, 192 copy group requirements, 158 creating, 154 deleting, 199 editing by associating, 189 prerequisites (mainframe), 150 wizard, about, 141 Pair Configuration Wizard launching, 142 Pair Configurations view, 311 pair management copy groups defined in storage, 260 virtual command devices, 253 pair management server, 312 adding (to site), 94 removing, 333 pair management server>redundant, 32 pair names editing, 156 pair status changing,
remote paths about, 111 conditions, 111 creating, 111, 113 deleting, 323 editing, 321 managing, 321 wizard, 112 remote_MU, 382 replica generation, 161 replicas about, 381, 401, 402 check status workflow, 432 concealing secondary volumes, 59 configuration requirements, 395 create (workflow), 401 creating, 389, 403 data protection status, 299, 300 data types, 395 generations, 149, 381 information stores, 407 mounting/unmounting, 431 precautions, 384, 400 resources, 432 restoring, 392, 409 restoring (simple),
Split (SSWS), 243 Split (SWSS), 242, 245 SQL Server database status, 416 distribution database, 429 publication database, 429 replication function, 428 restoring, 428 standby status, 416 start time, 278 Storage Groups, 433 storage system status of copy pairs, 291 storage systems adding to resource group, 85 adding to site, 93 removing from site, 332 setting up, 101 viewing a list, 307 viewing a summary, 308 viewing individual, 309 viewing information (open systems), 316 volume information, 313 subscription
V V-VOLs and CVS installation, 105 conditions for adding, 105 creating, 104, 106 deleting, 319 deleting multiple, 319 deleting, conditions, 319 managing, 319 prerequisites, 105 wizard, 106 VDI Meta File Generation Timeout, 62 verification replicas, 60 virtual command devices, 253 VOL, 111 volume belonging to a host, 313 candidates, 156 conditions for adding (mainframe), 153 mainframe discovery, 65 selecting multiple candidates, 157 selection restrictions, 152, 153 Volume Scan about, 66 range, 68, 69 range(S
