Veritas InfoScale™ 7.2 Installation Guide - AIX
- Section I. Introduction to Veritas InfoScale
- Section II. Planning and preparation
- System requirements
- Preparing to install
- Mounting the ISO image
- Setting up ssh or rsh for inter-system communications
- Obtaining installer patches
- Disabling external network connection attempts
- Verifying the systems before installation
- Setting up the private network
- Setting up shared storage
- Synchronizing time settings on cluster nodes
- Configuring LLT interconnects to use Jumbo Frames
- Planning the installation setup for SF Oracle RAC systems
- Updating the SCSI reserve ODM attribute settings for VIOS
- Section III. Installation of Veritas InfoScale
- Installing Veritas InfoScale using the installer
- Installing Veritas InfoScale using response files
- Installing Veritas Infoscale using operating system-specific methods
- Completing the post installation tasks
- Section IV. Uninstallation of Veritas InfoScale
- Section V. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- About setting tunable parameters using the installer or a response file
- Setting tunables for an installation, configuration, or upgrade
- Setting tunables with no other installer-related operations
- Setting tunables with an un-integrated response file
- Preparing the tunables file
- Setting parameters for the tunables file
- Tunables value parameter definitions
- Appendix C. Troubleshooting installation issues
Planning volume layout
The following recommendations ensure optimal layout of VxVM/CVM volumes:
Mirror the volumes across two or more storage arrays, if using VxVM mirrors. Keep the Fast Mirror Resync regionsize equal to the database block size to reduce the copy-on-write (COW) overhead. Reducing the regionsize increases the amount of Cache Object allocations leading to performance overheads.
Distribute the I/O load uniformly on all Cache Objects when you create multiple Cache Objects.
Implement zoning on SAN switch to control access to shared storage. Be aware that physical disks may be shared by multiple servers or applications and must therefore be protected from accidental access.
Choose DMP I/O policy based on the storage network topology and the application I/O pattern.
Exploit thin provisioning for better return on investment.
For SF Oracle RAC:
Separate the Oracle recovery structures from the database files to ensure high availability when you design placement policies.
Separate redo logs and place them on the fastest storage (for example, RAID 1+ 0) for better performance.
Use "third-mirror break-off" snapshots for cloning the Oracle log volumes. Do not create Oracle log volumes on a Space-Optimized (SO) snapshot.
Create as many Cache Objects (CO) as possible when you use Space-Optimized (SO) snapshots for Oracle data volumes.