AIX PowerHA SystemMirror 6.1：企业版存储高可用与灾备解决方案

版权申诉

125 浏览量更新于2024-06-21 收藏 1.68MB PDF 举报

PowerHA SystemMirror Version 6.1 for AIX Enterprise Edition 是一款针对AIX企业版设计的高级可用性和灾难恢复解决方案。该版本专注于基于存储的高可用性和灾难恢复功能，旨在确保系统的稳定运行和数据安全性。它通过镜像技术，将关键业务数据复制到多个物理或逻辑位置，以便在发生故障时能快速切换，减少停机时间和数据丢失的风险。在使用前，请务必阅读第153页的"注意事项"部分，了解相关的限制、安全指南和兼容性信息。此版本适用于PowerHA SystemMirror 6.1 for AIX Enterprise Edition，以及后续所有版本和修改，除非有特别声明，否则一直有效。版权归属于IBM公司，1998年和2011年。文档内容涵盖多个主题，包括： 1. **关于本文档**：介绍了文档的目的、结构和读者群，旨在帮助用户正确理解和操作PowerHA SystemMirror 6.1。 2. **高亮功能**：可能涉及到新版中的新增特性、改进的性能指标或者优化的用户体验。 3. **AIX中的大小写敏感性**：强调在AIX操作系统环境下的命名规则，以避免因不恰当的操作导致的问题。 4. **ISO 9000**：可能提及产品符合的质量管理体系标准，表明其在质量控制上的承诺。 5. **相关信息**：可能包括兼容的操作系统版本、硬件需求、许可证信息等，帮助用户确定其环境是否适合此版本。 6. **PowerHA SystemMirror Enterprise Edition**：详细介绍了该产品的核心功能，即基于存储的高可用性和灾难恢复方案，这部分内容通常会深入解释如何配置、管理和维护这些特性。 7. **新功能亮点**：这部分重点阐述了6.1版本相对于前作在存储高可用性和灾难恢复方面的重大改进，如更快的故障转移速度、更强的数据一致性保障等。在探索PowerHA SystemMirror Version 6.1 for AIX Enterprise Edition时，用户应确保充分理解其工作原理、设置流程，并根据文档提供的指南进行操作，以充分利用这一强大的灾备工具。同时，定期更新和维护也是确保系统持续可用的关键步骤。

When an application is running on an active production site:

v Updates to the application data are made to the disks associated with the active production site.

v Data is mirrored using PPRC to the backup disks.

If the node or the disks at the production site become unavailable:

v The application moves to a server at the backup site.

v The application continues operation using the mirrored copy of the data.

When the initial production site becomes active again, resource group and site management policies

determine whether or not the application moves back to the previous site:

v The direction of mirroring may be reversed.

v The application may be stopped and restarted on another node.

v Manual intervention may be required to bring the application back to a nominal functioning state.

Related information:

Planning guide

PowerHA SystemMirror Enterprise Edition for Metro Mirror general planning

These topics describe planning tasks required for all the types of PowerHA SystemMirror Enterprise

Edition Metro Mirror support.

Related concepts:

“General PowerHA SystemMirror planning worksheets” on page 82

You should print and use the paper planning worksheets from the PDF version of this guide instead of

the HTML version. The PDF version has each worksheet aligned to start at the top of a page. You may

need more than one copy of some of the worksheets.

PowerHA SystemMirror Enterprise Edition for Metro Mirror management types:

PowerHA SystemMirror Enterprise Edition for Metro Mirror supports both synchronous and

extended-distance PPRC mirrored volumes. The method used to manage PPRC depends on the hardware

configuration available.

Using the table below, you can decide what type of PPRC configuration you will need to manage your

cluster.

Mirror type Hardware Type PPRC is managed by

How PowerHA SystemMirror manages PPRC

pairs

Synchronous ESS 800, etc. Copy Services Server (CSS,

on storage controller)

Directly manages the fallover and

