#VERITAS VOLUME MANAGER COMMAND LINE FULL#

d file containing defaults for vxassist if not specified /etc/default/vxassist is used About VxassistДў.1 Extending a volume up to certain length,ДЎ1.Displaying Volume Configuration InformationД¬ommonly used options are given below (See man vxassist for complete list of supported options) The default length is taken as number of blocks but this can be specified in Kilobytes or Megabytes or Gigabytes. The default behavior of vxassist is to create volumes in the rootdg diskgroup if diskgroup is not specified. VCS 5.Vxassist utility in veritas volume manager is used to create volumes, add mirrors and logs to existing volumes, extend and shrink existing volumes, provides for the migration of data from a specified set of disks, and provides facilities for the on-line back up of existing volumes. Once these are set the resources should be able to online/monitor/offline properly.ДЇor future reference, suggest you take a look at the Bundled Agents Reference Guide and User's Guide in terms of how these fit together: Reference from VCSВ 5.0MP3 (Solaris) Bundled Agents Reference Guide:ДЄdditionally, your Volume resource is missing the Volume attribute according to your steps above. NB: did you mount the filesystems manually? according to your steps above you didn't set the MountPoint attributes so VCS wouldn't have known where to mount the filesystems!! The reason VCS would not have been able to online the Mount resources is because you did not set / you were missing the following required attributes: #hares -modify APP_vol3_mnt BlockDevice /dev/vx/dsk/APP_dg/APP_vol3

#hares -modify APP_vol4_mnt BlockDevice /dev/vx/dsk/APP_dg/APP_vol5 For a beginner like me, it is difficult to understand the complications or difficulties possibilities expected during the maintanance.ДЄccording to the steps you provided above, the only attributes you set for the Mount resources was the BlockDevice: Please help to get GUI method steps and also method right from scratch till failover in addition to what above two guys had helped to assist. there is also a QA oracle database existing on the 2 node cluster test servers. We need to take these two Volumes say APP_vol03 & APP_vol04 under VCS control either by using GUI or command line step by step and there after need to carry ot the failover test. Two new filesystems created & mounted on Node1 as below in addition to existing ones:. opt/app/APP is filesystem already created and in use. Service Group say 'APP_sg' already existing

#VERITAS VOLUME MANAGER COMMAND LINE FULL#

Request: Can anyone share full steps to be carried out through 'Veritas Cluster Manager' GUI to take newly createdВ additional two Filesystem/Volumes under VCS control into existing SG for example in a group where volume depends on diskgroup resource, diskgroup will be child & volume would be parent. Please note in VCS, parent resource depends on child resource, so be careful while linking. # hares -modify Critical 0 (Assume you don't want to make volume as critical resource)ДЇinally you have to link volume resource to diskgroup &/OR mount # hares -modify Enabled 1 (to enable resource> You will need to modify some attributes of your volume resource which are mandatory your resource type here would be Volume (V is capital) so you need to add them as resources into a VCS service group:ДЄdd both volumes with above step. Once volumes are created, you need to put them under VCSВ control. I hope you have added volumes in veritas volume manager diskgroup first, if not, following would be commands to do that:Дisks of this diskgroup must be located on shared storage.Д¬reate mount points on both the cluster nodes

Veritas volume manager command line