Veritas InfoScale™ 7.3.1 Virtualization Guide - Solaris

Last Published:
Product(s): InfoScale & Storage Foundation (7.3.1)
Platform: Solaris
  1. Section I. Overview of Veritas InfoScale Solutions used in Solaris virtualization
    1. Overview of Veritas InfoScale Virtualization Solutions
      1.  
        Overview of the Veritas InfoScale Products Virtualization Guide
      2. About Veritas InfoScale support for Solaris virtualization technology
        1. About SmartIO in the Solaris virtualized environments
          1.  
            Performing live migration between LDOMs in the SmartIO environment
      3.  
        Virtualization use cases addressed by Veritas InfoScale products
  2. Section II. Zones and Projects
    1. Storage Foundation and High Availability Solutions support for Solaris Zones
      1.  
        About Solaris Zones
      2. About VCS support for zones
        1.  
          Overview of how VCS works with zones
        2.  
          About the ContainerInfo service group attribute
        3.  
          About the ContainerOpts resource type attribute
        4.  
          About the ResContainerInfo resource type attribute
        5.  
          Zone-aware resources
        6. About the Mount agent
          1.  
            Sample configurations for Physical-to-Virtual (P2V) scenarios
          2.  
            Bringing a Mount resource online in the zone
          3.  
            Setting the attribute values for a Mount resource for NFS mounts
          4.  
            Configuring a direct mount of VxFS file system in a non-global zone with VCS
        7.  
          About networking agents
        8.  
          About the Zone agent
        9.  
          About configuring failovers among physical and virtual servers
      3. Configuring VCS in zones
        1. Prerequisites for configuring VCS in zones
          1.  
            Method for file system access inside non-global zone
          2.  
            Using custom agents in zones
        2. Deciding on the zone root location
          1.  
            Creating a zone with root on local disk
          2.  
            Creating a zone with root on shared storage
        3.  
          Performing the initial internal zone configuration
        4.  
          About installing applications in a zone
        5. Configuring the service group for the application
          1.  
            Resource dependency diagrams: zone root on local disks
          2.  
            Resource dependency diagrams: zone root on shared disks
        6.  
          Configuring a zone resource in a failover service group with the hazonesetup utility
        7.  
          Configuring zone resource in a parallel service group with the hazonesetup utility
        8.  
          Configuring multiple zone resources using same VCS user for password less communication
        9.  
          Modifying the service group configuration
        10.  
          Verifying the zone configuration
        11.  
          Synchronizing the zone configuration across cluster nodes
        12.  
          Performing maintenance tasks
        13.  
          Troubleshooting zones
        14.  
          Configuring for physical to virtual and virtual to physical failovers - a typical setup
      4.  
        Adding VxFS file systems to a non-global zone
      5.  
        Mounting VxFS as lofs into a non-global zone
      6.  
        Mounting VxFS directly into a non-global zone from global zone
      7.  
        Mounting VxFS as VxFS inside a non-global zone
      8.  
        Adding a direct mount to a zone's configuration
      9.  
        Benefits of a VxFS mount in a non-global zone over VxFS mount from global zone into the non-global zone
      10.  
        SFCFSHA mounts
      11.  
        Concurrent I/O access in non-global zones
      12.  
        Veritas Extension for Oracle Disk Manager
      13. Exporting VxVM volumes to a non-global zone
        1.  
          VxVM devices in Oracle Solaris global zones
        2.  
          Removing a VxVM volume from a non-global zone
      14. About SF Oracle RAC support for Oracle RAC in a zone environment
        1.  
          Supported configuration
        2. Known issues with supporting SF Oracle RAC in a zone environment
          1.  
            CFS mount agent does not support mounting VxVM devices inside non-global zones
          2.  
            Issue with VCS agents
          3.  
            Stopping non-global zones configured with direct-mount file systems from outside VCS causes the corresponding zone resource to fault or go offline
          4.  
            Error message displayed for PrivNIC resource if zone is not running
          5.  
            Warning messages displayed when VCS restarts
          6.  
            The installer log of non-global zone contains warning messages
          7.  
            Issue with CFS mounts
      15.  
        Configuring Solaris non-global zones for disaster recovery
      16. Software limitations of Storage Foundation support of non-global zones
        1.  
          Administration commands are not supported in non-global zone
        2.  
          VxFS file system is not supported as the root of a non-global zone
        3.  
          QIO and CQIO are not supported
        4.  
          Package installation in non-global zones
        5.  
          Package removal with non-global zone configurations
        6.  
          Root volume cannot be added to non-global zones
        7.  
          Some Veritas Volume Manager operations can cause volume device names to go out of sync
    2. Storage Foundation and High Availability Solutions support for Solaris Projects
      1.  
        About Solaris Projects
      2. About VCS support for Solaris projects
        1. Overview of how VCS works with Solaris projects
          1.  
            How VCS models containers
          2.  
            Installing and configuring projects in a VCS environment
          3.  
            Configuring the ContainerInfo attribute
        2.  
          About the ContainerInfo service group attribute
        3.  
          About the ContainerOpts resource type attribute
        4.  
          Project-aware resources
        5.  
          About the Project agent
      3. Configuring VCS in Solaris projects
        1. Prerequisites for configuring VCS in projects
          1.  
            Using custom agents in projects
  3. Section III. Oracle VM Server for SPARC
    1. Storage Foundation and High Availability Solutions support for Oracle VM Server for SPARC
      1.  
        About Oracle VM Server for SPARC
      2.  
        Terminology for Oracle VM Server for SPARC
      3. Oracle VM Server for SPARC deployment models
        1.  
          Split Storage Foundation stack
        2.  
          Guest-based Storage Foundation stack
        3.  
          Layered Storage Foundation stack
      4. Benefits of deploying Storage Foundation High Availability solutions in Oracle VM server for SPARC
        1.  
          Standardization of tools
        2.  
          Array migration
        3.  
          Moving storage between physical and virtual environments
        4.  
          Boot Image Management
      5. Features
        1. Storage Foundation features
          1. The vxloadm utility enables access to a file system contained in a VxVM volume from the Control Domain
            1.  
              Examples of using the vxloadm utility
          2. The vxformat utility automatically relabels the virtual disk backed by a VxVM volume in the guest domain
            1.  
              Example of using the vxformat utility
        2. Oracle VM Server for SPARC features
          1.  
            Guest domain migration
          2.  
            Virtual I/O dynamic reconfiguration
      6. Split Storage Foundation stack model
        1.  
          How Storage Foundation and High Availability Solutions works in the Oracle VM Server for SPARC
        2.  
          Storage Foundation features restrictions
      7. Guest-based Storage Foundation stack model
        1.  
          How Storage Foundation and High Availability Solutions works in the guest domains
        2. About SFCFSHA in an Oracle VM Server for SPARC environment
          1.  
            Supported configurations with SFCFSHA and multiple I/O Domains
          2.  
            SFCFSHA limitations
        3. Storage Foundation features restrictions
          1.  
            Veritas Volume Replicator bunker replication
          2.  
            Mirroring across controllers using vxassist the mirror=ctlr option
          3.  
            DMP SCSI bypass
          4.  
            Event Source Daemon (vxesd) fabric monitoring capabilities
          5.  
            Physical WWN for a path
      8. Layered Storage Foundation stack model
        1. DMP as a multi-pathing solution in an Oracle VM Server for SPARC environment
          1.  
            Enabling DMP in the control and alternate I/O domains
          2.  
            Enabling DMP path failover in the guest domain
          3.  
            Enabling I/O fencing in the guest domain
        2.  
          How Storage Foundation and High Availability Solutions works in the Oracle VM Server for SPARC
        3.  
          Storage Foundation features restrictions
      9. System requirements
        1.  
          Hardware requirements
      10.  
        Product release notes
      11.  
        Product licensing
      12. Installing Storage Foundation in a Oracle VM Server for SPARC environment
        1.  
          Installing and configuring Oracle VM Server for SPARC and domains
        2. Installing Storage Foundation in the control domain or guest
          1.  
            Installing the split Storage Foundation stack model
          2.  
            Installing the guest-based Storage Foundation stack model
        3.  
          Installing Veritas File System in the guest domain
        4.  
          Verifying the configuration
      13.  
        Exporting a Veritas volume to a guest domain from the control domain
      14. Provisioning storage for a guest domain
        1.  
          Provisioning Veritas Volume Manager volumes as data disks for guest domains
        2. Provisioning Veritas Volume Manager volumes as boot disks for guest domains
          1. Using VxVM mirrored volumes as boot devices for Ldoms
            1.  
              Provisioning boot disks for a guest domain
            2.  
              Using VxVM snapshot as a backup copy of the boot image during the upgrade
            3.  
              Restore the original environment
      15.  
        Using Veritas Volume Manager snapshots for cloning logical domain boot disks
      16.  
        Support of live migration for Solaris LDOMs with fencing configured in DMP mode
      17.  
        Configuring Oracle VM Server for SPARC guest domains for disaster recovery
      18. Software limitations
        1.  
          When an I/O domain fails, the vxdisk scandisks or vxdctl enable command take a long time to complete (2791127)
        2.  
          Resizing a Veritas Volume Manager volume (exported as a slice or full disk) does not dynamically reflect the new size of the volume in the guest
      19. Known issues
        1. Guest-based known issues
          1.  
            Encapsulating a non-scsi disk may fail (1745409)
          2.  
            Guest domain node shows only one PGR key instead of two after rejecting the other node in the cluster
          3.  
            Disk paths intermittently go offline while performing I/O on a mirrored volume
        2. Split Storage Foundation stack known issues
          1.  
            Caching of data writes on the backend volume in the service domain
          2.  
            A volume can become inaccessible from the guest in the event of control domain reboot
    2. Cluster Server support for using CVM with multiple nodes in a Oracle VM Server for SPARC environment
      1.  
        Clustering using Cluster Volume Manager
      2. Installing Storage Foundation on multiple nodes in a Logical Domain
        1. Reconfiguring the clustering agents for Cluster Volume Manager
          1.  
            Removing the vxfsckd resource
          2.  
            Creating CVMVolDg in a group
      3. Cluster Volume Manager in the control domain for providing high availability
        1.  
          Provisioning storage to guests with Flexible Storage Sharing volumes of control domain
    3. VCS: Configuring Oracle VM Server for SPARC for high availability
      1. About VCS in a Oracle VM Server for SPARC environment
        1.  
          Benefits of using VCS in Oracle VM server for SPARC environments to manage logical domains
        2.  
          Dynamic reconfiguration of memory and CPU of a guest domain
        3.  
          AdaptiveHA for logical domains
        4.  
          Cluster Server requirements
        5.  
          Cluster Server limitations
        6. Cluster Server known issues
          1.  
            Shutting down the control domain may cause the guest domain to crash (1631762)
      2. About Cluster Server configuration models in an Oracle VM Server for SPARC environment
        1. Cluster Server setup to fail over a logical domain on a failure of logical domain
          1. Configuration scenarios
            1.  
              Network configuration
            2. Storage configurations
              1.  
                Veritas Volume Manager exposed volumes
              2.  
                Image files
            3.  
              Configuring logical domain
            4.  
              Installing Cluster Server inside the control domain
          2.  
            Creating the VCS service groups for logical domains
          3. Verifying a logical domain service group failover
            1.  
              Using hagrp -switch command
            2.  
              Other verification scenarios
        2. Cluster Server setup to fail over an Application running inside logical domain on a failure of Application
          1.  
            Configuring VCS to fail over an application on a failure
      3. Oracle VM Server for SPARC guest domain migration in VCS environment
        1.  
          Overview of a warm migration
        2. Overview of a live migration
          1. VCS initiated migration of service groups that have LDom resource configured to monitor Oracle VM for SPARC guest domains
            1.  
              Troubleshooting migration-related issues
          2.  
            User initiated migration of Oracle VM guest domains managed by VCS
        3.  
          Prerequisites before you perform domain migration
        4.  
          Supported deployment models for Oracle VM Server for SPARC domain migration with VCS
        5.  
          Migrating Oracle VM guest when VCS is installed in the control domain that manages the guest domain
        6.  
          Migrating Oracle VM guest when VCS is installed in the control domain and single-node VCS is installed inside the guest domain to monitor applications inside the guest domain
        7.  
          Migrating Oracle VM guest when VCS cluster is installed in the guest domains to manage applications for Oracle VM Server for SPARC version 2.1 and above
        8.  
          Migrating Oracle VM guest when VCS cluster is installed in the guest domains to manage applications for Oracle VM Server for SPARC version 2.0
      4. About configuring VCS for Oracle VM Server for SPARC with multiple I/O domains
        1.  
          About Alternate I/O domain
        2.  
          Setting up the Alternate I/O domain
        3.  
          Configuring VCS to manage a Logical Domain with multiple I/O domains
      5. Configuring VCS to manage a Logical Domain using services from multiple I/O domains
        1.  
          A typical setup for a Logical Domain with multiple I/O services
        2.  
          Identify supported storage and network services
        3.  
          Determine the number of nodes to form VCS cluster
        4.  
          Install and configure VCS inside the control domain and alternate I/O domain
        5. Configuring storage services
          1.  
            Configuring virtual disk with LUN, Shared Disk, or CVM Volume
          2.  
            Virtual disk configurations with DMP
          3.  
            Configuring storage services when back-end device is a ZFS volume
        6.  
          Configure storage service groups
        7.  
          Configure network service groups
        8. Configure a service group to monitor services from multiple I/O domains
          1.  
            Type of service group configuration for the AlternateIO resource
        9. Configure the AlternateIO resource
          1.  
            Sample service group configuration for the AlternateIO resource
        10. Configure the service group for a Logical Domain
          1.  
            Sample configuration for LDom service group
        11.  
          Failover scenarios
        12.  
          Recommendations while configuring VCS and Oracle VM Server for SPARC with multiple I/O domains
        13.  
          Sample VCS configuration for AlternateIO resource configured as a fail over type
      6.  
        Configuring VCS on logical domains to manage applications using services from multiple I/O domains
    4. SF Oracle RAC support for Oracle VM Server for SPARC environments
      1.  
        About deploying SF Oracle RAC in Oracle VM Server for SPARC environments
      2.  
        Sample configuration scenarios
      3.  
        Preparing to deploy SF Oracle RAC in logical domain environments
      4.  
        SF Oracle RAC with Oracle RAC database on I/O domains of two hosts
      5.  
        SF Oracle RAC with Oracle RAC database on guest domains of two hosts
      6.  
        SF Oracle RAC with Oracle RAC database on guest domains of single host
      7.  
        SF Oracle RAC with Oracle RAC database on I/O domain and guest domain of single host
    5. Support for live migration in FSS environments
      1.  
        About live migration in Flexible Storage Sharing (FSS) environments
      2.  
        Performing live migration of Oracle VM Server for SPARC systems in Flexible Storage Sharing (FSS) environments
  4. Section IV. Reference
    1. Appendix A. Where to find more information
      1.  
        Veritas InfoScale documentation
      2.  
        Solaris virtualization documentation
      3.  
        Service and support
      4.  
        About Veritas Services and Operations Readiness Tools (SORT)

