Storage Foundation 7.2 Configuration and Upgrade Guide - Solaris

Last Published:
Product(s): InfoScale & Storage Foundation (7.2)
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 for Volume Replicator
          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.2 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.  
        Installing language packages
      3.  
        Switching on Quotas
      4.  
        Enabling DMP support for native devices
      5. 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

Converting a powervxvm disk to auto:simple

In VxVM 4.0, and particularly in previous releases, EMCpower disks can be defined by a persistent disk access record (darec) using powervxvm script, and identified as simple disks. If an EMCpower disk is used using powervxvm, it must be manually converted to auto:simple format before you upgrade to VxVM 7.2.

If there are any controllers or devices that are suppressed from VxVM as powervxvm requirement, then such controllers or disks must be unsuppressed. This is required for Veritas DMP to determine the association between PowerPath metanodes and their subpaths. After the conversion to auto:simple is complete, the powervxvm script is no longer useful, and should be disabled from startup script.

The following example is used to illustrate the procedure. The ls command shows the mapping of the EMC disks to persistent disk access records:

# ls -l /dev/vx/rdmp/
crw-------   1 root     root     260, 76 Feb  7 02:36 emcpower0c

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c6t0d12s2    auto:sliced       -            -          online
emcpower0c   simple          ppdsk01      ppdg         online
# vxprint
Disk group: fdg
TY NAME     ASSOC      KSTATE  LENGTH   PLOFFS STATE TUTIL0 PUTIL0
dg ppdg     ppdg       -       -        -      -     -      -
dm ppdsk01  emcpower0c -       2094960  -      -     -      -

To convert an EMCpower disk (defined using powervxvm) to auto:simple format

  1. Stop all the volumes in the disk group, and then deport it:
    # vxvol -g ppdg stopall
    # vxdg deport ppdg
  2. Use the vxdisk rm command to remove all emcpower disks from VxVM:
    # vxdisk rm emcpower0c

    If you now run the vxdisk list command, the EMCpower disk is no longer displayed:

    # vxdisk list
    DEVICE       TYPE            DISK         GROUP        STATUS
    c6t0d12s2    auto:sliced       -            -          online
  3. Use the vxprtvtoc command to retrieve the partition table entry for this device:
    # /etc/vx/bin/vxprtvtoc -f /tmp/vtoc /dev/vx/rdmp/emcpower0c
  4. Use the vxedvtoc command to modify the partition tag and update the VTOC:
    # /etc/vx/bin/vxedvtoc -f /tmp/vtoc /dev/vx/rdmp/emcpower0c 
    # THE ORIGINAL PARTITIONING IS AS FOLLOWS:
    # SLICE     TAG  FLAGS   START  SIZE
      0         0x0  0x201   0      0
      1         0x0  0x200   0      0
      2         0x5  0x201   0      17675520
    
    # THE NEW PARTITIONING WILL BE AS FOLLOWS:
    # SLICE     TAG  FLAGS   START  SIZE
      0         0xf  0x201   0      17675520
      1         0x0  0x200   0      0
      2         0x5  0x201   0      17675520
    
    DO YOU WANT TO WRITE THIS TO THE DISK ? [Y/N] :Y 
    WRITING THE NEW VTOC TO THE DISK #
  5. Upgrade to VxVM 7.2 using the appropriate upgrade procedure.
  6. After upgrading VxVM, use the vxdisk list command to validate the conversion to auto:simple format:
    # vxdisk list
    DEVICE       TYPE            DISK         GROUP        STATUS
    c6t0d12s2    auto:sliced       -            -          online
    emcpower0s2  auto:simple       -            -          online
  7. Import the disk group and start the volumes.
    # vxdg import ppdg
    # vxvol -g ppdg startall
    # vxdisk list
    
    DEVICE       TYPE            DISK         GROUP        STATUS
    c6t0d12s2    auto:sliced       -            -          online
    emcpower0s2  auto:simple     ppdsk01       ppdg        online