Restarting an SRDF/A Session Using SYMCLI

 

Topic

Managing SRDF

Selections

Select SRDF management tool: Managing SRDF using Solutions Enabler SYMCLI

Select SRDF using SYMCLI task: Managing SRDF/A

Select an SRDF/A task: Restarting a session

 

 

Contents

Restart an SRDF/A session. 4

About this procedure. 4

About SRDF/A. 4

Examine SRDF/A status and recover a backup copy of data. 4

Task 1:  Query the device group. 4

Task 2:  Query, associate, and establish BCV devices. 6

Task 3:  Split the R2/BCV pairs to make a gold copy. 7

Prepare to re-activate SRDF/A. 7

Task 4:  Disable consistency. 7

Task 5:  Change the SRDF mode to adaptive copy disk mode. 8

Task 6:  Re-establish the SRDF pairs. 10

Re-activate SRDF/A. 10

Task 7:  Verify that the number of invalid tracks is below 30,000. 10

Task 8:  Change the SRDF mode to asynchronous. 11

Task 9:  Enable and verify consistency protection. 13

 


 

Restart an SRDF/A session

About this procedure

·    This procedure is based on content in the the following documents:

·    EMC Solutions Enabler Symmetrix SRDF Family CLI Product Guide

·    SRDF/A and SRDF/A Multi-Session Consistency on UNIX and Windows EMC Engineering Solutions Guide

·    EMC Solutions Enabler Symmetrix Array Management CLI Product Guide.

·    EMC Solutions Enabler TimeFinder Family CLI Product Guide

You can download these guides from EMC Online Support (registration required): https://support.EMC.com.

·    Devices are managed by device group (-g GroupName).

CAUTION:   The user should be familiar with the concepts of SRDF/A, and have some experience using Solutions Enabler SYMCLI commands before attempting this procedure.

·    This procedure describes the steps necessary to restart a single source SRDF/Asynchronous mode (SRDF/A) session dropped due to an unplanned network outage.

Note:  If you are running Solutions Enabler 6.4 or greater, you can use the symrecover command to monitor, recover, and restart SRDF/S and SRDF/A sessions. Refer to Recovering SRDF Sessions in the Symmetrix DMX Procedure Generator.

About SRDF/A

SRDF/Asynchronous (SRDF/A) is a long distance disaster restart solution with fast application response times.

SRDF/A provides a dependent-write consistent point-in-time image on the target (R2) device, that is  slightly behind the source (R1) device. Host writes are collected for a configurable interval (-cycle_time) into delta sets. Delta sets are transferred to the remote Symmetrix array in predefined timed cycles.

SRDF/A’s timed cycles ensure that data at the remote (R2) site is dependent-write consistent.  This mode requires an SRDF/A license.

Examine SRDF/A status and recover a backup copy of data

Task 1:     Query the device group

Type the symrdf –g GroupName query –rdfa command to display the status of the specified device group.

To display device group pocsun00data:

symrdf -g pocsun100data query –rdfa

 

Device Group (DG) Name             : pocsun100data

DG's Type                          : RDF1

DG's Symmetrix ID                  : 000187461502

 

RDFA Session Number                : 34

RDFA Cycle Number                  : 0

RDFA Session Status                : Inactive

RDFA Minimum Cycle Time            : 00:00:30

RDFA Avg Cycle Time                : 00:00:00

Duration of Last cycle             : 00:00:00

RDFA Session Priority              : 10

Tracks not Committed to the R2 Side: 0

Time that R2 is behind R1          : 00:00:00

RDFA R1 Side Percent Cache In Use  :  0

RDFA R2 Side Percent Cache In Use  :  0

 

 

       Source (R1) View                 Target (R2) View     MODES

-------------------------------    --------------- ----- -----------

             ST                  LI      ST

Standard      A                   N      A

Logical       T  R1 Inv   R2 Inv  K      T  R1 Inv   R2 Inv      RDF Pair

Device  Dev  E  Tracks    Tracks  S Dev  E  Tracks  Tracks MDAC  STATE

------------------------------- -- --------------- ----- -----------

 

DEV001  00E1 RW   0        16072 NR 00E1 WD    3211      0 A..X  Suspended

DEV002  00E2 RW   0        17427 NR 00E2 WD    1859      0 A..X  Suspended

DEV003  00E3 RW   0        19270 NR 00E3 WD       0      0 A..X  Suspended

DEV004  00E4 RW   0        19270 NR 00E4 WD       0      0 A..X  Suspended

 

