Chat now with support
Chat with Support

NetVault Plug-in for Oracle 12.3 - User Guide

Introducing Quest® 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-in in a failover cluster environment Using the plug-in with Oracle Data Guard Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs) Troubleshooting

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.

Start SQL*Plus, and connect with administrator privileges to the database.
sqlplus SYS/<password> AS SYSDBA
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:

Enabling Block Change Tracking

When this feature is enabled, RMAN uses a change-tracking file to record changed blocks in each datafile. This feature eliminates the need to scan every block in the datafile for an Incremental Backup, thus improving performance of the Incremental Backup jobs.

IMPORTANT: Because it introduces minimal performance overhead on the database during normal operations, Block Change Tracking is disabled by default on Oracle 10g and later. However, the benefits of avoiding full datafile scans during Incremental Backups are considerable, especially if only a small percentage of data blocks is changed between backups. For more information on Incremental Backups and change tracking, see Improving Incremental Backup Performance Change Tracking in the Oracle Database Backup and Recovery Basics guide.

You can enable change tracking when the database is either open or mounted.

Start SQL*Plus, and connect with administrator privileges to the target database.
sqlplus SYS/<password>@<connect_identifier> AS SYSDBA
To store it in the default location:
Set the DB_CREATE_FILE_DEST parameter for the target database.
To store it in a user-defined location, issue the following SQL statement:
FILE '/<path to desired destination>/rman_change_track.dat' REUSE;
The REUSE option tells Oracle to overwrite an existing file with the specified name.

Using DR Series or QoreStor as the storagedevice for Oracle Database 12.x or later on Linux or UNIX

If you are running Oracle Database 12.x or later on Linux or UNIX, backups generated using NetVault Backup might fail if the device you select for Target Storage is a software-defined Quest DR Series system or QoreStor storage device. To avoid this issue, run the storage device sc_manager command with the disable option. Use the root account to complete the following steps on the applicable operating system.

Run the sc_manager command with the disable option.

Recommended configuration for a single-instance non-RAC environment

While you can set up a single machine as both the NetVault Backup Server and the Oracle Database Server, that is, all software installation and configuration requirements are performed on a single machine, Quest recommends that these two entities exist on separate machines. For more information on installing Plug‑in for Oracle in a RAC environment, see Installation prerequisites.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating