New Volume Configuration To The Existing Veritas Cluster

Reason for Change
Mysql database is generating more replication logs and elastic logs on hourly basis, and it causes the platform outages as it gets filled up volume. Hence finally we decided to dedicate the new volume to the DB cluster for these logs
Procedure
1.Two new LUNs need to be available on each host ( should be shared storage)
2.Once we add new LUNs to the server, need to label them, and should bring the LUNs under   
   VERITAS control 
   #cfgadm -al -o show_FCP_dev
    #export PATH=$PATH:/opt/VRTS/bin:/opt/VRTSvcs/bin:/etc/vx/bin
    #vxdisk scandisks new
    #vxdisk list
3.Initialize the each disk and create new disk group with new LUNs
   #vxdisksetup -i <new LUN> 
    #vxdisksetup -i <2nd new LUN>
    #vxdisk list
    #vxdg init new_bindg new_bindisk01=<new LUN>
    #vxdg -g new_bindg adddisk new_bindisk02=<2nd new LUN>
4.Check whether the new disk group is working or not 
   #vxdg deport new_bindg   [needs to be done on A node] 
    #vxdisk -o alldgs list
    #vxdg import new_bindg   [Needs to be done on B node]
    #vxvol -g new_bindg start new_binlogs [start the volume if we have any]
5.Create new striped volume using new LUNs
    #vxassit -g new_bindg make new_binlogs 398g layout=stripe ncol=2 stwidth=8k 
       new_bindisk01 new_bindisk02
    #vxprint -hvpst
6.check the volume with temporary mount point
   #mkfs -F vxfs /dev/vx/rdsk/new_bindg/new_binlogs 
    #mkdir -p /binlogs  [ do it on both the nodes]
    #chown -R dba:other /binlogs [do it on both the nodes]
    #mount -F vxfs /dev/vx/rdsk/new_bindg/new_binlogs /binlogs
    #umount /binlogs
7. Freeze the cluster before going to add the volume
   #cp /etc/VRTSvcs/conf/config/main.cf /etc/VRTSvcs/conf/config/main.cf.bkp
    #cp /etc/VRTSvcs/conf/config/types.cf /etc/VRTSvcs/conf/config/types.cf.bkp
    #haconf makerw   [ Make the configuration as writable]
    #hagrp -freeze newsDB -persistent
    #hastatus -sum
8.Add disk group resource to the cluster
   #hares -add newsDBbin-dg DiskGroup newsDB

       VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors  [ignore notice]

   #hares -modify newsDBbin-dg DiskGroup new_bindg
   #hares -modify newsDBbin-dg Enabled 1
9.Add volume resource to the cluster 
   #hares -add newsDBbin-vol Volume newsDB

         VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors [ignore notice]

   #hares -modify newsDBbin-vol Volume new_binlogs
    #hares -modify newsDBbin-vol DiskGroup new_bindg
    #hares -modify newsDBbin-vol Enabled 1
10.Add mount resource to the cluster
     #hares -add newsDBbin-mnt Mount newsDB
          VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors [ignore notice]
    #hares -modify newsDBbin-mnt MountPoint /binlogs
    #hares -modify newsDBbin-mnt BlockDevice /dev/vx/rdsk/new_bindg/new_binlogs
    #hares -modify newsDBbin-mnt FSType vxfs
    #hares -modify newsDBbin-mnt MountOpt rw
    #hares -modify newsDBbin-mnt FsckOpt %y
    #hares -modify newsDBbin-mnt Enabled 1
11.Define the dependencies
    #hares -link newsDB-app newsDBbin-mnt
    #hares -link newsDBbin-mnt newsDB-mnt
    #hares -link newsDBbin-mnt newsDBbin-vol
    #hares -link newsDBbin-vol newsDBbin-dg
    #hares -link newsDBbin-mnt newsDBlog-mnt
12. Go through the configuration
    #more /etc/VRTSvcs/conf/config/main.cf 


13.Unfreeze the cluster
     #hagrp -unfreeze newsDB -persistent
     #haconf -dump -makero [Make the configuration as readable]
     #hacf -verify /etc/VRTSvcs/conf/config/  [check the configuration]
     #hastop -all  [ need stop the cluster for reconfiguration for the new resources]
     #hastart  [ do it on A after that B node]
     #hastatus -sum