• Torne-se um profissional do portal
• Download
• Imprimir
• Meus downloads ()

• Suporte
• Documentação técnica
• NetVault Plug-in for Oracle 13.0
• NetVault Plug-in for Oracle 13.0 - User Guide

NetVault Plug-in for Oracle 13.0 - User Guide

Navegação de conteúdo  

Introducing Quest® NetVault® Plug-in  for Oracle

Quest NetVault 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 NetVault Policy Management

Installing and removing the plug-in

Prerequisites

NetVault 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 Using DR Series or QoreStor as the storagedevice for Oracle Database 12.x or later on Linux or UNIX

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

Flashback Logs

Viewing Flashback Database status Flashback Database options Flashback Database restrictions Restoring data with the plug-in and Flashback Database

Restoring data

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 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 '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 media name

Performing CLI-based restores Using the CROSSCHECK and CATALOG commands with backups

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

Deployment

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

Restoring data

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

Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs)

Oracle PDBs: an overview Enabling connection to a PDB Querying CDB, PDB, and non-CDB databases Restrictions for backing up and restoring a PDB Backing up data Restoring data

Troubleshooting

Unable to add a database Backup fails Backup job hangs Restore fails Oracle RMAN output is not displayed correctly in binary logs

• Viewing Topics 121 - 124 of 220

×

Renaming or relocating files

With the RMAN backup method, the plug-in lets you rename the Control File and datafiles during restore. Renaming files can be useful if you do not want to overwrite the existing version and want to create a copy of the file. You can also relocate the files to a different directory while restoring it with the plug-in.

1	Complete the steps outlined in Preparing the database for recovery.

2	In the Navigation pane, click Create Restore Job.

3	In the saveset table, select the applicable saveset, and click Restore.

For more information, see Selecting data for a restore.

4	On the Create Selection Set page, click the datafile or Control File to restore, and select Rename from the context menu.

5	In the Rename/Relocate dialog box, enter the applicable information.

•	Rename: Enter the new name.

•	Relocate: Enter the new path.

The plug-in uses the RMAN SET NEWNAME command to restore or rename — or both — RMAN backups. The SET NEWNAME command has precedence over the DB_CREATE_FILE_DEST parameter. If the full path is not specified for a restore or rename, the plug-in behaves as follows:

•	SPFILE: The file is restored to the “$ORACLE_HOME/dbs” directory with the new name.

•

Datafile:

•	If you specify a new location when the file is created, the file is restored or renamed to this location with the new name.

•	If you do not specify a new location when the file is created, the file is restored or renamed to “$ORACLE_HOME/dbs” with the new name.

 

NOTE: A full path can include a path to an ASM location. For example: +DATA/my_db/my_datafile_renamed.dbf

When renaming the Control File during restore, the resulting filename should exist in the CONTROL_FILES list in the Oracle Parameter File.

6	To apply changes, click OK.

The item is accompanied by the name and location information in parentheses.

7	Continue with the restore procedure as explained in Finalizing and submitting the job.

Duplicating a database in a non-RAC environment

A Duplicate Database backup lets you create a duplicate or clone of a source database for special purposes that does not affect the backup and restore procedures for the source database. RMAN supports duplicating databases to increase a DBA’s flexibility when performing the following tasks:

•	Testing backup and recovery procedures.

•	Testing an upgrade to a new release of the Oracle database.

•	Testing the effect of applications on database performance.

•	Generating reports.

For more information on duplicating a multi-instance RAC database, see Duplicating a database in a RAC environment. For more information on Oracle’s Duplicate Database functionality, see Duplicating a Database in the Oracle Database Backup and Recovery User’s Guide.

The plug-in provides the following restore scenarios for the Duplicate Database backup:

•	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

Restoring a Duplicate Database to the same server

The following procedure details the steps to restore a Duplicate Database backup to the local or same server where the source database resides. Because the duplicated database or destination database resides on the same physical server as the source database, the destination database must use a different directory structure.

