HP XP20000, XP24000 User Manual 3
HP StorageWorks
XP24000/XP20000 Snapshot User Guide
Abstract
This guide explains how to use HP StorageWorks XP Snapshot Software to create space-efficient point-in-time copies of data
volumes on an HP StorageWorks XP24000/XP20000 storage system. Topics include creating, monitoring, and troubleshooting
snapshot pools, virtual volumes, and copy pairs. The intended audience is a storage system administrator or authorized service
provider with independent knowledge of HP StorageWorks XP storage systems and Remote Web Console.
HP Part Number: T5213-96033
Published: May 2011
Edition: Twelfth
© Copyright 2007, 2011 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Windows is a U.S. registered trademark of Microsoft Corporation.
ShadowImage and TrueCopy are registered trademarks of Hitachi, Ltd. and Hitachi Data Systems Corporation.
UNIX is a registered trademark of The Open Group.
Export Requirements
You may not export or re-export this document or any copy or adaptation in violation of export laws or regulations.
Without limiting the foregoing, this document may not be exported, re-exported, transferred or downloaded to or within (or to a national resident
of) countries under U.S. economic embargo, including Cuba, Iran, North Korea, Sudan, and Syria. This list is subject to change.
This document may not be exported, re-exported, transferred, or downloaded to persons or entities listed on the U.S. Department of Commerce
Denied Persons List, Entity List of proliferation concern or on any U.S. Treasury Department Designated Nationals exclusion list, or to parties directly
or indirectly involved in the development or production of nuclear, chemical, biological weapons, or in missile technology programs as specified
in the U.S. Export Administration Regulations (15 CFR 744).
Revision History
DescriptionDateEdition
This edition applies to microcode version 60-01-31-00/00 or later.June 2007First
This edition applies to microcode version 60-01-68-00/00 or later.September 2007Second
This edition applies to microcode version 60-02-04-00/00 or later.November 2007Third
This edition applies to microcode version 60-02-25-00/00 or later.January 2008Fourth
This edition applies to microcode version 60-02-48-00/00 or later.April 2008Fifth
This edition applies to microcode version 60-03-04-00/00 or later.June 2008Sixth
This edition applies to microcode version 60-03-24-00/00 or later.September 2008Seventh
This edition applies to microcode version 60-04-04-00/00 or later.December 2008Eighth
This edition applies to microcode version 60-04-13-00/00 or later.February 2009Ninth
This edition applies to microcode version 60-05-00-00/00 or later.June 2009Tenth
This edition applies to microcode version 60-07-00-00/00 or later.June 2010Eleventh
This edition applies to microcode version 60-08-01-00/00 or later.May 2011Twelfth
Contents
1 Overview of HP StorageWorks XP Snapshot Software......................................6
XP Snapshot............................................................................................................................6
Features..................................................................................................................................6
Benefits...................................................................................................................................6
Differentiation from HP StorageWorks XP Business Copy Software...................................................7
2 About XP Snapshot Operations....................................................................8
XP Snapshot Components..........................................................................................................8
Volumes and Volume Pairs....................................................................................................8
Volume Pairs and Consistency Group.....................................................................................8
XP Snapshot Software...........................................................................................................8
License...............................................................................................................................8
RAID Manager....................................................................................................................9
XP Snapshot Operations............................................................................................................9
Create V-VOL Management Area Operation..........................................................................10
Creation of a Pool..............................................................................................................10
Creation of a Virtual Volume...............................................................................................11
Creation of an XP Snapshot Pair..........................................................................................12
Storing XP Snapshot Data...................................................................................................12
Restoration of an XP Snapshot Pair.......................................................................................13
Deletion of XP Snapshot Data or an XP Snapshot Pair.............................................................13
Status of the XP Snapshot Pairs.................................................................................................14
Copy Threshold Option...........................................................................................................25
Interoperability with Other Products and Functions......................................................................26
Data Retention Utility..........................................................................................................27
Auto LUN..........................................................................................................................27
XP Business Copy...............................................................................................................27
XP Continuous Access or XP Continuous Access Journal..........................................................30
HP StorageWorks XP Thin Provisioning Software....................................................................32
3 Preparing for XP Snapshot Operations........................................................33
System Requirements...............................................................................................................33
Volume Requirements..........................................................................................................33
XP Snapshot Software Requirements.....................................................................................35
License Requirements..........................................................................................................35
Shared Memory Requirements.............................................................................................35
Requirements for RAID Manager..........................................................................................35
Operational Requirements........................................................................................................35
Calculating the Maximum Number of Pairs............................................................................36
Calculating the Number of XP Snapshot Pairs by Using the Number of Differential Tables.......36
Calculating the Number of XP Snapshot Pairs by Using the Shared Memory Capacity for the
Virtual Volume Management Area...................................................................................37
Calculating the Number of XP Snapshot Pairs Using the Number of Pair Tables.....................39
Performance Considerations................................................................................................40
Notes on Defining Pool Capacity.........................................................................................40
Notes on Using External Volumes as Pool-VOLs......................................................................41
Requirements for Maintaining XP Snapshot................................................................................41
Notes on Replacing the Microcode Offline............................................................................41
Notes on Switching Off the Power Supply.............................................................................41
Contents 3
Installing and Uninstalling XP Snapshot.....................................................................................42
Installing XP Snapshot........................................................................................................42
Uninstalling XP Snapshot....................................................................................................42
Starting XP Snapshot...............................................................................................................42
4 Using the XP Snapshot GUI........................................................................44
Pair Operation Window..........................................................................................................44
Volume List........................................................................................................................46
Preview List.......................................................................................................................49
History Window.....................................................................................................................51
XP Snapshot Window.............................................................................................................53
Pool Window.........................................................................................................................56
V-VOL Window......................................................................................................................63
5 Performing XP Snapshot Operations............................................................66
XP Snapshot Processes............................................................................................................66
Configuring the Volume List......................................................................................................67
Deleting the Settings in Preview List...........................................................................................69
Creating or Deleting Pools.......................................................................................................69
Creating New Pools...........................................................................................................69
Changing the Information for the Pools.................................................................................71
Deleting Pools...................................................................................................................72
Deleting a Pool.............................................................................................................72
Deleting Multiple Pools..................................................................................................73
Optimizing the V-VOL Management Area or Pool Management Block.......................................73
Optimizing the V-VOL Management Area.........................................................................73
Optimizing the Pool Management Block...........................................................................74
Creating or Deleting Virtual Volumes.........................................................................................74
Creating New Virtual Volumes.............................................................................................74
Deleting Virtual Volumes and a Virtual Volume Group.............................................................83
Deleting Multiple Virtual Volume Groups ..............................................................................83
Creating XP Snapshot Pairs......................................................................................................85
Storing XP Snapshot Data........................................................................................................85
Storing XP Snapshot Data by Consistency Group with At-Time Snapshot Function............................86
Restoring XP Snapshot Pairs.....................................................................................................88
Deleting XP Snapshot Data......................................................................................................88
Deleting XP Snapshot Pairs......................................................................................................89
Deleting XP Snapshot Pairs by Selecting the Pairs per Port.......................................................89
Deleting XP Snapshot Pairs by Selecting the Pairs per Pool.......................................................91
Viewing Detailed Volume and Pair Information...........................................................................91
Viewing S-VOL Path Information................................................................................................93
Viewing the Number of Pairs and License Information..................................................................94
Displaying the Operation History..............................................................................................96
6 Troubleshooting........................................................................................98
Procedure to Recover a Blocked Pool.......................................................................................101
Procedure to Complete the Pool-Related SIMs...........................................................................102
Troubleshooting When Using XP RAID Manager.......................................................................103
7 Support and other resources....................................................................116
Contacting HP......................................................................................................................116
HP technical support........................................................................................................116
4 Contents
Subscription service..........................................................................................................116
Documentation Feedback..................................................................................................116
Related information...............................................................................................................116
Websites........................................................................................................................117
Conventions for storage capacity values..................................................................................117
Typographic conventions.......................................................................................................117
Glossary..................................................................................................119
Index.......................................................................................................121
Contents 5
1 Overview of HP StorageWorks XP Snapshot Software
This chapter provides an overview of XP Snapshot and describes the features and benefits of XP
Snapshot.
• “XP Snapshot” (page 6)
• “Features” (page 6)
• “Benefits” (page 6)
• “Differentiation from HP StorageWorks XP Business Copy Software” (page 7)
Unless otherwise specified, the term storage system in this guide refers to the following disk arrays:
• HP StorageWorks XP24000 Disk Array
• HP StorageWorks XP20000 Disk Array
The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer
browser. Actual windows may differ depending on the operating system and browser used. GUI
contents also vary with licensed program products, storage system models, and firmware versions.
XP Snapshot
The XP Snapshot feature of the HP storage system rapidly creates logical point-in-time snapshot
copies of data volumes within the storage system, or behind the storage system as external storage,
without impacting host service or performance levels. XP Snapshot accelerates backup and recovery
processes by reducing the amount of disk storage required for the snapshot copies. Because only
the changed data blocks are stored in the XP Snapshot storage pool, the snapshot copy is
substantially smaller than the source, saving a significant amount of storage capacity over full
cloning methods. XP Snapshot’s capability for quick restoration of data reduces traditional,
tape-based application restore time from hours to seconds.
Features
The key features of XP Snapshot are:
• Point-in-time copies of only changed blocks in the XP Snapshot data pool, not full volume.
• Instantaneous restore of just the data you need.
• Versioning of backups for easy restore.
• RAID protection of all XP Snapshot copies.
• Near-instant copy creation and deletion.
• Easy integration with industry-leading backup software applications.
Benefits
XP Snapshot provides the following business benefits:
• Reduces recovery time from data corruption or human error considerably via an immediate
• Allows frequent data backup operations to be performed nondisruptively, while critical
• Accelerates application testing and deployment by providing always-available copies of
restore from a disk-resident, point-in-time data snapshot copy.
applications run unaffected.
current production information.
• Enables immediate access to time-critical information.
• Eliminates the backup window.
6 Overview of HP StorageWorks XP Snapshot Software
• Improves operational efficiency by allowing multiple processes to run in parallel with access
to the same information.
• Allows disk space to be used efficiently through volume snapshots rather than full-copy clones,
which helps maximize disk space.
Differentiation from HP StorageWorks XP Business Copy Software
XP Business Copy differs from XP Snapshot in that it creates physically separate copies of the data;
no portion is shared between primary and secondary volumes. Table 1 (page 7) highlights the
key differences between the XP Snapshot and XP Business Copy products.
Table 1 XP Snapshot and XP Business Copy Differentiators
XP Business Copy CloneXP Snapshot Virtual Volume
Features
Disk Space Used
Data Recovery Time After P-VOL is
corrupted
Size of Physical Volume
Provides a very quick copy because
it is a virtual volume
InstantaneousTime to Create
amount of data changed
1. V-VOL verify, data not available to
host
2. Copy back from a tape storage or
other, data available
P-VOL Pool for one V-VOL
Superior protection because it is a
complete copy
Immediate restore if P-VOL becomes
corrupted
From minutes to hours, depending on
the size of the P-VOL
Same amount as P-VOLSize will vary depending upon the
InstantaneousTwo-stage restore:
P-VOL = S-VOL
P-VOL : S-VOL = 1 : 3P-VOL : V-VOL = 1 : 64Pair Configuration
P-VOL can be restored from S-VOLP-VOL can be restored from any V-VOLRestore
Figure 1 Product Differentiators for XP Snapshot and XP Business Copy Software
Differentiation from HP StorageWorks XP Business Copy Software 7
2 About XP Snapshot Operations
This chapter describes the volumes used by XP Snapshot and the functions of XP Snapshot.
• “XP Snapshot Components” (page 8)
• “XP Snapshot Operations” (page 9)
• “Status of the XP Snapshot Pairs” (page 14)
• “Copy Threshold Option” (page 25)
• “Interoperability with Other Products and Functions” (page 26)
XP Snapshot Components
A system using XP Snapshot usually contains the following components.
• Pair of volumes (P-VOL and S-VOL)
• Consistency group
• XP Snapshot program product
• Licensed XP Business Copy program product
• XP RAID Manager
Volumes and Volume Pairs
XP Snapshot copies the original data in a P-VOL to a V-VOL. A V-VOL is specified as an S-VOL
and manages a P-VOL. A P-VOL is the logical volume and an S-VOL, which is the V-VOL, is the
volume for an XP Snapshot pair.
• A virtual volume of XP Thin Provisioning Software can be specified as a logical volume, but
a virtual volume of XP Snapshot should not be specified.
• The differential data between the P-VOL and the S-VOL will be stored in a pool volume as
snapshot data. Therefore, you need at least one logical volume as a copy source (P-VOL), one
V-VOL as a copy target (S-VOL), and one pool-VOL where you can store snapshot data.
Volume Pairs and Consistency Group
You can define plural XP Snapshot pairs as one consistency group by using RAID Manager. When
you store snapshot data by consistency group, data is copied as of the same point in time for all
P-VOLs in the group.
XP Snapshot Software
You can operate XP Snapshot by using the XP Remote Web Console computer. The Remote Web
Console computer is connected to the storage systems via the TCP/IP local-area network (LAN).
The Remote Web Console computer communicates and exchanges data directly with the service
processor (SVP) of the connected systems. You can then acquire the information about the
configuration or status of the system, or issue commands to the system.
License
You need to install the XP Business Copy license in the Remote Web Console computer before you
operate XP Snapshot. In addition, to create XP Snapshot pairs, you must purchase the XP Business
Copy license and ensure that there is enough licensed capacity for the pairs you are going to
create.
8 About XP Snapshot Operations
XP Business Copy license capacity includes:
• XP Snapshot P-VOLs
• XP Snapshot pool-VOLs
• XP Business Copy P-VOLs
• XP Business Copy S-VOLs
• XP Business Copy reserved volumes
These volumes are called used volumes. When determining how much license capacity to purchase,
ensure that there will be enough licensed capacity for these used volumes. You must limit the total
capacity of the used volumes so that it will be equal to or less than the licensed capacity.
RAID Manager
Part of XP Snapshot operations require RAID Manager. When you use RAID Manager, you do not
need to use the Remote Web Console computer. Instead, you operate XP Snapshot directly from
the host by executing the commands.
XP Snapshot Operations
XP Snapshot enables you to maintain and copy data on the HP storage system. XP Snapshot is
used for data for open systems such as UNIX and PC servers. “How Data is Copied Using XP
Snapshot” (page 9) illustrates how data is copied in the XP24000/20000 Disk Array storage
system using XP Snapshot.
Figure 2 How Data is Copied Using XP Snapshot
XP Snapshot Operations 9
In Figure 2 (page 9), Data A is stored in some part of the P-VOL of an XP Snapshot pair. When
the host requests an update of Data A to Data B, XP Snapshot will copy Data A to the pool volume
in the pool before the P-VOL is updated. After the copy operation of Data A has completed, Data
B will be written to the part where Data A was stored in P-VOL, and the P-VOL will be updated.
From the V-VOL, you can access Data B in the P-VOL and Data A in the pool-VOL.
Create V-VOL Management Area Operation
A V-VOL management area needs to be created in the shared memory before you use XP Snapshot.
The V-VOL management area is an important area for associating an S-VOL (a V-VOL) of XP
Snapshot with a pool-VOL. The V-VOL management area is created automatically when the
additional shared memory is installed. Call HP technical support for the installation of additional
shared memory.
There are two kinds of areas in the V-VOL management area: pool management block and pool
association information. When you create pools or XP Snapshot pairs, the pool management block
or pool association information will be stored in the V-VOL management area; therefore, the
available capacity of the V-VOL management area decreases. When all capacity of the V-VOL
management area is used, the capacity ratio of the pool management block and the pool association
information in the V-VOL management area will be fixed. If the capacity of the pool management
block is insufficient, problems may occur; for example, you cannot create new pools or create
pools with a large amount of capacity. To solve such problems, you need to optimize the V-VOL
management area.
Creation of a Pool
An XP Snapshot pool is an area to store snapshot data. A pool consists of multiple pool-VOLs, and
snapshot data is stored in a pool-VOL. 1024 pool-VOLs can be registered in a pool, and 128
pools can be created in a storage system. Figure 3 (page 10) illustrates the relationship between
an XP Snapshot pair and a pool.
Figure 3 The Relationship Between an XP Snapshot Pair and a Pool
10 About XP Snapshot Operations
You need to create a pool when you use XP Snapshot. Pool-VOLs registered in a pool can be
added but cannot be deleted. In addition, all snapshot data in the pool must be deleted to delete
the pool itself.
WARNING! The capacity of a pool is equal to the total capacity of the pool-VOLs registered in
the pool. The status of the XP Snapshot pair will be PSUE (status when failure occurred) when the
usage rate of the pool exceeds the capacity of the pool as a result of writing data in the volume
of that pair. XP Snapshot data cannot be stored in the pool, and no new XP Snapshot pair can be
created. Read “ Notes on Defining Pool Capacity” (page 40), and ensure that there is sufficient
pool capacity.
To create a pool, use the Pool window of the Remote Web Console.
Creation of a Virtual Volume
A V-VOL is a virtual volume which does not have physical memory space. A V-VOL needs to be
created before you create an XP Snapshot pair, because you must use a V-VOL as the S-VOL of
an XP Snapshot pair.
The definition of a V-VOL cannot be released if the V-VOL is being used as the S-VOL of an XP
Snapshot pair. To release the definition, you must delete the XP Snapshot pair that uses the V-VOL.
CAUTION: If you are using HP-UX as a host server, remember the following when you execute
the command on V-VOLs in order to recognize the device from the host server:
• If the device is already recognized by the host server, do not change its volumes to V-VOLs.
• Before executing the command to recognize the device, create XP Snapshot pairs and store
snapshot data.
If you do not follow these precautions, an error may occur and the host server may be terminated.
When the host server is terminated because of the command to recognize the device, retry the
command by completing the following steps:
1. Force the command process and its parent process to terminate.
2. Create an XP Snapshot pair.
3. Store the snapshot data in the pool.
4. Execute the command again to recognize the device.
Servers (including RAID Manager) will indicate the emulation type of the V-VOLs with a 0 (for
example, OPEN-0V). When you create an XP Snapshot pair, specify the volume whose emulation
type includes 0, such as OPEN-0V, as the S-VOL.
Before creating a V-VOL, you need to define a V-VOL group. Like the emulation type of V-VOLs,
the emulation type of a VDEV for a V-VOL group is OPEN-V. In addition, the capacity of the VDEV
is always 4 TB. Therefore, the maximum capacity of a V-VOL is also 4 TB.
XP Snapshot Operations 11
Creation of an XP Snapshot Pair
An XP Snapshot pair uses a V-VOL as its S-VOL. Therefore, you need to create a V-VOL before
creating an XP Snapshot pair. In an XP Snapshot pair, up to 64 S-VOLs can be specified for a
P-VOL.
CAUTION: When you create an XP Snapshot pair, you decide which pool will be used by the
pair. If you create two or more XP Snapshot pairs that share the same P-VOL, you need to specify
the same pool for these pairs. For example, if you specify three S-VOLs for one P-VOL, you need
to specify the same pool for these three pairs.
When you delete an XP Snapshot pair, the status of the volumes becomes SMPL(PD). You cannot
create pairs by using SMPL(PD) volumes. If the volumes are in SMPL(PD) status, wait for a while
and issue the command to create pairs after the volume status changes to SMPL.
Use the XP Business Copy's Pair Operation window to see the status of the volume. Using RAID
Manager, you can check the volume status by the pairdisplay command, but you cannot
distinguish between an SMPL volume and an SMPL(PD) volume. To distinguish between an SMPL
volume and an SMPL(PD) volume by using RAID Manager, you need to issue the inqraid command
as well. The inqraid command will show you whether or not the volume is being used by XP
Snapshot. As a result of the inqraid command, if the volume is not used by XP Snapshot, the
volume status is SMPL. If the volume is used by XP Snapshot, the status of the volume is SMPL(PD).
NOTE: When using the inqraid command specify the -fw option of the XP Snapshot pair IDs
from 3 to 63.
Storing XP Snapshot Data
XP Snapshot data is a replica of data in the P-VOL of an XP Snapshot pair, and is stored in a pool.
When the P-VOL is updated, the updated part of the data is copied to the pool as snapshot data
before the P-VOL is updated. This process is called storing snapshot data.
If you issue a command to an XP Snapshot pair to store snapshot data, the snapshot data will be
stored in the pool later, at the time a host makes a write request to the P-VOL of an XP Snapshot
pair. An XP Snapshot pair can store up to 64 snapshot data per a P-VOL.
To store snapshot data, you can use the RAID Manager command.
You can also store snapshot data for each consistency group by using RAID Manager. When you
store snapshot data by consistency group, data is copied as of the same point in time for all P-VOLs
in the group. Figure 4 (page 13) shows an overview of storing snapshot data by a consistency
group.
12 About XP Snapshot Operations
Figure 4 Overview of Storing XP Snapshot Data by a Consistency Group
When an XP24000/XP20000 Disk Array accepts the command from RAID Manager, which
requests storing the data by a consistency group (1 in Figure 4 (page 13)), all status of the XP
Snapshot pairs in the corresponding consistency group will change to PSUS (2 in Figure 4 (page
13)). After that, when the host issues write I/O request to each P-VOL in the corresponding
consistency group (3 in Figure 4 (page 13)), snapshot data of corresponding volume is stored (4
in Figure 4 (page 13)).
You can also use the RAID Manager commands to store snapshot data by a consistency group.
From XP Remote Web Console, you can only view the consistency groups.
XP Snapshot does not support Quick Split mode. Therefore, even if you specify Quick Split mode,
Quick Split mode does not take effect.
Restoration of an XP Snapshot Pair
XP Snapshot can restore the contents of the P-VOL to the state when the snapshot data was stored
in the pool by writing the snapshot data back to the P-VOL. Writing the snapshot data to the P-VOL
is called restoration of the XP Snapshot pair.
If you restore the pair when the data is written in the S-VOL, instead of the snapshot data, the data
in the S-VOL will be written back to the P-VOL.
If there are problems with the data of a P-VOL during a failure, you can restore the P-VOL to the
normal state when the snapshot data was stored by executing restoration.
Deletion of XP Snapshot Data or an XP Snapshot Pair
The status of the XP Snapshot pair will be PSUE (status when the failure occurred) when, as a result
of writing data in the volume of that pair, the capacity of snapshot data exceeds the capacity of
the pool specified when the pool was defined. An XP Snapshot pair cannot be created and snapshot
data cannot be stored in the pool. Therefore, unnecessary snapshot data needs to be deleted.
There are two ways to delete snapshot data:
XP Snapshot Operations 13
• Delete the XP Snapshot pair itself.
• Delete only the snapshot data.
When an XP Snapshot pair is deleted, not only is the snapshot data stored in the pool deleted,
but also the relationship between the P-VOL and the S-VOL will be released. If only the snapshot
data is deleted, the relationship between the P-VOL and the S-VOL is maintained. When only the
snapshot data is deleted, the snapshot ID of the deleted snapshot data can be assigned to the
newly stored snapshot data of the XP Snapshot pair.
After the command is issued to delete snapshot data, no more snapshot data of that XP Snapshot
pair will be stored in the pool, even if the host tries to write data in the P-VOL. To store snapshot
data for that XP Snapshot pair again, you need to issue the command for storing snapshot data.
The required time for deleting snapshot data or XP Snapshot pairs is several seconds, and sometimes
more than ten minutes. The time will increase if the deleted pair uses a large amount of the pool,
or if multiple pairs are deleted at one time.
When you delete an XP Snapshot pair, the status of the volumes becomes SMPL(PD). Use the XP
Business Copy's Pair Operation window to see the status of the volume.
Using RAID Manager, you can check the volume status by the pairdisplay command, but you
cannot distinguish between an SMPL volume and an SMPL(PD) volume. To distinguish between an
SMPL volume and an SMPL(PD) volume by using RAID Manager, you need to issue the inqraid
command as well. The inqraid command will show you whether or not the volume is being used
by XP Snapshot. As a result of the inqraid command, if the volume is not used by XP Snapshot,
the volume status is SMPL. If the volume is used by XP Snapshot, the status of the volume is SMPL(PD).
NOTE: When using the inqraid command, specify the -fw option of the XP Snapshot pair IDs
from 3 to 63.
Status of the XP Snapshot Pairs
When you create or split an XP Snapshot pair, the status of the pair changes. “XP Snapshot Pair
Status Transition” (page 15) shows the transition of the status of an XP Snapshot pair.
14 About XP Snapshot Operations
Figure 5 XP Snapshot Pair Status Transition
1. If a volume is not assigned to an XP Snapshot pair, its status is SMPL.
2. Issue the paircreate command on the SMPL volume to create an XP Snapshot pair. When
you create the first pair for the P-VOL, the pair status changes to COPY, and then the pair
status changes to PAIR when the operation completes. If you specify a volume which is already
paired with one or more S-VOLs as the P-VOL to create another pair, the pair status will not
change to COPY. The pair status will change to PAIR when the operation completes.
3. Issue the pairsplit command on the XP Snapshot pair in PAIR status to store the snapshot
data in the pool. When the operation completes, the pair status changes to PSUS.
• If you execute the paircreate command immediately after deleting the last snapshot
data of the P-VOL, it may take time to create a new pair.
• If the pool capacity exceeds the threshold when an XP Snapshot pair is in PAIR status,
the pair status changes to PFUL in RAID Manager. For details, see the HP StorageWorks
XP RAID Manager User Guide.
• If the pool capacity exceeds the threshold when an XP Snapshot pair is in PSUS status,
the pair status changes to PFUS in RAID Manager. For details, see the HP StorageWorks
XP RAID Manager User Guide.
4. To delete only snapshot data and leave the XP Snapshot pair, issue the pairresync command
to the PSUS or PFUS pair. During the operation, the pair status changes to COPY(RS).
To delete the XP Snapshot pair, issue the pairsplit-S command or use Remote Web
Console. During the operation, the pair status changes to SMPL(PD).
5. Issue the pairresync -restore command on the XP Snapshot pair in PSUS status to restore
the pair. After that, the snapshot data will be written back to the P-VOL. During the operation,
Status of the XP Snapshot Pairs 15
the pair status changes 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 the pool exceeds the pool capacity, the pair status changes to PSUE. The pair status
also changes to PSUE when a failure occurs while restoring the pair or when the usage rate
of the pool reaches 100 percent. The pair status may change to PSUE when the failure occurs
during a process other than restoring.
Whether the host can read and write the P-VOL or S-VOL of an XP Snapshot pair depends on the
status of the pair. Table 2 (page 16) shows the relationship between the pair status and the
availability of the host access.
Table 2 Whether Hosts Can Access P-VOL and S-VOL
S-VOLP-VOLPair Status
WriteReadWriteRead
——YesYesSMPL
NoNoYesYesCOPY
NoNoYesYesPAIR/PFUL
YesYesYesYesPSUS/PFUS
NoNoYesYesSMPL(PD)
NoNoYesYesCOPY(RS)
NoNoYesYesCOPY(RS-R)
NoNoYes*Yes*PSUE
Yes: Host can access the volume.
No: Host cannot access the volume.
*: If the pair status changes to PSUE because of a failure during restoration, the host cannot access
that pair.
CAUTION: If the host computer uses application software to monitor the volumes of the XP
Snapshot pairs, problems such as an abnormal end may occur. For example, because the S-VOL
whose status is not PSUS (or PFUS) rejects the access from the host, problems may occur on the
monitoring application software whose access is rejected. In addition, if the host computer connects
to more than one port, problems may also occur on the ports that are not connected to the S-VOL
that rejected the host access. You need to terminate the application software which monitors the
volumes in order to solve these problems.
Use RAID Manager commands to operate XP Snapshot pairs. However, whether or not the
operations complete normally depends on the status of the pairs. Table 3 (page 16) shows the
pair statuses and the results of the RAID Manager commands.
Table 3 Pair Statuses and the Results of the RAID Manager Commands
RAID Manager CommandPair Status
paircreate
16 About XP Snapshot Operations
−split
pairresyncpairsplitpaircreate
-restore
pairsplit -Epairsplit -Spairresync
NoNOPNoNoNoNoYesSMPL
NoNoNOPNOPNoNoNOPCOPY
NoYesNOPNOPYesYesNOPPAIR / PFUL
Table 3 Pair Statuses and the Results of the RAID Manager Commands (continued)
RAID Manager CommandPair Status
pairsplit -Epairsplit -Spairresync
NoYesYesYesNOPNOPNoPSUS /
NoNOPNoNoNoNoNoSMPL(PD)
NoNoNOPNOPNoNoNOPCOPY(RS)
NoNoNOPNOPNoNoNOPCOPY(RS-R)
NOPYesNoYes*NoNoNoPSUE
PFUS
paircreate
−split
pairresyncpairsplitpaircreate
-restore
Yes: The command executes the process and ends normally.
NOP: The command does not execute the process, but ends normally.
No: The command ends abnormally (that is, command rejected).
* If you issue the pairresync command to the pair whose status has changed to PSUE because
of the shortage of the shared memory for the V-VOL management area, the command will be
rejected and end abnormally.
When the command executes the process and ends normally, the pair status changes according
to the process. For information about how the pair status changes when the command ends normally,
see “XP Snapshot Pair Status Transition” (page 15) and the paragraphs under the figure.
• The hide mode (-m noread) on the S-VOL is not supported. If you specify the hide mode on
the S-VOL and create a pair, the command will end normally, but the hide mode will be
ignored.
• When the RAID Manager command ends abnormally (for example, when the RAID Manager
command is rejected), and if the OS of the host computer is HP-UX, SSB (sense byte), which
indicates the cause of the error, will be generated in the RAID Manager error log file. For
more information about the SSBs and the cause of the errors, see “Troubleshooting When
Using XP RAID Manager” (page 103).
Table 4 SSBs and Causes of Error Issued Upon Rejection of RAID Manager Commands
Cause of ErrorRAID Manager CommandSSB
paircreate, pairresync, pairsplitB901
B9A8
B9A9
B9AD
paircreate9685
paircreate9686
paircreate9700
An error has occurred during the XP
Snapshot pair operation. For the cause,
check the SSB being output together.
Because there are no pair tables
available, the XP Snapshot pair cannot
be created.
Because of the shortage of the
differential tables, XP Snapshot pair
cannot be created.
Because the pool is not available, the
XP Snapshot pair cannot be created.
Status of the XP Snapshot Pairs 17
Table 4 SSBs and Causes of Error Issued Upon Rejection of RAID Manager Commands (continued)
Cause of ErrorRAID Manager CommandSSB
paircreate9702
paircreate9703
paircreate9704
paircreate9705
paircreate9706
paircreate9707
When attempting to create multiple XP
Snapshot pairs by specifying multiple
S-VOLs for one P-VOL, you specified a
pool ID that was different from the one
being used by existing pairs. As a
result, new XP Snapshot pairs cannot
be created.
Because the volume you specified as
the P-VOL is being used by the other XP
Snapshot S-VOL, the pair cannot be
created.
Because the volume you specified as
the S-VOL is being used by the other XP
Snapshot P-VOL, the pair cannot be
created.
Because the volume you specified as
the S-VOL is being used by the other XP
Snapshot S-VOL, the pair cannot be
created.
Because the specified snapshot ID is
being used by the other XP Snapshot
pair, the new pair cannot be created.
Because the capacity of the pair
exceeds the licensed capacity, the pair
cannot be created.
All commands9718
All commands9719
paircreate971a
paircreate971b
pairresync -restore971f
The command ended abnormally
because a command other than the
paircreate command was issued for the
volume in the pair other than XP
Snapshot pair.
This error also may be reported when
the command is executed with
specifying an unsupported parameter.
The command ended abnormally
because the pair is in the status that the
corresponding command is not
accepted at present.
This error also may be reported when
the command is executed with
specifying an unsupported parameter.
Because the capacity of shared memory
is insufficient, the pair cannot be
created.
Because the capacity of shared memory
is insufficient, the pair cannot be
created.
Because the volume you specified as
the P-VOL has an S-VOL Disable
attribute, XP Snapshot pair cannot be
restored.
18 About XP Snapshot Operations
All commands9720
Any errors have occurred because of
the XP Snapshot operation.
Table 4 SSBs and Causes of Error Issued Upon Rejection of RAID Manager Commands (continued)
Cause of ErrorRAID Manager CommandSSB
9721
9727
9728
paircreate pairsplit pairresync
pairresync -restore
All commands9723
All commands9724
All commands9725
All commands9726
paircreate, pairsplit, pairresync,
pairresync -restore
paircreate, pairsplit, pairresync,
pairresync -restore
Because either XP Snapshot or XP
Business Copy is not installed, the
command ends abnormally.
Because no additional shared memory
(FCV2, TPF, Extension is available, the
command ends abnormally.
Because no additional shared memory
(more than XP Snapshot) is available,
the command ends abnormally.
Because the LDEV number of the volume
you specified as the P-VOL is beyond
the specified range, the command ends
abnormally.
Because you specified the unmounted
volume as the XP Snapshot P-VOL, the
command ends abnormally.
Because you specified the blocked
volume as the XP Snapshot P-VOL, the
command ends abnormally.
Because you specified the volume that
is in process of formatting as the XP
Snapshot P-VOL, the command ends
abnormally.
9729
paircreate, pairsplit, pairresync,
pairresync -restore
paircreate972a
paircreate972c
paircreate972e
paircreate972f
paircreate9730
pairresync -restore9731
Because you specified the volume
whose emulation type is other than
OPEN-V as the XP Snapshot P-VOL, the
command ends abnormally.
Because the volume you specified as
the XP Snapshot P-VOL has the
command device setting, the pair
cannot be created.
Because the capacity of the volume you
specified as the XP Snapshot P-VOL
exceeds the supported size (4 TB), the
pair cannot be created.
Because the capacity of the volume you
specified as the XP Snapshot S-VOL
exceeds the supported size (4 TB), the
pair cannot be created.
Because you specified a V-VOL as the
XP Snapshot P-VOL, the pair cannot be
created.
Because you specified a pool-VOL as
the XP Snapshot P-VOL, the pair cannot
be created.
When the XP Snapshot P-VOL and XP
Continuous Access P-VOL share the
volume, the status of the XP Continuous
Access pair is other than PSUS or PSUE.
Therefore, the XP Snapshot pair cannot
be restored.
Status of the XP Snapshot Pairs 19
Table 4 SSBs and Causes of Error Issued Upon Rejection of RAID Manager Commands (continued)
Cause of ErrorRAID Manager CommandSSB
9736
pairresync -restore9732
pairresync -restore9733
pairresync -restore9734
paircreate9735
paircreate, pairsplit, pairresync,
pairresync -restore
paircreate973a
When the XP Snapshot P-VOL and XP
Continuous Access Journal P-VOL share
the volume, the status of the XP
Continuous Access Journal pair is other
than PSUS or PSUE. Therefore, the XP
Snapshot pair cannot be restored.
Because the XP Snapshot P-VOL and XP
Continuous Access S-VOL share the
volume, the XP Snapshot pair cannot
be restored.
Because the XP Snapshot P-VOL and XP
Continuous Access Journal S-VOL share
the volume, the XP Snapshot pair
cannot be restored.
Because you specified an XP
Continuous Access Journal’s journal
volume as the XP Snapshot P-VOL, the
XP Snapshot pair cannot be created.
Because the LUSE volumes you specified
for the P-VOL and S-VOL do not have
the same structure, the command ends
abnormally.
Because you specified the volume with
the VMA setting as the XP Snapshot
P-VOL, the pair cannot be created.
973d
973e
973f
All commands973b
All commands973c
paircreate, pairsplit, pairresync,
pairresync -restore
paircreate, pairsplit, pairresync,
pairresync -restore
paircreate, pairsplit, pairresync,
pairresync -restore
paircreate9740
paircreate9742
Because the LDEV number of the volume
you specified as the S-VOL is beyond
the specified range, the command ends
abnormally.
Because you specified the unmounted
volume as the XP Snapshot S-VOL, the
command ends abnormally.
Because you specified the blocked
volume as the XP Snapshot S-VOL, the
command ends abnormally.
Because you specified the volume that
is in process of formatting as the XP
Snapshot S-VOL, the command ends
abnormally.
Because you specified the volume
whose emulation type is other than
OPEN-V as the XP Snapshot S-VOL, the
command ends abnormally.
Because the volume you specified as
the XP Snapshot S-VOL has the
command device setting, the pair
cannot be created.
Because you specified an external
volume as the XP Snapshot S-VOL, the
pair cannot be created.
20 About XP Snapshot Operations
paircreate9745
Because you specified a volume other
than V-VOL as the XP Snapshot S-VOL,
the pair cannot be created.
Table 4 SSBs and Causes of Error Issued Upon Rejection of RAID Manager Commands (continued)
Cause of ErrorRAID Manager CommandSSB
paircreate9746
paircreate9747
paircreate9748
paircreate9749
paircreate974a
paircreate974b
Because you specified a pool-VOL as
the XP Snapshot S-VOL, the pair cannot
be created.
Because you specified the XP
Continuous Access P-VOL as the XP
Snapshot S-VOL, the XP Snapshot pair
cannot be created.
Because you specified the XP
Continuous Access S-VOL as the XP
Snapshot S-VOL, the XP Snapshot pair
cannot be created.
Because you specified the XP
Continuous Access Journal data volume
or journal volume in the intermediate
site of 3DC cascading configuration as
the XP Snapshot S-VOL, the XP Snapshot
pair cannot be created.
Because you specified the XP
Continuous Access Journal P-VOL as the
XP Snapshot S-VOL, the XP Snapshot
pair cannot be created.
Because you specified the XP
Continuous Access Journal S-VOL as the
XP Snapshot S-VOL, the XP Snapshot
pair cannot be created.
9752
9753
paircreate974c
All commands974f
paircreate9750
paircreate, pairsplit, pairresync,
pairresync -restore
paircreate, pairsplit, pairresync,
pairresync -restore
paircreate9754
Because you specified the XP
Continuous Access Journal journal
volume as the XP Snapshot S-VOL, the
XP Snapshot pair cannot be created.
Because the volume you specified as
the S-VOL has an S-VOL Disable
attribute, the command ends
abnormally.
Because you specified the volume with
the VMA setting as the XP Snapshot
S-VOL, the pair cannot be created.
Because the Max LBA size of the
volumes you specified as the XP
Snapshot P-VOL and S-VOL are
different, the command ends
abnormally.
Because the number of slots of the
volumes you specified as the XP
Snapshot P-VOL and S-VOL are
different, the command ends
abnormally.
Because you specified the XP Thin
Provisioning V-VOL as the XP Snapshot
S-VOL, the XP Snapshot pair cannot be
created.
All commands9756
Because you specified the XP Business
Copy reserved volume as the XP
Snapshot P-VOL, the command ends
abnormally.
Status of the XP Snapshot Pairs 21
Table 4 SSBs and Causes of Error Issued Upon Rejection of RAID Manager Commands (continued)
Cause of ErrorRAID Manager CommandSSB
All commands9757
All commands9758
All commands9759
All commands975a
All commands975b
Because you specified the XP Auto LUN
source volume as the XP Snapshot
P-VOL, the command ends abnormally.
For information on using XP Auto LUN,
contact HP technical support (see
“Contacting HP” (page 116)).
Because you specified the XP Auto LUN
target volume as the XP Snapshot
P-VOL, the command ends abnormally.
For information on using XP Auto LUN,
contact HP technical support (see
“Contacting HP” (page 116)).
Because you specified the XP Auto LUN
reserved volume as the XP Snapshot
P-VOL, the command ends abnormally.
For information on using XP Auto LUN,
contact HP technical support (see
“Contacting HP” (page 116)).
Because you specified the XP Business
Copy P-VOL as the XP Snapshot S-VOL,
the command ends abnormally.
Because you specified the XP Business
Copy S-VOL as the XP Snapshot S-VOL,
the command ends abnormally.
All commands975c
All commands975d
All commands975e
All commands975f
paircreate976a
Because you specified the XP Business
Copy reserved volume as the XP
Snapshot S-VOL, the command ends
abnormally.
Because you specified the XP Auto LUN
source volume as the XP Snapshot
S-VOL, the command ends abnormally.
For information on using XP Auto LUN,
contact HP technical support (see
“Contacting HP” (page 116)).
Because you specified the XP Auto LUN
target volume as the XP Snapshot
S-VOL, the command ends abnormally.
For information on using XP Auto LUN,
contact HP technical support (see
“Contacting HP” (page 116)).
Because you specified the XP Auto LUN
reserved volume as the XP Snapshot
S-VOL, the command ends abnormally.
For information on using XP Auto LUN,
contact HP technical support (see
“Contacting HP” (page 116)).
Unavailable parameter (unsupported
parameter) is specified in the command.
22 About XP Snapshot Operations
pairsplit976c
Because the command was executed
with the PSUE option, the XP Snapshot
data cannot be stored.
Table 4 SSBs and Causes of Error Issued Upon Rejection of RAID Manager Commands (continued)
Cause of ErrorRAID Manager CommandSSB
pairresync976e
pairsplit976e
pairsplit976f
paircreate9771
paircreate9772
When XP Snapshot P-VOL and XP
Continuous Access S-VOL share the
volume, the status of the XP Continuous
Access pair is COPY. Therefore, the
snapshot data cannot be stored.
When the XP Snapshot P-VOL and XP
Continuous Access S-VOL share the
volume, the status of the XP Continuous
Access pair is COPY. Therefore, the
snapshot data cannot be stored.
When the XP Snapshot P-VOL and XP
Continuous Access Journal S-VOL share
the volume, the status of the XP
Continuous Access Journal pair is
COPY. Therefore, the snapshot data
cannot be stored.
Because you specified XP Continuous
Access Journal delta resync pair volume
as the XP Snapshot P-VOL, the XP
Snapshot pair cannot be created.
Because you specified the XP
Continuous Access Journal delta resync
pair volume as the XP Snapshot S-VOL,
the XP Snapshot pair cannot be
created.
paircreate9774
paircreate9776
paircreate9777
paircreate9778
When the XP Snapshot P-VOL and XP
Business Copy P-VOL share the volume,
the MU number you specified for the
XP Snapshot pair is already used by
the XP Business Copy pair. Therefore,
the XP Snapshot pair cannot be
created.
When the XP Snapshot P-VOL and XP
Business Copy P-VOL share the volume,
the XP Business Copy P-VOL you
specified for the XP Snapshot P-VOL has
consistency group settings. Therefore,
the XP Snapshot pair cannot be
created.
When the XP Snapshot P-VOL and XP
Business Copy S-VOL share the volume,
you specified the MU number zero (0)
for the XP Snapshot P-VOL. Therefore,
the XP Snapshot pair cannot be
created.
When the XP Snapshot P-VOL and XP
Business Copy S-VOL share the volume,
the XP Business Copy S-VOL you
specified for the XP Snapshot P-VOL has
consistency group settings. Therefore,
the XP Snapshot pair cannot be
created.
Status of the XP Snapshot Pairs 23
Table 4 SSBs and Causes of Error Issued Upon Rejection of RAID Manager Commands (continued)
Cause of ErrorRAID Manager CommandSSB
paircreate, pairsplit977a
paircreate, pairsplit977b
pairresync -restore977c
pairresync -restore977d
pairsplit977e
When the XP Snapshot P-VOL and XP
Business Copy P-VOL share the volume,
the XP Business Copy pair was in the
process of resynchronization. Therefore,
the command ends abnormally.
When the XP Snapshot P-VOL and XP
Business Copy S-VOL share the volume,
the status of the XP Business Copy pair
is other than PSUS. Therefore, the
command ends abnormally.
When the XP Snapshot P-VOL and XP
Business Copy P-VOL share the volume,
the status of the XP Business Copy pair
is other than PSUS or PSUE. Therefore,
the XP Snapshot pair cannot be
restored.
When the XP Snapshot P-VOL and XP
Business Copy S-VOL share the volume,
the status of the XP Business Copy pair
is other than PSUS. Therefore, the XP
Snapshot pair cannot be restored.
Since the pool or the pool-VOL is
blocked, the XP Snapshot data cannot
be stored.
9786
9787
pairresync -restore9783
paircreate, pairsplit, pairresync,
pairresync -restore
paircreate, pairsplit, pairresync,
pairresync -restore
The XP Snapshot pair cannot be
restored for any of the following
reasons:
• The snapshot data of the XP
Snapshot pair for restoration is
being stored per consistency group.
• The P-VOL of the XP Snapshot pair
for restoration is used as the P-VOL
of another XP Snapshot pair, and
the snapshot data of the latter XP
Snapshot pair is being stored per
consistency group.
Since quorum disks are specified as
P-VOLs of XP Snapshot pairs, the
command ends abnormally.
Since quorum disks are specified as
S-VOLs of XP Snapshot pairs, the
command ends abnormally.
24 About XP Snapshot Operations
Table 4 SSBs and Causes of Error Issued Upon Rejection of RAID Manager Commands (continued)
Cause of ErrorRAID Manager CommandSSB
paircreate978a
paircreate978b
pairsplit978c
Because one of the following cases
happened, the XP Snapshot pair cannot
be created by specifying the
consistency number.
• The specified consistency group
number is in use for XP Business
Copy Software.
• The number of pairs has already
exceeded the maximum number of
pairs that can be created for one
consistency group.
• The pair which uses the same P-VOL
exists already in the specified
consistency group.
The XP Snapshot pair cannot be created
because the specified consistency group
number is out of the range of the
number which can be specified.
The snapshot data cannot be stored
because the XP Continuous Access
Asynchronous Software pair status is
other than PSUS or PSUE when XP
Snapshot (P-VOL) and XP Continuous
Access Asynchronous Software (S-VOL)
share the volume.
Copy Threshold Option
If the load of the storage system increases, host server I/O performance (response) may be
degraded. If XP Snapshot performs the restore operation when the load of the storage system is
heavy, it is more likely that host server I/O performance (response) may be degraded. The Copy
Threshold option temporarily stops copy processing caused by the restore operation when the load
of the storage system is heavy. If you set this option in effect, you can minimize the degradation
of host I/O performance by temporarily stopping copy processing caused by the restore operation
when the load of the storage system is heavy.
paircreate978e
paircreate9790
paircreate9793
All commandsB9A7
The XP Snapshot pair for which the
consistency group is specified cannot
be created because the P-VOL or S-VOL
of the XP Continuous Access
Asynchronous Software pair is specified
as the P-VOL of the XP Snapshot pair.
The XP Thin Provisioning virtual volume
that is undergoing capacity expansion
is specified as the XP Snapshot P-VOL.
Therefore, the XP Snapshot pair cannot
be created.
The XP Snapshot pair cannot be created
because the XP Thin Provisioning
Software V-VOL that is discarding zero
data is specified as a P-VOL of the XP
Snapshot pair.
The consistency group information
cannot be obtained because the XP
Snapshot is not installed.
Copy Threshold Option 25
The Copy Threshold option is effective only when the load of the storage system is heavy. When
the Copy Threshold option is in effect, all the copy processing by the restore operation stops. For
information about the setting of the Copy Threshold option, call HP technical support.
Copy operations that are stopped by the Copy Threshold option will resume when the load of the
storage system becomes light. If this option is in effect, not only XP Snapshot copy operations, but
also the copy operations of the following program products, will stop when the load of the storage
system is heavy:
• XP Business Copy Software
• XP Business Copy for Mainframe
• HP StorageWorks XP for FlashCopy Mirroring Software (both Version 1 and 2)
• XP Auto LUN Software
Interoperability with Other Products and Functions
XP Snapshot can create pairs by sharing volumes with other program products, such as XP Business
Copy or XP Continuous Access. In addition, you can create XP Snapshot pairs by using volumes
to which attributes are assigned by the Data Retention Utility or RAID Manager. Table 5 (page 26)
shows whether or not XP Snapshot pairs can share volumes with other program products.
Table 5 Volume Sharing with Other Program Products
XP Business Copy pair P-VOL
XP Business Copy pair S-VOL
1
2
XP Snapshot Pair S-VOLXP Snapshot Pair P-VOLVolumes of Other Program Products
NoYes
NoYes
NoYesXP Continuous Access pair P-VOL
NoYesXP Continuous Access pair S-VOL
NoYesHP StorageWorks XP XP Continuous Access
Journal Software pair P-VOL
NoYesXP Continuous Access Journal pair S-VOL
2
2
Yes: The XP Snapshot volume can be shared.
No: The XP Snapshot volume cannot be shared.
1 An XP Business Copy pair and an XP Snapshot pair cannot have the same mirror unit (MU) number. For
example, if the MU number of the XP Business Copy pair is 0, you cannot create an XP Snapshot pair
whose MU number is 0 and whose P-VOL is also used as an XP Business Copy P-VOL. Also, if the MU
number of the XP Snapshot pair is 1, you cannot create an XP Business Copy pair whose MU number is 1
and whose P-VOL is also used as an XP Snapshot P-VOL.
2
For information on using XP Auto LUN Software, contact HP technical support (see “Contacting HP”
(page 116)).
When XP Snapshot shares volumes with the other program products, some operations are restricted according
to the pair statuses. For detailed information, see the following sections.
NoYesAuto LUN source volume
NoNoAuto LUN target volume
YesYesRead Only volume
YesYesProtect volume
YesYesS-VOL Disable volume
YesYesZero Read Capacity volume
YesYesInvisible volume
26 About XP Snapshot Operations
• You need Data Retention Utility to set the Read Only attribute, the Protect attribute, or S-VOL
Disable. For details, see the HP StorageWorks XP24000/XP20000 Data Retention Utility User
Guide.
• You need RAID Manager to set the Zero Read Capacity attribute or the Invisible attribute. For
details, see the HP StorageWorks XP RAID Manager User Guide.
• You can check if the volume has the Read Only attribute, the Protect attribute, S-VOL Disable,
the Zero Read Capacity attribute, or the Invisible attribute by checking the Data Retention
Utility window. For details, see the HP StorageWorks XP24000/XP20000 Data Retention
Utility User Guide.
Data Retention Utility
Data Retention Utility can set four different kinds of access attributes on the volumes: Read/Write,
Read Only, Protect, and S-VOL Disable. XP Snapshot cannot create a pair by specifying a volume
whose access attribute is S-VOL Disable as the S-VOL. In addition, if the S-VOL Disable attribute
is set on the P-VOL of the XP Snapshot pair, you cannot restore the pair.
By using Data Retention Utility, you can set the Read/Write, Read Only, Protect, or S-VOL Disable
attribute on the volumes that are already used by the XP Snapshot pairs. However, when the pair
is in the following status, you cannot set the S-VOL Disable attribute on the pair volumes:
• COPY*
• SMPL(PD)*
• COPY(RS)*
• COPY(RS-R)
• PSUE*
*: You can set S-VOL Disable on the P-VOL even if the pair status is COPY, SMPL(PD), COPY(RS),
or PSUE.
For detailed information about setting the access attribute, see the HP StorageWorks
XP24000/XP20000 Data Retention Utility User Guide.
Auto LUN
Regardless of the status of the migration plans of Auto LUN, you cannot perform any XP Snapshot
operations on a volume that is used by the migration plan. To use an XP Snapshot P-VOL as the
source volume for the migration plan, you need to create the XP Snapshot pair first, and then create
the migration plan.
When the XP Snapshot P-VOL and the source volume for the migration plan are shared, you can
execute the migration plan only when the XP Snapshot pair is in PAIR status. Deleting and canceling
the migration plan are always allowed. These operations are not affected by the XP Snapshot pair
status.
For information on using XP Auto LUN, contact HP technical support (see “Contacting HP”
(page 116)).
XP Business Copy
“XP Snapshot Operations for Shared XP Snapshot P-VOL/XP Business Copy P-VOL” (page 28) and
“XP Snapshot Operations for Shared XP Snapshot P-VOL/XP Business Copy S-VOL” (page 28)
show the relationship between XP Business Copy pair status and XP Snapshot operations when the
XP Snapshot P-VOL is shared with an XP Business Copy volume.
“XP Business Copy Operations for Shared XP Snapshot P-VOL/XP Business Copy P-VOL” (page 29)
and “XP Business Copy Operations for Shared XP Snapshot P-VOL/XP Business Copy S-VOL”
Interoperability with Other Products and Functions 27
(page 29) show the relationship between the XP Snapshot pair status and XP Business Copy
operations for shared volumes.
For detailed information about XP Business Copy pair status and operations, see the HP
StorageWorks XP24000/XP20000 Business Copy Software User Guide.
• Because the XP Snapshot S-VOL uses the data in the P-VOL, XP Business Copy's quick backward
pairresync operation (Quick Restore) is not allowed.
• If a volume of an XP Business Copy pair has consistency group settings, you cannot use this
volume to create an XP Snapshot pair. Also, if you use a volume of an XP Snapshot pair to
create the XP Business Copy pair, you cannot set the consistency group to the XP Business
Copy pair.
• If a volume of an XP Snapshot pair has consistency group settings, you cannot use this volume
to create an XP Business Copy Software pair. Also, if you use a volume of an XP Business
Copy pair to create the XP Snapshot pair, you cannot set the consistency group to the XP
Snapshot pair.
Table 6 XP Snapshot Operations for Shared XP Snapshot P-VOL/XP Business Copy P-VOL
XP Business Copy Pair StatusXP Snapshot Operations
PSUECOPY
YesNoYesYesYesYesYesYesCreating pairs (paircreate)
YesNoYesYesYesYesYesYesStoring snapshot data
YesNoNoYesNoNoNoNoRestoring pairs (pairresync
YesYesYesYesYesYesYesYesDeleting snapshot data
YesYesYesYesYesYesYesYesDeleting pairs (pairsplit
(pairsplit)
−restore)
(pairresync)
−S)
COPY
PAIRCOPY
(SP)
(SP)
PSUSPSUS
COPY
(RS)
(RS-R)
Yes: Operation is allowed.
No: Operation is not allowed (command rejected).
Table 7 XP Snapshot Operations for Shared XP Snapshot P-VOL/XP Business Copy S-VOL
XP Business Copy Pair StatusXP Snapshot Operations
COPY
PAIRCOPY
(SP)
(SP)
PSUSPSUS
COPY
(RS)
(RS-R)
PSUECOPY
NoNoNoYesNoNoNoNoCreating pairs (paircreate)
(pairsplit)
−restore)
(pairresync)
−S)
Yes: Operation is allowed.
No: Operation is not allowed (command rejected).
N/A: Not applicable.
28 About XP Snapshot Operations
NoNoNoYesNoNoNoN/AStoring snapshot data
NoNoNoYesNoNoNoN/ARestoring pairs (pairresync
YesYesYesYesYesYesYesN/ADeleting snapshot data
YesYesYesYesYesYesYesN/ADeleting pairs (pairsplit
Table 8 XP Business Copy Operations for Shared XP Snapshot P-VOL/XP Business Copy P-VOL
XP Snapshot Pair StatusXP Business Copy Operations
PSUSPAIRCOPY
(paircreate −split)
resynchronization
(pairresync)
resynchronization
(pairresync −restore)
resynchronization
(pairresync −restore)
−E)
−S)
Yes: Operation is allowed.
No: Operation is not allowed (command rejected).
SMPL
(PD)
COPY
(RS)
PSUECOPY
(RS-R)
YesNoYesYesYesYesYesCreating pairs (paircreate)
YesNoYesYesYesYesYesCreating and splitting pairs
YesNoYesYesYesYesYesSplitting pairs (pairsplit)
YesNoYesYesYesYesYesForward pair
YesNoYesYesYesYesYesNormal backward pair
NoNoNoNoNoNoNoQuick backward pair
YesYesYesYesYesYesYesSuspending pairs (pairsplit
YesYesYesYesYesYesYesDeleting pairs (pairsplit
Table 9 XP Business Copy Operations for Shared XP Snapshot P-VOL/XP Business Copy S-VOL
XP Snapshot Pair StatusXP Business Copy Operations
PSUECOPY
NoNoNoNoNoNoNoCreating pairs (paircreate)
NoNoNoNoNoNoNoCreating and splitting pairs
YesNoYesYesYesYesYesSplitting pairs (pairsplit)
YesNoYesYesYesYesYesForward pair
YesNoYesYesYesYesYesNormal backward pair
NoNoNoNoNoNoNoQuick backward pair
YesNoYesYesYesYesYesSuspending pairs (pairsplit
YesYesYesYesYesYesYesDeleting pairs (pairsplit
(paircreate −split)
resynchronization
(pairresync)
resynchronization
(pairresync −restore)
resynchronization
(pairresync −restore)
−E)
−S)
PSUSPAIRCOPY
SMPL
(PD)
COPY
(RS)
(RS-R)
Yes: Operation is allowed.
No: Operation is not allowed (command rejected).
Interoperability with Other Products and Functions 29
XP Continuous Access or XP Continuous Access Journal
“XP Snapshot Operations for Shared XP Snapshot P-VOL/XP Continuous Access or XP Continuous
Access Journal P-VOL” (page 30) and “XP Snapshot Operations for Shared XP Snapshot P-VOL/XP
Continuous Access or XP Continuous Access Journal S-VOL” (page 30) show the relationship
between the XP Continuous Access or XP Continuous Access Journal pair status and XP Snapshot
operations when the XP Snapshot P-VOL is shared with an XP Continuous Access or XP Continuous
Access Journal volume.
“XP Continuous Access / XP Continuous Access Journal Operations for Shared XP Snapshot
P-VOL/XP Continuous Access or XP Continuous Access Journal P-VOL” (page 31) and “XP Continuous
Access/XP Continuous Access Journal Operations for Shared XP Snapshot P-VOL/XP Continuous
Access or XP Continuous Access Journal S-VOL” (page 31) show the relationship between the XP
Snapshot pair status and XP Continuous Access or XP Continuous Access Journal operations for
shared volumes.
If a volume uses two mirrors in the 3DC multi-target configuration, the 3DC cascade configuration,
or the delta resync configuration consisting of three XP Continuous Access Journal sites, the volume
cannot be used as an XP Snapshot pair volume.
For detailed information about XP Continuous Access pair status and operations, see the HP
StorageWorks XP24000/XP20000 Continuous Access Software User Guide. For detailed
information about XP Continuous Access Journal pair status and operations, see the HP
StorageWorks XP24000/XP20000 XP Continuous Access Journal Software User Guide.
Table 10 XP Snapshot Operations for Shared XP Snapshot P-VOL/XP Continuous Access or XP
Continuous Access Journal P-VOL
XP Continuous Access / XP Continuous Access Journal Pair StatusXP Snapshot Operations
DeletingSuspendingPSUEPSUSPAIRCOPY
YesYesYesYesYesYesCreating pairs (paircreate)
Storing snapshot data
(pairsplit)
−restore)
(pairresync)
−S)
Yes
Yes
*
*
Yes
*
Yes
*
Yes
*
Yes
NoNoYesYesNoNoRestoring pairs (pairresync
YesYesYesYesYesYesDeleting snapshot data
YesYesYesYesYesYesDeleting pairs (pairsplit
*
Yes: Operation is allowed.
No: Operation is not allowed (command rejected).
* These pairs cannot be used as XP Continuous Access Journal delta resync pair volumes.
Table 11 XP Snapshot Operations for Shared XP Snapshot P-VOL/XP Continuous Access or XP
Continuous Access Journal S-VOL
XP Continuous Access / XP Continuous Access Journal Pair StatusXP Snapshot Operations
Creating pairs (paircreate)
Yes
Yes
1
Yes
3
3
PSUEPSUSPAIRCOPY
Yes
3
Yes
3
Yes
3
3
DeletingSuspendingSSWS
Yes
3
(pairsplit)
−restore)
30 About XP Snapshot Operations
2
YesYesYesYesYesYesNoStoring snapshot data
NoNoNoNoNoNoNoRestoring pairs (pairresync
Loading...