Oracle SecureBackup 10.4 备份指南

需积分: 12 140 浏览量更新于2024-07-18 收藏 2.49MB PDF 举报

"Oracle SecureBackup是Oracle公司提供的一款专业的数据保护软件，主要针对数据库和其他关键业务应用的数据备份与恢复。该软件提供了全面的备份解决方案，包括安装、配置、管理和监控等功能，确保企业的数据安全。本指南详细介绍了Oracle SecureBackup 10.4版本的使用方法，由多个专家共同编写，涵盖了从基础到高级的各种操作和策略。" 在《Oracle SecureBackup Administrator's Guide》中，你将学习到以下关键知识点： 1. **产品概述**：Oracle SecureBackup的核心功能是为Oracle数据库提供高效的备份和恢复服务，同时支持多种其他数据源，如文件系统、应用程序数据等。它采用了先进的数据压缩和加密技术，确保数据的安全性和存储效率。 2. **安装与配置**：安装过程中会涉及到服务器硬件需求、操作系统兼容性、网络设置以及许可证管理。配置部分将教你如何安装和配置备份服务器、客户端代理、存储设备以及备份策略。 3. **备份策略**：了解如何制定适合业务需求的备份策略，包括全量备份、增量备份和差异备份，以及如何设定备份计划和保留策略。同时，还会介绍如何进行数据验证以确保备份的完整性。 4. **恢复操作**：学习如何快速有效地从备份中恢复数据，包括单个文件恢复、数据库恢复和灾难恢复。这部分还会讲解如何处理恢复过程中的问题和冲突。 5. **性能优化**：通过监控和调整备份和恢复操作的性能，以提高工作效率和资源利用率。这可能涉及调整备份窗口、设置并发备份任务和优化存储配置。 6. **安全管理**：理解如何设置权限和访问控制，保护备份数据免受未经授权的访问。此外，还会讲解如何使用加密技术来增强数据安全性。 7. **故障排查与维护**：学习识别和解决Oracle SecureBackup可能出现的问题，包括日志分析、错误代码解析和系统维护。这部分内容对于确保系统的稳定运行至关重要。 8. **集成与扩展**：了解如何将Oracle SecureBackup与其他Oracle产品（如RMAN）集成，以及如何扩展备份解决方案以适应企业规模的增长。 9. **最佳实践**：书中可能包含一系列最佳实践建议，帮助你充分利用Oracle SecureBackup的功能，提升备份和恢复流程的效率和可靠性。通过深入阅读和实践《Oracle SecureBackup Administrator's Guide》，你将能够熟练掌握这款备份工具，从而为你的组织构建一个强大且可靠的数据保护体系。

Administrative Domains, Catalog Data and Configuration Files

1-2 Oracle Secure Backup Administrator's Guide

■ Duplex database backups so that the same data stream goes to multiple tape

devices

You can specify a different media family or tape device for each copy of the data.

■ Create backups that span multiple volumes

A volume is a unit of media, such as an 8mm tape.

■ Optimize tape resources with automatic tape drive sharing

■ Restore data rapidly

Oracle Secure Backup uses direct-to-block positioning and direct access restore to

avoid unnecessarily reading tape blocks to locate files. Oracle Secure Backup

maintains a record of the tape position of all backup data in its catalog for rapid

retrieval.

■ Maintain security and limit the users who are authorized to perform data

management operations

By default, Secure Sockets Layer (SSL) is used for host authentication and

communication in the administrative domain.

■ Manage media rotation from one location to another

■ Automate tape duplication with user-defined policies

Administrative Domains, Catalog Data and Configuration Files

An administrative domain is a network of hosts that you manage as a common unit to

perform backup and restore operations. Oracle Secure Backup organizes information

about the administrative domain as a hierarchy of files in the Oracle Secure Backup

home on the administrative server. The Oracle Secure Backup home is the directory in

which Oracle Secure Backup is installed.

Figure 1–1 shows the directory structure of an Oracle Secure Backup home. This

directory structure is the same for all platforms, but the default Oracle Secure Backup

home is /usr/local/oracle/backup for UNIX and Linux and C:\Program

Files\Oracle\Backup for Windows.

Figure 1–1 Directories on the Administrative Server

class dataset default device family host

history config log state

schedule summary user

admin

/usr/local/oracle/backup

Should be backed up on a

regular basis

Centralized on the administrative

server

encryption security

Oracle Secure Backup Daemons

Oracle Secure Backup Concepts 1-3

Oracle Secure Backup administrative data includes configuration data about each

domain-wide entity, such as a class, a tape device, or a media family. As shown in

Figure 1–1, the config directory contains several subdirectories, each of which

represents an object that Oracle Secure Backup maintains. In each object directory,

Oracle Secure Backup maintains files describing the characteristics of the

corresponding object.

The Oracle Secure Backup catalog contains backup-related information. The

admin/history/host directory contains subdirectories named after the hosts in the

administrative domain. Each subdirectory has a file in which the catalog data is stored.

Oracle Secure Backup supports catalog files larger than 2 GB. This support is restricted

to operating systems and file systems that themselves support files of over 2 GB.

The amount of space consumed by the catalog is different for native and NDMP hosts.

The sum of the following three components gives an estimate in bytes for expected

growth of the catalog for a native Oracle Secure Backup backup:

■ (number of new files and directories) * (43 + average file leaf name length)

■ (number of modified existing files) * (27 bytes for statistics record)

■ (number of unmodified existing files) * 0.5

The sum of the following three components gives an estimate in bytes for expected

growth of the catalog when backing up a third-party NDMP filer:

■ (number of new files and directories) * (53 + average file leaf name length)

■ (number of modified existing files) * (35 bytes for statistics record)

