Plug‑in for Oracle offers two backup methods: User Managed and RMAN. The plug-in supports implementing a pure User Managed or a pure RMAN-based backup strategy; that is, your backup strategy should include either User Managed backups or RMAN backups, not a combination of the two.
Oracle® continues to support traditional User Managed backup and recovery. With this method, the files that make up the database are backed up and restored using a combination of host operating system (OS) commands and SQL*Plus backup- and recovery-related capabilities.
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.
Oracle® provides RMAN, which automatically integrates with sessions running on the Oracle Database Server to perform a range of backup and recovery activities. RMAN also reduces the administration work associated with your backup strategy by maintaining an extensive record of metadata about backups, archive logs, and its own activities, known as the RMAN repository. In restore operations, RMAN uses this information to eliminate the need for you to identify backup files for use in restores.
For a feature comparison between User Managed and RMAN backups, see 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.
The following figure illustrates the RMAN-based backup process:
2 |
Plug‑in for Oracle converts the job definition into the corresponding RMAN backup commands. |
3 |
RMAN runs backup commands that read data from the Oracle® database datafiles. |
The following figure illustrates the RMAN-based restore and recovery process:
2 |
Plug‑in for Oracle converts the job definition into corresponding RMAN restore and recovery commands. |
4 |
RMAN uses the Oracle® Media Management API to read the backup from the backup device managed by the NetVault Backup Server. |
Plug‑in for Oracle lets you back up the following types of Oracle® database files, which are critical to the successful operation of the Oracle Instance:
• |
Datafiles: A Datafile is 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 called 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. 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 specific point 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. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center