Search <book_title>...

Veritas InfoScale™ 7.1 Release Notes - Linux

Last Published: 2018-01-09

Product(s): InfoScale & Storage Foundation (7.1)

Enabling the application isolation feature in CVM environments

Enabling the application isolation feature involves taking applications offline resulting in application downtime. The VCS configuration is updated to set the CVMDGSubClust attribute of the CVMCluster resource to 1. The change is persistent across cluster reboots.

The VCS port 'h' must be active for enabling the application isolation feature.

To enable the application isolation feature

Verify that the GAB port h is active.
```
# hastatus
```
Take the CVM group offline on all nodes in the cluster:
```
# hagrp -offline cvm -sys sys_name
```

Enable the CVMDGSubClust attribute of the CVMCluster resource:

# haconf -makerw
# hares -modify cvm_clus CVMDGSubClust 1
# haconf -dump -makero

Bring the CVM group online on all nodes:
```
# hagrp -online cvm -sys sys_name
```
The application isolation capability is enabled and ready for use after the CVM group is brought online on all nodes.

Import the disk groups to nodes in the cluster.

Since the disk group is not auto-imported on any node in the cluster, you must configure VCS to import the disk groups to the required nodes in the cluster. Use one of the following commands, depending on your need.

cfsdgadm	Use this option if you are using a block device.
cfsmntadm	Use this option if you plan to create a cluster file system on the block device.

# cfsdgadm add dgname sys1 sys2

This will update the VCS configuration file as follows:

group vrts_vea_cfs_int_cvmvoldg2 (
   SystemList = { sys1 = 5, sys2 = 6 }
   AutoFailOver = 0
   Parallel = 1
   AutoStartList = { sys1, sys2 }
   )
   CVMVolDg cvmvoldg2 (
      Critical = 0
      CVMDiskGroup = bdg
      CVMActivation @sys1 = sw
      CVMActivation @sys2 = sw
      NodeList = { sys1, sys2 }
      )
      requires group cvm online local firm
        // resource dependency tree
        //
        //      group vrts_vea_cfs_int_cvmvoldg2
        //      {
        //      CVMVolDg cvmvoldg2
        //      }

# cfsmntadm add dgname volname /mnt1 \
sys1=cluster sys2=cluster

This will update the VCS configuration file as follows:

group vrts_vea_cfs_int_cfsmount1 (
  SystemList = { sys1 = 5, sys2 = 7 }
  AutoFailOver = 0
  Parallel = 1
  AutoStartList = { sys1, sys2 }
  )
  CFSMount cfsmount1 (
     Critical = 0
     MountPoint = "/mnt1"
     BlockDevice = "/dev/vx/dsk/adg/avol1"
     MountOpt @sys1 = "cluster"
     MountOpt @sys2 = "cluster"
     NodeList = { sys1, sys2 }
     )
     CVMVolDg cvmvoldg1 (
        Critical = 0
        CVMDiskGroup = adg
        CVMVolume = { avol1 }
        CVMActivation @sys1 = sw
        CVMActivation @sys2 = sw
        NodeList = { sys1, sys2 }
        )
        requires group cvm online local firm
        cfsmount1 requires cvmvoldg1
        // resource dependency tree
        //
        //      group vrts_vea_cfs_int_cfsmount1
        //      {
        //      CFSMount cfsmount1
        //          {
        //          CVMVolDg cvmvoldg1
        //          }
        //      }

Verify that the application isolation feature is enabled:

# hares -display cvm_clus | grep CVMDGSubClust
cvm_clus     CVMDGSubClust         global        1