InfoScale™ 9.0 Virtualization Guide - Solaris
- Section I. Overview of InfoScale solutions in Solaris virtualization environments
- Section II. Zones
- InfoScale Enterprise Solutions support for Solaris Native Zones
- About VCS support for zones
- 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 InfoScale SFRAC component support for Oracle RAC in a zone environment
- Known issues with supporting a InfoScale SFRAC component in a zone environment
- Software limitations of InfoScale support of non-global zones
- InfoScale Enterprise Solutions support for Solaris Native Zones
- Section III. Oracle VM Server for SPARC
- InfoScale Enterprise Solutions support for Oracle VM Server for SPARC
- Oracle VM Server for SPARC deployment models
- Benefits of deploying Arctera InfoScale Enterprise solutions in Oracle VM server for SPARC
- Features
- Split InfoScale stack model
- Guest-based InfoScale stack model
- Layered InfoScale stack model
- System requirements
- Installing InfoScale 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
- SFRAC support for Oracle VM Server for SPARC environments
- Support for live migration in FSS environments
- Using SmartIO in the virtualized environment
- InfoScale Enterprise Solutions support for Oracle VM Server for SPARC
- Section IV. Reference
Cluster FileSystem mounts
The component in InfoScale Enterprise provides support for the same file system to be made available from multiple nodes that have been grouped together as a cluster. VxFS supports the sharing or delegation of cluster-mounted file systems in the non-global zone.
Note:
A non-global zone root can not be created on VxFS or CFS for Solaris 11. The only supported file system for non-global zone root on Solaris 11 is zfs.
See Mounting VxFS as lofs into a non-global zone.
The requirements to support InfoScale Enterprise in non-global zones are similar to those for InfoScale Enterprise support in global zones. Some key points are as follows:
Both lofs and direct mount are supported; Arctera recommends direct mount.
The device must be visible and shared on all nodes.
The zone configuration must be the same on all nodes. The zone name can be different.
Mounting a VxFS file system as a cluster file system from the non-global zone is not supported.
Arctera File System supports the InfoScale Enterprise in a non-global zone.
To direct mount a VxFS file system as a cluster file system in a non-global zone
- Log in to the zone and make the mount point:
global# zlogin newzone newzone# mkdir dirmnt newzone# exit
- Mount the file system from the global zone.
Cluster File System:
global# mount -F vxfs -o cluster /dev/vx/dsk/dg/vol1 \ /zonedir/zone1/root/dirmnt
Note:
It is not possible to make InfoScale Enterprise cluster between different non-global zones of the same node.
Note:
Cluster file system should not be used as a part of non-global zone configuration. It should be used through VCS as a part of main.cf
configuration or it should be mounted manually from global zone. If using LOFS to mount the cluster file system within the non global zone, then do not use any cluster file system related options in the zone configuration since the cluster file system will already be mounted in the global zone.