Veritas InfoScale™ 7.4.1 Virtualization Guide - AIX
- Section I. Overview
- Storage Foundation and High Availability Solutions in AIX PowerVM virtual environments
- Section II. Implementation
- Setting up Storage Foundation and High Availability Solutions in AIX PowerVM virtual environments
- Supported configurations for Virtual I/O servers (VIOS) on AIX
- Installing and configuring Storage Foundation and High Availability (SFHA) Solutions in the logical partition (LPAR)
- Installing and configuring Cluster Server for logical partition and application availability
- Supported configurations for Virtual I/O servers (VIOS) on AIX
- Setting up Storage Foundation and High Availability Solutions in AIX PowerVM virtual environments
- Section III. Use cases for AIX PowerVM virtual environments
- Application to spindle visibility
- Simplified storage management in VIOS
- Configuring Dynamic Multi-Pathing (DMP) on Virtual I/O server
- Configuring Dynamic Multi-Pathing (DMP) pseudo devices as virtual SCSI devices
- Extended attributes in VIO client for a virtual SCSI disk
- Virtual machine (logical partition) availability
- Simplified management and high availability for IBM Workload Partitions
- Implementing Storage Foundation support for WPARs
- How Cluster Server (VCS) works with Workload Patitions (WPARs)
- Configuring VCS in WPARs
- High availability and live migration
- Limitations and unsupported LPAR features
- Multi-tier business service support
- Server consolidation
- About IBM Virtual Ethernet
- Using Storage Foundation in the logical partition (LPAR) with virtual SCSI devices
- How DMP handles I/O for vSCSI devices
- Physical to virtual migration (P2V)
- Section IV. Reference
Enabling Veritas Extension for ODM file access from WPAR with VxFS
Veritas Extension for ODM can be enabled from WPAR only when Storage Foundation (SF) is installed in the global environment. For information on installing SF, see the Veritas InfoScale Installation Guide.
To enable ODM file access from WPAR with VxFS
- (Optional.) Create a system WPAR.
For example:
# mkwpar -n orawpar
For other options while creating WPARs, refer to the IBM Redbook for WPAR.
- Start the system WPAR.
- Create VxVM volumes and VxFS systems for the databases in the global environment.
For example:
/dev/vx/dsk/oradatadg/oradatavol, /dev/vx/dsk/oradatadg/oraarcvol, /dev/vx/dsk/orabindg/orabinvol
- Make sure that the mount point directories are created inside the WPAR base directory from the global environment.
For example:
# mkdir -p /wpars/orawpar/oracle/oradata # mkdir -p /wpars/orawpar/oracle/oraarc # mkdir -p /wpars/orawpar/oracle/orabin
Note:
While creating the directory, use the complete path of WPAR.
- Mount the VxVM volumes with VxFS systems on the following mount points.
For example:
# mount -V vxfs /dev/vx/dsk/oradatadg/oradatavol\ /wpars/orawpar/oracle/oradata # mount -V vxfs /dev/vx/dsk/oradatadg/oraarcvol\ /wpars/orawpar/oracle/oraarc # mount -V vxfs /dev/vx/dsk/orabindg/orabinvol\ /wpars/orawpar/oracle/orabin
- Make sure that the ODM pseudo device
/dev/odm
is mounted on the/dev/odm
directory in the global environment.For example:
# mount -V odm /dev/odm /dev/odm
- Share the
/dev/odm
directory from the global environment using namefs mount. The mount pointdev/odm
directory must be created inside the WPAR base directory from the global environment. This step enables ODM file access from WPAR.For example:
# mkdir -p /wpars/orawpar/dev/odm # mount -V namefs /dev/odm /wpars/orawpar/dev/odm # mount (only related with above commands)
Mounted Mounted over vfs date options /dev/odm /dev/odm vxodm Jun 09 17:30 smartsync /dev/vx/dsk/oradatadg/oradatavol /wpars/orawpar/oracle/oradata vxfs Jun 10 14:08 rw,delaylog,suid,ioerror=mwdisable,qio,largefiles /dev/vx/dsk/oradatadg/oraarcvol /wpars/orawpar/oracle/oraarc vxfs Jun 10 14:08 rw,delaylog,suid,ioerror=mwdisable,qio,largefiles /dev/vx/dsk/orabindg/orabinvol /wpars/orawpar/oracle/orabin vxfs Jun 10 14:08 rw,delaylog,suid,ioerror=mwdisable,qio,largefiles /dev/odm /wpars/orawpar/dev/odm namefs Jun 10 14:44 rw
Note:
While creating the directory, use the complete path of WPAR.
- Log on to WPAR.
For example:
# clogin orawpar # df -kg
Filesystem GB blocks Free %Used Iused %Iused Mounted on Global 2.00 1.94 3% 4670 2% / Global 1.00 0.99 1% 5 1% /home Global 5.00 3.81 24% 12095 2% /opt Global - - - - - /proc Global 2.00 1.99 1% 70 1% /tmp Global 5.00 2.60 49% 52955 9% /usr Global 2.00 1.98 1% 454 1% /var Global 9.00 8.42 7% 6 1% /oracle/oradata Global 9.00 8.42 7% 4 1% /oracle/oraarc Global 9.00 1.86 80% 39074 8% /oracle/orabin Global 0.00 0.00 -1% 6 100% /dev/odm
- Install and configure Oracle Database server single instance in the system WPAR.
See the IBM and Oracle documentation for the detailed information on creating system WPAR and installing Oracle Database server single instance in a system WPAR on AIX.
- Link the ODM libraries for Oracle inside the WPAR.
For example:
# ln -sf /opt/VRTSodm/lib/libodm64.so libodm11.so # ls -lta |grep -i libodm11.so
lrwxrwxrwx 1 root system 28 Jun 10 14:51 libodm11.so -> /opt/VRTSodm/lib/libodm64.so
For information on configuring Oracle single instance database, see the Veritas InfoScale Storage and Availability Management for Oracle Databases.