Snapshot Status

The general snapshot status and the current snapshot operation status are displayed in the management console.

General Snapshot Status

Snapshot status is displayed:

Snapshot Status

Aborted

Either the Promote to Full or Update Source snapshot operation has been aborted.

Failed

A general failure has occurred with an active snapshot.

When a snapshot is failed, no access is allowed to the virtual disk storage source on the snapshot side. Host and mirror access, as well as replication traffic to the snapshot side will be blocked. If this is the case, either the snapshot issue needs to be resolved or the snapshot must be deleted so that all access will be enabled and mirrors can recover.

Failed reading from source

A failure has occurred when trying to read from the source virtual disk.

Failed reading from snapshot

A failure has occurred when trying to read from the snapshot virtual disk.

Failed reading from mapstore

A failure has occurred when trying to read from the repository of snapshot maps (failed activation).

Failed restoration

A failure occurred when trying to access the repository of snapshot maps (mapstore).

Failed writing to source

A failure has occurred when trying to write to the source virtual disk.

Failed writing to snapshot

A failure has occurred when trying to write to the snapshot virtual disk.

Healthy

The snapshot is in a healthy state.

Inaccessible

The snapshot is temporarily unavailable while the source is in a failed redundancy state.

Not present

The snapshot exists in the configuration, but actions cannot be performed. This status could appear if a server has missing back-end physical disks; specifically, if the mapstore source or destination storage sources are unavailable.

When the snapshot is not present, the system will take the source and destination virtual disks offline. There are two ways to correct this snapshot status:

  1. restore the missing back-end disks and stop and restart the server,
    or
  2. delete the snapshot.

Out of memory

Available memory was insufficient to perform the snapshot operation.

Shutdown dirty

Server has recovered from an unexpected shutdown without saving the snapshot. Differential snapshots will be failed.

If the state of a full snapshot cannot be determined, those snapshots may also be failed, however it is possible for data to be valid.

Check snapshot data to determine validity - use with caution.

Stopped

The snapshot is in stopped state. The server on which the snapshot is taken is deactivated or not active.

Operation Status

Operation status is displayed:

  • In the Snapshot Details page under the icon when an operation is active, otherwise the general status is displayed.
  • In the Operation column in the Virtual Disk Details page>Snapshots tab when an operation is active, otherwise the snapshot is idle and the field is empty.
  • In the Status column in the Virtual Disk List when an operation is active, otherwise the general status is displayed.
Snapshot Operation Status

Aborting...

The active operation is in the process of being aborted.

Deleting...

The snapshot is in the process of being deleted.

Cloning...

This state occurs when a full snapshot is created or updated, or when a differential snapshot is being promoted to a full snapshot.

Creating snapshot...

This state occurs when a differential snapshot is created or updated.

Reverting...

The snapshot is in the process of reverting from the snapshot (the source virtual disk is becoming a copy of the current state of the snapshot).