Chatee ahora con Soporte

Obtener ayuda en vivo
Completar registro

Iniciar sesión

Solicitar precios

Comuníquese con Ventas

NetVault Plug-in for Oracle 12.2 - User Guide

Navegación de contenido

Introducing Quest® NetVault® Backup Plug-in for Oracle

Quest NetVault Backup Plug-in for Oracle: at a glance Key benefits Feature summary Target audience Recommended additional reading

Defining a backup strategy

Defining a strategy: overview Reviewing the available backup methods

User Managed backup method Recovery Manager (RMAN) backup method

Reviewing the supported Oracle file types Defining an RMAN backup strategy

Choosing the location for the RMAN repository Reviewing the RMAN Tablespace and Datafile backup types Reviewing the Control File backup types Reviewing the other backup types

Flash Recovery Area (FRA) backups

Developing a Recovery Catalog backup strategy Examples of backup sequences Defining a Backup Destination strategy

Oracle Flashback technology NetVault Backup Policy Management

Installing and removing the plug-in

NetVault Backup Server and Client software Database in ARCHIVELOG mode

Prerequisites for RMAN backups

Adding the Oracle user to the local administrator group on Windows Determining the Oracle SID and Home directory in a non-RAC environment

Windows Linux and UNIX

Creating the RMAN repository

Configuring the Recovery Catalog database Creating the Recovery Catalog owner Creating the Recovery Catalog

Registering the target database Enabling Control File Autobackups Enabling Flashback Database

Determining whether Flashback Database is enabled Setting a retention target

Enabling Block Change Tracking

Recommended configuration for a single-instance non-RAC environment Installing or upgrading the plug-in Removing the plug-in

Configuring the plug-in

Configuring a default Target Set for RMAN backups Configuring default settings Adding a database

Editing database information Setting the database password Removing a saved password Removing a database Viewing database details Using RMAN Post-Backup Scripts

Creating an RMAN Post-Backup Script Updating a Post-Backup Script Removing a Post-Backup Script

Language support

Backing up data

Performing User Managed backups

Selecting data for a backup Selecting backup options Finalizing and submitting the job

Performing RMAN backups

Selecting data for a backup Setting backup options Finalizing and submitting the job

Using Plug-in for FileSystem to back up Oracle ACFS

Using the Oracle Flashback Database

Flashback Database: an overview

Viewing Flashback Database status Flashback Database options Flashback Database restrictions Restoring data with the plug-in and Flashback Database

Restoring and recovering data: an overview

Understanding User Managed recovery

Determining which datafiles require recovery Recovering datafiles and archive logs Restoring Control Files

Understanding RMAN recovery

How RMAN backups are selected for use in recovery operations Choosing between Incremental Backups and Redo Logs Choosing the restore source Datafile media recovery Block Media Recovery

Performing User Managed restores

Preparing the database for recovery Selecting data for a restore Finalizing and submitting the job Recovering the database Opening the database for use

Using advanced User Managed restore procedures

Renaming or relocating Control File, Datafile, or individual Archived Log files Renaming or relocating the Archive Log Directory

Performing RMAN restores

Selecting data for a restore Setting restore options

Viewing the contents of backup pieces Setting the Pre-Restore and general Restore Options Setting recovery options Setting Block Media Recovery options Setting Post Recovery options Setting Destination Details Setting the Recovery Catalog details Setting the Clone Database options Setting Generate RMAN Script options

Finalizing and submitting the job

Using RMAN types of recovery in a non-RAC environment

Restoring the Control File from an Autobackup Recovering individual datafiles and tablespaces to the same server Recovering Whole Database to same server Performing disaster recovery with RMAN

Using the Stepwise Disaster Recovery process Disaster recovery to same server Retrieving a Control File manually

Using advanced procedures with RMAN restores

Renaming or relocating files Duplicating a database in a non-RAC environment

Restoring a Duplicate Database to the same server Restoring a Duplicate Database to an alternate server with the same directory structure Restoring a Duplicate Database to an alternate server with an alternate directory structure

Performing table-level recovery

Uses of table-level recovery Table-level requirements and limitations Configuring channels for table-level recovery Performing table-level recovery from the RMAN CLI Performing table-level recovery from the NetVault Backup WebUI

Maintaining the Recovery Catalog

Resynchronizing the Recovery Catalog

Using CROSSCHECK to update the RMAN repository

Using the RMAN CLI

CLI-based RMAN backups and restores: an overview Prerequisites for CLI-based backups and restores

Verifying that the proper RMAN executable is in use (Linux only) Ensuring an "SBT_TAPE" channel is established Running the NetVault Backup 'nvpluginaccess' utility

