* Adding physical disks to the volume manager results in creation of public and private region in the disk by the volume manager. In two hosts and a shared storage situation one host can take over the ownership of the disk groups and drives in case other host fails. * Disk groups enable high availability as these can be shared by two or more hosts but can be accessed by only one host at a time. all the operations on a particular disk group remains confined to that particular group. * Volume Manager objects cannot span disk groups i.e. All the configuration changes made to a disk group are applied to the disks in that disk group only. * A disk group is a collection of volume manager disks grouped together to hold the data. While device name is system dependent based on controller and disk id the disk name is user defined. įor example device name c2t3d0s2 represents controller number 2, target id 3, disk group 0 and slice 2 and disk01 may be its disk name. Disk name is the common name given to the device name as an easy to remember name. The device name specifies controller, target id and slice of the disk. Volume Manager Configuration ( options menu)Ģ.8 Enable access to (import) a disk groupĢ.9 Remove access to (deport) a disk groupĢ.12 Mark a disk as a spare for a disk groupĭisks are referred in volume manager by two terms – device name and disk name. ġ.7 Volume Manger Objects & their RelationshipĢ. The following article describes the volume manager objects and configuration of these objects using a text menu based utility called vxdiskadm. Dynamic reconfiguration of disk storage in an online system state. Provides fail over features by providing transferable disk group ownership between systems.Ĥ. Provides high availability storage solutions through RAID ,Mirroring of disks. This overcomes the physical limit of the disk. Allows creation of logical volumes spanning over multiple disks. The main features of volume manager are followingġ. Click OK to validate.Veritas Volume Manager is used to manage disk storage spread over an array of disks. ▪ Click Add and enter the name of the VxVM disk path you wish to add to the monitoring environment. The Additional Disk Paths (manual discovery) section allows you to add VxVM disk paths manually, when they are not automatically discovered: Repeat the operation for any other VxVM disk path you wish to exclude from the monitoring processĥ.
Enter the name of the VxVM disk path or identify it by using a regular expression (example: test-disk path *). ▪ In the Exclude Disk Paths section, click Add and identify the VxVM disk path you do not want to monitor. Repeat the operation for any other VxVM disk path you wish to include in the monitoring process Enter the name of the VxVM disk path or identify it by using a regular expression (example: prod-disk path *). ▪ In the Keep Only Disk Paths section, click Add and identify the VxVM disk path you wish to monitor.
a hostname or IP address to apply these settings to a specific server.localhost to apply these settings to all PATROL Agents installed on the VxVM Server.From the Add Monitoring Configuration panel, select VxVM Disk Paths from the Monitor Type list.Ģ. Because the monitoring of some VxVM disk paths may be irrelevant for various reasons, you can apply filters to specify the VxVM disk paths that will be monitored or discarded. Configuring VxVM Disk Path Configuring VxVM Disk Pathīy default, the solution monitors all the Veritas Volume Manager disk paths discovered, which may represent an important workload for the Agents and the TrueSight OM servers.
0 kommentar(er)
