サポートと今すぐチャット
サポートとのチャット

NetVault Plug-in for Oracle 7.1 - User Guide

Introducing Dell™ NetVault™ Backup Plug‑in for Oracle® Defining a backup strategy Installing and removing the plug-in Configuring the plug-in Backing up data Using the Oracle Flashback Database Restoring data
Restoring and recovering data – an overview Performing User Managed restores Using advanced User Managed restore procedures Performing RMAN restores Using RMAN types of recovery in a non-RAC environment Using advanced procedures with RMAN restores
Maintaining the Recovery Catalog Using the RMAN CLI Using the Plug-in with Oracle RAC Using the Plug-inin a failover cluster environment Using the plug-in with Oracle Data Guard Troubleshooting Glossary About Dell

Reviewing the available backup methods

The backup-and-restore strategies available with the User Managed method are discussed in the Oracle Database Backup and Recovery Advanced User’s Guide and the Oracle Database Backup and Recovery User’s Guide for 11g.

Recovery Manager (RMAN) backup method

For a feature comparison between User Managed and RMAN backups, refer to Feature Comparison of Backup Methods in the Oracle Database Backup and Recovery Basics guide. The same guide also discusses the backup and restore strategies available with the RMAN method.

Reviewing the supported Oracle file types

Datafiles – Datafiles are a physical file on disk that was created by Oracle Database and contain data structures such as tables and indexes. A datafile can belong to only one database, and is located either in an OS file system or in an ASM disk group.
Control File – Control Files are binary files that record the physical structure of the database. The file includes: the database name, names and locations of associated datafiles and online redo log files, timestamps for database creation, current log sequence number, and checkpoint information. Protecting the Control File is critical to many recovery scenarios.
Parameter File – The client-side initialization parameter file (PFILE) or the server-side initialization parameter file (SPFILE) for the Oracle database.
Archived Redo Logs – The Oracle database copies full online redo log groups to one or more archive locations on disk, where they are collectively called the archived redo log. Individual files are referred to as archived redo log files. After a redo log file is archived, it can be backed up to other locations on disk or on tape, for long-term storage and use in future recovery operations. Without archived redo logs, your database backup and recovery options are severely limited. Your database must be taken offline before it can be backed up, and if you must restore your database from backup, the database contents are only available as of the time of the backup. Reconstructing the state of the database to a point in time is not possible without archive logs.
External Configuration Files – The Oracle database depends on other files for operation such as network configuration files (“tnsnames.ora” and “listener.ora”) and password files. These files need to be protected for corruption or disaster recovery purposes.

Defining an RMAN backup strategy

Control File – RMAN can conduct all necessary backup and recovery operations using just the Control File to store the RMAN repository information. This increases the importance of protecting the Control File as part of your backup strategy.
Enable Oracle’s Control File Autobackup feature. This causes RMAN to back up the Control File automatically, and also lets RMAN restore the Control File Autobackup without access to a repository.
Keep a record of your Oracle Database ID (DBID), which may be required to recover the database when the Control File is lost.
Recovery Catalog – You can also use an external Oracle database to store the RMAN repository. This external database is known as the Recovery Catalog. While the Control File has finite space for records of backup activities, a Recovery Catalog can store a longer history. The added complexity of administering a Recovery Catalog database can be offset by the convenience of having the extended backup history available if you have to do a recovery that goes back further than the history in the Control File.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択