Howto recover vxdg with only one side of mirrors

Pretty old version  :)

When you moved Storage Luns B to Sol 10 machine, it were simply presented to new solaris box OR you have disassociated disks from vxvm view on Sol 7 machine & then have moved the disks ?

I am not very sure since its a very old version but looks like vxvm is not happy with half of the disks on new node & is expecting all the disks in the dg to be available on new Sol 10 node .. & clearly force import is not a choice in DG version 70.

I also believe DG split & join feature will not be available in that version as that would have made life little easy.

First I would suggest to try a "vxdg move" option, with this you can move objects between diskgorups. I am not sure if this will work in 3.1 but worth a try ..

# vxdg move <source dg > <target dg> <object>

If you use your SAN B disks as objects, you should be able to move disks & volumes with SAN A to different DG, once all objects are moved, then diskgroup information is updated with correct number of disks, with this you should be able to move any one of SAN A or SAN B diskgroup to new Sol 10 system

I can think of another solution but may be tricky ..

1. Get all the disks back to Sol 7 machine.

2. Do a clean import of all the diskgroups

3. Take detailed output of vxprint -htg <diskgroup>, vxprint -mvphsr <diskgroup>, vxprivutil dumpconfig <disk>, vxdisk list <disk> for each disk.

4. Disassociate 1 plex of SAN A from all the volumes.

5. Take all SAN A disks out of diskgroup so that diskgroup config is aware of number of disks

6. Move the diskgroup to new sol 10 machine (with all SAN A disks out)

7. On Sol 7 machine, perform a rebuild of dg & all the volumes using vxmake.

G

Yes pretty old, but App has been / is running 24x7 and now I need to upgrade OS + VxDMP to support new storage array. So to get a cloned copy of data without stopping App on Sol7, I attached new san luns and mirrored onto these luns. Quick shutdown sol7, removed fiber from san B from sol7, rebooted sol7 and removed mirrored plexs from san B on sol7, everything is happy on sol7, and App is still running.

Now I planned to import DGs from san B luns to new[er] host OS+VxDMP to verify App will be working here, only...

Yes it's properly sol10 missing quorum in DG that's making vxvm unhappy as san B lun are 3x size of san A luns and thus: 3x #B luns = #A luns, hence properly quorum is lost as on sol7 it were okay...

Forced import were tried on sol10 & DG v.140 (vxvm 5.0 :)

Anyway to rebuild/reconstruct new DGs, SDs, PLXs & VOLs on san B luns without loosing data in SDs?

I believe import on new node should be possible without loosing data .. however as a safe step, take an appropriate backup of data

Since you have mirrored data from SAN B (new Storage)  to SAN A (old storage), that means disks were initialized from SAN B & later plexes were created which were mirrored to SAN A

I believe on new node, if you reinitialize the disks with exact offsets & length, you should be able to recover them on new node

Do you have a vxprint -ht output of server when disks were mirroed from SAN A & SAN B ? & also paste out a sample output of "vxdisk list <disk_from_SAN A> & vxdisk list <disk_from_SAN B>

G

1. I've mirrored from A(old)  to B(new) :)

I've got these output of A+B mirrored config:

​$vxdisk list > vxdisk_list
$vxdisk -q list | awk '$3!="-" && $5=="online"{print $1}' | xargs $vxdisk list > vxdisk_list.detail
$vxdisk -q list | awk '$2!="simple" && $3!="-" && $5=="online"{print "/dev/rdsk/"$1}' | xargs $prtvtoc > prtvtoc_all_disk
$vxprint -qG | awk '/^dg /{print $2}' - | while read dg; do
  $vxprint -g $dg -rhmvps > vxprint_config.$dg
done

Attaching outputs...

You should be able to rebuild On Solaris 10 while app is running on Sol 7 as follows:

1. On Sol 7 system, for each diskgroup run vxprint -mvpsg dg_name > dg_name.make
2. On Sol 7 system, run "vxdisk list" > vxdisk_list
3. On Sol 7 system disassociate SAN B plexes and remove SAN disks from diskgroup 
4. Edit files created above to:
   a. Remove subdisk records for SAN A
   b. Remove the associated plex record to SAN A
   c. Edit plex attribute of the volulme record to remove the deleted plex from SAN A
   
   Note you do not need to change disk device names if these are different when disks are present on Sol10 system
    
5. On Sol 10 system create a diskgroup from the SAN B disks and gives the disk names the original names using the output of vxdisk_list.  Note the private region on the disk should not have changed as the private region is created when you run "vxdisksetup" which you do not need to re-run.
   You may need to use "cds=off" when you create diskgroup or it may be better to create diskgroup on Sol 7 system and then rename on Sol 10 system if you want to keep the same block device for mounts
