InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - Linux
- Introducing bundled agents
- Storage agents
- DiskGroup agent
- DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Volume agent
- VolumeSet agent
- Sample configurations for VolumeSet agent
- LVMLogicalVolume agent
- LVMVolumeGroup agent
- LVMVolumeGroup agent notes
- Sample configurations for LVMVolumeGroup agent
- Mount agent
- Sample configurations for Mount agent
- VMwareDisks agent
- SFCache agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- Notes for the NIC agent
- Sample configurations for NIC agent
- IPMultiNIC agent
- MultiNICA agent
- IP Conservation Mode (ICM) for MultiNICA agent
- Performance Mode (PM) for MultiNICA agent
- Sample configurations for MultiNICA agent
- DNS agent
- Agent notes for DNS agent
- About using the VCS DNS agent on UNIX with a secure Windows DNS server
- Sample configurations for DNS agent
- AWSIP agent
- AWSRoute53 agent
- AzureDNSZone agent
- File share agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- NetBios agent
- Service and application agents
- Apache HTTP server agent
- Application agent
- Notes for Application agent
- Sample configurations for Application agent
- AzureAuth agent
- CoordPoint agent
- KVMGuest agent
- Notes for KVMGuest agent
- Sample configurations for KVMGuest environment
- Sample configurations for RHEV environment
- Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- ProcessOnOnly agent
- RestServer agent
- Infrastructure and support agents
- Testing agents
- Replication agents
- RVG agent
- RVGPrimary agent
- RVGSnapshot
- RVGShared agent
- RVGLogowner agent
- RVGSharedPri agent
- VFRJob agent
- Dependencies for VFRJob agent
- Notes for the VFRJob agent
Enabling volume group activation protection
On each node in the cluster, perform the following procedure to enable activation protection for volume groups on Red Hat and SUSE systems.
To enable volume group activation protection
- On each node, edit the /etc/lvm/lvm.conf file and add the following line:tags { hosttags = 1 }
Note:
When you set the value of hosttags to 1, it enables LVM tagging for all the volume groups. By default, this value is set to 0 (disabled).
- On each node, create the node-specific configuration file with the name as /etc/lvm/lvm_host_name.conf. Where, host_name is the output of the uname -n command.
- In the volume_list entry of the lvm_host_name.conf file, add the names of all the volume groups and volumes that are not managed by VCS, and append the "@host_name" tag:
activation { volume_list = [ "os_vg", "@host_name" ] }
where, "os_vg" is the root volume group that is not managed by VCS, andhost_name is the output of the uname -n command.
- Set the value of EnableLVMTagging to 1 for all the configured LVMVolumeGroup resources.
- Optionally, to disable LVM tagging for a particular volume group that is managed by VCS, add its name in the volume_list entry.
activation { volume_list=[ "os_vg", "vg1", "@host_name" ] }
Then, set EnableLVMTagging to 0 for the corresponding LVMVolumeGroup resource.
This configuration instructs the LVMVolumeGroup agent not to use LVM tagging while activating the volume group vg1.