VERITAS VOLUME MANAGER GUI FOR 7.2 HOW TO

# mkvg -v 57 -S -n -Qn -y fs01vg hdisk38 hdisk42 hdisk45 Finally, the major number should be set (in the example below: -V 57).ДЄs such, run the following mkvg command to create the volume group (Note: please adjust the volume group name, the major number and disk names according to your situation and preference): Also, The quorum should be disabled (by using -Qn), and the auto-varyon should be disabled as well (by using the -n option) as PowerHA will varyon the volume group for us. For the purpose of this article, let's assume major number 57 is available.ДЇor PowerHA, a new volume group should be configured as concurrent-capable (configured by the -C option of the mkvg command). For that purpose, run the following command on all cluster nodes, which lists the available major numbers:Д¬hoose a major number available on all cluster nodes. The first thing that we'll need to know is a common majar number that is available on both nodes of a cluster. The next step is to create the new volume group(s). These attributes are stored in the ODM of the AIX system locally, and don't automatically transfer over to other nodes of the cluster, so you'll have to set these attributes for all new disks on all cluster nodes. To check the max_xfer_size attribute on the fiber adapter, run (for example for adapter fcs0):ДЄlso please make sure to set the disk attributes for all the new disks on both nodes. By default attribute max_transfer is set to 0x40000, which is usually lower than the max_xfer_size attribute on the fiber adapter, which results in a smaller buffer size memory being used. # chdev -l hdisk4 -a max_transfer=0x100000 -a queue_depth=32 -a reserve_policy=no_reserve -a algorithm=round_robinДЇor clustered nodes, it's important that the reserve_policy is set to no_reserve.ДЄ note about the max_transfer attribute: This value should be set to the same value as the max_xfer_size attribute of the fiber adapter. Now, this may differ for the type of storage used (so please make sure to check your storage vendor's recommendations on this topic), but a good starting point is (for example, for disk hdisk4):

On both nodes, make sure that the disk attributes are set correctly. And when you run 'lspv' on the second node after running cfgmgr, you'll notice that the PVID is already set for all the discovered disks (it was set on the first node). Next, log in to the other node, and run the cfgmgr command on that node as well, so the disks will be discovered on the other node as well. Repeat this command for any of the new disks. Set a PVID on all the new disks that have been discovered. Then discover the newly added storage by running the cfgmgr command on one of the nodes: In the case of SAN storage, please ensure that your storage administrator adds the storage to both nodes of the cluster. The first step is to add the storage to both of the nodes of the PowerHA cluster.

VERITAS VOLUME MANAGER GUI FOR 7.2 HOW TO

This article describes how to add a new volume group to an existing resource group of an active PowerHA cluster. Topics: PowerHA / HACMP, Storage Adding a new volume group to an active PowerHA resource group

Veritas volume manager gui for 7.2