Total          -------- --------           --------   --------

  Track(s)            0    72039               5070       0

  MB(s)             0.0   2251.2              158.4     0.0

 

Legend for MODES:

 

 M(ode of Operation): A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

 D(omino)           : X = Enabled, . = Disabled

 A(daptive Copy)    : D = Disk Mode, W = WP Mode, . = ACp off

 C(onsistency State): X = Enabled, . = Disabled, - = N/A

 

Interpreting the output

·        RDFA Session Status is Inactive The underlying cause can include:

·        R1 cache overrun

·        Link outage longer than link limbo timeout parameter

·        Hardware failure

·        Human error

·        The link is NR (not ready)

·        The RDF pairs are in a suspended state.

·        In the Source (R1) View, there are R2 Invalid Tracks, and in the Target (R2) View, there are R1 Invalid Tracks. This indicates that the session dropped in mid-cycle.

Specifically, at the time of the suspension, there were:

·        5,070 invalid tracks in the R2 receive cycle (still owed to the R2 target by the source).

·        72,039 invalid tracks in the transmit cycle on the source.

 

Best practice: invalid tracks

Invalid tracks accumulate in the source transmit cycle as long as the applications are active.

During a prolonged link outage, hundreds of thousands of invalid tracks can accumulate in the source transmit cycle.

Activating SRDF/A with a large number of invalid tracks owed to the R2 side can overload the DA, flood the RDF link, and flood the R1 cache, causing the SRDF/A session to drop. Activating SRFD/A with a large number of invalid tracks owed to the R2 side can cause other active SRDF/A sessions in the array to experience elongated cycle times.

Always use adaptive copy disk mode to move large amounts of data until the invalid track count falls below 30,000, or one cycle set of data. This minimizes your risk of flooding the cache or your link.

Task 2:     Query, associate, and establish BCV devices

                       

Best practice: create a gold copy

After any unplanned SRDF/A session drop, capture a backup copy (gold copy) of the data before performing any other recovery operation.

The established R2/RBCV session contains the last consistent data image prior to the outage.

   1. [   ]    Type the symmir –g GroupName query –rdf command to display established source/target pairings.

To display group pocsun100data:

symmir -g pocsun100data query –rdf

 

Device Group (DG) Name: pocsun100data

DG's Type             : RDF1

DG's Symmetrix ID     : 000187461502

Remote Symmetrix ID   : 000187461514

 

 

                     R E M O T E      S Y M M E T R I X

 

 

     Standard Device                    BCV Device                  State

-------------------------- ---------------------------- ------------

                    Inv.                                  Inv.

Logical        Sym  Tracks Logical        Sym     Tracks STD <=> BCV

-------------------------- ---------------------------- ------------

 

DEV001         00E1      0 RBCV001       01E8 *    0    Synchronized

DEV002         00E2      0 RBCV003       01EA *    0    Synchronized

DEV003         00E3      0 RBCV002       01E9 *    0    Synchronized

DEV004         00E4      0 RBCV004       01EB *    0    Synchronized

Total              -------                               -------

  Track(s)               0                         0

  MB(s)                0.0                       0.0

 

Legend:

 

(*): The paired BCV device is associated with this group.

 

The next step varies depending on whether the BCV devices are associated (as in the example above).

If the BCV devces are associated (as in the example above), skip to Task 3:

If the BCV devices are not associated, proceed to Step 2. [   ]

   2. [   ]    Type the symbcv –g GroupName –sid SID associate command to associate one or a range of BCVs to a one or a range of standard device.

Note:  . When you associate a BCV device with a device group, you can assign it a logical device name. If not, a logical device name is assigned automatically.

To associate a single BCV device with a standard device:

symbcv –g GroupName –sid SID associate dev SymDevName LdevName

For example:

symbcv –g pocsun100data –sid 502 associate dev 001F BCV001

 

To associate a range of BCV devices to a device group:

symbcv –g GroupName –sid SID associateall dev - range StartSymDev:EndSymDev

For example:

symbcv –g pocsun100data –sid 502 associateall dev –range 087:08A

 

   3. [   ]    Type the symmir –g GroupName –full establish LDev command to perform a full establish on the specified standard/BCV device pair.

For example:

symmir –g pocsun100data –full establish DEV001

Task 3:     Split the R2/BCV pairs to make a gold copy

The split operation splits off a dependent-write consistent, restartable copy of a database management system in seconds with no interruption to online service.

Consistent split helps to avoid inconsistencies and restart problems that can occur when splitting a database-related BCV without first quiescing the database.

