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
Veritas Extension for Oracle Disk Manager
The Veritas Extension for Oracle Disk Manager (ODM) is specifically designed for file management and disk I/O throughput. The features of ODM are best suited for databases that reside in a Veritas File System (VxFS). ODM allows users to improve database throughput for I/O intensive workloads with special I/O optimization.
The Veritas extension for ODM is supported in non-global zones. To run Oracle 11g Release 2 on a non-global zone and use ODM, the Oracle software version must be 11.4.
See the Veritas InfoScale Support matrix for IBM DB2 for more information on supported versions.
Care must be taken when installing and removing packages when working with the VRTSodm package, for more information refer to the following:
This section describes how to enable ODM file access from non-global zones with VxFS:
On Solaris 11:
If there is no existing zone.
If there is existing zone.
On Solaris 11: To enable ODM file access from non-global zones with VxFS, if there is no existing zone
- Install SF in the global zone.
See the Storage Foundation Configuration and Upgrade Guide.
- Set publisher for installation after going in the
pkgs
folder of the same installer:global# pkg set-publisher -P -g VRTSpkgs.p5p Veritas
- Create a zone with the following configuration:
zonecfg:myzone> create create: Using system default template 'SYSdefault' zonecfg:myzone> set zonepath=/export/home/myzone zonecfg:myzone> set fs-allowed=default,vxfs,odm zonecfg:myzone> add fs zonecfg:myzone:fs> set dir=/etc/vx/licenses/lic zonecfg:myzone:fs> set special=/etc/vx/licenses/lic zonecfg:myzone:fs> set type=lofs zonecfg:myzone:fs> end zonecfg:myzone:fs> remove anet linkname=net0 zonecfg:myzone> add device zonecfg:myzone:device> set match=/dev/vxportal zonecfg:myzone:device> end zonecfg:myzone> add device zonecfg:myzone:device> set match=/dev/fdd zonecfg:myzone:device> end zonecfg:myzone> add device zonecfg:myzone:device> set match=/dev/odm zonecfg:myzone:device> end zonecfg:myzone> verify zonecfg:myzone> commit
- Install the zone:
global# zoneadm -z myzone install
- Boot the zone.
global# zoneadm -z myzone boot
- Configure the zone:
global# zlogin -C myzone
- Install VRTSvxfs, VRTSodm, and VRTSvlic in the zone:
myzone# pkg install --accept VRTSvxfs VRTSodm VRTSvlic
- Enable the
vxodm
service inside the zone:myzone# svcadm enable vxodm
- Execute the mount -p | grep odm in the local zone and confirm the output looks similar to the following:
/dev/odm - /dev/odm odm - no nodevices,smartsync,zone=myzone, sharezone=5
- Unset the publisher after coming inside the global zone:
global# pkg unset-publisher Veritas
On Solaris 11: To enable ODM file access from non-global zones with VxFS, if there is existing zone
- Check whether, SF is installed in the global zone or not. If not, Install SF in the global zone.
See the Storage Foundation Configuration and Upgrade Guide.
- 2. Set publisher for installation after going in the
pkgs
folder of the same installer with which SF was installed in the global zone.global# pkg set-publisher -P -g VRTSpkgs.p5p Veritas
- Check whether the zone is in running or in installed state. If it is running then shut it down:
global# zoneadm -z myzone shutdown
- Set
fs-allowed
to bedefault,vxfs,odm
:zonecfg -z myzone zonecfg:myzone> set fs-allowed=default,vxfs,odm zonecfg:myzone> verify zonecfg:myzone> commit
- Add license directory as
fs
in zone configuration file:zonecfg -z myzone zonecfg:myzone> add fs zonecfg:myzone:fs> set dir=/etc/vx/licenses/lic zonecfg:myzone:fs> set special=/etc/vx/licenses/lic zonecfg:myzone:fs> set type=lofs zonecfg:myzone:fs> end zonecfg:myzone> verify zonecfg:myzone> commit
- Add three devices
vxportal
,fdd
, andodm
in the zone configuration file:zonecfg -z myzone zonecfg:myzone> add device zonecfg:myzone:device> set match=/dev/vxportal zonecfg:myzone:device> end zonecfg:myzone> add device zonecfg:myzone:device> set match=/dev/fdd zonecfg:myzone:device> end zonecfg:myzone> add device zonecfg:myzone:device> set match=/dev/odm zonecfg:myzone:device> end zonecfg:myzone> verify zonecfg:myzone> commit
- Boot the zone:
global# zoneadm -z myzone boot
- Install VRTSvxfs, VRTSodm, and VRTSvlic in the zone:
myzone# pkg install --accept VRTSvxfs VRTSodm VRTSvlic
- Enable the
vxodm
service inside the zone:myzone# svcadm enable vxodm
- Execute the
mount - p | grep odm
in the local zone and confirm the output looking similar to the following:/dev/odm - /dev/odm odm - no nodevices,smartsync,zone=myzone,sharezone=5
- 11. Unset the publisher after coming inside the global zone:
global# pkg unset-publisher Veritas