Capacity saving storage planning considerations

Provisioning Guide for VSP One Block

Version
10.2.x
Audience
anonymous
Part Number
MK-23VSP1B012-00

Review this table for information about settings, configuration, and performance considerations when using capacity saving.

Category Item Remarks
Setting Capacity saving setting Determine the capacity saving function to use by using the capacity saving rate (%) that is estimated by the Data Reduction Estimation Tool or by guessing at the capacity saving rate (%).
Configuration Capacity of a DRD-VOL whose capacity saving setting is enabled Estimate the number and capacity of the V-VOLs to be provided to the host. If the number of V-VOLs is small, the following performances might not be obtained.
  • Host I/O
  • Capacity saving processing for the initial data in the post-process mode
  • Garbage collection
  • Data migration in the inline mode
  • Disabling the capacity saving setting
  • Formatting an LDEV
  • Converting LDEV data compression

    The transition from data compression with software to data compression with compression accelerator, or from data compression with compression accelerator to data compression with software is enabled on VSP One B26 and VSP One B28.

  • Initial copy operation
Number of DDP groups Determine the number of DDP groups when designing a pool. If you consider the number of DDP groups, these cases can be considered:
  • The capacity, alone
  • The capacity and performance

For details, contact customer support.

Cache memory capacity Determine the cache memory capacity to be installed based on the total used DRD-VOL capacity.

For details, contact customer support.

Shared memory capacity Determine the shared memory capacity to be installed based on the total used DRD-VOL capacity.

For details, contact customer support.

Performance Estimated performance value Estimate the average write throughput in a customer use case and confirm that garbage data does not keep increasing with the workload. For the average write throughput, estimate the write throughput in the operation cycle (1 day to 1 week, for example). If garbage data increases constantly, the capacity saving function cannot be applied.