Note:  This functionality requires a TimeFinder/CG license.

Type the symmir –g GroupName split –consistent –rdf command to split off a gold copy.

For example:

symmir -g pocsun100data split -consistent -rdf –nop

 

Remote 'Split' operation execution is in progress for

device group 'pocsun100data'. Please wait...

Remote 'Split' operation successfully executed for device group

'pocsun100data'.

 

Prepare to re-activate SRDF/A

Task 4:     Disable consistency

                       

   1. [   ]    Type the symrdf –g GroupName disable command to disable consistency for your device group.

To disable consistency for group pocsun100data:

symrdf -g pocsun100data disable –nop

 

An RDF 'Disable' operation execution is

in progress for device group 'pocsun100data'. Please wait...

The RDF 'Disable' operation successfully executed for

device group 'pocsun100data'.

 

   2. [   ]    Type the symrdf –g GroupName query command to confirm that consistency is disabled.

To query group pocsun100data:

symrdf -g pocsun100data query –rdfa

 

Device Group (DG) Name             : pocsun100data

DG's Type                          : RDF1

DG's Symmetrix ID                  : 000187461502

 

RDFA Session Number                : 34

RDFA Cycle Number                  : 0

RDFA Session Status                : Inactive

RDFA Minimum Cycle Time            : 00:00:30

RDFA Avg Cycle Time                : 00:00:00

Duration of Last cycle             : 00:00:00

RDFA Session Priority              : 10

Tracks not Committed to the R2 Side: 0

Time that R2 is behind R1          : 00:00:00

RDFA R1 Side Percent Cache In Use  :  0

RDFA R2 Side Percent Cache In Use  :  0

 

  Source (R1) View             Target (R2) View     MODES

-------------------------------------------- ----- -----------

             ST                  LI      ST

Standard      A                  N       A

Logical       T  R1 Inv  R2 Inv  K    T  R1 Inv   R2 Inv    RDF Pair

Device  Dev   E  Tracks  Tracks  S Dev   E  Tracks Tracks MDAC  STATE

--------------------------------------------------- ----- -----------

 

DEV001  00E1 RW     0    16072 NR 00E1 WD   3211        0 A..  Suspended

DEV002  00E2 RW     0    17427 NR 00E2 WD   1859        0 A..  Suspended

DEV003  00E3 RW     0    19270 NR 00E3 WD      0        0 A..  Suspended

DEV004  00E4 RW     0    19270 NR 00E4 WD      0        0 A..  Suspended

 

Total          -------- --------           -------- --------

  Track(s)            0    72039               5070        0

  MB(s)             0.0   2251.2              158.4      0.0

 

Legend for MODES:

 

 M(ode of Operation): A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

 D(omino)           : X = Enabled, . = Disabled

 A(daptive Copy)    : D = Disk Mode, W = WP Mode, . = ACp off

 C(onsistency State): X = Enabled, . = Disabled, - = N/A

Task 5:     Change the SRDF mode to adaptive copy disk mode

                       

Adaptive copy disk mode is designed to move large amounts of data with no impact to applications. Use adaptive copy mode to perform the initial copy of local data across the SRDF link to the remote site.

CAUTION:    Starting an SRDF establish in synchronous mode could create serious I/O latency issues for the host application.

   1. [   ]    Type the symrdf –g GroupName set mode acp_disk command to change the SRDF mode to adaptive copy disk.

To set the mode for the device group pocsun100data to adaptive copy disk:

symrdf -g pocsun100data set mode acp_disk –nop

 

An RDF Set 'ACp Disk Mode ON' operation execution is in

progress for device group 'pocsun100data'. Please wait...

 

The RDF Set 'ACp Disk Mode ON' operation successfully executed

for device group 'pocsun100data'.

 

   2. [   ]    Type the symrdf –g GroupName query -rdfa command and confirm the group is in adaptive copy mode.

When the SRDF mode is set to adaptive copy disk:

·        The array acknowledges all writes to source (R1) devices as if they were local devices.

·        New data accumulates on the source (R1) device and is marked as invalid tracks until it is transferred to the target (R2) device.

·        The remote director transfers each write to the target (R2) device whenever link paths become available.

·        Tracks are read from the physical disk for transfer to the R2.

 

symrdf -g pocsun100data query –rdfa

 

Device Group (DG) Name             : pocsun100data

DG's Type                          : RDF1

DG's Symmetrix ID                  : 000187461502

 

RDFA Session Number                : 34

