Veritas Access Installation Guide

Pre-upgrade steps only for the LTR-configured Veritas Access cluster

1. Ensure that the backup or restore jobs from NetBackup are stopped.
2. If you are performing an upgrade from Veritas Access 7.3.1, copy the upgrade_scripts/odd_config_export_va731.py script from the ISO to / (root directory) on the management console node.
3. Execute the respective script to export the OpenDedup configuration:

   For 7.3.1: python odd_config_export_va731.py [filename]

   Note:

   If a file name is not provided, the default config file name, odd_config.exp is used.

To export the Veritas Access configurations

1. You can export the Veritas Access configurations by using the script provided by Veritas Access.

   Prerequisites:

   • RHEL 7.3 or later should be installed.

   • Veritas Access version 7.3.1 or later should be installed.

   • Make sure that you have stopped all I/Os and services related to Veritas Access such as CIFS, NFS, and FTP using the Veritas Access command-line interface.

   • Make sure that operations like create, destroy, add, and remove are not running since they may update the Veritas Access configuration.

2. From the ISO, copy the upgrade_scripts/config_export directory to the root directory of the cluster node on which the management console service group is online.
3. From the directory, run the following command on the shell (terminal) by using the support login to export the Veritas Access configurations:

   /bin/bash -f export_lib.sh export local filename

To verify the Veritas Access configuration export

• Run the following command using the Veritas Access command-line interface to see the list of available configurations:

  system config list

  you can find the configuration files in the /opt/VRTSnas/conf/backup location.

  Note:

  Store the configuration files on a node that is not part of the cluster nodes to avoid any damage to the configuration file.

To install the required version of RHEL

1. Prerequisites:

   • Make sure that you stop all the I/O processes and modules that are running on the Veritas Access command-line interface.

   • Run the network> ip addr show command and cluster> show command on the Veritas Access command-line interface before you install the RHEL operating system. Make a note of these IP addresses and cluster node names. Make sure to use the same IP addresses and cluster name when you install the Veritas Access cluster after the RHEL operating system is installed.

   Examples:

   upgrade> network ip addr show
   
   IP             Netmask/Prefix Device  Node        Type     Status
   --             -------------- ------  ----        ----     ------
   192.168.10.151 255.255.255.0  pubeth0 upgrade_01  Physical
   192.168.10.158 255.255.255.0  pubeth1 upgrade_01  Physical
   192.168.10.152 255.255.255.0  pubeth0 upgrade_02  Physical
   192.168.10.159 255.255.255.0  pubeth1 upgrade_02  Physical
   192.168.10.174 255.255.255.0  pubeth0 upgrade_01  Virtual  ONLINE(Con IP)
   192.168.10.160 255.255.255.0  pubeth0 upgrade_01  Virtual  ONLINE
   192.168.10.161 255.255.255.0  pubeth1 upgrade_01  Virtual  ONLINE
   

   upgrade> cluster show 
   
   Node       State    CPU(15 min)   pubeth0(15 min)     pubeth1(15 min) 
                           %        rx(MB/s) tx(MB/s)   rx(MB/s) tx(MB/s)
   ----       -----    -----------  -------- --------   -------- --------
   upgrade_01 RUNNING  11.52          0.67     0.06       0.60     0.00 
   upgrade_02 RUNNING   4.19          0.61     0.05       0.60     0.00 

   Note:

   In this example, the cluster name is upgrade and the cluster node names are upgrade_01 and upgrade_02.

2. Restart all the nodes of the cluster.
3. Install the supported RHEL operating system on the desired nodes.

   See Installing the operating system on each node of the cluster.

   Note:

   Veritas recommends to select the same disk or disks for the installation on which your previous version of the RHEL operating system was installed. Make sure that you do not select any other disk, because those disks may be part of a pool, and may result in data loss.

To install Veritas Access 7.4.2

• Restart the nodes and when they are up, start the Veritas Access 7.4.2 installation using the installer.

  Note:

  Make sure that you use the same IP addresses and cluster name that were used for the previous Veritas Access installation.

  See Installing Veritas Access on the target cluster nodes.

