> CommCell Console > Solutions and Use Cases > FlexFrame

FlexFrame - Prerequisites

Before you install the Commvault agent software, create a directory structure and add symbolic links on the Flexframe mount point so that the software can be installed successfully. You must perform this configuration in Maintenance Mode.

Note

All application specific user IDs that are configured in the Commvault software must have the umask002 in the .profile file.

Naming Conventions

The following naming conventions are used in this document:

  • NetApp volume - volume on the Vserver, for example, fas04.

  • client_name - The name of the host where you perform the operation, for example, esx01.

  • commvault_volume - the NetApp volume that you create, for example, fas04 node.

  • commvault_pool - The FlexFrame pool that you use for the Commvault software, for example, p01.

  • grp_id - The Commvault group id, for example, 4711.

  • Controller node -The central node, for example, cn1.

Commvault Software Directories

The Commvault files such as the executable files, the configuration files and the registry files are located in the add-on volume and must be mounted on the application nodes. From this location, create the following directory structure for every FlexFrame pool and database (indicated by the database SID). FlexFrame provides the physical node for these directories.

  • commvault_pool - contains application-specific Commvault outputs. Mount this directory as /addon/commvault_pool.

    • IndexCache - contains the MediaAgent index of all the applications that belong to the FlexFrame pool.

      • db<sid> - contains the application-specific index cache information. Must be empty before installing the Commvault software.

        If you have several pools, add the Commvault client name to the directory name. Example, db<sid>_clientname.

      • <pool>-db<sid>-se - contains the application-specific index cache information.

    • job_results - contains the Commvault job results of all the applications that belong to the Flexframe pool.

      • db<sid> - contains the application-specific job results information. Must be empty before installing the Commvault software.

        If you have several pools, add the Commvault client name to the directory name. Example, db<sid>_clientname.

      • <pool>-db<sid>-se - contains the application-specific job results information.

    • scripts - contains the Commvault Pre/Post Process scripts for all the applications that belong to the Flexframe pool.

      • db<sid>- contains the application-specific Pre/Post Process scripts.

    • For the Commvault DB2 Agent, you need the db2dirs directory. The following directories that are created during the installation.

      • Db2Archive – contains the SID directory and sub structures that includes the Archive Log cache information.

      • Db2AuditError – contains the Audit error information.

      • Db2Retrieve – used for retrieval purposes.

    • For Commvault SAP Agent for MaxDB or HANA, you need the config directory that contains the application-specific configuration and parameter files.

  • commvault_ host_<pool>/<host> - contains the directories that have the Commvault software on the host. Mount this directory as /addon/commvault_host.

    • opt - contains the configuration details of the Commvault software on the host. Must be empty before installing the Commvault software.

    • local - contains the local binaries that are linked from the /usr/local/bin path. Example, db2ls binary for the DB2 Agent.

    • etc/CommVaultRegistry - contains Commvault configurations. Must be empty before installing the Commvault software.

    • etc/init.d- must contain an empty file named Galaxy before the installation. To create the file, use the command, Touch Galaxy.

    The binary (/opt) and the registry (/etc/CommVaultRegistry) directories cannot contain a symbolic link.

Note

To allow root access on the FlexFrame nodes, modify the FlexFrame default export option for these two parts of the addon volume from anon=0.

For assistance with setting up the directories, contact Fujitsu Customer Support.

Procedure

  1. Create a volume using the following NetApp command:

     
    volume create addon -vserver vserver_name -policy policy_name -l C.UTF-8 aggr2 -size volume_size -state online -unix-permissions ---rwxr-xr-x -type RW -junction-path /vol/addon

    Where:

    • vserver_name is the name of the Vserver.

    • storage_policy_name is the FlexFrame policy.

    • volume_size is the size of the volume, for example, 100GB.

    The following example creates a volume on the Vserver that is named svm1 that is 100GB and uses the fo_rw_CN_ro_all standard policy. In this example, the parameters are listed on the command line:

    volume create addon -vserver svm1 -policy ffo_rw_CN_ro_all -l C.UTF-8 aggr2 -size 100GB -state online -unix-permissions ---rwxr-xr-x -type RW -junction-path /vol/addon

  2. Create qtrees—pool specific and host specific—under the volume that you created.

    Pool qtree

    qtree create /vol/addon/commvault_pool

    Example of pool qtree:

    qtree create /vol/addon/commvault_p01

    Host qtree

    qtree create /vol/addon/commvault_host_pool

    Example of host qtree:

    qtree create /vol/addon/commvault_host_p01
    mkdir /vol/addon/commvault_pool
