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
VCS initiated migration of service groups that have LDom resource configured to monitor Oracle VM for SPARC guest domains
This section describes how to initiate migration of service groups by Cluster Server (VCS).
VCS contains the "migrate" operation for initiating service group migration. The LDom agent contains the "migrate" entry point to initiate migration of guest domains.
For details of supported service group configurations with VCS initiated migration refer to the Cluster Server Administrator's Guide on Solaris.
To initiate migration of service groups by VCS
- The guest domain must meet domain migration requirements for memory, CPU, firmware version, OVM version, etc.
For details on domain migration requirements, refer to Oracle VM server for SPARC documentation.
- Migrate a service group, enter:
# hagrp -migrate service_group -to sys_name
- The UserName and Password attributes of the LDom agent are mandatory attributes for supporting VCS initiated migration of service groups. A sample configuration for migration of a service group:
group sg1 ( SystemList = { sys1 = 0, sys2 = 1 } ) LDom ldmres1 ( LDomName = ldm1 CfgFile = "/etc/ldm1.xml" NumCPU = 16 Memory = 8G Password = aabbccddee UserName = user1 )
Refer to Oracle documentation for steps to authorize non-root users to issue commands to the logical domain manager.
- The guest domain migration command uses physical system name, if VCS node name is different from physical system name, you must configure PhysicalServer attribute (system level) of VCS with the physical system name on each VCS node. On each VCS node, enter:
# haconf -makerw # hasys -modify node_name PhysicalServer node_name
Oracle VM server for SPARC does not support migration of more than one guest domain on a system at a time either as source of migration or as target for migration. Attempting VCS initiated migration with more than one service group between two systems at a time is not supported.
Configuring more than one LDom resource in a service group is also not supported for VCS initiated migration.