RDFA Cycle Number                  : 0

RDFA Session Status                : Inactive

RDFA Minimum Cycle Time            : 00:00:30

RDFA Avg Cycle Time                : 00:00:00

Duration of Last cycle             : 00:00:00

RDFA Session Priority              : 10

Tracks not Committed to the R2 Side: 0

Time that R2 is behind R1          : 00:00:00

RDFA R1 Side Percent Cache In Use  :  0

RDFA R2 Side Percent Cache In Use  :  0

 

       Source (R1) View          Target (R2) View     MODES

-------------------  ------------------------ ----- -----------

            ST                 LI    ST

Standard     A                  N     A

Logical      T  R1 Inv   R2 Inv K     T  R1 Inv   R2 Inv       RDF Pair

Device  Dev  E  Tracks   Tracks S Dev E  Tracks   Tracks MDAC  STATE

-------------------------- -- ------------------------ ----- ------

DEV001  00E1 RW    0   16072 NR 00E1 WD    3211        0 C.D.  Suspended

DEV002  00E2 RW    0   17427 NR 00E2 WD    1859        0 C.D.  Suspended

DEV003  00E3 RW    0   19270 NR 00E3 WD       0        0 C.D.  Suspended

DEV004  00E4 RW    0   19270 NR 00E4 WD       0        0 C.D.  Suspended

 

Total          -------- --------           -------- --------

  Track(s)         0    72039              5070    0

  MB(s)          0.0   2251.2             158.4  0.0

 

Legend for MODES:

 

 M(ode of Operation): A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

 D(omino)           : X = Enabled, . = Disabled

 A(daptive Copy)    : D = Disk Mode, W = WP Mode, . = ACp off

 C(onsistency State): X = Enabled, . = Disabled, - = N/A

 

   3. [   ]    Confirm that the mode has changed to adaptive copy disk (C  D in the MDAC column).

Task 6:     Re-establish the SRDF pairs

                       

Type the symrdf –g GroupName establish command to initiate a data copy from the source (R1) side to the target (R2) side.

To establish devices in group pocsun100data:

symrdf -g pocsun100data establish –nop

 

An RDF 'Incremental Establish' operation execution is

in progress for device group 'pocsun100data'. Please wait...

  Suspend RDF link(s).......................................Done.

  Mark target (R2) devices to refresh from source R1)......Started.

  Devices: 00E1-00E2 ...................................... Marked.

  Mark target (R2) devices to refresh from source (R1)......Done.

  Merge device track tables between source and target.......Started.

  Devices: 00E1-00E2 ...................................... Merged.

  Merge device track tables between source and target.......Done.

  Resume RDF link(s)........................................Started.

  Resume RDF link(s)........................................Done.

 

The RDF 'Incremental Establish' operation successfully initiated for device group 'pocsun100data'.

 

Re-activate SRDF/A

Task 7:     Verify that the number of invalid tracks is below 30,000

                       

IMPORTANT:   Do not activate SRDF/A mode with a large number of invalid tracks.

Best practice

Wait for the total number of invalid tracks to fall below 30,000 before changing the mode to SRDF/A.

Activating SRDF/A with a large number of invalid tracks owed to the R2 side can overload the DA, flood the RDF link, and flood the R1 cache, causing the SRDF/A session to drop. Activating SRFD/A with a large number of invalid tracks owed to the R2 side can cause other active SRDF/A sessions in the array to experience elongated cycle times.

Remain in adaptive copy disk mode until the invalid track count falls below 30,000, or one cycle set of data. This minimizes your risk of flooding the cache or your link.

   1. [   ]    Type the symrdf –g GroupName query -rdfa –i Seconds command to display the number of invalid tracks at the specified interval.

   2. [   ]    Monitor the output until the number of invalid tracks falls below 30,000.

                       

symrdf -g pocsun100data query -rdfa -i 5

 

Device Group (DG) Name             : pocsun100data

DG's Type                          : RDF1

DG's Symmetrix ID                  : 000187461502

 

RDFA Session Number                : 34

RDFA Cycle Number                  : 0

RDFA Session Status                : Inactive

RDFA Minimum Cycle Time            : 00:00:30

RDFA Avg Cycle Time                : 00:00:00

Duration of Last cycle             : 00:00:00

RDFA Session Priority              : 10

Tracks not Committed to the R2 Side: 0

Time that R2 is behind R1          : 00:00:00

RDFA R1 Side Percent Cache In Use  :  0

RDFA R2 Side Percent Cache In Use  :  0

 

 

       Source (R1) View                 Target (R2) View     MODES

