SamClaret
2 Iron

Re: Removing a STD-BCV relationship

Hello

There are 2 correct methods to cancel a relationship like this.

1) create a file and use the symmir cancel -f option

2) create a device group and use the symmir cancel -g option

If neither of these are working then you will need to open a Service Request with EMC and the PSE Lab will ultimately have to investigate.

It is possible that you have an orphaned SDDF session or some such. The software will not be able to fix that.

Thankyou

Sam Claret EMC TSE3

0 Kudos
rworkman1
2 Bronze

Re: Removing a STD-BCV relationship

Just a suggestion...

Now that they are back together, do a clean split command.

Check to ensure the dg does in fact show a nice clean 'split' status.

If it does, then (without a hammer) try using the old command symbcv -g <name> disassociate dev <bcv-symdev#>

...double check on the syntax...I'm not at a machine right now.

One it disassociates, then remove the std device from the dg and get rid of the test-dg

Just a thought,

Rita

0 Kudos
xe2sdc
4 Ruthenium

Re: Removing a STD-BCV relationship

I guess customers don't usually use inlines 😉

0 Kudos
mugurstef
2 Bronze

Re: Removing a STD-BCV relationship

Hi,

@rworkman,

Here it is:

symmir -g testdg split -instant

Execute 'Split' operation for device group
'testdg' (y/) ? y

'Split' operation execution is in progress for
device group 'testdg'. Please wait...

'Split' operation successfully executed for device group
'testdg'.

symdg show testdg