mkdir /vol/addon/commvault_host_pool

    Example:

    cn1:~ # mkdir /FlexFrame/fas04/vol/addon/commvault_p01
cn1:~ # mkdir /FlexFrame/fas04/vol/addon/commvault_host_p01

  3. Add automount for the qtrees that you created. A FlexFrame administrator can modify the automount of the commvault pool using the ff_custom_mnt_adm.pl script that is available in the Toolbox of FlexFrame Service DVD.

    The commvault_<pool> qtree should be mounted as commvault_pool. The commvault_host_<pool> to be mounted as commvault_host.

    For pool specific part, run the following command:

    cn1:~ # ff_custom_mnt_adm.pl --op add --pool pool --name addon --entry commvault_pool --volume filer:/vol/addon/commvault_pool --export sec=sys,rw=10.10.243.0/24,root=10.10.243.0/24,anon=0 --description "Pool-specific part for Commvault p01"

    Example: 

    cn1:~ # ff_custom_mnt_adm.pl --op add --pool p01 --name addon --entry commvault_pool --volume filer-01-p01-st:/vol/addon/commvault_p01 --export sec=sys$,rw=$[10.10.243.0/24,root=10.10.243.0/24,anon=0 --description "Pool-specific part for Commvault p01"

    For host specific part, run the following command:

    cn1:~ # ff_custom_mnt_adm.pl --op add --pool pool --name addon --entry commvault_host –volume filer:/vol/addon/commvault_host_pool --export -sec=sys,rw=10.10.243.0/24,root=10.10.243.0/24,anon=0 –description "Host-specific part for Commvault p01" --expandpath HOST

    Example:

    cn1:~ # ff_custom_mnt_adm.pl --op add --pool p01 --name addon --entry commvault_host –volume filer-01-p01-st:/vol/addon/commvault_host_p01 --export -sec=sys,rw=10.10.243.0/24,root=10.10.243.0/24,anon=0 –description "Host-specific part for Commvault p01" --expandpath HOST

  4. Create a directory structure under the host specific qtree and pool specific qtree. In the following command, esx01 is the hostname.

    cn1:/FlexFrame/fas04/addon/commvault_host_p01 # mkdir -p esx01/etc/init.d 
cn1:/FlexFrame/fas04/addon/commvault_host_p01 # mkdir –m 775 -p esx01/etc/CommVaultRegistry 
cn1:/FlexFrame/fas04/addon/commvault_host_p01 # mkdir –m 770 -p esx01/local 
cn1:/FlexFrame/fas04/addon/commvault_host_p01 # mkdir –m 770 -p esx01/opt/commvault 
cn1:/FlexFrame/fas04/addon/commvault_host_p01 # chgrp 4711 esx01/etc/CommVaultRegistry 
cn1:/FlexFrame/fas04/addon/commvault_host_p01 # chgrp 4711 esx01/local 
cn1:/FlexFrame/fas04/addon/commvault_host_p01 # chgrp 4711 esx01/opt 
cn1:/FlexFrame/fas04/addon/commvault_host_p01 # touch esx01/etc/init.d/Galaxy 
cn1:/FlexFrame/fas04/addon/commvault_p01 # mkdir –m 770 job_results IndexCache db2dirs scripts config
cn1:/FlexFrame/fas04/addon/commvault_p01 # chgrp 4711 job_results 
cn1:/FlexFrame/fas04/addon/commvault_p01 # chgrp 4711 IndexCache 
cn1:/FlexFrame/fas04/addon/commvault_p01 # chgrp 4711 db2dirs
cn1:/FlexFrame/fas04/addon/commvault_p01 # chgrp 4711 scripts
cn1:/FlexFrame/fas04/addon/commvault_p01 # chgrp 4711 config

    Note

    Directory db2dirs is required only when using DB2 databases

  5. Restart automounter, and then prepare directories and links in Maintenance mode. You must perform the changes on the virtual machine.

    Below example is performed on machine esx01 that is running in maintenance mode.

    esx01:/ # rcautofs stop 
