Seagate ST3250824NS Manuel d'utilisateur télécharger pdf (Page 22)

22 R/Evolution Storage System Release Notes • December 2006

All snap pools include a 526 Mbyte reserve for internal use. This reserve space

guarantees that there is enough space to store pending data.

For example:

minimum snap-pool size = 1Gbyte

snap-pool reserve = 526 Mbyte

space available = 474 Mbyte

In this example, all threshold percentages are based on the space available of 474

Mbyte. The default error-level threshold of 90 percent will cause the corresponding

error policy to trigger at 426 Mbyte.

For larger snap pool volumes, the impact of this reserve space is less noticeable.

■ For a 10-Gbyte snap pool, the 90 percent trigger would occur at 8.6 Gbyte.

■ For a 100-Gbyte snap pool, the 90 percent trigger would occur at 89.5 Gbyte.

Failover and Snap Pools

The master volume and its snap pool must be owned by the same controller.

When you create a master volume in dual-controller mode, RAIDar shows only snap

pools owned by the same controller for you to select. So you cannot see or wrongly

select the snap pool owned by the other controller.

Now assume B goes offline and A takes control of B's resources.

While failed-over (i.e., in single-controller mode), RAIDar shows snap pools owned

by A and B. Because the page doesn't show ownership, it is possible to select a snap

pool owned by the "wrong" controller causing the error "Specified virtual

disks/volumes are not on the same controller. "193"" to display.

In order to work around this, when one of the controllers has failed, change the

owner of the vdisks such that they are owned by the remaining controller.

From RAIDar, select:

Manage > Virtual Disk Config > Vdisk Configuration > Change Vdisk Owner

From the CLI, use the

set vdisk command.

1 2 ... 17 18 19 20 21 22 23 24 25 26 27 28

Pas de commentaire

Seagate ST3250824NS Manuel d'utilisateur Page 22