Using Veritas Volume Manager snapshots for cloning logical domain boot disks

The following highlights the steps to clone the boot disk from an existing logical domain using VxVM snapshots, and makes use of the third-mirror breakoff snapshots.

See Provisioning Veritas Volume Manager volumes as boot disks for guest domains.

Figure: Example of using Veritas Volume Manager snapshots for cloning Logical Domain boot disks illustrates an example of using Veritas Volume Manager snapshots for cloning Logical Domain boot disks.

Figure: Example of using Veritas Volume Manager snapshots for cloning Logical Domain boot disks

Example of using Veritas Volume Manager snapshots for cloning Logical Domain boot disks

Before this procedure, ldom1 has its boot disk contained in a large volume, /dev/vx/dsk/boot_dg/bootdisk1-vol.

This procedure involves the following steps:

  • Cloning the logical domain configuration to form a new logical domain configuration.

    This step is a Solaris logical domain procedure, and can be achieved using the following commands:

    # ldm list-constraints -x
    # ldm add-domain -i

    Refer to the Oracle documentation for more information about cloning the logical domain configuration to form a new logical domain configuration.

    See the Oracle VMServer for SPARC Administration Guide.

  • After cloning the configuration, clone the boot disk and provision it to the new logical domain.

    To create a new logical domain with a different configuration than that of ldom1, skip this step of cloning the configuration and create the desired logical domain configuration separately.