•	Prerequisites

•	Restoring the Duplicate Database

Prerequisites

To restore a Duplicate Database backup to the same server, the following prerequisites must be met:

•	Same version of Oracle database software: The version and edition of Oracle for the destination database must be identical to the version and edition of Oracle being used for the source database. This requirement includes identical patch levels.

•	Duplicate Database backup available: A Duplicate Database backup must be completed successfully and made available.

•	Source database in open state: The source database must remain in an OPEN READ WRITE state during the entire Duplicate Database restore process.

•	Auxiliary instance prepared: RMAN’s backup-based Duplicate Database process requires the preparation of an auxiliary instance:

1

Oracle password file for auxiliary instance created: Required if you want to use a password file versus OS authentication for the auxiliary connection when duplicating to the same host as the source database. For more information on creating a password file, see Creating and Maintaining a Password File in the Oracle Database Administrator’s Guide.

2	Oracle Net connectivity established to auxiliary instance: The auxiliary instance must be available through Oracle Net by adding the instance to the “tnsnames.ora” file. Additionally, on Windows platforms, perform the following command to start the instance:

oradim -new -sid <sid_name>

3

Auxiliary instance destination directories exist: The following destination directories for the auxiliary instance must be created on the server where the destination database resides. If the destination database stores its datafiles in ASM, the ASM instance name for the destination database must exist.

•	Control_Files

•	DB_Create_File_Dest

•	Audit_File_Dest

•	Background_Dump_Dest

•	User_Dump_Dest

4	PFILE created for auxiliary instance: A client-side PFILE for the Auxiliary Database must be created from the SPFILE of the source database.

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

sqlplus sys/<password>@<source_connect_identifier> AS SYSDBA

•	Create a PFILE from the SPFILE.

create pfile = '<PFILE_destination_directory>/

init<auxiliary_sid>.ora' from spfile;

5	PFILE updated with auxiliary values: The PFILE created for the auxiliary instance must be updated with the parameter values specific to the auxiliary instance.

•	Remove all entries that begin with: <source_sid>.__

•	Update the *.db_name= entry to reflect the name of the destination database.

•

Update the following entries to reflect the destination directory for the auxiliary instance. This directory must exist; however, if the source database stores the datafiles in ASM, the ASM instance name for the destination database should be specified for each of the following control_files and db_create_file_dest parameters:

*.audit_file_dest=

*.background_dump_dest=

*.control_files=

*.user_dump_dest=

*.db_create_file_dest=

*.db_recovery_file_dest=

•	Comment out the following entry by inserting a “#” (number sign) at the beginning of the following entry:

*.dispatchers='(PROTOCOL=TCP) (SERVICE=<source_sid>XDB)'

•	Add the following line to specify the pairs of strings for converting the names of datafiles and tempfiles.

*.db_file_name_convert='<source_db_create_file_dest>/<source_sid>',

'<destination_db_create_file_dest>/<destination_sid>'

For example:

*.db_file_name_convert=' C:\oracle\oradata\prod',

'c:\oracle\oradata\test'

•	Add the following line to specify the pairs of strings for naming online redo log files:

*.log_file_name_convert='<source_db_create_file_dest>/

<source_sid>', '<destination_db_create_file_dest>/

<destination_sid>'

For example:

*.log_file_name_convert=' C:\oracle\oradata\prod',

'c:\oracle\oradata\test'

6	Auxiliary instance started in NOMOUNT state: The auxiliary instance must be started in NOMOUNT state with the PFILE that has been updated with the parameter values specific to the auxiliary instance.

•	Start SQL*Plus, and connect with administrator privileges to the auxiliary instance.

sqlplus sys/<password>@<auxiliary_connect_identifier> AS SYSDBA

•	Start the instance in NOMOUNT state.

startup nomount pfile = '<PFILE_destination_directory>/

init<auxiliary_sid>.ora'