Group Name:  testdg

    Group Type                                   : REGULAR
    Device Group in GNS                          : Yes
    Valid                                        : Yes
    Symmetrix ID                                 : xxx
    Group Creation Time                          : Fri Jan 14 08:18:00 2011
    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           :    1
    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
    Number of Remotely-assoc'd BCV's (Hop-2 BCV) :    0
    Number of Remotely-assoc'd VDEV's(Hop-2 VDEV):    0
    Number of Remotely-assoc'd TGT's (Hop-2 TGT) :    0

    Standard (STD) Devices (1):
        {
        --------------------------------------------------------------------
                                                      Sym               Cap
        LdevName              PdevName                Dev  Att. Sts     (MB)
        --------------------------------------------------------------------
        DEV000                N/A                     01D7 (M)  NR    138105
    symdg show testdg

Group Name:  testdg

    Group Type                                   : REGULAR
    Device Group in GNS                          : Yes
    Valid                                        : Yes
    Symmetrix ID                                 : xxx
    Group Creation Time                          : Fri Jan 14 08:18:00 2011
    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           :    1
    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
    Number of Remotely-assoc'd BCV's (Hop-2 BCV) :    0
    Number of Remotely-assoc'd VDEV's(Hop-2 VDEV):    0
    Number of Remotely-assoc'd TGT's (Hop-2 TGT) :    0

    Standard (STD) Devices (1):
        {
        --------------------------------------------------------------------
                                                      Sym               Cap
        LdevName              PdevName                Dev  Att. Sts     (MB)
        --------------------------------------------------------------------
        DEV000                N/A                     01D7 (M)  NR    138105
        }

    BCV Devices Locally-associated (1):
        {
        --------------------------------------------------------------------
                                                      Sym               Cap
        LdevName              PdevName                Dev  Att. Sts     (MB)
        --------------------------------------------------------------------
        BCV000                N/A                     028F (M)  RW    138105
        }

symmir -g testdg query

Device Group (DG) Name: testdg
DG's Type             : REGULAR
DG's Symmetrix ID     : 000000001129


     Standard Device                    BCV Device                  State
-------------------------- ------------------------------------- ------------
                    Inv.                                  Inv.
Logical        Sym  Tracks Logical              Sym       Tracks STD <=> BCV
-------------------------- ------------------------------------- ------------

DEV000         01D7      0 BCV000               028F *         0 Split

Total              -------                               -------
  Track(s)               0                                     0
  MB(s)                0.0                                   0.0

Legend:

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

symbcv -g testdg disassociate dev 028F   (without a hammer )

Cannot proceed when the device is paired in a Copy Session except if the force flag is used

symbcv -g testdg disassociate ld BCV000 

Cannot proceed when the device is paired in a Copy Session except if the force flag is used

@samclaret

I tried:

symmir -g testdg cancel DEV000 bcv dev 028F

Execute 'Cancel' operation for device 'DEV000'
in device group 'testdg' (y/) ? y

'Cancel' operation execution is in progress for device 'DEV000'
paired with BCV device '028F' in
device group 'testdg'. Please wait...

'Cancel' operation successfully executed for device 'DEV000'
in group 'testdg' paired with BCV device '028F'.

symdev -sid 129 show 028F

    Device Physical Name     : Not Visible

    Device Symmetrix Name    : 028F
    Device Serial ID         : N/A
    Symmetrix ID             : xxx

    Device Group Name        : testdg
    Device Logical Name      : BCV000

    Attached VDEV TGT Device : N/A

    Vendor ID                : EMC
    Product ID               : SYMMETRIX
    Product Revision         : 5772
    Device WWN               : xxx
    Device Emulation Type    : FBA
    Device Defined Label Type: N/A
    Device Defined Label     : N/A
    Device Sub System Id     : 0x0003
    Cache Partition Name     : DEFAULT_PARTITION

    Device Block Size        : 512

    Device Capacity
        {
        Cylinders            :     147312
        Tracks               :    2209680
        512-byte Blocks      :  282839040
        MegaBytes            :     138105
        KiloBytes            :  141419520
        }

    Device Configuration     : 2-Way BCV Mir   (Meta Head,
                                                Non-Exclusive Access)

    Device is WORM Enabled   : No
    Device is WORM Protected : No

    SCSI-3 Persistent Reserve: Disabled

    Dynamic Spare Invoked    : No

    Dynamic RDF Capability   : None

    STAR Mode                : No
    STAR Recovery Capability : None
    STAR Recovery State      : NA

    Device Service State     : Normal

    Device Status            : Ready            (RW)
    Device SA Status         : N/A              (N/A)

    Meta Configuration       : Striped
    Meta Stripe Size         : 960k    (1 Cylinders)
    Meta Device Members (8)  :
        {
        ----------------------------------------------------------------------
                               BCV  DATA                    RDF  DATA
                      ----------------------------  --------------------------
        Sym    Cap    Std Inv BCV Inv Pair          R1 Inv R2 Inv Pair
        Dev    (MB)   Tracks  Tracks  State         Tracks Tracks State
        ----------------------------------------------------------------------
    --> 028F  17263        0       0  SplitNoInc         -      - N/A
        0290  17263        0       0  SplitNoInc         -      - N/A
        0291  17263        0       0  SplitNoInc         -      - N/A
        0292  17263        0       0  SplitNoInc         -      - N/A
        0293  17263        0       0  SplitNoInc         -      - N/A
        0294  17263        0       0  SplitNoInc         -      - N/A
        0295  17263        0       0  SplitNoInc         -      - N/A
        0296  17263        0       0  SplitNoInc         -      - N/A
        ----------------------------------------------------------------------
             138105        0       0                     -      -
        }

    Mirror Set Type          : [Data,Data,N/A,N/A]

    Mirror Set DA Status     : [RW,RW,N/A,N/A]

    Mirror Set Inv. Tracks   : [0,0,0,0]

    Back End Disk Director Information
        {
        Hyper Type                             : Data
        Hyper Status                           : Ready           (RW)
        Disk [Director, Interface, TID]        : [05C, D, 3]
        Disk Director Volume Number            :  140 (0x8B)
        Hyper Number                           :    9
        Mirror Number                          : 1
        Disk Capacity                          : 140014m
        Disk Group Number                      : 1
        Disk Group Name                        : DISK_GROUP_001

        Hyper Type                             : Data
        Hyper Status                           : Ready           (RW)
        Disk [Director, Interface, TID]        : [15C, D, 3]
        Disk Director Volume Number            :  140 (0x8B)
        Hyper Number                           :    9
        Mirror Number                          : 2
        Disk Capacity                          : 140014m
        Disk Group Number                      : 1
        Disk Group Name                        : DISK_GROUP_001
        }

    BCV Pair Information
        {
        Standard (STD) Device Symmetrix Name   : 01D7
        Standard (STD) Device Serial ID        : Not Visible
        Standard (STD) Device Group Name       : testdg
        Standard (STD) Composite Group Name    : Not/Grouped

        BCV Device Symmetrix Name              : 028F
        BCV Device Serial ID                   : Not Visible
        BCV Device Associated Group Name       : testdg
        BCV Device Associated CG Name          : Not/Associated

        BCV Device Status                      : Ready           (RW)

        State of Pair ( STD < \ > BCV )        : SplitNoInc
        Time of Last BCV Action                : N/A

        State of BCV Mirrors                   : Synchronized

        BCV State Flags                        : (AllReady)
        Percent Split                          : 100%

        Number of Inv. Tracks for STD Device   : 0
        Number of Inv. Tracks for BCV Device   : 0
        }

It seems that I'll have to open a Service Request for this problem. I really don't know what could have happened.

Thank you,

Message was edited by: SymmetrixForumsModerator Modified Symmetrix ID.

0 Kudos
PaulCork
3 Argentium

Re: Removing a STD-BCV relationship

Have you tried running a symmir –g group cancel ? Then run the disassociate.

The disassociate is removing the BCV from the group it is asking for the force because it rightly detects that there is a valid relationship there, adding the force flag is telling the software you realize that there is a relationship but you want to remove the device anyway.

Disassociating will not get rid of the copy session which is in essence the relationship you must first run the cancel to clear the relationship.

0 Kudos
mugurstef
2 Bronze

Re: Removing a STD-BCV relationship

@Paul Martin

Starting from the following status:

symmir -g testdg query

Device Group (DG) Name: testdg
DG's Type             : REGULAR
DG's Symmetrix ID     : xxx


     Standard Device                    BCV Device                  State
-------------------------- ------------------------------------- ------------
                    Inv.                                  Inv.
Logical        Sym  Tracks Logical              Sym       Tracks STD <=> BCV
-------------------------- ------------------------------------- ------------

DEV000         01D7      0 BCV000               028F *         0 Synchronized

Total              -------                               -------
  Track(s)               0                                     0
  MB(s)                0.0                                   0.0

Legend:

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

symmir -g testdg split -instant

Execute 'Split' operation for device group
'testdg' (y/) ? y

'Split' operation execution is in progress for
device group 'testdg'. Please wait...

'Split' operation successfully executed for device group
'testdg'.

symmir -g testdg query

Device Group (DG) Name: testdg
DG's Type             : REGULAR
DG's Symmetrix ID     : 000000001129


     Standard Device                    BCV Device                  State
-------------------------- ------------------------------------- ------------
                    Inv.                                  Inv.
Logical        Sym  Tracks Logical              Sym       Tracks STD <=> BCV
-------------------------- ------------------------------------- ------------

DEV000         01D7      0 BCV000               028F *         0 Split

Total              -------                               -------
  Track(s)               0                                     0
  MB(s)                0.0                                   0.0

Legend:

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

symmir -g testdg cancel DEV000 bcv dev 028F

Execute 'Cancel' operation for device 'DEV000'
in device group 'testdg' (y/) ? y

'Cancel' operation execution is in progress for device 'DEV000'
paired with BCV device '028F' in
device group 'testdg'. Please wait...

'Cancel' operation successfully executed for device 'DEV000'
in group 'testdg' paired with BCV device '028F'.

symbcv -g testdg disassociate ld BCV000

symdg show testdg

Group Name:  testdg

    Group Type                                   : REGULAR
    Device Group in GNS                          : Yes
    Valid                                        : Yes
    Symmetrix ID                                 : 000000001129
    Group Creation Time                          : Fri Jan 14 08:18:00 2011
    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):    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
    Number of Remotely-assoc'd BCV's (Hop-2 BCV) :    0
    Number of Remotely-assoc'd VDEV's(Hop-2 VDEV):    0
    Number of Remotely-assoc'd TGT's (Hop-2 TGT) :    0

    Standard (STD) Devices (1):
        {
        --------------------------------------------------------------------
                                                      Sym               Cap
        LdevName              PdevName                Dev  Att. Sts     (MB)
        --------------------------------------------------------------------
        DEV000                N/A                     01D7 (M)  NR    138105
        }