To clone the boot disk using Veritas Volume Manager snapshots

  1. Create a snapshot of the source volume bootdisk1-vol. To create the snapshot, you can either take some of the existing ACTIVE plexes in the volume, or you can use the following command to add new snapshot mirrors to the volume:
    primary# vxsnap [-b] [-g diskgroup] addmir volume \
    [nmirror=N] [alloc=storage_attributes]

    By default, the vxsnap addmir command adds one snapshot mirror to a volume unless you use the nmirror attribute to specify a different number of mirrors. The mirrors remain in the SNAPATT state until they are fully synchronized. The -b option can be used to perform the synchronization in the background. Once synchronized, the mirrors are placed in the SNAPDONE state.

    For example, the following command adds two mirrors to the volume, bootdisk1-vol, on disks mydg10 and mydg11:

    primary# vxsnap -g boot_dg addmir bootdisk1-vol \
    nmirror=2 alloc=mydg10,mydg11

    If you specify the -b option to the vxsnap addmir command, you can use the vxsnap snapwait command to wait for synchronization of the snapshot plexes to complete, as shown in the following example:

    primary# vxsnap -g boot_dg snapwait bootdisk1-vol nmirror=2
  2. To create a third-mirror break-off snapshot, use the following form of the vxsnap make command.

    Caution:

    Shut down the guest domain before executing the vxsnap command to take the snapshot.

    primary# vxsnap [-g diskgroup] make \ 
    source=volume[/newvol=snapvol] \
    {/plex=plex1[,plex2,...]|/nmirror=number]}

    Either of the following attributes may be specified to create the new snapshot volume, snapvol, by breaking off one or more existing plexes in the original volume:

    plex

    Specifies the plexes in the existing volume that are to be broken off. This attribute can only be used with plexes that are in the ACTIVE state.

    nmirror

    Specifies how many plexes are to be broken off. This attribute can only be used with plexes that are in the SNAPDONE state. Such plexes could have been added to the volume by using the vxsnap addmir command.

    Snapshots that are created from one or more ACTIVE or SNAPDONE plexes in the volume are already synchronized by definition.

    For backup purposes, a snapshot volume with one plex should be sufficient.

    For example,

    primary# vxsnap -g boot_dg make \
    source=bootdisk1-vol/newvol=SNAP-bootdisk1-vol/nmirror=1

    Here bootdisk1-vol makes source; SNAP-bootdisk1-vol is the new volume and 1 is the nmirror value.

    The block device for the snapshot volume will be /dev/vx/dsk/boot_dg/SNAP-bootdisk1-vol.

  3. Configure a service by exporting the/dev/vx/dsk/boot_dg/SNAP-bootdisk1-vol file as a virtual disk.
    primary# ldm add-vdiskserverdevice \ 
    /dev/vx/dsk/boot_dg/SNAP-bootdisk1-vol vdisk2@primary-vds0
  4. Add the exported disk to ldom1 first.
    primary# ldm add-vdisk vdisk2 \
    SNAP-bootdisk1-vol@primary-vds0 ldom1
    primary# ldm bind ldom1 
    primary# ldm start ldom1
  5. Start ldom1 and boot ldom1 from its primary boot disk vdisk1.
    primary# ldm bind ldom1 
    primary# ldm start ldom1
  6. If the new virtual disk device node entries do not show up in the/dev/[r]dsk directories, then run the devfsadm command in the guest domain:
    ldom1# devfsadm -C

    where vdisk2 is the c0d2s# device.

    ldom1# ls /dev/dsk/c0d2s* 
    /dev/dsk/c0d2s0 /dev/dsk/c0d2s2 /dev/dsk/c0d2s4 /dev/dsk/c0d2s6
    /dev/dsk/c0d2s1 /dev/dsk/c0d2s3 /dev/dsk/c0d2s5 /dev/dsk/c0d2s7
  7. Mount the root file system of c0d2s0 and modify the /etc/vfstab entries such that all c#d#s# entries are changed to c0d0s#. You must do this because ldom2 is a new logical domain and the first disk in the operating system device tree is always named as c0d0s#.
  8. Stop and unbind ldom1 from its primary boot disk vdisk1.
    primary# ldm stop ldom1
    primary# ldm unbind ldom1
  9. After you change the vfstab file, unmount the file system and unbind vdisk2 from ldom1:
    primary# ldm remove-vdisk vdisk2 ldom1
  10. Bind vdisk2 to ldom2 and then start and boot ldom2.
    primary# ldm add-vdisk vdisk2 vdisk2@primary-vds0 ldom2 
    primary# ldm bind ldom2 
    primary# ldm start ldom2

    After booting ldom2, appears as ldom1 on the console because the other host-specific parameters like hostname and IP address are still that of ldom1.

    ldom1 console login:
  11. To change the parameters bring ldom2 to single-user mode and run the sys-unconfig command.
  12. Reboot ldom2.

    During the reboot, the operating system prompts you to configure the host-specific parameters such as hostname and IP address, which you must enter corresponding to ldom2.

  13. After you have specified all these parameters, ldom2 boots successfully.