bcv split

can you post output of "symdg show oradba" and symmir -g oradba query"

symmir -g oradba query

Device Group (DG) Name: oradba
DG's Type             : REGULAR
DG's Symmetrix ID     : 0000000123
 
 
        Standard Device Name           Directors              Device
----------------------------------   ------------- ----------------------------
                                                                           Cap
Logical     Physical          Sym    SA :P DA :IT  Config        Att Sts   (MB)
----------------------------------   ------------- ----------------------------
 
DEV001      Not Visible       0177 + ???:? 02A:CF  2-Way Mir         RW   11866
DEV002      Not Visible       0181 + ???:? 16B:D11 2-Way Mir         RW   11866
DEV003      Not Visible       0182 + ???:? 15C:D11 2-Way Mir         RW   11866
DEV004      Not Visible       019F + ???:? 16A:C3  2-Way Mir         RW   11866
DEV005      Not Visible       013A + ???:? 15B:C3  2-Way Mir         RW   11866
DEV006      Not Visible       013B + ???:? 01B:D10 2-Way Mir         RW   11866
DEV007      Not Visible       013C + ???:? 02C:D10 2-Way Mir         RW   11866
DEV008      Not Visible       013D + ???:? 01D:D10 2-Way Mir         RW   11866
 
Legend for STD devices:
 
(+): Paired with a BCV device that is associated with this dg.
(-): Paired with a BCV device that is non-associated with this dg.
 
 
BCV Devices associated with this dg:
 
             BCV Device                    Standard Device          Status
------------------------------------ --------------------------- ------------
                              Inv.                        Inv.
Logical         Sym  RDF Att. Tracks Logical         Sym  Tracks BCV <=> STD
------------------------------------ --------------------------- ------------
 
BCV001          08BA        +      0 DEV001          0177      0 Split
BCV002          08BB        +      0 DEV002          0181      0 Split
BCV003          08BC        +      0 DEV003          0182      0 SplitBfrSync
BCV004          08BD        +      0 DEV004          019F      0 Split
BCV005          08BE        +      0 DEV005          013A      0 Split
BCV006          08BF        +      0 DEV006          013B      0 Split
BCV007          08C0        +      0 DEV007          013C      0 Split
BCV008          08C1        +      0 DEV008          013D      0 Split
 
Total                       --------                    --------
  Track(s)                         0                           0
  MB(s)                          0.0                         0.0
 
 
Legend for BCV devices:
 
(+): BCV is paired with a member STD device.
(-): BCV is paired with a non-member STD device.

symdg show oradba

Group Name:  oradba
 
    Group Type                                   : REGULAR
    Device Group in GNS                          : No
    Valid                                        : Yes
    Symmetrix ID                                 : 0000000123
    Group Creation Time                          : Wed May  9 11:05:28 2007
    Vendor ID                                    : EMC Corp
    Application ID                               : SYMCLI
 
    Number of STD Devices in Group               :    8
    Number of Associated GK's                    :    0
    Number of Locally-associated BCV's           :    8
    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):    0
    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 (8):
        {
        --------------------------------------------------------------------
                                                      Sym               Cap
        LdevName              PdevName                Dev  Att. Sts     (MB)
        --------------------------------------------------------------------
        DEV001                N/A                     0177      RW     11866
        DEV002                N/A                     0181      RW     11866
        DEV003                N/A                     0182      RW     11866
        DEV004                N/A                     019F      RW     11866
        DEV005                N/A                     013A      RW     11866
        DEV006                N/A                     013B      RW     11866
        DEV007                N/A                     013C      RW     11866
        DEV008                N/A                     013D      RW     11866
        }
 
    BCV Devices Locally-associated (8):
        {
        --------------------------------------------------------------------
                                                      Sym               Cap
        LdevName              PdevName                Dev  Att. Sts     (MB)
        --------------------------------------------------------------------
        BCV001                rdmp/c4t50060482D52E43* 08BA      RW     11866
        BCV002                rdmp/c4t50060482D52E43* 08BB      RW     11866
        BCV003                rdmp/c4t50060482D52E43* 08BC      NR     11866
        BCV004                rdmp/c4t50060482D52E43* 08BD      RW     11866
        BCV005                rdmp/c4t50060482D52E43* 08BE      RW     11866
        BCV006                rdmp/c4t50060482D52E43* 08BF      RW     11866
        BCV007                rdmp/c4t50060482D52E43* 08C0      RW     11866
        BCV008                rdmp/c4t50060482D52E43* 08C1      RW     11866
        }
 

why is BCV003 NR, was this an unprotected BCV ?

You have to full establish the affected pair. It's already "splitted" (due to a drive failure). Now you have to fully establish the pair and later split it again.

It's "SpltBfrSync" .. or "Split before sync" for human readers

you typically see unprotected BCVs used for some sort of backup operations, it's ok to lose a BCV since it will get re-sync anyway. So the failed drive has been replaced now ?

there was a drive failure and the bcv dev got effected.
this is our standard we use unprotected BCV, but how did you figured that out.

yes, the failed drive was replaced.

now how do we go about this

symmir -g diskgrp -full establish DEV00n BCV ld BCV00n
symmir -g diskgrp split instant DEV00n BCV ld BCV00n

will this work out or I am missing some extra switches

thank you ..typo

symmir -g oradba establish DEV001 bcv ld BCV003 -full

might need to add "-force" if it does not take it like that.

BCV003 is NR since it was syncing when the drive broke. Now BCV003 is NR (and its status is "split before sync") thus you have to "clean up" things with a full establish of BCV003 with its corresponding STD device. It looks like Dynamox is already showing you examples.

As he said, be ready to drop in a couple of "-force" or "-symforce" in case symmir complains

but one of the dev is NR. so can we do an est in this case?

I'd use DEV003 as SRC

try symcfg discover and then run symdev show on that BCV ..see if it's really NR.