Seagate ST3250824NS Instrukcja Użytkownika Pobierz pdf (Strona 21)

Release Notes 21

Known Issues

The following sections describe known issues for this release:

■ “Snapshot Known Issues” on page 21

■ “MPIO” on page 23

■ “Documentation Issues” on page 23

■ “Known Bugs” on page 24

Snapshot Known Issues

There are three issues with snapshots that can cause confusion for users.

Duplicate Snapshot Names

You can create snapshots with the same name as another volume. While the second

snapshot will be created and I/O directed properly, it is advisable to name snapshot

volumes with array-wide unique names for manageability purposes.

If two volumes have the same name, rename one of the volumes as soon as possible.

If duplicate names must exist, do not rely on the volume names when performing

actions on those volumes.

From a manageability perspective, duplicate names can be an issue. Specifically:

■ From the CLI: The volume name must not be specified as the volume identifier

to any CLI command. Doing so can result in incorrect and irreversible issues,

such as deletion of the wrong volume.

■ From RAIDar: Verify that the volume being acted on is the correct volume. To do

this, check the vdisks on which the volume exists, volume size, type, creation

time, etc.

Policy Triggers

A snapshot policy might trigger before it appears that a specified threshold has been

reached. This is because a threshold percentage is based on the size of the snap pool

volume, less a fixed amount of reserve space.

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

Brak uwag

Seagate ST3250824NS Instrukcja Użytkownika Strona 21