esx01:/ # mkdir /addon 
esx01:/ # rcautofs start 
esx01:/ # ln -s /addon/commvault_host/etc/init.d/Galaxy /etc/init.d/Galaxy 
esx01:/ # ln -s /addon/commvault_host/etc/CommVaultRegistry /etc/CommVaultRegistry 
esx01:/ # ln -s /addon/commvault_host/opt/commvault /opt/commvault
esx01:/ # chgrp -h commvault /etc/CommVaultRegistry 
esx01:/ # chgrp -h commvault /opt/commvault 
esx01:/ # ln -s /addon/commvault_host/local/db2ls /usr/local/bin/db2ls
esx01:/ # ln -s /opt/commvault/installer/detect /usr/bin/detect 
esx01:/ # ln -s /opt/commvault/installer/support /usr/bin/support
esx01:/ # ln -s /opt/commvault/Base64/cvpkgchg /usr/bin/cvpkgchg
esx01:/ # ln -s /opt/commvault/Base64/cvpkgcheck /usr/bin/cvpkgcheck
esx01:/ # chgrp -h commvault /usr/bin/cvpkgcheck /usr/bin/cvpkgchg /usr/bin/support /usr/bin/detect

    Verify that the links are created properly:

    esx01:/ # cd /usr/bin
esx01:/usr/bin # ls -l cvpkgcheck cvpkgchg support detect

    The output must be similar to the following:

    lrwxrwxrwx 1 root commvault 32 Jun 30 12:26 cvpkgcheck -> /opt/commvault/Base64/cvpkgcheck
lrwxrwxrwx 1 root commvault 30 Jun 30 12:25 cvpkgchg -> /opt/commvault/Base64/cvpkgchg
lrwxrwxrwx 1 root commvault 31 Jun 30 12:25 detect -> /opt/commvault/installer/detect
lrwxrwxrwx 1 root commvault 32 Jun 30 12:25 support -> /opt/commvault/installer/support

    Verify that /etc/init.d/Galaxy is not a dangling link and the Galaxy file is empty.

  6. Create additional links to enable the automatic start of the Commvault software when the system boots.

    To resolve the dangling links, on the control node, run the insserv command and use the ff_new_an.custom script that is available in the Toolbox of FlexFrame Service DVD

     
    cn1:~ # vi /FlexFrame/volFF/os/Linux/<OSIMAGE>/ff_new_an.custom
 [...]
# Enable Galaxy-Service for Commvault
 ln -s ../Galaxy $ROOT_IMG/etc/init.d/rc3.d/K01Galaxy
 ln -s ../Galaxy $ROOT_IMG/etc/init.d/rc5.d/K01Galaxy

    Where KO1Galaxy is the SID ID.

  7. To modify the Commvault log files directory for database agents, use the following command:

    # chmod g+s /var/log/commvault/Log_Files

  8. Bring the system out of the Maintenance Mode.

What to Do Next

Boot the Application Node and verify that the following conditions are met:

  • /opt/commvault is a dangling link.

  • /etc/init.d/Galaxy is not a dangling link.

  • The job_results directory and the IndexCache directory of the pool-specific directory/addon/commvault_pool belong to the commvault group and have 770 permissions.

  • If you use the DB2 database application, then you must have the /var/db2 directory with permissions 777.

  • If you use the SAP Oracle database application, then you need to create the /tmp/sapexe directory with 777 permissions.

  • If you use the SAP HANA for IntelliSnap application, set one of the following NFS options on the source data volumes before taking a snapshot.

    • lookupcache=pos

    • lookupcache=none

    At the time of a revert operation, the software inherits the mount options set on the data volumes to the snapshot volumes.

×

Loading...