Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Replicating data

You can perform backup of data in a storage system and restore it when a data failure occurs.

There are two types of backup: using snapshots or images of a volume, and copying or reusing data from volumes with Snap Clones.

Workflow for creating backup data using snapshots

To create backup data, you can add a snapshot of a volume. Snapshots are images of volumes at a specific point in time. Differential data from the original volume is stored in the pool when you create a snapshot. This section describes the workflows for creating a snapshot and restoring data.

GUID-17A73B17-B6EC-4472-A6FC-A2278482FAA7-low.gif

Schedule snapshot creation by using the REST API. You can also manually create a snapshot by using the web-based user interface.

Note

If you use the web-based user interface, the creation date and time for a snapshot is displayed based on the time zone set for the management client system. If you use the REST API, the data and time are returned based on Coordinated Universal Time (UTC).

You can use the Embedded CCI to schedule snapshots or to configure a consistency group, using the following commands: raidcom add snapshot, raidcom modify snapshot, raidcom delete snapshot.

You can also use the Embedded CCI to configure snapshots for Thin Image pools.

Workflow for replicating data by using Snap Clone

You can nondisruptively copy data from volumes to create copies for software testing or development and data protection operations.

GUID-75259699-5644-4041-B4A5-0AE701308A26-low.gif
Note

If you use the web-based user interface, the creation date and time for a snapshot is displayed based on the time zone set for the management client system. If you use the REST API, the data and time are returned based on Coordinated Universal Time (UTC).

Creating snapshots

You can create snapshots manually.

  1. In the dashboard or in the navigation bar, click Servers. If you are not using Storage Advisor Embedded to manage servers, click Volumes in the dashboard or in the navigation bar, and then skip to step 3.

  2. Click the server name to open the server details page.

  3. Select one or more volumes and click GUID-542988FC-7EB6-415E-8245-4CC7E5F003E7-low.gif (Create Snapshots).

    GUID-0A82BF8C-BC1C-4263-B1B8-4F0C96C45F92-low.png
  4. Specify the required information and then create the snapshots.

    Be sure to select a pool that has a sufficient amount of free space. The snapshots, including those that already exist, might become unusable if the pool usage rate exceeds the depletion threshold value.

    Differential data cannot be stored in a tiered pool.

Creating volumes by using Snap Clone

Using Snap Clone, you can create a clone of volumes for software testing or development and data protection operations.

Before you begin

  • Be sure to select a pool that has a sufficient amount of free space. The snapshots, including those that already exist, might become unusable if the pool usage rate exceeds the depletion threshold value.
  • You can not use a tiered pool for creating clone of volumes.

Procedure

  1. In the dashboard or in the navigation bar, click Servers. If you are not using Storage Advisor Embedded to manage servers, click Volumes in the dashboard or in the navigation bar, and then skip to step 3.

  2. Click the server name to open the details page.

  3. Select one or more volumes and click GUID-0FEB76FB-A3D1-4948-8D65-288BEBFAA172-low.gif (Create Volumes by Snap Clone).

    GUID-341D4A0F-31FD-4F42-BCA5-8B9026BD927A-low.png
  4. Specify the required information and then run Snap Clone.

Results

When the Snap Clone processing finishes, the volume is no longer displayed in the inventory of snapshots. The volumes created by Snap Clone are displayed in the inventory of volumes and can be used as normal volumes.

Volume names in the following format are automatically assigned to the newly created volumes: "Clone of ID: ID-of-volume-created-from-snapshot".

Checking snapshot and Snap Clone status

You can check the status of snapshots and of Snap Clone when the Health Status indicates that an error has occurred.

  1. In the dashboard or in the navigation bar, click Servers. If you are not using Storage Advisor Embedded to manage servers, click Volumes in the dashboard or in the navigation bar, and then skip to step 3.

  2. Click the server name to open the server details page.

  3. Click the volume name to open the volume details page.

  4. On the Snapshots tab, check the status of the snapshot or Snap Clone.

    GUID-ACF1C360-9251-4B44-B0D3-230A514BCAD5-low.gif

    The following provides a description for each type of snapshot status:

    Status

    Description

    Creating Creation of the snapshot settings is in progress.
    In Sync Snapshot synchronization or restoration is complete.
    Completed Snapshot creation is complete.
    Restoring Snapshot restoration is in progress.
    Deleting Snapshot settings and differential data deletion is in progress.
    Error A failure occurred.

    The following provides a description for each type of Snap clone and Diff Clone status:

    Status

    Description

    Preparing Creation of the Snap Clone settings is in progress.
    Clone Ready Snap Clone settings creation is complete.
    Cloning Replication by using Snap Clone is in progress.
    Diff Cloning Replication by using Diff Clone in the VASA environment is in progress.
    Removing Snap Clone settings removal is in progress.
    Error A failure occurred.

Restoring snapshots

In the event of data corruption, you can use the snapshots to restore the data of a specific volume to a specific point in time.

Procedure

  1. In the dashboard or in the navigation bar, click Servers. If you are not using Storage Advisor Embedded to manage servers, click Volumes in the dashboard or in the navigation bar, and then skip to step 3.

  2. Click the server name to open the server details page.

  3. Click the volume name to open the volume details page.

  4. On the Snapshots, display the inventory of snapshots, select the snapshot with date and time to restore, and then click GUID-C05A13D0-56C8-40EC-B82A-0249ECC1BA82-low.gif(Restore from Snapshot).

    GUID-E483DA4F-65CD-4A71-9F14-C0D48FFDEC69-low.gif

Results

The data is restored back to the state at the date and time when the snapshot was created.

You can check whether a volume is being restored by referring to the inventory of snapshots. When processing to restore a volume is complete, the status shows as In Sync.

Deleting snapshots

You can delete snapshots that are no longer necessary.

  1. In the dashboard or in the navigation bar, click Servers. If you are not using Storage Advisor Embedded to manage servers, click Volumes in the dashboard or in the navigation bar, and then skip to step 3.

  2. Click the server name to open the server details page.

  3. Click the volume name to open the volume details page.

  4. On the Snapshots, select one or more snapshots and click GUID-F074FA1A-3F5C-4AD5-A29C-48E36520F7C7-low.gif (Delete Snapshots).

Creating a snapshot

The following request creates a snapshot for backing up data or for re-purposing the backed up data. This request also allows you to clone a snapshot.

Execution permission

Storage Administrator (Local Copy)

Request line

