Anyways, today I finally decided to write a blog entry on a bit unusual task I did recently - Migrate VERITAS (VxVM) to Solaris Disk Suite (SDS). In past have done several migrations, like UFS to ZFS, UFS/SDS to VxVM, VxVM to ZFS however this time I been contacted for some different and backward migration which is VxVM to SDS. When SDS is getting obsolete but on other hand still there are some requirement comes, in which demanding for such things… anyways, good to perform anything which you feels interesting and uncommon. Then let’s do it…
Point To Ponder - Make sure you have full backup of the system on which you're going to operate.
Let's first see which disks are part of bootdg.
Disk_0 auto rootdisk rootdg online c3t0d0s2
Disk_5 auto rootmirror rootdg online c0t0d0s2
Which all volumes needs to be converted to the SVM -
# df -kh | grep bootdg
/dev/vx/dsk/bootdg/rootvol 5.9G 4.3G 1.5G 75% /
/dev/vx/dsk/bootdg/var 5.9G 4.7G 1.1G 81% /var
/dev/vx/dsk/bootdg/opt 5.9G 1.8G 4.0G 32% /opt
Take the pre-veritas vfstab copy.
root@XXXXXX# cat /etc/vfstab.prevm
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c0t0d0s1 - - swap - no -
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no nologging
/dev/dsk/c0t0d0s5 /dev/rdsk/c0t0d0s5 /var ufs 1 no nologging
/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /opt ufs 2 yes nologging
/dev/dsk/c0t2d0s0 /dev/rdsk/c0t2d0s0 /var/crash ufs 2 yes nologging
/devices - /devices devfs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes -
#/dev/dsk/c3t0d0s0 is currently mounted on /.
#/dev/dsk/c3t0d0s1 is currently used by swap.
#/dev/dsk/c3t0d0s5 is currently mounted on /opt.
#/dev/dsk/c3t0d0s6 is currently mounted on /var.
Let's first unencapsulate the rootdisk using the vxunroot.
Detach all the plexes associated with the 'rootmirror' disk if applicable & Verify the rootmirror plexes have been detached.
# vxprint -qhtg rootdg -s | grep -i rootmirror | awk '{print $3}' > /var/tmp/subs.plex && cat /var/tmp/subs.plex
rootvol-02
swapvol-02
opt-02
var-02
# for x in `cat /var/tmp/subs.plex`
> do
> vxplex -g rootdg dis $x
> vxprint -qhtg rootdg -p $x
> done
pl rootvol-02 - DISABLED - 12584484 CONCAT - RW
sd rootmirror-01 rootvol-02 rootmirror 0 12584484 0 Disk_5 ENA
pl swapvol-02 - DISABLED - 31458321 CONCAT - RW
sd rootmirror-02 swapvol-02 rootmirror 12584484 31458321 0 Disk_5 ENA
pl opt-02 - DISABLED - 12584484 CONCAT - RW
sd rootmirror-03 opt-02 rootmirror 44042805 12584484 0 Disk_5 ENA
pl var-02 - DISABLED - 12584484 CONCAT - RW
sd rootmirror-04 var-02 rootmirror 56627289 12584484 0 Disk_5 ENA
# /etc/vx/bin/vxunroot
VxVM vxunroot NOTICE V-5-2-1564
This operation will convert the following file systems from
volumes to regular partitions:
opt rootvol swapvol var
VxVM vxunroot INFO V-5-2-2011
Replacing volumes in root disk to partitions will require a system
reboot. If you choose to continue with this operation, system
configuration will be updated to discontinue use of the volume
manager for your root and swap devices.
Do you wish to do this now [y,n,q,?] (default: y) y
VxVM vxunroot INFO V-5-2-287 Restoring kernel configuration...
VxVM vxunroot INFO V-5-2-78
A shutdown is now required to install the new kernel.
You can choose to shutdown now, or you can shutdown later, at your
convenience.
Do you wish to shutdown now [y,n,q,?] (default: n) n
VxVM vxunroot INFO V-5-2-258
Please shutdown before you perform any additional volume manager
or disk reconfiguration. To shutdown your system cd to / and type
shutdown -g0 -y -i6
# sync;sync;sync;shutdown -g0 -y -i6
Well, after 2-3 reboots server came back online and now I've UFS filesystems for OS volumes.
# df -kh / /var /opt
Filesystem size used avail capacity Mounted on
/dev/dsk/c3t0d0s0 5.9G 4.3G 1.5G 74% /
/dev/dsk/c3t0d0s6 5.9G 4.7G 1.1G 81% /var
/dev/dsk/c3t0d0s5 5.9G 1.8G 4.0G 32% /opt
Just to be sure, once just try booting from mirror disk too.
Now let's create a partition slice for metadb.
# format c3t0d0
selecting c3t0d0
[disk formatted]
Warning: Current Disk has mounted partitions.
/dev/dsk/c3t0d0s0 is currently mounted on /. Please see umount(1M).
/dev/dsk/c3t0d0s1 is currently used by swap. Please see swap(1M).
/dev/dsk/c3t0d0s5 is currently mounted on /opt. Please see umount(1M).
/dev/dsk/c3t0d0s6 is currently mounted on /var. Please see umount(1M).
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
![cmd] - execute [cmd], then return
quit
format> p
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
![cmd] - execute [cmd], then return
quit
partition> p
Current partition table (original):
Total disk cylinders available: 24620 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 3 - 4358 6.00GB (4356/0/0) 12584484
1 swap wu 4359 - 15247 15.00GB (10889/0/0) 31458321
2 backup wu 0 - 24619 33.92GB (24620/0/0) 71127180
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 15248 - 19603 6.00GB (4356/0/0) 12584484
6 var wm 19604 - 23959 6.00GB (4356/0/0) 12584484
7 unassigned wm 0 0 (0/0/0) 0
partition> 7
Part Tag Flag Cylinders Size Blocks
7 unassigned wm 0 0 (0/0/0) 0
Enter partition id tag[unassigned]:
Enter partition permission flags[wm]:
Enter new starting cyl[0]: 23960
Enter partition size[0b, 0c, 23960e, 0.00mb, 0.00gb]: 128mb
partition> p
Current partition table (unnamed):
Total disk cylinders available: 24620 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 3 - 4358 6.00GB (4356/0/0) 12584484
1 swap wu 4359 - 15247 15.00GB (10889/0/0) 31458321
2 backup wu 0 - 24619 33.92GB (24620/0/0) 71127180
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 15248 - 19603 6.00GB (4356/0/0) 12584484
6 var wm 19604 - 23959 6.00GB (4356/0/0) 12584484
7 unassigned wm 23960 - 24050 128.37MB (91/0/0) 262899
partition> l
Ready to label disk, continue? yes
Good enough, now let's create metadb.
# metadb -a -f -c 3 c3t0d0s7
# metadb -i
flags first blk block count
a u 16 8192 /dev/dsk/c3t0d0s7
a u 8208 8192 /dev/dsk/c3t0d0s7
a u 16400 8192 /dev/dsk/c3t0d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
Set SDS on root file system.
# metainit -f d11 1 1 c3t0d0s0
d11: Concat/Stripe is setup
# metainit d10 -m d11
d10: Mirror is setup
# metaroot d10
After executing metaroot, check the changes in /etc/vfstab and /etc/system.
#live-upgrade:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
fd - /dev/fd fd - no -
/proc - /proc proc - no -
#live-upgrade:
/dev/dsk/c3t0d0s1 - - swap - no -
/dev/md/dsk/d10 /dev/md/rdsk/d10 / ufs 1 no nologging
/dev/dsk/c3t0d0s6 /dev/rdsk/c3t0d0s6 /var ufs 1 no nologging,nosuid
/dev/dsk/c3t0d0s5 /dev/rdsk/c3t0d0s5 /opt ufs 2 yes nologging
/dev/vx/dsk/crashdg/crashvol /dev/dsk/crashdg/crashvol /var/crash vxfs 2 yes -
/devices - /devices devfs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes nosuid
* Begin MDD root info (do not edit)
rootdev:/pseudo/md@0:0,10,blk
* End MDD root info (do not edit)
Good enough.
# metastat -ac
d10 m 6.0GB d11
d11 s 6.0GB c3t0d0s0
# metainit -f d31 1 1 c3t0d0s6
d31: Concat/Stripe is setup
# metainit d30 -m d31
d30: Mirror is setup
# metainit -f d51 1 1 c3t0d0s5
d51: Concat/Stripe is setup
# metainit d50 -m d51
d50: Mirror is setup
# metainit -f d1 1 1 c3t0d0s1
d1: Concat/Stripe is setup
# metainit d0 -m d1
d0: Mirror is setup
# metastat -ac
d0 m 15GB d1
d1 s 15GB c3t0d0s1
d50 m 6.0GB d51
d51 s 6.0GB c3t0d0s5
d30 m 6.0GB d31
d31 s 6.0GB c3t0d0s6
d10 m 6.0GB d11
d11 s 6.0GB c3t0d0s0
So in above,
d0 - swap
d10 - /
d30 - /var
d50 - /opt
Now it's time to change the vfstab to change slices into metadb devices.
# vi /etc/vfstab
# cat /etc/vfstab
#live-upgrade:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
fd - /dev/fd fd - no -
/proc - /proc proc - no -
#live-upgrade:
/dev/md/dsk/d0 - - swap - no -
/dev/md/dsk/d10 /dev/md/rdsk/d10 / ufs 1 no nologging
/dev/md/dsk/d30 /dev/md/rdsk/d30 /var ufs 1 no nologging,nosuid
/dev/md/dsk/d50 /dev/md/rdsk/d50 /opt ufs 2 yes nologging
/dev/vx/dsk/crashdg/crashvol /dev/dsk/crashdg/crashvol /var/crash vxfs 2 yes -
/devices - /devices devfs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes nosuid
Reboot the box once.
Now it's time to add mirror disk to existing metadevices.
At this stage the mirror disk is part of rootdg and for rootdg it's the last disk in the disk group hence we need to destroy rootdg.
# vxdg destroy rootdg
Unsetup the disk so it will be out of VERITAS control.
# vxdiskunsetup -C Disk_5
Cool, now I'm all set to create/copy partition table on mirror disk as exisitng disk part of metadevices.
# prtvtoc /dev/rdsk/c3t0d0s2 | fmthard -s - /dev/rdsk/c0t0d0s2
fmthard: New volume table of contents now in place.
Fine, Set redundant database on mirror disk.
# metadb -a -f -c 3 c0t0d0s7
# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c3t0d0s7
a p luo 8208 8192 /dev/dsk/c3t0d0s7
a p luo 16400 8192 /dev/dsk/c3t0d0s7
a u 16 8192 /dev/dsk/c0t0d0s7
a u 8208 8192 /dev/dsk/c0t0d0s7
a u 16400 8192 /dev/dsk/c0t0d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
Create metadevices on mirror.
# metainit -f d12 1 1 c0t0d0s0
d12: Concat/Stripe is setup
# metainit -f d2 1 1 c0t0d0s1
d2: Concat/Stripe is setup
# metainit -f d52 1 1 c0t0d0s5
d52: Concat/Stripe is setup
# metainit -f d32 1 1 c0t0d0s6
d32: Concat/Stripe is setup
Attach metadevices.
# metattach d10 d12
d10: submirror d12 is attached
# metattach d30 d32
d30: submirror d32 is attached
# metattach d50 d52
d50: submirror d52 is attached
# metattach d0 d2
d0: submirror d2 is attached
# metastat -ac
d0 m 15GB d1 d2 (resync-76%)
d1 s 15GB c3t0d0s1
d2 s 15GB c0t0d0s1
d50 m 6.0GB d51 d52
d51 s 6.0GB c3t0d0s5
d52 s 6.0GB c0t0d0s5
d30 m 6.0GB d31 d32
d31 s 6.0GB c3t0d0s6
d32 s 6.0GB c0t0d0s6
d10 m 6.0GB d11 d12
d11 s 6.0GB c3t0d0s0
d12 s 6.0GB c0t0d0s0
Install boot block on both disks.
# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0
# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c3t0d0s0
Well, that completes VxVM to SDS migration. I'm sure hardly anyone need to do such backward migration but just in case then this method will certainly help you... :)
Have a good weekend!
HI Nilesh,
ReplyDeletei m regularly check you block for knowing more thing on vertias. Thanks for providing such a blog, so that i learn more thing from it.
Recently i have installed the vertias volume manager in my laptop for practicals. when i m mounting vertias filesystem, i go the following error. can you please check it and let me know.
bash-3.00# mkfs -F vxfs /dev/vx/rdsk/dg1/vol1
ld.so.1: mkfs: fatal: libadm.so.1: version `SUNW_1.2' not found (required by file /usr/lib/fs/vxfs/mkfs)
ld.so.1: mkfs: fatal: libadm.so.1: open failed: No such file or directory
Killed
bash-3.00# ldd /usr/lib/fs/vxfs/mkfs
libefi.so.1 => /usr/lib/libefi.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libadm.so.1 => /usr/lib/libadm.so.1
libadm.so.1 (SUNW_1.2) => (version not found)
libm.so.2 => /usr/lib/libm.so.2
libsocket.so.1 => /usr/lib/libsocket.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libpthread.so.1 => /usr/lib/libpthread.so.1
libc.so.1 => /usr/lib/libc.so.1
libuuid.so.1 => /usr/lib/libuuid.so.1
libmp.so.2 => /usr/lib/libmp.so.2
libmd.so.1 => /usr/lib/libmd.so.1
libscf.so.1 => /usr/lib/libscf.so.1
libdoor.so.1 => /usr/lib/libdoor.so.1
libuutil.so.1 => /usr/lib/libuutil.so.1
libgen.so.1 => /usr/lib/libgen.so.1
bash-3.00# ls -ltr /lib/libadm.so.1
-rwxr-xr-x 1 root bin 125596 Jun 9 2006 /lib/libadm.so.1
bash-3.00# find / -name libadm.so.1 -print 2>/dev/null
/usr/lib/amd64/libadm.so.1
/usr/lib/libadm.so.1
/lib/amd64/libadm.so.1
/lib/libadm.so.1
bash-3.00#
Hi Praveen Kumar,
ReplyDeleteCan you please check and post your LD_LIBRARY_PATH? At first glance it looks to be issue with your LD_LIBRARY_PATH environment variable.
Thanks/Nilesh
Hello Nilesh,
DeleteGood Morning!
Could you please help me in migration Oracle DB which are running on VxFS to ZFS within same Server (Solaris 10) . Basically we want to remove veritas layer to reduce license cost and want to use native file system (ZFS).
Thanks:
Gaurav
Hello Nilesh,
DeleteGood Morning!
Could you please help me in migration Oracle DB which are running on VxFS to ZFS within same Server (Solaris 10) . Basically we want to remove veritas layer to reduce license cost and want to use native file system (ZFS).
Thanks:
Gaurav
Hi Gaurav,
DeleteDid you ever do the above project of the VxFS to ZFS? can you please help me in sharing the details. We are in a similar boat as you.
Thanks
Vamsee
Ahh.. :)
ReplyDeleteI found an issue you faced on Symantec forum, and I understand the work-able solution provided is -
Setting below environment variables eliminates the issue.
LD_NOVERSION=yes;export LD_NOVERSION
To make these variable permanent, I would include the above string in to profile file
Thanks/Nilesh
Hi Nilesh,
ReplyDeleteAnd how to do it in reverse order, I mean SVM to VXVM ?
I have removed the Metadb, done the metaclear and booted the server on slice mode.
However "vxdisk -e list " shows that both disk (root and root-mirror disk ) as SVM under the status field.
Thanks,
Harish
Excellent information in this blog.Thank you very much for sharing.We are providing UNIX Online Training.UNIX Online Training
ReplyDeletethanks for sharing it's very nice article.we are providing unix online training.
ReplyDeleteunix ONLINE TRAINING
i got a lot of information in this blog it's very nice article.we are providing unix online training.
ReplyDeleteUNIX ONLINE TRAINING