Preparing and starting a FlashCopy mapping by using the CLI

Before you start the FlashCopy process by using the command line interface (CLI), you must prepare a FlashCopy mapping.

Starting a FlashCopy mapping creates a point-in-time copy of the data on the source volume and writes it to the target volume for the mapping.

These steps help you prepare and start a FlashCopy mapping:

Issue the prestartfcmap CLI command to prepare the FlashCopy mapping.
To run the following command, the FlashCopy mapping cannot belong to a consistency group.
```
prestartfcmap -restore main1copy
```
Where main1copy is the name of the FlashCopy mapping.

This command specifies the optional restore parameter, which forces the mapping to be prepared even if the target volume is being used as a source in another active FlashCopy mapping.
The mapping enters the preparing state and moves to the prepared state when it is ready.

Issue the lsfcmap CLI command to check the state of the mapping.

The following code is an example of the output that is displayed:

lsfcmap -delim :
id:name:source_vdisk_id:source_vdisk_name:target_vdisk_id:
target_vdisk_name:group_id:group_name:status:progress:copy_rate
0:main1copy:0:mainvdisk1:1:bkpvdisk1:::prepared:0:50

Issue the startfcmap CLI command to start the FlashCopy mapping.
The following code is an example of the CLI command you can issue to start the FlashCopy mapping:
```
startfcmap -restore main1copy
```
Where main1copy is the name of the FlashCopy mapping.

This command specifies the optional restore parameter, which forces the mapping to be started even if the target volume is being used as a source in another active FlashCopy mapping.
Issue the lsfcmapprogress CLI command with the FlashCopy mapping name or ID to check the progress of the mapping.
The following code is an example of the output that is displayed; the FlashCopy mapping ID 0 is 47% completed.
```
lsfcmapprogress -delim :
id:progress
0:47
```

You created a point-in-time copy of the data on a source volume and wrote that data to a target volume. The data on the target volume is only recognized by the hosts that are mapped to it.