NetApp 7.3.2 数据存储操作手册概要

需积分: 31 40 浏览量更新于2024-07-19 收藏 2.15MB PDF 举报

"DataONTAP® 7.3.2 是NetApp提供的一个高级网络存储管理系统，该版本的操作手册详细列出了可用于管理和维护存储设备的各种命令。这份文档是NetApp Inc.官方出版物，位于495 East Java Drive, Sunnyvale, CA 94089, USA，联系电话和传真号码也提供了方便用户获取支持。手册的更新日期为2009年8月17日，适用于DataONTAP 7.3.2版本。手册的核心部分包括了一系列命令的参考，这些命令涵盖了数据管理和存储池操作，例如创建、配置、备份、恢复以及性能监控等关键功能。用户可以通过查阅这些命令来了解如何高效地使用NetApp的存储解决方案，确保数据的安全性和可靠性。此外，手册还强调了版权信息，所有内容受1994-2009年NetApp公司版权保护，未经书面许可，禁止任何形式的复制或传播，无论是打印、电子还是机械方式，包括但不限于复印件、录音、录像或存储在电子检索系统中。对于软件部分，手册指出此软件提供“原样”（AS IS）且没有任何明示或暗示的保证，包括适销性和特定用途的适合性，NetApp不对软件的任何问题或故障承担责任。这意味着用户在使用过程中需自行承担风险，并可能需要自行寻求技术支持。 NetApp 7.3.2手动页面参考文档是管理员和IT专业人士的重要参考资料，它详细介绍了如何通过命令行工具进行日常操作，同时也为用户提供了理解和处理可能出现的技术问题的基础。在使用过程中，用户应仔细阅读并遵循其中的安全指南和最佳实践，以确保数据中心的稳定运行和数据资产的完整保护。"

The Shelf S/N displays the disk shelf serial number of the shelf in which ACPP is located.

The Current State gives the state code of the ACPP. More details can be displayed using the stroage

show acp command. Possible values are:

[0x5] active

[0x1] inactive (initializing)

[0x2] inactive (not ready)

[0x3] inactive (waiting for in-band information)

[0x4] inactive (no in-band connectivity)

