HP XP P9000 Fast Snap User Guide Abstract This guide explains how to use HP XP P9000 Fast Snapshot Software to create space-efficient point-in-time copies of data volumes on an HP XP P9000 disk array. Topics include creating, monitoring, and troubleshooting pools, virtual volumes, and copy pairs. The intended audience is a storage system administrator or authorized service provider with independent knowledge of HP XP P9000 disk arrays and the HP Remote Web Console.
© Copyright 2012, 2013 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 1 Overview of Fast Snap................................................................................6 Fast Snap................................................................................................................................6 Components of Fast Snap..........................................................................................................7 Components of volumes........................................................................................................
Calculating the number of Fast Snap pairs based on the number of cache management devices........................................................................................................................32 Calculating the number of cache management devices...........................................................32 Fast Snap cache management device requirements............................................................32 Effects on I/O performance of the storage system...............................
Maintenance requirements.......................................................................................................62 Replacing the microcode offline...........................................................................................62 Powering-off......................................................................................................................62 6 Troubleshooting........................................................................................
1 Overview of Fast Snap You can use Fast Snap (FS) to perform cost-effective duplication by storing only differential data between primary volumes (P-VOLs) and secondary volumes (S-VOLs) of virtual volumes (V-VOLs). Fast Snap FS stores snapshots, or a duplicate, of data in your P9500 storage system. Snapshot data is a copy of updated data in FS P-VOLs. You can use this data in open-system volumes. If a data storage failure occurs in your storage system, you can use the snapshot data to restore the data.
Required software applications Thin Provisioning (THP) is required to use FS. THP accesses data in pool volumes by way of V-VOLs, and can handle data in open-system servers such as UNIX and PC servers. For more information about THP, see “Thin Provisioning” (page 8). Components of Fast Snap FS typically consists of the following components: • FS pairs - Components of volumes (P-VOL, S-VOL, and pool-VOL) For more information, see “Components of volumes” (page 8).
Components of volumes FS manages logical volumes of P-VOLs and V-VOLs of S-VOLs as FS pairs. Logical volumes of P-VOLs include V-VOLs that have a provisioning type is Thin Provisioning. You can only use V-VOLs that are used by an FS pair as an S-VOL. The differential data of P-VOLs are stored as snapshot data in pool volumes.
RAID Manager Use the RAID Manager to perform FS tasks. You do this by running commands from a host. For more information about the commands, see “RAID Manager command reference” (page 72) and HP XP P9000 RAID Manager Reference Guide. How Fast Snap works This topic explains how FS works. Fast Snap Pools FS stores snapshot data in pools. A pool consists of multiple pool-VOLs. The pool-VOLs contain the snapshot data. A pool can contain up to 1,024 pool-VOLs.
To use FS, create pools. With FS, you can add pool-VOLs but you cannot delete them. To delete a pool, delete all of the FS pairs. CAUTION: The pool capacity is calculated by subtracting the capacity of V-VOL management areas from the total capacity of pool-VOLs in the pool. If you write data to FS pair volumes and the amount of pool usage exceeds the pool capacity, the following occurs: • You cannot store snapshot data. • The FS pair status changes to “PSUE”, which indicates a failure.
Figure 1 Storing snapshot data for a group Use the following process to store snapshot data: 1. Issue a request to store snapshot data for a group. To do this, run the raidcom modify snapshot -snapshot_data create RAID Manager command. 2. The host issues a write request to each P-VOL in the group. Snapshot data for the volumes are stored. 3. Store snapshot data for a consistency group or a snapshot group using the RAID Manager command.
Snapshot data storage methods You can use the Copy-On-Write (COW) method or the Copy-After-Write (CAW) method to store snapshot data. In the COW method, when the P-VOL snapshot data is acquired, the status changes to the write completion status. In the CAW method, when the P-VOL snapshot data is written, the status changes to the write completion status. The CAW method wait time is shorter than that of the COW method. The following figure illustrates the CAW method.
Differences in methods for storing snapshots depending on volumes The method in which you store snapshot data is dependent on the types and RAID levels of P-VOLs. Use the following list to determine which method to use to store snapshot data: • • The P-VOL is an internal volume. ◦ If the P-VOL RAID level is RAID 1, use the COW method. ◦ If the P-VOL RAID level is something other than RAID 1, use the CAW method. The P-VOL is a THP volume.
FS pair status and deleting snapshot data Deleting all of the pairs in a snapshot group (“SMPL” status) deletes the snapshot group. Delete the snapshot group before performing the next pair task. If a failure occurs while you delete an FS pair, the FS pair status changes to “PSUE” status, data is written to the FS pair volumes, and the capacity of snapshot data exceeds the pool capacity. You cannot create new FS pairs. Delete the unneeded snapshot data.
If you do not use the volumes as an FS pair, the volumes remain unpaired (“SMPL” status). If you do not pair the P-VOL with an S-VOL and you create the pair, the pair status changes to “COPY” and then to “PAIR”. If you pair the P-VOL with one or more S-VOLs and you create the pair, the pair status changes to “PAIR”. If you create a FS pair directly after deleting the last P-VOL snapshot data, the process can take time.
NOTE: Even if the restore process is not in progress, the pair status can change to “PSUE” when a failure occurs. • The pool usage rate reaches 100 percent. The status of FS pairs depends on whether the hosts can read from or write to the FS pair P-VOL or S-VOLs. The following table explains the host access and pair status.
For more information about enabling the copy threshold option, contact HP Technical Support. Interoperability with other software applications You can create FS pairs using pair volumes for replication software applications such as BC/SS and Continuous Access Synchronous (Cnt Ac-S). You can also create FS pairs using volumes to which attributes are defined by Data Retention (Data Ret) or RAID Manager. The following table shows whether you can share pair volumes by FS and other software applications.
Software volume types Used as FS P-VOL Used as FS S-VOL 5. RAID Manager is required to set Zero Read Capacity and Invisible attributes. 6. You can use Data Ret. to confirm whether Read Only, Protect, S-VOL Disable, Zero Read Capacity and Invisible attributes are set to volumes. Legend Yes: You can share the volume. No: You cannot share the volume. If you share a volume with a software application listed in the previous table, the pair status determines whether tasks are performed.
Access attribute of volume specified by FS FS pool task Pool-VOL setting S-VOL Disable No Legend Yes: You can perform the task No: You cannot perform the task NOTE: FS tasks do not change access attributes of volumes. Reverse resync tasks do not copy access attributes of S-VOLs to P-VOLs when writing snapshot data to P-VOLs, As shown in the following table, Data Ret. cannot assign access attributes to some FS P-VOL and S-VOLs, depending on the FS pair status.
The following tables list the relationship between pair tasks and status.
BC/SS task FS pair status COPY PAIR, PFUL PSUS, PFUS SMPL(PD) RCPY PSUE Normal Copy Yes Yes Yes Yes No Yes Reverse Copy Yes Yes Yes Yes No Yes Quick Restore No No No No No No Suspend replication Yes Yes Yes Yes Yes Yes Delete pair Yes Yes Yes Yes Yes Yes Legend Yes: You can perform the task No: You cannot perform the task (the command is rejected) The following table shows a list of the SI tasks that you can perform when you share an FS P-VOL with an BC S-VOL.
The following table shows the FS tasks you can perform based on Cnt Ac-S/Cnt Ac-J pair volume status.
Cnt Ac-S/Cnt Ac-J task FS status COPY PAIR, PFUL PSUS, PFUS RCPY PSUE N/A: Not applicable The following table shows the Cnt Ac-S/Cnt Ac-J tasks you can perform when the FS P-VOL is shared with a Cnt Ac-S/Cnt Ac-J S-VOL.
• Pair 1 is a Cnt Ac-S pair. • Pair 2 is a Cnt Ac-J pair. • Pair 3 is a Cnt Ac-J pair for delta resync. • 1. 2. 3. Pairs 4, pair 5, and pair 6 are FS pairs. Create 3DC multi-target and delta resync pairs (pairs 1, 2, and 3). Create pair 4. Create pairs 5 and 6. Thin Provisioning Note the following if you are using FS, THP, and Thin Provisioning Z (THP Z) in a single storage system: • If you are expanding the THP V-VOL capacity, you cannot create FS pairs that have an THP V-VOL as the P-VOL.
Resource Partition You can create a FS pair without regards to the P-VOL and S-VOLs resource group assignment. Assign the pool you are using to the resource group where the P-VOL is assigned or to the resource group where you can create FS pairs. For more information about resource groups, see the HP XP HP XP P900 Provisioning for Open Systems User Guide.
2 Planning and design This topic discusses requirements for using FS. Please read this topic before using FS. System requirements The following is a list of system requirements that are required to perform FS tasks: • A P9500 storage system with P-VOL and S-VOLs. • FS and THP, which run on RWC computers. Requirements for Fast Snap The following is a list of requirements to use FS: • The hardware and microcode is configured and set up. • The license key for THP is installed using RWC.
The following table shows the FS volumes and capacity calculated as the FS usage. The total amount of these values must not exceed FS license capacity. The intended volumes The intended capacity Program product The kind of volumes Normal volume or THP-VOL FS P-VOL Normal volume The volume capacity THP-VOL The pool capacity used by the volume Normal volume The volume capacity Pool VOL For details about license, see the HP XP P900 Remote Web Console User Guide.
Item Requirement Note: This value can be increased depending on your system configuration. For information about the calculating the maximum number of FS pairs, see “Calculating the number of Fast Snap pairs” (page 30). Path definitions Required. Volume capacity limit 4 TB The following table shows the requirements for FS S-VOLs. Item Requirement Volume type V-VOLs You cannot specify the following volumes as FS S-VOLs: • Volumes that are already used as S-VOLs.
Item Requirement • External Storage Access Manager quorum disks • RAID-1 RAID level volumes that have a SATA-E hard disk drive type. Note: • Use only external pool-VOLs whose cache mode is the same, either enabled or disabled, in the data pool. • Use only volumes that are in different resource group in the data pool. • Use only internal volumes and external volumes with an enabled cache mode in the data pool. Emulation type OPEN-V RAID level All RAID levels are supported.
Notes on consistency groups • (If you are using RAID Manager to create snapshots) To avoid the raidcom add snapshot command from being rejected, define an FS pair that shares the same P-VOL in the separate consistency groups.
1. 2. Calculate the number using the number of differential tables (see (page 31)). Compare the results of the three calculations. The smallest of the three is the maximum number of FS pairs that you can create in the storage system. When you create FS pairs again, you do not need to use the snapshot estimated manageable capacity and the number of cache management devices. Use only the number of pair tables and calculate the number of FS pairs that you can create.
1,048,575 - 15,000 - 30,000 = 1,003,575 The results of the calculation shows that you can create up to 1,003,575 FS pairs. An FS pair consists of a P-VOL and up to 1,024 V-VOLs. Differential tables are used per P-VOL. The number of differential tables you can you use does not depend on the number of V-VOLs. Calculating the number of Fast Snap pairs based on the snapshot estimated manageable capacity You can view the snapshot estimated manageable capacity in the Local Replications window.
Effects on I/O performance of the storage system If you perform FS restore tasks when the workload on the storage system is high, I/O performance of host servers can decline because replication process starts for the P-VOL. Enable the copy threshold option to lower the workload on the storage system.. For more information, see “Copy threshold option” (page 16). For more information about enabling the copy threshold option, contact HP Technical Support.
Volumes in external storage systems are referred to as external volumes. Volumes in a local storage system are referred to as internal volumes. If External Storage is installed, you can use external and internal volumes as pool-VOLs. However, if external volumes are used, it increases the likelihood of a failure, and the disaster recovery is more complex and challenging. If you use external volumes as pool-VOLs, to minimize adverse effect of failure, use a pool for each external storage system.
3 Performing configuration tasks This topic describes creating pools, creating V-VOLs, and settings of the command device for configuring FS. Configuration tasks workflow The following image shows how to run FS. Use the following process to run FS: 1. Create a V-VOL management area in the shared memory. The V-VOL management area is created when you install additional shared memory. For more information about installing shared memory, see “Installing Fast Snap workflow” (page 26).
Priority Hard disk drive type 3 SAS10K 4 SAS15K 5 SSD 6 External volume If more than one pool-VOL of the same hard disk drive type exists, its priority is determined according to storage system’s the internal index information. Creating Fast Snap data pools You can create FS data pools using RWC. Prerequisites • 1. 2. 3. Prerequisite: The volumes that you plan to add to the pool have the same assigned CLPR. In the Storage Systems tree, select Pools. In the Pools window, click Create Pools.
Required: Yes - For Prefix, type case-sensitive, alphanumeric characters. - For Initial Number, type a number, which is up to nine digits. 7. In the Options window, Initial Pool ID and other items are shown. Complete the following and then click Add: • For Initial Pool ID, type a number. Values: 0 to 127 Default: The smallest available number If an available pool ID does not exist, a number is not shown.
• For Number of LDEVs, type the number of V-VOLs (LDEVs) to be created. The range is shown below the text box. • For LDEV Name, type a name of the V-VOL. - For Prefix, type the alphanumeric characters, which are fixed characters placed before the V-VOL name. The characters are case-sensitive. - For Initial Number, type the initial number for V-VOL. Digit limit: 9 Character limit: 32 including the Prefix and Initial number The following items are required: 4. 5. 6.
For more information about how to edit SSIDs, see “Editing the V-VOL SSID” (page 39). • LDEV Click Change LDEV Settings to open the Change LDEV Settings window. For more information about how to change the LDEV settings, see “Changing the V-VOL settings” (page 40). 10. Complete the following and then click Apply: • For Task Name, type the name of the task.
2. 3. 4. 5. 6. In the Edit SSIDs window, the SSIDs table shows the existing SSIDs and the SSIDs that you can add. Select the row of the SSID you want to edit and click Change SSIDs. In the Change SSIDs window, type the new SSID and click OK. In the Edit SSIDs window, click OK. In the Create LDEVs window, click Finish. In the Confirm window, complete the following and then click Apply: • For Go to tasks window for status, select to open the Tasks window.
4 Pair tasks This chapter provides instructions for performing pair tasks. Creating Fast Snap pairs You can assign a P-VOL to a maximum of 1,024 FS pairs. You can create up to 1,024 pairs at a time. To create more than 1,024 pairs, repeat this procedure. When specifying the P-VOL and S-VOLs, make sure that the size of the two volumes is the same. When specifying a P-VOL that is already used as the P-VOL of another FS pair, make sure that the two FS pairs share the same pool.
- No shows LDEVs that are not used as P-VOLs. • If you selected No in Use Primary Volumes of Snapshot Pairs, click Select Pool. In the Select Pool window, select a pool then click OK. • In Available LDEVs, select an LDEV to be the P-VOL and click Add. The LDEV is moved to Selected LDEVs. 5. Click Next and complete the following: In the Available LDEVs table, select the LDEV that you want to use as a S-VOL, and then select a snapshot group. To create a new snapshot group, type the name and click Set.
Use 1. 2. 3. 4. the following process to create FS pairs using RWC: Select the pair configuration. Select the P-VOL. Select the S-VOLs. Perform confirmation. Configuring a complex pair If you add S-VOLs to an existing pair, ensure that the Number of Secondary Volumes field contains a number that is larger than the current number of S-VOLs of the existing pair. For example, if you add an S-VOL to an existing pair that has one P-VOL and one S-VOL, specify 2 for the number of S-VOLs.
1. Specify 2 as the number of S-VOLs, and select two P-VOLs. The storage system assumes two pairs of two S-VOLs each will be created. 2. Select the S-VOL. Select and delete the S-VOL MU#1 of the second pair. By deleting a S-VOL, you can create multiple pairs of different configurations. Figure 3 Creating two pairs of different pair configurations Splitting pairs You can create up to 1,024 snapshots from one P-VOL. This topic explains how to split pairs.
Related topics • Page 102 Using the At-Time Snapshot function to acquire snapshot data for a consistency group You can use RAID Manager’s At-Time Snapshot function to acquire snapshot data for a consistency group. Use the RAID Manager to run the commands. 1. Run the raidcom add snapshot RAID Manager command, using an option to specify the consistency group number. A consistency group is created that should be the target of the At-Time Snapshot function.
Figure 4 At-Time Snapshot configuration with Cnt Ac-J Figure 5 At-Time Snapshot configuration with Cnt Ac-S 46 Pair tasks
The following table explains when you can run the At-Time Snapshot function.
Notes on acquiring snapshot data • • (If you are using RAID Manager to run the raidcom modify snapshot -snapshot_data create RAID Manager command to split pairs and the consistency group includes a pair in a status other than “PAIR”) The command can terminate abnormally, as follows: ◦ The command is rejected. ◦ Timeout occurs. The error code is EX_EWSTOT. ◦ The pair is suspended. The error code is EX_EWSUSE.
3. 4. 5. In the Resync Pairs window, for Resync Type, select Reverse Copy (Secondary > Primary) to reverse resynchronize the volumes from the S-VOL to the P-VOL. All differential data is updated to the P-VOL. Click Finish. In the Confirm window, for Task Name, type a name for the task and then click Apply. The pair is restored. Related topics • Page 105 Deleting snapshot data Deleting only the snapshot data maintains the relationship between the P-VOL and S-VOLs.
2. 3. In the Pairs tab, select the pair you want to delete, and click More Actions > Delete Pairs. In the Delete Pairs window, type a Task Name, and then click Apply. While the pair is in the process of being deleted, the P-VOL and S-VOLs status is “SMPL(PD)”. After the FS pair is deleted, the status changes to “SMPL”.
5 Monitoring and maintenance This topic provides information and instructions for monitoring and maintaining the FS system. Monitoring pair information You can monitor pair information in the following ways: • “Viewing the number of pairs and a list of pairs” (page 51). • “Monitoring pair properties” (page 51). • “Monitoring synchronous rates” (page 52). Viewing the number of pairs and a list of pairs 1. 2. In the Storage Systems tree, click Replications > Local Replications.
2. Select the pair in the Pairs tab and then click More Actions > View Pair Properties. Related topics • Page 87 Monitoring synchronous rates You can check on the percentage of data that is synchronized between the P-VOL and S-VOLs. You must have the Storage Administrator (Local Copy) role to monitor synchronous rates. The FS synchronous rate shows the rate that S-VOL data matches that of the S-VOL’s next new generation.
Related topics • “View Pair Synchronous Rate window” (page 89) Monitoring consistency groups You monitor consistency groups in the following ways: • “Viewing the number of consistency groups” (page 53). • “Viewing a list of consistency groups” (page 53). • “Viewing consistency group properties” (page 53). Viewing the number of consistency groups 1. 2. In the Storage Systems tree, click Replications > Local Replications > Consistency Group. View the number of consistency groups.
The following table shows FS tasks that are shown in the View Histories window. The Description column indicates which tasks ran. Code Description Explanation 2001 PAIR The pair was created. 2011 PSUS The pair was split. 2021 SMPL The pair was deleted. 2030 COPY(RS-R) START Pair restoration task began. 2031 COPY(RS-R) END Pair restoration task completed. 2032 COPY(RS-R) ENDED ABNORMAL Pair restoration task failed. 2040 INITIALIZE START Initialization processing began.
1. In RWC, click Actions > Local Replications > BC/SS > History. If some of the pairs include LUSE volumes or if the total number of the following pairs and migration plans is 500 or more in the subsystem, you may need to wait until the History window shows the operation history. 2. 3. • BC/SS pairs • SS pairs • BC Z pairs • FC Z • Auto LUN • FS pairs In the History window, see FS information in the bottom part of the window. The list sorts based on the column heading you click.
4. If the information on the list is not updated, click File > Refresh to update with the latest information. For tasks involving the copying process, the History window does not show information about the tasks until the copying process starts. If you perform an task on a pair before the copying process starts, the History window does not show information about the task. 5. If there are many records of tasks, scroll the list to see the task history that is not currently shown.
Monitoring licensed capacity 1. 2. In the Storage Systems tree, select Replications. View the licensed capacity. Related topics • Page 80 Monitoring the number of cache management devices You can monitor the number of cache management devices, such as the current number of devices and maximum amount allowed in the storage system, in the View Management Resource Usage window. 1. On the menu bar, select Actions > View Management Resource Usage. 2.
• Correction access executes to the pool-VOL in the selected pool. • The format function for a free space of a pool is not operating. The following are the cases that the formatted pool capacity may decrease: • The system is allocating new pages. • 1. 2. The system is performing a correction copy. In the Storage Systems tree, select Pools. In the Pools window, complete the following: 1. From the Pools table, click the row for the pool you want to confirm free pool capacity. 2.
Changing pool threshold Use the following procedure to change the pool threshold. Prevent the pool from reaching full capacity by monitoring the pool usage rate. CAUTION: For example, when the actual pool usage rate is 50.1%, you round the value down to the closest integer 50, and 50% is shown in the Edit Pools window. If you set 50% as the pool threshold, even though the value shown on the window does not exceed the threshold, the excessive pool usage in SIM and SNMP is reported. 1. 2. 3. 4.
4. In the Edit Pools window, check the Pool Name, and then click Finish: • For Pool Name, type a new pool name. Character limit: 32 (for the Pool Name and Initial Number combined.) - For Prefix, type alphanumeric characters Case-sensitive: Yes - For Initial Number, type a number Limit: 9 digits 5. In the Confirm window, complete the following and then click Apply: • For Task Name, type a name for the task.
Related topics • The Restore Pools window in the HP XP P9000 Provisioning for Open Systems User Guide. Deleting pools You can delete one of more pools in a single operation. Related topics • 1. 2. 3. 4. The Delete Pools wizard in the HP XP P9000 Provisioning for Open Systems User Guide. In the Storage System tree, select Pools. In the Pools window, from the list, select the pool you want to delete, and then click More Actions > Delete Pools. In the Delete Pools window, click Finish.
Related topics • The Edit LDEVs wizard in the HP XP P9000 Provisioning for Open Systems User Guide. Deleting V-VOLs To delete V-VOLs and V-VOL groups that are specified for FS S-VOLs, first release the pairs. Related topics • 1. 2. The Delete LDEVs window in the HP XP P9000 Provisioning for Open Systems User Guide. In the Storage System tree, select Logical Devices. In the list, click the rows for the V-VOLs that you want to delete. Hold down the Shift key when clicking multiple adjacent pools.
Switching off the power supply while you are storing snapshot data by consistency group and the status of all the pairs in the consistency group have not changed completely does not resume the storing of snapshot data. Switching on the power supply does not guarantee a status change for some pairs. If information in shared memory is lost after switching off the power supply The storage system has a battery used to maintain the information in shared memory.
6 Troubleshooting This topic provides FS troubleshooting information. General troubleshooting The following table shows FS troubleshooting information. Problem Causes and solutions Pool information is not shown. Cause: The pool is blocked. Solution: Recover the blocked pool. For more information, see “The workflow for recovering blocked pools workflow” (page 66). A pool is blocked. Cause: • The pool-VOLs are blocked. • The pool reaches full capacity. Solution: 1. Recover the blocked pool.
Problem Causes and solutions You cannot create FS pairs. Causes: • There are not enough cache management devices. • There are not enough resources depending on cache management devices. • The conditions to create the pair are not fulfilled. • The status of the specified volume is not shown because an FS pair is being deleted. Solutions: • Ensure that there are enough cache management devices to create the pairs. For more information, see “Fast Snap cache management device requirements” (page 32).
Problem Causes and solutions To check whether the host has access to pair volumes, see “Pair status” (page 14). When the host computer tries to access the port, an error occurs and the host cannot access the port. Cause: A port may go offline because access to a volume on another port has been rejected. Solutions: • Wait awhile, then retry the task. • If a host application is installed to monitor the volume, stop the application. RWC frequently times out.
1. Correct pool-related Service Information Messages (SIMs) for the following, if they occur: • Reference code 601XXX: Pool usage rate exceeds the threshold. • Reference code 602XXX: Pool is blocked. XXX indicates the pool ID. Check SIMs using the System Information/Status window in RWC. 2. • Reference code 602FFE: Multiple pools are blocked. • Reference code 603000: The snapshot estimated manageable capacity is less than 128TB.
1. Calculate the remaining number of the remaining cache management devices. To do this, use the following formula: number-of-cache-management-devices = 65,280 number-of-cache-management-devices-being-used For more information about how to confirm the number of cache management devices being used, see “Monitoring the number of cache management devices” (page 57). If a warning SIM is issued before you deplete the cache management devices, that does not mean a problem occurs immediately.
7 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
• http://www.hp.com/support/downloads • http://www.hp.
WARNING! CAUTION: IMPORTANT: NOTE: TIP: Indicates that failure to follow directions could result in bodily harm or death. Indicates that failure to follow directions could result in damage to equipment or data. Provides clarifying information or specific instructions. Provides additional information. Provides helpful hints and shortcuts.
A RAID Manager command reference This topic describes RAID Manager commands corresponding to actions in the RWC GUI. Statuses required for RAID Manager tasks You can use RAID Manager to perform pair tasks. You can also use RWC. To perform tasks using RAID Manager, you run existing commands for pair tasks or the raidcom commands. Use raidcom commands to store 65 or more snapshot data or use 64 or more MU numbers.
Status PSUE RAID Manager command paircreate paircreate -split pairsplit pairresync pairresync -restore pairsplit -S pairsplit -E Ab Ab Ab Ok Ab Ok Np Ok: ends normally Np: not performed but ends normally Ab: the command is rejected, ends abnormally You cannot use the noread mode (-m noread) for S-VOLs if you are using RAID Manager. If the noread mode is specified for a S-VOL when creating a pair, the command ends normally but the noread mode does not take effect.
For details about error codes that are not described in the following table, contact HP Technical Support. The following table shows the RAID Manager error codes for SSB1: 2E31, B901, B9A8, B9A9, B9AD, B9AE). SSB2 RAID Manager command Cause of error 9100 All commands You cannot run the command because the user authentication is not performed. 9685 paircreate You cannot create the FS or SS pair because of a shortage of pair tables.
SSB2 RAID Manager command Cause of error 9724 All commands The command ended abnormally because there is no additional shared memory (more than TI 1). 9725 All commands The command ended abnormally because the LDEV number of the volume you specified as the FS or SS P-VOL is beyond the specified range. 9726 All commands The command ended abnormally because you specified the unmounted volume as the FS or SS P-VOL.
SSB2 RAID Manager command Cause of error 973E paircreate, pairsplit, pairresync, pairresync -restore The command ended abnormally because you specified a volume that is in process of formatting as the FS or SS S-VOL. 973F paircreate, pairsplit, pairresync, pairresync -restore The command ended abnormally because you specified a volume that has an emulation type other than OPEN-V as the FS or SS S-VOL.
SSB2 RAID Manager command Cause of error 9759 All commands The command ended abnormally because you specified an Auto LUN V2 reserved volume as the FS or SS P-VOL. For information o about n using Auto LUN V2, contact HP Technical Support. 975A All commands The command ended abnormally because you specified a BC/SS P-VOL as the FS or SS S-VOL. 975B All commands The command ended abnormally because you specified a BC/SS S-VOL as the FS or SS S-VOL.
SSB2 RAID Manager command Cause of error 9783 pairresync -restore You cannot restore the FS or SS pair for one of the following reasons: • A snapshot for the FS or SS pair to be restored is being stored per consistency group. • The P-VOL of the FS or SS pair to be restored is used as the P-VOL of another FS or SS pair, and the snapshot data of the latter pair is being stored per consistency group.
SSB2 RAID Manager command Cause of error 97B5 paircreate You cannot create the FS or SS pair for the specified P-VOL because the maximum number of snapshot ID (MU number) was used. 97B6 paircreate You cannot create the FS or SS pair because of one of the following reasons: • The new snapshot group was being created, but the maximum number of snapshot groups were defined. • The maximum number of pairs are defined in the specified snapshot group.
B Fast Snap GUI reference This appendix describes FS windows and dialog boxes. Replications window The following image shows this window.
Item Description Number of Differential Tables Number of differential tables in use. The number of differential tables is not increased or decreased by FS pair tasks because differential tables are not used for FS pairs. View Histories button Click to open the View History window. Replica LDEVs tab Only pairs that consist of the P-VOL and S-VOLs (the source and target volumes for FC Z or FCSE) allocated to each user are shown. Item Description LDEV ID Selected LDEV's identifier.
Summary tab Item Description Number of Pairs The number of pairs for each local replication software application type. Number of Reserve Volumes The number of reserved volumes: • Open: The number of open system reserved volumes. • Mainframe: The number of mainframe system reserved volumes. • Total: The total amount of reserved volumes. • Total including Secondary Volumes: This value includes the number of reserve volumes and number of S-VOLs for BC/SS, BC Z, FS and SS.
Item Description Number of Pair Tables The number of pair tables for the following combinations of software applications: • BC/BC Z/Auto LUN: Number of BC/SS, BC Z, and Auto LUN pair tables in use. • FS/SS: Number of FS and SS pair tables in use. Number of Differential Tables The number of differential tables in use. The number of differential tables is not increased or decreased by FS pair tasks because differential tables are not used for FS pairs.
Item Description (FS) COPY (SS) COPY The pair is being resynchronized. Status names are: (BC) COPY(RS)/COPY (BC Z) Resync/PENDING (FS) RCPY (SS) RCPY The pair is being resynchronized from secondary to P-VOL. Status names are: (BC) COPY(RS-R)/RCPY (BC Z) Resync-R/REVRSY (FS) RCPY (SS) RCPY The pair is being split in normal mode. Status names are: (BC) COPY(SP)/COPY (BC Z) SP-Pend/TRANS • This icon is used for the following: The volumes are paired.
Item Description • LUN ID: The S-VOL LDEV's LUN path LUN ID. • Emulation Type: The S-VOL's emulation type. • Capacity: The S-VOL's volume capacity. • CLPR: The S-VOL's CLPR number. Snapshot Date The date and time the snapshot was acquired. A hyphen (-) is shown for non-FS pairs or non-SS pairs Pool Name (ID) The pool name and identification number. A hyphen (-) is shown for non-FS pairs or non-SS pairs Copy Pace The copy speed.
The reserved volume for BC/SS and BC Z. Only LDEVs that are allocated to each user are shown. Item Description LDEV ID Reserved volume LDEV's identifier.
Item Description • Free: Consistency group not being used and is not reserved. • (Changing...): Status is in the process of changing. Number of Pairs Number of pairs for the consistency group in use. Reserve Mainframe CTGs Click to open the Reserved Mainframe CTGs window. Release Reserved Mainframe CTGs Click to open the Release Reserved Mainframe CTGs window. Export Click to open a dialog for downloading table information to a file.
Item Description Most Recent Snapshot Date The date and time the latest snapshot data was acquired. LDEV ID The P-VOL and S-VOL LDEV identification numbers. LDEV Name The P-VOL and S-VOL LDEV names. Pairs table All pairs, which are related to a pair shown on the Pair Property table, are shown. Item Description Primary Volume P-VOL information. Values: • LDEV ID: The P-VOL's LDEV identifier. • LDEV Name: The P-VOL's LDEV name. • Emulation Type: The P-VOL's emulation type.
View Pair Synchronous Rate window Pairs table Item Description Primary Volume The P-VOL information. Values: • LDEV ID: P-VOL's LDEV identifier • LDEV Name: P-VOL's LDEV name • CLPR: P-VOL's CLPR number Copy Type The copy type. Values: • BC-L1: BC/SS L1 pair • BC-L2: BC/SS L2 pair • FS: FS pair • SS: SS pair • BC Z: BC Z pair Snapshot Group The snapshot group name. A hyphen (-) is shown for non-FS pairs. If you do not configure a snapshot group for a FS pair, this item is blank.
Item Description Values • LDEV ID: S-VOL's LDEV identifier • LDEV Name: S-VOL's LDEV name • CLPR: S-VOL's CLPR number Copy Pace The copy speed. A hyphen (-) is shown for FS pairs or SS pairs. Mirror Unit The mirror unit number. Refresh Click to update the information in the Pairs table. View Histories window Setting fields Item Description Copy Type The copy type.
Histories table Only the task on the pairs that consist of the P-VOL and/or S-VOLs (the source and/or target volumes for FC Z/FCSE) allocated to each user are shown. Item Description Date The task date and time. Primary Volume (Source Volume for FC Z/FCSE) The information about the P-VOL (the source volume for /FCSE). Values: • LDEV ID: The P-VOL/source volume's LDEV identifier. • Provisioning Type: The P-VOL’s type (source volume).
Consistency Group Properties window Consistency Group Properties table Item Description CTG ID The consistency group identifier. Status The consistency group status: • BC Used: The consistency group is in use by BC/SS. • BC Z Used (RAID Manager): BC Z uses the consistency group and RAID Manager manages the consistency group. • BC Z Used (PPRC/BCM): BC Z uses the consistency group and PPRC and Business Continuity Manager manages the consistency group. • FS Used: FS uses the consistency group.
Item Description • Emulation Type: P-VOL's emulation type • Capacity: P-VOL's volume capacity • CLPR: P-VOL's CLPR number Copy Type The copy type. Values: • BC-L1: BC/SS L1 pair • BC-L2: BC/SS L2 pair • FS: FS pair • SS: SS pair • BC Z: BC Z pair Snapshot Group The snapshot group name. A hyphen (-) is shown for non-FS pairs. If you do not configure a snapshot group for a FS pair, this item is blank. Status The pair status. For more information, see “Pair status definitions” (page 51).
Create Pair window Select Pair Configuration window Item Description Copy Type The copy type. Values: • Snapshot • Business Copy for Mainframe • FS • Snapshot Emulation Type The emulation type. Values: OPEN-V For FS or SS, you can only specify OPEN-V. Number of Secondary Volumes Specify the total number of S-VOLs assigned to one P-VOL. Includes volumes for pairs being created, volumes in existing pairs, and volumes in L2 pairs (BC only). For BC/SS, this item is blank.
Select Primary Volumes window Item Description Use Primary Volumes of Snapshot Pairs Specifies whether you will use the P-VOL of snapshot pair. Values: • Yes: The storage system shows only P-VOLs of the pair that is already created in the Available LDEVs table. • No: The storage system shows only the LDEV of the pair that is not created yet in the Available LDEVs table. For BC/SS or BC Z, this item is blank. Port ID Port name of the LDEV's LUN path. Nothing is shown for BC Z.
Item Description Host Group Name The host group name of the LDEV's LUN path. Nothing is shown for BC Z. LUN ID The LUN ID of the LDEV's LUN path. (For BC Z) This item is blank. Provisioning Type The LDEV provisioning type. Values: • Basic: Internal volume • DP: THP volume • External: External volume Emulation Type Emulation type of the LDEV. Capacity Capacity of the LDEV. CLPR CLPR number of the LDEV. Number of Secondary Volumes The number of S-VOLs.
Item Description Provisioning Type The LDEV provisioning type. Values: • Basic: Internal volume • DP: THP volume • External: External volume Emulation Type The emulation type of LDEV. Capacity The capacity of LDEV. CLPR The CLPR number. Number of Secondary Volumes Displays the number of S-VOLs. The number for an L1 pair does not include the number of L2 S-VOLs (BC only). Primary Volume The information about the P-VOL is shown if the LDEV is the S-VOL of the existing pair.
Available Pools table Item Description Pool Name (ID) The nickname and ID of the pool. RAID Level The RAID level of the pool. Capacity • Total: The total pool capacity. • Used: The amount of pool capacity that is used. • Used (%): The percentage of pool capacity that is used. Note: The number truncated to an integer is shown. Drive Type/RPM The hard disk drive type and RPM. User-Defined Threshold (%) The threshold you configure.
Item Description Values: • Create New Snapshot Group: Type the new snapshot group name. • Use Existing Snapshot Group: Select the desired snapshot group. This item is shown only when you select FS as the copy type. Set button Click to move the selected LDEV to the Selected Pairs table. Clear button Click to return the selected S-VOL from the Selected Pairs table back to the Available LDEVs table. Available LDEVs table Item Description LDEV ID Identifier of LDEV, which you can specify as the S-VOL.
Item Description • Emulation Type: The P-VOL's emulation type. • Capacity: The P-VOL's volume capacity. Snapshot Group Snapshot group name. For FS, this item is blank. New Snapshot Group Indicates whether the Snapshot group is newly created or not. • Yes: Newly created Snapshot group • No: Already defined Snapshot group For FS or SS, this item is blank. Secondary Volume S-VOL information. Values: • LDEV ID: The S-VOL's LDEV identifier. If an LDEV is not allocated, this field is blank.
Confirm window Selected Pairs table Item Description Primary Volume P-VOL information. Values: • LDEV ID: The P-VOL's LDEV identifier. • LDEV Name: The P-VOL's LDEV name. • Port ID: The port name of the P-VOL LDEV's LUN path. • Host Group Name: Host group name of the P-VOL LDEV's LUN path. • LUN ID: LUN ID of the P-VOL LDEV's LUN path. • Emulation Type: The P-VOL's emulation type. • Capacity: The P-VOL's volume capacity. • CLPR: The P-VOL's CLPR number. Copy Type The copy type.
Item Description Values: • LDEV ID: The S-VOL's LDEV identifier. • LDEV Name: The S-VOL's LDEV name. • Port ID: The S-VOL LDEV's LUN path port name. • Host Group Name: The S-VOL LDEV's LUN path host group name. • LUN ID: The S-VOL LDEV's LUN path LUN ID. • Emulation Type: The S-VOL's emulation type. • Capacity: The S-VOL's volume capacity. • CLPR: The S-VOL's CLPR number. Pool Name (ID) The pool name and ID number. Split Pairs wizard Use this wizard to split pairs.
Item Description Values: • LDEV ID: The P-VOL's LDEV identifier. • LDEV Name: The P-VOL's LDEV name. • Emulation Type: The P-VOL's emulation type. • Capacity: The P-VOL's volume capacity. • CLPR: The P-VOL's CLPR number. Copy Type The copy type. Values: • BC-L1: BC/SS L1 pair • BC-L2: BC/SS L2 pair • FS: FS pair • SS: SS pair • BC Z: BC Z pair Snapshot Group Snapshot group name. If you do not configure a snapshot group for the FS pair, this item is blank. Status Pair status.
Confirm window Selected Pairs table Item Description Primary Volume P-VOL information. Values: • LDEV ID: The P-VOL's LDEV identifier. • LDEV Name: The P-VOL's LDEV name. • Emulation Type: The P-VOL's emulation type. • Capacity: The P-VOL's volume capacity. • CLPR: The P-VOL's CLPR number. Copy Type The copy type. Values: • BC-L1: BC/SS L1 pair • BC-L2: BC/SS L2 pair • FS: FS pair • SS: SS pair • BC Z: BC Z pair Snapshot Group Snapshot group name.
Item Description Values: • Quick Split: Immediately splits the pair. • Steady Split: The differential data is copied and then the pair is split. Copy Pace The copy speed. A hyphen (-) is shown for FS pairs or SS pairs. Secondary Volume S-VOL information. Values: • LDEV ID: S-VOL's LDEV identifier • LDEV Name: S-VOL's LDEV name • Emulation Type: S-VOL's emulation type • Capacity: S-VOL's volume capacity • CLPR: S-VOL's CLPR number Pool Name (ID) The pool name and ID number.
Resync pairs window Selected Pairs table Item Description Primary Volume P-VOL information. Values: • LDEV ID: The P-VOL's LDEV identifier. • LDEV Name: The P-VOL's LDEV name. • Emulation Type: The P-VOL's emulation type. • Capacity: The P-VOL's volume capacity. • CLPR: The P-VOL's CLPR number. Copy Type The copy type. Values: • BC-L1: BC/SS L1 pair • BC-L2: BC/SS L2 pair • FS: FS pair • SS: SS pair • BC Z: BC Z pair Snapshot Group The snapshot group name.
Item Description Secondary Volume S-VOL information. Values: • LDEV ID: The S-VOL's LDEV identifier. • LDEV Name The S-VOL's LDEV name. • Emulation Type: The S-VOL's emulation type. • Capacity: The S-VOL's volume capacity. • CLPR: The S-VOL's CLPR number. Snapshot Date The date and time the snapshot was acquired. Pool Name (ID) The pool name and identification number. Mirror Unit The mirror unit number. Resync Type The type of resynchronization.
Confirm window Selected Pairs table Item Description Primary Volume P-VOL information. Values: • LDEV ID: The P-VOL's LDEV identifier. • LDEV Name: The P-VOL's LDEV name. • Emulation Type: The P-VOL's emulation type. • Capacity: The P-VOL's volume capacity. • CLPR: The P-VOL's CLPR number. Copy Type The copy type. Values: • BC-L1: BC/SS L1 pair • BC-L2: BC/SS L2 pair • FS: FS pair • SS: SS pair • BC Z: BC Z pair Snapshot Group Snapshot group name.
Item Description Resync Type The type of resynchronization is specified: • Normal Copy (Primary > Secondary): All differential data is updated on the S-VOL. • Reverse Copy (Secondary > Primary): All differential data is updated on the P-VOL. • Quick Resync (Primary > Secondary): Immediately changes the pair status to “PAIR”. The differential data is copied during the updating copy. • Quick Restore (Secondary > Primary): Replaces the P-VOL and the S-VOL.
Selected Pairs table Item Description Primary Volume P-VOL information. Values: • LDEV ID: The P-VOL's LDEV identifier. • LDEV Name: The P-VOL's LDEV name. • Emulation Type: The P-VOL's emulation type. • Capacity: The P-VOL's volume capacity. • CLPR: The P-VOL's CLPR number. Copy Type The copy type. Values: • BC-L1: BC/SS L1 pair • BC-L2: BC/SS L2 pair • FS: FS pair • SS: SS pair • BC Z: BC Z pair Snapshot Group The snapshot group name.
BC/FS/SS System Options table Item Description System Option The system options that you can change. Values: • Swap & Freeze: Quick Restores and then immediately saves the data. Note: Enabling this option with Quick Restore inhibits the update copy operation and the paired S-VOL is not updated. • Host I/O Performance: Gives weight to I/O response rather than the copy time. This option controls the copy operation and improves the host I/O response. • Copy Pace Ext. Slower1 • Copy Pace Ext.
Item Description Values: • Swap & Freeze: Quick Restores and then immediately saves the data. Note: Enabling this option with Quick Restore inhibits the update copy operation and the paired S-VOL (T-VOL for FC Z or FCSE) is not updated. • Host I/O Performance: Gives weight to I/O response rather than the copy time. This option controls the copy operation and improves the host I/O response. • FC Slower Copy1 (FC Z or FCSE only): Reduces the multiplicity of background copy into half.
BC/FS/SS System Options table Item Description System Option The system options that you can change. Status Shows whether the option is currently enabled or disabled. BC Z/FC Z/FCSE System Options table Item Description System Option The system options that you can change. Status Shows whether the option is currently enabled or disabled.
Glossary BC P9000 or XP Business Copy. An HP application that provides volume-level, point-in-time copies in the disk array. CLPR Cache logical partition. Cnt Ac-J P9000 or XP Continuous Access Journal software. Cnt Ac-S P9000 or XP Continuous Access Synchronous software. command device A volume in the disk array that accepts Continuous Access, Business Copy, or P9000 for Business Continuity Manager control operations, which are then executed by the array. CU Control unit. DKC Disk controller.
RAID5-level data storage A RAID that provides data striping at the byte level and also stripe error correction information. RAID5 configurations can tolerate one drive failure. Even with a failed drive, the data in a RAID5 volume can still be accessed normally. RAID6-level data storage A RAID that provides data striping at the byte level and also stripe error correction information. RAID6 configurations can tolerate two drive failures.
index deleting, 61 increasing capacity, 58 B blocked pool, 64 blocked pool, recovering, 66 blocked volume, 65 C consistency group, monitoring, 53 contacting HP, 69 conventions document, 70 storage capacity values, 70 text symbols, 71 creating pools, 36 D deleting V-VOLs, 62 document conventions, 70 related information, 69 documentation HP website, 69 providing feedback, 69 F free pool capacity, 57 H help obtaining, 69 Histories window, 90 host access problem, 66 HP subscription service, 69 technical su
