startfcconsistgrp

You can use the startfcconsistgrp command to start (trigger) a FlashCopy group of mappings. This command makes a point-in-time copy of the source virtual disk at the moment the command is executed.

Syntax

Read syntax diagramSkip visual syntax diagram>>- svctask -- -- startfcconsistgrp -- --+---------+-- --------->
                                         '- -prep -'

>--+- fc_consist_group_id ---+---------------------------------><
   '- fc_consist_group_name -'

Parameters

-prep
Optionally specifies to prepare the mapping or group prior to triggering the mapping.
fc_consist_group_id | fc_consist_group_name
Specifies the ID or name of the consistency group to trigger. Triggering Consistency Group 0 is invalid.

Description

This command triggers a group of mappings (on a consistency group basis). Triggering means to take a point-in-time copy of the source virtual disks.

The group must first be prepared for triggering. See the svctask prestartfcconsistgrp command to prepare the triggering. However, you can run this command with the optional -prep argument, which prepares the group and triggers the copy as soon as the preparation is complete. This means it is under the systems control when the trigger happens. That is, the preparation step takes some time to complete before the copy is made. If you want to control the triggering, you should use the svctask prestartfcconsistgrp command first.

The consistency group enters the copying state. The way the copy proceeds depends on the background copy rate attribute of the mapping. If the mapping is set to 0, only data that is subsequently updated on the source will be copied to the destination. This operation means that the destination can only be used as a backup copy while the mapping exist in the copying state. If the copy is stopped, the destination will not be usable. If you want to end up with a duplicate copy of the source at the destination, you should set the background copy rate greater than 0. This means that the system copies all the data (even unchanged data) to the destination and eventually reaches the idle or copied state. After this data is copied, you can delete the mapping and have a usable point-in-time copy of the source at the destination.

Triggering is usually performed on a consistency group basis. Only mappings belonging to Consistency Group 0 can be triggered on their own.

Possible failures

Examples

An invocation example

svctask startfcconsistgrp -prep 2