NetApp NCDA 认证备考指南：DataONTAP 8.07 模式

需积分: 50 118 浏览量更新于2024-07-25 2 收藏 1.66MB PDF 举报

"NetApp NCDA (Network Appliance Certified Data Administrator) 认证是针对NetApp Data ONTAP操作系统的一款入门级认证，旨在验证个人在管理、监控和维护使用Data ONTAP 8.0 7-Mode存储系统方面的技能和知识。这个认证主要通过NS0-154考试进行评估，该考试包含了对NetApp存储解决方案的基本理解、数据管理、性能监控和故障排查等内容。提供的学习资料是官方的学习指南，适用于培训环境，以帮助考生准备认证考试。" NetApp NCDA认证的学习资料——NS0-154认证学习指南，课程编号STRSW-ILT-ANCDA-D87M，是针对Data ONTAP 8.0 7-Mode的详细教材，版本号2.0，更新日期为2010年5月25日。这份指南不仅包含理论知识，还可能包含一些实践活动，这些活动在非生产环境中有助于培训，但并不适用于生产环境，因为它们可能导致系统停机或其他严重后果。 Data ONTAP是NetApp公司的核心存储操作系统，7-Mode是其早期的一个版本，主要关注的是传统的单控制器配置。学习Data ONTAP 8.0 7-Mode的NCDA认证，考生将学习如何配置和管理NetApp存储阵列，包括： 1. **基础操作**：了解NetApp存储术语，如LUN（逻辑单元号）、VLAN（虚拟局域网）、VServer（虚拟服务器）和FlexVol（灵活卷）等，并掌握基本的系统设置和管理。 2. **数据管理**：学习如何创建、扩展和删除数据存储空间，以及如何进行数据迁移和备份策略的设定。 3. **性能监控**：理解如何使用NetApp的监控工具来跟踪系统性能，包括I/O速率、存储利用率和CPU利用率等关键指标。 4. **故障排查**：学习识别和解决常见的硬件、软件和网络问题，以确保系统的稳定运行。 5. **高级特性**：探索如SnapMirror（快照镜像）和SnapVault（快照归档）等高级数据保护功能，以及如何利用Clustering进行多控制器集群的管理。 6. **安全性和权限管理**：学习如何设置用户访问控制，管理权限和角色，以确保数据的安全性。 7. **最佳实践**：了解NetApp推荐的操作流程和配置建议，以提高效率并减少潜在问题。学习资料特别提醒，所有信息仅供培训使用，未经授权不得用于复制。如果需要技术参考材料，应参考NetApp的官方产品文档，这些文档可在NetApp的产品信息网站http://now.netapp.com上获取。 NetApp NCDA认证的学习是一个深入理解和熟练掌握Data ONTAP 8.0 7-Mode操作的关键步骤，对于希望在存储领域发展的人来说，这是一个必要的起点。通过这个认证，个人将具备在企业环境中部署、管理和维护NetApp存储解决方案的能力。

11 Data ONTAP 8.0 7-Mode NCDA NSO-154 Certification Study Guide

The license for Operations Manager enables Performance Advisor, Protection Manager and Provisioning

Manager are separately licensed products.

NOTE: Management of the FAS storage infrastructure can be promoted to the host operating system

(Windows or UNIX) by the SnapDrive® tool and to the application layer by the SnapManager® tool. Both

tools are optional purchases and require licenses.

The various SAN and network-attached (NAS) protocols differ in many technical details: SAN provides

block-level access, and NAS provides file-level access. Additionally, some protocols use FC connections, and

others use Ethernet. However, both SAN and NAS provide remote systems (hosts) with access to centralized,

shared storage.

Perhaps the simplest way to define the difference between SAN and NAS is by describing how the file system

is managed and how access is shared. For a SAN device, the controller provides block-level access to the

hosts. The hosts then create and manage their own local file system (for example, ext3), and the local file

system is typically not shared with other hosts. On the other hand, NAS storage uses the file system on the

controller—the WAFL® (Write Anywhere File Layout) system, and the controller provides shared file-level

access to multiple remote systems (hosts).

Both FC and iSCSI SANs support multipathing. With multipathing, there are redundant physical paths (two

or more) between a host and the controller. Refer to Figure 4 for an example.

Multipathing ensures storage availability, even if a SAN hardware failure occurs. NetApp supports various

multipathing options for both FC and iSCSI.

 FC and iSCSI multipathing

– With the host platform‘s native multipath I/O (MDIO) driver

– With the NetApp device-specific module (DSM) for Windows

– With the Veritas Dynamic Mulitpath (VxDMP)software

 iSCSI only multipathing, with iSCSI‘s inherent multiple connections per second (MCS)

You choose the multipath solution that best meets the needs of your environment.

The NetApp on the Web (NOW)® online support and services site is available to all customers and business

partners. You should become familiar with the NOW site, as it is a primary resource for questions regarding

the configuration or performance of a FAS storage controller. Some of the resources available on the NOW

site include:

 A knowledgebase (searchable) of NetApp product information

 Online manuals, for all NetApp products

 Software downloads, including updates and evaluation versions

 Return Merchandise Authorization (RMA), used to request replacement of failed hardware

 Bugs online, used to review all known software bugs

 Release Comparison, used to identify the version of Data ONTAP in which a particular bug was fixed

64-BIT AGGREGATES

Before Data ONTAP 8.0, aggregates and, consequently, the volumes within the aggregates were based upon a

32-bit architecture. This architecture effectually limits the size of an aggregate to 16 TB.

As storage demands increase, the 16-TB limitation causes three major issues. First, as the size of each disk