POST base-URL/simple/v1/objects/snapshots
Request message
  • Object ID

    None.

  • Query parameters

    None.

  • Body

    The following is an example of cloning, in the pool with ID 13, a snapshot from the master volume (ID 100). In this example, a snapshot group (snapshot name: snapshotGroup) is also created at the same time.

    {
      "params": [
        {
          "masterVolumeId": 100,
          "poolId": 13,
          "snapshotGroupName": "snapshotGroup",
          "type": "Snap Clone"
        }
      ]
    }

    The following is an example of creating, in the pool with ID 13, a snapshot from the master volume (ID 100, snapshot group name: snapshotGroup):

    {
      "params": [
        {
          "masterVolumeId": 100,
          "poolId": 13,
          "snapshotGroupName": "snapshotGroup",
          "type": "Snapshot"
        }
      ]
    }

    The following is an example of creating, in the pool with ID 13, a snapshot from the master volume (ID 100, snapshot group name: snapshotGroup). In this example, the volume ID is also defined for the volume to create from the snapshot.

    {
      "params": [
        {
          "masterVolumeId": 100,
          "poolId": 13,
          "snapshotGroupName": "snapshotGroup",
          "type": "Mapped Snapshot"
        }
      ]
    }

    Attribute

    Type

    Description

    params

    object[]

    Information about a snapshot to create

    • masterVolumeId (int)

      (Required) Specify the ID of the master volume from which snapshots are created, as an integer from 0 through 65279.

    • poolId (int)

      (Required) Specify the ID of the pool in which the differential data of the snapshot is stored as an integer in the range from 0 through 127.

      If the usage rate of the pool exceeds the depletion threshold value, snapshots including the created snapshot might become unusable. Make sure that there is enough free space in the specified pool.

      Tiered pools cannot be specified.

      To check the usage rate of the pool and whether the pool has a tiered structure, execute the API function for getting information about a specific pool by specifying a pool ID.

    • snapshotGroupName (string)

      (Required) Specify a snapshot group name of up to 32 characters.

      You can use alphanumeric characters (0 through 9, A through Z, a through z), space characters, and the following symbols:

      Comma (,), hyphen (-), period (.), forward slash (/), colon (:), at sign (@), back slash (\), underscore (_)

      This attribute is case-sensitive.

      You can use a space character between characters, but cannot use it at the beginning or end of the snapshot group name.

      When getting detailed information or using an API request that supports changing the configuration (an API request that does not include simple in the request line), if the snapshot group name includes a space character, you cannot get snapshot group name and information about snapshots.

      You cannot use a hyphen (-) at the beginning of the snapshot group name.

      If you specify a new snapshot group name, a snapshot group of that name will be created when the request is executed.

    • type (string)

      (Required) Snapshot type:

      • Snap Clone: Create a volume by Snap Clone.
      • Snapshot: Create a snapshot.
      • Mapped Snapshot: Create a snapshot, and define a volume ID for the snapshot.

      If Snap Clone or Mapped Snapshot is specified for this attribute, a nickname is automatically assigned, in the following applicable format, to the volume that is created from the snapshot.

      • If Snap Clone is specified:

        "Clone of ID:ID-of-master-volume-created-from-snapshot"

      • If Mapped Snapshot is specified:

        "Snapshot of ID:ID-of-master-volume-created-from-snapshot"

    • destinationSize (int)

      (Optional) Specify the capacity of the volume for which the snapshot is created as an integer from 47 through 268435456.

      Specify a value greater than the capacity of the master volume from which the snapshot is created. You can specify this attribute only when Snap Clone is specified for the type attribute.

      If this attribute is omitted but Snap Clone is specified for the type attribute, a value equal to the capacity of the master volume from which the snapshot is created is assumed.

Response message
Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X POST --data-binary @./InputParameters.json https://192.0.2.100/ConfigurationManager/simple/v1/objects/snapshots

Getting snapshot information

The following request gets information about snapshots. You can specify filter conditions.

Execution permission

Storage Administrator (View Only)

Request line

GET base-URL/simple/v1/objects/snapshots
Request message
  • Object ID

    None.

  • Query parameters

    With each request, you can obtain information for a maximum of 1000 snapshots. To obtain information for more than 1000 snapshots, execute the API request several times by using a combination of the count and startId parameters. By specifying the count parameter, you can also filter the snapshot information.

    Parameter

    Type

    Filter Condition

    masterVolumeId

    int

    (Optional) Master volume ID of the snapshot

    snapshotDateFrom

    ISO8601string

    (Optional) Specify the date and time from which snapshots will be obtained, in YYYY-MM-DDThh:mm:ssZ format.

    Information about snapshots created on and after the date and time specified for this parameter will be obtained.

    snapshotDateTo

    ISO8601string

    (Optional) Specify the date and time until which snapshots will be obtained, in YYYY-MM-DDThh:mm:ssZ format.

    Information about snapshots created on and before the date and time specified for this parameter will be obtained.

    snapshotGroupName

    string

    (Optional) Snapshot group name

    Information about the snapshot that is a perfect match with the specified value is obtained.

    startId

    string

    (Optional) Specify the first snapshot information to obtain, by specifying the master volume ID of the snapshot and the snapshot ID, linked by a comma.

    masterVolumeId,snapshotId

    If this parameter is omitted, "0,0" is assumed.

    count

    int

    (Optional) Specify the number of snapshots by using a value in the range from 1 through 1000.

    If this parameter is omitted, 1000 is considered.

  • Body

    None.