resynchronization of the PPRC pairs by issuing

commands directly to the ESS systems. In this

book, this is referred to as Direct management.

In general, it refers to PPRC between ESS

storage systems.

Synchronous ESS (800) or DS (8000,

6000) or intermix of any of

these

DSCLI management, via

ESSNI Server on either

storage controller or

Hardware Management

Console (HMC)

Relies on the ESSNI server to manage PPRC

pairs. Directly manages the fallover and

resynchronization of the PPRC pairs by issuing

commands directly to the storage systems. In

this book, this is referred to as DSCLI

management.

Synchronous vDisks as provided by

SAN Volume Controller.

(Hardware as supported

by SVC services)

SVC management of PPRC

services on SVC-specific

hardware

Relies on the Copy Services Server in order to

manage PPRC function. Directly manages the

fallover and resynchronization of the PPRC

pairs by issuing commands directly to the

Copy Services Server. In this book, this is

referred to as PPRC SVC management.

8 PowerHA SystemMirror Version 6.1 for AIX Enterprise Edition: Storage-based high availability and disaster recovery

Coexistence of two solutions

PowerHA SystemMirror Enterprise Edition for Metro Mirror solutions can coexist on the same PowerHA

SystemMirror cluster only if the PPRC pairs are managed by one of the PPRC solutions at a time. Please

refer to the latest support information for which PPRC solutions can successfully coexist on a single

PowerHA SystemMirror cluster.

Planning overview:

Once you have decided what type of PowerHA SystemMirror Enterprise Edition for Metro Mirror

implementation to set up, you can begin planning the configuration.

At this stage, you should be familiar with the planning tasks for base PowerHA SystemMirror. For

information about planning PowerHA SystemMirror clusters, see the Planning Guide.

The following planning is required for all PowerHA SystemMirror Enterprise Edition for Metro Mirror

implementations:

v Identify sites for PowerHA SystemMirror Enterprise Edition for Metro Mirror.

v Identify the resource groups needed to manage the PPRC replicated resources (optional at this point,

can be done at a later stage).

v Identify storage systems to be used in the configuration.

v Plan for connections to the storage units.

v Plan the PowerHA SystemMirror Enterprise Edition for Metro Mirror configuration.

Identify the type of PowerHA SystemMirror Enterprise Edition for Metro Mirror support to be used.

Related concepts:

“General PowerHA SystemMirror planning worksheets” on page 82

You should print and use the paper planning worksheets from the PDF version of this guide instead of

the HTML version. The PDF version has each worksheet aligned to start at the top of a page. You may

need more than one copy of some of the worksheets.

Related information:

Planning guide

Planning PowerHA SystemMirror sites:

Within a resource group, the nodes at one site may handle the PPRC replicated resource differently than

the nodes at the other site, especially in cases where the states of the volumes (suspended or full duplex)

are different at the two sites.

PowerHA SystemMirror Enterprise Edition for Metro Mirror requires two PowerHA SystemMirror sites

for use within a resource group to control which volume in a PPRC pair a node can access. Although

nodes at both sites can access a volume group, access is permitted to only one volume in a PPRC pair at

a time - the source volume. This prevents nodes at different sites from accessing the same volume group

at the same time. Typically, a number of volumes are mirrored through PPRC from one site to the other.

Completing the PowerHA SystemMirror Enterprise Edition for Metro Mirror site worksheet:

An PowerHA SystemMirror Enterprise Edition for Metro Mirror configuration requires two sites. Each

site contains one ESS and the nodes attached to it.

Complete a PowerHA SystemMirror Site Worksheet for each site.

To define an PowerHA SystemMirror Enterprise Edition for Metro Mirror site, enter the following

information on the worksheet:

PowerHA SystemMirror Enterprise Edition: Storage based High Availability and Disaster Recovery 9

1. Record the Site Name. Use no more than 20 alphanumeric characters and underscores. Do not begin

the name with a number.

