HP XP RAID Manager Software - Manual (Page 51)

Table 21 RAID Manager error codes for SSB1: B901, B9A8, B9A9, B9AD, B9AE (continued)
Cause of Error RAID Manager
Command SSB2
Since you specified the Auto LUN target volume as the Snapshot S-VOL, the
command ends abnormally. All commands 975e
For information about using Auto LUN, contact HP Technical Support.
Since you specified the Auto LUN reserved volume as the Snapshot S-VOL, the
command ends abnormally. All commands 975f
For information about using Auto LUN, contact HP Technical Support.
The Snapshot pair cannot be created for any of the following reasons: paircreate 9763
• The shared memory is not increased.
•
Initialization is in process.
Unavailable parameter (unsupported parameter) is specified in the command. paircreate 976a
Since the command was executed with the PSUE option, the Snapshot data
cannot be stored. pairsplit 976c
When Snapshot P-VOL and Continuous Access Synchronous S-VOL share the
volume, the status of the Continuous Access Synchronous pair is COPY. Therefore,
the Snapshot data cannot be stored. pairsplit 976e
When Snapshot P-VOL and Continuous Access Journal S-VOL share the volume,
the status of the Continuous Access Journal pair is COPY. Therefore, the Snapshot
data cannot be stored. pairsplit 976f
Since you specified Continuous Access Journal delta resync pair volume as the
Snapshot P-VOL, the Snapshot pair cannot be created. paircreate 9771
Since you specified Continuous Access Journal delta resync pair volume as the
Snapshot S-VOL, the Snapshot pair cannot be created. paircreate 9772
When the Snapshot P-VOL and Business Copy P-VOL share the volume, the MU
number you specified for the Snapshot pair is already used by the Business Copy
pair. Therefore, the Snapshot pair cannot be created. paircreate 9774
When the Snapshot P-VOL and Business Copy S-VOL share the volume, you
specified MU number zero (0) for the Snapshot P-VOL. Therefore, the Snapshot
pair cannot be created. paircreate 9777
When the Snapshot P-VOL and Business Copy P-VOL share the volume, the
Business Copy pair was in the process of resynchronization. Therefore, the
command ends abnormally. paircreate, pairsplit 977a
When Snapshot P-VOL and Business Copy S-VOL share the volume, the status
of the Business Copy pair is other than PSUS. Therefore, the command ends
abnormally. paircreate, pairsplit 977b
When Snapshot P-VOL and Business Copy P-VOL share the volume, the status
of the Business Copy pair is other than PSUS or PSUE. Therefore, the Snapshot
pair cannot be restored. pairresync -restore 977c
When Snapshot P-VOL and Business Copy S-VOL share the volume, the status
of the Business Copy pair is other than PSUS. Therefore, the Snapshot pair cannot
be restored. pairresync -restore 977d
Since the pool or the pool-VOL is blocked, the Snapshot data cannot be stored. pairsplit 977e
The Snapshot pair cannot be restored for any of the following reasons: pairresync -restore 9783
• The Snapshot data of the Snapshot pair for restoration is being stored per
consistency group.
•
The P-VOL of the Snapshot pair for restoration is used as the P-VOL of another
Snapshot pair, and the Snapshot data of the latter Snapshot pair is being
stored per consistency group.
Troubleshooting with RAID Manager 51