Response message
  • Body

    {
      "data": [
        {
          "id": "100,3",
          "masterVolumeId": 100,
          "snapshotId": 3,
          "status": "Completed",
          "snapshotDate": "2015-03-20T09:27:35Z",
          "snapshotGroupName": "snapshotGroup",
          "rootVolumeId": 100,
          "type": "Snapshot",
          "poolId": 10,
          "usedCapacityPerRootVolume": 126,
          "isVolumeCapacityExpanding": false
        },
        {
          "id": "100,4",
          "masterVolumeId": 100,
          "snapshotId": 4,
          "status": "Completed",
          "snapshotDate": "2015-03-20T09:27:35Z",
          "snapshotGroupName": "snapshotGroup",
          "rootVolumeId": 100,
          "type": "Snapshot",
          "poolId": 10,
          "usedCapacityPerRootVolume": 126,
          "isVolumeCapacityExpanding": false
        },
      ],
      "count": 2,
      "totalCount": 2,
      "hasNext": false
    }

    Attribute

    Type

    Description

    id

    string

    Master volume ID of the snapshot and the snapshot ID, linked by a comma

    masterVolumeId

    int

    Master volume ID of the snapshot

    snapshotId

    int

    Snapshot ID

    The mirror unit number is obtained.

    status

    string

    Status of the snapshot:

    • Creating: Snapshot creation is in progress
    • In Sync: Snapshot synchronization is complete
    • Completed: Snapshot creation is complete
    • Deleting:Snapshot deletion is in progress
    • Restoring: Snapshot restoration is in progress
    • Preparing: Preparation for Snap Clone is in progress
    • Clone Ready: Snap Clone is ready
    • Cloning: Replication by using Snap Clone is in progress
    • Diff Cloning: Replication by using Diff Clone in the VASA environment is in progress
    • Removing: Removal of the Snap Clone settings is in progress
    • Error: A failure has occurred

    snapshotDate

    ISO8601string

    Date and time when the snapshot was created

    snapshotGroupName

    string

    Snapshot group name

    mappedVolumeId

    int

    ID of the volume to be created from the snapshots

    This attribute is obtained only if the ID of the volume for which the snapshot was created is defined.

    rootVolumeId

    int

    ID of the root volume of the snapshots

    poolId

    int

    ID of the pool in which the differential data of the snapshots is stored

    usedCapacityPerRootVolume

    long

    The amount of disk space (MiB) occupied by differential information and control information used by the snapshot group created from the same volume.

    isVolumeCapacityExpanding

    boolean

    Indicates whether the snapshot capacity is being expanded

    • true: Capacity expansion is in progress

      When a volume is mapped to the snapshot, true appears (indicating that processing to expand the capacity is occurring) if the capacity of the volume from which the snapshot was created differs from the capacity of the volume to which the snapshot is mapped.

      When no volume is mapped to the snapshot, true appears (indicating that processing to expand the capacity is occurring) only if processing is expanding the capacity of the volume from which the snapshot was created.

    • false: Capacity expansion is not occurring

    type

    string

    Type of snapshot:

    • Snap Clone: Snap Clone replication is in progress
    • Snapshot: A snapshot or volume ID is defined for the snapshot
    • Diff Clone: Diff Clone replication in the VASA environment is in progress (VSP G130, G/F350, G/F370, G/F700, G/F900 models only)

    diffCompareVolumeId

    int

    Volume ID of the base volume that is used when creating a Diff Clone

    The attribute type appears only for Diff Clone.

Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X GET https://192.0.2.100/ConfigurationManager/simple/v1/objects/snapshots

Mapping a snapshot

The following request maps snapshots based on the specified master volume ID of the snapshot and the specified snapshot ID. Mapping a snapshot enables you to use the volume created from the specified snapshot.

Execution permission

Storage Administrator (Local Copy)

Request line

POST base-URL/simple/v1/objects/snapshots/object-ID/actions/map/invoke
Request message
  • Object ID

    Specify the id value obtained by getting snapshot information. The value of the id attribute is obtained in the following format, where the master volume ID of the snapshot and the snapshot ID are linked by a comma. You can specify these values (obtained by getting snapshot information) in the command by using the same format: masterVolumeId followed by snapshotId, linked by a comma.

    masterVolumeId,snapshotId

    Attribute

    Type

    Description

    masterVolumeId

    int

    (Required) Master volume ID of the snapshot

    snapshotId

    int

    (Required) Snapshot ID

  • Query parameters

    None.

  • Body

    {
      "poolId": 13
    }

    Attribute

    Type

    Description

    poolId

    int

    (Required) Specify the ID of the pool in which the volume to which snapshots are mapped as an integer in the range from 0 through 127.

    Note

    When snapshots are mapped, nicknames in the following format are automatically assigned to the volumes created from the snapshots:

    "Snapshot of ID:ID-of-master-volume-created-from-snapshot"

Response message
Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X POST --data-binary @./InputParameters.json https://192.0.2.100/ConfigurationManager/simple/v1/objects/snapshots/100,3/actions/mount/invoke

Getting the operating status of snapshots and pools

The following request gets status information about pools and snapshots, and enables you to check the operating status of storage resources.

Execution permission

Storage Administrator (View Only)

Request line

GET base-URL/simple/v1/objects/health-status
Request message
  • Object ID

    None.

  • Query parameters

    None.

  • Body

    None.

Response message
  • Body

    {
      "poolStatus":{
        "summary":"PartiallyBlocked",
        "abnormalItems":[
          {
            "status":"PartiallyBlocked",
            "poolIds":[
              0
            ]
          },
          {
            "status":"ExceededThreshold",
            "poolIds":[
              0,77,39,26
            ]
          }
        ]
      },
      "snapshotStatus":{
        "summary":"Normal"
      }
    }

    Attribute

    Type

    Description

    poolStatus

    object

    Status of the pool:

    • summary (string)
      • Normal: All pools are normal.
      • ExceededThreshold: There is at least one pool where usage rate exceeds the threshold value.
      • PartiallyBlocked: There is at least one pool where some of the volumes that make up the pool are blocked.
      • Error: At least one pool is in the error status because it is full.
    • abnormalItems (object[])

      Information about abnormal pools:

      • status (string)

        - PartiallyBlocked: Some of the volumes that make up the pool are blocked.

        - ExceededThreshold: The pools where usage rate exceeds the threshold value.

        - Error: The pools that are in the error status because they are full.

      • poolIds (int[])

        Pool ID

    snapshotStatus

    object

    Status of the snapshot:

    • summary (string)
      • Normal: All snapshots are normal.
      • Error: There is at least one snapshot where an error occurred.
    • abnormalItems (object[])

      Information about abnormal snapshots:

      • status (string)

        - Error: Snapshots where an error occurred.

      • masterVolumeIds (int[])

        Master volume ID of the snapshot

Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X GET https://192.0.2.100/ConfigurationManager/simple/v1/objects/health-status

Restoring a snapshot

The following request restores snapshots based on the specified master volume ID of the snapshot and the specified snapshot ID. This request overwrites the data of the specified master volume.

Execution permission

Storage Administrator (Local Copy)

Request line

POST base-URL/simple/v1/objects/snapshots/object-ID/actions/restore/invoke
Request message
  • Object ID

    Specify the id value obtained by getting snapshot information. The value of the id attribute is obtained in the following format, where the master volume ID of the snapshot and the snapshot ID are linked by a comma. You can specify these values (obtained by getting snapshot information) in the command by using the same format: masterVolumeId followed by snapshotId, linked by a comma.

    masterVolumeId,snapshotId

    Attribute

    Type

    Description

    masterVolumeId

    int

    (Required) Master volume ID of the snapshot

    snapshotId

    int

    (Required) Snapshot ID

  • Query parameters

    None.

  • Body

    None.

