Chatee ahora con Soporte

Obtener ayuda en vivo
Completar registro

Iniciar sesión

Solicitar precios

Comuníquese con Ventas

NetVault Plug-in for Oracle 13.0 - User Guide

Navegación de contenido

Introducing Quest® NetVault® Plug-in for Oracle

Quest NetVault 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 Policy Management

Installing and removing the plug-in

NetVault 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 Using DR Series or QoreStor as the storagedevice for Oracle Database 12.x or later on Linux or UNIX

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 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 '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 media name

Performing CLI-based restores Using the CROSSCHECK and CATALOG commands with backups

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

Creating the RMAN repository

As discussed in Choosing the location for the RMAN repository, for an RMAN backup strategy you must first choose a location for the RMAN repository. By default, this repository is maintained in the Control File. However, for larger or more mission-critical databases, create a Recovery Catalog database that can store a much longer history than the Control File.

Creating a Recovery Catalog is a three-step process: configure the database that will contain the Recovery Catalog, create the Recovery Catalog owner, and then create the Recovery Catalog itself.

Configuring the Recovery Catalog database

When you use a Recovery Catalog, RMAN requires that you maintain a Recovery Catalog schema. The Recovery Catalog is stored in the default tablespace of the schema. SYS cannot be the owner of the Recovery Catalog. Decide which database you want to use to install the Recovery Catalog schema. Quest recommends that you create a separate database for the Recovery Catalog and run the catalog database in ARCHIVELOG mode.

Next, allocate space to be used by the catalog schema. The size of the Recovery Catalog schema depends on the number of databases managed by the catalog. The schema also grows as the number of archived redo log files and backups for each database increases. For more information on sizing the Recovery Catalog schema, see Planning the Size of the Recovery Catalog Schema in the Oracle Database Backup and Recovery Advanced User’s Guide.

Creating the Recovery Catalog owner

After choosing the Recovery Catalog database and creating the necessary space, perform the following steps to create the owner of the Recovery Catalog and grant this user the necessary privileges:

1

Start SQL*Plus, and connect with administrator privileges to the database that will contain the Recovery Catalog.

sqlplus SYS/<password>@<connect_identifier> AS SYSDBA

2

Create a user and schema for the Recovery Catalog.

For example, enter:

CREATE USER rman IDENTIFIED BY <password>

TEMPORARY TABLESPACE temp

DEFAULT TABLESPACE tools

QUOTA UNLIMITED ON tools;

3

Grant the RECOVERY_CATALOG_OWNER role to the schema owner.

This role provides the user with all privileges required to maintain and query the Recovery Catalog.

GRANT RECOVERY_CATALOG_OWNER TO rman;

4

Grant the CONNECT role to the rman user.

GRANT CONNECT TO rman;

Creating the Recovery Catalog

After creating the catalog owner, create the catalog tables with the RMAN CREATE CATALOG command. This command creates the catalog in the default tablespace of the catalog owner.

1

Connect to the database that will contain the catalog as the catalog owner.

> rman CONNECT CATALOG rman/<password>@<connect_identifier_for_catalog>

2

Run the CREATE CATALOG command to create the catalog.

The creation of the catalog can take several minutes.

If the catalog tablespace is this user’s default tablespace, you can run this command:

CREATE CATALOG;

You can also specify the tablespace name for the catalog in the CREATE CATALOG command. For example:

CREATE CATALOG TABLESPACE <tablespace_name>;

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación

© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center