Planning for availability with AIX

Learn how to minimize downtime and maximize availability on your AIX® server.

Before you begin your planning tasks, complete this checklist:

Before you begin
__ Go to IBM® System p® and AIX Information Center Web site at http://publib.boulder.ibm.com/infocenter/pseriesLink outside information center to review information about System p and AIX.
__ Read the AIX Release Notes®.
__ Identify your disaster recovery plan.
__ Identify your backup and recovery strategy.
__ Identify the cost per hour of a system outage to both your business and your users.
AIX availability planning tasks
__ Establish a backup policy

Determine a strategy for backing up the systems and files that are needed for your organization. For more information about backing up your systems, see Backup files and storage media and Establishing a backup policy.

__ Establish a logical volume policy

Determine a strategy for logical volume use that is oriented toward availability and performance. This policy may include write-verify and mirroring, which can enhance availability, but degrade performance. Establish a policy that is best suited to your needs. For more information about creating a logical volume policy, see Developing a Logical Volume Strategy.

__ Establish a volume group policy

Determine a strategy for volume groups to protect against disk failure. This should include mirroring, which can also aid performance. For more information about creating a volume group policy or using commands to mirror your volume group, such as the alt_disk_install command, seeDeveloping a Volume Group Strategy.

__ Understand the different file system types

Know the difference between CIFS, GPFS, JFS, JFS2, NFS, UDFS, and other file system types and how they can increase your AIX availability. For more information about clusters in AIX, see File Systems.

__ Plan for High Availability Cluster Multi-Processor (HACMP™) technology

Depending on the size and scope of your enterprise, consider using an HACMP solution to ensure continuous data and application availability. Current HACMP solutions enable long-distance site mirroring, which is why they are called HACMP/XD (eXtreme distance). HACMP/XD High Availability Geographic Cluster (HAGEO) for AIX 5L™ is a high-end solution for business-critical applications and data. HACMP/XD Remote Copy for IBM Enterprise Storage Server® is appropriate for less critical operational applications and data. To determine which solution is right for your business and to plan accordingly, see the Planning considerations for geographically dispersed clusters using HACMP/XD HAGEO technology Link to a PDF white paper. Once you have decided on an HACMP solution, see the High Availability Cluster Multi-Processing for AIX Link outside information center Web site for resources that enable you to add more detail to your plan.

__ Plan for High Performance Switch (HPS) clusters

You should install High Performance Switches (HPSes) for your high availability clusters to function at their peak performance. To plan for HPSes on pSeries® servers, see eServer™ Cluster 1600: pSeries High Performance Switch Planning, Installation, and Service Link to a PDF. To plan for HPSes on eServer p5 servers, see eServer Cluster 1600: High Performance Switch Planning, Installation, and Service for IBM eServer p5 servers Link to a PDF.

When you have completed these tasks, you should have a plan for AIX availability that identifies these elements:

After you finish
__ Implement your established backup policy.
__ Record a complete availability strategy for a single server or multiple server environment.
__ Record a complete strategy for backing up your server.
__ Record a complete strategy for server recovery.
__ Record a complete strategy for data protection that includes mirroring, concurrent maintenance, and Redundant Array of Independent Disks (RAID). Include detailed configuration and placement information for disk subsystem components.
__ Record a complete and validated plan for HACMP cluster configurations, if applicable.
__ Ensure that the hardware requirements for your cluster configuration have been met, if applicable.