Response message
Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X POST https://192.0.2.100/ConfigurationManager/simple/v1/objects/snapshots/100,3/actions/restore/invoke -d ""

Deleting a snapshot

The following request deletes a snapshot for the specified master volume ID of the snapshot and the specified snapshot ID.

Execution permission

Storage Administrator (Local Copy)

Request line

DELETE base-URL/simple/v1/objects/snapshots/object-ID
Request message
  • Object ID

    Specify the id value obtained by getting snapshot information. The value of the id attribute is obtained in the following format, where the master volume ID of the snapshot and the snapshot ID are linked by a comma. You can specify these values (obtained by getting snapshot information) in the command by using the same format: masterVolumeId followed by snapshotId, linked by a comma.

    masterVolumeId,snapshotId

    Attribute

    Type

    Description

    masterVolumeId

    int

    (Required) Master volume ID of the snapshot

    snapshotId

    int

    (Required) Snapshot ID

  • Query parameters

    None.

  • Body

    None.

Response message
Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X DELETE https://192.0.2.100/ConfigurationManager/simple/v1/objects/snapshots/100,3

Getting a list of snapshot group names

The following request gets a list of snapshot group names.

Execution permission

Storage Administrator (View Only)

Request line

GET base-URL/simple/v1/objects/snapshot-groups
Request message
  • Object ID

    None.

  • Query parameters

    None.

  • Body

    None.

Response message
  • Body

    {
      "data": [
        {
          "name": "snapshotGroup"
        },
        {
          "name": "snapshotGroup2"
        }
      ],
      "count": 2
    }

    Attribute

    Type

    Description

    name

    string

    Snapshot group name

Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X GET https://192.0.2.100/ConfigurationManager/simple/v1/objects/snapshot-groups

Getting information about a specific snapshot group

The following request gets information about a snapshot group for the specified snapshot group name.

Execution permission

Storage Administrator (View Only)

Request line

GET base-URL/simple/v1/objects/snapshot-groups/object-ID
Request message
  • Object ID

    Specify a value for the name that was obtained by getting the list of snapshot group names.

    Attribute

    Type

    Description

    name

    string

    (Required) Snapshot group name

    Note

    Do not specify the following snapshot group names:

    • Names that include a slash (/) or backslash (\)
    • Names consisting of only a period (.)

    You can get information about these snapshot groups by running the API request for getting snapshot information with the query parameter snapshotGroupName specified.

  • Query parameters

    With each request, you can obtain information for a maximum of 1000 snapshot groups. To obtain information for more than 1000 snapshot groups, execute the API request several times by using a combination of the count and startId parameters. By specifying the count parameter, you can also filter the snapshot group information to obtain.

    Parameter

    Type

    Filter Condition

    startSnapshotId

    string

    (Optional) Specify the ID of the snapshot from which to obtain information.

    If this parameter is omitted, "0,0" is assumed.

    count

    int

    (Optional) Specify the number of snapshot groups for which you want to obtain information by using a value in the range from 1 through 1000.

    If this parameter is omitted, 1000 is assumed.

  • Body

    None.

Response message
  • Body

    The following is an example of the output when getting information about the snapshot group with the name snapshotGroup:

    {
      "name": "snapshotGroup",
      "snapshots": [
        {
          "masterVolumeId": 100,
          "snapshotId": 3
        },
        {
          "masterVolumeId": 100,
          "snapshotId": 4
        }
      ],
      "count": 2,
      "totalCount": 2,
      "hasNext": false
    }

    Attribute

    Type

    Description

    name

    string

    Snapshot group name

    snapshots

    object[]

    The following information about the snapshot is obtained:

    • masterVolumeId (int)

      Master volume ID of the snapshot

    • snapshotId (int)

      Snapshot ID

      The mirror unit number is obtained.

Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X GET https://192.0.2.100/ConfigurationManager/simple/v1/objects/snapshot-groups/snapshotGroup

Deleting a snapshot group

The following request deletes a snapshot group and all snapshots in the snapshot group for the specified snapshot group name.

Execution permission

Storage Administrator (Local Copy)

Request line

DELETE base-URL/simple/v1/objects/snapshot-groups/object-ID
Request message
  • Object ID

    Specify a value for the name that was obtained by getting the list of snapshot group names.

    Attribute

    Type

    Description

    name

    string

    (Required) Snapshot group name

    Note

    Do not specify a snapshot group name that contains a slash (/) or a backslash (\).

    To delete a snapshot group whose name contains a slash (/) or a backslash (\), execute the API request for deleting a snapshot.

    If all snapshots in a snapshot group are deleted, the snapshot group is also deleted automatically.

  • Query parameters

    None.

  • Body

    None.

Response message
Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X DELETE https://192.0.2.100/ConfigurationManager/simple/v1/objects/snapshot-groups/snapshotGroup

raidcom add snapshot

Add a combination of the specified LDEV number and Pool ID to a snapshot group. If there is no name of specified snapshot group, create a new snapshot group.

