hp_snapshotug rootsan technologies pvt ltd

8/6/2019 hp_SnapshotUG Rootsan technologies Pvt Ltd

1/74

HP StorageWorks

Snapshot XP user guide

Part number: T1713-96021Fourth edition: June 2006


2/74

Legal and notice information

Copyright 2005, 2006 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. Governmentunder vendors standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.

Adobe and Acrobat are trademarks of Adobe Systems Incorporated.

z/OS, AIX, PPRC and ESCON are registered trademarks or trademarks of International Business Machines Corporation (IBM).

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and othercountries.

Solaris is a trademark of Sun Microsystems, Inc.

HP-UX is a registered trademark of Hewlett-Packard Company.

Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation in the U.S. and other countries.

Snapshot XP user guide


3/74

Snapshot XP user guide 3

About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Supported storage platforms and firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8HP web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Overview of copy solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Snapshot XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Business Copy XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Snapshot XP functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Volumes Snapshot XP uses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Snapshot XP primary volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Snapshot XP secondary volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Snapshot XP pool volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Creating virtual volume management areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Creating pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Creating virtual volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Creating Snapshot XP pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Storing snapshot data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Restoring Snapshot XP pairs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Deleting snapshot data or Snapshot XP pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Viewing Snapshot XP pair information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3 Requirements for Snapshot XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Requirements for using Snapshot XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Installing and uninstalling Snapshot XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Installing Snapshot XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Uninstalling Snapshot XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Calculating the number of Snapshot XP pairs you can create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Using the number of differential tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Using shared memory capacity for the virtual volume management area . . . . . . . . . . . . . . . . . . . . . . 23Using the number of pair tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4 Using Snapshot XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Procedure for using Snapshot XP processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Status of Snapshot XP pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Notes on creating pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Defining pool capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Using external LUs as pool-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Notes on using Snapshot XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Switching off the power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Replacing the microprogram offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Combining Snapshot XP with other software products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Combining Snapshot XP with Business Copy XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Combining Snapshot XP with Continuous Access XP or Continuous Access XP Journal . . . . . . . . . . . . . 33Combining Snapshot XP with Auto LUN XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Combining Snapshot XP with LUN Security XP Extension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Contents


4/74

4

5 Snapshot XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Displaying the Business Copy XP main pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Volume list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Preset List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Specifying conditions for volumes displayed in the volume list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Creating or deleting pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Creating new pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Changing pool information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Deleting pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Deleting one pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Deleting multiple pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Initializing V-VOL management areas or pool management blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . 48Initializing V-VOL management areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Initializing pool management blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Creating or deleting virtual volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Creating new virtual volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Deleting virtual volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Creating Snapshot XP pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Storing snapshot data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Restoring Snapshot XP pairs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Deleting snapshot data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Deleting Snapshot XP pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Deleting Snapshot XP pairs by selecting pairs per port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Deleting Snapshot XP pairs by selecting pairs per pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Displaying detailed information about Snapshot XP pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Detail pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59S-Vol Path Information pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Displaying operation history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65General troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Troubleshooting Snapshot XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Recovering blocked pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Recovering pool-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Recovering pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Recovering Snapshot XP pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Recovering V-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Completing pool-related SIMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Figures1 Snapshot XP mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Snapshot XP pair and pool mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Procedure for using Snapshot XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Snapshot XP pair status transition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Business Copy XP main pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

