NetBackup架构详解：存储与SAN概念
下载需积分: 0 | PDF格式 | 2.53MB |
更新于2024-08-02
| 201 浏览量 | 举报
"本文档是Veritas NetBackup架构的概述，涵盖了NetBackup存储以及存储区域网络（SAN）的概念。文档详细介绍了NetBackup的硬件组成部分、数据传输方式、备份存储设备及配置管理等关键方面，旨在提供对NetBackup系统全面的理解。"
在NetBackup架构中，了解其核心组件和工作原理对于有效地实现数据保护至关重要。以下是对各部分的详细说明：
1.0-INTRODUCTION: 引言部分简要介绍NetBackup架构的基本概念，同时给出了术语表，以便读者理解后续的专业术语。
1.1-GLOSSARYOFTERMS: 提供了NetBackup相关的专业词汇解释，帮助读者理解文档中的专业概念。
1.2-BANDWIDTHOVERVIEW: 讨论了带宽在NetBackup环境中的角色，如何影响备份和恢复的效率，以及如何优化网络资源。
1.3-NETBACKUPOVERVIEW: 描述了NetBackup的主要功能，包括其在数据保护中的定位，以及如何满足恢复点目标(RPO)、恢复时间目标(RTO)和服务水平协议(SLA)。
1.4-DATAPROTECTIONINANUTSHELL: 简化了数据保护流程，概述了NetBackup如何进行备份、保留策略以及快速恢复。
1.5-RPO/RTO/SLADEVELOPMENTANDRECOVERY: 详细阐述了如何制定和实现RPO、RTO和SLA，以确保业务连续性和数据安全性。
2.0-NETBACKUPHARDWARE: 阐述了NetBackup架构中硬件的需求和配置，包括主服务器、媒体服务器、全功能媒体服务器和SAN媒体服务器的CPU、内存和磁盘空间要求，以及实例配置。
2.1-MASTERSERVER: 主服务器是NetBackup的核心，负责策略管理和作业调度。它需要足够的CPU和RAM，以及用于存储目录和日志的磁盘空间。
2.2-THEMEDIASERVER: 媒体服务器负责实际的数据备份和恢复，其硬件需求与主服务器类似，但可能需要更高的I/O性能。
2.3-FULLMEDIASERVER: 全功能媒体服务器可以处理更多的备份负载，通过负载均衡提高性能。
2.4-SANMEDIASERVER: 针对SAN环境的媒体服务器，优化了对光纤通道设备的访问。
2.5-LANCLIENT/SANCLIENT: LAN客户端和SAN客户端描述了如何通过局域网或存储区域网络连接到备份系统。
3.0-MOVINGDATA:LANANDSAN: 解释了数据如何通过LAN和SAN进行传输，以及如何通过扩展这些网络来适应不断增长的备份需求。
4.0-BACKUPSTORAGEDEVICES: 提到了多种备份存储设备，如磁带驱动器、磁带库和硬盘作为备份目标。特别提到了去重技术在提高存储效率和虚拟磁带库(VTL)的应用。
5.0-CONFIGURATIONANDMANAGEMENT: 包括NetBackup策略配置、存储单元的定义以及如何管理备份和恢复操作。
5.1-NETBACKUPPOLICYCONFIGURATION: 详细介绍了如何根据业务需求定制备份策略，以确保数据安全。
5.2-STORAGEUNITS: 存储单元是NetBackup中的逻辑存储容器，用于组织和管理备份数据。
5.3-REC: (这部分内容不完整，可能指的是记录或报告功能，但具体细节无法提供)。
NetBackup架构是一个复杂而高效的数据保护解决方案，涵盖从硬件配置到策略管理的多个层面，旨在确保企业的数据安全并满足其业务连续性需求。通过理解和掌握这些知识点，IT专业人员可以更有效地设计、部署和维护NetBackup环境。
5
White Paper: Netbackup Architecture Overview
· Storage Unit—A virtual representation for physical storage where NetBackup will send data.
· Recovery Point Objective or RPO—Determines how much data loss is acceptable. For example, if backups occur only
once every 24 hours, then the maximum data loss could be as many as 24 hours. In order to meet a specific
RPO, careful planning and testing are required. Short RPOs require backup and recovery scenarios that typically will
not involve traditional backup from disk to tape.
· Recovery Time Objective or RTO—Determines how long the environment has until it needs to be back online. In many
instances this could be less than an hour, in which case traditional backup to disk/tape is not the right choice for
protection. Similar to the RPO, proper planning and extensive testing are needed to document steps for recovery to
shorten the amount of time recovery takes.
· Service Level Agreement or SLA—The SLA of an environment is usually based on input from those whose data is being
protected and determines how data should be backed up, the RPO/RTO associated with the data, how long it is
stored (retention), etc.
1.2 Bandwidth Overview
The term “bandwidth” is used extensively when developing a data protection solution. In general, it refers to the ability to
move data from point A to point B, and how fast that data is capable of moving—based on the components that are in use. In
the broader sense, bandwidth is also used for the “human” component. For example, only very small environments should have a
single data protection administrator. While it is difficult to pinpoint exact FTE requirements, recommendations will be made in this
document based on other customers’ experiences and overall size of the solution.
As an environment is developed, various components within the solution will have specific bandwidth numbers they are capable
of; for example, speeds. Based on testing and customer experiences, we recommend that any bandwidth numbers follow the “70%
rule,” which dictates that any speed claimed by the hardware vendor be reduced to 70% of the top-rated speed. For instance,
Gigabit Ethernet (GbE) speed is theoretically 125 MB/sec; however, customer experience and testing have shown that a practical
speed for performing bandwidth calculations is closer to 87 MB/sec (125 * 70% = 87.5 MB/sec). If you use 87 MB/sec as the
maximum throughput speed of a GbE connection as your baseline when developing the architecture it makes the overall numbers
more realistic. Any extra speed that can be achieved just makes the backups faster, but should not be expected.
The only exception to the 70% rule is tape drives. They can be driven to 100% of “native” rated speed with the right hardware and
exceed native speeds based on the compressibility of the data being backed up.
1.3 NetBackup Overview
NetBackup is considered a “three-tiered architecture” in that it has a master server that provides configuration services, policy
creation, scheduling, reporting, logging, etc. It is the “traffic cop” of the backup solution and allocates resources to the media
servers, the second tier.
The master server processes are typically CPU-intensive based on such things as job scheduling, running binaries, metadata
gathering (catalog), etc. The disk used for the master server should be “fast” disk based on the need to write the catalog data;
however, it does not need to be the fastest and most expensive disk in the data center. It should be configured for fast writes and
should have the ability to be expanded (size increased) on the fly without bringing the server down. The master server also needs a
disk area to write any log files. This will be discussed in more detail later.
剩余23页未读，继续阅读
相关推荐
chiounan
- 粉丝: 0
- 资源: 10
我的内容管理
展开
最新资源
- KeilC51使用详解V1.0
- AJAX开发简略(含续一).pdf
- uml建模讲义 OO方法、RUP与UML建模
- G[1].729A声码器的VC++面向对象封装实现
- JavaScript DOM 编程艺术英文pdf
- 适合新手学习的td测试工具的使用
- JdonFramework 应用开发文档
- Thinking in Java 中文版
- 恒温箱温度显示的控制
- MyEclipse开发基于MVC 模式的WEB应用实例讲解
- 基于ADS40的线阵摄影测量及数据处理
- ORACLE PL/SQL入门
- Perl 语言入门（第四版）
- Beginning HTML with CSS and XHTML - Modern Guide and Reference(2007)
- JSP 2.0 技术手册-电子工业出版社
- Erlang +中文编程