As you can see from the following command nothing changed for the device 028F:

symdev -sid xxx show 028F

    Device Physical Name     : Not Visible

    Device Symmetrix Name    : 028F
    Device Serial ID         : N/A
    Symmetrix ID             : xxx

    Attached VDEV TGT Device : N/A

    Vendor ID                : EMC
    Product ID               : SYMMETRIX
    Product Revision         : 5772
    Device WWN               : xxx
    Device Emulation Type    : FBA
    Device Defined Label Type: N/A
    Device Defined Label     : N/A
    Device Sub System Id     : 0x0003
    Cache Partition Name     : DEFAULT_PARTITION

    Device Block Size        : 512

    Device Capacity
        {
        Cylinders            :     147312
        Tracks               :    2209680
        512-byte Blocks      :  282839040
        MegaBytes            :     138105
        KiloBytes            :  141419520
        }

    Device Configuration     : 2-Way BCV Mir   (Meta Head,
                                                Non-Exclusive Access)

    Device is WORM Enabled   : No
    Device is WORM Protected : No

    SCSI-3 Persistent Reserve: Disabled

    Dynamic Spare Invoked    : No

    Dynamic RDF Capability   : None

    STAR Mode                : No
    STAR Recovery Capability : None
    STAR Recovery State      : NA

    Device Service State     : Normal

    Device Status            : Ready            (RW)
    Device SA Status         : N/A              (N/A)

    Meta Configuration       : Striped
    Meta Stripe Size         : 960k    (1 Cylinders)
    Meta Device Members (8)  :
        {
        ----------------------------------------------------------------------
                               BCV  DATA                    RDF  DATA
                      ----------------------------  --------------------------
        Sym    Cap    Std Inv BCV Inv Pair          R1 Inv R2 Inv Pair
        Dev    (MB)   Tracks  Tracks  State         Tracks Tracks State
        ----------------------------------------------------------------------
    --> 028F  17263        0       0  SplitNoInc         -      - N/A
        0290  17263        0       0  SplitNoInc         -      - N/A
        0291  17263        0       0  SplitNoInc         -      - N/A
        0292  17263        0       0  SplitNoInc         -      - N/A
        0293  17263        0       0  SplitNoInc         -      - N/A
        0294  17263        0       0  SplitNoInc         -      - N/A
        0295  17263        0       0  SplitNoInc         -      - N/A
        0296  17263        0       0  SplitNoInc         -      - N/A
        ----------------------------------------------------------------------
             138105        0       0                     -      -
        }

    Mirror Set Type          : [Data,Data,N/A,N/A]

    Mirror Set DA Status     : [RW,RW,N/A,N/A]

    Mirror Set Inv. Tracks   : [0,0,0,0]

    Back End Disk Director Information
        {
        Hyper Type                             : Data
        Hyper Status                           : Ready           (RW)
        Disk [Director, Interface, TID]        : [05C, D, 3]
        Disk Director Volume Number            :  140 (0x8B)
        Hyper Number                           :    9
        Mirror Number                          : 1
        Disk Capacity                          : 140014m
        Disk Group Number                      : 1
        Disk Group Name                        : DISK_GROUP_001

        Hyper Type                             : Data
        Hyper Status                           : Ready           (RW)
        Disk [Director, Interface, TID]        : [15C, D, 3]
        Disk Director Volume Number            :  140 (0x8B)
        Hyper Number                           :    9
        Mirror Number                          : 2
        Disk Capacity                          : 140014m
        Disk Group Number                      : 1
        Disk Group Name                        : DISK_GROUP_001
        }

    BCV Pair Information
        {
        Standard (STD) Device Symmetrix Name   : 01D7
        Standard (STD) Device Serial ID        : Not Visible
        Standard (STD) Device Group Name       : testdg
        Standard (STD) Composite Group Name    : Not/Grouped

        BCV Device Symmetrix Name              : 028F
        BCV Device Serial ID                   : Not Visible
        BCV Device Associated Group Name       : Not/Associated
        BCV Device Associated CG Name          : Not/Associated

        BCV Device Status                      : Ready           (RW)

        State of Pair ( STD < \ > BCV )        : SplitNoInc
        Time of Last BCV Action                : N/A

        State of BCV Mirrors                   : Synchronized

        BCV State Flags                        : (AllReady)
        Percent Split                          : 100%

        Number of Inv. Tracks for STD Device   : 0
        Number of Inv. Tracks for BCV Device   : 0
        }

