Dell VNX8000 VNX2 Deduplication and Compression - Maximizing effective capacit - Page 26

Mapped Storage Pool Properties Window.,

Page 26 highlights

Figure 18. Mapped Storage Pool Properties Window. After enabling or disabling VNX Block Deduplication, a migration into or out of the deduplication container begins. To view which LUNs are migrating, view the LUNs within the Block Storage Pool, as shown in Figure 19. If the Deduplication column is not shown, click the wrench icon in the LUNs window and select Choose Columns. Also shown in Figure 19 is a single LUN which is enabling Block Deduplication. In this example, VNX Block Deduplication should be enabling on all 10 LUNs within the Storage Pool based on their usage within the Mapped Storage Pool. However, due to the minimal Free Capacity within this Block Storage Pool, only 1 enabling process was allowed to start. When enabling VNX Block Deduplication each migration requires free space greater than 110% of the consumed capacity of the original LUN. Once the migration completes, the source LUN is deleted and space is freed back to the Storage Pool. VNX Block Deduplication for VNX File contains an internal process which checks the Fixed-Block Deduplication states every 30 minutes. During this process, all back-end storage resources are also checked for consistency with the current state. If a backend LUN is in the wrong deduplication state, the state will be corrected, which will require an enabling or disabling process to start. EMC VNX2 Deduplication and Compression 26

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55

26
EMC VNX2 Deduplication and Compression
Figure 18. Mapped Storage Pool Properties Window.
After enabling or disabling VNX Block Deduplication, a migration into or out of the
deduplication container begins. To view which LUNs are migrating, view the LUNs
within the Block Storage Pool, as shown in
Figure 19
. If the Deduplication column is
not shown, click the wrench icon in the LUNs window and select Choose Columns.
Also shown in
Figure 19
is a single LUN which is enabling Block Deduplication. In this
example, VNX Block Deduplication should be enabling on all 10 LUNs within the
Storage Pool based on their usage within the Mapped Storage Pool. However, due to
the minimal Free Capacity within this Block Storage Pool, only 1 enabling process was
allowed to start. When enabling VNX Block Deduplication each migration requires free
space greater than 110% of the consumed capacity of the original LUN. Once the
migration completes, the source LUN is deleted and space is freed back to the
Storage Pool.
VNX Block Deduplication for VNX File contains an internal process which checks the
Fixed-Block Deduplication states every 30 minutes. During this process, all back-end
storage resources are also checked for consistency with the current state. If a back-
end LUN is in the wrong deduplication state, the state will be corrected, which will
require an enabling or disabling process to start.