Unable to import the Disk Group that has been created on a solaris server.

book

Article ID: 100029597

calendar_today

Updated On:

Resolution

Disk Group could not be imported on solaris server.
--> The disks within the Disk Group was in the sliced format while they required to be in CDS ( Cross-platform Data Sharing ) format.
--> The Disk Group version was 90 and to convert the disk group from sliced to CDS, it requires DG version 110 or higher.
--> Disk Group did not have enough space to proceed with the conversion of Disk Group from sliced to CDS.
I noticed that the disk format is sliced and not CDS hence I suggested customer to import the DG back to the Solaris box where actually the DG was created and then change the disk format to CDS. A CDS disk group allows cross-platform datasharing of VxVM objects, so that data written on one of the supported platform may be accessed on any other supported platform. A CDS disk group is composed only of CDS disks ( VM disks with the disk format "cdsdisk" ), and is only available for disk group version 110 and higher.

To upgrade the DG version following command executed:

#vxdg -T 110 upgrade tradingdg

Ran the following command to convert the disk group to CDS:

# vxcdsconvert -g  tradingdg  -o novolstop group---->  This step was not successful to lack free space in the DG hence asked customer to add a temporary disk to the DG in order to carry out and then plexes associated to "trading-datavol" could not be moved to the newly added disk as "trading-datavol" volume was too big for the new disk (25GB) to hold. Hence asked customer to take a backup of the volume "trading-datavol" and delete it then convert the DG to CDS and then again recreate the volume and put data back to the volume from the backup.

 

Issue/Introduction

Unable to import the Disk Group that has been created on a solaris server.