How to import clone disk group on the same host where the original disk group is imported

book

Article ID: 100007902

calendar_today

Updated On:

Description

Error Message

VxVM vxdg ERROR V-5-1-10978 Disk group DG_RS5_ORA_DB: import failed:
Disk group exists and is imported

Resolution

A user used a third party vendor's data mirroring solution to mirror the data bit-by-bit from the source luns to the target luns.  This resulted in the mirror copy luns having duplicate disk IDs as the original luns

The user then deported the original disk group called DG_TEST to a new disk group name DG_TEST2.  After deporting both the original disk group and the new disk group on the clone data luns, the user was only able to import one disk group although now the original source data lun disk group and the cloned disk group having different disk group names. When tried to import the DG_TEST, the error below was shown.

VxVM vxdg ERROR V-5-1-10978 Disk group DG_TEST: import failed:
Disk group exists and is imported

vxdisk -o alldgs list shows:

tagmastore-usp0_2a5a auto:cdsdisk    DG_TEST-00   DG_TEST2     online
tagmastore-usp0_2a5b auto:cdsdisk    DG_TEST-01   DG_TEST2     online
tagmastore-usp0_2a5c auto:cdsdisk    DG_TEST-02   DG_TEST2     online
tagmastore-usp0_2a5d auto:cdsdisk    DG_TEST-03   DG_TEST2     online
tagmastore-usp0_2a5e auto:cdsdisk    DG_TEST-04   DG_TEST2     online
tagmastore-usp0_2a5f auto:cdsdisk    DG_TEST-05   DG_TEST2     online
tagmastore-usp0_2a54 auto:cdsdisk    DG_TEST-06   DG_TEST2     online
tagmastore-usp0_2a55 auto:cdsdisk    DG_TEST-07   DG_TEST2     online
tagmastore-usp0_2a56 auto:cdsdisk    DG_TEST-08   DG_TEST2     online
tagmastore-usp0_2a57 auto:cdsdisk    -            (DG_TEST)    online udid_mismatch
tagmastore-usp0_2a58 auto:cdsdisk    -            (DG_TEST)    online udid_mismatch
tagmastore-usp0_2a59 auto:cdsdisk    -            (DG_TEST)    online udid_mismatch
tagmastore-usp0_2a60 auto:cdsdisk    -            (DG_TEST)    online udid_mismatch
tagmastore-usp0_2a61 auto:cdsdisk    -            (DG_TEST)    online udid_mismatch
tagmastore-usp0_2a62 auto:cdsdisk    -            (DG_TEST)    online udid_mismatch
tagmastore-usp0_2a63 auto:cdsdisk    -            (DG_TEST)    online udid_mismatch
tagmastore-usp0_2a64 auto:cdsdisk    -            (DG_TEST)    online udid_mismatch
tagmastore-usp0_2a65 auto:cdsdisk    -            (DG_TEST)    online udid_mismatch

 

The vxdg import issue was caused by both the original disk group and the new disk group having the same DGID (Disk Group ID) as the vxdg deport command with attribute -n only assinged a new disk group name to the disk group without setting up a new DGID on the new disk group.

To import the disk groups with the same DGID as well as the luns with udid_mismatch flag set, use -o useclonedev and -o updateid attributes.

#vxdg -n DG_TEST3 -o useclonedev=on -o updateid import DG_TEST
 

The attribute useclonedev is used to import a disk group with devices that have the clone_disk or udid_mismatch flag  set  on the disks.

The attribute updateid is used to generate new identification values (listed below) for the disks that are being imported:

               - Disk identifier.

               - Unique disk identifier (UDID).

               - Disk group identifier (DGID).

               - Global unique identifier (GUID).

               - Base minor number.
 

 

 

Issue/Introduction

Unable to import clone disk group on the same host where the original disk group is imported