- Veritas Infoscale Vxvm
- Veritas Vxvm Commands
- Veritas Vxvm Cheat Sheet
- Veritas Vxvm And Systems Integration
- Veritas Vxvm Log
The company has its origins in Tolerant Systems, founded in 1983 and later renamed Veritas Software. Torch browser review. It specializes in storage management software including the first commercial journaling file system, VxFS, VxVM, VCS, the personal/small office backup software Backup Execand the enterprise backupsoftware, NetBackup. Veritas Volume Manager (VxVM) is a popular and powerful, enterprise-class storage management tool. When you want to inspect a large setup (or sometimes even a small one!), its output ( vxprint ) can be unclear, even cryptic.
Veritas has re-branded it’s “Storage Foundation and High Availability” family products and now, from version 7 all the of the Veritas products under this category comes with a brand name of “Infoscale“. In this tutorial, we are going to teach how to create a Veritas Volume Manager (VxVM) volume and then how to create a VxFS filesystem and mount it in Red Hat Enterprise Linux 7 (RHEL 7).
This will be a basic VxVM tutorial with easy to understand steps. For better understanding perform this live on your test environment for learning.
Pre-Requisite:
1.Red Hat Enterprise Linux 7 (RHEL 7) or CentOS 7.
2. Infoscale Foundation (VxVM + VxFS).
3. Knowledge of Linux Operating System.
Creating Veritas Volume Manager (VxVM) Volume & Filesystem in RHEL 7
1. First of all, check the disks which are visible to Veritas Volume Manager (VxVM) and this can be done by “vxdisk” command as below.
2. Once the disks are visible to the VxVM, initialize the disk which are not under VxVM control, i.e. showing “Online Invalid” status.
By default CDSDISK (Cross-Platform Data Sharing Disk) type is used and can be changed as per requirement.
Once the disk is initialized and is under control of VxVm, we can create a Disk Group (DG). Here we are using a single disk to create a DG and a Volume. No complex layouts in this tutorial like Stripe, Mirror, Mirror-Concat, etc.
3. To create a disk group (DG) with one disk use below command.
testdg01 is a logical name called DM name (Disk media name). If the DM name is not given while creating the disk group, then by default disk name will be used.
4. Once DG is created with one disk, create a volume as below.
The above command will create a volume with the name “testvol” having size 100 MB.
Mounting VxFS Filesystem in Red Hat Enterprise 7 (RHEL 7)
5. Now, once the volume is created, format it as a VxFS filesystem using the below command.
Note: /dev/vx/rdsk/testdg/testvol is a character or RAW device and for mounting we don’t use it. For mounting purpose block device is used.
6. Now create a directory to mount the filesystem.
Now your VxFS filesystem is mounted and you can start using it. If you want to mount it permanently put an entry in “/etc/fstab” file like any other filesystem.
Tip: Use Veritas™ Services and Operations Readiness Tools (SORT) to check version compatibility. It is a web-based tools that optimizes the end to end experience for Veritas products.
This tutorial is just a basic and first in our Veritas Volume Manager (VxVM) tutorial series, we will also cover other simple and advance tutorials, so do subscribe to our blog and get alerts for FREE whenever a new article is published.
If you like this article, do not forget to share it with your friends and social network. Also, do let us know if you have any doubts through your comments.
Veritas Volume Manager Cheat Sheet:
The Setup:an Oracle database supporting an application called ABC, and given thefollowing:
Assuming that we need to create filesystems intended for Oracle and:
we are using a SID of 'ABC'
we have nine disks, c0t0d1 through c0t0d9
we will be creating six volumes: /u01/oradata/ABC ( 4gb), /u02/oradata/ABC (4gb ), /u03/oradata/ABC (8gb ), /u04/oradata/ABC (4gb ), /u01/app/oracle/product/8.0.5_ABC ( 4gb ), and /u01/admin/ABC (4gb ).
We added these disks to Volume Manager Control duringinstallation with vxinstall, or later withvxdiskadd(1m). Both vxinstalland vxdiskadd can add either initialize a previouslyunused disk, or 'encapsulate' a disk already containing data, but not underVolume Manager control.
we could take the following steps to set up our filesystems.
Adding an EMC disk to Veritas
Use the inq utility to see if you have SCSI visibility to the disk
Use vxdisk -o alldgs list to see if Veritas has seen the disk
if not, try the following, and then repeat the previous step:
devfsadm
vxdctl initdmp
vxdctl enable
Creating a Disk Group in Volume Manager:
Create a vxvm disk group for the Oracle SID using vxdg(1m).It's important that all of the disks/filesystems necessary for the ABCdatabase to run are included in the disk group, otherwise the databasecould not be moved to another system.
The easiest way to do this is to use vxdiskadd
vxdiskadd c0t0d0 c0t0d1 c0t0d2 . . .
Doing it the hard way:
vxdg init ABCdg ABCdg01=c0t0d1
This would create a disk group called ABCdg containingone physical disk, c0t0d1, which will be referred to by it's name withinvxvm, ABCdg01. You cannot initiate a disk group without specifying at leastone disk as a member of the group. You should not include any disks destinedto be part of an Oracle Database in the default vxvm group, rootdg. Thisallows you to use the vxdg 'deport' and 'import'commands to migrate an entire vxvm disk group to another host.
Now that we've create the disk group for our database,we can add the rest of our disks to it:
vxdg -g ABCdg adddisk ABCdg02=c0t0d2
vxdg -g ABCdg adddisk ABCdg09=c0t0d9
Creating Volumes With vxassist
vxassist(1m) is a vxvm commandthat acts as a front-end to other vxvm commands, much as newfs(1m)acts as a simpler-to-use front-end to mkfs(1m).Using vxassist with it's -vflag will display the actual vxvm commands used during volume construction.vxassist also front-ends vxfs commands andnormal UNIX utilities during volume construction. An example of this isusing a single vxassist command to set up avolume.Using vxassist simplifies many vxvm tasks,but you should pay careful attention to the defaults you will inherit whensetting up volumes using this tool. Understanding the contents of the /etc/default/vxassist Foxit pdf editor for mac crack. file is important, especially when striping disks.
To make our 8gb /u03/oradata/ABC volume, we could usethe following command line:
vxassist -g ABCdg make ABC01 8g
Breaking it down into it's component parts:
vxassist
-g ABCdg # this volume will belong to the ABCdg disk group
make # tells vxassist that we are creating a new volume
ABC01 # name the volume
8g # specify the size of the volume
Here we create the other five volumes:
vxassist -g ABCdg make ABC02 8g
vxassist -g ABCdg make ABC03 8g
vxassist -g ABCdg make ABC04 8g
vxassist -g ABCdg make ABC05 8g
vxassist -g ABCdg make ABC06 8g
Creating a File System:
We now lay filesystems down on our newly created volumes.We assume here that you've agreed with the Oracle DBA's to use a blocksize of 8192 for our filesystems. Not specifying a block size allow Veritasto dynamically assign one for you based upon the size of the volume. Ourvolumes would default to 1024 for a block size on our 4 GB volumes, and2048 for our 8GB volume. We will specify the largefiles option, becausethe mkfs_vxfs(1m) command uses nolargefilesas a default, unlike mkfs_ufs(1m) on Solaris2.6 or greater, which uses largefiles as adefault. If we forgot to do so, we could use fsadm( fsadm_vxfs(1m) ) to set the largefilesbit on. fsadm can also query a mounted filesystemfor the current setting of this flag. Be certain that whatever flags youset during file system creation or modification are reflect in vfstab,or the resulting file system may be un-mount-able.
mkfs -F vxfs -o bsize=8192,largefiles /dev/vx/rdsk/ABCdg/ABC01
Mounting a File System:
Creating and mounting filesystems go hand in hand. Youmust be certain that any special flags set at creation time are reflectedin /etc/vfstab, or on the command line if thereis no entry in vfstab for your filesystem.
mount -F vxfs -o largefiles /dev/vx/dsk/ABCdg/ABC01/u03/oradata/ABC
Resizing a mounted volume and file system:
/etc/vx/bin/vxresize -g rootdg -F vxfs archive 16g
Recovering disks under VM control:
(if you want to live dangerously, try looking at dfwset01:/root/progs/hose_vx_dg.pl)
Pre-reqs
- Do a vxprint -g mydg first to see what disks your volumes lie on!
- Do a vxdisk list and save it
- Do an inq -et and save it!
- You may wish to review moving a volume off of a particluar disk
Acrobat reader for mac yosemite free download. Procedure
1) comment the volume(s) you're destroying out of vfstab
2) umount the volume
3) stop it:
vxvol stop volume01
4) remove it:
vxedit -rf rm volume01
5) remove the disk(s) the volume was on from the disk group ( up to the last disk )
vxdg -g mydg rmdisk dmdiskname01
6) Remove the the disk(s) from VXVM control
vxdisk rm c1t1d51s2
7) If you wish do get rid of the disk group ( in order to recover the last disk ), you must destroy the disk group:
vxdg destroy mydg
8) remove the last disk
vxdisk rm c2t7d9s2
9) If you're removing the disks from the EMC port, be sure to clean up:
drvconfig
disks
vxdctl enable
vxdctl initdmp
10) Freak out and realize you whacked the wrong thing, use /root/eotw to recover.
Renaming a VM Disk:
Since names like 'ABCdg10' are not as descriptive as theycould be, you can rename it to something more useful.
vxedit rename ABCdg10 ABCdg_hot_spare
Using long disk names can be more descriptive, but willmake using vxva trickier, as it will truncate your disk name somewhat ifit is too long.
Moving a Disk Group to Another System:
1) umount the disks:
umount /u01/app/oracle/product/8.0.5_ABC
umount /u01/admin/ABC
umount /u01/oradata/ABC
umount /u02/oradata/ABC
umount /u03/oradata/ABC
umount /u04/oradata/ABC
2) Stop the volumes:
vxvol -g ABCdg stopall
3) deport the disk group from one system:
vxdg deport ABCdg
4) import them on another system:
vxdg import ABCdg
5) Start all of the volumes on the new system and resyncmirrors in the background:
vxrecover -g ABCdg -sb
6) mount the filesystems
mount /u01/app/oracle/product/8.0.5_ABC
mount /u01/admin/ABC
mount /u01/oradata/ABC
mount /u02/oradata/ABC
mount /u03/oradata/ABC
mount /u04/oradata/ABC
Veritas Infoscale Vxvm
This procedure assumes that the second system can seethe disks, and also that you have commented the file systems out of vfstabon the old system.
Rename a Disk Group
/root
dfwns19 # df -k | grep reports
/dev/vx/dsk/reportsdg/ncr01 /u01/app/oracle/admin/REPORTS
/dev/vx/dsk/reportsdg/ncr02 /u01/app/oracle/product/8.0.5REPORTS
/dev/vx/dsk/reportsdg/ncr03 /u01/oradata/REPORTS
/dev/vx/dsk/reportsdg/ncr04 /u02/oradata/REPORTS
/dev/vx/dsk/reportsdg/ncr05 /u03/oradata/REPORTS
/dev/vx/dsk/reportsdg/ncr06 /u04/oradata/REPORTS
/dev/vx/dsk/reportsdg/ncr07 /u11/oraarch/REPORTS
dfwns19 # umount /u01/app/oracle/admin/REPORTS
dfwns19 # umount /u01/app/oracle/product/8.0.5REPORTS
dfwns19 # umount /u01/oradata/REPORTS
dfwns19 # umount /u02/oradata/REPORTS
dfwns19 # umount /u03/oradata/REPORTS
dfwns19 # umount /u04/oradata/REPORTS
dfwns19 # umount /u11/oraarch/REPORTS
dfwns19 # vxvol -g reportsdg stopall
dfwns19 # vxdg deport reportsdg
Veritas Vxvm Commands
dfwns19 # vxdg -n nclproddg import reportsdg
dfwns19 # vxdg list
Mirroring and then breaking mirrors
NAME STATE ID
nclproddg enabled 949356971.2501.dfwns19
Renaming a disk group and volume
bansecdbdg -> secproddg used as an example
Resizing a disk, while specifying the disk
Veritas Vxvm Cheat Sheet
Veritas Vxvm And Systems Integration
Moving a volume off of a particluar disk
Veritas Vxvm Log
# Move u11 off of dm dev20dg20vxassist -g dev20dg move u11 !dev20dg20