Displaying Snapshot Configuration and Status

To display information about a volume’s snapshots, click:

Volumes > volume_name > Snapshots tab

The Volume Snapshots window appears (Figure 3: Volume Snapshots ).

Figure 3: Volume Snapshots

In the far left panel, snapshots appear under the volume name and are identified by the date and time when the snapshot was created.

The Snapshot Summary panel shows details about the volume’s snapshot configuration, including the snapshot settings, the amount of free snapshot reserve, and any snapshot schedules for the volume.

Note: If snapshot reserve is low, consider increasing the size of the reserve, as described in Modifying Snapshot Settings. If the snapshot reserve is exceeded, the snapshot space recovery policy will be enforced.

The Snapshots panel shows details about each snapshot, including the date and time it was created, whether the snapshot is part of a snapshot collection, whether the snapshot was created from a schedule, the current status, permission, and iSCSI connections.

Select a snapshot in the Snapshots panel to display related tasks in the Activities panel. For example, you can modify snapshot properties (name, description, or alias), clone the snapshot, set the snapshot online or offline, set the snapshot permission, or delete the snapshot.

Place the mouse over a snapshot to display a pop-up message displaying both the current snapshot status and the requested snapshot status. The requested status is set by an administrator and described in Table 1: Requested Snapshot Status.The Status column in the Volume Snapshots window displays the current snapshot status, as described in Table 2: Current Snapshot Status.

Table 1: Requested Snapshot Status

Status

Description

online

Administrator set the snapshot online. Authorized hosts can access the snapshot.

offline

Administrator set the snapshot offline. Hosts cannot access the snapshot.

online-no-space

Administrator set the snapshot offline, despite lost blocks.

Authorized hosts can access the snapshot. If an application attempts to read a lost block, an error will occur. If the block is rewritten, no error will occur, and the block will no longer be marked lost.

Table 2: Current Snapshot Status

Status

Description

online

Administrator set the snapshot online. Authorized hosts can access the snapshot, and no failures have occurred. Online snapshots appear in the far left panel in black text.

offline

Administrator set the snapshot offline. Hosts cannot access the snapshot, but no failures have occurred. Offline snapshots appear in the far left panel in gray text.

offline-lost-blocks

Snapshot was automatically set offline because lost blocks have occurred. Hosts cannot access the snapshot.

Note: To correct this condition, click the requested status link and choose how to handle the lost blocks. See Handling Lost Blocks for more information.

offline-inconsistent

Snapshot was automatically set offline due to data inconsistencies. Contact your array support provider for information on how to proceed.

offline-member-down

Snapshot was automatically set offline because a member that contains snapshot data is down or cannot be accessed by the other members over the network. Hosts cannot access the snapshot.

Note: To correct this condition, fix the problem that caused the member to go down or become unreachable on the network.

offline-nospace-auto-grow

Volume reserve was consumed, and the thin provisioned volume and its snapshots were set offline because there was not enough free pool space for the volume reserve to grow.

Note: To correct this condition, add more space to the pool (such as by adding another member to the pool).

offline-snap-reserve-met

Snapshot was automatically set offline because the reserved snapshot space has been exceeded and the snapshot recovery policy dictates that the snapshots be set offline. Hosts cannot access the snapshot.

Note: To correct this condition, increase the amount of reserved snapshot space.

offline-thin-max-grow-met

Thin-provisioned volume and its snapshots were set offline because in-use space reached the maximum allowed.

Note: To correct this condition, increase the value of the maximum in-use space for the volume or increase the volume size, as described in Modifying Volume Settings.

Note: If a snapshot is offline but it was set online by an administrator, ensure that all members that contain snapshot and volume data are online. Also, check the volume status. If a volume is offline but was set online by an administrator, all its snapshots will be set offline.

To display snapshot details, click:

Volumes > volume_name > snapshot_timestamp > Status tab

The Snapshot Status window appears (Figure 4: Snapshot Status ).

Figure 4: Snapshot Status

The Snapshot Status window displays details about the snapshot, including whether the snapshot was created from a volume collection or schedule, the current iSCSI connections, and the iSCSI target name. The Activities panel shows snapshot-related tasks.

If the snapshot belongs to a snapshot collection, click View snapshot collection to display details of the snapshot collection (Figure 14: Volume Collection - Snapshot Collection and Figure 15: Custom Snapshot Collection ).

Click the Access tab to display the Snapshot Access window (Figure 5: Snapshot Access ), which shows the access control records for the snapshot and its base volume. A host must exactly match one of the access control records in order to access the snapshot.

Figure 5: Snapshot Access

Select a record in the Access Control List panel to display details. See Managing Access Controls for Volumes and Snapshots for more information.