Performing CLI-based backups

Example of a basic CLI backup More parameters: the "format" clause More parameters: the "send" and "PARMS" clauses Querying the NetVault Backup media name

Performing CLI-based restores

Using the Plug-in with Oracle RAC

Oracle RACs: an overview Recommended additional reading Defining a deployment strategy

RMAN backup process for RAC environment RMAN restore process for RAC environment

Licensing Installing the plug-in in a RAC environment

RAC configuration requirements Installation prerequisites

Enabling Control File Autobackups in a RAC environment

Installing or upgrading the plug-in

Configuring the plug-in

Configuring default attributes Determining the local Oracle SID and Home directory in a RAC environment Adding a database to the plug-in

Backing up data

Performing backups after node failure

Restoring data in a RAC environment

Recovering a Whole Database to the same RAC environment Restoring SPFILE in a RAC environment Restoring Control Files in a RAC environment Performing disaster recovery in a RAC environment

Prerequisites Performing the disaster recovery

Performing restores after node failure Duplicating a database in a RAC environment

Prerequisites Post-restore procedure

Using the Plug-in in a failover cluster environment

Oracle Server Fail Safe Failover Clustering: an overview Installing the plug-in

Installation prerequisites Installing or upgrading the software

Creating a Virtual Client

Licensing the plug-in Configuring the plug-in and adding a database Backing up data Restoring data

Using the plug-in with Oracle Data Guard

Oracle Data Guard: an overview Defining a deployment strategy

Back up from Primary only Back up from both Primary and Standby Back up from Standby only

Single-instance to single-instance Data Guard deployment Multi-instance RAC to single-instance Data Guard deployment Multi-instance RAC to multi-instance RAC Data Guard deployment

Installing the plug-in in a Data Guard environment

Installation prerequisites

Optional RMAN configuration settings

Installing or upgrading the plug-in

Backing up data

Creating a User Defined Backup Tag Performing manual backups of Control File and SPFILE

Configuring a restore to an alternate server in a Data Guard environment Restoring data to an alternate server in a Data Guard environment Recovering Whole Database to Primary Database Server

Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs)

Oracle PDBs: an overview Enabling connection to a PDB Querying CDB, PDB, and non-CDB databases Restrictions for backing up and restoring a PDB Backing up data Restoring data

Troubleshooting

Unable to add a database Backup fails Backup job hangs Restore fails Oracle RMAN output is not displayed correctly in binary logs

Restore fails

Table 6. Troubleshooting restore failures

•

ORA-19511: Error received from media manager, error text: SBT error=7011, errno=1, sbtopen: system error

•

ORA-19511: Error received from media manager layer, error text: SBT error= 7063, errno = 0, sbtread: i/o error

•

ORA-27007: failed to open file

•

ORA-27012: Read from file failed

Ensure that NetVault Backup Server and Do Restore from NetVault Backup Server settings are defined as detailed in Configuring default settings.

RMAN-06054: media recovery requesting unknown log: thread <n> seq 40 scn <n>

This error might occur while performing a Clone Database operation. This error results because the old Control File has no record of the new archive log. Running the RMAN command ALTER DATABASE OPEN RESETLOGS brings the database online.

Warning (.. ..) Data Plug-in (… …) Failed with exit code 5

This warning appears if Block Media Recovery is selected with Oracle 11g databases. In spite of the “failed” message, the recovery completes with success and full access to the Oracle recovered data is granted.

The code 5 is a warning issued by Oracle 11g to let you know that recovery is necessary. Because the plug-in already includes the RMAN recovery command while performing Block Media Recovery, this message can be ignored.

Oracle RMAN output is not displayed correctly in binary logs

When running RMAN based jobs, the plug-in redirects the output from Oracle RMAN to the NetVault Backup binary logs. In this manner, the output from Oracle RMAN can be viewed in the NetVault Backup binary logs. However, the output for Oracle RMAN is either incorrectly displayed or not displayed in the NetVault Backup binary logs.

Possible causes

Depending on the NLS_LANG setting, the output might not be displayed correctly or is displayed incorrectly because the encoding of the output generated by Oracle RMAN cannot be displayed by the NetVault Backup binary logs.

To resolve this issue, change the NLS_LANG setting to a UTF-8 character set.

For example, if you have set NLS_LANG to JAPANESE_JAPAN.JA16SJISTILDE, and the NetVault Backup binary logs fail to display the output correctly, change the NLS_LANG setting to JAPANESE_JAPAN.UTF-8. For more information, see the NLS_LANG option in Adding a database.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación

© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center