Trouphaz

updated

18 years ago

T

Trouphaz

2 Intern

•

70 Posts

0

4103

August 21st, 2008 12:00

Creating local copy of SRDF R2?

I am deploying a DMX and need to replace an existing process that is done on our HDS arrays using Symmetrix tools. Right now I'm just in the proof of concept phase, so I just need help configuring one device.

I have my production data on device 1B0 in my production array. I have an SRDF/A replica on my DR array on device 201. I also have a device 202 on the DR array that I'd like to create a copy on. Would I use Timefinder/Clone for this or BCV? Some documents say Clone but another says that a remote R2 replica has to be a BCV.

Can someone provide any insight into this process? I'm familiar with BCVs and Clones and would prefer to use Clones if I can due to their flexibility and how quickly they can be accessed. But, if BCVs are requred then I can make due.
  • xe2sdc

    6 Operator

    •

    2831 Posts

    2052

    0

    Posted August 26th, 2008 03:00

    You can use symld with an added twist ;-)

    symld -g Rdf1Grp add dev 202 -rdf -tgt
  • xe2sdc

    6 Operator

    •

    2831 Posts

    1538

    0

    Posted August 21st, 2008 12:00

    If you use your own scripts, you can use either TF/clone or TF/mirror ... You need to convert device 202 to BCV before being able to use TF/mirror. Are you using RAID5 to protect device 202 ??

    When you create copies off SRDF/A R2 devices remember to use precopy (if you use TF/clone) and learn how to wait a full precopy cycle before activating clones ;-)

    Can you please provide a link to the document saying you need BCVs on R2 side ??
  • Trouphaz

    2 Intern

    •

    70 Posts

    1538

    0

    Posted August 21st, 2008 12:00

    All of the devices in question are RAID5.
    I'm not sure if this link works, but here it is. It is Solutions Enabler Symmetrix TimeFinder Family CLI Product Guide 6.4 A09 that I found on Powerlink. The specific page is 158 where it is dealing with cloning a copy on a remote Symmetrix array. Step 2 finishes with "A remote target device must be a BCV."

    http://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/live1/en_US/Offering_Technical/Technical_Documentation/300-000-876_a09_elccnt_0.pdf?mtcs=ZXZlbnRUeXBlPUttQ2xpY2tDb250ZW50RXZlbnQsZG9jdW1lbnRJZD0wOTAxNDA2NjgwMjM2MGNhLG5hdmVOb2RlPVNvZndhcmVEb3dubG9hZHMtMQ__


    Are there any docs that walk you through this step by step? The only thing that I've found so far is that document I linked that only deals with BCVs.
  • xe2sdc

    6 Operator

    •

    2831 Posts

    1538

    0

    Posted August 21st, 2008 12:00

    Upgrade to 6.5 and enjoy ;-)

    Oh BTW you find exact same procedure (with an added twist of joy) at page 178 ]:)

    Message was edited by:
    Stefano Del Corno
  • Trouphaz

    2 Intern

    •

    70 Posts

    1538

    0

    Posted August 22nd, 2008 10:00

    Man, this is painful. I was able to create the R1 -> R2 -> Clone through ECC (creating the clone with precopy) and do the activate to make the data available to the host. When I try to do a recreate to update teh data, it comes back and says it can't be done with SRDF/A in async mode.

    I blew away the clone configuration and switched that device to a BCV. I'm following the steps exactly as they are in the manual for a remote BCV copy and it says the request is not allowed for SRDF/A-capable devices in async mode. I don't know if this is simply because the BCV device is RAID5 and thus actually a clone or what.
  • xe2sdc

    6 Operator

    •

    2831 Posts

    1538

    0

    Posted August 22nd, 2008 12:00

    Can you post commands you issued and resulting errors ?? I'm pretty curious since I clone SRDF/A R2 devices since S.E. 6.3 without glitches :-) ..I have to say I issue commands from R2 side (while you are on R1 side) however it works at least for me ;-)
  • Trouphaz

    2 Intern

    •

    70 Posts

    1538

    0

    Posted August 22nd, 2008 12:00

    I was going word for word from the document, though with the devices updated to my own. I was running all of these commands from the host that had control of the R1 device at our primary site. I also switched 202 from a standard device to a BCV (FYI: 202 is a RAID5 device)

    symdg create Rdf1Grp ¿type rdf1
    symld -g Rdf1Grp ¿sid add dev 1B0
    symbcv -g Rdf1Grp associate dev 202 -rdf
    symclone -g Rdf1Grp establish ¿full DEV001 bcv ld RBCV001 ¿rdf

    it was that last command that complained about SRDF/A-capable devices in async mode.
  • xe2sdc

    6 Operator

    •

    2831 Posts

    1538

    0

    Posted August 22nd, 2008 14:00

    Forgive me if I ask you more .. however can you post the exact error message you received from "symclone" command ??
  • Trouphaz

    2 Intern

    •

    70 Posts

    1538

    0

    Posted August 25th, 2008 08:00

    Actually, I don't have the error message anymore. I've already changed the device back from a BCV to a standard to go back to testing clones. If I get time later, I'll try it again.
  • Trouphaz

    2 Intern

    •

    70 Posts

    1538

    0

    Posted August 25th, 2008 10:00

    Here it goes:

    # symclone -g Rdf1Grp establish -full DEV001 bcv ld RBCV001 -rdf

    Execute remote 'Clone Full Establish' operation for device 'DEV001'
    in device group 'Rdf1Grp' (y/ ) ? y

    'Clone Full Establish' operation execution is in progress for device 'DEV001'
    paired with target device 'RBCV001' in
    device group 'Rdf1Grp'. Please wait...


    The request is not allowed for SRDF/A-capable devices in async mode



    Here is the output of symdg show Rdf1Grp:

    1# symdg show Rdf1Grp

    Group Name: Rdf1Grp

    Group Type : RDF1 (RDFA)
    Device Group in GNS : No
    Valid : Yes
    Symmetrix ID :
    Group Creation Time : Mon Aug 25 13:37:35 2008
    Vendor ID : EMC Corp
    Application ID : SYMCLI

    Number of STD Devices in Group : 1
    Number of Associated GK's : 0
    Number of Locally-associated BCV's : 0
    Number of Locally-associated VDEV's : 0
    Number of Locally-associated TGT's : 0
    Number of Remotely-associated VDEV's(STD RDF): 0
    Number of Remotely-associated BCV's (STD RDF): 1
    Number of Remotely-associated TGT's(TGT RDF) : 0
    Number of Remotely-associated BCV's (BCV RDF): 0
    Number of Remotely-assoc'd RBCV's (RBCV RDF) : 0

    Standard (STD) Devices (1):
    {
    --------------------------------------------------------------------
    Sym Cap
    LdevName PdevName Dev Att. Sts (MB)
    --------------------------------------------------------------------
    DEV001 rdmp/emcpower59s2 1B0 RW 35010
    }

    BCV Devices Remotely-associated (STD RDF) (1):
    {
    --------------------------------------------------------------------
    Sym Cap
    LdevName PdevName Dev Att. Sts (MB)
    --------------------------------------------------------------------
    RBCV001 N/A 0202 RW 35010
    }

    Device Group RDF Information
    {
    RDF Type : R1
    RDF (RA) Group Number : 3 (02)

    Remote Symmetrix ID :

    R2 Device Is Larger Than The R1 Device : False

    RDF Pair Configuration : Normal
    RDF STAR Mode : False

    RDF Mode : Asynchronous
    RDF Adaptive Copy : Disabled
    RDF Adaptive Copy Write Pending State : N/A
    RDF Adaptive Copy Skew (Tracks) : 65535

    RDF Device Domino : Disabled

    RDF Link Configuration : Fibre
    RDF Link Domino : Disabled
    Prevent Automatic RDF Link Recovery : Enabled
    Prevent RAs Online Upon Power ON : Enabled

    Device RDF Status : Ready (RW)

    Device RA Status : Ready (RW)
    Device Link Status : Ready (RW)

    Device Suspend State : N/A
    Device Consistency State : Disabled
    RDF R2 Not Ready If Invalid : Disabled

    Device RDF State : Ready (RW)
    Remote Device RDF State : Write Disabled (WD)

    RDF Pair State ( R1 <===> R2 ) : Consistent

    Number of R1 Invalid Tracks : 0
    Number of R2 Invalid Tracks : 0

    RDFA Information:
    {
    Session Number : 2
    Cycle Number : 8854
    Number of Devices in the Session : 1
    Session Status : Active

    Session Consistency State : Disabled
    Minimum Cycle Time : 00:00:30
    Average Cycle Time : 00:00:30
    Duration of Last cycle : 00:00:30
    Session Priority : 33

    Tracks not Committed to the R2 Side: 4
    Time that R2 is behind R1 : 00:00:50
    R1 Side Percent Cache In Use : 0
    R2 Side Percent Cache In Use : 0

    Transmit Idle Time : 00:00:00
    R1 Side DSE Used Tracks : 0
    R2 Side DSE Used Tracks : 0
    }
    }