7	Auxiliary instance created from SPFILE from the PFILE

create spfile from pfile='<PFILE_destination_directory>/

init<auxiliary_sid>.ora';

8	Exit SQL*Plus.

You must exit SQL*Plus for the Duplicate Database restore to complete successfully.

Restoring the Duplicate Database

To restore the Duplicate Database, perform the following steps.

1	On the Create Restore Job — Choose Saveset page, find the applicable Duplicate Database backup, and click Next.

2	On the Create Selection Set page, navigate to the source NetVault Client and database, select the Whole Database node, and click .

3	Click the Clone Database tab, and select the Duplicate Database option.

4	In the Destination Database section:

•	Specify the Oracle Net Service name of the auxiliary instance in the Target Service field.

•	Specify the Oracle Home for the auxiliary instance.

•	Specify the Oracle SYSDBA User Name that is used by the plug-in to connect to the auxiliary instance.

•	Specify the Oracle SYSDBA Password.

5	In the Duplicate From Database section:

•	Specify the Oracle SID for the source database.

•	Specify the Oracle Home for the source database.

•	Specify the Oracle SYSDBA User Name that is used by the plug-in to connect to the source database.

•	Specify the Oracle SYSDBA Password.

6	Continue with the restore procedure, including completion of the Schedule and Advanced Options lists, as explained in Finalizing and submitting the job.

Restoring a Duplicate Database to an alternate server with the same directory structure

The following procedure details the steps to restore a Duplicate Database backup to an alternate or remote server — other than where the source database resides — and use the same directory structure as the source database.

•	Prerequisites

•	Restoring the Duplicate Database

Prerequisites

To restore a Duplicate Database backup to an alternate or remote server, the following prerequisites must be met:

•	Same version of Oracle database software: The version and edition of Oracle for the destination database must be identical to the version and edition of Oracle being used for the source database. This requirement includes identical patch levels.

•	Duplicate Database backup available: A Duplicate Database backup must be completed successfully and made available.

•	Source database in open state: The source database must remain in an OPEN READ WRITE state during the entire Duplicate Database restore process.

•	Auxiliary instance prepared: RMAN’s backup-based Duplicate Database process requires the preparation of an auxiliary instance:

1

Oracle password file for auxiliary instance created: Required if you want to use a password file versus OS authentication for the auxiliary connection when duplicating to the same host as the source database. For more information on creating a password file, see Creating and Maintaining a Password File in the Oracle Database Administrator’s Guide.

2

Oracle Net connectivity established to auxiliary instance: The auxiliary instance must be available through Oracle Net by adding the instance to the “tnsnames.ora” file of both the source server and the alternate server. Additionally, on Windows platforms, perform the following command to start the instance:

oradim -new -sid <sid_name>

3

Auxiliary instance destination directories exist: The following destination directories for the auxiliary instance must be created on the server where the destination database resides. If the destination database stores its datafiles in ASM, the ASM Instance name for the destination database must exist.

•	Control_Files

•	DB_Create_File_Dest

•	Audit_File_Dest

•	Background_Dump_Dest

•	User_Dump_Dest

4	PFILE created for auxiliary instance: A client-side PFILE for the Auxiliary Database must be created from the SPFILE of the source database.

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

sqlplus sys/<password>@<source_connect_identifier> AS SYSDBA

•	Create a PFILE from the SPFILE.

create pfile = '<PFILE_destination_directory>/

init<auxiliary_sid>.ora' from spfile;

5	PFILE updated with auxiliary values: The PFILE created for the auxiliary instance must be updated with the parameter values specific to the auxiliary instance.

•	Remove all entries that begin with: <source_sid>.__

•	Update the *.db_name= entry to reflect the name of the destination database.

•

Update the following entries to reflect the destination directory for the auxiliary instance. This directory must exist; however, if the source database stores the datafiles in ASM, the ASM instance name for the destination database should be specified for each of the following control_files and db_create_file_dest parameters:

*.audit_file_dest=

*.background_dump_dest=

*.control_files=

*.user_dump_dest=

*.db_create_file_dest=

*.db_recovery_file_dest=

•	Comment out the following entry by inserting a “#” (number sign) at the beginning of the following entry

*.dispatchers='(PROTOCOL=TCP) (SERVICE=<source_sid>XDB)'

6	Auxiliary instance started in NOMOUNT state: The auxiliary instance must be started in NOMOUNT state with the PFILE that has been updated with the parameter values specific to the auxiliary instance.

•	Start SQL*Plus, and connect with administrator privileges to the auxiliary instance.

sqlplus sys/<password>@<auxiliary_connect_identifier> AS SYSDBA

•	Start the instance in NOMOUNT state.

startup nomount pfile = '<PFILE_destination_directory>/

init<auxiliary_sid>.ora'

7	Auxiliary instance created from SPFILE from the PFILE.

create spfile from pfile='<PFILE_destination_directory>/

init<auxiliary_sid>.ora';

8	Exit SQL*Plus.

You must exit SQL*Plus for the Duplicate Database restore to complete successfully.

•	NetVault software and the Plug‑in for Oracle installed: The same version of NetVault software and the plug-in must be installed and configured on the alternate server where the destination database resides.

When configuring the plug-in on the alternate server, ensure that the following Default Attributes are defined:

•	NetVault: Specify the name of the NetVault Server where the source database server was added as a NetVault Client.

•	Do Restore From NetVault Server: Specify the name of the NetVault Server where the source database server was added as a NetVault Client.

•	Restore Backup taken from NetVault Client: Specify the NetVault Machine Name for the source database server.

For more information, see Configuring default settings.

•	Source database added to Plug‑in for Oracle installed on alternate server: The source database must be added to the plug-in that is installed on the alternate (standby) server where the destination database resides.

For example, the production Oracle Server is named salesdb. On the alternate server that has the plug-in installed, add a database named salesdb. You complete this step even though the existing database has not yet been cloned to the alternate server. This step forces the plug-in to create a placeholder that can then be accessed during the cloning process when the Oracle database is restored to the alternate (standby) server.

For more information on adding a database, see Adding a database. These instructions work for the original database, as well as the placeholder that you create on the alternate server.

Restoring the Duplicate Database

1	On the Create Restore Job — Choose Saveset page, find the applicable Duplicate Database backup, and click Next.

2	On the Create Selection Set page, navigate to the source NetVault Client and database, select the Whole Database node, and click .

3	Click the Clone Database tab, and select the Duplicate Database option.

4	In the Destination Database section:

•	Specify the Oracle Net Service name of the auxiliary instance in the Target Service field.

•	Specify the Oracle Home for the auxiliary instance.

•	Specify the Oracle SYSDBA User Name that is used by the plug-in to connect to the auxiliary instance.

•	Specify the Oracle SYSDBA Password.

•	Select the Use nofilenamecheck option.

5	In the Duplicate From Database section:

•	Specify the Oracle SID for the source database.

•	Specify the Oracle Home for the source database.

•	Specify the Oracle SYSDBA User Name that is used by the plug-in to connect to the source database.

•	Specify the Oracle SYSDBA Password.

6	In the Target Client list, select the NetVault Machine Name of the alternate server where the destination database resides.

7	Continue with the restore procedure, including completion of the Schedule and Advanced Options lists.

For more information, see Finalizing and submitting the job.

•  Voltar
• Viewing Topics 121 - 124 of 220
• Avançar 

Procurar este documento Procurar todos os documentos

×

 Bem-vindo ao Suporte

Você pode encontrar ajuda de suporte on-line para *produto* da Quest em um local de suporte afiliado. Clique em Continue (Continuar) para ser direcionado ao conteúdo de suporte correto e à assistência a *produto*.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação

© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center