mugurstef
2 Bronze

Removing a STD-BCV relationship

Hello,

I cannot remove a STD-BCV relationship between 2 DMX3 devices.

DMX3 has 5772 MCode version.

The 2 devices are 2 meta devices (config=striped on 8 members):

01D7 - STD dev.

028F - BCV dev.

In this moment "State of Pair" (from symdev -sid xxx show 028F) is "SplitNoInc".

01D7 Not Visible            ???:? 05C:C2  2-Way Mir     N/Grp'd  (M) NR  138105

028F Not Visible            ???:? 05C:D3  2-Way BCV Mir N/Asst'd (M) RW  138105

Do you have any ideas?

Regards,

Mugur

Tags (3)
0 Kudos
38 Replies
xe2sdc
4 Ruthenium

Re: Removing a STD-BCV relationship

AFAIK you can't cancel relations. When you issue a "symdev" command against a specific device, the CLI (through Enginuity) will always report the last relationship that involved your device, even if the devices aren't still in the same devicegroup. The only way you have to cancel this relation is to create new relations...

Don't overestimate what symcli is telling you via the symdev command: it simply means that somewhere in the past you bound the two devices using symbcv. And since that time you didn't create different relations involving your devices. Nothing less, nothing more. 🙂

You can enjoy a full discussion on this topic here:

https://community.emc.com/message/400313

0 Kudos
Highlighted
mugurstef
2 Bronze

Re: Removing a STD-BCV relationship

It appears to me that I cannot do anything with these 2 devices.

I tried to delete both of them and it failed.

I tried "delete dev 01D7" (01D7 - STD dev) and it gave me:

COMMIT monitoring failed

    Error occurred while Committing
    The state of a snap session is blocking the activation of the new configuration. Please see the API log file

I tried "delete dev 028F" (028F - BCV dev) and it gave me:

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

I even tried to associate 028F in a new device group with another STD device and this failed too.

Thank you,

0 Kudos
xe2sdc
4 Ruthenium

Re: Removing a STD-BCV relationship

It looks like you are using timefinder emulation.

You have to cancel existing relation before removing the devices.

Just one question: why are you trying to remove this relation?

0 Kudos
mugurstef
2 Bronze

Re: Removing a STD-BCV relationship

Cancelling by "symmir -sid xxx -f bcv_temp cancel"  where bcv_temp file contains "01D7 028F" is not working:

"Execute 'Cancel' operation for the 1 specified device(s)
in device file 'bcv_temp' (y/) ? y

'Cancel' operation execution is in progress for the device list in
device file 'bcv_temp'. Please wait...

Cannot proceed because the device does not have any BCV pairing relationship"

I have to use both devices as 2 STD devices without any relationship between them. They are now one STD device and one BCV device because I have used them for testing (to increase the size of a meta striped device while maintaining the existent data).

From the symdev -sid xxx show 028F:

BCV Pair Information
        {
        Standard (STD) Device Symmetrix Name   : 01D7
        Standard (STD) Device Serial ID        : Not Visible
        Standard (STD) Device Group Name       : Not/Grouped
        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
        }

Any idea?

0 Kudos
dynamox
6 Thallium

Re: Removing a STD-BCV relationship

can you post symdev show for 01D7

0 Kudos
mugurstef
2 Bronze

Re: Removing a STD-BCV relationship

Here it is:

symdev -sid xxx show 01D7

    Device Physical Name     : Not Visible

    Device Symmetrix Name    : 01D7
    Device Serial ID         : N/A
    Symmetrix ID             : xxx

    Attached BCV Device      : N/A

    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     : 0x0002
    Cache Partition Name     : DEFAULT_PARTITION

    Device Block Size        : 512

    Device Capacity
        {
        Cylinders            :      18414
        Tracks               :     276210
        512-byte Blocks      :   35354880
        MegaBytes            :      17263
        KiloBytes            :   17677440
        }

    Device Configuration     : 2-Way Mir       (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            : Not Ready        (NR)
    Device SA Status         : N/A              (N/A)

    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, C, 2]
        Disk Director Volume Number            :   12 (0xB)
        Hyper Number                           :    3
        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, C, 2]
        Disk Director Volume Number            :   12 (0xB)
        Hyper Number                           :    3
        Mirror Number                          : 2
        Disk Capacity                          : 140014m
        Disk Group Number                      : 1
        Disk Group Name                        : DISK_GROUP_001
        }

and also:

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            :      18414
        Tracks               :     276210
        512-byte Blocks      :   35354880
        MegaBytes            :      17263
        KiloBytes            :   17677440
        }

    Device Configuration     : 2-Way BCV Mir   (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)

    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       : Not/Grouped
        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,

0 Kudos
xe2sdc
4 Ruthenium

Re: Removing a STD-BCV relationship

mugurs ha scritto:

Cancelling by "symmir -sid xxx -f bcv_temp cancel"  where bcv_temp file contains "01D7 028F" is not working:

"Execute 'Cancel' operation for the 1 specified device(s)
in device file 'bcv_temp' (y/) ? y

'Cancel' operation execution is in progress for the device list in
device file 'bcv_temp'. Please wait...

Cannot proceed because the device does not have any BCV pairing relationship"

...

Any idea?

1) Try cancelling with the -force option.

2) Try converting device 028F to 2-way-mir.

0 Kudos
dynamox
6 Thallium

Re: Removing a STD-BCV relationship

why do you think there is an existing relationship ? I don't see any BCV related information when you look at your STD device. BCV will always show the last STD device it was established to, you can't clear that information.

0 Kudos
mugurstef
2 Bronze

Re: Removing a STD-BCV relationship

Hi,

1. symmir -sid xxx -f bcv_temp cancel -force

Execute 'Cancel' operation for the 1 specified device(s)
in device file 'bcv_temp' (y/) ? y

'Cancel' operation execution is in progress for the device list in
device file 'bcv_temp'. Please wait...


Cannot proceed because the device does not have any BCV pairing relationship

2. Establishing a configuration change session...............Established.
    Processing symmetrix xxx
    {
      convert dev 028F to 2-Way Mir, raidset=false;
    }

    Performing Access checks..................................Allowed.
    Checking Device Reservations..............................Allowed.
    Submitting configuration changes..........................Submitted
    Locking devices...........................................Locked.
    Validating configuration changes..........................Validated.
    Initiating PREPARE of configuration changes...............Prepared.
    Initiating COMMIT of configuration changes................Queued.
    COMMIT requesting required resources......................Obtained.
    Step 002 of 027 steps.....................................Executing.
    Step 007 of 027 steps.....................................Executing.

    COMMIT monitoring failed

    Error occurred while Committing
    The state of a snap session is blocking the activation of the new configuration. Please see the API log file

    Closing configuration change request......................Closed.
    Terminating the configuration change session..............Done.

The configuration change session has failed.

Thank you,

0 Kudos