2. Record the names of the Site Nodes. The nodes must have the same names as those you define to the

PowerHA SystemMirror cluster. A site can have1-7nodes. A node can belong to only one site.

3. Record the Site Backup Communication Method as None.

Related reference:

“PowerHA SystemMirror Site Worksheet” on page 82

Use the PowerHA SystemMirror Site Worksheet to record PowerHA SystemMirror sites to support PPRC

replicated resources.

Planning PowerHA SystemMirror Enterprise Edition for Metro Mirror resource groups:

In addition to basic resource group planning, you need to plan for resource group attribute such as sites

and PPRC replicated resources.

Plan your resource groups using the guidelines in Planning resource groups in the Planning Guide.

Note: An PowerHA SystemMirror resource group can contain multiple volume groups, file systems,

PPRC replicated resources, applications, etc.

When configuring a resource group to use a PPRC replicated resource, the resource group includes nodes

in both cluster sites. For the resource group to manage nodes and resources across sites, you assign one

of the following inter-site management policies:

v Prefer Primary Site . In a two-site configuration, replicated resources at startup are on the site with the

highest priority, fall over to the other site, and then fall back to the site with the highest priority.

v Online on Either Site . Replicated resources are on either site at startup, fall over to the other site and

remain on that site after fallover. This selection simplifies resource group takeover rules, which is

helpful if you have a number of resource groups.

Note: Each PPRC pair will be included in a resource group whose home node is located at the site that is

primary for that PPRC pair.

If you want to set up a mutual recovery configuration for ESS volumes, you configure one resource

group in which one site is the active site and another resource group in which the other site is the active

site. For an example of a mutual recovery configuration, see Sample configuration for Direct

management.

Resource group limitations

In PowerHA SystemMirror Enterprise Edition for Metro Mirror configurations, all volume groups in a

resource group must contain only PPRC-protected disks.

If PowerHA SystemMirror Enterprise Edition for Metro Mirror is not being used, all volume groups in a

resource group must contain only non-PPRC-protected disks.

Each PPRC pair will be included in a resource group whose home node is located at the site that is

primary for that PPRC pair.

10 PowerHA SystemMirror Version 6.1 for AIX Enterprise Edition: Storage-based high availability and disaster recovery

Related reference:

“Sample configuration for Direct management” on page 21

You can set up a mutual recovery configuration in which each site acts as a production site with the other

site acting as an associated backup site.

Related information:

Planning resource groups

Completing the PPRC resource group worksheet:

Complete a Resource Groups for PPRC Replicated Resources Worksheet for each resource group that

contains PPRC replicated resources.

To identify information required to include PPRC replicated resources in a resource group, enter the

following information on the PPRC Replicated Resources Worksheet:

1. Record the Resource Group Name for the resource group that will contain the PPRC replicated

resource. The name can contain up to 32 characters and underscores. Do not begin the name with a

number.

2. Record the startup, fallover, and fallback policies for the resource group.

Resource groups that include PPRC replicated resources do not support the startup policy Online on

All Available Nodes.

3. Record the Intersite Management Policy: Prefer Primary Site or Online Either Site.

Prefer Primary Site is recommended for use with PPRC.

4. Record the names of the Nodes in the resource group, listing the nodes in the prioritized order in

which they will appear in the nodelist for the resource group.

5. Plan and record the name of each PPRC replicated resource that will be managed, (and if you will be

using Direct management PPRC, specify whether it is primary or secondary.) You will use this name

for the resources and assigned each as primary or secondary on the PPRC-Mirrored Volumes

Worksheet appropriate for the PowerHA SystemMirror Enterprise Edition PPRC configuration you are

working on.

6. Record the names of any related volume groups (and file systems).

Installing PowerHA SystemMirror Enterprise Edition for Metro Mirror

These topics describe how to install base PowerHA SystemMirror Enterprise Edition filesets. Details for

installing filesets and prerequisites for specific types of PPRC support are contained in subsequent

sections.

