지금 지원 담당자와 채팅
지원 담당자와 채팅

NetVault Plug-in for Oracle 7.1 - User Guide

Introducing Dell™ 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-inin a failover cluster environment Using the plug-in with Oracle Data Guard Troubleshooting Glossary About Dell

Registering the target database

The first step in using a Recovery Catalog with a target database is registering the database in the Recovery Catalog.
To register a target database
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 command to connect to the catalog database.
> rman TARGET / CATALOG rman/<password>@<connect_identifier_for_catalog>
2
If the target database is not mounted, mount or open it:
STARTUP MOUNT;
3
Register the target database in the connected Recovery Catalog:
REGISTER DATABASE;
RMAN creates rows in the catalog tables to contain information about the target database, and then copies all pertinent data about the target database from the Control File into the catalog, synchronizing the Catalog with the Control File.
4
Verify that the registration was successful.
REPORT SCHEMA
Registering multiple databases in a Recovery Catalog
You can register multiple target databases in a single Recovery Catalog, if they do not have duplicate DBIDs. RMAN uses the DBID to distinguish one database from another.
In a Data Guard environment, only the primary database is registered in the Recovery Catalog.

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 the Autobackup feature on by executing 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>'
– or –
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE <device type> TO '<string>'
Note that 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.
SHOW ALL;

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, you must set up your database in advance to create Flashback Logs.
To determine 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 will show the current status of Flashback Database.
To enable Flashback Database, you must first configure an FRA. For more information, refer to Enabling the Flash Recovery Area in the Oracle Database Backup and Recovery User’s Guide.
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 eliminates the need to scan every block in the datafile for an Incremental Backup, thereby 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 are changed between backups. For more information on Incremental Backups and change tracking, refer to 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.
To alter the change tracking setting
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 located 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;
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택