raidcom modify snapshot

Storage Advisor Embedded User Guide

Version
93-07-2x
88-08-12
Audience
anonymous
Part Number
MK-97HM85022-25

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. (Note that parameters clone, delete_garbage, and stop_deleting_garbage cannot be used in Thin Image Advanced.):

  • create: Takes snapshot data.1, 4, 6
  • split: Takes snapshot data.1, 4, 6
  • resync: Deletes the created snapshot data.1
  • restore: Restores the Thin Image pair.1
    For a Thin Image Advanced pair, perform the following steps:
    1. Verify that the status of the pair to be restored is PSUS or SSUS.
    2. Run the raidcom modify snapshot -snapshot_data restore, and then verify that the command is complete normally.
    3. Wait until the status of the pair to be restored migrates to a status that is not RCPY.
    4. If the pair status changes to PSUS or SSUS in step 3, the pair restore operation is successfully complete.
  • clone: Clones pairs.2, 5
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.
  4. For a Thin Image Advanced pair, the pair status changes to PSUP while the specified operation is in process, and then changes to PSUS when the processing is complete. To verify that the operation is complete, run the raidcom get snapshot command to verify that STAT has changed from PSUP to PSUS, SSUS, or PSUE.
  5. This operation is not available for a Thin Image Advanced pair.
  6. For a Thin Image Advanced pair, the group operation with the -snapshotgroup option specified might not be performed if all of the following conditions are met. If the following conditions are met, perform the operation on one pair at a time by specifying the -ldev_id and -mirror_id options.
    • The snapshot group is not in the CTG mode.
    • The snapshot group contains two or more pairs created using the same P-VOL.
[-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>.

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