Use the rmfcmap command to delete an
existing mapping.
Syntax
rmfcmap [ -force ] { fc_map_id | fc_map_name }
Parameters
- -force
- (Optional) Specifies that the target volume is brought online.
This parameter is required if the FlashCopy® mapping
is in the stopped state.
- fc_map_id | fc_map_name
- (Required) Specifies the ID or name of the FlashCopy® mapping
to delete. Enter the ID or name last on the command line.
Description
The rmfcmap command
deletes the specified mapping if the mapping is in the idle_or_copied or stopped state.
If it is in the stopped state, the -force parameter
is required. If the mapping is in any other state, you must stop the
mapping before you can delete it.
Deleting a mapping only deletes
the logical relationship between the two volumes; it does not affect
the volumes themselves. However, if you force the deletion, the target
volume (which might contain inconsistent data) is brought back online.
If the target of the FlashCopy mapping is a member of
the remote copy created , the remote copy can be affected in the following ways:
- If a stopped FlashCopy mapping is deleted and the
I/O group associated with the FlashCopy mapping is
suspended while this delete is being processed, then all remote copy relationships associated with
the target volume of a the FlashCopy mapping that were
active while the FlashCopy mapping was copying can be
corrupted. You must resynchronize them next time you start the system.
- If a stopped FlashCopy mapping that has previously
failed to prepare is deleted, then all remote copy relationships in the set of remote copy
relationships associated with the target volume can be corrupted. You must resynchronize them next
time you start the system.
Note: Remote copy includes Metro Mirror, Global
Mirror, and HyperSwap®.
Note: Maps that are rc_controlled are
not shown in the view when this command is specified.
An invocation example
rmfcmap testmap
The
resulting output:
No feedback