FMI (Fixed Metadata Incident) content (S.R.D.F)

Symptom:

When a server has both EMC Symmetrix Remote Data Facility (SRDF-R2) and EMC Business Continuance Volume (BCV) devices presented, the importing of a VxVM diskgroup containing the BCV devices may fail with an error message similar to the one given below.

# vxdg -Cfn bcv_DopeyDg -o useclonedev=on -o updateid import DopeyDg
VxVM vxdg ERROR V-5-1-10978 Disk group srdf2: import failed:
Disk group has no valid configuration copies

 

Description:

The BCV device and its corresponding EMC SRDF (srdf-r2) device have the same VxVM diskid and diskgroup id. The import operation will select the correct disk group configuration copy to use by grouping the disks with the same diskid, and then selecting the updated configuration copy from the list.

The srdf-r2 device is a write-disabled at the time of the import attempt, and hence it does not have any active paths for I/O. This leads to an error when selecting the configuration copies and the import operation is aborted. 
 

Resolution:

During the diskgroup import operation when grouping the disks with the same diskid, necessary checks are made to skip the write-disabled srdf-r2 devices. This enables the VxVM diskgroup import operation to select the correct configuration copies and the diskgroup import now succeeds without the need to use VxVM tags.

 

Note: The product enhancement requires the Storage Foundation Enterprise license to be installed.


How to import a BCV image of a SRDF (R2) write-disable lun with 5.0 MP3 RP4 HF3



1.] Ensure a "full" established copy of the source LUN has been copied to the target BCV lun.


Bashful # symmir -sid 414 -v -f  /bcv-mapping.txt -full establish -nopr

'Full Establish' operation execution is in progress for the device list in device file '/bcv-mapping.txt'. Please wait...


SELECTING the list of Standard devices in the group:

  Device: 0072 [SELECTED]

SELECTING BCV devices associated with the group:

  Device: 00DC [SELECTED]

PAIRING of Standard and BCV devices:

  Devices: 0072(S) - 00DC(B) [PAIRED]

STARTING a BCV 'ESTABLISH' operation.

The BCV 'ESTABLISH' operation SUCCEEDED.

'Full Establish' operation successfully initiated for the device list in device file '/bcv-mapping.txt'.



2.] Ensure the BCV lun has been "synchronized" prior to proceeding to "split" the BCV lun.


Bashful # symmir -sid 414 -v -f  /bcv-mapping.txt query

SELECTING the list of Standard devices in the group:

  Device: 0072 [SELECTED]

SELECTING BCV devices associated with the group:

  Device: 00DC [SELECTED]

PAIRING of Standard and BCV devices:

  Devices: 0072(S) - 00DC(B) [PAIRED]


Device File Name      : /bcv-mapping.txt
Device's Symmetrix ID : 000290301414



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

N/A            0072      0 N/A                  00DC           0 Synchronized

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



Legend:


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



3.] Split the BCV lun.


Bashful # symmir -sid 414 -v -f  /bcv-mapping.txt split

Execute 'Split' operation for the 1 specified device(s) in device file '/bcv-mapping.txt' (y/[n]) ? y

'Split' operation execution is in progress for the device list in device file '/bcv-mapping.txt'. Please wait...


SELECTING the list of Standard devices in the group:

  Device: 0072 [SELECTED]

SELECTING BCV devices associated with the group:

  Device: 00DC [SELECTED]

PAIRING of Standard and BCV devices:

  Devices: 0072(S) - 00DC(B) [PAIRED]

STARTING a BCV 'SPLIT' operation.

The BCV 'SPLIT' operation SUCCEEDED.

'Split' operation successfully executed for the device list in device file '/bcv-mapping.txt'.


4.] Ensure the BCV lun has been split.


Bashful # symmir -sid 414 -v -f  /bcv-mapping.txt query

SELECTING the list of Standard devices in the group:

  Device: 0072 [SELECTED]

SELECTING BCV devices associated with the group:

  Device: 00DC [SELECTED]

PAIRING of Standard and BCV devices:

  Devices: 0072(S) - 00DC(B) [PAIRED]


Device File Name      : /bcv-mapping.txt
Device's Symmetrix ID : 000290301414



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

N/A            0072      0 N/A                  00DC           0 Split

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



Legend:


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



5.] Refresh the VxVM content.


The extended attribute content reported by VxVM CLI command "vxdisk -e list" can be refreshed by running "vxdisk scandisks" .


Bashful # vxdisk scandisks

Bashful # vxdisk -eo alldgs list | grep -w DopeyDg
emc1_00dc    auto:cdsdisk   -            (DopeyDg)   online udid_mismatch c1t5006048C536979A0d80s2 bcv                 <<<< BCV (target) lun
emc1_0072    auto:cdsdisk   -            (DopeyDg)   online udid_mismatch c1t5006048C536979A0d65s2 srdf-r2            <<<< SRDF (source) lun
emc1_0073    auto:cdsdisk   -            (DopeyDg)   online               c1t5006048C536979A0d66s2 srdf-r2
emc1_0074    auto:cdsdisk   -            (DopeyDg)   online               c1t5006048C536979A0d67s2 srdf-r2
emc1_0075    auto:cdsdisk   -            (DopeyDg)   online               c1t5006048C536979A0d68s2 srdf-r2


6.] As a result of the product enhancement, VxVM tags do not need to be defined when the source LUN(s) are write-disabled.


Bashful # vxdg -Cfn bcv_DopeyDg -o useclonedev=on -o updateid import DopeyDg
VxVM vxdg WARNING V-5-1-560 Disk r1-008D: Not found, last known location: emc0_008d
VxVM vxdg WARNING V-5-1-560 Disk r1-008E: Not found, last known location: emc0_008e
VxVM vxdg WARNING V-5-1-560 Disk r1-008f: Not found, last known location: emc0_008f


Refreshed VxVM content.


Bashful # vxdisk -eo alldgs list | grep -w bcv_DopeyDg
emc1_00dc    auto:cdsdisk   r1-008C      bcv_DopeyDg online clone_disk    c1t5006048C536979A0d80s2 bcv
-            -         r1-008D      bcv_DopeyDg  failed was:emc0_008d
-            -         r1-008E      bcv_DopeyDg  failed was:emc0_008e
-            -         r1-008f      bcv_DopeyDg  failed was:emc0_008f


Note: The BCV VxVM diskgroup image imports without defining VxVM tags.
 

Applies To

Solaris

This document attempts to explain the product improvement made in Veritas Volume Manager (VxVM) 5.0 MP3 RP4 HF3 (Solaris), regarding the handling of EMC BCV devices.

Prior to the product enhancement introduced in VxVM 5.0 MP3 RP4 HF3 (Solaris), it was necessary to use VxVM tags when importing EMC BCV cloned images of EMC SRDF-R2 (write-disabled) devices.


Note: The SRDF (R2) lun is in a write-disabled state at the time of the VxVM diskgroup import attempt.


In this instance, the configuration consists of "4" EMC SRDF "R1" devices presented to production server "Dopey" from EMC Symmetrix id (SID) "822". An additional "4" EMC SRDF "R2" devices have been presented to DR server "Bashful" from EMC Symmetrix ID (SID) "414".


Figure 1.0

Note: At the time of writing this document, 5.0 MP3 RP4 HF9 is available for VxVM on Solaris.

 

ETrack: n/a