Thank you,

Message was edited by: SymmetrixForumsModerator Modified Symmetrix ID.

0 Kudos
dynamox
6 Thallium

Re: Removing a STD-BCV relationship

what did you expect to see ?

0 Kudos
mugurstef
2 Bronze

Re: Removing a STD-BCV relationship

Hi,

Maybe I'm wrong but I want to see no sign of any relationship between 01D7 and 028F.

Do you think that from the above status I could use 028F as a STD device?

I cannot delete 028F or do anything else but to mirror 01D7 in a device group.

Again, sorry if I'm missing something obviuos.

Thank you,

0 Kudos
dynamox
6 Thallium

Re: Removing a STD-BCV relationship

from the steps you've completed above you should be able to delete it now, run in "preview" mode and see if it still errors out on you.  Why do you want to use BCV as a STD device ?

0 Kudos
mugurstef
2 Bronze

Re: Removing a STD-BCV relationship

Hi dynamox,

Output from the "delete dev 028F" with preview:

A Configuration Change operation is in progress. Please wait...

    Establishing a configuration change session...............Established.

    Error occurred while Defining change number 1:
    Cannot use the device for this function because it is a Copy Session source
    Device 028F generated the failure

    Terminating the configuration change session..............Done.

The configuration change session has failed.

I would like to use 028F as a standard device and along with other identical devices to be allocated to a host. The BCV feature of it was for a test only purpose.

Thank you,

0 Kudos