Data Container Volume Diagnosis
Overview
If pinned data or bad sectors are created in the Data Container Volume where the Deduplication/Compression control information is stored, multiple Deduplication/Compression Volumes may be broken.
This function extracts broken Deduplication/Compression Volumes from pinned data or bad sectors of Data Container Volumes.
This function is displayed only when the Deduplication/Compression function for the storage system is enabled. Refer to the [Set Deduplication/Compression Mode] function for details.
This function can only be performed on one volume at a time.
- To use this function, the following operations must be performed for all Deduplication/Compression Volumes in the TPP to which the diagnosis target volume belongs.
Stop I/O for the relevant volumes.
Stop or suspend the Advanced Copy session for the relevant volumes.
This function cannot be performed when the diagnosis target volume is in the "Readying", "Not Ready", "Broken", or "Data Lost" state.
- Pinned data and bad sectors cannot be checked at the same time. Refer to "Flow of the Data Container Volume diagnosis" for details.
If this function is started in the [Pinned Data] screen or the [Pinned Data] tab, a check for broken data due to pinned data starts. Refer to the [Pinned Data] function for details.
If this function is started in the [Bad Sector] screen, a check for broken data due to bad sectors starts. Refer to the [Bad Sector] function for details.
- If pinned data or bad sectors are created, recover the Deduplication/Compression Volumes using the following procedure.
Use this function to extract the broken Deduplication/Compression Volumes.
Format all the broken Deduplication/Compression Volumes that were extracted in Step 1.
If backup data exist, restore the backup data to the relevant Deduplication/Compression Volumes.
After the diagnosis is complete, click the [Restart] button to return to the [Start Deduplication/Compression Data] screen. When the diagnosis is restarted, if no error occurs in the relevant volume, a message to that effect appears. Click the [Done] button to return to the screen when starting this function.
|
|---|
The procedures described below show the flow of the diagnosis when pinned data or bad sectors are created in the Data Container Volumes. A diagnosis must be performed for each factor (pinned data or bad sectors) and for each volume.
|
User Privileges
Availability of Executions in the Default Role
| Default role | Availability of executions |
|---|---|
| Monitor | |
| Admin | |
| StorageAdmin | |
| AccountAdmin | |
| SecurityAdmin | |
| Maintainer |
Refer to "User Roles and Policies" for details on the policies and roles.
Display Contents
[Start Data Container Volume Diagnosis] Screen
Target Volume
| Item | Description |
|---|---|
|
No. |
The volume number of the target volume is displayed. |
|
Name |
The name of the target volume is displayed. $DATA_CNTNRx x: TPP number |
|
Type |
The type for the target volume is displayed. TPV |
[Data Container Volume Diagnosis Progress] Screen or [Data Container Volume Diagnosis Complete] Screen
Target Volume
| Item | Description |
|---|---|
|
No. |
The volume number of the target volume is displayed. If the volume is waiting for the diagnosis to start or an error is detected, a "-" (hyphen) is displayed. |
|
Name |
The name of the target volume is displayed. If the volume is waiting for the diagnosis to start or an error is detected, a "-" (hyphen) is displayed. $DATA_CNTNRx x: TPP number |
|
Type |
The type for the target volume is displayed. If the volume is waiting for the diagnosis to start or an error is detected, a "-" (hyphen) is displayed. TPV |
|
Process |
The diagnosis status of the target volume is displayed. Click the [Reload] button to update the diagnosis status. If the volume is waiting for the diagnosis to start or an error is detected, a "-" (hyphen) is displayed. Diagnosing Complete Error End |
|
Progress |
The progress (0 to 100 %) of the diagnosis for the target volume is displayed. Click the [Reload] button to update the progress rate. If the volume is waiting for the diagnosis to start or an error is detected, a "-" (hyphen) is displayed. |
|
Completion Time |
The completion time (YYYY-MM-DD hh:mm:ss) of the diagnosis for the target volume is displayed. Click the [Reload] button to update the completion time. When the volume is waiting for the diagnosis to start, when the volume is being diagnosed, or when an error is detected, a "-" (hyphen) is displayed. |
Broken Deduplication/Compression Volume List
| Item | Description |
|---|---|
|
No. |
The volume number of the broken Deduplication/Compression Volume is displayed. |
|
Name |
The volume name of the broken Deduplication/Compression Volume is displayed. |
Operating Procedures
When Starting a Diagnosis
Select the Data Container Volume that is to be diagnosed and click [Data Container Volume Diagnosis] in [Action].
→ The [Start Data Container Volume Diagnosis] Screen appears.
Click the [Start] button.
→ A confirmation screen appears.
Caution- An error occurs in the following conditions:
Multiple bad sectors have independently occurred in the target volume
The number of pinned data in the target volume exceeds the maximum recoverable number
- An error occurs in the following conditions:
Click the [OK] button.
→ The Data Container Volume diagnosis starts.
Click the [Done] button to return to the screen when starting this function in Step 1.
NoteSelect the diagnosis target volume again and click [Data Container Volume Diagnosis] in [Action] to check the diagnosis progress.
When Checking the Progress of the Diagnosis and the Results of the Diagnosis
Select the Data Container Volume that is being diagnosed and click [Data Container Volume Diagnosis] in [Action].
The displayed screen varies depending on the Data Container Volume diagnosis progress.
When the Data Container Volume diagnosis is being performed
→ The [Data Container Volume Diagnosis Progress] Screen or [Data Container Volume Diagnosis Complete] Screen appears. Proceed to Step 2.
When the Data Container Volume diagnosis is completed
→ The [Data Container Volume Diagnosis Progress] Screen or [Data Container Volume Diagnosis Complete] Screen appears. Proceed to Step 3.
Caution- When selecting the Data Container Volume that is not being diagnosed and clicking [Data Container Volume Diagnosis] in [Action], the following screen appears.
When the Data Container Volume diagnosis is being performed, the [Diagnosing Data Container Volume] screen appears. Click the [OK] button to return to the screen when starting this function in Step 1. A diagnosis is performed one volume at a time.
When the Data Container Volume diagnosis has already been completed, the [Start Data Container Volume Diagnosis] Screen appears. Click the [Start] button to start the Data Container Volume diagnosis for the specified volume.
Click the [Reload] button to display the latest progress state.
The displayed screen varies depending on the Data Container Volume diagnosis progress.
When the Data Container Volume diagnosis is being performed
→ The [Data Container Volume Diagnosis Progress] Screen or [Data Container Volume Diagnosis Complete] Screen appears. Click the [Reload] button to display the latest progress state.
When the Data Container Volume diagnosis is completed
→ The [Data Container Volume Diagnosis Progress] Screen or [Data Container Volume Diagnosis Complete] Screen appears. Proceed to Step 3.
Caution- An error occurs in the following conditions:
Multiple bad sectors have independently occurred in the target volume
The number of pinned data in the target volume exceeds the maximum recoverable number
NoteIf the [OK] button is clicked when a diagnosis is being performed, the screen returns to the screen when starting this function in Step 1.
Click the [Done] button to return to the screen when starting this function in Step 1.
NoteAfter the diagnosis is completed, click the [Restart] button to display the [Start Data Container Volume Diagnosis] Screen.