[0x6] not-responding (last contact at: Sat Jan 31 21:40:58 GMT 2009")

[0x7] inactive (upgrading firmware)

[0x8] not-responding (last contact at: Sat Jan 31 21:40:58 GMT 2009") -- this non-responding state

indicates that an error was encountered when attempting to connect to this module.

The Inband ID column displays the ID of the ACPP as seen by the SAS inband channel. For example,

inband ID 7c.2.A means that the ACPP is connected to adapter 7c, disk shelf 2 on slot A.

BUGS

No known bugs exist at this time.

SEE ALSO

na_storage(1),

Data ONTAP 7.3 Commands: Manual Page Reference, Volume 1 17

acpadmin

aggr

NAME

na_aggr - commands for managing aggregates, displaying aggregate status, and copying aggregates

SYNOPSIS

aggr command argument ...

DESCRIPTION

The aggr command family manages aggregates. The aggr commands can create new aggregates,

destroy existing ones, undestroy previously destroyed aggregate, manage plexes within a mirrored

aggregate, change aggregate status, apply options to an aggregate, copy one aggregate to another, and

display their status. Aggregate commands often affect the volume(s) contained within aggregates.

The aggr command family is new in Data ONTAP 7.0. The vol command family provided control over

the traditional vol_umes that fused a single user-visible file system and a single RAID-level storage

container (aggregate) into an indivisible unit, and still does. To allow for more flexible use of storage,

aggregates now also support the ability to contain multiple, independent user-level file systems named

flexible volumes.

Data ONTAP 7.0 fully supports both traditional and flexible volumes. The aggr command family is the

preferred method for managing a filer’s aggregates, including those that are embedded in traditional

volumes.

Note that most of the aggr commands apply equally to both the type of aggregate that contains flexible

volumes and the type that is tightly bound to form a traditional volume. Thus, the term aggregate is

often used here to refer to both storage classes. In those cases, it provides a shorthand for the longer and

more unwieldy phrase "aggregates and traditional volumes".

Aggregates may either be mirrored or unmirrored. A plex is a physical copy of the WAFL storage

within the aggregate. A mirrored aggregate consists of two plexes; unmirrored aggregates contain a

single plex. In order to create a mirrored aggregate, you must have a filer configuration that supports

RAID-level mirroring. When mirroring is enabled on the filer, the spare disks are divided into two disk

pools. When an aggregate is created, all of the disks in a single plex must come from the same disk

pool, and the two plexes of a mirrored aggregate must consist of disks from separate pools, as this

maximizes fault isolation. This policy can be overridden with the -f option to aggr create, aggr add

and aggr mirror, but it is not recommended.

An aggregate name can contain letters, numbers, and the underscore character(_), but the first character

must be a letter or underscore. A combined total of up to 200 aggregates (including those embedded in

traditional volumes) can be created on each filer.

A plex may be online or offline. If it is offline, it is not available for read or write access. Plexes can be

in combinations of the following states:

18 Data ONTAP 7.3 Commands: Manual Page Reference, Volume 1

aggr

normal All RAID groups in the plex are functional.

failed At least one of the RAID groups in the plex has failed.

empty The plex is part of an aggregate that is being created, and one or more of the disks targeted to the

aggregate need to be zeroed before being added to the plex.

active The plex is available for use.

inactive

The plex is not available for use.

resyncing

The plex’s contents are currently out of date and are in the process of being resynchronized with the

contents of the other plex of the aggregate (applies to mirrored aggregates only).

adding disks

Disks are being added to the plex’s RAID group(s).

out-of-date

This state only occurs in mirrored aggregates where one of the plexes has failed. The non-failed plex

will be in this state if it needed to be resynchronized at the time the other plex failed.

A plex is named using the name of the aggregate, a slash character delimiter, and the name of the plex.

The system automatically selects plex names at creation time. For example, the first plex created in

aggregate aggr0 would be aggr0/plex0.

An aggregate may be online, restricted, iron_restricted, or offline. When an aggregate is offline, no read

or write access is allowed. When an aggregate is restricted, certain operations are allowed (such as

aggregate copy, parity recomputation or RAID reconstruction) but data access is not allowed.

Aggregates that are not a part of a traditional volume can only be restricted or offlined if they do not

contain any flexible volumes. When an aggregate is iron_restricted, wafliron is running in optional

commit mode on the aggregate and data access is not allowed.

Aggregates can be in combinations of the following states:

aggr The aggregate is a modern-day aggregate; it is capable of containing zero or more flexible

volumes.

copying

The aggregate is currently the target aggregate of an active aggr copy operation.

degraded

The aggregate contains at least one degraded RAID group that is not being reconstructed.

foreign

The disks that the aggregate contains were moved to the current filer from another filer.

growing

Disks are in the process of being added to the aggregate.

Data ONTAP 7.3 Commands: Manual Page Reference, Volume 1 19

aggr

wafl inconsistent

The aggregate has been marked corrupted. Please contact Customer Support if you see an aggregate in

this state.

USAGE

The following commands are available in the aggr suite:

add mirror restrict undestroy

copy offline scrub verify

create online show_space

destroy options split

media_scrub rename status

aggr add aggrname

[ -f ]

[ -n ]

[ -g {raidgroup | new | all} ]

{ ndisks[@size]

-d disk1 [ disk2 ... ] [ -d diskn [ diskn+1 ... ] ] }

Adds disks to the aggregate named aggrname. Specify the disks in the same way as for the aggr create

command. If the aggregate is mirrored, then the -d argument must be used twice (if at all).

If the -g option is not used, the disks are added to the most recently created RAID group util it is full,

and then one or more new RAID groups are created and the remaining disks are added to new groups.

Any other existing RAID groups that are not full remain partially filled.

The -g option allows specification of a RAID group (for example, rg0) to which the indicated disks

should be added, or a method by which the disks are added to new or existing RAID groups.

If the -g option is used to specify a RAID group, that RAID group must already exist. The disks are

added to that RAID group util it is full. Any remaining disks are ignored.

If the -g option is followed by new, Data ONTAP creates one or more new RAID groups and adds the

disks to them, even if the disks would fit into an existing RAID group. Any existing RAID groups that

are not full remain partially filled. The name of the new RAID groups are selected automatically. It is

not possible to specify the names for the new RAID groups.

If the -g option is followed by all, Data ONTAP adds the specified disks to existing RAID groups first.

After all existing RAID groups are full, it creates one or more new RAID groups and adds the specified

disks to the new groups.

The -n option can be used to display the command that the system will execute, without actually

making any changes. This is useful for displaying the automatically selected disks, for example.

By default, the filer fills up one RAID group with disks before starting another RAID group. Suppose

an aggregate currently has one RAID group of 12 disks and its RAID group size is 14. If you add 5

disks to this aggregate, it will have one RAID group with 14 disks and another RAID group with 3

disks. The filer does not evenly distribute disks among RAID groups.

Data ONTAP 7.3 Commands: Manual Page Reference, Volume 1 21

aggr

剩余631页未读，继续阅读

liulove81933

粉丝: 0
资源: 1

NetApp 7.3.2 数据存储操作手册概要

NetApp存储技术白皮书资源集合

NetApp Harvest 1.4.2 安装和管理指南

NetApp存储系统维护指南

NETAPP systemmgr

netapp 调研

NETAPP资料

简单的NETAPP-NetAPP技术介绍

netapp：Netapp集合的开发区域

go-netapp:golang的netapp客户端

最新资源