Veritas InfoScale™ 7.3.1 Virtualization Guide - Solaris
- Section I. Overview of Veritas InfoScale Solutions used in Solaris virtualization
- Section II. Zones and Projects
- Storage Foundation and High Availability Solutions support for Solaris Zones
- About VCS support for zones
- About the Mount agent
- Configuring VCS in zones
- Prerequisites for configuring VCS in zones
- Deciding on the zone root location
- Configuring the service group for the application
- Exporting VxVM volumes to a non-global zone
- About SF Oracle RAC support for Oracle RAC in a zone environment
- Known issues with supporting SF Oracle RAC in a zone environment
- Software limitations of Storage Foundation support of non-global zones
- Storage Foundation and High Availability Solutions support for Solaris Projects
- Storage Foundation and High Availability Solutions support for Solaris Zones
- Section III. Oracle VM Server for SPARC
- Storage Foundation and High Availability Solutions support for Oracle VM Server for SPARC
- Oracle VM Server for SPARC deployment models
- Benefits of deploying Storage Foundation High Availability solutions in Oracle VM server for SPARC
- Features
- Split Storage Foundation stack model
- Guest-based Storage Foundation stack model
- Layered Storage Foundation stack model
- System requirements
- Installing Storage Foundation in a Oracle VM Server for SPARC environment
- Provisioning storage for a guest domain
- Software limitations
- Known issues
- Cluster Server support for using CVM with multiple nodes in a Oracle VM Server for SPARC environment
- VCS: Configuring Oracle VM Server for SPARC for high availability
- About VCS in a Oracle VM Server for SPARC environment
- About Cluster Server configuration models in an Oracle VM Server for SPARC environment
- Cluster Server setup to fail over a logical domain on a failure of logical domain
- Cluster Server setup to fail over an Application running inside logical domain on a failure of Application
- Oracle VM Server for SPARC guest domain migration in VCS environment
- Overview of a live migration
- About configuring VCS for Oracle VM Server for SPARC with multiple I/O domains
- Configuring VCS to manage a Logical Domain using services from multiple I/O domains
- Configuring storage services
- Configure a service group to monitor services from multiple I/O domains
- Configure the AlternateIO resource
- Configure the service group for a Logical Domain
- SF Oracle RAC support for Oracle VM Server for SPARC environments
- Support for live migration in FSS environments
- Storage Foundation and High Availability Solutions support for Oracle VM Server for SPARC
- Section IV. Reference
Method for file system access inside non-global zone
File system mounts must meet one of the following two conditions:
Use a loopback file system with zone configuration. All mounts that the application uses must be part of the zone configuration and must be configured in the service group. For example, you can create a zone, z-ora, and define the file system containing the application's data to have the mount point as
/oradata
. When you create the zone, you can define a path in the global zone. An example is/export/home/oradata
, which the mount directory in the non-global zone maps to. The MountPoint attribute of the Mount resource for the application is set to/export/home/oradata
. Confirm that/export/home/oradata
maps to/oradata
with the zonecfg -z zone_name info command. You can also look into the zone configuration/etc/zones/zone_name.xml
file. The Zone resource depends on the Mount resource.Mount the file system inside zone's root-path. All file system mount points that the application uses that run in a zone must be set relative to the zone's root. For example, if the Oracle application uses
/oradata
, and you create the zone with the zonepath as/z_ora
, then the mount must be/z_ora/root/oradata
. The MountPoint attribute of the Mount resource must be set to this path. The Mount resource depends on the Zone resource.