Note: At runtime, make sure you have at least 9 MB of free space in the /tmp directory. PPRC commands

use this directory.

PowerHA SystemMirror Enterprise Edition for Metro Mirror is installed in addition to the PowerHA

SystemMirror base filesets. For more information on installing base PowerHA SystemMirror, refer to the

Installation Guide.

In order to install PowerHA SystemMirror Enterprise Edition for Metro Mirror, you must install the

cluster.xd.license fileset in addition to the base PowerHA SystemMirror cluster.license fileset.

Depending on what type of PowerHA SystemMirror Enterprise Edition for Metro Mirror configuration

you are setting up, go to the following sections to continue planning and move forward into installing

and configuring your cluster:

PowerHA SystemMirror Enterprise Edition: Storage based High Availability and Disaster Recovery 11

Management Type Chapter Reference

Direct management (PowerHA SystemMirror Enterprise Edition for Metro Mirror with Direct management)

DSCLI (PowerHA SystemMirror Enterprise Edition for Metro Mirror with DSCLI management)

DSCLI PPRC

SVC PPRC (PowerHA SystemMirror Enterprise Edition for Metro Mirror with SVC management)

Related information:

Installation guide

Installation prerequisites for PowerHA SystemMirror Enterprise Edition Metro Mirror:

Before installing PowerHA SystemMirror Enterprise Edition Metro Mirror, be sure to have the necessary

base PowerHA SystemMirror filesets installed.

PowerHA SystemMirror Enterprise Edition requires base PowerHA SystemMirror. Base PowerHA

SystemMirror can be installed at the same time as PowerHA SystemMirror Enterprise Edition. Installation

requisites will ensure the proper version(s) of base PowerHA SystemMirror filesets are installed before

installing PowerHA SystemMirror Enterprise Edition.

At least the following base PowerHA SystemMirror filesets should be installed on all cluster nodes:

Note: Fileset versions must reflect the version of PowerHA SystemMirror you are installing.

In addition, refer to the following table for a list of filesets to install for each type of PPRC management

support:

PPRC Management Type Filesets to install

Direct management cluster.es.pprc.cmds

cluster.es.pprc.rte

cluster.msg.en_US.pprc

(and/or other appropriate language message sets)

DSCLI cluster.es.pprc.cmds

cluster.es.pprc.rte

cluster.es.spprc.cmds

cluster.es.spprc.rte

cluster.msg.en_US.pprc

(and/or other appropriate language message sets)

SAN Volume Controller (SVC) cluster.es.svcpprc.cmds

cluster.es.svcpprc.rte

cluster.msg.en_US.svcpprc

(and/or other appropriate language message sets)

Since each type of PPRC management has different prerequisites, information on installing the particular

filesets for specific support types (for example, cluster.es.pprc filesets) is deferred to the section specific to

that PPRC management type.

Note: For the latest information about PowerHA SystemMirror Enterprise Edition software, see the

Release Notes in the /usr/es/sbin/cluster/release_notes_xd file.

12 PowerHA SystemMirror Version 6.1 for AIX Enterprise Edition: Storage-based high availability and disaster recovery

剩余171页未读，继续阅读

weixin_40191861_zj

粉丝: 86
资源: 1万+

AIX PowerHA SystemMirror 6.1：企业版存储高可用与灾备解决方案

PowerHA SystemMirror 6.1 Planning, Implementation and Administration

IBM Power AIX 6.1 Ha 7.1配置方法-R.pdf

概念PowerHA SystemMirror HA7.1

管理powerHA systemMirror HA v7.1

IBM+PowerHA+6[1].1+SystemMirror+for+AIX中文产品介绍

AIX powerHA 6.1 详细配置手册

powerHA for AIX cookbook

原创]AIX6.1配置PowerHA5.5完整手册.doc

PowerHA 6.1 对操作系统以及oracle10g .11g的支持

AIX6.1升级，HA5.5升级6.1

最新资源