Chat now with support
Chat with Support

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

Installing and removing the plug-in

•
Prerequisites
•
Prerequisites for RMAN backups
•
Recommended configuration for a single-instance non-RAC environment
•
Installing the plug-in
•
Removing the plug-in

Prerequisites

Before installing the plug-in, make sure that the following prerequisites are met on the machine designated as the Oracle Database Server:
NetVault Backup Server/Client software
At a minimum, the Client version of NetVault Backup must be installed on the machine where the plug-in will be installed. In a single-instance non-RAC environment, the plug-in will be installed on the server where the Oracle database resides. In a multi-instance RAC environment, the plug-in will be installed on one of the nodes that hosts one of the instances for the RAC-enabled database.
Database in ARCHIVELOG mode
Make sure that the database is running in ARCHIVELOG mode. For instructions on enabling the archiving of filled groups of redo log files, refer to the Oracle Administrator’s Guide.
To verify that the database is properly set in this mode
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:
ARCHIVE LOG LIST
The output will show the current mode. If the Automatic archival property displays an Enabled status, the database is properly configured. The following example shows that the Database log mode is set to Archive Mode.
SQL> archive log list
Database log mode                 Archive Mode
Automatic archival                Enabled
Archive destination               e:\oraclelogs
Oldest online log sequence        11
Next log sequence to archive      13
Current log sequence              13
SQL>

Prerequisites for RMAN backups

The following sections identify the requirements for performing RMAN backups:
•
Determining the Oracle SID and Home directory in a non-RAC environment
•
Creating the RMAN repository
•
Registering the target database
•
Enabling Control File Autobackups
•
Enabling Flashback Database
•
Enabling Block Change Tracking
Determining the Oracle SID and Home directory in a non-RAC environment
To identify the Oracle system ID (SID) and home directory, use one of the following procedures (based on the OS running on the Oracle Database Server).
Windows
On Windows, the SID and Oracle Home can be determined from the Registry.
1
Launch the Registry Editor on the Oracle Database Server.
a
On the taskbar, click Start, and then click Run.
b
On the Run dialog, type regedit, and then click OK.
2
Locate the following registry key:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
Various directories are displayed. Each folder prefaced with “KEY_” represents an installation of Oracle on the target machine (if multiple installations of Oracle exist on the machine).
3
Open the folder entitled “KEY_<Oracle_Home>” that represents the target installation of Oracle to list the registry items in the frame on the right.
4
In the Name column, locate the following items, and make note of the associated entry in the Data column:
•
ORACLE_HOME
•
ORACLE_SID
5
Exit the Registry Editor.
Linux/UNIX
On Linux/UNIX-based OSs, you can use the “oratab” file to identify the SID and Oracle Home.
1
Open the “oratab” file by issuing the following command in a terminal window:
more /etc/oratab
2
In the “oratab” file, note the application information.
The file contains entries for each Oracle database running on the server in the following format:
<ORACLE_SID>:<ORACLE_HOME>:<Additional Information>
For example, if “oratab” contains the following:
PROD:/u03/app/oracle/product/10.2.0/db_1:N
It indicates that:
•
“PROD” is the ORACLE_SID
•
“/u03/app/oracle/product/10.2.0/db_1” is the ORACLE_HOME

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: you must 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. Note that SYS cannot be the owner of the Recovery Catalog. Decide which database you will use to install the Recovery Catalog schema. Dell recommends that you create a separate database for the Recovery Catalog and run the catalog database in ARCHIVELOG mode.
Next, you must 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, refer to 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.
For example:
> 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>;
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating