La commande 'mirror_list' permet d'afficher la liste des miroirs de la baie et les informations rattachées.

# mirror_list

Name                 Mirror Type       Mirror Object   Role   Remote System             Remote Peer           Active   Status         Link Up  

h6_testvg01_R   sync_best_effort   Volume  Master XIV 78 Prod salle F   h6_testvg01_J   yes Synchronized     

h6_testvg02_R   sync_best_effort   Volume  Master XIV 78 Prod salle F   h6_testvg02_J   yes Synchronized

Il est également possible de limiter le nombre des champs à l'écran avec l'option '-t':

# mirror_list -t local_peer_name,current_role,sync_state
Name                  Role   Status       
h6_testvg01_J   Slave  Consistent   
h6_testvg02_J   Slave  Consistent  

 

 

Extrait de la documentation officielle IBM ci-dessous :

Viewing Mirroring Status

Lists the status and configuration of mirroring couplings

mirror_list [ vol=VolName | cg=cgName | < [ scope=<cg|volume> ] 
[ sync_type=<sync_best_effort|async_interval> ] > ]

Parameters:

NameTypeDescriptionMandatoryDefault
sync_type Enumeration

List type - 
SYNC_BEST_
EFFORT, 
ASYNC_
INTERVAL,

or All (if no parameter is specified)
N All (if no parameter is specified)
scope Enumeration List type - [all mirrors,] all volumes, all CGs N All (if no param is specified)
vol Object name Local volume name. N [none]
cg Object name Local CG name. N [none]

This command shows current configuration and status for the remote mirroring of volumes or Consistency Groups. Size/part/time to synchronize are unknown if this is the slave and connection is broken.

Les différents champs affichés par la commande :

  • Name
  • Mirror Type (sync_best_effort, async_interval)
  • Mirror Object (CG, Volume)
  • Role (Master, Slave)
  • Remote System (target name)
  • Remote Peer (volume name)
  • Active (Yes, No)
  • Status (Initializing, Synchronized, Unsynchronized, Consistent, Inconsistent, RPO OK, RPO Lagging, Change Tracking)
  • Link Up (Yes, No)

The following optional parameters can be listed by explicitly specifying the proper columns:

  • Designation (Primary, Secondary)
  • Estimated Sync Time (estimated time to synchronization in seconds)
  • Size To Synchronize (size to synchronize in MB)
  • Operational (Yes, No)
  • Sync Progress (sync progress in %)
  • Mirror Error (why mirroring is deactivated: No_Error, Configuration_Error, Secondary_Pool_Exhausted, Master_Pool_Exhausted, No_Thin_Provisioning_Resources)
  • Schedule Name (schedule name)
  • Last replicated Snapshot Time (yyyy-mm-dd hh:mm:ss)
  • Specified RPO (value in h:mm:ss format)
The following deactivation reasons can be read from the output list (available only in XML output format):
  • INACTIVE_USER - No_Error
  • INACTIVE_SECONDARY_LOCKED - Secondary_Pool_Exhausted
  • INACTIVE_POOL_EXHAUSTED - Master_Pool_Exhausted
  • INACTIVE_VOL_SIZE_MISMATCH - Remote_And_Local_Volume_Size_Mismatch
  • INACTIVE_CONS_GROUP_MEMBERSHIP_MISMATCH - Cons_Group_Membership_Mismatch
  • INACTIVE_POSSIBLE_VOL_SIZE_MISMATCH - Possible_Remote_And_Local_Volume_Size_Mismatch
  • INACTIVE_POSSIBLE_CONS_GROUP_MEMBERSHIP_MISMATCH - Possible_Cons_Group_Membership_Mismatch
  • INACTIVE_THIN_PROVISIONING - No_Thin_Provisioning_Resources
  • INACTIVE_PEER_STATUS_MISMATCH - Peer_Status_Mismatch
  • INACTIVE_UPGRADE - Temporarily_Deactivated_For_Upgrade
IdNameDescriptionDefault Position

local_peer_
name

Name N/A 1
mirror_object Mirror Object N/A 3
designation Designation N/A N/A
current_role Role N/A 4
target_name Remote System N/A 5

remote_peer_
name

Remote Peer N/A 6
active Active N/A 7
sync_state Status N/A 8
connected Link Up N/A 9

size_to_
synchronize

Size To Sync (MB) N/A N/A
operational Operational N/A N/A
sync_progress Sync Progress (%) N/A N/A
mirror_error Mirror Error No Error, Secondary pool exhausted, Configuration error or No thin provisioning resources N/A
sync_type Mirror Type N/A 2
schedule_name Schedule Name N/A N/A

last_
replicated_
snapshot_time

Last Replicated N/A N/A
specified_rpo RPO N/A N/A
remote_rpo Remote RPO N/A N/A

application_
consistent

App Consistency N/A N/A

Output:

<command id="0">
<administrator>
    <command>
        <changes_session_id value="1288716489394201:1:1288903896317961:1"/>
        <code value="SUCCESS"/>
        <last_change_index value="32289"/>
        <status value="0"/>
        <status_str value="Command completed successfully"/>
        <return>
            <mirror id="100777">
                <id value="100777"/>
                <creator value=""/>
                <creator_category value="none"/>
                <local_peer_id value="100776"/>
                <local_peer_name value="SYNC_vol_5"/>
                <schedule_name value=""/>
                <designation value="Secondary"/>
                <current_role value="Slave"/>
                <remote_mirror_id value="100872"/>
                <remote_peer_name value="SYNC_vol_4"/>
                <target_id value="100707"/>
                <target_name value="SYNC_target_2"/>
                <sync_type value="sync_best_effort"/>
                <sync_state value="Consistent"/>
                <active value="yes"/>
                <connected value="yes"/>
                <operational value="yes"/>
                <sync_progress value="100"/>
                <size_to_synchronize value="-1"/>
                <estimated_sync_time value="0"/>
                <mirror_error value="No_Error"/>
                <mirror_object value="Volume"/>
                <specified_rpo value=""/>
                <remote_rpo value=""/>
                <last_replicated_snapshot_time value=""/>
                <init_type value="online"/>
            </mirror>
        </return>
    </command>
</administrator>
<aserver status="DELIVERY_SUCCESSFUL"/>
</command>
icon phone
Téléphone/Whatsapp : +33 (0)6 83 84 85 74
icon phone