
NUM_LDEV : 1
LDEVs : 640
NUM_PORT : 1
PORTs : CL2-E-0 14 Linux_X86
F_POOLID : NONE
VOL_ATTR : CVS : VVOL : QS
:
TIER_Alloc_level : H
TIER#1_Alloc_rate : MAX : 50 : MIN : 30
TIER#3_Alloc_rate : MAX : 50 : MIN : 30
Snap_Used_Pool(MB) : 2181
For more information about the
raidcom
command, see the
HPE XP Storage RAID Manager Reference
Guide
.
Maintaining pairs during storage system maintenance
Switching off the power supply
1.
Stop the host I/O.
2.
Switch off the power supply.
When power is restored, the behavior of Fast Snap depends on the following:
• The power supply and having data in shared memory.
• The power supply and losing data in shared memory.
More information
Creating Fast Snap data pools on page 89
Creating Fast Snap pairs using Remote Web Console on page 114
Power supply and existing shared memory
The storage system checks the status of the pool and pool-VOLs. If the pool-VOLs are blocked at the
time you switch off the power supply, the pool is blocked and the pairs are suspended ("PSUE" status).
If you interrupt the workflow of storing snapshot data or cloning pairs by consistency groups by switching
off the power supply and the status of all the pairs in a consistency group has not completely changed,
the workflow does not resume when you switch the power supply on again. The status of some pairs may
remain unchanged.
If the pool is blocked and the pairs are suspended, complete the following:
1.
Restore the power.
2.
Recover the pools.
More information
Recovering blocked pools on page 169
176
Maintaining pairs during storage system maintenance
Summary of Contents for HPE XP7
Page 7: ...Documentation feedback 311 Contents 7...
Page 24: ...24 Overview of Fast Snap...
Page 109: ...2 In the Replication window click Edit Options Local Replication Configuring Fast Snap 109...
Page 186: ...186 Troubleshooting Fast Snap...
Page 187: ...Troubleshooting Fast Snap 187...
Page 214: ...The following table lists the items on this tab 214 Fast Snap GUI windows and wizards...