----------------------    ------------------------ ----- -----------

            ST                  LI    ST

Standard     A                   N     A

Logical      T  R1 Inv   R2 Inv  K     T  R1 Inv   R2 Inv   RDF Pair

Device  Dev  E  Tracks   Tracks  S Dev E  Tracks   Tracks  MDAC STATE

----------------------- -- ------------------------ ---- -----------

 

DEV001  00E1 RW    0      12605 RW 00E1 WD    0      2037 C.D.  SyncInProg

DEV002  00E2 RW    0          0 RW 00E2 WD    0        0  C.D.  Synchronized

DEV003  00E3 RW    0          0 RW 00E3 WD    0        0  C.D.  Synchronized

DEV004  00E4 RW    0       5570 RW 00E4 WD    0        0  C.D.  SyncInProg

 

Total          -------- --------           -------- --------

  Track(s)           0    18175                  0   2037

  MB(s)             0.0    568.0                0.0     63.7

 

Legend for MODES:

 

 M(ode of Operation): A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

 D(omino)           : X = Enabled, . = Disabled

 A(daptive Copy)    : D = Disk Mode, W = WP Mode, . = ACp off

 C(onsistency State): X = Enabled, . = Disabled, - = N/A

Task 8:     Change the SRDF mode to asynchronous

                       

   1. [   ]    When the number of invalid tracks falls below 30,000, type the symrdf –g GroupName set mode async command to change the mode of the group to asynchronous.

To change the mode for group pocsun100data to asynchronous:

symrdf -g pocsun100data set mode async –nop

 

 An RDF Set 'Asynchronous Mode' operation execution is in

 progress for device group 'pocsun100data'. Please wait...

 

 The RDF Set 'Asynchronous Mode' operation successfully executed

 for device group 'pocsun100data'.

 

   2. [   ]    Type the symrdf –g GroupName query –rdfa –i Seconds command to confirm the change and monitor the number of tracks not commited to the R2 side.

To display/monitor group pocsun100data every 5 seconds:

symrdf -g pocsun100data query -rdfa -i 5

 

Device Group (DG) Name             : pocsun100data

DG's Type                          : RDF1

DG's Symmetrix ID                  : 000187461502

 

RDFA Session Number                : 34

RDFA Cycle Number                  : 1

RDFA Session Status                : Active

RDFA Minimum Cycle Time            : 00:00:30

RDFA Avg Cycle Time                : 00:00:30

Duration of Last cycle             : 00:00:00

RDFA Session Priority              : 10

Tracks not Committed to the R2 Side: 5067

Time that R2 is behind R1          : 00:00:11

RDFA R1 Side Percent Cache In Use  :  0

RDFA R2 Side Percent Cache In Use  :  0

 

       Source (R1) View                 Target (R2) View     MODES

---------------------    ------------------------ ----- -----------

           ST                  LI    ST

Standard    A                   N     A

Logical     T  R1 Inv   R2 Inv  K     T  R1 Inv   R2 Inv    RDF Pair

Device  Dev E  Tracks   Tracks  S Dev E  Tracks   Tracks sMDAC  STATE

-------------------------------- -- -------------- ----- -----------

 

DEV001  00E1 RW    0        0 RW 00E1 WD      0        0 A...  Consistent

DEV002  00E2 RW    0        0 RW 00E2 WD      0        0 A...  Consistent

DEV003  00E3 RW    0        0 RW 00E3 WD      0        0 A...  Consistent

DEV004  00E4 RW    0        0 RW 00E4 WD      0        0 A...  Consistent

 

Total          -------- --------           -------- --------

  Track(s)            0        0                  0        0

  MB(s)             0.0      0.0                0.0      0.0

 

Legend for MODES:

 

 M(ode of Operation): A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

 D(omino)           : X = Enabled, . = Disabled

 A(daptive Copy)    : D = Disk Mode, W = WP Mode, . = ACp off

 C(onsistency State): X = Enabled, . = Disabled, - = N/A

 

Interpreting the output

·        RDFA Cycle Number – 1 indicates SRDF/A is in the first cycle since activation.

·        RDFA Session Status is Active – SRDF/A session has been successful activated.

·        Duration of Last cycle – 00:00 indicates no cycles prior to the current cycle have completed

·        Tracks not Committed to the R2 Side - 5,067 invalid tracks are marked as write pending on the R2 side.

