This capacity indicates the pool capacity which is used as snapshot data
stored from the P-VOL, but it does not include all of the information required
to manage snapshot data. Although snapshot data is assigned from the pool
in 42 MB blocks, Thin Image stores snapshot data from a P-VOL in 256 KB
blocks. Therefore, the snapshot data capacity is not always consistent with
each pool’s used capacity.
The following example shows how to use the raidcom command to view
snapshot data capacity.
#raidcom get ldev -ldev_id 640
Serial# : 63502
LDEV : 640
SL : 0
CL : 0
VOL_TYPE : OPEN-V-CVS
VOL_Capacity(BLK) : 2181120
VOL_Capacity(cyl) : 22720
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 Command
Control Interface Command Reference.
Maintaining pairs during storage system maintenance
You can maintain pairs when you switch off the storage system power and
when you replace the microcode.
Switching off the power supply
Use this workflow to switch off the power supply.
1. Stop the host I/O.
2. Switch off the power supply.
When power is restored, the behavior of Thin Image depends on the
following:
• The power supply and having data in shared memory.
• The power supply and losing data in shared memory.
Monitoring and maintaining Thin Image 193
Hitachi Thin Image User Guide for Hitachi Virtual Storage Platform G Series and F Series
To Next Page
Loading...
Need help?
General