Chatee ahora con Soporte
Chat con el soporte

NetVault Plug-in for Oracle 12.2 - 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.

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;
startup mount;
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.

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.

1
Start SQL*Plus, and connect with administrator privileges to the target database.
sqlplus SYS/<password>@<connect_identifier> AS SYSDBA
2
Store the Block Change Tracking file in one of the following locations:
•
To store it in the default location:
•
Set the DB_CREATE_FILE_DEST parameter for the target database.
•
Issue the following SQL statement to enable Block Change Tracking:
ALTER DATABASE ENABLE BLOCK CHANGE TRACKING;
•
To store it in a user-defined location, issue the following SQL statement:
ALTER DATABASE ENABLE BLOCK CHANGE TRACKING USING
FILE '/<path to desired destination>/rman_change_track.dat' REUSE;
The REUSE option tells Oracle to overwrite an existing file with the specified name.
 
* 
IMPORTANT: In a RAC environment, the change-tracking must be on shared storage that is accessible from all nodes in the cluster.
The following example stores the Block Change Tracking File in a file located in an ASM File System, which is used for shared storage in a RAC environment.
ALTER DATABASE ENABLE BLOCK CHANGE TRACKING USING
FILE '+DATA/o10grac/block_change_tracking.dat' REUSE;

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.

Figure 3. Single-instance non‑RAC configuration

 

 
* 
IMPORTANT: Regardless of the configured environment, separate NetVault Backup Server and Oracle Database Server vs. a single machine configured as both, the plug-in must be installed on the host on which the Oracle Database Server resides.

Installing or upgrading the plug-in

1
In the Navigation pane, click Manage Clients.
2
On the Manage Clients page, select the machine that contains the Oracle Database Server, and click Manage.
3
Click the Install Plugin button ().
4
Click Choose Plug-in File, navigate to the location of the “.npk” installation file for the plug-in, for example, on the installation CD or the directory to which the file was downloaded from the website.
Based on the OS in use, the path for this software may vary on the installation CD.
5
Select the file entitled “ora-x-x-x-x-x.npk,” where xxxxx represents the version number and platform, and click Open.
6
To begin installation, click Install Plugin.
After the plug-in is successfully installed, a message is displayed.
 
* 
IMPORTANT: When installing Plug‑in for Oracle on Windows, the plug-in copies a dynamic-link library (DLL) file, “ORASBT.DLL,” to the “…\system32” directory. If you are installing the 32-bit version of the plug-in on a 64-bit version of Windows, this directory is named “…\sysWOW64”. This DLL is the link between Oracle and the media management utilities used by NetVault Backup, and is required for the proper functioning of the plug-in. Ensure that the ORASBT.DLL exists in this directory.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación