UNSOLVED

storey1

updated

16 years ago

S

storey1

13 Posts

1

11641

November 16th, 2010 22:00

How do I add device to existing srdf/a protection on DMX-3

I already have srdf/a protection and device group in operation.

I want to add one single meta to this protection.

Here is what I propose to do.

add the single source device to the existing rdf group.

1.    symld -sid 999 -g devgrpname add dev xxx

2.    Then create a file with source production dev and rdf device called  rdf.cmd

3.     then run this command to create pair relationship.

symrdf createpair -g  devgrpname -f rdf.cmd -sid 999 -rdfg 5 -type rdf1 -invalidate R2

4    then I wish  to establish using

      symrdf -file rdf.cmd -sid 999 -rdfg 5 establish.

I wish to set the establish to adaptive copy disk mode for this new device pair as I dont want to affect the production device performance while synching.

Can I do this for just the pair of devices ?. Also the first step returns an error saying

Cannot add a non R1 device to a device group of RDF R1 devices..

..the devs are

Dynamic RDF Capability   : RDF1_OR_RDF2_Capable

  • PedalHarder

    4 Apprentice

    •

    465 Posts

    2449

    1

    Posted November 16th, 2010 23:00

    To do this seamlessly you need 5773 microcode on your DMX3, and a resent version of Solutions Enabler. These things give you access to the MOVEPAIR / Consistency Exempt  functionality. The MOVEPAIR allows an existing SRDF device to be moved from  one RDF group to another. The Consistency Exempt feature allows a device NOT to be in step with all other devices in an existing SRDF/A group.

    Here is what you do:
    - SRDF/A remains active at all times.

    - Create an RDF group for the purposes of initial synch up.

    - Do the create pair to the synch-up RDF group.

    - Synch the device in Adaptive copy mode.

    - suspend the device with the -cons_exempt option

    - perform a symrdf MOVEPAIR to move the new device into the SRDF/A group

    - on the new device (not sure if this step is required from memory)

    - symrdf resume the device

    - The consistency exempt flag will go away automatically once the device is in srdf/a mode with no invalid tracks (in lock step with all other devices)

    - now you can add the device into the device group.

  • Booyah2

    2 Intern

    •

    185 Posts

    2449

    0

    Posted November 17th, 2010 04:00

    'Cannot add a non R1 device to a device group of RDF R1 devices.."

    ..the devs are

    Dynamic RDF Capability   : RDF1_OR_RDF2_Capable

    Check to be sure your new device is DYNAMIC RDF device before adding it to the RDF Group.

    REMINDER:

    If you find any of the replies to your question as helpful, please be so kind as to mark replies as being "helpful" or "answered". This helps us track our success with the Forum.

  • Booyah2

    2 Intern

    •

    185 Posts

    2449

    0

    Posted November 17th, 2010 05:00

    This should read:

    Check to be sure your new device is DYNAMIC RDF device before adding it to the "DEVICE GRP OF RDF R1 DEVICES".

  • storey1

    13 Posts

    2449

    0

    Posted November 17th, 2010 14:00

    Yes the devices are dynamic_rdf .

    I have  5773 code.

    and solutions enabler  7.1.2

    Any other ideas on why it wouldnt allow me to add it to the rdf group with error

  • Boom1

    131 Posts

    2449

    0

    Posted November 17th, 2010 15:00

    Create pair first, and add device later to device group.

    symrdf createpair -f pair.cmd -type r1 -sid xxx -rdfg xxx -invalidate r2

    For Adptive copy..

    symrdf -file xxx -sid xxx -rdfg xxx set mode acp_disk -noprompt

    symrdf -file pair.cmd -sid xxx -rdfg xx establish -full -noprompt

    symld -sid xxx -g xxx add dev xxx

  • ahmad_faraz

    22 Posts

    2450

    0

    Posted September 21st, 2011 16:00

    As per my understanding below are the steps required to add the devices to already running device group in SRDF/A

    1) first the consistency needs to be disabled for the already running device group

    2) Local devices and remote device need to be put in the file

    3) create pair

    4) establish

    5) set the Device in file to the adaptive copy mode

    6) set the device group in the adaptive copy mode also

    7)Add the device to device group

    8) Once the invalid tracks go below 30,000K

    9) Set the device group to Async mode

    10) enable consistancy to th device group.

    Please correct me if the steps are wrong ...or how exactly the steps follows

    Reply will much appretiated

  • 2450

    0

    Posted September 21st, 2011 17:00

    Looks good to me. However you can skip a step of disabling consisteny by using the cons_exempt option while running the createpair command. This option will exempt the newly created device from consistency and allow this non consistent pair to be added to the consistent group. After two cycles, your newly added devicepair will become consistent..

    cons_exempt is available from 5773.

    regards,

    Saurabh

  • SKT2

    2 Intern

    •

    1340 Posts

    1894

    0

    Posted September 24th, 2011 09:00

    on step 8, its not 30,000K , it is 30,000 tracks; considerring each track 64KB(128 blocks of 512 bytes) then when you are close to 2GB left to sycn you may put in async mode.

    what do you say Saurabh?

  • 1894

    0

    Posted September 25th, 2011 01:00

    yeah i missed that out, it should be 30,000 tracks not 30,000k.

    nice catch

    regards,

    Saurabh

  • SKT2

    2 Intern

    •

    1340 Posts

    1602

    0

    Posted September 27th, 2011 06:00

    Do you see any document metioned cons_exempt being enabled from a  particular code level?. I searched in couple of RN  i have and did not get  a hit at all.