Storage Foundation 7.4.1 Configuration and Upgrade Guide - Solaris

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.1)
Platform: Solaris
  1. Section I. Introduction and configuration of Storage Foundation
    1. Introducing Storage Foundation
      1. About Storage Foundation
        1.  
          About Veritas Replicator Option
      2.  
        About Veritas InfoScale Operations Manager
      3.  
        About Veritas Services and Operations Readiness Tools (SORT)
    2. Configuring Storage Foundation
      1.  
        Configuring Storage Foundation using the installer
      2. Configuring SF manually
        1. Configuring Veritas Volume Manager
          1.  
            Starting and enabling the configuration daemon
          2.  
            Starting the volume I/O daemon
          3.  
            Using vxinstall to configure Veritas Volume Manager
        2. Configuring Veritas File System
          1.  
            Loading and unloading the file system module
          2.  
            vxtunefs command permissions and Cached Quick I/O
      3.  
        Configuring SFDB
  2. Section II. Upgrade of Storage Foundation
    1. Planning to upgrade Storage Foundation
      1.  
        About the upgrade
      2.  
        Supported upgrade paths
      3. Preparing to upgrade SF
        1.  
          Getting ready for the upgrade
        2.  
          Creating backups
        3. Pre-upgrade planning when VVR is configured
          1. Planning an upgrade from the previous VVR version
            1.  
              Planning and upgrading VVR to use IPv6 as connection protocol
          2.  
            Additional settings for using VVR in a localized environment
        4.  
          Verifying that the file systems are clean
        5.  
          Upgrading the array support
      4.  
        Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
    2. Upgrading Storage Foundation
      1. Upgrading Storage Foundation to 7.4.1 using the product installer
        1.  
          Upgrading Storage Foundation with the product installer
      2. Upgrading Volume Replicator
        1. Upgrading VVR without disrupting replication
          1.  
            Upgrading VVR on the Secondary
          2.  
            Upgrading VVR on the Primary
      3.  
        Upgrading language packages
      4.  
        Upgrading SFDB
    3. Performing an automated SF upgrade using response files
      1.  
        Upgrading SF using response files
      2.  
        Response file variables to upgrade SF
      3.  
        Sample response file for SF upgrade
    4. Upgrading SF using Boot Environment upgrade
      1.  
        About ZFS Boot Environment (BE) upgrade
      2.  
        Supported upgrade paths for Boot Environment upgrade
      3. Performing Boot Environment upgrade on Solaris 11 systems
        1.  
          Creating a new Solaris 11 BE on the primary boot disk
        2.  
          Upgrading SF using the installer for upgrading BE on Solaris 11
        3.  
          Completing the SF upgrade on BE on Solaris 11
        4.  
          Verifying Solaris 11 BE upgrade
        5. Administering BEs on Solaris 11 systems
          1.  
            Reverting to the primary BE on a Solaris 11 system
      4.  
        About Live Upgrade in a Volume Replicator (VVR) environment
    5. Performing post-upgrade tasks
      1.  
        Optional configuration steps
      2.  
        Recovering VVR if automatic upgrade fails
      3.  
        Resetting DAS disk names to include host name in FSS environments
      4.  
        Upgrading disk layout versions
      5.  
        Upgrading VxVM disk group versions
      6.  
        Updating variables
      7.  
        Setting the default disk group
      8. Upgrading the Array Support Library
        1.  
          Adding JBOD support for storage arrays for which there is not an ASL available
        2. Unsuppressing DMP for EMC PowerPath disks
          1.  
            Converting a foreign disk to auto:simple
          2.  
            Converting a defined disk to auto:simple
          3.  
            Converting a powervxvm disk to auto:simple
      9.  
        Converting from QuickLog to Multi-Volume support
      10.  
        Verifying the Storage Foundation upgrade
  3. Section III. Post configuration tasks
    1. Performing configuration tasks
      1.  
        Changing root user into root role
      2.  
        Switching on Quotas
      3.  
        Enabling DMP support for native devices
      4. About configuring authentication for SFDB tools
        1.  
          Configuring vxdbd for SFDB tools authentication
  4. Section IV. Configuration and Upgrade reference
    1. Appendix A. Installation scripts
      1.  
        Installation script options
      2.  
        About using the postcheck option
    2. Appendix B. Configuring the secure shell or the remote shell for communications
      1.  
        About configuring secure shell or remote shell communication modes before installing products
      2.  
        Manually configuring passwordless ssh
      3.  
        Setting up ssh and rsh connection using the installer -comsetup command
      4.  
        Setting up ssh and rsh connection using the pwdutil.pl utility
      5.  
        Restarting the ssh session
      6.  
        Enabling and disabling rsh for Solaris

Starting the volume I/O daemon

The volume I/O daemon (vxiod) provides extended I/O operations without blocking calling processes. Several vxiod daemons are usually started at system boot time after initial installation, and they should be running at all times. The procedure below describes how to verify that the vxiod daemons are running, and how to start them if necessary.

To verify that vxiod daemons are running, enter the following command:

# vxiod

The vxiod daemon is a kernel thread and is not visible using the ps command.

If, for example, 16 vxiod daemons are running, the following message displays:

16 volume I/O daemons running

where 16 is the number of vxiod daemons currently running. If no vxiod daemons are currently running, start some by entering this command:

# vxiod set no_of_daemons

where the number of daemons ranges from 1 to16. Veritas recommends that at least one vxiod daemon should be run for each CPU in the system.

For more information, see the vxiod(1M) manual page.