Preparing to initialize duplicated data

The Initialize Duplicated Data function initializes the status of the capacity saving function for a pool. You can implement it by using Device Manager - Storage Navigator or RAID Manager.

When the Initialize Duplicated Data function is used, data in a DRD-VOL that has duplicate data in the pool is forcibly discarded.

Before using Initialize Duplicated Data, check and complete the following, as necessary:

  • Back up necessary data
  • Recover pools in the event of a RAID level failure (Drive failure exceeding drive redundancy)
  • Initialize after shared memory data volatilization has been caused by a forced power outage
The following table lists the requirements for using Initialize Duplicated Data.

Item Specification
Specified range Per pool
Target DRD-VOL whose capacity saving setting is Deduplication and Compression* and deduplication system data volume (both fingerprint and data store) that belong to the specified pool
Volume status after initializing duplicated data
  • The deduplication system data volume (fingerprint) that was blocked before initializing duplicated data changes to normal status.
  • DRD-VOL and deduplication system data volume (data store) that were blocked before initializing duplicated data remain blocked. To restore them to the normal status, perform LDEV format.
Execution time

It takes one minute per total capacity 40 TB of the target volumes.

Execution time = 5[min.] + ↑(Total capacity [TB]/40[TB])↑

↑()↑: The value enclosed in ↑()↑ must be rounded up to the nearest whole number.

(Example) When the capacity is 100 TB, the execution time is calculated as follows: 5+↑(100/40)↑ = 5+↑2.5↑= 8[min.]

*To initialize DRD-VOLs for which the capacity saving settings are “Deduplication and Compression” and “Compression”, you must set the system option mode 1115 to ON in advance. For details about system option modes, contact customer support.
NoteWhen issues occur while DRD-VOLs are being used, you can resolve them by following the solutions for SIM or messages. For troubleshooting, see Troubleshooting Dynamic Provisioning.