Changing the modification priority of a disk pool – Dell POWERVAULT MD3600I User Manual

Page 102

Advertising
background image

Changing The Modification Priority Of A Disk Pool

Use the Modification Priority option to specify the priority levels for modification operations in a disk pool relative to the

system performance.

NOTE: Selecting higher priority for modification operations in a disk pool can slow the system performance.

The following are the priority levels to modify a disk pool:

Degraded Reconstruction Priority — The degraded reconstruction priority level determines the priority of the

data reconstruction operation when a single physical disk fails in a disk pool.

Critical Reconstruction Priority — The critical reconstruction priority level determines the priority of the data

reconstruction operation when at least two physical disks fail in a disk pool.

Background Operation Priority — The background operation priority level determines the priority of the disk pool

background operations, such as Virtual Disk Expansion (VDE) and Instant Availability Format (IAF).

To configure alert notifications for a disk pool:

1.

In the AMW, select the Storage & Copy Services tab.

2.

Select the disk pool.

3.

From the menu bar, select Storage → Disk Pool → Change → Settings.
The Change Disk Pool Settings dialog is displayed.

4.

In the Modification Priorities area, move the slider bars to select a priority level.
You can choose a priority level for:

– Degraded reconstruction
– Critical reconstruction
– Background operation

You can select one of the following priority levels:

– lowest
– low
– medium
– high
– highest

The higher the priority level, the larger is the impact on host I/O and system performance.

Changing The RAID Controller Module Ownership Of A Disk Pool

You can change the RAID controller module ownership of a disk pool to specify which RAID controller module must own

all of the virtual disks in the disk pool.

Changing the RAID controller module ownership at the disk pool level causes each virtual disk in that disk pool to
transfer to the other RAID controller module and use a new I/O path. If you do not want to set each virtual disk to the
new path, change the RAID controller module ownership at the virtual disk level instead of the disk pool level.

CAUTION: Possible loss of data access – If you change the RAID controller module ownership while an application
is accessing the virtual disks in the disk pool, it may result in I/O errors. Make sure that the application is not
accessing the virtual disks, and there is a multi-path driver installed on the hosts before you perform this
procedure.

102

Advertising