reallocate the /etc/vx/cbr/bk , vg config backup file without any service restart ...
1. Create the directory to copy the vg config backup file . # mkdir -p /tech/vgconfigbackup/bk ( please must create the "bk" directory ) 2. Take the backup of scripts " /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh " # cp /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh_bkp<date> 3. Made the required change care fully in below script . # vi /usr/lib/vxvm/voladm.d/lib/vxcbrlib comment the existing line "CF_BKUP_BASE_PATH" and change CF_BKUP_BASE_PATH to point to a new location. 4. Delete the all old vg configuration file backup from default location . 5. Take the new vg configuration backup and test 6. Check the new vg configuration file backup in new location .1.4KViews4likes3CommentsSome VCS plexes disabled after power outage
Hi all, I'm running the Veritas Storage Foundation Standard HA 5.0MP3 under Suse Linux Enterprise Server 11 on two Oracle X6270 servers. There was a power outage, causing an immediate brutal shutdown of both servers. After power was restored, the server on which the Oracle service group was active ("db1-hasc") could not boot at all (mainboard failure). The other server ("db2-hasc") booted, but reported during boot that cluster cannot start, and that manual reseeding might be needed to start it, so I started the cluster from the working server db2-hasc using command gabconfig -x (found it after some googling). In the meantime, the failed server db1-hasc was fixed and cluster is now working (all service groups online, but on the db2-hasc, the one which started successfully after power outage). No attempt has been made yet to try to switchover any of the service groups (except network service groups which are online) to the db1-hasc server. However, I have noticed some problems with several volumes in disk group "oracledg": db2-hasc# vxprint -g oracledg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg oracledg oracledg - - - - - - dm oracled01 - - - - NODEVICE - - dm oracled02 sdb - 335462144 - - - - v archvol fsgen ENABLED 62914560 - ACTIVE - - pl archvol-01 archvol DISABLED 62914560 - NODEVICE - - sd oracled01-02 archvol-01 DISABLED 62914560 0 NODEVICE - - pl archvol-02 archvol ENABLED 62914560 - ACTIVE - - sd oracled02-02 archvol-02 ENABLED 62914560 0 - - - v backupvol fsgen ENABLED 167772160 - ACTIVE - - pl backupvol-01 backupvol DISABLED 167772160 - NODEVICE - - sd oracled01-03 backupvol-01 DISABLED 167772160 0 NODEVICE - - pl backupvol-02 backupvol ENABLED 167772160 - ACTIVE - - sd oracled02-03 backupvol-02 ENABLED 167772160 0 - - - v dbovol fsgen ENABLED 62914560 - ACTIVE - - pl dbovol-01 dbovol DISABLED 62914560 - NODEVICE - - sd oracled01-01 dbovol-01 DISABLED 62914560 0 NODEVICE - - pl dbovol-02 dbovol ENABLED 62914560 - ACTIVE - - sd oracled02-01 dbovol-02 ENABLED 62914560 0 - - - db2-hasc# vxprint -htg oracledg DG NAME NCONFIG NLOG MINORS GROUP-ID ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK CO NAME CACHEVOL KSTATE STATE VT NAME RVG KSTATE STATE NVOLUME V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE DC NAME PARENTVOL LOGVOL SP NAME SNAPVOL DCO EX NAME ASSOC VC PERMS MODE STATE SR NAME KSTATE dg oracledg default default 0 1265259474.12.db1-HASc dm oracled01 - - - - NODEVICE dm oracled02 sdb auto 65536 335462144 - v archvol - ENABLED ACTIVE 62914560 SELECT - fsgen pl archvol-01 archvol DISABLED NODEVICE 62914560 CONCAT - WO sd oracled01-02 archvol-01 oracled01 62914560 62914560 0 - NDEV pl archvol-02 archvol ENABLED ACTIVE 62914560 CONCAT - RW sd oracled02-02 archvol-02 oracled02 62914560 62914560 0 sdb ENA v backupvol - ENABLED ACTIVE 167772160 SELECT - fsgen pl backupvol-01 backupvol DISABLED NODEVICE 167772160 CONCAT - WO sd oracled01-03 backupvol-01 oracled01 125829120 167772160 0 - NDEV pl backupvol-02 backupvol ENABLED ACTIVE 167772160 CONCAT - RW sd oracled02-03 backupvol-02 oracled02 125829120 167772160 0 sdb ENA v dbovol - ENABLED ACTIVE 62914560 SELECT - fsgen pl dbovol-01 dbovol DISABLED NODEVICE 62914560 CONCAT - WO sd oracled01-01 dbovol-01 oracled01 0 62914560 0 - NDEV pl dbovol-02 dbovol ENABLED ACTIVE 62914560 CONCAT - RW sd oracled02-01 dbovol-02 oracled02 0 62914560 0 sdb ENA Does anyone have some ideas on how to recover the disabled plexes/subdisks? Or which other commands to run to ascertain the current state of the cluster, in order to have a clear(er) picture what is wrong and which steps to take to remedy the problem? If so, I would appreciate if you can share any tips/suggestions. The physical disks seem fine (no errors reported in ILOM diagnostics). Thanks, /HrvojeSolved2.1KViews4likes9CommentsVeritas Volume migration onto new Disk
Hello all , Can anyone pleasesuggest how to migrate these volumes to new disk . The new DM disk are emc1_1660 & emc2_1661. I am looking for options to create mirror first with the new disk & then disassociate/remove the old plex. dg dg_pqata01m_mqm default default 25000 dm emc1_1678 emc1_1678 auto 65536 844599776 - dm emc2_1d9a emc2_1d9a auto 65536 844599776 - dm emc1_1660 emc1_1660 auto 65536 844599776 - dm emc2_1661 emc2_1661 auto 65536 844599776 - v vol_log_pqata01m - ENABLED ACTIVE 41943040 SELECT - fsgen pl vol_log_pqata01m-01 vol_log_pqata01m ENABLED ACTIVE 41943040 CONCAT - RW sd emc1_1678-02 vol_log_pqata01m-01 emc1_1678 796917760 41943040 0 emc1_1678 ENA pl vol_log_pqata01m-02 vol_log_pqata01m ENABLED ACTIVE 41943040 CONCAT - RW sd emc2_1d9a-01 vol_log_pqata01m-02 emc2_1d9a 0 41943040 0 emc2_1d9a ENA dc vol_log_pqata01m_dco vol_log_pqata01m vol_log_pqata01m_dcl v vol_log_pqata01m_dcl - ENABLED ACTIVE 67968 SELECT - gen pl vol_log_pqata01m_dcl-01 vol_log_pqata01m_dcl ENABLED ACTIVE 67968 CONCAT - RW sd emc2_1d9a-02 vol_log_pqata01m_dcl-01 emc2_1d9a 41943040 67968 0 emc2_1d9a ENA pl vol_log_pqata01m_dcl-02 vol_log_pqata01m_dcl ENABLED ACTIVE 67968 CONCAT - RW sd emc1_1678-04 vol_log_pqata01m_dcl-02 emc1_1678 838955520 67968 0 emc1_1678 ENA991Views2likes3CommentsSFHA 5.x version life -- (A conflicting link ?)
I have discuss a topic in below link regarding "Does end of life of SFHA 5.x version is extended ?" . https://www-secure.symantec.com/connect/forums/does-end-life-sfha-5x-version-extended The above discussion end accurately but today I saw a Symantec link which made the above solved discussion unclear. See the below link which says "(Support for SF 5.0 is available until Aug 6, 2015.)" . http://www.symantec.com/support/bcs/supportextensions.htmlSolved431Views2likes1CommentVxVM siteconsistent feature
I had a query on VxVM site-consistent feature. I have "Veritas Storage Foundation Basic" product installed and I am using mirroing with site consistent feature (mirror=site). On documentation, till release 5.0, this chapter "Administering sites and remote mirrors"was present in Storage Foundation Admin Guide. Now the same chapter has been moved to "SFCFS Admin Guide". I am assuming the with only "Storage Foundation" too, site-consistent feature is supported. Please correct me is I am wrong. Thanks,810Views2likes4CommentsOEL 6.1 with SF 5.1 SP1 PR2 P1 install doesn't work
Hello, I tried to install SF 5.1 SP1 PR2 on Oracle Enterprise Linux 6.1 I got this error: Logs are being written to /var/tmp/installer-201109191328Uoa while installer is in progress Starting SF: 90% _______________ Estimated time remaining: 0:05 10 of 11 Performing SF configuration .............................................................................................................................. Done Starting vxdmp ........................................................................................................................................... Done Starting vxio ............................................................................................................................................ Done Starting vxspec .......................................................................................................................................... Done Starting vxconfigd ....................................................................................................................................... Done Starting vxesd ........................................................................................................................................... Done Starting vxrelocd ........................................................................................................................................ Done Starting vxconfigbackupd ................................................................................................................................. Done Starting vxdbd ........................................................................................................................................... Done Starting vxodm ........................................................................................................................................... Done Veritas Storage Foundation Startup did not complete successfully vxdmp failed to start on edev vxio failed to start on edev vxspec failed to start on edev vxconfigd failed to start on edev vxesd failed to start on edev vxodm failed to start on edev It is strongly recommended to reboot the following systems: edev Execute '/sbin/shutdown -r now' to properly restart your systems After reboot, run the '/opt/VRTS/install/installsf -start electra-dev' command to start Veritas Storage Foundation installer log files, summary file, and response file are saved at: I found the following article about the bug: https://sort.symantec.com/patch/detail/5186/ I upgraded the vxvm with this patch vm-rhel6_x86_64-5.1SP1PR2P1. I got the following error message: [root@edev rpms]# rpm -Uvh VRTSvxvm-5.1.120.100-SP1PR2P1_RHEL6.x86_64.rpm Preparing... ########################################### [100%] stopping vxrelocd stopping vxconfigbackupd stopping vxnotify 1:VRTSvxvm ########################################### [100%] Installing file /etc/init.d/vxvm-boot creating VxVM device nodes under /dev Error in loading module "vxdmp". See documentation. WARNING: Unable to load new drivers. You should reboot the system to ensure that new drivers get loaded. I doesn't work after reboot too. I found a similar differences between version of SF kernel module and the Oracle factory default kernel version. #pwd /etc/vx/kernel [root@electra-dev kernel]# ls dmpaaa.ko.2.6.32-71.el6.x86_64 dmpap.ko.2.6.32-71.el6.x86_64 dmpnetapp.ko.2.6.32-71.el6.x86_64 vxfs.ko.2.6.32-71.el6.x86_64 dmpaa.ko.2.6.32-71.el6.x86_64 dmpCLARiiON.ko.2.6.32-71.el6.x86_64 dmpsun7x10alua.ko.2.6.32-71.el6.x86_64 vxio.ko.2.6.32-71.el6.x86_64 dmpalua.ko.2.6.32-71.el6.x86_64 dmpEngenio.ko.2.6.32-71.el6.x86_64 dmpsvc.ko.2.6.32-71.el6.x86_64 vxodm.ko.2.6.32-71.el6.x86_64 dmpapf.ko.2.6.32-71.el6.x86_64 dmphuawei.ko.2.6.32-71.el6.x86_64 fdd.ko.2.6.32-71.el6.x86_64 vxportal.ko.2.6.32-71.el6.x86_64 dmpapg.ko.2.6.32-71.el6.x86_64 dmpjbod.ko.2.6.32-71.el6.x86_64 vxdmp.ko.2.6.32-71.el6.x86_64 vxspec.ko.2.6.32-71.el6.x86_64 # uname -a Linux edev 2.6.32-100.34.1.el6uek.x86_64 #1 SMP Wed May 25 17:46:45 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux Is it important or not? How can I build a right SF kernel modul version for OEL 6.1? # rpm -qa | grep VRTS VRTSspt-5.5.000.006-GA.noarch VRTSvxfs-5.1.120.000-SP1PR2_RHEL6.x86_64 VRTSvxvm-5.1.120.100-SP1PR2P1_RHEL6.x86_64 VRTSperl-5.10.0.0-RHEL6.0.x86_64 VRTSob-3.4.291-0.i686 VRTSdbed-5.1.120.000-SP1PR2_RHEL6.i686 VRTSsfmh-3.1.429.0-0.i686 VRTSvlic-3.02.52.000-0.x86_64 VRTSaslapm-5.1.120.000-SP1PR2_RHEL6.x86_64 VRTSodm-5.1.120.000-SP1PR2_RHEL6.x86_64 thank you in advance xid123412Views2likes0CommentsSFHA Solutions 6.2: Symantec Storage plug-in for OEM 12c
Symantec Storage plug-in for OEM12c enables you to view and manage the Storage Foundation and VCS objects through the Oracle Enterprise Manager 12c (OEM), which has a graphical interface. It works with the Symantec Storage Foundation and High Availability 6.2 product suite. The Symantec Storage plug-in allows you to: SmartIO: manage Oracle database objects using SmartIO. Snapshot: create point-in-time copies (Storage Checkpoint, Database FlashSnap, Space-optimized Snapshot, and FileSnap) of Oracle databases using SFDB features Cluster: vew cluster-specific information. You can get the plug-in by downloading the attached file. For more information about installing and using the plug-in, download the attached Application Note. Terms of use for this information are found in Legal Notices.3.1KViews1like0CommentsImport disk group failure
Hello everyone! When I finished disk group configuration, I cannot find disk group until I imported by manual,butafter rebooting server,Icouldn't findthe disk group only if I imported again.following are my operations.Also the RVG was DISABLED until I started it,but it's still DISABLED after rebooting.Any help and suggestion would be appreciate [root@u31_host Desktop]# vxdisk list DEVICE TYPE DISK GROUP STATUS sda auto:none - - online invalid sdb auto:cdsdisk - - online sdc auto:cdsdisk - - online sdd auto:cdsdisk - - online [root@u31_host Desktop]# vxdg list NAME STATE ID [root@u31_host Desktop]# cd /dev/vx/dsk/ [root@u31_host dsk]# ls [root@u31_host dsk]# vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS sda auto:none - - online invalid sdb auto:cdsdisk - (netnumendg) online sdc auto:cdsdisk - (netnumendg) online sdd auto:cdsdisk - (netnumendg) online [root@u31_host dsk]# vxdg import netnumendg [root@u31_host dsk]# vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS sda auto:none - - online invalid sdb auto:cdsdisk netnumendg01 netnumendg online sdc auto:cdsdisk netnumendg02 netnumendg online sdd auto:cdsdisk netnumendg03 netnumendg online [root@u31_host dsk]# vxprint -rt |grep ^rv rv netnumenrvg 1 DISABLED CLEAN primary 2 srl_vol [root@u31_host dsk]# vxrvg -g netnumendg start netnumenrvg [root@u31_host dsk]# vxprint -rt |grep ^rv rv netnumenrvg 1 ENABLED ACTIVE primary 2 srl_vol After reboot the server [root@u31_host Desktop]# vxprint [root@u31_host Desktop]# vxdg list NAME STATE ID [root@u31_host Desktop]# vxdisk list DEVICE TYPE DISK GROUP STATUS sda auto:none - - online invalid sdb auto:cdsdisk - - online sdc auto:cdsdisk - - online sdd auto:cdsdisk - - online [root@u31_host Desktop]# vxprint -rt |grep ^rv [root@u31_host Desktop]# cd /dev/vx/dsk/ [root@u31_host dsk]# ls [root@u31_host dsk]# vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS sda auto:none - - online invalid sdb auto:cdsdisk - (netnumendg) online sdc auto:cdsdisk - (netnumendg) online sdd auto:cdsdisk - (netnumendg) onlineSolved1KViews1like1Comment