drive increases, the number of drives per aggregate must decrease. For example, in Data ONTAP 7.3, an

aggregate can accommodate only nineteen 1-TB data drives. Second, performance is directly affected. As the

number of drives decreases, the read and write performance that can be realized from an aggregate also

decreases.

12 Data ONTAP 8.0 7-Mode NCDA NSO-154 Certification Study Guide

The third issue with the 16-TB limitation is that aggregate management becomes more complex and less

efficient. For example, a FAS6070 system with 500 TB of storage requires a minimum of 32 aggregates. Such

a requirement greatly increases the complexity of managing large storage arrays.

NetApp is pleased to announce that its Data ONTAP 8.07-Mode operating system supports 64-bit aggregates.

This architecture overcomes the disadvantages of the 16-TB limitation.

NOTE: In Data ONTAP 8.0 Cluster-Mode, 64-bit aggregates are not available.

Data ONTAP 8.0 7-Mode supports aggregates of up to 100 TB—running on top-of-line hardware with greater

aggregate sizes available in the future.

See Figure 5 for information about platforms and maximum aggregate sizes.

* Supported only through a Policy Variation Request (PVR)

FIGURE 5: 64-BIT AGGREGATES—MAXIMUM AGGREGATE SIZE PER PLATFORM

In Data ONTAP 8.0, NetApp added the -B switch to the aggr create command. This switch accepts 32 or

64 as a valid parameter.

aggr create <aggr-name> [-B {32 | 64}]…

The 32 parameter designates a 32-bit aggregate architecture, and the 64 parameter designates a 64-bit

aggregate architecture. The 32 parameter is the default.

To create a 64-bit aggregate, you must explicitly use the 64 parameter. For example, if a storage administrator

enters the following: aggr create sales aggr -B 64 24, a 64-bit aggregate is created. The new

aggregate is named ―sales aggr,‖ and 24 spare disks, chosen by Data ONTAP, are added the new 64-bit

aggregate.

NOTE: The command succeeds only if the specified number of spare disks exists. As in earlier Data ONTAP

releases, the storage administrator can manually choose the disks to be added by specifying a -d switch and

the disk names.

When a storage administrator upgrades a storage system from Data ONTAP 7.3 or earlier to Data ONTAP

8.0, all existing aggregates are designated as 32-bit aggregates. In Data ONTAP 8.0, you cannot directly

convert a 32-bit aggregate to a 64-bit aggregate. Similarly, volumes within a 32-bit aggregate cannot be

moved directly to a 64-bit aggregate. If you want to take advantage of the 64-bit aggregate feature, you must

migrate data from a 32-bit aggregate to a 64-bit aggregate. To migrate data, you may use the ndmpcopy

command.

13 Data ONTAP 8.0 7-Mode NCDA NSO-154 Certification Study Guide

PERFORMANCE

You can use several commands on the FAS storage controller to collect system performance data.

Performance data can consist of a broad summary of system performance or of details about specific

performance parameters.

Some common commands for collecting performance data are:

 sysstat

– The default output includes CIFS, NFS, HTTP; CPU, nonvolatile RAM (NVRAM), network interface

card (NIC), and disk performance values. The –b parameter adds block-level (that is, FC and iSCSI)

performance to the output.

– Example: The sysstat –s 5 command runs every five seconds and prints a summary on

termination. The default interval is 15 seconds.

– Example: The sysstat –u command displays extended utilization data, including consistency

point (CP) time and type. The command can be used to identify when a controller is busy. Outputs

such as cp_from_log_full (‗F‘) and cp_from_cp (‗B‘) indicate that the controller is busy.

 statit

– This command can output performance data on various object types, specific instances of object type,

and other performance counters.

– The command displays many performance items, including per-disk performance data.

 stats

– This advanced mode command can provide low-level performance data.

– Example: The stats show cifs:cifs:cifs_latency command displays the average

latency value for the CIFS protocol.

– Performance counters can also be accessed via the Windows PerfMon GUI (but only if CIFS is

enabled).

Some commands for collecting statistics about the performance of the Ethernet network interface and other

data are:

 netstat: The netstat -i command identifies the network interfaces, the number of in and out

network packets, errors, and collision values

 ifstat: The ifstat –a command displays a low level view of interface performance data, including

transmitted (Tx) and received (Rx) bytes per second

If you cannot resolve a performance problem by using the systat, stats, status, netstat, or

ifstat commands, then you may need to download the perfstat command from the NOW online

support and services site.

Characteristics of the perfstat command:

 Captures all needed performance information

 Captures information from hosts and filers

 Captures all information simultaneously and thus enables cross correlation

 Operates on all host platforms and all filer platforms

 Records all captured data in one plain-text output file

DATA ONTAP SECURITY

The security of the FAS controller, the security of the Data ONTAP operating system, and the security of the

data stored on the controller are different topics. This section deals only with Data ONTAP security.

剩余61页未读，继续阅读

bagua158

粉丝: 0
资源: 2

NetApp NCDA 认证备考指南：DataONTAP 8.07 模式

Netapp 存储培训

ASAP 最新题库.zip

NETAPP资料

NetApp存储基础学习汇总(第一部分)

NetApp存储系统操作手册

NetApp NCDA认证题库

AI企联系统 Ai企业级系统开心版 uniapp适配 Web+H5+微信小程序+抖音小程序+双端APP

2000d.doc

通过SpringCloud实现微服务：Eureka+Ribbon+Feign+Zuul.zip

基于CNN-BiLSTM-Adaboost的自行车租赁数量预测研究附Matlab代码.rar

最新资源