·        Time that R2 is behind R1 – 00:00:11 indicates that data marked as write pending on the R2 side is 11 seconds behind the current image on the R1 side.

 

   3. [   ]    If necessary, repeat the symrdf –g GroupName query –rdfa command to monitor the number of Tracks not Commited to the R2 Side until the value falls to 0.

For example:

symrdf -g pocsun100data query –rdfa

 

Device Group (DG) Name             : pocsun100data

DG's Type                          : RDF1

DG's Symmetrix ID                  : 000187461502

 

RDFA Session Number                : 34

RDFA Cycle Number                  : 26

RDFA Session Status                : Active

RDFA Minimum Cycle Time            : 00:00:30

RDFA Avg Cycle Time                : 00:00:30

Duration of Last cycle             : 00:00:30

RDFA Session Priority              : 10

Tracks not Committed to the R2 Side: 0

Time that R2 is behind R1          : 00:00:49

RDFA R1 Side Percent Cache In Use  :  0

RDFA R2 Side Percent Cache In Use  :  0

.

.

.

Task 9:     Enable and verify consistency protection

                       

   1. [   ]    Type the symrdf –g GroupName enable command to enable SRDF/A consistency protection.

To enable consistency for group pocsun100data:

symrdf -g pocsun100data enable –nop

 

 An RDF 'Enable' operation execution is

 in progress for device group 'pocsun100data'. Please wait...

 

 The RDF 'Enable' operation successfully executed for

 device group 'pocsun100data'.

 

   2. [   ]    Wait one full RDFA cycle for consistency mode to activate.

   3. [   ]    Type the symsrdf –g GroupName query –rdfa command to confirm normal operations.

In the following example:

·    Device group pocsun100data is running in normal SRDF/A operations

·    SRDF/A session number is 34 with a session priority of 10.

·    The SRDF/A session status for device group pocsun100data is active.

If you performed the same query on a device group that was in an RDF mode other than asynchronous, this value would say inactive because there would be no associated SRDF/A session.

·    Cycle time statistics (minimum cycle time, average cycle time, and the actual duration time of the last cycle) are normal.

The default SRDF/A cycle time is 30 seconds. R2 devices are two cycle sets behind the R1 devices. R2 devices should be behind the R1 device by ~60 seconds. See “Time that R2 is behind R1” value.

These values are snapshots and should be considered approximate numbers.

·    The session is operating in asynchronous mode (A)

·    RDFA consistency protection is enabled (X) (“A..X”).

·    RDF pair state is consistent.

The consistent state is the normal state of operation for device pairs in asynchronous mode

symrdf -g pocsun100data query –rdfa

 

 Device Group (DG) Name             : pocsun100data

 DG's Type                          : RDF1

 DG's Symmetrix ID                  : 000187461502

 

 RDFA Session Number                : 34

 RDFA Cycle Number                  : 28

 RDFA Session Status                : Active

 RDFA Minimum Cycle Time            : 00:00:30

 RDFA Avg Cycle Time                : 00:00:30

 Duration of Last cycle             : 00:00:30

 RDFA Session Priority              : 10

 Tracks not Committed to the R2 Side: 0

 Time that R2 is behind R1          : 00:00:48

 RDFA R1 Side Percent Cache In Use  :  0

 RDFA R2 Side Percent Cache In Use  :  0

 

 

        Source (R1) View                 Target (R2) View     MODES

 ----------------------    ------------------------ ----- ----------

            ST                  LI     ST

 Standard    A                   N      A

 Logical     T  R1 Inv   R2 Inv  K      T  R1 Inv  R2 Inv  RDF Pair

 Device  Dev E  Tracks   Tracks  S Dev  E  Tracks  Tracks MDAC STATE

 ---------------------- -- ------------------------ ----- ----------

 

 DEV001  00E1 RW    0      0    RW 00E1 WD      0      0  A..X Consistent

 DEV002  00E2 RW    0      0    RW 00E2 WD      0      0  A..X Consistent

 DEV003  00E3 RW    0      0    RW 00E3 WD      0      0  A..X Consistent

 DEV004  00E4 RW    0      0    RW 00E4 WD      0      0  A..X Consistent

 

 Total          -------- --------           -------- --------

   Track(s)            0        0                  0        0

   MB(s)             0.0      0.0                0.0      0.0

 

 Legend for MODES:

 

  M(ode of Operation): A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

  D(omino)           : X = Enabled, . = Disabled

  A(daptive Copy)    : D = Disk Mode, W = WP Mode, . = ACp off

 C(onsistency State): X = Enabled, . = Disabled, - = N/A