6 Volume list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 Preset List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Display Filter pane (Snapshot XP tab selected). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Pool pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4310 New Pool pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4711 Change Pool Information pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4812 V-VOL pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4913 New V-VOL Group pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5214 Create V-VOL wizard pane (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5215 Create V-VOL wizard pane (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5316 Create V-VOL wizard pane (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5417 Pairsplit-S pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57


5/74


18 Snapshot XP pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5819 Detail pane for Snapshot XP pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6020 S-Vol Path pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6121 History pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Tables1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Requirements for Snapshot XP P-VOLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Requirements for Snapshot XP S-VOLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4 Requirements for Snapshot XP pool-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Requirements for using Snapshot XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Whether hosts can access P-VOLs and S-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Pair status and results of RAID Manager XP commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Volume sharing with other software products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Snapshot XP operations when Snapshot XP P-VOL and Business Copy XP P-VOL are shared . . . . . . . . . 3110 Snapshot XP operations when Snapshot XP P-VOL and Business Copy XP S-VOL are shared . . . . . . . . . 3111 Business Copy XP operations when Snapshot XP P-VOL and Business Copy XP P-VOL are shared. . . . . . 3212 Business Copy XP operations when Snapshot XP P-VOL and Business Copy XP S-VOL are shared . . . . . 3213 Snapshot XP operations when Snapshot XP P-VOL and Continuous Access XP/Continuous Access XP

Journal are shared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3314 Snapshot XP operations when Snapshot XP P-VOL and Continuous Access XP/Continuous Access XP

Journal S-VOL are shared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3315 Continuous Access XP/Continuous Access XP Journal operations when Snapshot XP P-VOL and

Continuous Access XP/Continuous Access XP Journal P-VOL are shared . . . . . . . . . . . . . . . . . . . . . . . 3316 Continuous Access XP/Continuous Access XP Journal operations when Snapshot XP P-VOL and

Continuous Access XP/Continuous Access XP Journal S-VOL are shared . . . . . . . . . . . . . . . . . . . . . . . 3417 Information displayed in Prog./Sync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3918 Shortcut menu in volume list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4019 Shortcut menu in Preset list on Business Copy XP main pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4120 Shortcut menu in Pool tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4421 Shortcut menu in the V-VOL group tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5022 Snapshot XP history reference codes and messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6223 Troubleshooting for Snapshot XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65


6/74

6


7/74


About this guideThis guide provides information about:

Understanding Snapshot XP and Business Copy XP

Understanding Snapshot XP functions

Preparing to use Snapshot XP

Using Snapshot XP Troubleshooting Snapshot XP

Supported storage platforms and firmwareIn this guide, the term arrayrefers to the following storage platforms:

HP StorageWorks XP12000 Disk Array

HP StorageWorks XP10000 Disk Array

HP StorageWorks 200 Storage Virtualization System

For information about required firmware versions, see the HP StorageWorks XP Remote Web Consoleuser guide for XP12000/XP10000/SVS200.

Intended audienceThis guide is intended for customers and HP-authorized service providers with knowledge of:

Disk array hardware and software

Data processing and RAID storage subsystems and their basic functions

PrerequisitesPrerequisites for using this product include:

Installing the HP StorageWorks disk array(s)

Installing the license key for this product

Related documentationThe following documents provide related information:

HP StorageWorks XP glossary

HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200

HP StorageWorks Auto LUN XP user guide for the XP12000/XP10000

HP StorageWorks Business Copy XP user guide for the XP12000/XP10000/SVS200

HP StorageWorks Continuous Access XP user guide for the XP12000/XP10000/SVS200

HP StorageWorks Continuous Access XP Journal user guide

HP StorageWorks External Storage XP user guide

HP StorageWorks LUN Configuration and Security Manager XP user guide for theXP12000/XP10000/SVS200

HP StorageWorks LUN Security XP Extension user guide

Hitachi ShadowImage for z/OS user guide

You can find the above documents at http://www.hp.com/support/rwc/manuals

HP StorageWorks RAID Manager XP user guide

You can find the above document at http://www.hp.com/support/manuals
http://www.hp.com/support/rwc/manuals/http://www.hp.com/support/manuals/http://www.hp.com/support/manuals/http://www.hp.com/support/rwc/manuals/


8/74

8

Document conventions and symbols

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

HP technical supportTelephone numbers for worldwide technical support are listed on the HP support web site:http://www.hp.com/support/.

Collect the following information before calling:

Technical support registration number (if applicable)

Product serial numbers Product model names and numbers

Error messages

Operating system type and revision level

Detailed, specific questions

For continuous quality improvement, calls may be recorded or monitored.

Subscription serviceHP recommends that you register your product at the Subscribers Choice for Business web site:http://www.hp.com/go/e-updates.

Table 1 Document conventions

Convention Element

Blue text: Table 1 Cross-reference links and e-mail addresses

Blue, underlined text: (http://www.hp.com) Web site addresses

Bold text Keys that are pressed

Text typed into a GUI element, such as a box

GUI elements that are clicked or selected, such asmenu and list items, buttons, and check boxes

Italic text Text emphasis

Monospace text File and directory names

System output

Code

Commands, their arguments, and argument values

Monospace, italic text Code variables

Command variables

Monospace, bold text Emphasized monospace text
http://www.hp.com/support/http://www.hp.com/go/e-updates/http://www.hp.com/go/e-updates/http://www.hp.com/support/


9/74


After registering, you will receive e-mail notification of product enhancements, new driver versions,firmware updates, and other product resources.

HP web sitesFor additional information, see the following HP web sites:

http://www.hp.com

http://www.hp.com/go/storage

http://www.hp.com/service_locator

http://www.hp.com/support/manuals

http://www.hp.com/support/downloads

http://www.hp.com/support/rwc/manuals

Documentation feedbackHP welcomes your feedback.

To make comments and suggestions about product documentation, please send a message [email protected]. All submissions become the property of HP.
http://www.hp.com/http://www.hp.com/go/storage/http://www.hp.com/service_locator/http://www.hp.com/support/manuals/http://www.hp.com/support/downloads/http://www.hp.com/support/rwc/manuals/http://www.hp.com/support/rwc/manuals/http://www.hp.com/support/downloads/http://www.hp.com/support/manuals/http://www.hp.com/service_locator/http://www.hp.com/go/storage/http://www.hp.com/


10/74

10


11/74


1 Overview of copy solutionsHP StorageWorks XP12000/XP10000/SVS200 arrays provide an extensive suite of data replicationsoftware. This chapter describes HP StorageWorks Snapshot XP. This chapter also covers portions ofHP StorageWorks Business Copy XP because Snapshot XP is an integrated feature of Business Copy XP.

NOTE: The use of Snapshot XP, Business Copy XP, and all other software products is governed by theterms of your license agreements with Hewlett-Packard.

IMPORTANT: This guide contains information about internal disks or LDEVs. Unlike theXP12000/XP10000 Disk Arrays, the SVS200 has no internal disks. Therefore, information about internaldisks or LDEVs does not apply to the SVS200.

Snapshot XPSnapshot XP, like Business Copy XP, enables you to create multiple real-time online local copies of logical

volumes. Snapshot XP enables applications and solutions such as zero-downtime backup and disasterrecovery. While Business Copy XP creates complete copies, Snapshot XP creates space-efficient copiesthat replicate only data from the primary volume that was rewritten using less disk space, which reducescosts. Snapshot XP is supported on open systems such as UNIX and PC servers. Snapshot XP is anintegrated feature of Business Copy XP.

Snapshot XP creates pairs of primary volumes (P-VOLs) and secondary volumes (S-VOLs). Snapshot XPsecondary volumes are partial copies containing only changed P-VOLs. Snapshot XP is also known asCopy-on-Write Snapshot. All changed data is kept in common snapshot pools (pool-VOLs). Pointers keptin mapping tables allow access to secondary volumes through virtual volumes (V-VOLs). The S-VOL iscomposed of data in the pool-VOL (old data that has since changed in the P-VOL) and data in the P-VOL(data that has not changed yet). The P-VOL/S-VOL pair that Snapshot XP creates is called a Snapshot XPpair.


12/74

12 Overview of copy solutions

Figure 1 illustrates the mechanism Snapshot XP uses to copy data in the array.

Figure 1 Snapshot XP mechanism

In Figure 1, Data A is stored in the Snapshot XP pairs P-VOL. When the host requests to update Data A toData B, Snapshot XP copies Data A to the pool volume (pool-VOL) in the pool before updating the P-VOL.After the copy operation for Data A is complete, Snapshot XP writes Data B to the area where Data A wasstored in the P-VOL, and the P-VOL is updated. From the S-VOL, you can access Data B in the P-VOL andData A in the pool-VOL.

Snapshot XP and Business Copy XP are similar because both create pairs. However, Snapshot XP pairS-VOLs do not consume array capacity because the S-VOLs are actually virtual volumes. Therefore,Snapshot XP reduces the capacity the array uses as a whole.

The copy process for Business Copy XP pairs takes longer because all P-VOL data is copied to the S-VOL.On the other hand, the copy process for Snapshot XP pairs takes less time compared to the copy processfor Business Copy XP pairs because, as you can see in Figure 1, only updated P-VOL data is copied to thepool-VOL. The same data in the P-VOL can be referenced by accessing the Snapshot XP pairs S-VOL, butthe actual data does not exist in the S-VOL. The P-VOL data can be referenced using the S-VOL.

As described previously, Snapshot XP requires less capacity in the array and less copy processing timecompared to Business Copy XP. HP recommends using Snapshot XP to copy and manage data in the shortterm with reduced costs. However, Snapshot XP only copies some of the P-VOL data. Therefore, datastored in the S-VOL is not guaranteed in the following:

When a physical failure occurs in a P-VOL

When a pool is blocked

On the other hand, Business Copy XP copies all P-VOL data to the S-VOL. Therefore, even if a physicalfailure occurs in a P-VOL, you can recover the P-VOL data using the S-VOL data. Business Copy XP provideshigher integrity than Snapshot XP. HP recommends using Business Copy XP when data integrity is moreimportant than copy process speed or array capacity. For a functional overview of Business Copy XP, seeBusiness Copy XP on page 13.


13/74


Business Copy XPUse Business Copy XP to maintain array-internal copies of all user data on the array for data on opensystems such as UNIX and PC servers. Business Copy XP creates a pair of P-VOL and S-VOL, both ofwhich are logical volumes in the same array. Pairs that Business Copy XP creates are called BusinessCopy XP pairs.

RAID-protected S-VOLs are created within the same array as the P-VOL. Use Business Copy XP to createup to three S-VOLs for a P-VOL. Using Business Copy XP with External Storage XP, you can use externalvolumes to create Business Copy XP pairs.

Unlike the Snapshot XP pairs S-VOL, all P-VOL data is copied to the Business Copy XP pairs S-VOL.Therefore, the capacity of the Business Copy XP pairs P-VOL and S-VOL is the same. In addition, BusinessCopy XPs copy process takes longer because all P-VOL data is copied to the S-VOL.

As described previously, Business Copy XP requires larger array capacity and the copy process takeslonger compared to Snapshot XP. However, when a failure disables access to one of the pairs volumes,the array can continue to operate using data stored in the other volume because the same data is storedin the P-VOL and S-VOL. HP recommends using Business Copy XP when data integrity is more importantthan copy process speed or array capacity. For more information, see the HP StorageWorks BusinessCopy XP user guide for the XP12000/XP10000/SVS200.


14/74

14 Overview of copy solutions


15/74


2 Snapshot XP functionsSnapshot XP creates pairs consisting of a P-VOL and S-VOL. When creating a pair, Snapshot XP uses aV-VOL as the pairs S-VOL. In addition, you can manage the P-VOLs snapshot data by copying the datato an area called the pool. This chapter describes the volumes Snapshot XP uses first, and then describesSnapshot XP functions.

Volumes Snapshot XP usesSnapshot XP uses the P-VOL, S-VOL, and pool-VOL. This section describes the requirements (such asemulation type or path definition) for the volumes Snapshot XP uses.

Snapshot XP primary volumes

Snapshot XP secondary volumes

Table 2 Requirements for Snapshot XP P-VOLs

Item Requirement

Volume type Logical volume (LDEV)

LUSE volume can be specified.

NOTE: A LUSE P-VOL must be paired with an S-VOL that has the same size and structure.For example, if a LUSE P-VOL is created by combining volumes that have 1 GB, 2 GB, and3 GB in that order, you must specify a LUSE volume that has exactly the same size andcombination order as the S-VOL.

You cannot specify the following volumes as Snapshot XP P-VOLs:

Volumes used as pool-VOLs

Volumes used as a Snapshot XP pairs S-VOL

Volumes used by a Flex Copy XP pair

NAS volumes

Emulation type OPEN-V

Maximum number 8,191

For more information about the maximum number of Snapshot XP pairs that can be created,see Calculating the number of Snapshot XP pairs you can create on page 22.

Path definition Required

Maximum capacity 2 TB

Table 3 Requirements for Snapshot XP S-VOLs

Item RequirementVolume type V-VOL

You cannot specify the following volumes as Snapshot XP S-VOLs:

Volumes used as a Snapshot XP pairs S-VOL

Volumes used by another software products pair or migration plan

NOTE: A LUSE S-VOL must be paired with a P-VOL that has the same size and structure.



16/74

16 Snapshot XP functions

Snapshot XP pool volumes

Creating virtual volume management areasTo use Snapshot XP, you must create virtual volume (V-VOL) management areas. The V-VOL managementarea is an important area for associating Snapshot XP S-VOLs (V-VOL) with pool-VOLs. The V-VOLmanagement area is automatically created when additional shared memory is installed. For moreinformation about shared memory requirements, see Table 5. To install additional shared memory,contact your HP account support representative.

There are two areas in the V-VOL management area: pool management block and pool associationinformation. When creating pools or Snapshot XP pairs, the pool management block or pool associationinformation is stored in the V-VOL management area. Therefore, the V-VOL management areas availablecapacity decreases. When all the V-VOL management areas capacity is used, the capacity ratio of thepool management block and pool association information in the V-VOL management area is fixed. If the

pool management blocks capacity is insufficient, problems might occur. For example, you cannot createpools or pools with a large capacity. To solve such problems, initialize the V-VOL management area. Formore information, see Initializing V-VOL management areas or pool management blocks on page 48.

Creating poolsA pool is an area where the snapshot data that Snapshot XP obtains is stored. A pool consists of multiplepool-VOLs, and snapshot data is stored in a pool-VOL. You can register 1,024 pool-VOLs in a pool. You


For more information about the maximum number of Snapshot XP pairs you can create, seeCalculating the number of Snapshot XP pairs you can create on page 22.

Path definition Required

Table 3 Requirements for Snapshot XP S-VOLs (continued)

Item Requirement

Table 4 Requirements for Snapshot XP pool-VOLs

Item Requirement

Volume type Logical volume (LDEV)

You cannot specify the following volumes as Snapshot XP pool-VOLs:

LUSE volumes

Volumes used as a Snapshot XP pairs P-VOL or S-VOL

Volumes used by another software products pair or migration plan

Volumes set with the Protect or Read Only attribute, or set to the S-VOL Disable setting

by LUN Security XP Extension NAS volumes



However, the maximum number of pool-VOLs that can be registered in each pool is 1,024.In addition, a volume already registered as a pool-VOL in a pool cannot be registered inanother pool.

Path definition Not required

Volumes with path definitions cannot be specified as pool-VOLs.


17/74


can create 128 pools in an array. Figure 2 illustrates the relationship between Snapshot XP pairs andpools.

Figure 2 Snapshot XP pair and pool mechanism

You must create a pool when using Snapshot XP. You can add pool-VOLs registered in a pool, but cannotdelete pool-VOLs during the operation. In addition, to delete the pool itself, you must delete all snapshotdata in the pool.

CAUTION: A pools capacity equals the total capacity of the pool-VOLs registered in the pool. TheSnapshot XP pairs status is PSUE (status when failure occurred) when the pools usage rate exceeds thepools capacity as a result of writing data in that pairs volume. You cannot store Snapshot data in thepool, and you cannot create Snapshot XP pairs. For more information about ensuring sufficient pool

capacity, see Notes on creating pools on page 28.

To create a pool, use the Pool pane in Command View XP or XP Remote Web Console. For moreinformation, see Creating or deleting pools on page 43.

Creating virtual volumesA V-VOL is a virtual volume defined in a VDEV. You must create a V-VOL before you create a Snapshot XPpair because you must use a V-VOL as the Snapshot XP pairs S-VOL.

A V-VOLs definition cannot be released if the V-VOL is being used as a Snapshot XP pairs S-VOL. Torelease the definition, delete the Snapshot XP pair using the V-VOL.

CAUTION: If you are using HP-UX as a host server, observe the following when executing thecommand on V-VOLs to recognize the device from the host server:

If the host server already recognizes the device, do not change its volumes to V-VOLs.

Before executing the command to recognize the device, create Snapshot XP pairs and store snapshotdata.

If you do not follow these cautions, an error might occur and the host server might be terminated. If thehost server is terminated because of the command to recognize the device, retry the command using thefollowing steps:

1. Force the command process and its parent process to terminate.


18/74


2. Create a Snapshot XP pair.

3. Store the snapshot data in the pool.

4. Execute the command again to recognize the device.

NOTE:

Servers (including RAID Manager XP) show V-VOLs with emulation type 0 (for example, OPEN-0V).When creating a Snapshot XP pair, specify the volume with emulation type 0, such as OPEN-0V, as theS-VOL.

Before creating a V-VOL, you must define a V-VOL group. The emulation type of the V-VOLs and theemulation type of the VDEV for a V-VOL group are OPEN-V. In addition, the VDEVs capacity is always2 TB. Therefore, the maximum capacity of a V-VOL is also 2 TB.

To delete a V-VOL, use the V-VOL pane in Command View XP or XP Remote Web Console. For moreinformation, see Creating or deleting virtual volumes on page 49.

Creating Snapshot XP pairsA Snapshot XP pair uses a V-VOL as its S-VOL. Therefore, you must create a V-VOL before creating aSnapshot XP pair. In Snapshot XP, you can specify up to 64 S-VOLs for a P-VOL.

To create Snapshot XP pairs, use a RAID Manager XP command. For more information, see CreatingSnapshot XP pairs on page 55.

CAUTION: When creating Snapshot XP pairs, you decide which pool the pairs use. If you create two ormore Snapshot XP pairs that share the same P-VOL, you must specify the same pool for these pairs. Forexample, if you specify three S-VOLs for one P-VOL, you must specify the same pool for these three pairs.

NOTE: When deleting a Snapshot XP pair, the volumes status becomes SMPL(PD). You cannot createpairs using SMPL(PD) volumes. If the volumes are in SMPL(PD) status, wait for a while and issue thecommand to create pairs after the volumes status changes to SMPL.

Use the Business Copy XP main pane to see the volumes status. Using RAID Manager XP, you can checkthe volume status with the pairdisplay command, but you cannot distinguish between SMPL andSMPL(PD) volumes. To distinguish between SMPL and SMPL(PD) volumes using RAID Manager XP, issuethe inqraid command as well. The inqraid command shows whether Snapshot XP is using thevolume. If Snapshot XP is not using the volume, the volume status is SMPL. If Snapshot XP is using thevolume, the volume status is SMPL(PD).

Storing snapshot dataSnapshot data is a replica of data in a Snapshot XP pairs P-VOL, and is stored in a pool. When theP-VOL is updated, updated data is copied to the pool as snapshot data before the P-VOL is updated. Thisprocess is called storing snapshot data.

If you issue a command to a Snapshot XP pair to store snapshot data, the snapshot data is stored in thepool when a host issues a write request to the Snapshot XP pairs P-VOL.

To store snapshot data in a pool, use a RAID Manager XP command. For more information, see Storingsnapshot data on page 55.

Restoring Snapshot XP pairsSnapshot XP can restore a P-VOLs contents to the state when the snapshot data was stored in the pool bywriting the snapshot data back to the P-VOL. Writing the snapshot data to the P-VOL is called restorationof a Snapshot XP pair.


19/74


NOTE: If you restore the pair when data is written in the S-VOL instead of the snapshot data, data in theS-VOL is written back to the P-VOL.

If there are problems with the P-VOL data during a failure, you can restore the P-VOL to the normal statewhen the snapshot data was stored by executing restoration.

To restore a Snapshot XP pair, use a RAID Manager command. For more information, see RestoringSnapshot XP pairs on page 55.

Copy Threshold option: If the arrays load increases, host server I/O performance (response) might bedegraded. If Snapshot XP performs restore operations when the arrays load is heavy, it is more likely thathost server I/O performance (response) might be degraded. The Copy Threshold option temporarily stopscopy processing caused by restore operations when the arrays load is heavy. If you enable this option,you can minimize the degradation of host I/O performance by temporarily stopping copy processingcaused by restore operations when the arrays load is heavy.

The Copy Threshold option is effective only when the arrays load is heavy. When the Copy Thresholdoption is enabled, all copy processing by restore operations stops. For more information about setting theCopy Threshold option, contact your HP account support representative.

NOTE: Copy operations stopped by the Copy Threshold option resume when the arrays load becomelight. If this option is enabled, copy operations for Snapshot XP and the following software products stopwhen the arrays load is heavy:

Business Copy XP

ShadowImage for z/OS

Hitachi FlashCopy Mirroring

Hitachi FlashCopy Mirroring Version 2

Flex Copy XP

Auto LUN XP

Deleting snapshot data or Snapshot XP pairsThe status of the Snapshot XP pair is PSUE (status when failure occurred) when, as a result of writing datain that pairs volume, the snapshot datas capacity exceeds the pools capacity specified when the poolwas created. You cannot create Snapshot XP pairs and store snapshot data in the pool. Therefore, youmust delete unnecessary snapshot data. There are two ways to delete snapshot data. One way is to deletethe Snapshot XP pair itself. The other way is to delete only the snapshot data.

When deleting the Snapshot XP pair itself, snapshot data stored in the pool is deleted and the relationshipbetween the P-VOL and S-VOL is released. On the other hand, if you delete only snapshot data, therelationship between the P-VOL and S-VOL is maintained. When deleting only snapshot data, thesnapshot ID of the deleted snapshot data can be assigned to the newly stored snapshot data of theSnapshot XP pair.

To delete snapshot data or Snapshot XP pairs, use a RAID Manager XP command. When deletingSnapshot XP pairs, you can also use the Pairsplit -S pane in Command View XP or XP Remote WebConsole. For more information, see Deleting snapshot data on page 56 or Deleting Snapshot XPpairs on page 56.

NOTE:

After issuing the command to delete snapshot data, no more snapshot data for that Snapshot XP pairis stored in the pool, even if the host tries to write data in the P-VOL. To store snapshot data for thatSnapshot XP pair again, you must issue the command for storing snapshot data.


20/74


The required time for deleting snapshot data or Snapshot XP pairs is several seconds, and sometimesmore than 10 minutes. The time increases if the deleted pair uses a large amount of the pool or ifmultiple pairs are deleted at one time.

The more disk adaptors used in the array, the shorter the time required for deleting snapshot data orSnapshot XP pairs. Since the XP10000/SVS200 has a smaller number of disk adaptors than theXP12000, the XP10000/SVS200 needs a longer time to delete snapshot data or Snapshot XP pairsthan the XP12000, even if the operational conditions are the same.

When deleting a Snapshot XP pair, the volumes status becomes SMPL(PD). Use the Business Copy XPmain pane to see the volumes status. Using RAID Manager XP, you can check the volume status withthe pairdisplay command, but you cannot distinguish between SMPL and SMPL(PD) volumes. Todistinguish between SMPL and SMPL(PD) volumes using RAID Manager XP, issue the inqraidcommand as well. The inqraid command shows whether Snapshot XP is using the volume. IfSnapshot XP is not using the volume, the volume status is SMPL. If Snapshot XP is using the volume, thevolume status is SMPL(PD).

Viewing Snapshot XP pair informationYou can view information about Snapshot XP pairs, such as snapshot ID or pair status, on the Detail panein Command View XP or XP Remote Web Console. For more information, see Deleting Snapshot XPpairs on page 56.

In addition, you can view operation history for Snapshot XP pairs, such as creating or deleting SnapshotXP pairs and storing snapshot data, on the History pane. For more information, see Displaying detailedinformation about Snapshot XP pairs on page 59.


21/74


3 Requirements for Snapshot XP operationsThis chapter describes requirements for using Snapshot XP, installing Snapshot XP, and calculating thenumber of pairs that Snapshot XP can create.

Requirements for using Snapshot XP

For requirements of volumes used for Snapshot XP, see Volumes Snapshot XP uses on page 15.

Installing and uninstalling Snapshot XPThis section describes procedures for installing and uninstalling Snapshot XP.

Installing Snapshot XP1. Install additional shared memory for differential tables.

2. Install additional shared memory for the V-VOL management area.

When using an XP10000/SVS200, you do not need to install additional shared memory. You onlyneed to define shared memory for the V-VOL management area.

3. Install Business Copy XP, which is a prerequisite for Snapshot XP.

4. Install Snapshot XP.

NOTE: Contact your HP account support representative to install additional shared memory for the V-VOL

management area.

After installing additional shared memory for the V-VOL management area, you cannot partiallyuninstall it. To uninstall additional shared memory for the V-VOL management area, you must uninstallthe entire shared memory added for the V-VOL management area.

Skip step 1 if shared memory for the differential tables is already installed.

Note that step 2 and step 3 are interchangeable.

Skip step 3 if Business Copy XP is already installed on the array.

Table 5 Requirements for using Snapshot XP

Item Requirement

RAID level RAID1, RAID5, or RAID6

Shared memory Install shared memory for the differential table on the base board.

Configure shared memory so you can create the V-VOL management area in theshared memory.

For the XP12000/SVS200, reserve from 512 MB 2 to 2 GB 2 capacity of theshared memory for the V-VOL management area on the optional board.1 For moreinformation, see Calculating the number of Snapshot XP pairs you can create onpage 22.

1. Because the XP10000/SVS200 does not have the optional board, you must reserve 342 MB 2 capacity of the sharedmemory on the basic board if you are using the XP10000/SVS200.

Prerequisite software product Install Business Copy XP.

Pool Create the pool. The pools maximum capacity changes with shared memoryscapacity.

V-VOL Create the V-VOL.

Operation Command View XP or XP Remote Web Console and RAID Manager XP arerequired to operate Snapshot XP.


22/74

22 Requirements for Snapshot XP operations

Uninstalling Snapshot XP1. Delete all Snapshot XP pairs.

2. Delete all pools.

3. Delete all V-VOLs.

4. Uninstall Snapshot XP.

For more information about deleting pairs, pools, and V-VOLs, see Snapshot XP operations onpage 37.

Calculating the number of Snapshot XP pairs you can createThe number of Snapshot XP pairs you can create for an array depends on the number of differentialtables, V-VOL management areas shared memory capacity, or number of pair tables. To calculate thenumber of Snapshot XP pairs you can create, first use the number of differential tables, then use the V-VOLmanagement areas shared memory capacity, and finally use the number of pair tables. Then comparethe three results. The smallest value is the maximum number of Snapshot XP pairs you can create for thearray.

Using the number of differential tablesYou can use a maximum of 13,652 differential tables for an array if additional shared memory is notinstalled. You can use a maximum of 30,718 differential tables if additional shared memory is installed.

To calculate the number of Snapshot XP pairs you can create, calculate the number of differential tablesrequired for the Snapshot XP pair and compare it with the number of differential tables for the wholearray. In addition to Snapshot XP, the following software products use differential tables in the array:

Business Copy XP

ShadowImage for z/OS

Hitachi FlashCopy Mirroring

Hitachi FlashCopy Mirroring Version 2

Flex Copy XP

Auto LUN XP

If you use any of these software products in the same array, calculate the number of differential tables

Snapshot XP pairs can use by subtracting the number of differential tables the pairs use (migration planfor Auto LUN XP) for these software products from the number of differential tables for the whole array.

For more information about calculating the number of required differential tables for Business Copy XP,ShadowImage for z/OS, Hitachi FlashCopy Mirroring, Hitachi FlashCopy Mirroring Version 2, FlexCopy XP, and Auto LUN XP, see the software products manual.

To calculate the number of differential tables for each Snapshot XP pair, use the following formula:

( (X) 256) (Z)

where:

(X) is the volumes capacity (in kilobytes)

(Z) is the number of slots a differential table can manage (1,916 32)

You must round up the calculation result to the nearest whole number.

If the volumes capacity ((X) in the previous formula) is 16 GB (16,777,216 KB), the number of differentialtables for each Snapshot XP pair is calculated as:

(16,777,216 256) (1,916 32) = 1.06889

Round up 1.06889 to 2. Therefore, two differential tables are required to create a Snapshot XP pair.

Assume that no other software products use differential tables in an array where additional sharedmemory is not installed. The number of differential tables that Snapshot XP can use is 13,652. To createSnapshot pairs that require two differential tables for each pair, the calculation is as follows:

13,652 2 = 6,826


23/74


Therefore, you can create a maximum of 6,826 Snapshot XP pairs.

Using shared memory capacity for the virtual volume management areaThe V-VOL management area consists of the following:

Pool association information

Pool management block

Other management information (shared memory is fixed at 8 MB)

To calculate the maximum number of Snapshot XP pairs you can create for an array, use the followingformula:

{ ( (X) - 8) ( () + () ) }

where:

(X) is shared memory capacity for the whole V-VOL management area (in megabytes)

() is shared memory capacity for the pool association information (in bytes)

() is shared memory capacity for the pool management block (in bytes)

You should round off the calculation result to the nearest whole number.

The following is the calculation of the shared memory capacity of the pool association information () andthe shared memory capacity of the pool management block ():

NOTE:

You can check the shared memory capacity of the pool association information and pool managementblock in the Snapshot XP pane (Figure 18).

If all the V-VOL management areas capacity is used by the pool management block and poolassociation information, the capacity ratio of the pool management block and pool associationinformation in the V-VOL management area is fixed. For more information, see Creating virtualvolume management areas on page 16.

() = ( (Y) 256) 4 1.08

() =

( (Z) 256)

32where:

(Y) is pool-VOLs capacity (in kilobytes)

(Z) is pool usage (in kilobytes)

You must round up the value enclosed by two upward arrows ( ) to the nearest whole number.

NOTE: When calculating a pools usage:

When copying snapshot data to the pool, Snapshot XP always uses a multiple of 256 KB of the poolscapacity, even when the snapshot data is smaller than 256 KB.

When snapshot data is stored consecutively, snapshot data capacity and pool usage is almost the

same. However, pool usage might be larger than snapshot data capacity when snapshot data isstored randomly.

When shared memory capacity for the whole V-VOL management area ((X) in the previous formula) is2,047 MB, pool-VOL capacity ((Y) in the previous formula) is 16 GB (16,777,216 KB), and pool usage((Z) in the previous formula) is 1 GB (1,048,576 KB), the number of Snapshot XP pairs you can create foran array is calculated as:

(2047 - 8) [ { (16,777,216 256) 4 1.08} + { (1,048,576 256) 32} ] = 5162.02933...

According to these results, you can create a maximum of 5,162 Snapshot XP pairs.


24/74

24 Requirements for Snapshot XP operations

Using the number of pair tablesHitachi FlashCopy Mirroring Version 2 and Snapshot XP pairs use pair tables to store control informationneeded to manage pairs. To create an Hitachi FlashCopy Mirroring Version 2 or Snapshot XP pair, youneed one pair table for each pair.

Usually, up to 32,768 pair tables are available in one array. However, if the relationship expansionfunction, which is an Hitachi FlashCopy Mirroring Version 2 function, is enabled, the maximum number ofavailable pair tables in one array is 1,048,575.

Among array software products, only Hitachi FlashCopy Mirroring Version 2 and Snapshot XP use pairtables. Therefore, if you use Hitachi FlashCopy Mirroring Version 2, calculate the number of availablepair tables for Snapshot XP pairs by subtracting the number of differential tables Hitachi FlashCopyMirroring Version 2 pairs use from the number of pair tables for the whole array.

For information about checking the number of pair tables Hitachi FlashCopy Version 2 uses (that is, thenumber of existing Hitachi FlashCopy Version 2 pairs), see the Hitachi ShadowImage for z/OS userguide.

For example, when the relationship expansion function is enabled and the number of pair tables HitachiFlashCopy Mirroring Version 2 uses is 30,000, calculate the number of Snapshot XP pairs you can createfor an array as follows.

32,768 - 30,000 = 2,768

According to this result, you can create a maximum of 2,768 Snapshot XP pairs.


25/74


4 Using Snapshot XPThis chapter describes procedures for using Snapshot XP.

The first section describes the flow of Snapshot XP processes. The next section describes how the status ofa Snapshot XP pair changes while using Snapshot XP. The other sections provide information needed tocreate pools and switch off the arrays power supply after you start using Snapshot XP.

Procedure for using Snapshot XP processes

Figure 3 Procedure for using Snapshot XP

To create pools and V-VOLs, use Command View XP or XP Remote Web Console. To create Snapshot XPpairs and perform subsequent operations, use RAID Manager XP. You can also use Command View XP orXP Remote Web Console to delete pairs. For more information, see Snapshot XP operations onpage 37.

NOTE:

Before creating a pool, you must create the virtual volume management area in shared memory.Virtual volume management areas are automatically created when you install additional shared

memory. For more information about installing additional shared memory, contact your HP accountsupport representative.

If you already created pools or Snapshot XP pairs for testing purposes before you actually start usingSnapshot XP for production purposes, HP recommends initializing the V-VOL management areabeforehand. For more information, see Initializing V-VOL management areas or pool managementblocks on page 48.

You do not always need to delete Snapshot XP pairs after storing snapshot data in the pool. However,since one P-VOL can be paired with up to 64 S-VOLs, you must delete the snapshot data or unnecessarypairs. When deleting a Snapshot XP pair, the pairs snapshot data is also deleted from the pool.


26/74

26 Using Snapshot XP

If a failure occurs when restoring a Snapshot XP pair, the pairs snapshot data is written back to theP-VOL. You might not be able to restore the pair if another pair is being restored.

For more information about the status of Snapshot XP pairs and operations on pairs, see Status ofSnapshot XP pairs on page 26.

Status of Snapshot XP pairsWhen creating or splitting a Snapshot XP pair, the pair status changes. Figure 4 shows the transition ofthe Snapshot XP pair status.

Figure 4 Snapshot XP pair status transition

1. If a volume is not assigned to a Snapshot XP pair, its status is SMPL.

2. Issue the paircreate command on the SMPL volume to create a Snapshot XP pair. When creatingthe first pair for the P-VOL, the pair status changes to COPY. When the operation completes, the pairstatus changes to PAIR.

If you specify a volume that is already paired with one or more S-VOLs as the P-VOL to create anotherpair, the pair status does not change to COPY. When the operation completes, the pair status changesto PAIR.

NOTE:

If you execute the paircreate command immediately after deleting the P-VOLs last snapshotdata, it might take time to create a new pair.

If the pool capacity exceeds the threshold when a Snapshot XP pair is in PAIR status, the pairstatus changes to PFUL in RAID Manager XP. For more information, see the HP StorageWorksRAID Manager XP user guide.

If you issue the paircreate command when the pool capacity exceeds the threshold, thecommand is rejected and you cannot create the pair.


27/74


3. Issue the pairsplit command on the Snapshot XP pair in PAIR status to store the snapshot data inthe pool. When the operation completes, the pair status changes to PSUS.

NOTE: If the pool capacity exceeds the threshold when a Snapshot XP pair is in PSUS status, thepair status changes to PFUS in RAID Manager XP. For more information, see the HP StorageWorksRAID Manager XP user guide.

4. To delete only snapshot data and leave the Snapshot XP pair, issue the pairresync command for

the PSUS or PFUS pair. During the operation, the pair status changes to COPY(RS).To delete the Snapshot XP pair, issue the pairsplit-S command or use Command View XP or XPRemote Web Console. During the operation, the pair status changes to SMPL(PD).

5. To restore the pair, issue the pairresync-restore command on the Snapshot XP pair in PSUSstatus. After that, the snapshot data is written back to the P-VOL. During the operation, the pair statuschanges to COPY(RS-R). When the operation completes, the pair status changes to PAIR.

6. A pool can contain only a predefined amount of data. If the total capacity of the snapshot data in thepool exceeds the pool capacity, the pair status changes to PSUE. The pair status also changes to PSUEwhen a failure occurs while restoring the pair or when the pool usage rate reaches 100 percent. Thepair status might change to PSUE when a failure occurs during a process other than restoring.

Whether the host can read and write the Snapshot XP pairs P-VOL or S-VOL depends on the pair status.

Table 6 shows the relationship between the pair status and availability of host access.

CAUTION: If the host computer uses application software to monitor the Snapshot XP pairs volumes,problems, such as abnormal end, might occur. For example, since the S-VOL whose status is not PSUS (orPFUS) rejects access from the host, a problem might occur on the monitoring application software whose

access is rejected. In addition, if the host computer connects to more than one port, a problem might alsooccur on ports that are not connected to the S-VOL that rejected the host access. You must terminate theapplication software monitoring the volumes to solve these problems.

Table 6 Whether hosts can access P-VOLs and S-VOLs

Pair status P-VOL S-VOL

Read Write Read Write

SMPL OK OK

COPY OK OK No No

PAIR/PFUL OK OK No No

PSUS/PFUS OK OK OK OK

SMPL(PD) OK OK No No

COPY(RS) OK OK No No

COPY(RS-R) OK OK No No

PSUE OK1

1. If the pair status changes to PSUE because a failure occurred during the restoration, the host cannot access that pair.

OK1 No No


28/74


Use RAID Manager XP commands to operate Snapshot XP pairs. However, whether the operationscomplete normally or not depends on the pair status. Table 7 shows the pair status and results of the RAIDManager commands.

When the command executes the process and ends normally, the pair status changes according to theprocess. For more information about how the pair status changes when the command ends normally, seeFigure 4 and the corresponding text.

Notes on creating poolsWhen creating pools, you must be careful about the pool capacity and types of volumes specified aspool-VOLs. This section describes notes on pool capacity definitions and using external LUs as pool-VOLs.

Defining pool capacityPool capacity is the total capacity of pool volumes defined in the pool. If pool capacity is insufficient, thestatus of Snapshot XP pairs could change to PSUE. When creating a pool, you must estimate the copycapacity (for example, the capacity of snapshot data to be copied to the pool) and set enough poolcapacity for the estimated copy capacity. If copy capacity changes according to the time period, setenough pool capacity for the largest copy capacity.

NOTE:

When snapshot data is copied to a pool, a multiple of 256 KB of the pool is used. Even if the snapshotdata capacity is less than 256 KB, you need 256 KB in the pool for the data.

If the same P-VOL area is updated more than once, snapshot data for the area is copied to the poolonly when the first update occurs. Therefore, when the same P-VOL area is updated only once, writtendata capacity is equal to copied data capacity. However, when the same P-VOL area is updatedrepeatedly, copy capacity is smaller than written data capacity.

HP recommends using a volume with a capacity that is a multiple of 256 KB as a pool-VOL. If thecapacity of the volume specified as a pool-VOL is not a multiple of 256 KB, the capacity that is lessthan 256 KB is rounded off. For example, if you add a volume with 100.125 MB as a pool-VOL,125 KB is rounded off and the pools capacity increases by only 100 MB.

When estimating copy capacity, consider whether there is only one snapshot data or more than onesnapshot data.

Table 7 Pair status and results of RAID Manager XP commands

Pair status RAID Manager XP command1

1. OK: Command executes the process and ends normally.NOP: Command does not execute the process, but ends normally.No: Command ends abnormally (that is, command is rejected).

paircreate paircreate-split

pairsplit pairresync pairresync-restore

pairsplit -S pairsplit -E

SMPL OK No No No No NOP No

COPY NOP No No NOP NOP No No

PAIR/PFUL NOP OK OK NOP NOP OK No

PSUS/PFUS No NOP NOP OK OK OK No

SMPL(PD) No No No No No NOP No

COPY(RS) NOP No No NOP NOP No No

COPY(RS-R) NOP No No NOP NOP No No

PSUE NO No No OK2

2. If you issue the pairresync command for a pair whose status has changed to PSUE because of a shortage of sharedmemory for the V-VOL management area, the command is rejected and ends abnormally.

No OK NOP


29/74


For one snapshot data

If the same P-VOL area is updated only once, copy capacity is equal to the capacity of data writtenbetween storing and deleting snapshot data.

For example, to make a backup using Snapshot XP, you can back up S-VOL data after storing thesnapshot data, and then delete the snapshot data. In this case, only data written during the backupmust be copied to the pool, and there is only one snapshot data. Therefore, you can make a backupwith a pool with small capacity. However, since you must read a large amount of S-VOL data duringthe backup, access to the P-VOL increases and, consequently, host I/O performance might bereduced.

For multiple snapshot data

After storing each snapshot data, if the same P-VOL area is updated only once until the snapshot datais deleted, copy capacity is equal to the capacity of data written between storing and deleting thesnapshot data. If there is more than one P-VOL, copy capacity is equal to the total capacity of datawritten to each P-VOL.

NOTE: When storing more than one snapshot data in the pool, some Snapshot XP pairs might sharesnapshot data in the pool. While snapshot data is shared, you can delete pairs, but cannot delete sharedsnapshot data from the pool. Shared snapshot data is not deleted from the pool until all Snapshot XP pairssharing the snapshot data are deleted.

Although you estimate copied data capacity and set pool capacity according to the information in thissection, if pool capacity exceeds the threshold, implement the measures described in TroubleshootingSnapshot XP on page 65.

Using external LUs as pool-VOLsBy using External Storage XP, you can connect multiple arrays to the XP12000/XP10000/SVS200 array.In that case, the original XP12000/XP10000/SVS200 array is called the local array, and the connectedstorage arrays are called external arrays. A volume in an external array is called an external LU. Avolume in the local array is called an internal storage virtualizer LDEV(referred to as an internal LDEV).

If External Storage XP is installed, you can use internal LDEVs and external LUs as pool-VOLs. However,external LUs are more likely to fail than internal LDEVs. In addition, solutions for external LU failures are

more complicated than those for internal LDEV failures. To minimize the effects of failures,HP recommends using external LUs as follows:

Specify external LUs of only one external array for one pool

Do not specify both internal LDEVs and external LUs as pool-VOLs in one pool

You can specify the external LUs of several external arrays for one pool, or use both internal LDEVs andexternal LUs as pool-VOLs in one pool, but in that case, remember that problems such as volume blockadecan occur more easily. For example, if a problem occurs and the external LUs being used as a pool-VOLare blocked, the pool becomes blocked as well. For more information, see Recovering blocked pools onpage 68.

For more information about external arrays and solutions for errors related to external LUs, see the

HP StorageWorks External Storage XP user guide.Notes on using Snapshot XP

This section describes switching off the power supply and replacing the microprogram offline whileSnapshot XP is in use.

Switching off the power supplyBefore switching off the power supply while Snapshot XP is running, stop host I/O operations. Whenswitching on the power supply, Snapshot XP behaves differently depending on whether information inshared memory remains before and after switching off the power supply.

If information in shared memory remains before and after switching off the power supply


30/74


You can usually use the pools and Snapshot XP pairs you used before switching off the power.However, since the array checks the status of pools and pool volumes, if pool volumes are blocked atthat time, the pool is blocked and the status of Snapshot XP pairs changes to PSUE. When this occurs,you must recover the pools after switching on the power. For more information, see Recoveringblocked pools on page 68.

If information in shared memory is lost after switching off the power supply

The array has a battery to maintain information in shared memory. However, when a certain timeperiod elapses after the breaker is turned off, the battery dies and information in shared memory islost. If information in shared memory is lost after switching off the power supply, information aboutpools and Snapshot XP pairs is erased. Therefore, you must create pools and pairs again afterswitching on the power.

For more information about the amount of time before information in shared memory is lost when thebreaker is turned off, contact your HP account support representative.

Replacing the microprogram offlineReplacing the microprogram is usually performed online, but in some cases, such as when the sharedmemory configuration must be changed, replacing the microprogram is performed offline. If you replacethe microprogram offline, pool information or Snapshot XP pair information in shared memory is lost.Therefore, you must create pools and pairs again after replacing the microprogram.

Combining Snapshot XP with other software productsYou can create Snapshot XP pairs by sharing volumes with other products, such as Business Copy XP orContinuous Access XP. In addition, you can create Snapshot XP pairs using volumes to which LUNSecurity XP Extension or RAID Manager XP have assigned attributes. Table 8 shows whether or notSnapshot XP pairs can share volumes with other software products.

Table 8 Volume sharing with other software products

Volumes of other software products Snapshot XP pair P-VOL Snapshot XP pair S-VOL

Business Copy XP pair P-VOL OK1

1. A Business Copy XP and Snapshot XP pair cannot have the same mirror unit (MU) number. For example, if the Business CopyXP pairs MU number is 0, you cannot create a Snapshot XP pair whose MU number is 0 and whose P-VOL is also used as aBusiness Copy XP P-VOL. Also, if the Snapshot XP pairs MU number is 1, you cannot create a Business Copy XP pair whose MUnumber is 1 and whose P-VOL is also used as a Snapshot XP P-VOL.

No

Business Copy XP pair S-VOL OK1 No

Continuous Access XP pair P-VOL OK NoContinuous Access XP pair S-VOL OK No

Continuous Access XP Journal pair P-VOL OK No

Continuous Access XP Journal pair S-VOL OK No

Auto LUN XP source volume OK NO

Auto LUN XP target volume No No

Read Only volume OK OK

Protect volume OK OK

S-VOL Disable volume OK OK

Volume with VMA No No

Volume with extents No No

Zero Read Capacity volume OK OK

Invisible volume OK OK


31/74


NOTE:

You need LUN Security XP Extension to set the Read Only attribute, Protect attribute, S-VOL Disable, orVMA. For more information, see the HP StorageWorks LUN Security XP Extension user guide.

You need RAID Manager XP to set extents, Zero Read Capacity, or Invisible attribute. For moreinformation, see the HP StorageWorks RAID Manager XP user guide.

You can check if the volume has the Read Only attribute, Protect attribute, S-VOL Disable, VMA,extents, Zero Read Capacity attribute, or Invisible attribute by accessing the LUN Security XP Extension

pane. For more information, see the HP StorageWorks LUN Security XP Extension user guide.

When Snapshot XP shares volumes with the software products shown in Table 8, some operations arerestricted according to the pair statuses.

Combining Snapshot XP with Business Copy XPWhen the Snapshot XP P-VOL and Business Copy XP pairs volume are shared, the relationship betweenthe Business Copy XP pair status and Snapshot XP operations is shown in Table 9 and Table 10.

Table 9 Snapshot XP operations when Snapshot XP P-VOL and Business Copy XP P-VOL are shared

Snapshot XP

operations

Business Copy XP pair status1

1. OK: Operation allowed.No: Operation not allowed (command rejected).

COPY PAIR COPY(SP) PSUS(SP) PSUS COPY(RS) COPY(RS-R) PSUE

Creating pairs(paircreate)

OK OK OK OK OK OK No OK

Storing snapshot data(pairsplit)

OK OK OK OK OK OK No OK

Restoring pairs(pairresync -restore)

No No No No OK No No OK

Deleting snapshotdata (pairresync)

OK OK OK OK OK OK OK OK

Deleting pairs(pairsplit -S)


Table 10 Snapshot XP operations when Snapshot XP P-VOL and Business Copy XP S-VOL are shared

Snapshot XPoperations

Business Copy XP pair status1


COPY PAIR COPY(SP) PSUS(SP) PSUS COPY(RS) COPY(RS-R) PSUE

Creating pairs(paircreate)

No No No No OK No No No

Storing snapshotdata (pairsplit)


Restoring pairs(pairresync -restore)


Deleting snapshotdata (pairresync)


Deleting pairs(pairsplit -S)



32/74


The relationship between the Snapshot XP pair status and Business Copy XP operations is shown inTable 11 and Table 12.

NOTE: Since a Snapshot XP S-VOL uses data in the P-VOL, Business Copy XPs quick backwardpairresync operation (Quick Restore) is not allowed.

Table 11 Business Copy XP operations when Snapshot XP P-VOL and Business Copy XP P-VOL areshared

Business Copy XP operations Snapshot XP pair status1


COPY PAIR PSUS SMPL(PD) COPY(RS) COPY(RS-R) PSUE

Creating pairs (paircreate) OK OK OK OK OK No OK

Creating and splitting pairs(paircreate -split)

OK OK OK OK OK No OK

Splitting pairs (pairsplit) OK OK OK OK OK No OK

Forward pair resynchronization(pairresync)


Normal backward pairresynchronization (pairresync-restore)


Quick backward pairresynchronization (pairresync

-restore)

No No No No No No No

Suspending pairs (pairsplit -E) OK OK OK OK OK OK OK

Deleting pairs (pairsplit -S) OK OK OK OK OK OK OK

Table 12 Business Copy XP operations when Snapshot XP P-VOL and Business Copy XP S-VOL areshared

Business Copy XP operations Snapshot XP pair status1



Creating pairs (paircreate) No No No No No No No

Creating and splitting pairs(paircreate -split)


Splitting pairs (pairsplit) OK OK OK OK OK No OK

Forward pair resynchronization(pairresync)


Normal backward pairresynchronization (pairresync-restore)


Quick backward pairresynchronization (pairresync-restore)


Suspending pairs (pairsplit -E) OK OK OK OK OK No OK



33/74


For more information about Business Copy XP pair status and operations, see the HP StorageWorksBusiness Copy XP user guide for the XP12000/XP10000/SVS200.

Combining Snapshot XP with Continuous Access XP or Continuous Access XPJournal

When the Snapshot XP P-VOL and the Continuous Access XP or Continuous Access XP Journal pair volumeare shared, the relationship between the Continuous Access XP or Continuous Access XP Journal pairstatus and Snapshot XP operations is shown in Table 13 and Table 14.

The relationship between the Snapshot XP pair status and Continuous Access XP or Continuous Access XPJournal operations is shown in Table 15 and Table 16.

Table 13 Snapshot XP operations when Snapshot XP P-VOL and Continuous Access XP/ContinuousAccess XP Journal are shared

Snapshot XP operations Continuous Access XP/Continuous Access XP Journal pair status1


COPY PAIR PSUS PSUE Suspending Deleting

Creating pairs (paircreate) OK OK OK OK OK OK

Storing snapshot data (pairsplit) OK OK OK OK OK OK

Restoring pairs (pairresync -restore) No No OK OK No No

Deleting snapshot data (pairresync) OK OK OK OK OK OK

Deleting pairs (pairsplit -S) OK OK OK OK OK OK

Table 14 Snapshot XP operations when Snapshot XP P-VOL and Continuous Access XP/ContinuousAccess XP Journal S-VOL are shared

Snapshot XP operations Continuous Access XP/Continuous Access XP Journal pair status1


COPY PAIR PSUS PSUE SSWS2

2. SSWS is a status of Continuous Access XP Journal pairs. Continuous Access XP pairs do not change to SSWS status.

Suspending Deleting

Creating pairs (paircreate) OK OK OK OK OK OK OK

Storing snapshot data

(pairsplit)

No OK OK OK OK OK OK

Restoring pairs (pairresync-restore)3

3. When restoring the Snapshot XP pair whose P-VOL is used as a Continuous Access XP or Continuous Access XP Journal S-VOL,you must switch operations from the local site to the remote site by executing the horctakeover command.


Deleting snapshot data(pairresync)

OK OK OK OK OK OK OK


Table 15 Continuous Access XP/Continuous Access XP Journal operations when Snapshot XP P-VOL andContinuous Access XP/Continuous Access XP Journal P-VOL are shared

Continuous Access XP/Continuous Access XP

Journal operations

Snapshot XP pair status1


Creating pairs (paircreate) OK OK OK OK OK No OK

Splitting pairs (pairsplit) OK OK OK OK OK OK


34/74


For more information about Continuous Access XP pair status and operations, see the HP StorageWorksContinuous Access XP user guide for the XP12000/XP10000/SVS200. For more information aboutContinuous Access XP Journal pair status and operations, see the HP StorageWorks Continuous Access XPJournal user guide.

Combining Snapshot XP with Auto LUN XPRegardless of the status of Auto LUN XPs migration plans (Auto LUN XP pairs), you cannot perform anySnapshot operations on the volume the migration plan uses. To use a Snapshot XP P-VOL as the migrationplans source volume, you must create the Snapshot XP pair first, and then create the migration plan.

When the Snapshot XP P-VOL and migration plans source volume are shared, you can execute themigration plan only when the Snapshot XP pair is in PAIR status. Deleting and canceling the migration

plan are always allowed. These operations are not affected by the Snapshot XP pair status.For more information about the status of migration plans and Auto LUN XP operations, see theHP StorageWorks Auto LUN XP user guide for the XP12000/XP10000.

Combining Snapshot XP with LUN Security XP ExtensionLUN Security XP Extension can set four kinds of access attributes on the volumes: Read/Write, Read Only,Protect, and S-VOL Disable. Snapshot XP cannot create a pair by specifying a volume whose accessattribute is S-VOL Disable as the S-VOL. In addition, if the S-VOL Disable attribute is set on the SnapshotXP pairs P-VOL, you cannot restore the pair.

By using LUN Security XP Extension, you can set the Read/Write, Read Only, Protect, or S-VOL Disableattribute on volumes that Snapshot XP pairs already use. However, when the pair is in the following

statuses, you cannot set the S-VOL Disable attribute on the pair volumes:

Resynchronizing pairs(pairresync)


Deleting pairs (pairsplit -S) OK OK OK OK OK OK OKSwitching to remote site(horctakeover)


1. OK: Operation allowed.No: Operation not allowed (command rejected).: Not applicable.

Table 16 Continuous Access XP/Continuous Access XP Journal operations when Snapshot XP P-VOL andContinuous Access XP/Continuous Access XP Journal S-VOL are shared


Journal operations




Creating pairs (paircreate) No No No OK No No No

Splitting pairs (pairsplit) OK OK OK OK OK OK OK

Resynchronizing pairs(pairresync)



Switching to remote site(horctakeover)


Table 15 Continuous Access XP/Continuous Access XP Journal operations when Snapshot XP P-VOL andContinuous Access XP/Continuous Access XP Journal P-VOL are shared (continued)


Journal operations




35/74


COPY

SMPL(PD)

COPY(RS)

COPY(RS-R)

PSUE

NOTE: You can set S-VOL Disable on the P-VOL even if the pair status is COPY, SMPL(PD), COPY(RS), orPSUE.

For more information about setting the access attribute, see the HP StorageWorks LUN Security XPExtension user guide.


36/74



37/74


5 Snapshot XP operationsThis chapter describes Snapshot XP operations and panes.

Displaying the Business Copy XP main pane1. Launch Command View XP or XP Remote Web Console.

2. Click the Business Copy ( ) button. The Business Copy XP main pane appears.

Figure 5 Business Copy XP main pane

NOTE: Although the Business Copy XP main pane displays information about Business Copy XP andSnapshot XP pairs, this section only explains items related to Snapshot XP pairs. For more informationabout items related to Business Copy XP pairs, see the HP StorageWorks Business Copy XP user guide forthe XP12000/XP10000/SVS200.

Display Filterbutton: Displays the Display Filter pane (Figure 8) where you can filter the volumesdisplayed in the volume list.

Tree (left area of pane): Displays ports that are defined paths, host groups, iSCSI targets, or LUNs in atree format. When you select items in the tree, information about Business Copy XP or Snapshot XPpairs appears in the volume list on the right of the pane.

To display information about all pairs in the array, select Subsystem at the top of the tree.

The following icons appear in the tree.Icon Description

Array

Port

Host group or iSCSI target

LUN


38/74

38 Snapshot XP operations

Volume list (upper-right area of pane): Displays Business Copy XP or Snapshot XP pairs on the port,host group, iSCSI target, or LUN selected in the tree. You can sort volumes by any column heading inthe volume list.

Preset list: Displays operations that have been performed in the Business Copy XP main pane, buthave not been applied to the array. To apply operations displayed in the Preset list to the array, click

Apply.

For more information, see Preset List on page 40.

Apply button: Applies operations displayed in the Preset list to the array. If specified operations are

applied successfully, the Preset list is cleared. If an error occurs during an operation, the failedoperation remains in the Preset list preceded with an error icon ( ). Error codes and messagesappear on the error pane.

Cancel button: Cancels all operations set in the Preset list.

Volume listThe volume list is the upper-right area of the Business Copy XP main pane. The volume list displaysvolumes that Business Copy XP or Snapshot XP can use and pair information about these softwareproducts.

Figure 6 Volume list

When you select a port, host group, iSCSI target, or LUN in the tree on the left side of the Business CopyXP main pane, information about volumes belonging to the selected item appears in the volume list. Youcan specify conditions such as pair status or reserved attribute on the Display Filter pane to select volumesthat can be displayed in the volume list. For more information about the Display Filter pane, seeSpecifying conditions for volumes displayed in the volume list on page 41.

Previous button: hen the total number of volumes in the array is more than 1,024, displays theprevious page of the volume list. If the number of items in the volume list is less than 1,024, this buttonis grayed out.

Next button: When the total number of volumes in the array is more than 1,024, displays the nextpage of the volume list. If the number of items in the volume list is less than 1,024, this button is grayedout.


39/74


Port: P-VOLs port ID (cluster and channel number).

G-ID: Group number of the P-VOLs host group or iSCSI target.

LUN: P-VOLs CU:LDEV (control unit image:logical device ID).

NOTE: An LDEV number ending with # (for example, 00:01#) indicates the LDEV is an externalLU. For more information about external LUs, see the HP StorageWorks External Storage XP userguide.

MU: Snapshot XP pairs snapshot ID. If the pair is in SMPL status, three hyphens (---) appear. For moreinformation about what is displayed for Business Copy XP pairs, see the HP StorageWorks BusinessCopy XP user guide for the XP12000/XP10000/SVS200.

Status: Snapshot XP or Business copy XP pair status. For more information about Snapshot XP pairstatus, see Status of Snapshot XP pairs on page 26. For more information about Business Copy XPpair status, see the HP StorageWorks Business Copy XP user guide for theXP12000/XP10000/SVS200.

Port: S-VOLs port ID (cluster and channel number). If there is no S-VOL

hp_snapshotug rootsan technologies pvt ltd

Documents