6. On Sol 10 system, for each diskgroup run "vxmake -g dg_name -d dg_name.make" and then "vxvol -g dg_name startall
7. On Sol 10 system, you should now be able to mount filesystem

You may want to script steps 4 and 5 if you have a lot of disks and volumes

Mike

Thanks, only your step 5 gives me this:

# trying to recreate DG arr1imsdg

ims-v3:/var/tmp/backup> vxdg init arr1imsdg svc1=c6t0d1s2 cds=off
VxVM vxdg ERROR V-5-1-2349 Device c6t0d1s2 appears to be owned by disk group arr1imsdg.

ims-v3:/var/tmp/backup> vxdg -o override init arr1imsdg svc1=c6t0d1s2 cds=off
VxVM vxdg ERROR V-5-1-2349 Device c6t0d1s2 appears to be owned by disk group arr1imsdg.

wondering howto overcome this...

Should I run forced vxdisksetup on disks before step 5

Tried to recreate the single-disk DG after vxdisksetup -fi DA privlen=1777 to get an aligned public region, I ran vxmake succesfull and find all vol,plex and sd, only they are marked EMPTY and won't start...

ims-v3:/var/tmp/backup> vxvol -g arr1imsdg startall

VxVM vxvol ERROR V-5-1-11804 Volume archlv is empty and cannot be started

VxVM vxvol ERROR V-5-1-11804 Volume data5lv is empty and cannot be started

VxVM vxvol ERROR V-5-1-11804 Volume redo2lv is empty and cannot be started

ims-v3:/var/tmp/backup> vxprint -g arr1imsdg

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0

dg arr1imsdg    arr1imsdg    -        -        -        -        -       -

dm svc1         c6t0d1s2     -        62908416 -        -        -       -

v  archlv       fsgen        DISABLED 40899584 -        EMPTY    -       -

pl archlv-02    archlv       DISABLED 40903680 -        EMPTY    -       -

sd svc1-01      archlv-02    ENABLED  20451840 0        -        -       -

sd svc1-02      archlv-02    ENABLED  20451840 20451840 -        -       -

v  data5lv      fsgen        DISABLED 10485760 -        EMPTY    -       -

pl data5lv-01   data5lv      DISABLED 10485760 -        EMPTY    -       -

sd svc1-03      data5lv-01   ENABLED  10485760 0        -        -       -

v  redo2lv      fsgen        DISABLED 2097152  -        EMPTY    -       -

pl redo2lv-02   redo2lv      DISABLED 2104320  -        EMPTY    -       -

sd svc1-04      redo2lv-02   ENABLED  2104320  0        -        -       -

but altering plex state from empty was handled by init clean:

ims-v3:/var/tmp/backup> vxvol -g arr1imsdg init clean redo2lv

ims-v3:/var/tmp/backup> vxvol -g arr1imsdg init clean archlv

ims-v3:/var/tmp/backup> vxvol -g arr1imsdg init clean data5lv

and fsck:

ims-v3:/var/tmp/backup> fsck -F vxfs /dev/vx/rdsk/arr1imsdg/archlv 

file system is clean - log replay is not required

ims-v3:/var/tmp/backup> fsck -F vxfs /dev/vx/rdsk/arr1imsdg/redo2lv 

file system is clean - log replay is not required

ims-v3:/var/tmp/backup> fsck -F vxfs /dev/vx/rdsk/arr1imsdg/data5lv 

file system is clean - log replay is not required

ms-v3:/var/tmp/backup> fsck -F vxfs /dev/vx/rdsk/arr1imsdg/archlv 

file system is clean - log replay is not required

ims-v3:/var/tmp/backup> fsck -F vxfs /dev/vx/rdsk/arr1imsdg/redo2lv 

file system is clean - log replay is not required

ims-v3:/var/tmp/backup> mount -F vxfs /dev/vx/dsk/arr1imsdg/archlv /arch 

ims-v3:/var/tmp/backup> mount -F vxfs /dev/vx/dsk/arr1imsdg/redo2lv /redo2

ims-v3:/var/tmp/backup> ls -l /redo2/oradata/I321/

total 1228896

-rw-r-----   1 oracle   dba      157286912 Jun 25 10:19 redolog0102.rdo

-rw-r-----   1 oracle   dba      157286912 Jun 25 08:41 redolog0104.rdo

-rw-r-----   1 oracle   dba      157286912 Jun 25 09:44 redolog0201.rdo

-rw-r-----   1 oracle   dba      157286912 Jun 25 07:41 redolog0203.rdo

and seems I have my data, thanks all!

will work over the other DGs as well...

Got rest of the DGs recreated fine as well and reimported with all data, thanks for all hints!