Obtaining a list of S-VOL information for the volume

Virtual Storage Platform One SDS Block Virtual Private Storage Administrator Guide

Version
1.15.x
Audience
anonymous
Part Number
MK-24VSP1SDS003-02

The following information can be obtained.

  • snapshotVolumeId: Volume ID (uuid) of the S-VOL

  • snapshotVolumeName: Name of the S-VOL

  • snapshotVolumeNickname: Nickname of the S-VOL

  • statusSummary: Status summary of the S-VOL

  • status: Volume status

  • snapshotStatus: Snapshot status

    It might take about one minute for snapshotStatus to transit. To confirm the transition of snapshotStatus, wait about one minute and then check again.

  • snapshotProgressRate: Progress rate of preparation for taking snapshots of, deleting, and restoring the S-VOL [%]

  • snapshotTimestamp: Time when recording of difference data started for the P-VOL at the time of snapshot creation

  • snapshotType: Snapshot type

  • snapshotConcordanceRate: Match rate between the volume and one newer generation of S-VOL or copy-source volume (P-VOL) [%]

  • isWrittenInSvol: Whether the volume has been written from the compute node (host)

  • vpsId: ID of the VPS to which the S-VOL belongs

  • vpsName: Name of the VPS to which the S-VOL belongs

  • qosParam: QoS-related parameter

    • upperLimitForIops: Upper limit for volume performance [IOPS]

    • upperLimitForTransferRate: Upper limit for volume performance [MiB/sec]

    • upperAlertAllowableTime: Alert threshold value for the upper limit of volume performance [sec]

    • upperAlertTime: The last time the upper limit of volume performance was continuously exceeded and the conditions for the alert threshold of the performance upper limit were met (UTC)

Note:

The matching rate of the S-VOL is handled as follows. Whether the generation is older or newer can be verified from snapshotTimestamp.

  • snapshotConcordanceRate [%] for the newest generation (S-VOL1) is the rate of matching with the P-VOL.

  • snapshotConcordanceRate [%] for the S-VOL2 is the rate of matching with the S-VOL3, which is one generation newer than the S-VOL2.

  • snapshotConcordanceRate [%] for the S-VOL3 is the rate of matching with the S-VOL1, which is one generation newer than the S-VOL3.

When data is written to the P-VOL, the matching rate of the S-VOL1 (newest generation) seemingly decreases because the data written to the P-VOL is assumed to be differential data. If data is written to an S-VOL, the matching rate of only the S-VOL decreases.

  • Required role: VpsSecurity, VpsStorage, or VpsMonitor

  1. Verify the volume ID of the P-VOL that is the source of the intended S-VOL.

    If you use the CLI to specify a volume by name, check the name of the volume.

    REST API: GET /v1/objects/volumes

    CLI: volume_list

  2. Obtain a list of S-VOL information.

    Run either of the following commands with the P-VOL volume ID specified.

    If you use the CLI, you can specify a name instead of the ID of the volume.

    REST API: GET /v1/objects/volumes/<id>/snapshot-volumes

    CLI: snapshot_volume_list

    Note:

    If the storage cluster stops while snapshot volumes are being deleted or restored, the delete or restore job disappears due to interruption or failure. As a result, the storage cluster stops. When you restart the storage cluster, the delete or restore operation will be automatically resumed.

    To verify the status of deleting or restoring snapshot volumes, obtain the volume information and verify snapshotStatus. When the delete operation ends, snapshotStatus changes to "Empty". When the restore operation ends, it changes to "Prepared".

    Note that the S-VOLs remain even if the snapshot volume is deleted and snapshotStatus is changed to "Empty" by the resumed delete operation (Automatic deletion does not take place if the storage cluster stops.). To delete the S-VOLs, run the snapshot deletion command again.