To verify the Veritas Access installation

1. By using the console IP, check whether the Veritas Access command-line interface is accessible.
2. Run the following command on the Veritas Access command-line interface to see whether the disks are accessible:

   storage disk list

   Note:

   If the disks are not visible in the command line output, run the storage scanbus force command on the Veritas Access command-line.

3. Run the following command to see whether the pools are accessible:

   storage pool list

   Note:

   If the pools are not visible in the command line output, run the storage scanbus force command on the Veritas Access command-line.

4. Run the following command to see whether the file systems are accessible:

   storage fs list

   Note:

   If the file systems are not visible in the command line output, run the storage scanbus force command on the Veritas Access command-line.

5. Make sure that the file systems are online. If the file systems are not online, you need to run the following command on the Veritas Access command-line to bring them online:

   storage fs online fs name

To import the Veritas Access configuration

1. Prerequisites:

   Make sure that the file systems are online. If the file systems are not online, you need to run the following command in the Veritas Access command-line interface to bring them online:

   storage fs online <fs name>

   Note:

   Make sure that the cluster uses the same IP addresses and cluster names that were used for the Veritas Access installation on the previous version of the operating system.

   If the same virtual IP addresses which were used for Veritas Access on the previous RHEL version are not added during installation, add the virtual IPs from the Veritas Access command-line interface after Veritas Access is installed on the latest RHEL version, and then import the configuration.

2. Copy the exported configuration files to the cluster nodes to the /opt/VRTSnas/conf/backup/ location.
3. Run the following command to see the available exported configuration:

   system config list

4. Import the module configuration file by using the following command:

   system config import local config-filename module-to-import

   You can import the following modules:

   upgrade> system config import local file_name [config-type]  
    -- Import the configuration which is stored locally
   
   file_name     : configuration file name
   config-type   : input type of configuration to import (network/admin/
   all/report/system/support/cluster_specific/all_except_cluster_specific/
   nfs/cifs/ftp/backup/replication/storage_schedules/storage_quota/
   storage_fs_alert/storage_fs_policy/compress_schedules/defrag_schedules/
   storage_dedup/smartio/target/object_access/loadbalance/opendedup/dedupe) 
   [all]
   
   upgrade> system config import local

   Note:

   The module names are auto-suggested in the Veritas Access command-line interface.

Post-upgrade steps only for the LTR-configured Veritas Access cluster

1. Start the required authentication services (AD, LDAP, or NIS), which are used by the ObjectAccess service.
2. If the upgrade is from Veritas Access 7.3.1 or later versions, set the pool for ObjectAccess, and enable the ObjectAccess as follows:

   Cluster1> objectaccess set pools pool1
   ACCESS ObjectAccess INFO V-493-10-0 Set pools successful. Please make 
   sure the storage is provisioned as per the requirements of the layout.
   Cluster1> objectaccess server enable
   100% [********************] Enabling ObjectAccess server.
   ACCESS ObjectAccess SUCCESS V-493-10-4 ObjectAccess server enabled.

3. Start the ObjectAccess service by using the following command:

   cluster2> objectaccess server start
   ACCESS ObjectAccess SUCCESS V-493-10-4 ObjectAccess started successfully.

4. Import the OpenDedup configuration by using the following command.

   cluster2> system config import remote file location opendedup

   Note:

   You can import the OpenDedup configuration that you have exported by using the steps provided in the Pre-upgrade steps only for the LTR-configured Veritas Access cluster.

5. Take all the OpenDedup volumes offline by using the following command:

   cluster2> opendedup volume offline vol-name

6. Update the OpenDedup /etc/sdfs/<vol-name>-volume-cfg.xml config file by adding the dist-layout="false" parameter to the extended-config tag.

   Where <vol-name> is the name of the OpenDedup volume.

   Note:

   This parameter should not be used for the existing OpenDedup volumes because they may have existing data with the default layout. If you use the existing OpenDedup volumes, it may result in data corruption.

7. Bring all the OpenDedup volumes online by using the following command:

   cluster2> opendedup volume online vol-name