Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

NetVault Plug-in for Oracle 11.3 - User Guide

Table of Contents

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

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

Troubleshooting

NetVault Backup 10.x service (netvault-pgsql) does not start on Windows Unable to add a database Backup fails Backup job hangs Restore fails Oracle RMAN output not displayed correctly in binary logs

Enabling Control File Autobackups

Control File Autobackups are required for disaster recovery with the plug-in. For more information on Control File Autobackups, see Reviewing the Control File backup types. For more information on multi-instance RAC databases, see Enabling Control File Autobackups in a RAC environment.

You can turn on the Autobackup feature by running the following commands from the RMAN command-line utility:

1

After making sure that the Recovery Catalog database is open, connect RMAN to the target database and Recovery Catalog database.

For example, issue the following commands to connect to the catalog database:

> rman TARGET / CATALOG rman/<password>@<connect_identifier for catalog>

Optionally, you can use the following commands to change the autobackup format. The default format for Control File Autobackup is “%F”.

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE

TYPE <device type> TO '<string>'

SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE <device type> TO '<string>'

The SET CONTROLFILE AUTOBACKUP FORMAT command overrides the configured autobackup format in the current session only.

If you modify the default format for the autobackups, you must specify the same format during a restore.

2

Configure the default device type to “SBT_TAPE”.

CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';

3

Enable Control File Autobackups.

CONFIGURE CONTROLFILE AUTOBACKUP ON;

4

Confirm that Control File Autobackups are enabled by reviewing the RMAN configuration settings.

Enabling Flashback Database

Flashback Database lets you rewind an Oracle® database to a previous time to correct problems caused by logical data corruptions or user errors as long as the datafiles are intact. For more information on Flashback Database, see Oracle Flashback technology.

Flashback Database uses its own logging mechanism, creating Flashback Logs and storing them in the FRA. You can only use Flashback Database if Flashback Logs are available. To take advantage of this feature, set up your database in advance to create Flashback Logs.

•

Determining whether Flashback Database is enabled

•

Setting a retention target

Determining whether Flashback Database is enabled

1

Start SQL*Plus, and connect with administrator privileges to the database.

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

2

From the SQL> prompt, enter:

select flashback_on from v$database;

The output shows the status of Flashback Database.

To enable Flashback Database, first configure an FRA. For more information, see Enabling the Flash Recovery Area in the Oracle Database Backup and Recovery User’s Guide.

Setting a retention target

After ensuring that FRA is configured, perform the following steps to set a flashback retention target. This retention target specifies how far back you can rewind a database with Flashback Database. From the target time onwards, the database regularly copies images of every changed block in the datafiles to the Flashback Logs.

1

Start SQL*Plus, and connect with administrator privileges to the database.

sqlplus SYS/<password> AS SYSDBA

2

From the SQL> prompt, shut down and mount the database:

shutdown immediate;

3

Optionally, set the DB_FLASHBACK_RETENTION_TARGET to the length of the desired flashback window in minutes.

By default, DB_FLASHBACK_RETENTION_TARGET is set to one day — 1440 minutes. To set the flashback window, issue the following commands:

alter system set db_flashback_retention_target=1440;

alter database flashback on;

4

Open the database:

alter database open;

Flashback Database is now enabled and available for use.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center