Syntax
raidcom add snapshot -ldev_id <ldev#(P)> <ldev#(S)> -pool 
{<pool ID#> | <pool naming>} 
-snapshotgroup <name> [-snap_mode <mode>] [-mirror_id <mu#>]
Options and parameters
  • -ldev_id <ldev#(P)> <ldev#(S)>

    Specifies the LDEV number to be created the snapshot data. LDEV numbers for P-VOL and S-VOL must be included.

  • -pool {<pool ID#> | <pool naming>}

    Specifies the pool ID or the pool name created for Snapshot.

  • -snapshotgroup <name>

    Specifies a name to be given for snapshot group.

  • [-mirror_id <mu#>]

    Supported storage systems:

    • VSP 5000 series
    • VSP G1x00 and VSP F1500
    • VSP G130, G/F350, G/F370, G/F700, G/F900

    Specifies the mirror ID.

    If this option is omitted, an unused mirror ID is allocated automatically.

  • [-snap_mode <mode>]

    Specifies the mode to create a snapshot group and the mode to add a P-VOL or S-VOL to the snapshot group. If you specify multiple modes, use a space as a separator.

    The following modes can be specified:

    • <mode>= CTG: For creating in CTG mode. The consistency group number is allocated internally by itself.

      If this option is omitted, the snapshot group is created in normal mode.

      This option is effective only when a new snapshot group is to be created.

      This option is ignored if this is specified for the existing snapshot group.

    • <mode> = clone: For adding a P-VOL or S-VOL as a volume for which you can create a pair with the clone attribute (clone mode).

    • <mode>= cascade: For adding a P-VOL or S-VOL as a volume in which you can create a cascade pair (cascade mode).

    Example:

    • -snap_mode CTG clone
    • -snap_mode CTG
Examples

Adding a combination of the P-VOL (LDEV number 10:10), the S-VOL (LDEV number 20:20), and the Pool (SnapPool00) to the snapshot group (db1).

# raidcom add snapshot -ldev_id 0x1010 0x2020 -pool SnapPool00 -snapshotgroup db1

raidcom map snapshot

Maps the specified snapshot data to the S-VOL. The S-VOL to be mapped snapshot data must be created before it is specified.

Syntax
raidcom map snapshot -ldev_id <ldev#(P)> <ldev#(S)> {-snapshotgroup <name> | -mirror_id <mu#>}
Options and parameters
  • -ldev_id <ldev#(P)> <ldev#(S)>

    Specifies the LDEV number of P-VOL and S-VOL.

  • -snapshotgroup <name>

    Specifies the name of the snapshot group in which the snapshot data as the operation target is included.

    One MU that corresponds to the specified P-VOL is mapped from the specified snapshot group.

    Note

    Because the MU is selected automatically, an unexpected MU could be mapped. So if you intend to specify the specific snapshot data, specify the snapshot data by an MU number instead of a snapshot group.

  • -mirror_id <mu#>

    Specifies the mirror ID of a snapshot data to be a target.

Examples

Mapping the snapshot data of the LDEV number 10:10 that is included in the snapshot group (db1) to the LDEV number 20:00.

# raidcom map snapshot -ldev_id 0x1010 0x2000 -snapshotgroup db1

Mapping the snapshot data of the LDEV number 10:10 and the Mirror ID 10 to the LDEV number 20:00.

# raidcom map snapshot -ldev_id 0x1010 0x2000 -mirror_id 10

raidcom unmap snapshot

Unmaps the S-VOL which is mapping the snapshot data.

Syntax
raidcom unmap snapshot -ldev_id <ldev#> [-snapshotgroup <name> | -mirror_id <mu#>] 
Options and parameters
  • -ldev_id <ldev#>

    Specifies the LDEV number to be unmapped.

    Snapshot group name or MU number must be specified when you specify the LDEV number of P-VOL to identify the snapshot data.

    Do not specify the snapshot group name and MU number when you specify the LDEV number of S-VOL.

  • [-snapshotgroup <name>]

    Specifies the name of the snapshot group in which the snapshot data as the operation target is included.

    One MU which corresponds to the specified P-VOL is unmapped from the specified snapshot group.

    Note

    Because the MU is selected automatically, an unexpected MU could be unmapped. So if you intend to specify the specific snapshot data, specify the snapshot data by an MU number instead of a snapshot group.

  • [-mirror_id <mu#>]

    Specifies the mirror ID of the snapshot data to be a target of unmapping when you specify the LDEV number of P-VOL.

Examples

Unmapping the S-VOL (LDEV number 20:00).

# raidcom unmap snapshot -ldev_id 0x2000

Unmapping the snapshot data of the LDEV number 10:10 that is included in the snapshot group (db1).

# raidcom unmap snapshot -ldev_id 0x1010 -snapshotgroup db1

Unmapping the P-VOL (LDEV number 10:10) and the mirror ID 10.

# raidcom unmap snapshot -ldev_id 0x1010 -mirror_id 10

raidcom modify snapshot

Operate the specified snapshot group.

Syntax
raidcom modify snapshot -ldev_id <ldev#> {-snapshotgroup <name> 
| -mirror_id <mu#>} -snapshot_data <op> [-copy_pace <copy pace>]
 
raidcom modify snapshot -snapshotgroup <name> -snapshot_data <op> 
[-copy_pace <copy pace>] 
 
raidcom modify snapshot -ldev_id <ldev#> -snapshot_data <op> 
[-copy_pace <copy pace>] 
 
raidcom modify snapshot -snapshotgroup <current name>
<new name> -snapshot_data rename
Options and parameters
  • -ldev_id <ldev#>

    Specifies the LDEV number of P-VOL (or S-VOL) to be performed.

  • -snapshotgroup <name>

    Specifies the snapshot group name in which the snapshot data is included.

  • -mirror_id <mu#>

    Specifies the mirror ID of a snapshot data.

  • -snapshot_data <op>

    Specifies the operation to be performed for the specified snapshot group. The parameter of the operation to be specified is the following:

    • create: Creates snapshot data.1
    • split: Creates snapshot data.1
    • resync: Discards the created snapshot data.1
    • restore: Restores the snapshot data.1
    • clone: Clones pairs.2
  • [-copy_pace <copy pace>]

    Specifies the copy speed. Enabled only when clone is specified for -snapshot_data. The following speeds can be specified:

    • slower
    • medium
    • faster

    When clone is specified for -snapshot_data, if you did not specify the copy speed, medium is set. When you specify a value other than clone, if you specify the copy speed, this option is not enabled.

  • -snapshotgroup <current name> <new name> -snapshot_data rename

    Specifies when you change the snapshot group name. The snapshot group name specified in <current name> is changed to the name specified in <new name>.

Note

  1. Clone mode pairs do not support this operation.
  2. Cascade mode pairs do not support this operation.
  3. For the details about the defragmentation, see the Hitachi Thin Image User Guide.

The following shows the operation of the snapshot data with the combination of options and parameters:

When creating a snapshot data (when specifying create/split)

#

The ways to specify the parameter

CTG mode

normal mode

1

LDEV number and snapshot group.

P-VOL in the snapshot group.

P-VOL in the snapshot group and the smallest number of MU.

2

LDEV number and MU number.

Specified P-VOL and MU number.

Specified P-VOL and MU number.

3

LDEV number only (Specifying S-VOL).

P-VOL and MU number that are mapped by the specified S-VOL.

P-VOL and MU number that are mapped by the specified S-VOL.

4

Snapshot group.

All the P-VOLs related to the snapshot group.

The consistency is endured.

All the P-VOLs related to the snapshot group.

The consistency is not endured.

When discarding or restoring the snapshot data (when specifying resync/restore)

#

The ways to specify the parameter

CTG mode

normal mode

1

LDEV number and snapshot group.

P-VOL in the snapshot group.

P-VOL in the snapshot group and the smallest number of MU.

2

LDEV number and MU number.

Specified P-VOL and MU number.

Specified P-VOL and MU number.

3

LDEV number only (Specifying S-VOL).

P-VOL and MU number that are mapped by the specified S-VOL.

P-VOL and MU number that are mapped by the specified S-VOL.

4

Snapshot group.

All the P-VOLs related to the snapshot group.

All the P-VOLs related to the snapshot group.

Examples

Creating a snapshot data for the P-VOL (LDEV number 10:10) that is included in the snapshot group (db1).

# raidcom modify snapshot -ldev_id 0x1010 -snapshotgroup db1 -snapshot_data create

Creating a snapshot data for the P-VOL (LDEV number 10:10) and the mirror ID 10.

# raidcom modify snapshot -ldev_id 0x1010 -mirror_id 10 -snapshot_data create

Creating a snapshot data for the S-VOL (LDEV number 20:10).

# raidcom modify snapshot -ldev_id 0x2010 -snapshot_data create

Creating a snapshot data for all the P-VOLs that are included in the snapshot group (db1).

# raidcom modify snapshot -snapshotgroup db1 -snapshot_data create

Discarding the snapshot data for the P-VOL (LDEV number 10:10) and the mirror ID 10.

# raidcom modify snapshot -ldev_id 0x1010 -mirror_id 10 -snapshot_data resync

Restoring the snapshot data for the S-VOL (LDEV number 20:10).

# raidcom modify snapshot -ldev_id 0x2010 -snapshot_data restore

Changing the snapshot group name (db1) to db2.

# raidcom modify snapshot -snapshotgroup db1 db2 -snapshot_data rename

raidcom get snapshot

Displays the information of snapshot group and snapshot data that are defined in the device. If this option is omitted, the list of snapshot group is displayed.

Syntax
raidcom get snapshot [-ldev_id <ldev#> [-key opt] | -snapshotgroup <name> 
[-key opt]] [-format_time] [{-check_status | -check_status_not} <string>... 
[-time <time>]]
Options and parameters
  • [-ldev_id <ldev#>]

    Specifies the LDEV number to be displayed the snapshot data information. Specifies either one of P-VOL or S-VOL for the LDEV number.

  • [-snapshotgroup <name>]

    Specifies the snapshot group in which you want to display the snapshot data information.

  • [-key opt]

    Specify the -key opt option together with the -ldev_id or the -snapshotgroup option to display the following:

    • SMPP as the snapshot data status
    • (VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900) SLU attribute and information of the Diff Clone pair that is being used in the VASA environment
    • (VSP 5000 series, VSP G1x00 and VSP F1500, VSP G130, G/F350, G/F370, G/F700, G/F900) Status of expansion processing of DP-VOL
    • (VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900) Status of the Read Only attribute of the Snapshot data.
  • [–format_time]

    Specify this option to display the time when a snapshot data (SPLT-TIME) is created, with the format1 below. The time zone used in the storage system2 is displayed. Zero “0” is added to the beginning if the value of each element is shorter than the regulated length.

    Format: YYYY-MM-DDThh:mm:ss

    Where:

    • YYYY-MM-DD = year-month-date
    • hh = time in 24 hours, range 0-23
    • mm:ss = minute:second

    For example, December 2, 2016, one o’clock p.m. is displayed as 2016-12-02T13:00:00

    Notes:

    1. “T” in the format separates the date and the time.
    2. For VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900, VSP Gx00 models and VSP Fx00 models, the time zone set in the device is used.

      For other models, UTC+0 is used.

  • [-check_status <string> [-time <time>]]

    Check if the snapshot group or the snapshot data is in the same state as specified in <string>. If the option contains multiple states, the OR condition check is performed and verifies that the snapshot group or snapshot data is in one of the states contained in the option.

    The following strings are specified in the <string>:

    • COPY: Copy status.
    • PAIR: Pair status.
    • PSUS: Suspend status.
    • PSUE: Suspend failure status.
    • PFUL: Indicates that the Thin Image or Copy-on-Write Snapshot pool exceeds the threshold in the PAIR status.
    • PFUS: Indicates that the Thin Image or Copy-on-Write Snapshot pool exceeds the threshold in the PSUS status.
    • RCPY: Shows that the copying is in progress by resynchronization.
    • SMPP: Indicates that the pair is being deleted. When specifying SMPP, specify -key opt as well.
    • PSUP: Indicates that the pair with the clone attribute is split.

    If "-time" is specified, the status of the snapshot group or the snapshot data is checked every three seconds until the end of the specified <time> (seconds).

    When this option is specified, the returned values are as follows:

    • The snapshot group or the snapshot data is in one of the specified states: 0
    • The snapshot group or the snapshot data is in none of the specified states (without -time option): 1
    • The snapshot group or the snapshot data is in none of the specified states (when the specified <time> passed): EX_EWSTOT

    Note:

    When you specify -snapshotgroup <name>, and the pair is deleted, EX_ENOOBJ is returned.

  • [-check_status_not <string> [-time <time>]]

    Check if the snapshot group or the snapshot data is not in the same state as specified in <string>. If the option contains multiple states, the OR condition check is performed and verifies that the snapshot group or snapshot data is not in any of the states contained in the option. The following strings are specified in the <string>.

    • COPY: Copy status.
    • PAIR: Pair status.
    • PSUS: Suspend status.
    • PSUE: Suspend failure status.
    • PFUL: Indicates that the Thin Image or Copy-on-Write Snapshot pool exceeds the threshold in the PAIR status.
    • PFUS: Indicates that the Thin Image or Copy-on-Write Snapshot pool exceeds the threshold in the PSUS status.
    • RCPY: Shows that the copying is in progress by resynchronization.
    • SMPP: Indicates that the pair is being deleted. When specifying SMPP, specify -key opt as well.
    • PSUP: Indicates that the pair with the clone attribute is split.

    If "-time" is specified, the status of the snapshot group or the snapshot data is checked every three seconds until the end of the specified <time> (seconds).

    When this option is specified, the returned values are as follows:

    • The snapshot group or the snapshot data is not in any of the specified states: 0
    • The snapshot group or the snapshot data is in one of the specified states (without -time option): 1
    • The snapshot group or the snapshot data is in one of the specified states (when the specified <time> passed): EX_EWSTOT
    Note

    When you specify -snapshotgroup <name>, and the pair is deleted, EX_ENOOBJ is returned.

Examples

Displaying the list of snapshot groups.

# raidcom get snapshot
SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIME
snap1         -   -    85000098  -    -   -       -  - ----    -
snap2         -   -    85000098  -    -   -       -  - ----    -
snap3         -   -    85000098  -    -   -       -  - ----    -

Displaying the snapshot data related to the specific P-VOL (LDEV number: 14536).

# raidcom get snapshot -ldev_id 14536
SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIME
snap1       P-VOL PAIR 85000098 14536 1010    -    2 100 ----   -
snap2       P-VOL PAIR 85000098 14536 1011  13000  2 100 G---   -
snap3       P-VOL PAIR 85000098 14536 1012    -    2 100 ----   -

Displaying the snapshot data related to the specific S-VOL (LDEV number: 13000).

# raidcom get snapshot -ldev_id 13000
SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIME
snap2       S-VOL PAIR 85000098 13000 1011 14536  2 100 G---  -

Displaying the snapshot data included in the specific snapshot group.

# raidcom get snapshot -snapshotgroup snap2
SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIME
snap2       P-VOL PAIR 85000098 14536 1011 13000  2 100 G---  -
snap2       P-VOL PAIR 85000098 14537 1011 13001  2 100 G---  -
snap2       P-VOL PAIR 85000098 14538 1011 13002  2 100 G---  -

Displaying SPLT-TIME in YYYY-MM-DDThh:mm:ss format.

# raidcom get snapshot -ldev_id 14356  -format_time
SnapShot_name   P/S STAT   Serial# LDEV#   MU# P-LDEV# PID    % MODE SPLTTIME
        snap1 P-VOL PSUS 85000098 14536 1010       -	  2 100 ---- 2016-07-22T10:18:20
        snap2 P-VOL PSUS 85000098 14536 1011   13000  2 100 G--- 2016-07-22T10:18:20
        snap3 P-VOL PSUS 85000098 14536 1012       -   2 100 ---- 2016-07-22T10:18:20

Displays the snapshot data with the SLU attribute related to the specific S-VOL (LDEV # 40960) by specifying the -key opt option.

# raidcom get snapshot -ldev_id 40960 –key opt
SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID %
MODE SPLT-TIME SLU C_LDEV#  P  R
Snap2       S-VOL PAIR 85000098 40960 1012  258  2 100
A---        -    Y       -  -  D
Description of each column in output example:
  • SnapShot_name

    Displays the name of snapshot group defined in the device.

  • P/S

    Displays the attribute of the target LDEV. It displays P-VOL for the P-VOL and S-VOL for the S-VOL. In the list of snapshot, "-" is displayed.

  • STAT

    Displays the following status of each snapshot data:

    • SMPP: The pair is being deleted.
    • PSUP: The pair is being suspended.
    • CPYD: The differential data is being copied.
    • Other statuses: See pairdisplay command.
  • Serial#

    Displays the product serial number.

  • LDEV#

    Displays the LDEV number related to the snapshot.

  • MU#

    Displays the Mirror ID of the P-VOL for the snapshot.

  • P-LDEV#

    Displays the LDEV number of the volume (P-VOL or S-VOL) of the pair associated with the snapshot data. If the LDEV that is paired belongs to a different virtual storage machine, "----" is displayed.

  • PID

    Displays the pool ID.

  • %

    When MODE is clone or cascade mode, displays one of the following according to the status of STAT:

    • When STAT is COPY, RCPY, SMPP, or PSUP: Displays the progress rate of each processing.
    • For other statuses: Displays the concordance rate between the P-VOL and the S-VOL of a pair.

      When MODE is other than clone or cascade mode, the concordance rate between the P-VOL and the S-VOL is always displayed regardless of the STAT status.

    The following shows the concordance rate for each pair status.

    • PSUS: 0% to 100%
    • RCPY: 0% to 100%1
    • PAIR: 100%
    • COPY: 0% to 100%2
    • CPYD: 0% to 100%
    Note
    1. Displays the concordance rate before changing to RCPY status. The displayed value might decrease during RCPY status because the copy works.
    2. Displays the concordance rate before changing to COPY status. The displayed value does not change during COPY status.
  • MODE

    Displays the status of snapshot data:

    • G: The snapshot data created in CTG mode.
    • W: The status when the data are written in the secondary volume from the host in the PSUS/PFUS status.
    • C: The snapshot data created in clone mode.
    • A: The snapshot data created in cascade mode.
    • D: The snapshot data created in Diff Clone mode that is used in the VASA environment.
  • SPLT-TIME

    Displays the time when a snapshot data is created. When -format_time option is specified, displays in YYYY-MM-DDThh:mm:ss format. When -format_time option is not specified, indicates accumulated time in seconds from January 1, 1970 (GMT).

  • SLU

    Displays whether the SLU attribute is set for the snapshot:

    • Y: The SLU attribute is set.
    • N: Non-SLU attribute is set.

      A hyphen (-) is displayed for unsupported DKCMAIN microcode version.

  • C_LDEV#

    Displays the LDEV number of the diff compare volume (base volume), which is used for comparing the difference between the Diff Clone pair volumes in the VASA environment.

    A hyphen (-) is displayed for unsupported microcode version.

  • P

    Displays the status of expansion processing of DP-VOL (VSP 5000 series, VSP G1x00 and VSP F1500and VSP G130, G/F350, G/F370, G/F700, G/F900 only).

    • E: Expansion is in progress.
    • N: Not processed.
    • - (hyphen): This information is not available.

    A hyphen (-) is displayed if the microcode version is not supported.

  • R

    Displays the status of the Read Only attribute of the snapshot data (VSP 5000 seriesand VSP G130, G/F350, G/F370, G/F700, G/F900 only).

    • E: Read Only attribute is enabled.
    • D: Read Only attribute is disabled.
    • - (hyphen): This information is not available.

    A hyphen (-) is displayed if the microcode version is not supported.

raidcom modify snapshot

Operate the specified snapshot group.

Syntax
raidcom modify snapshot -ldev_id <ldev#> {-snapshotgroup <name> 
| -mirror_id <mu#>} -snapshot_data <op> [-copy_pace <copy pace>]
 
raidcom modify snapshot -snapshotgroup <name> -snapshot_data <op> 
[-copy_pace <copy pace>] 
 
raidcom modify snapshot -ldev_id <ldev#> -snapshot_data <op> 
[-copy_pace <copy pace>] 
 
raidcom modify snapshot -snapshotgroup <current name>
<new name> -snapshot_data rename
Options and parameters
  • -ldev_id <ldev#>

    Specifies the LDEV number of P-VOL (or S-VOL) to be performed.

  • -snapshotgroup <name>

    Specifies the snapshot group name in which the snapshot data is included.

  • -mirror_id <mu#>

    Specifies the mirror ID of a snapshot data.

  • -snapshot_data <op>

    Specifies the operation to be performed for the specified snapshot group. The parameter of the operation to be specified is the following:

    • create: Creates snapshot data.1
    • split: Creates snapshot data.1
    • resync: Discards the created snapshot data.1
    • restore: Restores the snapshot data.1
    • clone: Clones pairs.2
  • [-copy_pace <copy pace>]

    Specifies the copy speed. Enabled only when clone is specified for -snapshot_data. The following speeds can be specified:

    • slower
    • medium
    • faster

    When clone is specified for -snapshot_data, if you did not specify the copy speed, medium is set. When you specify a value other than clone, if you specify the copy speed, this option is not enabled.

  • -snapshotgroup <current name> <new name> -snapshot_data rename

    Specifies when you change the snapshot group name. The snapshot group name specified in <current name> is changed to the name specified in <new name>.

Note

  1. Clone mode pairs do not support this operation.
  2. Cascade mode pairs do not support this operation.
  3. For the details about the defragmentation, see the Hitachi Thin Image User Guide.

The following shows the operation of the snapshot data with the combination of options and parameters:

When creating a snapshot data (when specifying create/split)

#

The ways to specify the parameter

CTG mode

normal mode

1

LDEV number and snapshot group.

P-VOL in the snapshot group.

P-VOL in the snapshot group and the smallest number of MU.

2

LDEV number and MU number.

Specified P-VOL and MU number.

Specified P-VOL and MU number.

3

LDEV number only (Specifying S-VOL).

P-VOL and MU number that are mapped by the specified S-VOL.

P-VOL and MU number that are mapped by the specified S-VOL.

4

Snapshot group.

All the P-VOLs related to the snapshot group.

The consistency is endured.

All the P-VOLs related to the snapshot group.

The consistency is not endured.

When discarding or restoring the snapshot data (when specifying resync/restore)

#

The ways to specify the parameter

CTG mode

normal mode

1

LDEV number and snapshot group.

P-VOL in the snapshot group.

P-VOL in the snapshot group and the smallest number of MU.

2

LDEV number and MU number.

Specified P-VOL and MU number.

Specified P-VOL and MU number.

3

LDEV number only (Specifying S-VOL).

P-VOL and MU number that are mapped by the specified S-VOL.

P-VOL and MU number that are mapped by the specified S-VOL.

4

Snapshot group.

All the P-VOLs related to the snapshot group.

All the P-VOLs related to the snapshot group.

Examples

Creating a snapshot data for the P-VOL (LDEV number 10:10) that is included in the snapshot group (db1).

# raidcom modify snapshot -ldev_id 0x1010 -snapshotgroup db1 -snapshot_data create

Creating a snapshot data for the P-VOL (LDEV number 10:10) and the mirror ID 10.

# raidcom modify snapshot -ldev_id 0x1010 -mirror_id 10 -snapshot_data create

Creating a snapshot data for the S-VOL (LDEV number 20:10).

# raidcom modify snapshot -ldev_id 0x2010 -snapshot_data create

Creating a snapshot data for all the P-VOLs that are included in the snapshot group (db1).

# raidcom modify snapshot -snapshotgroup db1 -snapshot_data create

Discarding the snapshot data for the P-VOL (LDEV number 10:10) and the mirror ID 10.

# raidcom modify snapshot -ldev_id 0x1010 -mirror_id 10 -snapshot_data resync

Restoring the snapshot data for the S-VOL (LDEV number 20:10).

# raidcom modify snapshot -ldev_id 0x2010 -snapshot_data restore

Changing the snapshot group name (db1) to db2.

# raidcom modify snapshot -snapshotgroup db1 db2 -snapshot_data rename

raidcom delete snapshot

Deletes the snapshot data and the snapshot group. The relevant snapshot data of the LDEV is deleted from the snapshot group by specifying LDEV number. When no snapshot data left in the snapshot group, the snapshot group is deleted.

Syntax
raidcom delete snapshot {-snapshotgroup <name> | -ldev_id <ldev#> 
{-mirror_id <mu#> |-snapshotgroup <name> | -range tree}}
Options and parameters
  • -snapshotgroup <name>

    Specifies the snapshot group in which the target data to be deleted is included.

    If the snapshot group is specified as the target, all the snapshot data and the snapshot group are deleted.

  • -ldev_id <ldev#>

    Specifies the LDEV number of P-VOL or S-VOL for the snapshot data to be deleted.

    When P-VOL is specified, specify the snapshot data by specifying the MU number or the snapshot group (Specifying the MU number or the snapshot group is mandatory).

    When you specify the S-VOL, do not specify a MU number or a Snapshot group. If you specify the MU number or the Snapshot group, the P-VOL of specified LDEV number becomes the subject of deletion.

  • -mirror_id <mu#>

    Specifies the Mirror ID of the snapshot data to be deleted.

  • -snapshotgroup <name>

    Specifies the snapshot group to be deleted.

    The smallest number of MU in the snapshot group becomes the subject to be deleted.

  • -range tree

    Specify this option to delete snapshot data in all layers of a snapshot tree for which the root volume is specified by -ldev_id <ldev#>. To specify this option, the following conditions must be met:

    • Root volume is an LDEV specified by -ldev_id <ldev#>.
    • The pair to be deleted was created in the cascade or clone mode.
    • The user has the operation authority for volumes of all pairs to be deleted.
    Note

    When multiple snapshot trees are cloned, specify the root volume of the first snapshot tree for -ldev_id <ldev#>, and execute the command. Only the first snapshot tree is deleted, and the status of the pairs under the first snapshot tree changes to PSUE. Specify the root volume of a snapshot tree under the first snapshot tree for -ldev_id <ldev#>, and execute the command again. When this option is specified, the SIM code (4b3xxx) that indicates abnormal termination of the Thin Image option might be output. However, the snapshot tree has been deleted normally and there is no problem.

Examples

Deleting the snapshot data of the snapshot group (db1).

# raidcom delete snapshot -snapshotgroup db1

Deleting the snapshot data of the P-VOL (LDEV number 10:10) and the Mirror ID (10).

# raidcom delete snapshot -ldev_id 0x1010 –mirror_id 10

Deleting the snapshot data of the LDEV number 10:10 that is included in the snapshot group (db1).

# raidcom delete snapshot -ldev_id 0x1010 -snapshotgroup db1
# raidcom delete snapshot -snapshotgroup db1 -ldev_id 0x1010

Deleting the snapshot data of the S-VOL (LDEV number 20:10).

# raidcom delete snapshot -ldev_id 0x2010

Deleting the snapshot data in all layers of a snapshot tree whose root volume has LDEV number 20:10.

# raidcom delete snapshot -ldev_id 0x2010 -range tree