Please enter search query.
Search <book_title>...
Veritas InfoScale™ 7.3.1 Virtualization Guide - Solaris
Last Published:
2018-08-22
Product(s):
InfoScale & Storage Foundation (7.3.1)
Platform: 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
Exporting VxVM volumes to a non-global zone
A volume device node can be exported for use in non-global zone using the zonecfg command. The following procedure makes a volume vol1
available in the non-global zone myzone
.
Caution:
Exporting raw volumes to non-global zones has implicit security risks. It is possible for the zone administrator to create malformed file systems that could later panic the system when a mount is attempted. Directly writing to raw volumes, exported to non-global zones, and using utilities such as dd can lead to data corruption in certain scenarios.
To export VxVM volumes to a non-global zone
- Create a volume
vol1
in the global zone:global# ls -l /dev/vx/rdsk/rootdg/vol1 crw------- 1 root root 301, 102000 Jun 3 12:54 /dev/vx/rdsk/rootdg/vol1crw------- 1 root sys 301, 10200 0 Jun 3 12:54 /devices/pseudo/vxio@0:rootdg,vol1,102000,raw
- Add the volume device
vol1
to the non-global zonemyzone
:global# zonecfg -z myzone zonecfg:myzone> add device zonecfg:myzone:device> set match=/dev/vx/rdsk/mydg/vol1 zonecfg:myzone:device> end zonecfg:myzone> commit
- Ensure that the devices will be seen in the non-global zone:
global# zoneadm -z myzone halt global# zoneadm -z myzone boot
- Verify that
/myzone/dev/vx
contains the raw volume node and that the non-global zone can perform I/O to the raw volume node.The exported device can now be used for performing I/O or for creating file systems.