■ (number of unmodified existing files) * 0.5

An NDMP backup also consumes 16 bytes in the NDMP position file for every file

backed up regardless of whether it is new, modified, or unmodified.

Oracle Secure Backup automates the protection of the contents of the catalog and

configuration files. During installation, Oracle Secure Backup schedules the necessary

backup job to back up these files to tape. If the catalog data is lost, for example

because a disk fails, then you can restore the most recently backed up catalog from

tape and then restore the rest of your data.

In general, you should access configuration data and the catalog through obtool or the

Oracle Secure Backup Web tool. Avoid accessing the files containing this data directly

on the file system.

Oracle Secure Backup Daemons

Oracle Secure Backup daemons are background processes that perform Oracle Secure

Backup operations. Some daemons run continually, whereas others run only to

perform specific work and then exit when they have finished.

Note: Oracle Secure Backup makes a temporary copy of the catalog

during the processing of a backup. Planning for storage space on the

Oracle Secure Backup administrative server must take that temporary

copy into consideration.

See Also: Oracle Secure Backup Installation and Configuration Guide for

details on the contents of the files and directories in the Oracle Secure

Backup home

Oracle Secure Backup Daemons

Oracle Secure Backup Concepts 1-5

requesting host. observiced starts the schedule daemon and the Apache Web server

during initialization.

When running on a media server or client, observiced handles membership in a

administrative domain, allows for remote administration of the host, and handles

certificate operations. The identity certificate of the requesting host is used to verify

that it is permitted to invoke the operation.

On all hosts, the service daemon is usually started as part of system startup. On UNIX

and Linux, startup is usually performed through entries in /etc/init.d, whereas on

Windows systems the service is started by the Service Control Manager.

Schedule Daemon

The obscheduled daemon is the Oracle Secure Backup scheduler. The schedule

daemon runs continually on the administrative server.

The schedule daemon manages each scheduled backup, retains a list of every

available tape device in the domain, and assigns backups to tape devices as they

become available. The daemon receives job creation requests from obtool users and

from the SBT interface in response to RMAN commands.

Scheduler policies control how a backup request is scheduled.

Index Daemon

The obixd daemon manages the backup catalog for each client. The index daemon

runs intermittently on the administrative server.

The index daemon is started at the conclusion of any backup to import the index data

generated by obtar into the backup catalog. In addition, obixd is started when the

catalog must be accessed for restore or browsing operations.

Apache Web Server Daemon

The obhttpd daemon provides the Web tool for Oracle Secure Backup. This daemon

runs continually on the administrative server.

The Web server daemon is signaled to start by the observiced daemon, which itself

is normally started as part of system startup.

NDMP Daemon

The obndmpd daemon implements the NDMP tape service and provides data

communication between the media server and client. This daemon runs on both the

client and media server. It passes control of the data connection to a sub-process so it

can remain free to respond to control messages sent by obtar.

Two instances of obndmpd run during an active backup or restore operation. If the

same host is acting as both the media server and the client, then three instances of

obndmpd are running: one acting as controller, one acting as the data service, and one

acting as the mover.

Robot Daemon

The obrobotd daemon manipulates tapes in a tape library. This daemon runs

intermittently on a media server.

When an Oracle Secure Backup component such as obtar must interact with a tape

library, it asks observiced on the media server to start an instance of obrobotd.

The robot daemon then fields all requests for inventory manipulations, the movement

Oracle Secure Backup Daemons

1-6 Oracle Secure Backup Administrator's Guide

of media in the tape library, and so on. Each invocation of obrobotd manages a single

tape library. obrobotd exits when all users of a tape library have closed their

connections.

Proxy Daemon

The obproxyd daemon verifies user access for SBT backup and restore operations.

The proxy daemon runs on the host that contains the SBT library accessed during the

operations. The invocation of the proxy daemon is platform-specific.

The proxy daemon uses the operating system user identity of the process invoking the

SBT library and the local host name to determine the Oracle Secure Backup account to

use for the backup operation. If a preauthorization exists for this operating system

user and host, then the associated Oracle Secure Backup user is permitted to perform

RMAN backups and the login to Oracle Secure Backup is permitted.

Daemon Interaction in a File-System Backup

Figure 1–2 provides a simplified graphical illustration of the relationships among the

daemons on an administrative server, media server, and client.

Figure 1–2 Daemons in an Administrative Domain

The media server in Figure 1–2 shows an obtar instance, but obtar is not itself a

daemon. It is the underlying

Oracle Secure Backup engine that manipulates the data

and tape services during a backup or restore operation. When you issue commands in

obtool or the

Oracle Secure Backup Web tool, Oracle Secure Backup translates

them internally to obtar commands.

Imagine that observiced daemons run on all hosts, the observiced daemon on the

administrative server has invoked the obscheduled and obhttpd daemons, and a

client file-system backup job has been created and scheduled to run. The Oracle Secure

Backup daemons interact with obtar as follows:

1. On the administrative server, obscheduled sends a request to observiced to

run the backup job.

2. observiced on the administrative server sends a request to obrobotd on the

media server to mount the volume required for the backup job.

3. observiced on the administrative server sends a request to observiced on the

media server to invoke obtar.

Administrative Server

Media Server

observiced

obhttp

observiced

obtar

obixdobscheduled

observiced

obrobotdobndmpd

Client

obndmpd

observiced

剩余291页未读，继续阅读

800x600

粉丝: 1
资源: 10

Oracle SecureBackup 10.4 备份指南

oracle osb

oracl 安全备份系统的安装和配置

OSB管理指导手册

osb 安装示意手册

osb开发指导资料

osb操作手册

osb开发配置手册(oepe)v2.docx

oracle osb examaple

OSB-sklad

orace osb资料

最新资源