Professional Documents
Culture Documents
Administration Guide
P/N 300-006-990
REV A02
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Contents
Preface
Chapter 1
Introduction
Naming conventions used in this guide............................................................... 20
Importance of backups............................................................................................ 20
Product features ....................................................................................................... 20
Scheduled compared to manual backups ..................................................... 21
Deduplication backups and restores ............................................................. 21
Probe-based backups ....................................................................................... 23
Proxy backups and restores ............................................................................ 24
VMware support............................................................................................... 25
Archived redo log backups ............................................................................. 25
Control file autobackup ................................................................................... 25
Automatic channel allocation ......................................................................... 26
Backup and restore optimization ................................................................... 26
Backup copies.................................................................................................... 27
Backup of backup sets...................................................................................... 29
Cluster and RAC backups and restores......................................................... 29
Configuration wizards..................................................................................... 30
Internationalization (I18N) and localization (L10N) ................................... 33
Oracle Data Guard support............................................................................. 36
Parallelism ......................................................................................................... 36
Policy uniformity .............................................................................................. 37
Restartable backups.......................................................................................... 37
Retention policies ............................................................................................. 38
Save set bundling.............................................................................................. 39
Other Oracle features ....................................................................................... 44
Software used in the NMO environment ............................................................. 47
NetWorker software ......................................................................................... 47
NMO software................................................................................................... 48
NetWorker PowerSnap Module software ..................................................... 48
Oracle backup and recovery system .............................................................. 49
NMO components ................................................................................................... 51
NMO backup and restore processes ..................................................................... 52
Regular scheduled backup processes ............................................................ 53
Regular manual backup processes................................................................. 54
Deduplication backup processes.................................................................... 55
Regular restore processes ................................................................................ 57
Deduplication restore processes..................................................................... 58
Contents
Chapter 2
Software Configuration
Configuration roadmap.......................................................................................... 62
Verify the Oracle Server configuration................................................................. 63
Verify the NetWorker resources ............................................................................ 63
NetWorker Server resource.............................................................................. 63
NetWorker user group privileges ................................................................... 64
NetWorker Schedule resource......................................................................... 66
NetWorker Device resources ........................................................................... 66
NetWorker volume pools................................................................................. 66
Firewall support ................................................................................................ 67
Configuring I18N support ..................................................................................... 67
Requirements for I18N support ...................................................................... 68
Configure I18N support ................................................................................... 68
Configure L10N support ........................................................................................ 69
Migrating a legacy configuration with the nsrnmoadmin command ..............69
Requirements for using the nsrnmoadmin command for migration ........ 70
Migration command syntax and options ...................................................... 71
Configuring a backup with the NMC wizard......................................................72
About the backup configuration wizard ....................................................... 72
Requirements for using the backup configuration wizard ......................... 73
Configure a backup with the wizard ............................................................. 73
Configuring a backup with the NMC legacy method ........................................75
About backup configuration with the legacy method................................. 75
Create RMAN scripts for backups.................................................................. 75
Customize the nsrnmo script .......................................................................... 79
Configure a Group resource with NMC ........................................................ 86
Configure a Schedule resource with NMC.................................................... 87
Configure a Client resource with NMC ......................................................... 87
Configure save set bundling............................................................................ 91
Configure policy uniformity ........................................................................... 92
Configuring a deduplication backup ................................................................... 93
Requirements for a deduplication backup .................................................... 94
Best practices for a deduplication backup..................................................... 94
Configure a deduplication backup................................................................. 95
Configuring a probe-based backup ...................................................................... 97
Requirements for a probe-based backup ....................................................... 97
Configure a probe-based backup.................................................................... 97
Chapter 3
Backup Procedures
Manual backup procedures ..................................................................................104
Requirements for a manual backup ............................................................. 104
Manual backup through the RMAN command line interface ................. 105
Manual backup through Oracle Enterprise Manager Backup Management
Tools .................................................................................................................. 105
NetWorker server bootstrap backup ............................................................ 106
Cancel a manual backup ................................................................................ 107
Monitor a manual backup.............................................................................. 108
Scheduled backup procedures .............................................................................110
Test a scheduled backup ................................................................................ 110
Cancel a scheduled backup ........................................................................... 111
Monitor a scheduled backup......................................................................... 112
Automation of NSR_SERVER and NSR_GROUP parameter settings .... 113
Regular backup information in NetWorker indexes .........................................114
Deduplication backup information in NetWorker indexes..............................115
Contents
Chapter 4
Chapter 5
Disaster Recovery
About disaster recovery........................................................................................ 130
Preparing an Oracle database for disaster recovery ......................................... 130
Create the DBID text file................................................................................ 131
Set up a postcommand script for backup of Oracle-related files............. 131
Set up RMAN backups of the database and related files ......................... 132
Set up RMAN backups of Recovery Catalog.............................................. 132
Performing a disaster recovery............................................................................ 133
NetWorker server recovery ........................................................................... 133
Oracle disaster recovery to a new host........................................................ 133
Sample postcommand script................................................................................ 134
Chapter 6
Chapter 7
Contents
Appendix A
Appendix B
RMAN Commands
The delete expired backup command ................................................................ 210
The change...crosscheck and crosscheck commands ....................................... 210
The pool option of the backup command.......................................................... 210
The send command............................................................................................... 211
Syntax rules...................................................................................................... 211
Two ways to run the send command........................................................... 213
Precedence rules.............................................................................................. 215
The set duplex command..................................................................................... 215
The trace option of the backup command ......................................................... 217
Contents
Appendix C
220
221
222
223
231
233
235
236
Glossary
Index
Contents
Figures
Title
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Page
Figures
10
Tables
Title
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Page
NMO components................................................................................................................. 51
NetWorker Server resource attributes ............................................................................... 63
User group privileges required for NMO operations...................................................... 65
Options of the nsrnmoadmin command for migration................................................... 72
NetWorker Client resource attributes ................................................................................ 88
NetWorker Probe resource attributes ................................................................................ 98
PowerSnap parameters ...................................................................................................... 167
NWORA parameter resources .......................................................................................... 184
NWORA SID resource components ................................................................................. 186
Parameters in the RMAN command or script ................................................................ 201
Option values in the send command ............................................................................... 213
Set duplex command values.............................................................................................. 216
Trace option values and conditions traced...................................................................... 217
Error messages from the libnwora library....................................................................... 223
Error messages from the nsrnmoadmin program.......................................................... 231
Error messages from the nsrnmoinfo program .............................................................. 234
Error messages from the nsrnmoprobe program ........................................................... 235
Error messages from the nsrnmostart program ............................................................. 236
11
Tables
12
Examples
Title
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Page
Using the configure channel command with parms option for automatic channels .. 26
Specifying parameter values per automatic channel ....................................................... 26
Using the set backup copies command in the RMAN script .......................................... 28
Using automatic channels for backup copies .................................................................... 28
Expiring a backup ................................................................................................................. 38
Save set bundling for a one-week scheduled backup cycle of a tablespace ................. 42
Save set bundle join .............................................................................................................. 43
Splitting a save set bundle across volumes ....................................................................... 43
Using save set consolidation to re-unite a save set bundle ............................................. 44
RMAN script for a manual backup .................................................................................... 75
RMAN script for AES encryption during an Oracle backup .......................................... 76
RMAN script for a scheduled backup ................................................................................ 77
RMAN script for a manual deduplication backup ........................................................... 96
Possible Command Options settings for the nsrnmoprobe program ........................... 99
Multiple probes for a probe-based backup ..................................................................... 100
RMAN script to restore a tablespace ................................................................................ 121
RMAN script to restore an AES encrypted backup ....................................................... 122
RMAN script to restore from a specified pool ................................................................ 122
Sample nsrnmoinfo commands for Oracle restores ....................................................... 125
Volume information displayed by the nsrnmoinfo command ..................................... 125
Sample postcommand script on UNIX ............................................................................ 134
Sample postcommand script on Windows ...................................................................... 135
Setting up RAC nodes as storage nodes .......................................................................... 142
RMAN script for a manual Oracle backup on a RAC system ...................................... 146
RMAN script for an Oracle restore on a RAC system ................................................... 146
RMAN scripts with multiple channels ............................................................................ 165
PowerSnap parameter settings .......................................................................................... 168
PowerSnap parameter settings for a Celerra NAS device ............................................ 168
Proxy backup failure ........................................................................................................... 172
Proxy backup entries in the client file index ................................................................... 175
Proxy backup entries in the media database ................................................................... 176
Resource file backup entry in the client file index ......................................................... 176
Resource file backup entry in the media database ......................................................... 176
RESTORE_TYPE_ORDER parameter settings ................................................................ 177
Symbolic link specified in the set newname command ................................................. 180
Relocation of a raw volume ............................................................................................... 180
Default NWORA parameter resources ............................................................................ 186
NWORA SID resource ........................................................................................................ 187
Connection file contents ..................................................................................................... 188
Proxy backup entries in the index of a physical cluster client ...................................... 196
13
Examples
Title
41
42
43
44
14
Page
Proxy backup entries in the index of a virtual cluster client ......................................... 197
A send command sets the parameters for a specified channel ..................................... 212
An rman send command sets a parameter for all channels .......................................... 214
Order of parameters set according to the precedence rules .......................................... 215
Preface
As part of an effort to improve and enhance the performance and capabilities of its product
lines, EMC periodically releases revisions of its hardware and software. Therefore, some
functions described in this document may not be supported by all versions of the software or
hardware currently in use. For the most up-to-date information on product features, refer to
your product release notes.
If a product does not function properly or does not function as described in this document,
please contact your EMC representative.
Audience
This document is part of the EMC NetWorker Module for Oracle (NMO)
documentation set, and is intended for use by system administrators and Oracle
database administrators (DBAs) who are responsible for installing software and
maintaining the Oracle Server backup and recovery systems. Operators who monitor
Oracle database backups may also find this document useful.
Readers of this document are expected to be familiar with the following topics:
Related
documentation
Documentation related to the use of this product can be found at the EMC website,
http://Powerlink.EMC.com, including:
15
Preface
Conventions used in
this document
CAUTION
A caution contains information essential to avoid data loss or damage to the system
or equipment.
IMPORTANT
An important notice contains information essential to software or hardware
operation.
Typographical conventions
EMC uses the following type style conventions in this document:
Normal
Bold
16
Italic
Courier
Used for:
System output, such as an error message or script
URLs, complete paths, filenames, prompts, and syntax when shown outside of
running text
Courier bold
Used for:
Specific user input (such as commands)
Courier italic
<>
[]
Preface
{}
...
Your suggestions will help us continue to improve the accuracy, organization, and
overall quality of the user publications. Please send your opinion of this document to:
SSGdocumentation@EMC.com
17
Preface
18
1
Introduction
Introduction
20
20
20
47
51
52
19
Introduction
Oracle Server host refers to the host where both the Oracle Server and EMC
NetWorker Module for Oracle (NMO) software are installed.
Unlike the NetWorker software, which uses the term recover for all data retrieval
activities, Oracle distinguishes between restoring and recovering a database:
Restore refers to retrieving individual datafiles from backup and storing the
files on disk.
Recover refers to applying the redo logs to make the database consistent.
This guide follows the Oracle terminology.
"UNIX" refers to both UNIX and Linux operating systems, unless specified
otherwise.
Importance of backups
The reliability of computer equipment has improved greatly in recent years, but
system and hardware failures still occur, sometimes with catastrophic results.
In a client/server environment, data can be lost due to hardware failures and user
errors. Software bugs, procedural flaws, and simple user errors are common
problems that necessitate database restores from backup storage media. A viable
backup strategy can help in the recovery from disastrous situations.
Database administrators must recognize the importance of performing regular
backups of database files and frequent backups of archived redo logs. If all archived
redo logs are lost, a database can be recovered only to the time of the last consistent
backup. Without backups and archived redo logs, the database cannot be recovered
at all.
Product features
The following sections describe major features of the NMO, Oracle Recovery
Manager (RMAN), and Oracle Server software.
Certain sections refer to the send command, which is used to set parameters in the
RMAN script for an NMO backup, as described in The send command on
page 211.
The Oracle backup and recovery documentation provides more details on RMAN
backups and restores and Oracle product features.
20
Introduction
Product features
21
Introduction
The Avamar client-side binary, nsravtar, is installed on the NMO client with the
NetWorker client software. During a deduplication backup, the nsravtar process
sends the deduplicated client data to the Avamar server. A deduplication NMO
backup uses a hash cache on the client side. The Avamar and NetWorker
documentation provides more details about caches in deduplication backups.
The following sections describe the processes involved in deduplication backups and
restores:
22
Introduction
Probe-based backups
NMO 5.0 software provides new support for probe-based backups (also known as
event-based backups). A probe-based backup is a type of scheduled backup:
The NetWorker server starts a regular scheduled backup based on a time interval.
The NetWorker server starts a probe-based backup when specified conditions are
met.
The NetWorker Module for Oracle release notes provides details on the NetWorker
requirements for the support of probe-based backups.
Probe-based backups are not supported for proxy backups or cluster/RAC
environments.
Workflow of probe-based backups
A probe-based NMO backup starts when both of the following are true:
(Condition 1) The current time is within a specified window of time (the backup
window, defined by the probe start time and probe end time in the probe-enabled
backup group resource).
Product features
23
Introduction
Types of probes
There are two different types of probes:
An NMO probe.
The NMO probe is implemented through the NMO program nsrnmoprobe. The
nsrnmoprobe program returns a successful result (signifying that the condition
being checked has been met) when it detects either of the following:
The number of Oracle redo logs generated since the previous probe-based
backup exceeds a number known as the change threshold.
A new database incarnation (reset log) has occurred since the previous
probe-based backup.
User-defined probes.
A user-defined probe checks if any other user-defined condition (other than the
number of generated Oracle redo logs) has been met since the previous
probe-based backup. (This option requires more advanced configuration.) To
implement a user-defined probe, you must create a new script or program that
checks for the condition, as described in Configuring a probe-based backup on
page 97.
You must configure the required parameters and NetWorker resources to specify the
probe interval, backup window, and any other settings for a probe-based backup.
Configuring a probe-based backup on page 97 provides details on how to
configure a probe-based backup.
24
Introduction
VMware support
NMO 4.5 provided support for regular backups and restores of an Oracle database
installed on a VMware Virtual Machine (VM) on an ESX server.
NMO 5.0 extends this support with the support for the following advanced features
of a VMware ESX server:
VMotion The VMotion feature enables migration of virtual machines from one
ESX server to another while the servers are on. The migration is seamless to the
applications running on the virtual machines, and a user does not experience any
disconnection. If a migration occurs during an NMO backup or restore, the
backup or restore is not interrupted. VMware documentation provides details on
the VM requirements for VMotion.
The NetWorker Module for Oracle release notes provides details on the NetWorker
requirements for the support of VMware features.
Product features
25
Introduction
If the control file autobackup is set to on and the RMAN backup is performed with
NMO, the control file autobackup will also be performed with NMO. As a result, one
or more channels of device type sbt_tape must be allocated for the restore.
Note: Oracle also supports autobackup of the current server parameter file together with
control file autobackup.
IMPORTANT
Manual and automatic channels are mutually exclusive and cannot be mixed in an
RMAN session. The format of an automatic channel name of the device type for
NMO backups and restores is ORA_SBT_n or ORA_SBT_TAPE_n, where n is the
channel number. Do not use this name format for manual channel allocation for
NMO. Otherwise, RMAN reports an error.
With automatic channel allocation, specification of the send command before the
backup or restore command causes the following error:
RMAN-06422: no channels found for SEND command
You must use the configure channel...parms... command to set the NSR* parameters
for automatic channels for an NMO backup. Do not use the send command or option
to set the NSR* parameters for automatic channels if you plan to use scheduled
backups.
Table 10 on page 201 lists all the NSR* parameters and their requirements.
Example 1
Using the configure channel command with parms option for automatic channels
Automatic channels are configured for NMO backups with the NetWorker server
server1.emc.com by typing the following configure channel...parms... command:
configure channel device type sbt_tape parms
ENV=(NSR_SERVER=server1.emc.com)
This command sets the default parameters for all the automatic channels.
Example 2
Specific NSR* parameter values can be set for different channels (for example, a
separate setting of parameter NSR_GROUP for each channel) by typing the configure
channel n device type...parms... command, where n represents a channel number.
An NMO debug file is specified for the second automatic channel by typing the
following configure channel command:
configure channel 2 device type sbt_tape parms
ENV=(NSR_DEBUG_FILE=/db/logs/backup.log)
Introduction
Note:
- To force a backup that would otherwise be skipped due to backup optimization, use the force
option in the backup command.
- When RMAN skips a backup due to backup optimization, it does not produce an error
message. However, RMAN does issue a warning message similar to the following:
skipping archive log file...
IMPORTANT
When using Oracle backup optimization with NMO backups and restores, run the
crosscheck command regularly to synchronize the Recovery Catalog and
NetWorker indexes. This ensures that backups expired by the NetWorker server
are also marked as expired in the Recovery Catalog and RMAN does not skip a
backup when a referenced backup has already expired in NetWorker.
The restore optimization function prevents RMAN from restoring a file if the original
file is already in the correct location and contains the expected information.
Note: To force a restore that would otherwise be skipped due to restore optimization, use the
force option in the restore command.
Backup copies
IMPORTANT
If more than one RMAN channel is used for backup copies of an NMO backup,
parameter values set with the send command or option are passed by RMAN to the
first backup channel only. Due to this send command limitation, NMO does not
support the use of RMAN backup copies commands during scheduled backups.
NMO supports backup copies with manual backups only.
Use the RMAN commands for backup copies only during manual backups when the
parameters NSR_SERVER, NSR_DATA_VOLUME_POOL,
NSR_DATA_VOLUME_POOL1, NSR_DATA_VOLUME_POOL2, and
NSR_DATA_VOLUME_POOL3 are set with the parms option, not with the send
command or option.
The set duplex command is deprecated (no longer supported by Oracle, but still
functional in some Oracle releases). The Oracle documentation provides more details.
Despite the fact that RMAN provides different commands for duplexing backups, the
rules for duplexing through NMO remain the same as with the set duplex command.
Separate NetWorker pools must still be defined for each copy. The set duplex
command on page 215 provides more information on the set duplex command and
setting up NetWorker pools for each copy.
Product features
27
Introduction
Manual backups can be duplexed (up to four copies) by using one of the following
commands:
The configure...backup copies for device type sbt_tape to... command specifies
persistent settings for duplexing backups through NMO.
For example, specify persistent settings for duplex copies of datafiles and
archived redo logs (respectively) in NMO backups with the following types of
configure commands:
configure datafile backup copies for device type sbt_tape to 2
configure archivelog backup copies for device type sbt_tape to 2
The backup command with the copies option applies to objects within the
backup command. The backup...copies setting takes precedence over the
persistent settings in the configure...backup copies command.
The set backup copies command applies to all backup objects in the same run
job.
In the following examples, the parms option is used to configure the channel and set
the required parameters. These sample scripts must be invoked manually with
RMAN, for example, by using the following command:
rman cmdfile script_name
Example 3
The following RMAN script uses the set backup copies command to generate the
backup copies. The parameters are set with the parms option, as required. The
RMAN script must be invoked for a manual backup, not a scheduled backup:
run {
set backup copies 4;
allocate channel ch1 parms ENV=(NSR_SERVER=server_name,
NSR_DATA_VOLUME_POOL=nmo1, NSR_DATA_VOLUME_POOL1=nmo2,
NSR_DATA_VOLUME_POOL2=nmo3, NSR_DATA_VOLUME_POOL3=nmo4);
backup format '%d_%U'
tag tag_name
(tablespace 'SYSTEM' );
release channel ch1;
}
Example 4
28
Introduction
The backup set on disk can also be deleted with the delete input option in the backup
device type sbt backupset... command. For example, to back up the backup sets that
were created on disk more than a week ago and then remove the backup sets from
disk, use the following command:
backup device type sbt backupset completed before sysdate-7 delete
input
Product features
29
Introduction
Configuration wizards
NMO 5.0 software supports new backup and recovery configuration wizards that are
integrated with the NetWorker Management Console (NMC). The configuration
wizards used in NMO release 4.5 or earlier are replaced by the NMC-based wizards
in NMO release 5.0.
Configuration wizard plug-in components are installed with the NMO software on
the NMO client host. NMC loads the NMO wizard plug-in at run time. You can run
the NMO wizards from the NetWorker Console Administration window, which you
can start on any supported host by using a web browser session and specifying the
Console server URL.
The NetWorker Module for Oracle release notes provides details on the NetWorker
requirements for the support of the NMC-based configuration wizards.
Main features of the wizards
The configuration wizards can be used to configure the following for an NMO client:
RMAN scripts for Oracle database duplication to either a local or remote host.
Recovery configuration wizard on page 118 provides details on the recovery
configuration wizard.
30
Configure a new or use an existing NetWorker Group resource for the backup
Client resource.
Configure new or use existing browse and retention policies for the backup Client
resource.
Optionally save a copy of the configuration settings from the Client resource to a
nsrnmo script or RMAN script.
Modify a backup configuration that was created with the NMC-based NMO
configuration wizard.
Modify a backup configuration that was created either with the wizard from
NMO release 4.5 or earlier, or with the legacy method, but only after the
configuration has been migrated according to Migration of configurations for
the wizard on page 32.
Introduction
Note: NMO 5.0 still supports the legacy method of backup configuration whereby you
manually create a nsrnmo script and RMAN script, set any required parameters in the
NWORA resource file, and configure the NetWorker resources with NMC (without the
wizard). Configuring a backup with the NMC legacy method on page 75 describes the
legacy configuration method.
The wizard does not automatically generate a nsrnmo script and RMAN script, but
provides an option to save configuration settings to a nsrnmo script or RMAN script
on disk. These scripts are meant for reference use only.
When you run a backup that was configured through the wizard, the backup does not
access any nsrnmo or RMAN script file that the wizard saved to disk. Instead, the
backup accesses the configuration information that the wizard stored in the Client
resource.
The wizards do not store any database connection passwords in any RMAN scripts
that are saved to disk.
The backup configuration wizard also sets the following values in the Client
resource:
where:
database_Net_service_name is the the name of the Oracle database to be
backed up.
level is the Oracle backup level (full, incr_differential, or incr_cumulative).
name_of_first_tablespace_or_datafile is the name of the first tablespace or datafile
in the backup list. This name is included in Save Set attribute only if a partial
database (subset of the entire database) is selected for backup.
Product features
31
Introduction
Modify a backup configuration that was created either with the wizard from
NMO 4.5 or earlier, or with the legacy method, unless the configuration has been
migrated according to Migration of configurations for the wizard on page 32.
If you have a backup configuration that was created with the wizard from NMO
release 4.5 or earlier, or with a legacy configuration method, you must migrate the
configuration before you can use the new wizard to modify it. The recommended
migration method is to use the nsrnmoadmin command, as described in Migrating
a legacy configuration with the nsrnmoadmin command on page 69.
Note: Migration of a proxy backup configuration is not supported. Requirements for using the
nsrnmoadmin command for migration on page 70 describes the requirements and limitations
of migration with the nsrnmoadmin command.
Migration converts legacy configuration files and resources (the nsrnmo script,
RMAN script, NWORA resource file, and Client resource) to the configuration
storage framework used by the new wizard. Migration with the nsrnmoadmin
command does not create a new Client resource; the migration modifies an existing
Client resource, such that you can then use the wizard to modify it.
The migration process stores the following in a hidden attribute in the Client
resource:
32
Environment variable settings extracted from the nsrnmo script. (Any scripting
commands in the nsrnmo script are ignored.)
Introduction
The migration process also sets the following values in the Client resource:
I18N support that is provided by the operating system on the NMO client host.
I18N support that is provided by the NetWorker client and server software.
For example, if NetWorker software does not support non-ASCII data in a specific
NetWorker resource attribute (such as the group name in the Group resource), NMO
cannot support non-ASCII data in that resource attribute. The EMC Information
Protection Software Compatibility Guide and the NetWorker documentation include
more information on the I18N support provided by NetWorker.
Product features
33
Introduction
The format string of the RMAN backup command (unless the nsrnmoadmin -M
or nsrnmoadmin -P command is used for migration of a legacy backup
configuration on Windows)
Usernames in the connection strings to the target database and recovery catalog
Note: Oracle does not recommend the use of non-ASCII text in the Oracle database
usernames. Due to Oracle limitations, ASCII text must be used for the password of the
target database.
Content of output files created by the NMO wizard, such as nsrnmo scripts (for
example, nsrnmo.bat or nsrnmo.sh file) and RMAN scripts
Due to Oracle limitations, ASCII text must be input in the wizard for the following:
ORACLE_HOME path
Net service name of the Oracle target database, recovery catalog, or duplicate
database
The deduplication backup process, nsravtar, on the NMO client generates messages
in English only.
34
Introduction
When NMO I18N support is set up, NMO generates debug messages in English only.
NMO generates error messages in the nmo.messages.raw file in a
language-independent binary form, readable by the nsr_render_log program only.
The nmo.messages.raw file replaces the nmo.messages file used in previous NMO
releases. (The log file does not contain Oracle Server or RMAN errors.)
The NetWorker administration guide provides information on how to use the
nsr_render_log program to read any language-independent binary file, such as
nmo.messages.raw.
The PowerSnap Module documentation provides details on the PowerSnap options
that support non-ASCII values.
Configuring I18N support on page 67 describes how to set up NMO I18N support.
L10N features
NMO L10N is the capability of the NMO software to generate non-ASCII character
and numeric data based on the locale of the user, and output the data to the user
interface. This capability requires the installation of the appropriate NMO language
packs in non-English locales. The non-ASCII data generated by NMO is printed to the
command line or to specific log files or wizard screens.
When NMO I18N is set up, NMO can process and display non-ASCII data that is
passed to it by the operating system, NetWorker software, and Oracle software.
When NMO L10N is set up by also installing the required NMO language packs,
NMO can also generate non-ASCII data, localized according to the user locale. The
non-ASCII data can include text messages, dates, times, and numeric values
displayed in the locale-dependent format.
The EMC Information Protection Software Compatibility Guide on the Powerlink website
provides details on the different languages supported and the operating system,
Oracle Server, and NetWorker software requirements for NMO L10N.
NMO L10N is supported for the following:
L10N support that is provided by the operating system on the NMO client host.
L10N support that is provided by the NetWorker client and server software.
Comments (lines starting with the symbol #) in the nwora.res file and RMAN
scripts
All debug messages, including the messages in the configuration wizard debug
log files and in the log files specified by NSR_DEBUG_FILE and
NSR_SB_DEBUG_FILE
Configure L10N support on page 69 describes how to set up NMO L10N support.
Product features
35
Introduction
Parallelism
Parallelism is a feature that enables NMO backup or restore streams of Oracle data
from several clients, or many Oracle data streams from one client, at the same time.
Different types of configuration settings enable different types of parallelism during
NMO operations:
36
Introduction
For proxy operations, the PowerSnap parameter settings specify the maximum
number of parallel save streams on the proxy client host.
Note: The degree of proxy backup or restore parallelism is not controlled by the allocation
of multiple channels in the RMAN script. Oracle uses only one of the allocated channels for
the proxy backup or restore, unless specific backup options are used.
Policy uniformity
If policy uniformity is enabled, NMO automatically enforces the uniformity of the
browse and retention policies between all the dependent save sets in a scheduled
backup cycle (whether or not save set bundling is enabled). When save set bundling
is also enabled, all the save sets in a bundle receive the same browse and retention
policies.
After NMO performs an incremental scheduled backup, if the browse and retention
policies of the save sets in the backup are longer than the policies of preceding
dependent save sets in the same backup cycle, the NMO program nsrnmostart
changes the policies of all save sets in the cycle to match the longest policy of the new
incremental save sets. NMO modifies the policies recorded in the NetWorker media
database. As a result, backups cannot expire and become recyclable before other
dependent backups from the same backup cycle.
The NMO software does not enforce policy uniformity for a manual backup, except
when a subsequent scheduled backup is dependent on the manual backup, and then
the policies of the manual backup are modified accordingly.
Policy uniformity does not depend on whether save sets are stored on separate
volumes. For example, if parts of a save set bundle are split onto separate volumes, all
the save sets in the bundle still receive the same browse and retention policies.
Configure policy uniformity on page 92 provides information on how to configure
policy uniformity for NMO backups.
Restartable backups
RMAN can back up files that have not been backed up since a specified time. For
example, to continue the backup of a database that was canceled 2 days ago, use the
following command:
backup device type sbt database not backed up since time sysdate-2
RMAN compares the given time in this command with the completion time of the
most recent backup of a datafile to determine if the datafile requires backup. The
appropriate Oracle backup and recovery documentation provides more information.
The following sections provide more information on how to cancel NMO backups:
Product features
37
Introduction
Retention policies
RMAN provides an Oracle retention policy for backups. An Oracle retention policy is
based on the recovery window or redundancy; it is not based on a defined time
period, such as a year. Oracle considers a backup obsolete when it is no longer
required according to the Oracle retention policy setting. Oracle checks the retention
policy of a backup when the report obsolete... or delete obsolete... command is run.
NMO supports the Oracle retention policy with some restrictions, since the
NetWorker server has its own browse and retention policies to specify how long data
is available for recovery. NetWorker browse and retention policies are based on a
user-defined time period. Since the Oracle retention policy is independent from that
of the NetWorker server, and there is no mechanism to synchronize these policies, the
NetWorker and Oracle policies could conflict.
Example 5
Expiring a backup
A NetWorker server might expire an NMO backup that is not yet obsolete in RMAN,
depending on the NetWorker browse and retention policies. Use of NMO cannot
guarantee that the NetWorker server will not expire a backup volume until all the
RMAN backups on that volume have been removed from the RMAN catalog.
To avoid conflicts, perform either of the following:
Disable the Oracle retention policy (and then use only the NetWorker server
policy) with the following command:
configure retention policy to none
If the Recovery Catalog is used, exempt a backup from the retention policy with
one of the following commands:
change backupset...keep until/forever...
backup...keep until/forever...
(If you want to use the Oracle retention policy) Set the NetWorker browse and
retention policies to be long enough that backups are kept on the backup volumes
until the Oracle retention policy makes them obsolete.
Set the NetWorker policies in the NetWorker Client resource for scheduled
backups or through the NSR_SAVESET_BROWSE and
NSR_SAVESET_RETENTION parameters. Configure a Client resource with
NMC on page 87 provides more information on how to set NetWorker policies
for NMO backups.
IMPORTANT
Run the crosscheck command on the NMO backups before running report
obsolete or delete obsolete backups of the device type sbt_tape. This ensures that
backups expired by the NetWorker server are flagged as expired in the RMAN
catalog. As a result, RMAN can correctly identify which backups are not needed
according to the Oracle retention policy.
For example:
1. Run the following command to synchronize the RMAN Catalog and
NetWorker indexes:
crosscheck backup;
2. Run the following command to delete all obsolete backups defined by the
current Oracle retention policy:
delete obsolete;
38
Introduction
During staging operations with NetWorker server release 7.4 and later, if the staging
criteria determine that a particular NMO save set should be staged (migrated) and
the save set is part of a save set bundle, the NetWorker server stages the entire save
set bundle. If the nsrstage command is used to manually stage one or more save sets
from a save set bundle, all the save sets in the bundle are staged.
Note: After a staging operation during which all the save sets in a bundle are staged, the
resulting available space on the staging device might exceed the lower-water mark specified in
the staging policy.
The NetWorker administration guide provides details on how to work with staging
policies and perform automatic and manual staging operations through the
NetWorker server.
NMO scheduled backups and save set bundling on page 39 describes NMO save
set bundling during regular scheduled backups, and how to configure save set
bundling.
If policy uniformity is configured, NMO automatically enforces the uniformity of
browse and retention policies for all the dependent save sets of the same scheduled
backup cycle or same save set bundle, which ensures that incremental backups do not
persist after the backups they depend on have expired.
Other Oracle features on page 44 provides more information on how policy
uniformity relates to save set bundling. Save set bundling and policy uniformity can
be enabled and disabled independently.
NMO scheduled backups and save set bundling
Use the information in the following sections to plan a save set bundling strategy and
enable save set bundling for NMO scheduled backups. Both are performed to
prepare for staging operations with NetWorker server 7.4 and later.
Configure save set bundling on page 91 provides information on how to configure
save set bundling for NMO scheduled backups.
RMAN backup levels and dependencies
An RMAN backup can be either full or incremental:
A full (or stand-alone full) backup includes every used block of the database
objects listed in the RMAN backup script (unused blocks might be skipped). This
type of backup is created when you do not specify a backup level with the RMAN
backup command. A full backup cannot be the parent of a subsequent
incremental backup. (Incremental backups cannot be dependent on a stand-alone
full backup.)
Product features
39
Introduction
A control file, parameter file (or spfile), archived log, or datafile cannot span more
than one backup set.
A control file or parameter file backup cannot span more than one backup piece.
An archived log or datafile backup can span more than one backup piece in a
backup set.
It is possible to determine which backup set contains a specific datafile (by querying
the v$ views in the Oracle database), but not which backup pieces within the backup
set contain the datafile.
An Oracle backup set contains either of the following:
The backup of a control file, parameter file, or archived log, which is always
performed as a full backup.
Note: The backup of a control file, parameter file, or archived log is always placed in its
own save set bundle.
40
Introduction
At the end of a full or level 0 scheduled backup, the NMO software creates a new save
set bundle for the backup set from the backup. If subsequent incremental backups are
performed that are dependent on the level 0 backup, NMO adds their save sets to the
save set bundle from the level 0 backup.
A separate save set bundle is created for each scheduled backup cycle of a particular
Oracle database object, where a backup cycle consists of a full or level 0 backup of the
object and all the subsequent incremental backups that are dependent on the level 0
backup.
A save set bundle contains one of the following:
The save sets from a stand-alone full backup, with no other dependent save sets.
For example, the save sets from the backup of a control file, parameter file, or
archived log (always performed as a full backup) are placed in their own save set
bundle.
The save sets from a level 0 backup of an Oracle object and all subsequent
incremental backups in the same backup cycle of the object.
When an incremental backup occurs and NMO cannot find a preceding dependent
backup in any existing bundles, NMO creates a new save set bundle for the
incremental backup.
Save sets from a manual backup are placed into a save set bundle only if a subsequent
scheduled backup is dependent on them. The manual backup save sets are placed in
the save set bundle at the same time as the dependent save sets from the scheduled
backup.
For save set bundling purposes, you can simultaneously run multiple backup cycles
that back up different objects from the same database, as long as different files are
backed up by the different cycles. For example, one cycle can back up datafiles 1 and
2, while another cycle backs up datafiles 3, 4, and 5 from the same database. The
cycles can also be of different lengths. For example, one cycle can last a week, while
another concurrent cycle lasts several weeks.
Note: The backup copies feature and save set bundling of backup copies are not supported
with NMO scheduled backups. Backup copies created during a manual backup are
independent of each other, and each copy goes to a different NetWorker volume.
If an error occurs during save set bundling, the bundling operation fails but the
scheduled backup can finish successfully. Information about the bundling failure is
printed to the savegrp output and to the debug file specified by NSR_DEBUG_FILE.
How the nsrnmostart program performs save set bundling
The NMO program nsrnmostart automatically places save sets into a save set bundle
at the end of a scheduled backup, before the nwora.res file is backed up. Configure
save set bundling on page 91 provides information on the nwora.res file.
To perform save set bundling, the nsrnmostart program connects to the Oracle
database by attempting to use the login and password from the RMAN script. If a
login and password are not available from the script, the program uses the
ORACLE_SID value from the nsrnmo script to search the nwora.res file for the
NSR_ORACLE_CONNECT_FILE parameter, and uses the connection strings from
the specified connection file. Configure save set bundling on page 91 provides
more details on the requirements of save set bundling.
Product features
41
Introduction
After connecting to the Oracle database, the nsrnmostart program obtains all the
required information about the backups from the Oracle control file (by querying the
v$backup_set, v$backup_piece, and v$backup_datafile tables). The control file can
store only a limited number of backup entries. When the maximum number of entries
is exceeded, old entries in the control file are overwritten by new ones. Save set
bundling is successful only if information in the control file about backed-up save
sets has not been overwritten. The Oracle documentation provides information about
proper maintenance of the control file and how much backup information the control
file can store.
The nsrnmostart program creates a save set bundle for each full or incremental level
0 backup. The program adds the save sets from subsequent incremental backups to
the bundles of the full or level 0 backups they are dependent on.
The name that the nsrnmostart program assigns to a save set bundle is a number
corresponding to the save time of the oldest save set in the bundle. NMO provides the
NetWorker server with the list of save sets contained in each save set bundle.
After a scheduled backup, the NetWorker server stores the save set bundle name and
the list of save sets it contains in the media database. You can view the bundle
information by using the mminfo command, as described in Save set bundling
information in the media database on page 43.
Example 6
NetWorker cannot simultaneously stage all the save sets from a save set bundle if
some of the save sets were backed up to separate volumes. NetWorker
simultaneously stages save sets only if they are located on the same staging
volume. Example 8 on page 43 provides more information.
To ensure the proper staging of all the save sets from a save set bundle, do not
split the backup between different staging volumes. If required, split the backup
into different backup cycles, with each cycle going to a separate volume.
NetWorker staging policies must not cause the save sets of an NMO backup cycle
to be staged before the cycle is complete. For example, if a one-week NMO cycle
starts on Sunday, the staging policy must not cause the partially complete save set
bundle to be staged before the final backup of the cycle occurs on Saturday.
To prevent a staging operation from splitting an NMO backup cycle, adjust the
NetWorker staging policy accordingly. For example, adjust the policy so that
older save sets are staged before new ones, or adjust the high-water and
low-water marks.
The NetWorker administration guide provides details on how to work with staging
policies and perform automatic and manual staging operations through the
NetWorker server.
42
Introduction
The mminfo -r command can display the name of the bundle associated with a
save set. For example, the following command displays a list of all save sets and
their bundles:
mminfo -a -r "ssid,ssbundle"
The mminfo -q command can display all the save sets in a specific bundle. For
example, the following command displays all the save sets in the bundle named
12983479182:
mminfo -a -q "ssbundle=12983479182"
The NetWorker command reference guide and the UNIX man pages provide more
information on the mminfo command and its available options.
Examples of save set bundles and staging
The following examples illustrate different aspects of save set bundling, and how
splitting the save set bundles across volumes can affect staging operations.
Example 7
Two save set bundles are created by separate level 0 backups of files A and B. Then a
new backup set is created by a level 1 backup of both files A and B. Since the new
backup set is dependent on both of the preceding level 0 backups, NMO combines all
three backups into the same save set bundle.
If the original file A backup has the oldest backup time, NMO places the new backup
set (from the level 1 backup) into the save set bundle of the (level 0) file A backup.
NMO then moves the original (level 0) file B backup into the save set bundle with the
other two backups. This method of combining existing bundles into a new save set
bundle is known as a save set bundle join.
Example 8
In both of the following cases, a save set bundle is split across multiple volumes. The
parts of the save set bundle on different volumes must be staged separately by the
NetWorker server:
A backup uses multiple channels so the backup set spans multiple volumes. All
the save sets belong to the same backup set and save set bundle, but parts of the
bundle are stored on different volumes. During staging, only the save sets on the
same volume can be staged together.
Product features
43
Introduction
Example 9
The Oracle Recovery Manager documentation provides a complete list of the RMAN
features.
When using Oracle RMAN features with NMO, consider the following:
A flash recovery area stores and manages files related to the recovery of a
particular database.
To back up RMAN disk backups, control file autobackups, and archived redo
logs from the flash recovery area to NetWorker volumes:
a. Allocate or configure one or more channels with the sbt_tape device type.
b. Back up the files with one of the following RMAN commands:
backup recovery area
backup recovery files
Note: Whether or not a flash recovery area is enabled, the backup recovery files
command can be used to perform the backup.
44
Introduction
If multiple channels are used for an RMAN backup command and one of the
channels fails, Oracle fails over to another channel to continue the backup job.
For example, if two channels are configured with different NetWorker volume
pools and one of the channels fails over to the other channel during a backup, the
entire backup goes to the volumes in the pool of that remaining channel.
Before using the backup command with the duration...minimize load option,
consider:
The minimize load option might impact the tape streaming since the transfer
rate of data sent by RMAN might be slow with this option, depending on the
duration value.
Note: This is not a concern if you use the NetWorker backup to disk feature.
Starting with release 10.1, RMAN does not print database connection strings
(user/password@Netservicename) to the session output. As a result, the parameter
NSR_RMAN_OUTPUT is not required (to suppress the connection strings in the
log files) for an RMAN scheduled backup.
Recovery catalog enhancements, such as virtual private catalogs and the import
and merging of recovery catalogs
Multisection or intrafile backup and validation, with the backup of a single large
datafile over multiple channels
Improved block media recovery, with the blockrecover command being replaced
by the recover...block command
Product features
45
Introduction
Oracle Enterprise Manager enhancements, with new interfaces for the Data
Recovery Advisor
To enable NMO support of two of the Oracle11g features, Data Recovery Advisor
and archival backup, you must perform the additional configuration procedures
described in Data Recovery Advisor on page 46 and Archival backup feature on
page 46.
The appropriate Oracle documentation provides more information on the Oracle11g
features.
Data Recovery Advisor
The Oracle Data Recovery Advisor is a new tool in Oracle11g. Integrated with RMAN
and Oracle Enterprise Manager (OEM), the tool enables a DBA to diagnose and repair
database failures.
Before you can use the Data Recovery Advisor to invoke an RMAN restore script that
involves NMO to repair a database failure, automatic channels must be configured to
specify at least the mandatory parameters NSR_SERVER and NSR_CLIENT.
Note: The NSR_SERVER and NSR_CLIENT parameters are the minimum parameters required
to perform a restore. Other NMO parameters may also be specified for the automatic channel
configuration.
To enable the use of Data Recovery Advisor with Oracle11g and NMO:
If automatic channels have not been configured for NMO backups, use the
following commands to ensure the basic automatic channel configuration:
configure channel device type sbt_tape parms
ENV=(NSR_SERVER=NetWorker_server_name,
NSR_CLIENT=NMO_client_name);
configure channel device type 'sbt_tape' parallelism
number_of_restore_channels;
46
Introduction
NetWorker software
The NetWorker software comprises a high-capacity, easy-to-use data storage
management solution that protects and helps manage data across an entire network.
The NetWorker software simplifies the storage management process and reduces the
administrative burden by automating and centralizing data storage operations.
The NetWorker software enables a user to:
NetWorker client/server technology uses the network remote procedure call (RPC)
protocol to back up data. The NetWorker client software consists of client-side
services and user interface programs.
The NetWorker server software consists of several server-side services and programs
that:
Maintain an online client file index and online media database, which together
comprise the online indexes on the NetWorker server
During a backup, the NetWorker server makes an entry in the online client file index
and records the location of the data in the online media database. These entries
provide recovery information required for all backed-up data.
47
Introduction
After a scheduled backup, the NetWorker server sends a record of the bootstrap file to
the default printer. This is a printed record of the dates, locations, and save set ID
numbers for the servers online indexes that are required for restoring data. Keep the
bootstrap printout on file as a quick reference in the event of a disaster, such as a disk
crash or server failure:
NMO software
NetWorker Module for Oracle (NMO) software is an add-on module for the
NetWorker server that enables you to perform the following tasks:
Capability to integrate database and file system backups, to relieve the burden of
backup from the database administrator while allowing the administrator to
retain control of the restore process.
Together with the NetWorker server, NMO augments the backup and recovery
system provided by the Oracle Server and provides a storage management solution
that addresses the need for cross-platform support of enterprise applications.
Proxy backups and restores of Oracle database files residing on specific types of
primary storage devices are supported. These proxy operations are performed by
NMO, with the NetWorker server and the appropriate NetWorker PowerSnap
Module software.
The NetWorker Module for Oracle installation guide provides information on how to
install the NMO software.
48
Introduction
During a proxy backup, the Oracle data can optionally be copied from the snapshot to
a NetWorker storage device. The data is copied to the secondary storage by either the
Oracle Server host or a proxy client host that is separate from the Oracle Server host.
The following sources provide information on how to configure and run proxy
backups and restores with the NMO and PowerSnap Module software:
The EMC Information Protection Software Compatibility Guide on the Powerlink website
provides a complete list of supported PowerSnap Modules.
Oracle Server
NetWorker server
NetWorker client
Figure 1 on page 50 illustrates the architecture of the regular Oracle backup and
recovery system, and shows the functional relationship between the NetWorker and
Oracle software components. The NetWorker Module for Oracle media management
library (MML) is integrated with the Oracle Server during the NMO installation on
the Oracle Server host. The NetWorker Management Console program (used to
configure the NetWorker resources) and the Oracle Enterprise Manager (OEM)
Backup Manager can be optionally located on a separate platform, referred to as the
GUI console.
49
Introduction
GUI console
NetWorker
server
Oracle
database files
OEM
Backup
Manager
RMAN
Oracle
Server
Recovery
Catalog
NetWorker
Module
for Oracle
MML
Storage
medium
NetWorker
client
NetWorker
Management Console
NetWorker
server
GEN-000170
Figure 1
50
Introduction
Image copies
Proxy copies
The Recovery Catalog is maintained by the RMAN utility. This utility uses the
catalog information or the database control file to determine how to perform
requested backup and restore operations. Store the Recovery Catalog in the dedicated
Recovery Catalog database.
The Oracle Recovery Manager documentation provides more information on the
Recovery Catalog, including the implications of not using it for backups and restores.
NMO components
Table 1 on page 51 lists the components that are installed on the NMO client host
during the NMO software installation. Unless specified otherwise, the files are
located in the same directory as the NetWorker client software.
Table 1
Name on UNIX
Name on Windows
Description
fdiff.jar
nwora.jar
nwora_res.jar
fdiff.jar
nwora.jar
nwora_res.jar
Plug-in jar files for the NMO backup and recovery configuration wizards.
libcommonssl.7.5.build#.so
libnwora.xx
In /usr/lib on UNIX only. The main NMO library (known as Media Management Library in
Oracle documentation) that is loaded by the Oracle backup or restore process.
nsrnmo
nsrnmo.bat
The nsrnmo script that contains parameter settings for a particular scheduled backup. The
script is only used for a scheduled backup that has been configured through NMC (the legacy
configuration method without the wizard).
In /etc on UNIX only. A sample template for the nsrnmo script. You should copy and customize
this template, and save the original file in /etc.
nsrnmo.sh
nsrnmoadmin
nsrnmoadmin.exe
The program that is used either to create resource settings in the NWORA resource file, or to
migrate legacy backup configurations to the new format supported by the configuration wizard.
nsrnmodrpostcmd
nsrnmodrpostcmd.exe
A sample postcommand script that can be customized to back up specific files at the end of a
scheduled backup, in preparation for disaster recovery.
nsrnmoinfo
nsrnmoinfo.exe
The program that determines the NetWorker volumes required to restore specified Oracle
backup pieces from NMO backups.
nsrnmoprobe
nsrnmoprobe.exe
The program that probes for the number of generated Oracle logs as a condition that triggers
probe-based backups.
NMO components
51
Introduction
Table 1
Name on UNIX
Name on Windows
Description
nsrnmostart
nsrnmostart.exe
The program that invokes a scheduled backup on the Oracle Server, launching RMAN by
passing arguments to the Oracle utility. The program optionally runs precommand and
postcommand scripts.
nsroraclecat
nsroraclecat.exe
Not available on Linux Itanium, Solaris AMD64/EM64T, or Windows Itanium (platforms that do
not support proxy backups). The program that is used to remove RMAN catalog entries during
automatic catalog synchronization for proxy backups.
nsrorara
nsrorara.exe
The program that performs operations on behalf of the NMO configuration wizard on the local
or remote NMO host.
nsrsbtcn.exe
orasbt.dll
On Windows only. The orasbt.dll file is the main NMO library (known as Media Management
Library in Oracle documentation) that is loaded by the Oracle backup or restore thread, and it
uses nsrsbtcn.exe to perform any corresponding NetWorker operations.
RMAN establishes connections with the target database. Each RMAN channel starts
an Oracle Server backup session that performs the backup. During the backup, the
following occurs:
1. The Oracle Server backup sessions read the datafile, control file, or archived redo
log being backed up, and then write it to the NetWorker server through the MML.
2. The NetWorker server stores the Oracle data to the appropriate backup storage
device.
At the end of the Oracle backup, the NetWorker server updates the online client and
media indexes with information about the backup media used and the Oracle data it
contains.
52
Introduction
Figure 2 on page 54 shows how the Oracle Server, NetWorker server, and NMO
processes interact during a regular scheduled NMO backup that was configured
through the legacy method (without the wizard).
53
Introduction
NetWorker server
Media database
tracking
information
Oracle
process
(channel)
NetWorker
Module
for Oracle
MML
Storage
medium
nsrindexd
nsrmmdbd
NetWorker Module
elements
data
nsrmmd
rman
interprocess
communication
savefs
nsrnmostart
nsrnmo
savegrp
nsrd
nsrexecd
GEN-001110
Figure 2
54
Introduction
3. The Oracle Server backup sessions send the backup data to the NetWorker media
service, nsrmmd, to store on the appropriate backup volumes.
4. Tracking information is stored in the NetWorker online indexes:
The nsrmmd service records tracking information in the NetWorker media
database by using the nsrmmdbd service.
The Oracle backup sessions send tracking information to the NetWorker client
file index by using the nsrindexd service.
Figure 3 on page 55 shows how the Oracle Server, NetWorker server, and NMO
processes interact during a regular manual NMO backup.
Oracle Server
(NetWorker client)
Backup pieces
RMAN
Oracle
process
(channel)
NetWorker
Module
for Oracle
MML
Storage medium
NetWorker server
Media database
tracking
information
nsrindexd
nsrmmdbd
data
nsrmmd
NetWorker
Module
element
nsrexecd
interprocess
communication
nsrd
GEN-000171
Figure 3
55
Introduction
3. The Oracle Server backup session contacts the main NetWorker service, nsrd, to
obtain the required authorization and the identifier of the nsrmmd process that
manages the requested backup device on the NetWorker server or storage node.
4. The Oracle Server backup session sends the backup data in the NetWorker save
set format to the nsravtar process.
5. The nsravtar process applies deduplication logic to the backup data by using
information in a local cache or by contacting the Avamar server, and sends the
unique data blocks to the Avamar server (NetWorker deduplication node).
6. The nsravtar process sends a hash ID (one hash ID per save set) to the Oracle
Server backup session.
7. The Oracle Server backup session sends the hash ID in save set format to the
NetWorker media service, nsrmmd, to store on the NetWorker backup device.
8. Tracking information is stored in the NetWorker online indexes:
The nsrmmd service records tracking information in the NetWorker media
database by using the nsrmmdbd service. The media database entry contains
extended attributes that identify the backup as a deduplication backup, as
described in Deduplication backup information in NetWorker indexes on
page 115.
The Oracle backup session sends tracking information to the NetWorker client
file index by using the nsrindexd service.
Figure 4 on page 57 shows how the Avamar server, NetWorker, and NMO processes
interact during a deduplication NMO backup. In the figure, the thickness of the data
arrows indicates the amount of data passed between processes:
56
All the data being backed up is passed between the Oracle Server backup session
and nsravtar process.
Hash IDs and new data blocks (never backed up before by the Avamar server) are
passed between the nsravtar process and Avamar server.
A single hash ID for the entire NMO save set is passed between the Oracle Server
backup session and NetWorker storage node.
Introduction
NetWorker
server
NetWorker
storage node
Hash ID
NMO client
NetWorker
deduplication node
(Avamar server)
Oracle Server
backup session
with NMO MML
NetWorker client /
utility node
acle
Oracle
data /
hash ID
GSAN
Node 1
nsravtar
Node 2
Deduplicated
data / hash ID
GEN-001111
Figure 4
The RMAN utility starts Oracle Server sessions on the target database. These Oracle
Server sessions initiate the restore by calling NMO media management library
(MML) software routines.
Note: Deduplication restore processes on page 58 provides information specifically for a
deduplication restore.
57
Introduction
4. The nsrmmd service calls the media database service, nsrmmdbd, to determine
which media contains the requested save set and issue a mount request.
5. The nsrmmd service reads the appropriate backup volumes and passes the data
to the Oracle sessions through the NMO MML.
6. The Oracle Server sessions write the data to the disk.
Figure 5 on page 58 shows how the Oracle Server, NetWorker server, and NMO
processes interact during a regular NMO restore.
Oracle Server
(NetWorker client)
Backup pieces
Storage
medium
NetWorker server
Media database
RMAN
tracking
information
Oracle
process
(channel)
NetWorker
Module
for Oracle
MML
nsrmmdbd
nsrindexd
NetWorker Module
element
data
nsrmmd
nsrexecd
interprocess
communication
nsrd
GEN-000173
Figure 5
Once RMAN has restored the required files from the backup volumes, a database
administrator can complete the standard Oracle database recovery.
58
Introduction
5. The nsrmmd service on the NetWorker server calls the media database service,
nsrmmdbd, to determine which media contains the requested save set and issue a
mount request.
6. The nsrmmd service reads the appropriate backup volumes and passes the data
(hash ID) to the Oracle Server session.
7. The Oracle Server session passes the hash ID to the nsravtar process.
8. The nsravtar process retrieves the data corresponding to the hash ID from either
the primary Avamar server or the replication Avamar server, and sends the data
to the Oracle Server session.
9. The Oracle Server session writes the data to the disk.
59
Introduction
60
2
Software
Configuration
Configuration roadmap................................................................................................
Verify the Oracle Server configuration.......................................................................
Verify the NetWorker resources ..................................................................................
Configuring I18N support ...........................................................................................
Configure L10N support ..............................................................................................
Migrating a legacy configuration with the nsrnmoadmin command ...................
Configuring a backup with the NMC wizard...........................................................
Configuring a backup with the NMC legacy method .............................................
Configuring a deduplication backup .........................................................................
Configuring a probe-based backup ............................................................................
Software Configuration
62
63
63
67
69
69
72
75
93
97
61
Software Configuration
Configuration roadmap
The Oracle Server and NetWorker server must be properly configured before the
NetWorker Module for Oracle (NMO) software can be used for backup and restore
operations.
Before configuring the Oracle Server and NetWorker server, ensure that the NMO
software is installed on the Oracle Server host according to the instructions in the
NetWorker Module for Oracle installation guide.
To perform specific configuration procedures, you can use either of the following
through NetWorker Management Console (NMC):
62
Software Configuration
Description
Name
Parallelism
Specifies the maximum number of backup save streams that the NetWorker software allows
to arrive concurrently at the server. The NetWorker server edition determines the maximum
parallelism value. When multiple data streams are backed up simultaneously, the efficiency of
the storage devices is increased.
Administrator
Specifies users with NetWorker Administrator privileges. The initial default setting of the
attribute is root@hostname on UNIX and Administrators@hostname on Windows, where
hostname is the NetWorker server hostname. Specify the required NetWorker privileges on
page 64 provides more information.
Datazone pass
phrase
Specifies the key or pass phrase to use for AES encryption of Oracle data during an NMO
backup. The pass phrase is required to restore the Oracle data from the backup.
NSR_AES_ENCRYPTION on page 201 provides more information.
63
Software Configuration
The NetWorker server online help and the NetWorker administration guide provide
more information on how to configure a NetWorker Server resource and its
attributes.
Specify the required NetWorker privileges
Certain NMO operations require specific NetWorker privileges. The NetWorker
privileges are specified through the User Group resource. NetWorker user group
privileges on page 64 provides more information.
One NMO operation that requires special privileges is deletion. NMO attempts to
remove an entry from the NetWorker index in the following cases:
Note: If the Oracle user is not granted the required NetWorker privileges in these cases, NMO
fails to remove the backup save set entries from the NetWorker index. However, RMAN might
remove the corresponding entries from the RMAN catalog, which would leave the NetWorker
index and RMAN catalog unsynchronized. To resynchronize the index and catalog, issue the
appropriate NetWorker media management command to manually remove the inconsistent
save set entries from the NetWorker index.
To enable NMO to remove an entry from the NetWorker index, ensure that the
Oracle user has the required NetWorker privileges. Verify that the required user
group privileges exist according to NetWorker user group privileges on page 64.
Note: The privileges associated with the Users group can be customized to fit the requirements
of the NetWorker users in the group. The privileges associated with the Administrators group
cannot be changed.
By default, the NetWorker server assigns the following privileges to all users:
64
Monitor NetWorker
Software Configuration
The default user group configurations are sufficient for RMAN backup, restore, and
crosscheck operations that use NMO. If the default user group configurations are
changed, ensure that the required privileges are assigned for the operations.
Verify that the required user group privileges exist for the NMO operations, as
described in Table 3 on page 65. The NetWorker administration guide provides
information on how to modify existing privileges.
Note: Proxy backups and restores require the same privileges as regular Oracle backups and
restores, plus the privileges required by the PowerSnap Module. The NetWorker PowerSnap
Module documentation provides more information on the required privileges.
Table 3
Operation
Operating system user that performs operation Required user group privileges
Configure NetWorker
RMAN crosscheck
On UNIX:
If Net service is used, it is the operating system user that starts the Net service.
If Net service is not used, it is the operating system user that runs RMAN.
In the case of a scheduled backup, the operating system user is root on UNIX
and system on Microsoft Windows.
On Windows, the operating system user that runs the Oracle service
(OracleServiceoracle_sid).
IMPORTANT
If the correct user group privileges are not assigned, an Oracle backup or restore
fails with an error message that indicates the required user group privileges. The
NetWorker administration guide provides more information on NetWorker user
groups and setting user group privileges.
65
Software Configuration
IMPORTANT
For scheduled NMO backups, the NetWorker backup levels that appear in the
Schedule resource do not determine the NMO backup levels. The level of the
NMO backup must be specified as either full or incremental in the RMAN backup
script. The backup level is determined by the level in the RMAN script only.
You must configure a Schedule resource through the legacy method with NMC, as
described in Configure a Schedule resource with NMC on page 87.
66
Software Configuration
Firewall support
The NMO software provides firewall support. The ports that the NMO software uses
for the firewall depend on the corresponding ports configured for the NetWorker
server.
To configure the firewall that the NMO software uses, follow the firewall
configuration instructions in the NetWorker administration guide for the particular
NetWorker server platform.
67
Software Configuration
The Oracle software provides the required National Language Support (NLS) or
Globalization support, and the Oracle database is configured with the required
non-ASCII character set. The Oracle Globalization Support documentation
provides details.
For I18N support during proxy operations, a supported release of the PowerSnap
Module is installed and configured, as described in the NetWorker Module for
Oracle release notes.
2. Set the environment variable NLS_LANG to the character set supported by the
operating system and Oracle database, and then restart the Oracle Server.
The Oracle Globalization Support documentation provides details on the
NLS_LANG variable.
For example, to ensure that Oracle properly returns Japanese text in a Japanese
locale, set NLS_LANG as follows:
export NLS_LANG=JAPANESE_JAPAN.JA16EUC
% lsnrctl stop
% lsnrctl start
% sqlplus /nolog
SQL*Plus: Release 10.1.0.2.0 - Production on Thu Apr 26 15:12:03
Copyright (c) 1982, 2004, Oracle. All rights reserved.
SQL> connect sys/oracle as sysdba;
68
Software Configuration
SQL> shutdown;
SQL> startup;
SQL> quit;
3. If you do not configure a scheduled backup with the configuration wizard, set the
NLS_LANG parameter in the nsrnmo script to the same value as the environment
variable NLS_LANG.
For example, in a Japanese locale, set NLS_LANG in the nsrnmo script as follows:
NLS_LANG=JAPANESE_JAPAN.JA16EUC
Note: If you configure the scheduled backup with the configuration wizard, you can set
NLS_LANG on a wizard screen. The wizard autopopulates the NLS_LANG field if
NLS_LANG is set in the NWORA resource file.
To configure NMO L10N support, enable the locale by installing the appropriate
NMO language pack for the user locale on the NMO client host. Each supported
language has its own language pack.
The NetWorker Module for Oracle installation guide provides details on how to
install a supported NMO language pack on a UNIX or Windows system.
69
Software Configuration
The RMAN script contains a single valid value for each of the following:
Target database username
Password of the target database user
Net service (instance) name
The RMAN script contains correct syntax for the following commands:
allocate channel
backup
connect
release channel
send
The RMAN script does not contain any of the following commands:
@
allocate channel for maintenance
configure
proxy
Note: Migration of a proxy backup configuration is not supported.
The RMAN script on Microsoft Windows does not include non-ASCII characters.
You have all of the NetWorker privileges needed to query and update the Client
resources on a NetWorker server, as described in Table 3 on page 65. The
NetWorker documentation provides information on the required user group
privileges.
70
Software Configuration
for the client by using NMC to edit the resource. The NetWorker
administration guide provides details on editing the Lockbox resource in the
section on lockbox password management.
When you use nsrnmoadmin in noninteractive mode (with the -Y option), the
migration does not prompt for any input. After the migration, you must add
the usernames to the NetWorker Lockbox resource for all the users that will
use the wizard to modify the configuration.
IMPORTANT
If you migrate the backup configuration of a cluster virtual client, you must do one
of the following to enable scheduled backups of the client:
- During the migration, when nsrnmoadmin prompts for names of wizard users to
add to the Lockbox resource, specify the name system@physical_hostname
(Windows) or root@physical_hostname (UNIX).
- After the migration, use NMC to edit the Lockbox resource for the cluster virtual
client, and add the name system@physical_hostname (Windows) or
root@physical_hostname (UNIX) to the resource.
The command user must meet the migration requirements listed in Table 3 on
page 65.
Windows 2008 and Windows Vista requirements for the nsrnmoadmin command
on page 189 provides details for Windows 2008 and Windows Vista systems.
The nsrnmoadmin command syntax and options are as follows:
nsrnmoadmin -M -s server_name [-c client_name] [-g group_name]
[-N save_set_name] [-Y]
nsrnmoadmin -P -s server_name [-c client_name] [-g group_name]
[-N save_set_name]
71
Software Configuration
Option
Description
-M
Specifies the migrate option. The nsrnmoadmin program performs the following:
1. Queries the NetWorker server resource database to locate all of the Client resources that match the values specified by the
-c, -g, -N, and -s options.
2. Migrates each legacy configuration (the nsrnmo script, RMAN script, NWORA resource file, Client resource) to the
configuration format that is supported by the new NMO wizard.
Note: The nsrnmoadmin program can only migrate a configuration that physically resides on the host where the nsrnmoadmin
command is typed. To migrate the Client resources for different physical hosts, you must run the nsrnmoadmin program on
each physical host, or write a script to automate the process.
-P
Specifies the probe option. The nsrnmoadmin program performs a probe to query the NetWorker server resource database and
locate all of the Client resources that match the values specified by the -c, -g, -N, and -s options, and prints the results to
standard output. The program does not actually migrate any legacy configurations.
Note: The nsrnmoadmin program can only probe configurations that physically reside on the host where the nsrnmoadmin
command is typed. To probe the Client resources created for different physical hosts, you must run the nsrnmoadmin program
on each physical host.
-c client_name
Optional. Specifies the hostname of the NetWorker client to be configured. Typically, this option specifies a virtual client in a
cluster. The default value is the hostname of the local physical client.
-g group_name
Optional. Specifies the name of the NetWorker group for the query operation. If this option is not specified, then a group name is
not included in the criteria for the query of the server resource database.
-N save_set_name
Optional. Specifies the value set in the Save Set attribute of the Client resource. If this option is not specified, then a save set
name is not included in the criteria for the query of the server resource database.
-s server_name
Mandatory. Specifies the hostname of the NetWorker server that backs up the client being configured.
-Y
Optional. Specifies non-interactive mode, which causes the nsrnmoadmin program to proceed with a migration without
prompting for confirmation. If this option is not specified, the nsrnmoadmin program displays all of the fields to be updated in the
Client resource and requests confirmation to proceed with the migration.
72
Software Configuration
The NMC user that starts the wizard (the wizard user) has the Configure
NetWorker privileges on the NetWorker server where the configuration is
created.
Communication between the NMC server, NetWorker server, and NMO client
uses nsrauth authentication. The NetWorker documentation provides any
requirements for nsrauth authentication.
The required NetWorker releases are installed on the NMC server, NetWorker
server, and NMO client hosts, as described in the NetWorker Module for Oracle
release notes.
73
Software Configuration
IMPORTANT
When you use the wizard to configure a cluster virtual client, the wizard attempts
to perform all of the additional settings required for the cluster environment,
including the following:
- Creating the required Client resources.
- Adding the required ACL entries to the Lockbox resource, for the physical hosts
provided in the Remote Access field on the NetWorker Client Properties screen of
the wizard.
- Setting the NSR_CLIENT parameter.
- Adding the -c virtual_clientname option to the Backup Command attribute in the
Client resource of the virtual client.
In the Client resource of the virtual client, ensure that the Remote Access attribute
is set with user@physical_hostname for each of the physical hosts of the cluster;
otherwise, the backup might fail.
74
Software Configuration
The following RMAN script is for a manual backup of an entire Oracle database to
the volume pool MondayFulls of the (remote) NetWorker server mars.emc.com:
run {
allocate channel t1 type SBT_TAPE;
allocate channel t2 type SBT_TAPE;
send NSR_ENV=(NSR_SERVER=mars.emc.com,
NSR_DATA_VOLUME_POOL=MondayFulls);
backup full filesperset 4 format FULL_%d_%U (database);
75
Software Configuration
To specify a Media Management (in this case, NMO) device, set the type option in the
allocate channel command to SBT_TAPE.
If a device is allocated by using the allocate channel t1 type disk command (with
Oracle correctly configured and NMO uninstalled), backups can be directed to disk
files through Oracles backup implementation.
In the preceding RMAN backup script, the format string FULL_%d_%U specifies the
name of each backup piece. This name can be anything, provided that each backup
piece has a unique name on the NetWorker server. Substitution variables, such as %d
and %U, can be used to guarantee unique names:
A format string such as FULL or FULL_%d will not generate unique names.
Similarly, the format string FULL_%U will not generate unique names for two
databases that are being backed up to the same NetWorker server.
IMPORTANT
If a backup piece name is not unique, the Oracle backup fails.
During a manual backup, the prefix RMAN: automatically precedes the backup piece
name in the NetWorker media database. For example, if the backup piece name
specified in the RMAN script is accounts_data_file, the manual backup records the
save set name as RMAN:accounts_data_file in the media database. The mminfo
command displays the save set name in this form.
The following sources provide more information:
Example 11
The following RMAN script performs a nonproxy backup of the Oracle database to
the NetWorker server mars.emc.com by using 256-bit AES encryption, as specified by
the NSR_AES_ENCRYPTION parameter setting:
run {
allocate channel t1 type SBT_TAPE;
send NSR_ENV=(NSR_SERVER=mars.emc.com, NSR_AES_ENCRYPTION=TRUE);
backup full filesperset 4 format FULL_%d_%U (database);
release channel t1;
}
The AES encryption uses the key or pass phrase that is set in the Datazone pass
phrase attribute of the NetWorker Server resource. NSR_AES_ENCRYPTION on
page 201 provides more information.
76
Software Configuration
IMPORTANT
Keep a record of all pass phrases used for 256-bit AES encryption. Be careful when
you change the pass phrase on the NetWorker server. If the pass phrase on the
server is changed and you cannot remember the pass phrase used for an NMO
backup, the encrypted data cannot be recovered. The NetWorker administration
guide provides more information on pass phrases.
Example 17 on page 122 shows a sample Oracle restore of an AES encrypted backup,
with the NSR_ENCRYPTION_PHRASES parameter that specifies the original pass
phrase that was used for the backup.
IMPORTANT
For scheduled backups (both regular and proxy backups), do not include send as
part of the allocate channel command. The send command must be separate.
For example, NMO does not support the following for scheduled backups:
allocate channel t1 type SBT_TAPE send
NSR_ENV=(NSR_SERVER=mars.emc.com);
With automatic channel allocation, specifying the send command before the backup
or restore command causes the following error:
RMAN-06422: no channels found for SEND command
The following RMAN script is for a scheduled backup of an entire Oracle database to
the volume pool MondayFulls. The Recovery Catalog is used in this case:
connect target target_user/target_passwd@target_Netservicename;
connect rcvcat rcvcat_user/rcvcat_passwd@rcvcat_Netservicename;
run {
set command id to xxx;
allocate channel t1 type SBT_TAPE;
allocate channel t2 type SBT_TAPE;
send NSR_ENV=(NSR_DATA_VOLUME_POOL=MondayFulls);
backup full filesperset 4
format FULL_%d_%U
(database);
release channel t1;
release channel t2;
}
If automatic channel allocation and persistent settings are used, a scheduled RMAN
backup script must still be created and contain the following commands:
connect target
backup
77
Software Configuration
target_user is the user with SYSDBA privileges for the target database.
target_Netservicename is the Net service name of the target database. This name is
mandatory in the connect target command.
A password file must be used for the target database. To use the password file, the
orapwd utility might need to be used and the REMOTE_LOGIN_PASSWORDFILE
parameter set to exclusive in the initoracle_sid.ora file. The appropriate Oracle
documentation provides more information.
Notes:
Since each scheduled backup RMAN script requires a connect target command,
each Oracle instance requires a separate scheduled backup RMAN script.
In the connect target command, do not use the value internal for target_user or the
value oracle for target_passwd.
To enable the scheduled backup to be canceled, the scheduled Oracle backup script
must include set command id to xxx (where xxx can be any string of characters
enclosed in single quotes). Cancel a scheduled backup on page 111 provides more
information on how to cancel a scheduled backup.
The remainder of the scheduled backup script in Example 12 on page 77, starting
with the first allocate channel command, is similar to the manual backup script in
Example 10 on page 75 except that the NSR_SERVER parameter setting is not
included.
IMPORTANT
Do not set the parameters NSR_SERVER or NSR_GROUP in a scheduled RMAN
backup script. NMO sets these two parameters to the values specified in the Client
resource for the scheduled Oracle backup, and these values cannot be overridden.
To have the scheduled backup automatically use a volume pool, the backup group
can be specified in the Pool resource. The scheduled backup uses that pool unless the
parameter NSR_DATA_VOLUME_POOL is set in the RMAN script. Then that
parameters setting takes precedence over any pool associated with the scheduled
backup group.
If NSR_DATA_VOLUME_POOL is set in the RMAN script to a pool different from
the one associated with the backup group, the scheduled backup uses the
78
Software Configuration
where:
group_name is the name of the scheduled backup group as specified in the Client
resource.
A sample nsrnmo script in the same directory as the NetWorker executables. The
sample script filenames are:
nsrnmo on UNIX
nsrnmo.bat on Windows
A template of the script in the /etc/nsrnmo.sh file on UNIX. Do not modify this
file.
Note: On Windows, save a copy of the original nsrnmo.bat file before modifying it.
Editing the nsrnmo.bat file on Windows 2008 or Windows Vista on page 80 provides
specific requirements for Windows 2008 and Windows Vista systems.
Multiple versions of the nsrnmo script can be created (for example, one for each
Oracle instance) on the same Oracle Server host. Each version of the script must have
a unique name, starting with the letters nsr or save. On Windows, the name must also
end in .bat or .cmd.
79
Software Configuration
A nsrnmo script from a previous NMO release works with NMO release 5.0.
However, the nsrnmo script installed with NMO release 5.0 might include new
parameter settings not found in the script from the previous release.
To facilitate the correct reporting of scheduled backup save sets for a UNIX NMO
client within the group details window of the NetWorker Management Console
(NMC), specify the following shell within the nsrnmo script on UNIX:
/bin/bash, if it exists on the UNIX client
/bin/ksh, if /bin/bash does not exist on the UNIX client
80
Software Configuration
The nsrnmo script contains only the parameters required on the particular system
where the script is installed. The following parameters appear in the nsrnmo script
on specific UNIX systems only:
Follow the instructions in the Oracle installation guide to determine which of the
parameters (LD_LIBRARY_PATH, LIBPATH, SHLIB_PATH) to set on a particular
operating system and to what value.
The ORACLE_HOME parameter is mandatory for each scheduled backup, and must
be set in the nsrnmo script. The other parameters in the nsrnmo script are optional,
and can be left undefined in the script, if preferred.
Note: For other parameters to be in effect during a scheduled backup, lines must be added in
the nsrnmo script to define and export the parameters. The use of either the UNIX setenv
command or Windows set command to set the parameters has no effect.
The following sections describe the parameters that can be set in the nsrnmo script
for scheduled backups. The comments in the nsrnmo script file provide details on the
parameters:
ORACLE_HOME on page 81
LD_LIBRARY_PATH on page 82
LIBPATH on page 82
SHLIB_PATH on page 82
NSR_RMAN_ARGUMENTS on page 82
NSR_SB_DEBUG_FILE on page 83
ORACLE_SID on page 83
ORACLE_USER on page 83
PRECMD on page 84
POSTCMD on page 85
TNS_ADMIN on page 86
ORACLE_HOME
This parameter is mandatory for each scheduled backup. Set ORACLE_HOME in the
nsrnmo script file to the home directory of the Oracle Server installation. The RMAN
executable, rman, must be located in the subdirectory bin of $ORACLE_HOME.
For example, if the Oracle Server installation is located in the directory
/disk3/oracle/app/oracle/product/10.0, ORACLE_HOME must be set in the
nsrnmo script as follows:
ORACLE_HOME=/disk3/oracle/app/oracle/product/10.0
81
Software Configuration
LD_LIBRARY_PATH
This parameter is optional for a scheduled backup. Set LD_LIBRARY_PATH in the
nsrnmo script file to the pathname of the directory that contains the Oracle libraries,
typically $ORACLE_HOME/lib or $ORACLE_HOME/lib64.
For example, if the Oracle libraries are located in the directory
/disk3/oracle/app/oracle/product/10.0/lib, set LD_LIBRARY_PATH in the
nsrnmo script as follows:
LD_LIBRARY_PATH=/disk3/oracle/app/oracle/product/10.0/lib
Uncomment the line export LD_LIBRARY_PATH (by removing the # symbol at the
start of the line) under the export_environment variables() function heading in the
nsrnmo script:
export_environment_variables()
{
export ORACLE_HOME
export NSR_RMAN_ARGUMENTS
:
:
export LD_LIBRARY_PATH
}
LIBPATH
This parameter is optional for a scheduled backup. It appears in the nsrnmo script on
AIX only. Set LIBPATH in the nsrnmo script file to the pathname of the directory that
contains the Oracle libraries, typically $ORACLE_HOME/lib.
To set LIBPATH in the nsrnmo script, follow the example shown in
LD_LIBRARY_PATH on page 82. Replace LD_LIBRARY_PATH with LIBPATH.
Uncomment the line export LIBPATH in the script.
SHLIB_PATH
This parameter is optional for a scheduled backup. It appears in the nsrnmo script on
HP-UX only. Set SHLIB_PATH in the nsrnmo script file to the pathname of the
directory that contains the Oracle libraries, typically $ORACLE_HOME/lib.
To set SHLIB_PATH in the nsrnmo script, follow the example shown in
LD_LIBRARY_PATH on page 82. Replace LD_LIBRARY_PATH with
SHLIB_PATH. Uncomment the line export SHLIB_PATH in the script.
NSR_RMAN_ARGUMENTS
This parameter is optional for a scheduled backup. Set NSR_RMAN_ARGUMENTS to
a double-quoted string that contains any valid combination of options for the RMAN
executable, rman. The appropriate Oracle Recovery Manager documentation
provides details on the valid options.
For example, to append RMAN output to the message log file
/nsr/applogs/msglog.log, set NSR_RMAN_ARGUMENTS in the nsrnmo script as
follows:
NSR_RMAN_ARGUMENTS="msglog /nsr/applogs/msglog.log append"
82
Software Configuration
NSR_SB_DEBUG_FILE
This parameter is optional for a scheduled backup. It is used only for debugging
purposes.
Enable debugging by setting NSR_SB_DEBUG_FILE to the complete pathname of a
file to receive detailed debug information for the scheduled backup. This file will
exclude MML-specific debug information, which is directed to NSR_DEBUG_FILE (if
set in the RMAN script).
Note: If NSR_SB_DEBUG_FILE is undefined (by default), no debug information is generated.
If a file with the specified pathname cannot be created, debug information is either directed to
the default location or not generated.
For example, to send detailed debug information for the scheduled backup to the
/usr/logs/schedbkup.log file, set the parameter NSR_SB_DEBUG_FILE in the
nsrnmo script as follows:
NSR_SB_DEBUG_FILE=/usr/logs/schedbkup.log
NMO error messages on page 222 provides more information on how the debug
information is written if the parameter NSR_SB_DEBUG_FILE is set to an invalid
pathname.
ORACLE_SID
This parameter is required for a scheduled backup in the following cases:
The connect target and connect rcvcat commands for the scheduled backup are
stored in a separate file, and the connect commands are invoked in the RMAN
script by using the @ command.
Set ORACLE_SID in the nsrnmo script file to the system identifier (SID) value of the
Oracle database to be backed up. For example, if catalog synchronization is enabled
for proxy backups and the SID of the Oracle database to be backed up is orcl10,
ORACLE_SID must be set as follows:
ORACLE_SID=orcl10
ORACLE_USER
This parameter is optional for a scheduled backup configured through the legacy
method (without the wizard) on UNIX only.
Enable the scheduled backup for operating system authentication by setting
ORACLE_USER to the username of the Oracle operating system user, which is set up
to connect to the Oracle database through operating system authentication.
Note: Using ORACLE_USER to perform an NMO backup through operating system
authentication is not supported for the following:
- A scheduled backup configured through the new configuration wizard.
- A scheduled backup on Microsoft Windows.
- A probe-based backup.
- A scheduled proxy backup.
83
Software Configuration
If the pre-command script fails (returns a nonzero value), the scheduled Oracle
backup does not proceed (that is, the RMAN script is not executed).
IMPORTANT
The script file must have permissions that allow execution by the root user, as the
scheduled Oracle backup is always launched by root. The script should return a
zero value when it succeeds and a nonzero value when it fails. The return of a
nonzero value will cause the scheduled backup to fail.
A sample preprocessing script for UNIX is shown as follows. This script is stored in
the file whose complete pathname is specified in the parameter PRECMD in the
nsrnmo script.
For example, if the script is stored in the /usr/scripts/orashutdown file, set the
parameter PRECMD as follows:
PRECMD=/usr/scripts/orashutdown
This sample script shuts down the Oracle database, presumably for an offline
database backup. The su command is required in the script since the nsrnmo script
runs as root user:
#!/bin/ksh
# Define Site Specifics Here
TARGET_DATABASE=proddb
ERRFILE=/tmp/precmd.log
ORACLE_USER=proddb
#
# Scheduled backup launches as "root" run PRECMD as oracle user
su - $ORACLE_USER -c "{
# Shutdown target database and start in maintenace mode
export ORACLE_SID=$TARGET_DATABASE
svrmgrl <<EOF1 > $ERRFILE
connect internal
shutdown
startup mount
exit
EOF1
}"
# Do checking as root since "su" will always return its status
export status
# Define status otherwise it is local to if [] statement
status=0
# Scan file for errors and only return true or false
grep -e error -e warning -e fatal $ERRFILE > /dev/null 2>&1
if [ $? -eq 0 ]; then
status=1
else
84
Software Configuration
status=0
fi
exit $status
POSTCMD
This parameter is optional. Set POSTCMD to the complete pathname of a file that
contains a postprocessing script to be executed after the RMAN backup script.
Note: The pathname value of POSTCMD must not contain any spaces. For example, instead of
setting POSTCMD to C:\Program Files\Legato\nsr\postcmd.bat, set the parameter to
C:\Progra~1\Legato\nsr\postcmd.bat.
If the RMAN backup script fails, the failure is reported, and the postprocessing script
is executed nevertheless. If the postprocessing script fails, an error message is
reported.
IMPORTANT
The script file must have permissions allowing execution by the root user, as the
scheduled Oracle backup is always launched by root. The script should return a
zero value when it succeeds and a nonzero value when it fails.
A sample postprocessing script for UNIX is shown as follows. This script is stored in
the file whose complete pathname is specified in the parameter POSTCMD in the
nsrnmo script.
For example, if the script is stored in the /usr/scripts/orastartup file, set the
parameter POSTCMD as follows:
POSTCMD=/usr/scripts/orastartup
This sample script starts up the Oracle database, presumably after an offline backup.
The su command is required in the script since the nsrnmo script runs as root user:
#!/bin/ksh
# Define Site Specifics Here
TARGET_DATABASE=proddb
ERRFILE=/tmp/postcmd.log
ORACLE_USER=proddb
#
# Scheduled backup launches as "root" run POSTCMD as user proddb
su - $ORACLE_USER -c "{
# Mount target database as ready for use
export ORACLE_SID=$TARGET_DATABASE
svrmgrl <<EOF > $ERRFILE
connect internal
alter database open;
exit
EOF
}"
# Do checking as root since "su" will always return its status
export status
# Define status otherwise it is local to if [] statement
status=0
# Scan file for errors and only return true or false
grep -e ORA- -e error -e warning -e fatal $ERRFILE > /dev/null 2>&1
if [ $? -eq 0 ]; then
status=1
else
status=0
fi
exit $status
85
Software Configuration
TNS_ADMIN
This parameter is mandatory if the Oracle Net configuration files are located in a
directory other than the default $ORACLE_HOME/network/admin directory.
In this case, set the value of TNS_ADMIN to the pathname of the directory that
contains the Oracle Net configuration files. To set TNS_ADMIN in the nsrnmo script,
follow the example shown in LD_LIBRARY_PATH on page 82. Replace
LD_LIBRARY_PATH with TNS_ADMIN. Uncomment the line export
TNS_ADMIN in the script.
For a scheduled NMO backup, a NetWorker Group resource must be configured that
specifies the attributes of the backup group. The Group resource specifies a set of
NetWorker Client resources that all start to back up data at a specified time, once the
following occurs:
By configuring one or more NetWorker backup groups for scheduled backups, the
backups can be:
Scheduled for a time of day when performance demands on the database and
NetWorker server are lower.
One or more Client resources configured for the Oracle Server host can be assigned to
a NetWorker backup group.
All NetWorker backup groups can be created and modified. All backup groups except
the Default group can be deleted.
To use the Default group for testing scheduled backups, change its Autostart
attribute to Enabled.
Note: To have a regular scheduled backup automatically use a volume pool associated with the
backup group, specify the group name in the Pool resource for the volume pool.
IMPORTANT
For a regular scheduled Oracle backup, the Snapshot attribute in the Group
resource must be set to False.
You can create a NetWorker Group resource with the NMC interface. The NetWorker
administration guide and NMC online help provide more information.
86
Software Configuration
Level full, incremental, or level 1 to 9 specifies that the NetWorker server runs the
backup script on that day.
Level skip specifies that the NetWorker server does not run the backup script on
that day.
Specify the name of the NetWorker schedule in the Schedule attribute of the Client
resource, as described in Configure a Client resource with NMC on page 87.
A NetWorker Client resource is a set of attributes assigned to the NMO client host
and stored on the NetWorker server. Before NMO software can be used for backups
or restores, a Client resource must be configured for the NMO client host.
If the NetWorker server software is installed on the NMO client host, a basic Client
resource for the NMO client is created automatically during the NetWorker
installation. The Client resource must be customized for an NMO backup.
NetWorker indexes and policies used for restores on page 118 provides more
information on how the NetWorker server uses the browse and retention policies to
manage Oracle backup data and enable the data to be restored.
Configuring the NetWorker Client resource on page 170 provides information on
how to configure the Client resource for proxy backups.
To configure the Client resource for a regular scheduled backup by using the NMC
interface, specify the required values for each attribute, according to Table 5 on
page 88.
Leave the following attributes blank:
Directive
Archive Users
Remote User
Password
87
Software Configuration
Note: On a Solaris system with Solaris zones, ensure that the security fields (such as Remote
Access and Privileges) of NetWorker resources used during NMO backups and restores refer
to the hostname of the zone in which NMO operates.
Each Oracle installation requires a separate Client resource. The Backup Command
attribute of the Client resource must contain only one nsrnmo script name, and
ORACLE_HOME is a mandatory parameter in each nsrnmo script.
If multiple RMAN scripts are specified for the Save Set attribute of the Client
resource:
Figure 6 on page 90 shows a sample Client resource for a UNIX NMO client.
Figure 7 on page 91 shows a sample Client resource for a Windows NMO client.
Table 5
Attribute
Description
Name
Backup Command
For a scheduled backup configured through the legacy method with NMC (not through the wizard), specifies the name of a
single customized nsrnmo script to use for the backup.
For example, the nsrnmo script name might be nsrnmo or nsrnmo2 on UNIX, or nsrnmo.bat or nsrnmo2.bat on Windows.
On a Solaris system with Solaris zones where NMO is installed on sparse root zones, the Backup Command attribute in the
Client resource for each sparse root zone must contain the unique nsrnmo filename for that zone.
Note: If you configure a scheduled backup through the configuration wizard, the wizard automatically adds the nsrnmostart
program name to this attribute. In that case, do not modify this attribute.
Browse Policy
Specifies the length of time that the NetWorker server retains an entry for an Oracle backup in the online client file index. This
attribute applies only to scheduled backups.
Note: For a scheduled backup, if the parameter NSR_SAVESET_BROWSE is set as described in Appendix A, Parameters
in an RMAN Session, its value overrides the Browse Policy attribute setting in the Client resource.
To set a specific browse policy for a manual backup, use the parameter NSR_SAVESET_BROWSE. If the parameter is not
set, the NetWorker server uses the most appropriate value for the browse policy.
Group
88
Specifies the NetWorker backup group to use for a scheduled backup. Configure a Group resource with NMC on page 86
provides more information on NetWorker backup groups.
Software Configuration
Table 5
Attribute
Description
Remote Access
Specifies the fully qualified hostname of a remote system, to enable restores of the backups to that remote system.
On a Solaris system with Solaris zones, the Remote Access attribute must contain the hostname of the zone in which NMO
operates.
Note: If backups from a cluster, or recovery to a host other than the one being backed up, are not required, do not modify the
Remote Access attribute.
Retention Policy
Specifies the minimum length of time that the NetWorker server maintains information about Oracle backup data in the online
media database. This attribute applies only to scheduled backups.
Note: For a scheduled backup, if the parameter NSR_SAVESET_RETENTION is set as described in Appendix A,
Parameters in an RMAN Session, its value overrides the Retention Policy attribute setting in the Client resource.
To set a specific retention policy for a manual backup, use the parameter NSR_SAVESET_RETENTION. If the parameter is
not set, the NetWorker server uses the most appropriate value for the retention policy.
Save Set
Specifies the complete pathname of each RMAN script to be used for a scheduled backup, preceded by RMAN:. Do not
include any spaces between the prefix RMAN: and the script name. On Windows, the pathname can include forward slashes,
for example, RMAN:F:/scripts/incr_1_bkup.
For example, if two separate RMAN backup scripts are created in the files /disk/rman_scripts/archlogbkup and
/disk/rman_scripts/fullbkup (to be run by the nsrnmo script in the Backup Command attribute), specify the complete file
pathnames prepended by RMAN: in the Save Set attribute:
RMAN:/disk/rman_scripts/archlogbkup
RMAN:/disk/rman_scripts/fullbkup
Note: If you configure a scheduled backup through the configuration wizard, the wizard automatically includes the prefix
RMAN: in the Save Set attribute setting, as described in Backup configuration storage with the wizard on page 31.
The save set information for the scheduled backup is stored in the NetWorker indexes as described in:
Regular backup information in NetWorker indexes on page 114
Deduplication backup information in NetWorker indexes on page 115
Schedule
Specifies the NetWorker backup schedule to use for a scheduled backup. Configure a Schedule resource with NMC on
page 87 provides more information on NetWorker backup schedules.
89
Software Configuration
Figure 6
90
Software Configuration
Figure 7
The NetWorker administration guide and NMC online help provide more
information on how to edit the attributes of the NetWorker Client resource.
91
Software Configuration
Ensure that NMO scheduled backups are configured properly according to the
Configuration roadmap on page 62.
Ensure that the user group privileges for the root or administrative user on the
NMO client include the Operate NetWorker privileges. The corresponding User
Group resource is configured on the NetWorker server, as described in
NetWorker user group privileges on page 64.
If the proper username and password are not located in the RMAN script (for
example, the connection strings are included as a command file in the RMAN
script, such as @connection_file), ensure the following:
The ORACLE_SID parameter is set in the nsrnmo script, as described in
Customize the nsrnmo script on page 79.
An NWORA SID resource with the NSR_ORACLE_CONNECT_FILE
parameter setting is created in the NWORA resource file (nwora.res) for the
ORACLE_SID, as described in NWORA SID resources on page 186.
NMO cannot retrieve the connection strings from the RMAN script when the
connection strings are included as a command file in the script. In this case, NMO
must retrieve the connection strings from the connection file specified by the
parameter in the NWORA resource file.
Ensure that the NetWorker server is release 7.4 or later, to support staging of the
NMO save set bundles.
In a RAC system, ensure that all channels are allocated on the same NMO client
node where the backup is initiated. Save set bundling does not support load
balancing across different RAC nodes.
To disable save set bundling, set the NSR_BUNDLING parameter value to disabled by
typing the following command:
nsrnmoadmin -r update NSR_BUNDLING disabled
92
Software Configuration
Ensure that NMO scheduled backups are configured properly according to the
Configuration roadmap on page 62.
Ensure that the user group privileges for the root or administrative user on the
NMO client include the Operate NetWorker privileges. The corresponding User
Group resource is configured on the NetWorker server, as described in
NetWorker user group privileges on page 64.
If the proper username and password are not located in the RMAN script (for
example, the connection strings are included as a command file in the RMAN
script, such as @connection_file), ensure the following:
The ORACLE_SID parameter is set in the nsrnmo script, as described in
Customize the nsrnmo script on page 79.
An NWORA SID resource with the NSR_ORACLE_CONNECT_FILE
parameter setting is created in the NWORA resource file (nwora.res) for the
ORACLE_SID, as described in NWORA SID resources on page 186.
NMO cannot retrieve the connection strings from the RMAN script when the
connection strings are included as a command file in the script. In this case, NMO
must retrieve the connection strings from the connection file specified by the
parameter in the NWORA resource file.
In a RAC system, ensure that all channels are allocated on the same NMO client
node where the backup is initiated. Policy uniformity does not support load
balancing across different RAC nodes.
93
Software Configuration
The NMO client platform and operating system support deduplication. The EMC
Information Protection Software Compatibility Guide on the Powerlink website
provides details on the platforms and operating systems that support
deduplication.
The NetWorker client and server releases support NMO deduplication. The
NetWorker Module for Oracle release notes provides more details.
The NetWorker backup device (receives only the backup metadata or hash ID
during the NMO deduplication backup) is configured as an advanced file type
device (AFTD), as described in the NetWorker administration guide.
Do not create more than four backup channels for a deduplication backup.
94
Do not use RMAN binary compression (for example, ZLIB) with a deduplication
backup.
Once a deduplication node (Avamar server) is selected for an initial full backup
of a client, continue to use the same deduplication node for all of the client's
backups, to take advantage of the data already stored on the server.
Software Configuration
Ensure that the same cache is used to back up the same data every time by not
changing the values of the parameters NSR_DEDUP_CACHE_ENABLED and
NSR_DEDUP_CACHE_TAG. The following sources provide more details:
NSR_DEDUP_CACHE_ENABLED on page 203
NSR_DEDUP_CACHE_TAG on page 204
Associate the backup of specific tablespaces with a specific channel to ensure that
Oracle does not distribute the data to a different channel when the database
structure or size changes.
For example, the following RMAN backup script shows how to associate
tablespaces with a channel:
run {
allocate channel c1 type 'SBT_TAPE';
send channel c1 'NSR_ENV=(NSR_DEDUP_CACHE_TAG=orcl102_c1)';
allocate channel c2 type 'SBT_TAPE';
send channel c2 'NSR_ENV=(NSR_DEDUP_CACHE_TAG=orcl102_c2)';
send 'NSR_ENV=(NSR_DEDUP_BACKUP=TRUE,
NSR_DEDUP_NODE=avamar.emc.com)';
backup filesperset=1
(tablespace tbs1, tbs5 channel c1)
(tablespace tbs2, tbs3, tbs4 channel c2);
release channel c1;
release channel c2;
}
Group tablespaces that contain similar (duplicated) data and associate them with
the same channel. This practice requires familiarity with the database data. A
tablespace must also be added to the backup script when a new tablespace is
created.
To use the configuration wizard (for a scheduled backup only), follow the
instructions in Configuring a backup with the NMC wizard on page 72.
On the Specify the De-duplication Options screen, apply these additional
settings:
Select to enable deduplication.
Specify the hostname of the deduplication node (Avamar server) that will
store the deduplicated backup data.
Configuring a deduplication backup
95
Software Configuration
When you select to enable deduplication, the wizard automatically sets the
parameter NSR_DEDUP_CACHE_TAG for each channel.
Note: You cannot override the default NSR_DEDUP_CACHE_TAG setting.
To use the legacy configuration method (without the wizard), follow the
instructions in Configuring a backup with the NMC legacy method on page 75.
Note: For a manual deduplication backup, the Client resource needs to include only the
two attribute settings in step a on page 96.
The following RMAN script shows the mandatory parameter settings for a manual
deduplication backup. The NSR_DEDUP_CACHE_TAG parameter must be set to a
different value for each allocated channel:
run {
allocate channel ch1 type 'SBT_TAPE';
allocate channel ch2 type 'SBT_TAPE';
send 'NSR_ENV=(NSR_SERVER=mars.emc.com, NSR_CLIENT=oracle.emc.com,
NSR_DEDUP_BACKUP=TRUE, NSR_DEDUP_NODE=node3.emc.com)';
send channel ch1 'NSR_ENV=(NSR_DEDUP_CACHE_TAG=ora11_ch1)';
send channel ch2 'NSR_ENV=(NSR_DEDUP_CACHE_TAG=ora11_ch2)';
backup full filesperset 4 format 'FULL_%d_%U' (database);
release channel ch1;
release channel ch2;
}
96
Software Configuration
If you want to use the nsrnmoprobe program provided with NMO to check for
the number of Oracle logs generated since the last probe-based backup (as a
condition that triggers a probe-based backup), ensure that you have reviewed the
details on nsrnmoprobe in Configure a probe-based backup on page 97.
If you want to check for a user-defined condition (other than the number of
generated Oracle logs) that triggers a probe-based backup, a script/program is
created that meets the requirements of the Probe Command attribute of the Probe
resource, as described in Configure a probe-based backup on page 97.
For example, the user-defined condition that triggers a probe-based backup is
that more than two tape drives are idle in a jukebox. To check for this condition, a
script named nsrjukeboxprobe is created in the /usr/sbin directory on Solaris.
When the script runs and checks the number of idle tape drives in the jukebox, it
returns one of the following values:
0 Signifies that more than two tape drives are idle in the jukebox.
1 Signifies that two or fewer tape drives are idle in the jukebox.
Other than 0 or 1 Signifies that an error occurred during the probe.
The NetWorker administration guide provides more information on user-defined
probes in the section on creating a client probe.
97
Software Configuration
Table 6
98
Attribute
Description
Name
Name of the Probe resource for the probe script/program used to check for a probe-based backup condition. Each Probe
resource must have a unique name, which does not have to be the same as the probe script/program name.
Probe Command
Name and path of the probe script/program that checks (probes) for the condition that triggers a probe-based backup. The
script/program meets the following requirements:
Name starts with nsr or save.
Location is the same directory as used for the NetWorker client binaries.
Permissions of the script/program file include the execute permission.
Returns one of the following code values when it finishes running its probe:
- 0 Signifies that the backup condition has been met.
- 1 Signifies that the backup condition has not been met.
- Other than 0 or 1 - Signifies that an error occurred during the probe.
To use the probe program that is included with the NMO software, set this attribute to nsrnmoprobe. The nsrnmoprobe
program checks for the number of Oracle logs generated since the last probe-based backup and triggers a new probe-based
backup when the number exceeds the change threshold.
Command Options
Required for the nsrnmoprobe program only, a comma-separated list of the settings of one or more of the following
parameters. Example 14 on page 99 outlines the parameter settings that nsrnmoprobe requires in each possible scenario.
Parameter
Description
LOG_THRESHOLD
Mandatory. Specifies the change threshold, which is the minimum number of redo logs
(generated since the last probe-based backup) required to trigger a new probe-based
backup. When the number of logs generated since the last probe-based backup equals
or exceeds the change threshold, nsrnmoprobe triggers a probe-based backup.
NSR_DEBUG_FILE
Optional. Specifies the pathname of the log file that receives debug information from
the probe-based backup triggered by nsrnmoprobe.
NSR_ORACLE_CONNECT_FILE
ORACLE_HOME
ORACLE_SERVICE
Software Configuration
Note: The State attribute of the Probe resource is visible only in diagnostic mode. At the
end of each successful probe-based backup, the nsrnmoprobe program stores the current
log sequence number and database instance number in the State attribute. The State
attribute is not used with user-defined probes.
2. Configure the NetWorker Group resource for a probe-enabled backup group. Set
the probe-specific attributes in the Group resource, as described in the NetWorker
administration guide (the section on creating and scheduling a probe group). The
Group resource has been extended to include several new attributes that must be
set for a probe-based backup group.
When probing is enabled through the Group resource attributes, probing occurs
continuously throughout the backup window, which is the time window defined
by the Probe Start Time and Probe End Time attributes.
Note: If a probe-enabled backup group is started manually, probing occurs immediately
(only once, not repeatedly at intervals) and the backup starts only if the probe conditions
are met.
3. Configure the NetWorker Client resource for the NMO client according to the
instructions in the appropriate section:
Configuring a backup with the NMC wizard on page 72
Configure a Client resource with NMC on page 87
In the Client resource:
For the Probe attribute, specify the name of the required Probe resource from
step 1. This attribute associates the Client resource with the probe
script/program specified in the Probe resource.
Note: A Client resource can be associated with only one probe.
The configuration wizard does not display the Probe field. If you configure a Client
resource with the wizard, you must then use NMC manually to edit the Client resource
and set the Probe attribute.
For the Group attribute, specify the probe-enabled group from step 2.
Note: A probe-based backup group must include at least one probe-enabled client.
To use the nsrnmoprobe program that is provided with the NMO software, the Probe
resource must be set up properly, as described in Configure a probe-based backup
on page 97.
99
Software Configuration
The Command Options attribute in the Probe resource must include specific
parameter settings, which depend on the particular scenario:
Three possible scenarios dictate the required settings in the Command Options
attribute:
a. The Client resource has been configured through the legacy method with
NMC (not with the wizard), and the NWORA resource file has not been set up
with the Oracle home and database connection information.
In this case, Command Options must include the parameters
LOG_THRESHOLD, NSR_ORACLE_CONNECT_FILE, and
ORACLE_HOME. (NSR_DEBUG_FILE is optional.)
For example, Command Options is set as follows:
LOG_THRESHOLD=10, NSR_DEBUG_FILE=/tmp/probe.log,
NSR_ORACLE_CONNECT_FILE=/RMAN/rmanpw,
ORACLE_HOME=/oracle/hp_11_31_ia/64bit/product/11.1.0.6.0
b. The Client resource has been configured with the wizard, and the NWORA
resource file has not been set up with the Oracle home and database
connection information.
In this case, Command Options must include the LOG_THRESHOLD
parameter. (NSR_DEBUG_FILE is optional.)
For example, Command Options is set as follows:
LOG_THRESHOLD=10, NSR_DEBUG_FILE=/tmp/probe.log
c. The Client resource has been configured through the legacy method with
NMC (without the wizard), and the NWORA resource file is set up to retrieve
Oracle home and database connection information.
In this case, the NWORA resource file must be set up through the command
nsrnmoadmin r add sid=Net_service_name home=Oracle_home
connect=connect_filepath. Command Options must include the parameters
LOG_THRESHOLD and ORACLE_SERVICE, where ORACLE_SERVICE is set
to the same Net service name as NSR_ORACLE_SID in the NWORA file.
(NSR_DEBUG_FILE is optional.)
Configuring the NWORA resource file with the nsrnmoadmin program on
page 188 provides important details on the nsrnmoadmin command.
For example, Command Options is set as follows:
LOG_THRESHOLD=10, NSR_DEBUG_FILE=/tmp/probe.log,
ORACLE_SERVICE=proddb.world
Example 15
At least 25 Oracle log files are generated on an NMO client named mars.
More than two tape drives are idle in a jukebox, attached to a NetWorker storage
node named marmaris. (The jukebox is used to save the data for the probe-based
backup.)
Both the NMO client and storage node are Solaris machines.
100
Software Configuration
The nsrnmoprobe program is installed with the NMO software in /usr/sbin on the
NMO client. The nsrnmoprobe program checks for the number of Oracle log files
generated on the NMO client.
A script named nsrjukeboxprobe is created with execute permissions and stored in
the /usr/sbin directory on the storage node. The script checks for the number of idle
tape drives in the jukebox, and returns either of two values:
0 Signifies that more than two tape drives are idle in the jukebox.
1 Signifies that two or fewer tape drives are idle in the jukebox.
101
Software Configuration
102
3
Backup Procedures
Backup Procedures
103
Backup Procedures
IMPORTANT
The NetWorker server bootstrap and client indexes are not automatically backed
up at the end of a manual Oracle backup, as they are for a scheduled Oracle
backup. After running a manual Oracle backup, perform a NetWorker server
bootstrap backup according to NetWorker server bootstrap backup on page 106.
Regular NetWorker server bootstrap backups help to ensure adequate preparation
for disaster recovery.
Monitor a manual backup on page 108 provides information on how to monitor the
status of a manual NMO backup.
Scheduled backup procedures on page 110 provides information on scheduled
NMO backups.
104
If using an RMAN script for the manual backup, the script is created, as described
in Create RMAN scripts for backups on page 75.
Backup Procedures
On Microsoft Windows, the command to run the RMAN script is rman.exe. The
appropriate Oracle backup and recovery documentation provides more information
on the rman or rman.exe command line options.
IMPORTANT
The NetWorker server bootstrap and client indexes are not automatically backed
up at the end of a manual Oracle backup, as they are for a scheduled Oracle
backup. After running a manual Oracle backup, perform a NetWorker server
bootstrap backup according to NetWorker server bootstrap backup on page 106.
Regular NetWorker server bootstrap backups help to ensure adequate preparation
for disaster recovery.
Cancel a manual backup on page 107 provides information on how to cancel a
manual NMO backup.
IMPORTANT
After the completion of an NMO backup or restore, the Oracle Enterprise Manager
job queue history displays the status of the job as failed, even if the backup or
restore completed successfully. This is due to a known problem with Oracle
Enterprise Manager. View the job output to confirm that the backup or restore
completed successfully.
The Oracle Enterprise Manager documentation included with the product kit
provides more information on using the Oracle Enterprise Manager Backup
Management Tools.
105
Backup Procedures
After finishing a manual Oracle backup, the bootstrap and client index must also be
backed up.
Back up the bootstrap and index
To back up the NetWorker server bootstrap and index:
1. Log in as follows:
On a UNIX NetWorker server as the root user.
On a Windows NetWorker server as the Windows system administrator.
2. Type the following savegrp command:
savegrp -O -l full -P printer_name -c Oracle_Server_name
-c NetWorker_server_name
where:
printer_name is the name of the printer where the bootstrap information is
printed at the end of the bootstrap backup.
Oracle_Server_name is the hostname of the Oracle Server.
NetWorker_server_name is the hostname of the NetWorker server.
After successfully backing up the bootstrap and the client index by using the savegrp
command:
Note: Store the bootstrap printout in a safe place. The printed bootstrap information includes
dates, locations, and save set ID numbers for the bootstrap save sets backed up during the past
month. With this information, determine which volumes are needed to recover the NetWorker
indexes and resource configuration files during a disaster recovery.
The following sources provide information on the savegrp command and options:
106
Backup Procedures
The NetWorker disaster recovery guide provides information on how to use the
bootstrap backup during a disaster recovery.
3. Type the following kill command to cancel the Oracle backup process:
kill -9 pid
107
Backup Procedures
The NetWorker administration guide and NMC online help provide more
information.
Figure 8
108
Backup Procedures
Figure 9
Figure 10
109
Backup Procedures
All the required parameters have been set, either through the wizard or through
the legacy method in the nsrnmo and RMAN scripts.
The NetWorker server and Oracle Server have been correctly configured.
110
Backup Procedures
Note: Cancel a scheduled backup on page 111 provides information on how to cancel the
scheduled Oracle backup.
Use the configuration wizard to set the parameter in the Advanced Environment
Options field on the Specify the Environment Options (Optional) screen.
Use the legacy configuration method to set the parameter in the nsrnmo script.
If the NetWorker server system is UNIX, then the Stop button is supported.
If the NetWorker server system is Windows, then the Stop button is not
supported.
Note: Although the progress message might indicate that the backup has exited
prematurely (before finishing), the NMO processes might still be running on the Oracle
Server host.
To cancel a running scheduled Oracle backup when the Stop button does not work,
the running rman process must be interrupted on the Oracle Server host:
1. In the NetWorker Administrator program, click the Stop button to prevent NMO
from retrying the backup.
2. For each allocated channel, perform the following:
a. View the RMAN message log file to determine the Oracle session ID for the
channel. (The log filename is specified in the NSR_RMAN_ARGUMENTS
parameter, set either through the Advanced Environment Options field in the
wizard or through the nsrnmo script in a legacy configuration.)
111
Backup Procedures
For example, the following sample line from an RMAN message log shows
that channel ch1 has the Oracle session ID 15:
channel ch1: sid=15 devtype=SBT_TAPE
b. Run the following select command in the Oracle svrmgrl or sqlplus program
to determine the serial number:
select serial# from v$session where sid=session_id;
where session_id is the Oracle session ID from the RMAN message log in
step a.
c. Run the following alter system command in the Oracle svrmgrl or sqlplus
program to terminate the channel:
alter system kill session session_id, serial#;
where:
session_id is the Oracle session ID from step a.
serial# is the serial number from step b.
Cancel a nonresponding manual backup on page 107 describes how to also cancel a
nonresponding scheduled backup.
During the backup, the Sessions tab lists one save session for each channel used
by NMO for the backup. The display shows the rate of data being backed up and
total size of the backed-up data.
After the backup, the Groups tab enables you to select the backup group and
display details about the group, including the Completed successfully box that
contains one entry for each channel used by NMO for the backup. Figure 11 on
page 113 shows the type of group details displayed, including the size of each
save set.
Note: For a deduplication backup, the NMC display shows the total size of the data prior to
deduplication, not the size of the deduplicated data. The display also does not indicate that the
data is for a deduplication backup that is stored on the Avamar server.
112
Backup Procedures
Figure 11
IMPORTANT
Do not set the parameter NSR_SAVESET_NAME.
To pass the information to the Oracle Server processes, NMO invokes the RMAN
executable with send as a command line option. The send command on page 211
provides more information.
113
Backup Procedures
For a manual backup, the name RMAN:backup_piece_name for the save set name.
For a scheduled backup with a NetWorker server release prior to 7.3.2, the value
from the Save Set field of the Client resource for the save set name.
For a scheduled backup with NetWorker server release 7.3.2 or later, the name
RMAN:backup_piece_name for the save set name.
Query the online NetWorker indexes by using the NetWorker commands, nsrinfo
and mminfo.
To query the client file index, use the nsrinfo command. For example:
nsrinfo -n oracle -s NetWorker_server_hostname
Oracle_Server_hostname
To query the media database, use the mminfo command. For example:
mminfo -v -s NetWorker_server_hostname -c Oracle_Server_hostname
The NetWorker command reference guide and the UNIX man pages provide more
information on these NetWorker commands.
The following examples show the command output for a manual or scheduled NMO
backup, where the backup piece is named 1hiu83f4_1_1 and the scheduled backup is
performed with NetWorker server release 7.3.2 or later:
The client file index includes the backup piece name for the save set:
nsrinfo -n oracle -s ca-oracle1 ca-oracle1
1hiu83f4_1_1, date=1192133159 Thu Dec 11 16:05:59 2008
The media database includes the prefix RMAN: with the backup piece name for
the save set:
mminfo -v -s ca-oracle1 -c ca-oracle1
volume
NMO.001
client
ca-oracle1
ssid
fl
4212032038 cb
date
12/11/08
time
16:05:59
size
145 MB
level
full
name
RMAN:1hiu83f4_1_1
Note: The media database also includes information about the bootstrap, index, and NWORA
resource file backups that occur as part of each scheduled backup. The preceding mminfo
command sample does not show the bootstrap, index, and NWORA resource file information
for the scheduled backup.
114
Backup Procedures
Cross-check the client file index and media database by using the save time. For
example:
mminfo -c ca-oracle1 -t 1192133159
nsrinfo -n oracle -t 12/11/08 16:05:59 ca-oracle1
The following examples show the index query results from the nsrinfo and mminfo
commands, where the backup piece is named 35ji3i75_1_1:
As for a regular backup, the client file index includes the backup piece name for
the save set of the deduplication backup:
nsrinfo -n oracle -vV molecule
UNIX file '35ji3i75_1_1', size=212, off=0, app=oracle(25),
date=1212610342 Wed Jun 04 16:12:22 2008, (unknown fid), file size=0
In this case, the size of the backup piece is the size of the Avamar hash ID (20
bytes) plus the size of the NetWorker metadata that contains the backup piece
name.
To query the media database, use the mminfo command with the -q dedupe
option (displays only save sets created through deduplication) and the -S option
(lists the extended options for the deduplication backups):
mminfo -S -q dedupe
ssid=1330050855 savetime=06/04/08 16:12:22 (1212610342)
RMAN:35ji3i75_1_1 level=full sflags=vF
size=216
files=1
insert=06/04/08 create=06/04/08 complete=06/04/08 browse=07/04/08
23:59:59 retent=06/04/09 23:59:59
clientid=08b98b33-00000004-4824ae51-4824ae45-000c0000-80de6f33
*Client path: /NetWorker/server_name/client_name;
*Data set size: 34000000;
*De-Dup session id: 27;
*De-Dup snapup time: 2008-06-04;
*De-duplication: Yes;
*De-duplication host: scip2d088.lss.emc.com;
*Domain: /NetWorker/server_name;
*New data on De-Dup Node: 6899656.00;
*New files: 1;
*Replication host: scip2d089.legato.com;
*Size on De-Dup Node: 34603008.00;
group: Default;
Clone #1: cloneid=1212610343 time=06/04/08 16:12:23
retent=06/04/09 flags=F
frag@
0 volid=1648811587
file/rec=1330050855/0
rn=0 last=06/04/08
The save file size reported by mminfo is the same as that reported by nsrinfo,
except for an extra four bytes due to a NetWorker end-of-save-set marker.
When a deduplication backup is deleted (for example, by a user or the NetWorker
server), the backup information is deleted immediately from the NetWorker indexes,
and a request is queued for deletion of the backup from the Avamar server. The
115
Backup Procedures
116
4
Data Restore and
Recovery
117
Review the following sections in preparation for the Oracle data restore and recovery
procedures:
The client file index entry is maintained until the browse policy specified for the
clients save set expires.
The media database entry is maintained until the retention policy specified for the
clients save set expires.
When the retention policies for all the save sets on a backup volume expire, the
volume becomes recyclable and eligible for automatic relabeling by the NetWorker
server. The save set entries, however, remain in the media database until the volume
is actually relabeled. When the volume is relabeled, the data on it becomes
inaccessible and can no longer be restored.
NetWorker Module for Oracle (NMO) uses the client file index entries to restore
Oracle backup pieces. Set the browse policy to a period long enough to retain the
client index entries for restoring the Oracle backup pieces.
Note: After a browse policy expires, the NetWorker scanner program can be used to rebuild
the online indexes. However, index entries regenerated by using scanner might cause the
NetWorker indexes to become unsynchronized with the RMAN catalog and lead to problems.
To avoid problems, ensure that the backup pieces have unique names, as described in RMAN
scripts for manual backups on page 75.
118
You can run the recovery configuration wizard from the NetWorker Console
Administration window, which you can start on any supported host by using a web
browser session and specifying the Console server URL.
The NetWorker Module for Oracle release notes provides details on the NetWorker
requirements for the support of the NMC-based configuration wizards.
To configure a restore with the wizard:
1. Review the information in Features of the recovery configuration wizard on
page 119.
2. Ensure that you meet the Requirements for using the recovery configuration
wizard on page 120.
3. Follow the steps in Configure a restore with the wizard on page 120.
Features of the recovery configuration wizard
The recovery configuration wizard can create an RMAN script for the following types
of restore and recovery:
Current time restore and recovery of a whole or partial Oracle database, where a
partial database is a set of tablespaces or datafiles.
The wizard can configure a tablespace restore as long as the control file contains
information about the tablespace.
Restore and recovery of Oracle data to a different database through the creation
of a duplicate database on either the local host or a remote host, using backups of
the original target database.
The database duplication script created by the wizard uses the RMAN duplicate
command to create a duplicate database while the original database is retained.
The duplicate database can either be an identical copy of the original database or
contain only a subset of the original tablespaces. For example, the duplicate
database can be created to run independently on a remote host, for the purpose of
practicing restore and recovery operations while the production database
remains in operation on the local host:
If the duplicate database is to be created on the same host as the original
database, the RMAN script is also generated on the local host. In this case, the
wizard requests names for the duplicate database, datafiles, and redo logs that
differ from those of the original database.
If the duplicate database is to be created on a remote host, the RMAN script is
generated on either the local or remote host, as specified in the wizard. In this
case, the wizard requests a name for the duplicate database that differs from
that of the original database. (The datafile and redo log names can be the same
as for the original database.)
The recovery configuration wizard can only create a new RMAN script for restore
and recovery. The wizard cannot modify an existing RMAN script. You must use a
text editor to modify an RMAN script that was created by the wizard.
RMAN scripts for restore and recovery on page 121 provides more information
about RMAN scripts for restore and recovery.
119
Proxy backups
The NMC user that starts the wizard (the wizard user) has the Remote Access
NetWorker privileges on the NetWorker server where the NMO client
configuration is stored.
Communication between the NMC server, NetWorker server, and NMO client
uses nsrauth authentication. The NetWorker documentation provides any
requirements for nsrauth authentication.
The required NetWorker releases are installed on the NMC server, NetWorker
server, and NMO client hosts, as described in the NetWorker Module for Oracle
release notes.
The NetWorker Client resource for the NMO client was created through one of
the following:
Backup configuration wizard in NMO 5.0
Migration of a legacy configuration with the nsrnmoadmin command
Legacy configuration method (without the wizard), where the value of the
Save Set attribute of the Client resource has the RMAN: prefix
120
5. To start the wizard, right-click the NMO client in the right pane, and select
Recover.
6. On each wizard screen that appears, specify the required values for the RMAN
script configuration.
Each wizard screen includes an online help button that you can click to access
descriptions of all the fields and options on the screen:
On all but the last screen, click Next to proceed.
On the last screen, Review and Accept the Script Creation, click Create to
create the RMAN restore script.
IMPORTANT
When you create an RMAN restore script with the wizard and select the offline or
online mode option for tablespaces, you might need to manually edit the script and
insert an "alter database open;" command before the sql...tablespace... commands,
if it will be required for your particular database (if the database will not be open
at the point where the sql commands are to be run).
The following RMAN script performs a restore of an Oracle tablespace by using the
(remote) NetWorker server mars.emc.com. The Oracle data is restored to the
NetWorker client server1.emc.com. This RMAN script also includes the recovery
step, which is explained in Perform an Oracle data recovery on page 127:
run {
allocate channel t1 type SBT_TAPE;
allocate channel t2 type SBT_TAPE;
send NSR_ENV=(NSR_SERVER=mars.emc.com,
NSR_CLIENT=server1.emc.com);
sql alter tablespace users offline immediate;
restore tablespace users;
recover tablespace users;
sql alter tablespace users online;
release channel t1;
release channel t2;
}
Create RMAN scripts for backups on page 75 provides more information on setting
NSR* parameters in an RMAN script.
121
Example 17
The Oracle data being restored was backed up with 256-bit AES encryption.
Example 11 on page 76 shows a sample Oracle backup with AES encryption.
The encryption phrase on the NetWorker server has changed since the Oracle
data was backed up.
By default, NMO and NetWorker use configuration settings and information in the
media database to determine the backup volume to use for an NMO restore.
As an alternative, you can use the NSR_RECOVER_POOL parameter in the RMAN
restore script to restore data from a specified volume pool if there are multiple copies
(clones) of the backup on different volume pools. NSR_RECOVER_POOL on
page 206 provides more information.
The following RMAN script performs a nonproxy restore of the database from the
specified volume pool named OracleClonePool2, where the pool contains a clone of
the original backup volume.
shutdown immediate;
startup mount;
run {
allocate channel c1 type 'SBT_TAPE';
send channel c1 NSR_ENV=(NSR_SERVER=backup01,
NSR_RECOVER_POOL=OracleClonePool2);
restore database;
release channel c1;
}
122
The volume required for the restore operation is mounted in a configured backup
device:
If you use a stand-alone tape drive, the volume is mounted manually.
If you use an autochanger, the NetWorker server mounts the volume
automatically.
To determine the volumes required for the restore, you can use the nsrnmoinfo
command, as described in Using the nsrnmoinfo command to determine the
volumes for restore on page 123.
123
where:
filename specifies the name of a text file that contains a list of one or more backup
piece names for restore:
The file must contain each backup piece name on a separate line.
The file cannot contain spaces or comments (for example, comment lines
preceded with the # symbol).
Command options in brackets ([ ]) are optional. Do not include the brackets when
typing the command.
To use the nsrnmoinfo command, specify the names of the backup pieces by either or
both of the following:
List the backup piece names in a text file, and specify the name of the file with the
-f option of the nsrnmoinfo command.
The nsrnmoinfo command displays a list of one or more volumes required for the
Oracle restore:
For each backup piece, the list includes the accessible volumes containing the
backup piece, which the NetWorker server will use for the restore.
The listed volumes are the most accessible ones, which the NetWorker server intends
to use for the restore at the time that the command is typed:
124
The command lists clones of volumes if the original volumes are not accessible.
If any listed volumes are removed from the NetWorker devices or deleted after
the nsrnmoinfo command is typed, the server can perform the restore by using
different volumes that are accessible. For example, the server can use an
accessible clone (already mounted in a drive or available for mounting in a
jukebox) instead of a listed volume.
Example 19
Each of the following nsrnmoinfo commands displays a list of the volumes required
to restore the specified backup pieces:
The following command searches in the NetWorker index of the client mars on
the server server1 for information on the volumes that contain the backup pieces
backupc_1 and backupc_2:
nsrnmoinfo -c mars -s server1 backupc_1 backupc_2
The following command searches in the NetWorker index of the local host for
information on the volumes that contain the backup pieces listed in the file
backup2.txt: (Both the NetWorker client and server are assumed to be the local
host.)
nsrnmoinfo -f backup2.txt
The following command searches in the NetWorker index of the client mars for
information on the volumes that contain both:
The backup piece backupc_3.
The backup pieces listed in the file backup3.txt.
(The NetWorker server is assumed to be the local host.)
nsrnmoinfo -c mars backupc_3 -f backup3.txt
Example 20
The following nsrnmoinfo command searches in the NetWorker index of the local
host on the server mars for information on the volumes containing the backup pieces
backup1 and backup2:
nsrnmoinfo -s mars backup1 backup2
Volumes mars.003 and mars.004 are required to restore the backup piece
backup1.
125
On Microsoft Windows, the command to run the RMAN script is rman.exe. The
appropriate Oracle backup and recovery documentation provides more information
on the rman or rman.exe command options.
Restore to a different host
In some cases, an Oracle database must be restored to a different system from the one
that was originally backed up. Some situations where this could occur include, but
are not limited to, performing a disaster recovery or duplicating a database on a
remote host. The appropriate Oracle documentation provides more information.
To restore an Oracle database to different system:
1. On the NetWorker server that contains the backup to be restored, specify the
hostname of the different system for the Remote Access attribute in the Client
resource of the original system.
2. Install and configure NMO on the different system where the Oracle data is to be
restored.
3. Install and configure RMAN on the different system.
4. Create an appropriate RMAN restore script.
5. In the RMAN script, set the parameter NSR_SERVER to the name of the
NetWorker server that contains the backup.
6. In the RMAN script, set the parameter NSR_CLIENT to either the name of the
NetWorker client (Oracle Server host) that was backed up or the value of
NSR_CLIENT that was used during the backup.
7. Use the appropriate RMAN command to run the script to restore the Oracle
database files.
The Oracle Enterprise Manager Backup Management Tools include a graphical user
interface to RMAN. This interface can be used instead of the RMAN command line
interface to do the following:
IMPORTANT
After the completion of an NMO backup or restore, the Oracle Enterprise Manager
job queue history displays the status of the job as failed, even if the backup or
restore completed successfully. This is due to a known problem with Oracle
Enterprise Manager. View the job output to confirm that the backup or restore
completed successfully.
The Oracle Enterprise Manager documentation included with the product kit
provides more information on using the Oracle Enterprise Manager Backup
Management Tools.
126
Include the Oracle commands in the RMAN restore script. A sample RMAN
script is provided on page 121.
After the RMAN restore script has completed successfully, type the commands at
the operating system command line.
127
128
5
Disaster Recovery
Disaster Recovery
130
130
133
134
129
Disaster Recovery
RAC environments
Control file
Registry files:
On UNIX, oratab is typically in /var/opt/oracle or /etc
On Windows, My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Oracle
The Oracle documentation provides an exhaustive list of the files (other than the
Oracle database) that should be backed up.
Follow these guidelines to facilitate disaster recovery:
130
Disaster Recovery
After manual Oracle backups, perform regular backups of the NetWorker server
bootstrap and Oracle client file index by using the procedure described in
NetWorker server bootstrap backup on page 106.
To back up the required files in preparation for disaster recovery, perform the
following:
1. Create the DBID text file on page 131
2. Set up a postcommand script for backup of Oracle-related files on page 131
3. Set up RMAN backups of the database and related files on page 132
4. Set up RMAN backups of Recovery Catalog on page 132
Text file containing the Oracle DBID, as described in Create the DBID text file
on page 131
Registry files:
On UNIX, oratab is typically in /var/opt/oracle or /etc
On Windows, My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Oracle
You can either create a postcommand script from scratch, or modify the
postcommand script that is provided with the NMO software.
131
Disaster Recovery
On UNIX, you can use any name for the postcommand script. On Windows, the
script name must end in .bat.
Note: During a scheduled NMO backup, the nsrnmostart process passes the options
-s server_name -g group_name to the postcommand script if the script name begins with
nsrnmodr.
If you use the NMO wizard to configure the RMAN backup, specify the
postcommand script in the wizard.
If you use the legacy method (without the wizard) to configure the RMAN
backup, set the POSTCMD parameter in the nsrnmo script.
Control file
Follow the instructions in the preceding chapters of this guide to properly configure
and run the RMAN backup with NMO.
For example, to include the control file and SPFILE in the backup, you can add the
following commands to the RMAN backup script:
backup spfile
132
Disaster Recovery
Bootstrap information
The NetWorker disaster recovery guide provides information on how to recover the
NetWorker server from various types of disasters. Related documentation on
page 15 describes how to access the guide.
133
Disaster Recovery
Note: On Windows, you may need to reinsert the oracle.reg file into the registry after
recovering it, for example, with the following command:
regedit /S C:\temp\oracle.reg
The Oracle documentation provides more details.
5. To perform the remainder of the disaster recovery, follow the instructions in the
Oracle Database Backup and Recovery Users Guide. In the RMAN script, set the
NSR_CLIENT parameter to the name of the original host.
Example 21
134
Disaster Recovery
1 ];
$GRP
$GRP
$GRP
$GRP
then
$ORACLE_HOME/network/admin
$ORACLE_HOME/dbs/orapw$ORACLE_SID
/var/opt/oracle/oratab
$ORACLE_HOME/dbid.txt
135
Disaster Recovery
save -s
save -s
regedit
save -s
save -s
:fail
136
6
Cluster and RAC
Systems
137
During a backup, the name of the NetWorker client whose index file should be
used to record the backup information.
During a restore, the name of the NetWorker client whose index file should be
used to search for the save set to be restored.
If NSR_CLIENT is not set, the NetWorker server uses the name of the local physical
host. Set the parameter NSR_CLIENT to the same value for all channels allocated
during the backup.
The value of NSR_CLIENT (either the default value or an explicitly defined value)
used for a backup should be the same as the value of NSR_CLIENT used for the
restore of that backup. Setting NSR_CLIENT to the name of the virtual (as opposed to
the physical) host might be preferable, so the backup and restore scripts run
successfully unmodified, regardless of the physical host that executes the scripts.
IMPORTANT
If NSR_CLIENT is set to any value other than the default value during a backup or
restore, the Remote Access attribute must be modified in that NetWorker Client
resource. The NetWorker administration guide provides more information.
For each Oracle backup and restore, set NSR_CLIENT by using either the rman send
command on the operating system command line or the send command in the
RMAN script.
Note: Setting NSR_CLIENT in the system environment has no effect.
138
NSR_SERVER
Set the parameter NSR_SERVER for a manual Oracle backup or restore if the
NetWorker server is a remote system for the node running the RMAN session. The
parameter must be set to the server name for each channel.
Note: The parameter NSR_SERVER does not need to be set for a scheduled Oracle backup.
Backup failover
Neither RMAN nor NMO supports Transparent Application Failover (TAF). As a
result, if a failure occurs during a backup, the backup is not automatically restarted
from the point of failure on another node. Only connect-time failover is supported.
Connect-time failover on page 144 provides more information.
Cluster systems
A cluster system typically includes multiple nodes connected by a shared SCSI bus to
which common storage is attached. In a cluster system, cluster services such as disk
services can be defined and assigned their own IP addresses and names (virtual
hosts). The services and their associated storage can migrate for failover between the
physical nodes in the cluster.
Together, the NMO and NetWorker server software can back up and restore an
Oracle database configured on cluster disk services. The NetWorker server treats
each cluster service as an independent client and stores the associated backup entries
in the online indexes under the name of the service.
After properly configuring a cluster service as a NetWorker client, NMO can be used
with the NetWorker server to back up and restore the database associated with the
service, independent of the actual node that provides the service.
Cluster systems
139
To configure a cluster system for Oracle backup and restore operations that use
NMO, follow the Roadmap for backup/restore configuration in a cluster system on
page 140.
The Oracle Server and NetWorker server system configurations are completed
according to the instructions in the Configuration roadmap on page 62.
To properly configure Oracle backup and restore operations with NMO in a cluster
system:
1. Configure the storage for the database as a cluster disk service.
The appropriate cluster administration guide from the particular cluster software
vendor provides more information.
2. Configure a Client resource on the NetWorker server for the virtual host and each
physical host that will run backups and restores.
3. Create an RMAN script that includes the appropriate NSR_CLIENT parameter
settings. NSR_CLIENT on page 138 provides more information.
Backup failover
When a node failure occurs during a manual (unscheduled) Oracle backup, a database
administrator (DBA) must restart the backup after instance recovery. Since the Oracle
Net services are configured with a cluster service name, the restarted backup is
executed on the physical node that takes control of the cluster service.
When a node failure occurs during a scheduled Oracle backup, the NetWorker server
restarts the backup (from the beginning, not from the point of failure) if the Client
Retries attribute in the NetWorker Group resource is set to a value greater than zero.
The restarted backup is executed on the node that takes control of the cluster service.
RAC systems
The NMO software supports backups and restores of RAC systems for parallelism
and high availability.
RAC terminology
A node in a RAC system is a physical computer with a hostname such as
node1.emc.com. An Oracle instance is a memory structure and a group of Oracle
Server processes running on a node.
140
An Oracle database (for example, named databs1) comprises a set of datafiles, which
are used by the Oracle instances and can be shared between the nodes. All instances
share the same datafiles and control file. Each node must have its own set of redo log
files and its own archived redo logs.
RAC systems
141
8. For each of the other RAC nodes that will not initiate the NMO backup, create a
basic Client resource. (Settings in these other Client resources do not affect the
NMO backup.)
9. On the RAC node that will initiate the NMO backup, create the required nsrnmo
script and RMAN backup script. The RMAN script must include the
NSR_CLIENT setting, as described in NSR_CLIENT on page 138.
Example 23 on page 142 shows how to set up three RAC nodes as storage nodes for
NMO backups.
Example 23
A RAC system contains three nodes named A, B, and C. Each node has a Linux
operating system, and an attached tape drive to be used for NMO backups.
NetWorker storage node software is installed on each node.
In the NMC interface, a Storage Node resource is created for each node by
right-clicking Storage Nodes in the Devices pane and selecting New.
142
After the Storage Node resources are created, a Device resource is created for each
tape drive. Each Device resource is created in NMC by right-clicking Devices in the
Devices pane and selecting New. Since the tape devices are attached to storage
nodes, the device names must have the format rd=host_name:device_name. For
example:
In the tape device on each node, a volume is labeled and mounted. All of the volumes
are assigned to the Default pool in this example.
Node A is selected to store the index entries for the NMO backups and initiate the
backups. (The choice of node A was arbitrary; node B or node C could have been
chosen instead.) In all the RMAN backup and restores scripts, NSR_CLIENT must be
set to the hostname of node A.
In the NetWorker Client resource for node A:
The following RMAN script uses all three nodes to perform the backup. Each node
backs up data to its local tape drive:
connect target sys/oracle@connect_identifier;
run {
allocate channel t1 type SBT_TAPE
connect sys/oracle@Net_service_name_of_instance_A;
allocate channel t2 type SBT_TAPE
connect sys/oracle@Net_service_name_of_instance_B;
allocate channel t3 type SBT_TAPE
connect sys/oracle@Net_service_name_of_instance_C;
send channel t1 NSR_ENV=(NSR_CLIENT=A);
send channel t2 NSR_ENV=(NSR_CLIENT=A);
send channel t3 NSR_ENV=(NSR_CLIENT=A);
backup database;
release channel t1;
release channel t2;
release channel t3;
}
143
Connect-time failover
If multiple listeners support a single service, a connect-time failover reroutes the
connection request to another listener if the first listener is down or cannot make the
connection. To enable the connect-time failover in RAC, there must be a listener on
each node, and each instance must use the same Net service name.
When using the local Net service naming method, the clients tnsnames.ora file
should include the following parameters:
o92pA.emc.com =
(DESCRIPTION =
(ADDRESS_LIST =
(FAILOVER = ON)
(ADDRESS = (PROTOCOL = tcp) (HOST = nodeA)
(PORT = 1521))
(ADDRESS = (PROTOCOL = tcp) (HOST = nodeB)
(PORT = 1521))
)
(CONNECT DATA =
(SERVICE_NAME = proddb)
)
)
When a node or listener to which a client tries to connect is not available, the next
listener on the list is contacted. When the instance is down but the listener is running,
the failover occurs only if the instance is configured to dynamically register with the
listener.
Dynamic instance registration
Dynamic instance registration was introduced in Oracle8i. During dynamic instance
registration, the database registers itself with the Oracle listener on startup and
unregisters itself on shutdown.
144
If the listener does not listen on the default port (1521), set the LOCAL_LISTENER
parameter in the initialization file.
It is not necessary to have the listener.ora file when the listener listens on the
default port.
When the instance is down, the listener does not know how to connect to it. As a
result, the listener tries the next connect option specified in the ADDRESS_LIST in the
tnsnames.ora file.
Note: Some applications such as Oracle Enterprise Manager still require static database
registration with a listener.
RAC systems
145
Backing up all archived logs from each node on page 147 provides a sample script
to back up all the archive log files in a RAC system.
To run an Oracle restore on a RAC system, none of the nodes can be open. Only the
node that is running the RMAN restore script needs to be mounted.
Example 25
Refer to Example 24 on page 146. A RAC system consists of two nodes named
node1.emc.com and node2.emc.com. The Oracle instances named instance1 and
instance2 are running on node1.emc.com and node2.emc.com, respectively. The
NetWorker server is located on a separate node, server1.emc.com.
146
In this example, the parallel Oracle backup was performed with NSR_CLIENT set to
node1.emc.com for each channel in the RMAN backup script. In order to restore the
backup data to node2.emc.com, add node2.emc.com to the Remote Access attribute in
the NetWorker Client resource for node1.emc.com.
The NetWorker administration guide provides more information on how to modify
the Client resource.
Restoring all archived logs from each node on page 148 provides a sample script to
restore all the archive log files in a RAC system.
RAC systems
147
backup filesperset 10
(archivelog all delete input format al_%s_%p);
release channel t1;
release channel t2;
}
148
7
Proxy Backups and
Restores
150
151
153
159
163
171
174
177
181
194
149
The proxy backups create snapshots of Oracle data that reside on primary storage
devices supported by the PowerSnap Modules that work with the NMO.
The EMC Information Protection Software Compatibility Guide on the Powerlink
website provides a complete list of supported PowerSnap Modules.
The proxy operations use the particular PowerSnap Module software designed
for the primary storage.
The following sources provide details on the installation requirements for proxy
operations:
Instant backups
An instant backup creates a point-in-time copy (snapshot) of Oracle data and stores
this copy on the primary storage system. Instant backups can be scheduled to occur
many times in a single day, with little impact to the Oracle Server or network.
The group of Oracle datafiles in the point-in-time copy is referred to as a snap set. A
snapshot policy must be configured to control the lifecycle of the snap set. This policy
specifies the frequency of instant backups and how long snapshots are retained
before being recycled. Software configuration roadmap on page 163 provides more
information.
Note: NMO supports scheduled instant backups only. Manual (unscheduled) instant backups
are not supported.
Live backups
NMO supports the following two types of live backup, which back up a snapshot to
secondary (traditional) storage:
150
IMPORTANT
Instant backups protect against logical failures only. To protect against physical
failures, the point-in-time copy must be backed up to secondary storage.
A proxy client host that is separate from the Oracle Server host can be used to move
the point-in-time copy to the traditional storage medium, such as tape. Using a proxy
client as a secondary host reduces the impact on the Oracle Server.
Note: The proxy client can be a NetWorker storage node.
Instant restores
During an instant restore, the saved data is retrieved from a mounted point-in-time
copy that was created with an instant backup. A minimal amount of time is required
for this type of restore.
Rollbacks
A rollback restores a whole point-in-time copy to a source location by using the
hardwares particular capabilities. Rollbacks are destructive restores because they
overwrite the entire contents of a snapshot unit, such as a volume or disk. Use the
NetWorker PowerSnap Module documentation to determine if a rollback is
supported on a specific type of hardware.
Restores from secondary storage
If the point-in-time copy was backed up to secondary storage through a live backup,
the PowerSnap Module software uses the NetWorker recover program to retrieve the
data.
151
Oracle Server
The following sections provide more information on RMAN and the Recovery
Catalog:
The EMC software components required for proxy backups are the following:
NetWorker server
NetWorker client (installed on the Oracle Server and proxy client host)
NetWorker PowerSnap Module (installed on the Oracle Server and proxy client
host)
Note: NetWorker storage node software can be optionally installed on the proxy client host.
Figure 12 on page 153 illustrates the architecture of the proxy backup and restore
system. It provides an overview of the functional relationship between the Oracle
and NetWorker software components. The interactions of the components are
described in the following sections:
152
RMAN
NetWorker
server
NetWorker
client
Oracle
Server
Recovery
Catalog
NetWorker
Module
for Oracle
MML
NetWorker
client
PowerSnap
Module
PowerSnap
Module
Oracle
data files
Point-in-time copy
of Oracle data files
NetWorker
server
Storage
medium
Primary storage
GEN-000174
Figure 12
When a proxy backup is initiated, the RMAN utility starts the Oracle Server
processes that call the MML proxy-specific routines. The MML routines communicate
with the PowerSnap Module service.
On the Oracle Server host, the PowerSnap Module uses a storage platform-specific
application programming interface (API) to take a snapshot of the Oracle data on the
primary storage.
153
If a live backup is performed, the PowerSnap Module moves the Oracle data from the
point-in-time copy (snapshot) on the primary storage to the NetWorker server or
storage node. The NetWorker server or storage node then stores the Oracle data on
the secondary storage, such as a tape.
At the end of the proxy backup, the NetWorker server updates the online client and
media indexes with information about the backup. The NetWorker administration
guide provides more information about NetWorker server and NetWorker client
programs and services.
Note: A proxy backup can be started only by automatic or manual invocation of the scheduled
NetWorker backup group. A proxy backup cannot be scheduled through Oracle Enterprise
Manager or started from RMAN. The NetWorker PowerSnap Module documentation provides
information on how to manually invoke a scheduled backup.
Note: To simplify the descriptions and illustrations in these sections, certain steps have been
omitted, such as the step to obtain the proper NetWorker authorization.
5. The nsrsnap program contacts the nsrexecd service, which starts the nsrnmo
script for the scheduled backup.
6. The nsrnmo script sets the required parameters and invokes the NMO program,
nsrnmostart.
154
7. The nsrnmostart program starts the RMAN utility to run the required RMAN
backup script.
8. RMAN starts an Oracle process that calls the MML, which contacts the
PowerSnap master program, nsrpsd, to perform the instant backup:
PowerSnap processes create the point-in-time copy that comprises the backup.
The nsrmmd service performs the following:
Stores metadata (used only by the PowerSnap Module) about the
point-in-time copy on the media belonging to the configured snapshot
pool.
Records tracking information about the metadata in the NetWorker media
database by using the nsrmmdbd service.
The nsrindexd service records information about the point-in-time metadata
in the NetWorker client file index.
The nsrindexd service records tracking information about each backup piece
name in the NetWorker client file index. The client index contains one entry
per datafile.
The Oracle Server records the backup entry in the RMAN catalog.
9. After the RMAN script completes successfully, the nsrnmostart program backs
up the NWORA resource file, described in The NWORA resource file on
page 183.
10. If the Snapshot Policy resource specifies that the point-in-time copy must be
copied to secondary storage, the nsrsnap program performs the steps in
Deferred live backup on page 158.
Note: The point-in-time copy is not deleted from the primary storage.
11. The savegrp program backs up the NetWorker server bootstrap and Oracle client
file indexes.
Figure 13 on page 156 shows how the Oracle Server and NetWorker processes
interact during a scheduled instant backup.
155
Oracle Server
(NetWorker client)
NetWorker
server
Primary storage
Oracle
data files
Point-in-time copy
of Oracle data files
Client file index
data
tracking
information
PowerSnap
processes
Oracle
process
PowerSnap
processes
nsrindexd
Media database
NetWorker
Module
for Oracle
MML
nsrpsd
RMAN
PowerSnap
elements
nsrexecd
nsrmmd
nsrmmdbd
NetWorker
Module
elements
nsrnmostart
nsrnmo
nsrd
nsrsnap
nsrsnapck
Snapshot
pool media
interprocess communication
nsrexecd
savefs
nsroraclecat
(optional)
savegrp
Start
Here
GEN-000175
Figure 13
1. At the scheduled backup start time, the main NetWorker service, nsrd, starts the
configured groups backup by invoking the savegrp program.
2. The savegrp program requests that the NetWorker client-side service, nsrexecd,
on the Oracle Server host run the savefs program to verify the existence of the
RMAN scripts to be used for the backup.
3. If the savefs program succeeds, the savegrp program starts the PowerSnap
program, nsrsnap, on the Oracle Server host. Otherwise, the backup fails.
156
5. The nsrsnap program contacts the nsrexecd service, which starts the nsrnmo
script for the scheduled backup.
6. The nsrnmo script sets the required parameters and invokes the NMO program,
nsrnmostart.
7. The nsrnmostart program starts the RMAN utility to run the required RMAN
backup script.
8. RMAN starts Oracle processes that call the MML, which contacts the PowerSnap
master program, nsrpsd, to perform the immediate live backup:
PowerSnap processes create the point-in-time copy, move the data to
secondary storage, and then delete the point-in-time copy from the primary
storage.
The nsrmmd service records the tracking information about the secondary
storage save sets in the NetWorker media database by using the nsrmmdbd
service.
The nsrindexd service records the tracking information for each backup piece
name and for each stored operating system datafile in the NetWorker client
file index. The client index contains two entries per datafile.
The Oracle Server records the backup entry in the RMAN catalog.
9. After the RMAN script completes successfully, the nsrnmostart program backs
up the NWORA resource file, described in The NWORA resource file on
page 183.
10. The savegrp program backs up the NetWorker server bootstrap and Oracle client
file indexes.
Figure 14 on page 158 shows how the Oracle Server and NetWorker processes
interact during a scheduled immediate live backup.
157
Oracle Server
(NetWorker client)
NetWorker
server
Primary storage
Oracle
data files
Point-in-time copy
of Oracle data files
Client file index
data
tracking
information
PowerSnap
processes
Oracle
process
PowerSnap
processes
nsrindexd
Media database
NetWorker
Module
for Oracle
MML
nsrpsd
RMAN
PowerSnap
elements
nsrexecd
nsrmmd
nsrmmdbd
nsrnmostart
nsrnmo
NetWorker
Module
elements
nsrd
nsrsnap
nsrsnapck
Secondary
storage medium
interprocess communication
nsrexecd
savefs
nsroraclecat
(optional)
savegrp
Start
Here
GEN-000176
Figure 14
2. The nsrmmd service records the tracking information about the deferred live
backup in the NetWorker media database by using the nsrmmdbd service.
3. The nsrindexd service records the tracking information for each stored operating
system datafile in the NetWorker client file index.
158
Figure 15 on page 159 shows how the Oracle Server and NetWorker processes
interact during a scheduled deferred live backup.
Oracle Server
(NetWorker client)
NetWorker
server
Primary storage
Oracle
data files
Point-in-time copy
of Oracle data files
Client file index
tracking
information
Start
Here
interprocess
communication
PowerSnap
processes
nsrindexd
data
Media database
nsrexecd
nsrmmd
nsrmmdbd
PowerSnap
elements
Secondary
storage medium
GEN-000177
Figure 15
The RMAN utility starts Oracle Server processes on the target database. These Oracle
Server processes start the restore by calling MML routines.
The following sections describe the process steps in the three types of proxy restore:
159
160
Oracle Server
(NetWorker client)
NetWorker
server
Primary storage
Oracle
data files
Point-in-time copy
of Oracle data files
Client file index
data
(for details on
data flow, see
description)
RMAN
tracking
information
Oracle
process
PowerSnap
module
NetWorker
Module
for Oracle
MML
nsrexecd
nsrpsd
PowerSnap
module
nsrexecd
nsrindexd
Media database
nsrmmd
PowerSnap
elements
nsrmmdbd
NetWorker
Module
element
Snapshot
pool media
nsrd
interprocess communication
GEN-000178
Figure 16
161
3. The nsrpsd program works with other PowerSnap and NetWorker programs to
retrieve the data from secondary storage, and perform the restore operation.
PowerSnap processes restore the files (save sets) into a destination requested by
NMO. The processes use the nsrmmd and nsrmmdbd processes to determine
which media contain the requested save sets and to read the backup volumes.
4. If operating system files (not raw devices or volumes) are restored, NMO moves
the restored files from the .nworapc directory to the parent directory.
Once the required Oracle files are restored from the backup volumes, a database
administrator can complete the standard Oracle database recovery.
Figure 17 on page 162 shows how the Oracle Server and NetWorker processes
interact during a restore from secondary storage.
Oracle Server
(NetWorker client)
NetWorker
server
Primary storage
Oracle
data files
Client file index
data
RMAN
tracking information
Oracle
process
NetWorker
Module
for Oracle
MML
nsrexecd
PowerSnap
module
nsrindexd
nsrpsd
nsrmmd
Media database
PowerSnap
elements
NetWorker
Module
element
nsrmmdbd
Secondary
storage
nsrd
interprocess communication
GEN-000179
Figure 17
162
Basic configurations
Ensure that the following basic configurations are performed:
The basic Oracle Server and NetWorker configurations are performed according
to the Configuration roadmap on page 62. The NetWorker Server, Client,
Device, and other resources must be configured:
For live Oracle backups, a Device resource must be configured for each
secondary storage device, such as a tape drive, to be used for the backups. The
devices must be mounted prior to the backups.
For instant Oracle backups, a snapshot Pool resource must be configured, as
described in Additional configurations for proxy operations on page 163.
Once all the configuration requirements are met, review the information in the
following sections prior to performing proxy backups and restores:
163
164
The parameter ORACLE_SID in the nsrnmo script (used for the proxy backup)
must be set to the same value as the parameter NSR_ORACLE_SID in the
NWORA SID resource.
The proxy or proxy only option must be specified with each RMAN backup
command.
Note: Certain options of the RMAN backup command, such as maxsetsize and diskratio,
are not supported with the proxy option. Contact Oracle Corporation for more information
on the RMAN options that are not supported.
As required by Oracle for proxy backups, the %p variable must be included in the
format string, either explicitly or implicitly within %U. The appropriate Oracle
backup and recovery documentation provides more information.
Allocate only one channel in the RMAN script. Do not allocate more than one
channel in the RMAN script, in an attempt to distribute the proxy backup over
more than one channel.
Note: Proxy backup parallelism is defined by the PowerSnap parameter
NSR_PS_SAVE_PARALLELISM. Table 7 on page 167 provides more information.
The following sample RMAN script performs a proxy backup of an entire Oracle
database that resides on one or more primary storage devices:
run {
allocate channel t1 type SBT_TAPE;
send NSR_ENV=(
NSR_PROXY_PFILE=/oracle/rman/proxy.cfg);
backup full proxy only
format FULL_%d_%U
(database);
release channel t1;
}
The proxy backup performed with the following RMAN script is written to either the
OracleVolume1 or OracleVolume2 volume pool (not to both volume pools) because
Oracle uses only one of the allocated channels for the proxy backup:
run {
allocate channel c1 type SBT_TAPE;
allocate channel c2 type SBT_TAPE;
send channel c1 NSR_ENV=(NSR_DATA_VOLUME_POOL=OracleVolume1);
send channel c2 NSR_ENV=(NSR_DATA_VOLUME_POOL=OracleVolume2);
165
The following RMAN script uses specific backup options to enforce distribution of
the proxy backup over two channels:
run {
allocate channel c1 type SBT_TAPE;
allocate channel c2 type SBT_TAPE;
send channel c1 NSR_ENV=(NSR_DATA_VOLUME_POOL=OracleVolume1);
send channel c2 NSR_ENV=(NSR_DATA_VOLUME_POOL=OracleVolume2);
backup proxy
(tablespace tbs1, tbs2 channel c1)
(tablespace tbs3, tbs4 channel c2);
release channel c1;
release channel c2;
}
Use the following RMAN script to replace both of the preceding two backup scripts:
run {
allocate channel c1 type SBT_TAPE;
send channel c1 NSR_ENV=(NSR_DATA_VOLUME_POOL=OracleVolume1);
backup proxy tablespace tbs1, tbs2, tbs3, tbs4;
release channel c1;
}
You might want to allocate more than one channel if you know that some of the data
does not reside on supported primary storage devices. In this case, one channel is
used for proxy backups and all the others are used for regular backups.
Setting the parameters
Two types of parameters can be set for the proxy backup and restore operations:
166
The configuration file consists of a separate line such as the following for each
parameter setting:
parameter_name=parameter_value
where:
parameter_name is the parameter name, such as RESTORE_TYPE_ORDER.
parameter_value is the parameter value, such as pit.
Use the following guidelines to set PowerSnap parameters:
Table 7
Parameter
Description
NSR_DATA_MOVER
NSR_PS_SAVE_PARALLELISM
16 (default).
An integer value less than or equal to the
Parallelism attribute value in the NetWorker Client
resource.
167
Table 7
Parameter
Description
NSR_MAX_STREAMS
16 (default).
An integer value.
RESTORE_TYPE_ORDER
pit:conventional (default).
One or more of the following values, each value
delimited from the others by a colon(:):
pit Specifies an instant restore.
conventional Specifies a proxy restore from
secondary storage media.
rollback Specifies a rollback restore from a
point-in-time proxy copy.
Proxy restore requirements on page 177 provides
more information.
Example 27
To enable proxy backup and restore operations with Celerra NAS devices, ensure
that the following PowerSnap parameters are set in the user-defined configuration
file that you specify with the NMO parameter NSR_PROXY_PFILE:
NAS_SNAP_SUBTYPE=CEL_SNAPSURE
Identifies the NAS SCM subtype to use.
NSR_SNAP_TYPE=nas
Specifies that this is a NAS save object.
Note: The value of NSR_SNAP_TYPE must be lowercase nas.
168
169
Only members of a NetWorker user group with the Change Security Settings
privilege can set the Remote Access attribute in the Client Resource.
The Browse Policy attribute in the Client resource applies only to the NetWorker
client file index entries for backups residing on secondary storage (live backups).
The Retention Policy attribute in the Client resource applies only to the
NetWorker media database entries for live backups.
IMPORTANT
A proxy backup can be started only by automatic or manual invocation of the
scheduled NetWorker backup group. A proxy backup cannot be scheduled
through Oracle Enterprise Manager, or started by invoking RMAN from the
operating system command line.
To verify the scheduled backup setup, follow the instructions for regular backups in
Test a scheduled backup on page 110.
Since manual (unscheduled) proxy backups are not supported, you cannot test a
proxy RMAN script by using the information in Test RMAN scripts for scheduled
170
backups on page 79. To determine if the script contains any errors, log the RMAN
output into a file by setting the parameter NSR_RMAN_ARGUMENTS in the
nsrnmo script used for the backup.
Proxy backups and restores on cluster systems on page 194 provides information
on proxy backups in a cluster environment.
None of the backup commands in the RMAN script include the proxy or proxy
only option.
The backup commands in the RMAN script include the proxy or proxy only
option, but none of the Oracle database objects (tablespaces or datafiles) specified
in the backup commands reside on a primary storage device that the PowerSnap
Module supports.
If RMAN performs only regular Oracle backups due to one of these conditions, NMO
generates the following warnings in the savegroup completion report:
WARNING: Snapshot savegrp is completed but no Oracle proxy backup is
detected.
WARNING: Either fix your RMAN script or reconfigure the group resource
without snapshot flag.
While the resulting backups are valid regular (nonproxy) backups, correct the RMAN
script or relocate the Oracle datafiles to a supported primary storage device, as
required to enable proxy backups.
The current EMC compatibility guides provide details on the primary storage devices
supported for proxy backups with the PowerSnap Modules.
If a backup command in the RMAN script includes the proxy only option and the
Oracle data objects reside on volumes that do not support snapshots, the scheduled
backup fails since RMAN cannot perform a regular backup of the objects. The Oracle
171
Example 29
If RMAN terminates any of the proxy backups in an RMAN script, the savegroup
completion report lists failure of the scheduled backup.
If any proxy backups in an RMAN script fail, RMAN still performs a regular
backup of the corresponding archived redo logs.
A scheduled backup includes the following RMAN script, with the database files
residing on volumes that support snapshots. However, the Snapshot attribute in the
Group resource is set to False. As a result, the proxy database backup fails:
run {
allocate channel ch1 type SBT_TAPE;
allocate channel ch2 type SBT_TAPE;
backup proxy database plus archivelog;
}
Despite the proxy backup failure, RMAN performs a regular backup of the archived
redo logs. The savegroup completion report lists failure of the scheduled backup.
IMPORTANT
A proxy backup cannot be scheduled through Oracle Enterprise Manager or started
by invoking RMAN from the operating system command line. The NetWorker
PowerSnap Module documentation provides information on how to manually
invoke a scheduled backup.
Specific types of Oracle files, such as control files, cannot be backed up through a
proxy backup. This is an Oracle constraint. The Oracle documentation for the
particular Oracle Server release provides more information on the Oracle file types
that do not support proxy backups.
172
Note: During RMAN operations, do not touch any files in this directory.
173
In the NetWorker indexes, the save set name for the NWORA resource file backup is
the same as the file pathname. You can use the NetWorker mminfo command to
display the save set name. NWORA resource file backup in the NetWorker indexes
on page 176 provides information on how the backup is represented in the
NetWorker indexes.
The NWORA resource file backup can be restored by using the NetWorker recover
command or nwrecover GUI program. The NetWorker administration guide
provides more information.
Note: The file is stored under the "backup" namespace, not the "oracle" namespace.
The browse and retention policies applied to the NWORA resource file backup are
the most conservative policies associated with the given NetWorker client, not the
policies that are applied to the Oracle backups. As a result, you may see a difference
between the policies assigned to the NWORA resource file backup and the Oracle
backups.
Canceling proxy backups
Proxy backups can be canceled by using the same methods as for regular Oracle
backups. The following sections provide more information:
Type the nsrinfo command to query the NetWorker client file index. For
example:
nsrinfo -n oracle -s NetWorker_server Oracle_Server_hostname
Type the mminfo command to query the NetWorker media database. For
example:
mminfo -v -s NetWorker_server -c Oracle_Server_hostname
The NetWorker command reference guide and the UNIX man pages provide more
information on these NetWorker commands.
174
Example 30
One entry is generated for the backup piece name assigned by RMAN, such as
/PROXY_O901JB_811_1/ in Example 30 on page 175.
The third entry is generated for the Oracle datafile that is backed up to secondary
storage, for example, /JBOD13_NMO41_MVOL3/tbspc4_data1.dbf in
Example 30 on page 175. This entry is created for a live backup only.
The nsrinfo command provides information on the proxy backup entries in the
NetWorker client file index:
nsrinfo -n oracle marmaris
scanning client marmaris for all savetimes from the oracle namespace
/PROXY_O901JB_811_1/, date=1178916449 Fri May 11 13:47:28 2007
/brcmeta.1/, data=1178916446 Fri May 11 13:47:25 2007
Physical files to rollover:
/JBOD13_NMO41_MVOL3/tbspc4_data1.dbf
/JBOD13_NMO41_MVOL3/tbspc4_data1.dbf, date=1178916453 Fri May 11
13:47:31 2007
One entry is generated for the point-in-time metadata. This entry is created for an
instant backup only.
In the mminfo command output for this entry:
The Size field contains the size of the metadata stored on the NetWorker
device.
The Flag field (fl) includes the letter P, representing the point-in-time copy.
To list the entries for an instant backup only, type the following mminfo
command:
mminfo -v -c Oracle_Server_hostname -q snap
The other entry is generated for the Oracle datafile that is backed up to secondary
storage. This entry is created for a live backup only.
Both entries in the media database include the name of the RMAN backup script used
for the proxy backup, such as /space1/home/oracle/bp1 in Example 31 on page 176.
175
Example 31
The mminfo command provides information on the proxy backup entries in the
NetWorker media database:
mminfo -v -c marmaris
volume
nmo.002
snap.001
client
marmaris
marmaris
date
05/10/07
05/10/07
time
13:18:39
13:18:41
ssid
4064690015
4098244417
fl
cb
cbP
lvl
full
full
name
/space1/home/oracle/bp1
/space1/home/oracle/bp1
size
102 MB
2 KB
Example 33
client
marmaris
date
05/10/07
time
13:18:39
ssid
3863367791
fl
cb
lvl
full
name
/nsr/res/nwora.res
size
4 KB
The NetWorker command reference guide and the UNIX man pages provide more
information on these NetWorker commands.
176
Proxy backups and restores on cluster systems on page 194 provides information
on proxy restores in a cluster environment.
To create an RMAN script for a proxy restore, follow the instructions in Chapter 4,
Data Restore and Recovery.
To perform a proxy restore, the appropriate parameters must be set, as described in
Setting the parameters on page 166.
The RESTORE_TYPE_ORDER parameter
The RESTORE_TYPE_ORDER parameter setting determines the type of proxy restore
that is performed:
1. RMAN determines which backup needs to be restored and passes the required
backup piece name to NMO.
2. The RESTORE_TYPE_ORDER parameter specifies whether the backup piece is to
be restored by using one of the following:
The point-in-time copy
The copy stored on secondary storage
Example 34
177
IMPORTANT
For the RESTORE_TYPE_ORDER parameter, NMO does not support the
force_rollback option, which is supported by PowerSnap Modules. If the option is
specified, the restore fails, even if other valid restore options are also specified.
Each element of the restore path must exist. Otherwise, the restore fails. For
example, to restore a file backup to /space1/oradata/file.dbf, the path
/space1/oradata must exist.
A proxy restore of a symbolic link restores the Oracle file to the location pointed
to by the symbolic link. Both the symbolic link and the restore path must exist.
Otherwise, the restore fails.
For a rollback restore, the psrollback.res file must be set up properly, as described
in Rollback restore on page 179.
For user-specified relocation of files during a proxy restore, the relocation path
must be specified as described in Relocating files during proxy restores on
page 179.
178
Rollback restore
For a rollback restore, the psrollback.res file must contain the directory name
.nworapc. The file is located as follows:
On UNIX: /nsr/res/psrollback.res
Add the directory name to the file by using a text editor as either the root user on
UNIX or a member of the Microsoft Windows Administrators group.
The following sources provide more information on the psrollback.res file:
To enable remount of the NAS file system at the end of a rollback operation, place an
entry for the target file system in the appropriate file:
/etc/vfstab on Solaris
/etc/fstab on HP-UX
If this is not done, the remount at the end of the rollback fails. The data is recovered,
but the file system must be remounted manually and the tablespace brought back
online.
IMPORTANT
Relocation is not supported during a rollback restore. If the
RESTORE_TYPE_ORDER parameter includes the rollback value and the RMAN
restore script specifies relocation, the restore fails, even if the parameter includes
other values.
During a proxy restore, NMO supports and controls relocation, which is the restore
of datafiles (regular files or raw volumes) to a new location. The new location can be
specified by using the RMAN set newname command.
Note: During a regular Oracle restore, relocation is also supported, but it is controlled by the
Oracle Server.
179
To relocate a regular file or raw volume during a proxy restore, the set newname
command must specify the name of the relocated file as one of the following:
Example 35
The complete pathname of a symbolic link that points to the location where the
file will be restored.
IMPORTANT
The procedure to relocate a raw volume includes a restriction that does not apply
when relocating a regular file.
To relocate a raw volume, the base filename (the filename without the directory path)
of the original backed-up raw volume must be identical to one of the following:
Example 36
The base filename of the relocation path specified in the set newname command.
If the set newname command specifies a symbolic link, the base filename in the
symbolic link.
180
During a proxy database backup, Oracle backs up the control file after the proxy
backup of the datafiles is complete. In a large database production environment,
there might be a delay between the end time of the datafile backup and the start time
of the control file backup.
During this time delay, if the physical structure of the database is changed (for
example, a new datafile is added), the control file must be backed up in a separate
RMAN session before the changes occur. This is due to the fact that the control file
backup from the proxy database backup session will include information on the new
database structure.
The NetWorker indexes provide information that NMO requires to perform the
restore.
The RMAN catalog contains backup piece entries that do not have corresponding
NetWorker index entries.
The NetWorker indexes contain backup piece entries that do not have
corresponding RMAN catalog entries.
Note: If catalog synchronization is enabled for NMO, proxy backup entries in the catalogs are
synchronized automatically.
181
At the start of an instant backup, if the number of existing instant backups equals
the value of the Retain Snapshots attribute in the NetWorker Snapshot Policy
resource, the oldest instant backup is automatically expired and its NetWorker
index entries are removed.
Note: This automatic expiration and index entry removal does not apply to instant backups
specified with the nsrnmo -c client_name command.
The following sections provide more information on using this command:
- Proxy backups from a virtual cluster client on page 195
- Proxy backups from a physical cluster client on page 196
When the expiration policy for an instant backup expires, the NetWorker process
nsrim prunes the backup entries from the NetWorker indexes.
The NetWorker process nsrexecd performs consistency checking that can remove
backup entries from the NetWorker indexes.
The DBA uses a NetWorker command, such as nsrmm, to remove a save set that
includes an instant backup.
The RMAN catalog might expire backups that are required for restores.
RMAN restores might fail when RMAN attempts to restore backup pieces that
have no corresponding NetWorker index entries.
The RMAN repository can be stored in either the control file of the target database or
in an RMAN recovery catalog. An RMAN recovery catalog is an Oracle database.
Note: For proxy instant backups, use an RMAN recovery catalog instead of a control file.
Control file versus recovery catalog on page 183 provides more information.
IMPORTANT
To enable automatic catalog synchronization for proxy backups:
- The parameter ORACLE_SID must be properly set in the nsrnmo scheduled
backup script at the time of the proxy backup. Customize the nsrnmo script on
page 79 provides details.
- An NWORA resource file must include the required resources, as described in
The NWORA resource file on page 183.
The NMO program nsroraclecat uses the NWORA resources in the file to perform
automatic synchronization of the RMAN catalog and NetWorker indexes. DBAs can
also synchronize the catalogs manually by using RMAN commands.
182
IMPORTANT
If you use a control file as the RMAN catalog during an instant backup, ensure that
the control file contains enough free entries for the backup. RMAN creates a new
entry in the control file for each file backed up in an instant backup. The backup of
a large database with many files can quickly use all the free entries in the control
file and start overwriting old entries. When entries are overwritten, the
corresponding backups cannot be restored.
On UNIX: /nsr/res/nwora.res
The NWORA resource file is created by the nsrnmoadmin program when it is run for
the first time.
To enable instant backups and catalog synchronization, specific NWORA resources
must be added to the file with the nsrnmoadmin program.
Note: The NWORA resource file must not be edited manually. All resources in the file must be
added, modified, or deleted by using the nsrnmoadmin program only. The nsrnmoadmin
program must be run by either the root user on UNIX or a member of the Microsoft Windows
Administrators group.
183
Note: The parameter resources listed in Table 8 on page 184 are the only ones supported. Do
not attempt to add other parameter resources to the NWORA resource file.
Table 8
Parameter resource
Description
NSR_NWPATH
NSR_ORACLECAT_LOG_FILE
184
Undefined (default).
Valid pathname of the nsroraclecat debug
file.
Undefined (default).
Valid pathname of the nsroraclecat log file.
Table 8
Parameter resource
Description
NSR_ORACLECAT_MODE
Undetermined (default).
Enabled.
Disabled.
Note: Instant backups require the resource value
to be set to either "enabled" or "disabled". If the
value is unset, instant backups fail.
NSR_ORACLE_NLS_LANG
NSR_REMOVE_ON_FAILURE
Undetermined (default).
Valid locale value, same as set in the
NLS_LANG environment variable.
FALSE (default).
TRUE.
To view the NWORA parameter resources in the resource file, use the nsrnmoadmin
-r list command.
To modify NWORA parameter resource settings, use the nsrnmoadmin -r update
command.
Configuring the NWORA resource file with the nsrnmoadmin program on
page 188 provides details on how to use the nsrnmoadmin command.
185
Example 37
IMPORTANT
If automatic catalog synchronization is enabled, but you do not create an NWORA
SID resource for an Oracle database, the catalogs will not be synchronized during
instant backups of that database. As a result, the catalogs can become
unsynchronized unless you synchronize them manually by using RMAN
commands. Automatic catalog synchronization with the nsroraclecat program on
page 191 provides more information.
Note: Each NWORA SID resource must have a unique NSR_ORACLE_SID value.
Table 9
Parameter
Description
NSR_ORACLE_CONNECT_FILE
Undefined (default).
Valid pathname of the RMAN connection file.
NSR_ORACLE_HOME
Undefined (default).
Valid pathname of the Oracle home directory.
Note: The value must be equal to the Oracle
parameter $ORACLE_HOME value.
186
Table 9
Parameter
Description
NSR_ORACLE_LIB_PATH
Undefined (default).
Valid pathname of the Oracle shared library
directory on UNIX.
Note: This parameter is not required on
Windows.
NSR_ORACLE_SID
Undefined (default).
Valid SID value of the Oracle database.
Note: The value must be equal to the
ORACLE_SID value in the particular nsrnmo
script used for the database backup.
ORACLE_SID on page 83 provides more
information.
NSR_ORACLE_TNS_ADMIN
Undefined (default).
Valid pathname of Oracle network
configuration directory.
Note: The value must be equal to the Oracle
parameter $TNS_ADMIN value.
The following NWORA SID resource can be added for the Oracle database:
NSR_ORACLE_CONNECT_FILE=/dbapps/proddb/connect.file
NSR_ORACLE_HOME=/dbapps/proddb/app/oracle/product/10.2.0/Db_1
NSR_ORACLE_LIB_PATH=/usr/lib
NSR_ORACLE_SID=proddb
NSR_ORACLE_TNS_ADMIN=/dbapps/proddb/tns
187
IMPORTANT
A DBA must create the connection file in a secure location.
The connection file must include the following:
Note: The connection file must not include any lines starting with the # symbol.
If the connection file does not contain a connection string for an RMAN recovery
catalog, the nsroraclecat program assumes that a control file is used as the RMAN
repository during instant backups.
Example 39
If the following lines exist in the connection file, an RMAN recovery catalog is used as
the RMAN repository:
connect target sys/oracle@proddb;
connect rcvcat rman/rman@oracat;
Note: RMAN catalog deletions fail if the connection file for a backup piece does not exist or
does not contain valid connection strings.
188
On Windows 2008 and Windows Vista, you must run the nsrnmoadmin command in
the Command Prompt window as an administrator:
1. Click Start.
2. Right-click Command Prompt.
3. Select Run as administrator.
4. Run the nsrnmoadmin command in the open Command Prompt window.
The nsrnmoadmin command syntax and options related to proxy backups
The nsrnmoadmin command syntax and options used to configure proxy backup
settings are as follows:
nsrnmoadmin [-D debug_level] -r list [ResourceName | SidName]
nsrnmoadmin [-D debug_level] -r add ResourceName ResourceValue
nsrnmoadmin [-D debug_level] -r add sid=SidName home=OracleHome
connect=ConnectFilePath [lib=LibraryPath] [tns=TNSPath]
nsrnmoadmin [-D debug_level] -r update ResourceName ResourceValue
nsrnmoadmin [-D debug_level] -r update sid=SidName [home=OracleHome]
[connect=ConnectFilePath] [lib=LibraryPath] [tns=TNSPath]
nsrnmoadmin [-D debug_level] -r delete SidName
where:
Command options and settings in brackets ([ ]) are optional. Do not include the
brackets when typing the command.
189
The following sections provide examples of how to use the nsrnmoadmin command
to list, add, update, and delete NWORA resources:
The nsrnmoadmin man page on a UNIX Oracle Server that contains the NMO
software.
To display the entire NWORA resource file contents, type the following:
nsrnmoadmin -r list
190
Only one nsroraclecat program can run at a time. If two nsroraclecat programs
are started, the one started first completes its operation before the second one
proceeds.
191
To remove the RMAN catalog entries, nsroraclecat obtains information from the
NWORA resource file and generates temporary RMAN scripts that include an
RMAN change...delete command for each backup piece to be removed.
A separate script is created for all the backup pieces from the same database (or
ORACLE_SID).
The nsroraclecat program names each RMAN script as follows:
On UNIX:
/nsr/tmp/.nworapc/nsroraclecat_date_pid
On Microsoft Windows:
NetWorker_install_path\tmp\.nworapc\nsroraclecat_date_pid
where:
NetWorker_install_path is the root directory of the NetWorker installation path.
date is the current date.
pid is the nsroraclecat process ID.
The nsroraclecat program runs each script in an RMAN session. After the scripts
have finished running, the program removes them.
Note: The nsroraclecat program generates information about the backup piece entries
removed from the RMAN catalog. The information is written to the nsroraclecat log and debug
files. NSR_ORACLECAT_LOG_FILE and NSR_ORACLECAT_DEBUG_FILE on page 184
provide more information on these files.
The nsroraclecat man page on a UNIX Oracle Server that contains the NMO
software.
The nsroraclecat entry in the NetWorker Module for Oracle command reference
guide on the Powerlink website.
The nsroraclecat program cannot connect to the NetWorker server to query the
NetWorker indexes.
The nsroraclecat program cannot locate the required backup pieces in the
NetWorker indexes.
To diagnose the cause of a nsroraclecat program failure, review the nsroraclecat log
files specified by NSR_ORACLECAT_DEBUG_FILE and
NSR_ORACLECAT_LOG_FILE. The operations log file is
/nsr/applogs/nsroraclecat.log by default.
If the nsroraclecat program fails, the nsrsnapck program removes the corresponding
NetWorker index entries by using the procedures described in NetWorker index
entry removals with nsrsnapck on page 193.
192
Files in either the temporary directory /tmp on UNIX or the temporary directory
specified by the TEMP system variable on Microsoft Windows, where the files
have the name nwora_bp_sid_pid:
sid is an ORACLE_SID value.
pid is a nsroraclecat process ID.
IMPORTANT
After a nsroraclecat program failure occurs or while catalog synchronization is
disabled, the DBA must synchronize the catalogs manually by using specific
RMAN commands. The appropriate Oracle documentation provides more
information.
IMPORTANT
The NSR_REMOVE_ON_FAILURE setting controls the result of the nsroraclecat
program failure to remove RMAN catalog entries.
- In general, NSR_REMOVE_ON_FAILURE should be set to TRUE, to enable
NetWorker index entries to be removed, even if the RMAN catalog entries are not
removed. Otherwise, if entries are not removed from the NetWorker indexes, the
snapshot resources are not freed and subsequent backups might fail.
- If RMAN backup optimization is enabled, NSR_REMOVE_ON_FAILURE
should be set to FALSE, to prevent the removal of NetWorker index entries.
Otherwise, RMAN might skip backing up certain files.
193
When the nsroraclecat program fails to run properly, the nsrsnapck programs
actions depend on whether the instant backup on the primary storage is intact:
If the instant backup on the primary storage is intact, the nsrsnapck program
does not remove any entries from the NetWorker indexes and generates an error
message about the failure in the following file:
On UNIX: /nsr/logs/daemon.raw
On Microsoft Windows: NetWorker_install_path\logs\daemon.raw, where
NetWorker_install_path is the root directory of the NetWorker installation path
The NetWorker administration guide provides more information on the
daemon.raw log file and how to view its contents.
IMPORTANT
The parameter NSR_CLIENT is not supported for proxy backups on a cluster
system. This parameter is used for restores and regular Oracle backups on a cluster
system, as described in Chapter 6, Cluster and RAC Systems.
Review the following information, specific to proxy operations on a cluster system:
194
195
Notes:
The host specified with -c client_name must have access to instant backups.
NMO and the PowerSnap Module must be installed and configured on the
host specified with -c client_name.
When the backup is started from the virtual cluster client, the backup entries
are stored in the NetWorker client file index of the virtual client by default.
The entries for the NWORA resource file backup are always stored in the
NetWorker index of the physical client.
Example 40
To specify that the backup entries be stored in the index of the physical cluster client
mars.emc.com, where the script name is nsrnmo, specify the following in the Backup
Command attribute:
nsrnmo -c mars.emc.com
When the backup is started from the physical client, the backup entries are stored in
the NetWorker index of the physical client by default.
Note: The entries for the NWORA resource file backup are always stored in the NetWorker
index of the physical client.
To specify that the proxy backup entries be stored in a NetWorker client file index
other than the physical client index, for example, in a virtual client index:
Add -c client_name to the nsrnmo script name in the Backup Command attribute in
the Client resource.
Specify the Oracle user from the physical host in the Remote Access attribute in
the Client resource for client_name.
The expiration of instant backups created with the nsrnmo -c client_name command
differs from the expiration of instant backups created without the -c option.
Removing instant backup entries from the NetWorker indexes on page 182
provides details on the expiration and removal of backups specified with nsrnmo -c
client_name.
Notes:
196
The host specified with -c client_name must have access to instant backups.
NMO and the PowerSnap Module must be installed and configured on the host
specified with -c client_name.
Example 41
To specify that the backup entries be stored in the index of the virtual client
monalisa.emc.com, where the script name is nsrnmo, specify the following in the
Backup Command attribute:
nsrnmo -c monalisa.emc.com
197
198
A
Parameters in an RMAN
Session
199
The NSR* parameters described in Table 10 on page 201 are parameters specific to
NetWorker that can be set for an RMAN session of:
An Oracle restore.
To ensure that the required NSR* parameters are set during an NMO backup or
restore, set them in one of the following ways unless specified otherwise in Table 10
on page 201:
If using automatic channels, set the parameters with the parms option in the
configure channel command.
Automatic channel allocation on page 26 provides more information on
automatic channels.
If not using automatic channels, set the parameters with the RMAN send
command (recommended), as one of the following:
The rman send command on the operating system command line.
The send command in the RMAN session or script.
Do not mix these different ways of setting the NSR* parameters in the same RMAN
session. The use of a UNIX setenv command or Windows set command on the
operating system command line to set the NSR* parameters has no effect.
On Windows, when an NSR* parameter is set through the parms option, the value of
that NSR* parameter remains in effect for all subsequent allocated channels, and for
all subsequent RMAN sessions until one of the following occurs:
The NSR* parameter is unset for the channel by using the parms option, as in the
following example:
run {
allocate channel t1 type SBT_TAPE
parms ENV=(NSR_SERVER=,NSR_DATA_VOLUME_POOL=);
:
:
release channel t1;
}
Note: On Windows, this does not occur if the parameters are set through the send command in
all RMAN sessions.
200
Table 10
Parameter
Description
NSR_AES_ENCRYPTION
NSR_CLIENT
NSR_COMPRESSION
201
Table 10
Parameter
Description
NSR_DATA_VOLUME_POOL
Undefined (default).
A valid NetWorker pool name.
The name must be different from the name used by
the parameter NSR_DATA_VOLUME_POOL,
NSR_DATA_VOLUME_POOL2, or
NSR_DATA_VOLUME_POOL3.
Undefined (default).
A valid NetWorker pool name.
The name must be different from the name used by
the parameter NSR_DATA_VOLUME_POOL,
NSR_DATA_VOLUME_POOL1, or
NSR_DATA_VOLUME_POOL3.
202
Undefined (default).
A valid NetWorker pool name.
The name must be different from the name used by
the parameter NSR_DATA_VOLUME_POOL,
NSR_DATA_VOLUME_POOL1, or
NSR_DATA_VOLUME_POOL2.
Table 10
Parameter
Description
NSR_DEBUG_FILE
Undefined (default).
The valid pathname of the debug file to use on the
Oracle Server.
NSR_DEBUG_LEVEL
NSR_DEDUP_BACKUP
NSR_DEDUP_CACHE_ENABLED
203
Table 10
Parameter
Description
NSR_DEDUP_CACHE_TAG
NSR_DEDUP_CHUNK_SIZE
Undefined (default).
Avamar server hostname set in the NetWorker
De-duplication Node resource.
204
Table 10
Parameter
Description
NSR_ENCRYPTION_PHRASES
Undefined (default).
One or more encryption phrases to use during an
Oracle restore with NMO. Each phrase must be a
string enclosed in quotes. Multiple phrases must be
separated by commas, and the entire group of
phrases surrounded by outer quotes that are
different from the inner quotes. For example:
NSR_ENCRYPTION_PHRASES="key1,key2"
- NMO itself supports double ("), single (), and
backward () quotes.
- Certain shells might not support certain types of
quotes, for example, when the parameter is set
with the send command on the command line.
- Oracle does not support the use of single quotes
within an RMAN script.
NSR_MMDB_RETRY_TIME
NSR_NO_BUSY_ERRORS
205
Table 10
Parameter
Description
NSR_NWPATH
NSR_RECOVER_POOL
Undefined (default).
A valid pathname of the configuration file.
Note: If undefined or an invalid pathname, parameter
settings in the preferred configuration file are ignored.
Undefined (default).
A valid name of a NetWorker volume pool that
contains a cloned backup to use for a restore.
NSR_SAVESET_BROWSE
206
Table 10
Parameter
Description
NSR_SAVESET_RETENTION
Undefined (default).
A valid name of a NetWorker server NIC.
207
208
B
RMAN Commands
RMAN Commands
209
RMAN Commands
IMPORTANT
NMO does not support the pool option of the RMAN backup command, with the
exception of pool=0.
If any nonzero value is specified for the pool option of the RMAN backup command,
the RMAN session terminates and NMO returns the following error message:
sbtbackup: Oracle pools are not supported
NMO error messages on page 222 provides more information on this error
message.
To specify the NetWorker volume pool to be used by NMO, set the parameter
NSR_DATA_VOLUME_POOL in the RMAN script. Appendix A, Parameters in an
RMAN Session, provides more information.
210
RMAN Commands
Note: In the following sections, brackets ([]) are used to denote the optional portions of a
command, for example, command options and corresponding settings. When typing the
command, do not include the brackets.
Syntax rules
The send command must have the following format:
send [ device_type device_specifier | channel channel_id ]
NSR_ENV=(name1=value1 [, name2=value2, ...])
These sections describe the syntax rules for the two main parts of the send command:
The maximum length of the command string is restricted by Oracle to 512 bytes,
including the terminating NULL.
The NSR_ENV keyword and the parameter names must be all uppercase.
Between the NSR_ENV keyword and left parenthesis, an equal sign and spaces
are optional. For example, these commands are all correct:
send
send
send
send
NSR_ENV = (NSR_SERVER=server1)
NSR_ENV=(NSR_SERVER=server1)
NSR_ENV (NSR_SERVER=server1)
NSR_ENV(NSR_SERVER=server1)
Inside the parentheses, there must be one or more NMO parameter names and the
corresponding parameter values.
Inside the parentheses, spaces are not allowed around the equal signs. A space
before an equal sign becomes part of the parameter name. A space after an equal
sign becomes part of the parameters value.
211
RMAN Commands
Comments are not allowed inside the quotes. In the following example,
# NSR_SERVER is considered the first parameters name:
run {
allocate channel t1 type SBT_TAPE;
send NSR_ENV=(
# NSR_SERVER=server1,
NSR_CLIENT=oracle);
:
A send command in an RMAN script can span multiple lines. For example:
send NSR_ENV=(
NSR_SERVER=server1,
NSR_CLIENT=oracle);
send with no option (only the quoted command string) sets the parameters for all
allocated channels.
send device_type SBT_TAPE sets the parameters for all channels of the backup
tape device.
Note: The send command has no effect with device type disk.
send channel sets the parameters for the specified channels only.
IMPORTANT
The device_type or the channel option can be used in the send command in an
RMAN script only. Neither option can be used in the send command on the
operating system command line. The send command on the operating system
command line on page 213 provides more information.
Example 42
In the following sample script, the parameters are set for channel t1 only, not for
channel t2:
run {
allocate channel t1 type SBT_TAPE;
allocate channel t2 type SBT_TAPE;
send channel t1 NSR_ENV=(NSR_SERVER=server1,
NSR_DATA_VOLUME_POOL=MondayFulls);
:
}
212
RMAN Commands
Table 11 on page 213 lists the values for options used with the send command. The
example referred to is Example 42 on page 212.
Table 11
Describes
device_specifier
The device type as specified in an allocate channel command in the RMAN script. For a
backup tape device, use SBT_TAPE.
channel_id
The channel identifier as specified in an allocate channel command in the RMAN script. In
the example, the identifier is t1.
name1
The first NMO parameter name. In the example, the first parameter name is
NSR_SERVER.
value1
The value assigned to the first parameter. In the example, the first value is server1.
name2
The second NMO parameter name. In the example, the second parameter name is
NSR_DATA_VOLUME_POOL.
value2
The value assigned to the second parameter. In the example, the second value is
MondayFulls.
In the run job of the RMAN script, as described in The send command in the
RMAN script on page 214.
If more than one send option appears in the rman command, only the last send
command is executed.
Follow all the send command syntax rules listed in The send command string
on page 211, except for the last rule, which applies only to a send command in an
RMAN script.
Do not use either the device_type or channel option. The send command
options on page 212 provides more information.
Use two sets of quotes around the command string, each set consisting of a single
and double quote. The single quote can be either before or after the double quote,
but the second set of quotes must be opposite to the first set. For example, this
command is also correct:
rman send NSR_ENV=(name1=value1[, name2=value2, ...])
Two sets of quotes are required to prevent some operating system shells (for
example, ksh) from treating spaces inside the quotes as meta (special) characters
and attempting to tokenize the string.
213
RMAN Commands
Example 43
The parameter values in the quoted string are applied to all channels allocated
during the RMAN session. These values are applied before any parameter values
specified in send commands within the RMAN script itself. Precedence rules
on page 215 provides more information.
(RMAN script:)
run {
allocate channel t1 type SBT_TAPE;
allocate channel t2 type SBT_TAPE;
allocate channel t3 type SBT_TAPE;
:
}
Follow all the send command syntax rules listed in The send command string
on page 211.
Use either the device_type or channel option (if required) with the send
command in an RMAN script, as described in The send command options on
page 212.
Specify the correct option values in the send command, as described in The send
command options on page 212.
RMAN commands are run in the order that they appear in the backup or restore
script. For a parameter value to be in effect during a backup or restore, put the
send command (setting the value) before the backup or restore command in the
script, but after the allocate channel commands for those channels to which the
parameter value applies.
The following sample RMAN script performs an Oracle backup of the entire database
to the volume pool MondayFulls of the (remote) NetWorker server mars.emc.com:
run {
allocate channel t1 type SBT_TAPE;
allocate channel t2 type SBT_TAPE;
send NSR_ENV=(NSR_SERVER=mars.emc.com,
NSR_DATA_VOLUME_POOL=MondayFulls);
backup full filesperset 4
format FULL_%d_%U
(database);
release channel t1;
release channel t2;
}
This script is the same as the sample script on page 75. The single send command sets
the parameters for both channels.
214
RMAN Commands
Precedence rules
Parameters are set for channels allocated during the RMAN session in the following
order:
1. In the parms option in the allocate channel or configure channel command
(configure channel is used only for automatic channel allocation).
2. In the rman send command on the operating system command line.
3. In the send command in the run job of the RMAN script.
IMPORTANT
If both the send command on the operating system command line and the send
option in the configure channel command are used at the same time, only the send
option in the configure channel command is executed by Oracle.
To prevent confusion and simplify the task of setting parameters in a specific order,
do not mix these different ways of setting parameters in the same RMAN session.
Example 44
In the following example, the parameters NSR_SERVER and NSR_CLIENT are set in
this order:
NSR_SERVER is set to server1 (by rman send), changed to server2 (by the first
send command), and finally changed to server3 (by send channel).
NSR_CLIENT is set to client1 (by rman send), changed to client2 (by the first
send command), and finally changed to client3 (by send channel):
rman send NSR_ENV=(NSR_SERVER=server1, NSR_CLIENT=client1)
(RMAN script:)
run {
allocate channel t1 type SBT_TAPE;
send NSR_ENV=(NSR_SERVER=server2, NSR_CLIENT=client2);
send channel t1 NSR_ENV=(NSR_SERVER=server3,
NSR_CLIENT=client3);
:
}
215
RMAN Commands
Table 12 on page 216 describes the results of setting duplex to each of the valid
values.
Table 12
set duplex=1
set duplex=2
or
set duplex=on
Two copies of the backup set are directed to the separate pools specified by
NSR_DATA_VOLUME_POOL and NSR_DATA_VOLUME_POOL1.
These two pools must be different.
set duplex=3
Three copies of the backup set are directed to the separate pools specified by
NSR_DATA_VOLUME_POOL, NSR_DATA_VOLUME_POOL1, and
NSR_DATA_VOLUME_POOL2.
These three pools must be different.
set duplex=4
Four copies of the backup set are directed to the separate pools specified by
NSR_DATA_VOLUME_POOL, NSR_DATA_VOLUME_POOL1,
NSR_DATA_VOLUME_POOL2, and NSR_DATA_VOLUME_POOL3.
These four pools must be different.
During an Oracle restore, RMAN selects only one of the copies to use, and if it fails
for some reason, the restore fails. If the first copy of a backup piece cannot be found in
NMO, RMAN issues the following type of error message:
RMAN-10035: exception raised in RPC: ORA-19507: failed to retrieve
sequential file, handle="CH2_bkup3_1_1"
To force RMAN to use the duplexed copy of this missing backup piece, run the
change...crosscheck, crosscheck, or change backuppiece...unavailable command
and retry the restore. These commands cause RMAN to mark the missing backup
piece as expired (Retention policies on page 38 provides a definition of expired) and
to use the duplexed copy for the restore operation.
216
RMAN Commands
On UNIX: /nsr/applogs/nmo.messages.raw
Conditions traced
0 (default)
217
RMAN Commands
218
C
Troubleshooting and
Error Messages
219
Troubleshooting tips
The following list of troubleshooting tips refers to sections of this administration
guide and the NetWorker Module for Oracle installation guide. Use the following list
to troubleshoot any problems in running Oracle backup and restore operations with
NetWorker Module for Oracle (NMO).
To set up an Oracle backup and restore system correctly:
1. Verify that the combination of the operating system, Oracle Server, NetWorker
server, and NetWorker client is supported.
The NetWorker Module for Oracle installation guide provides information on
installation requirements.
2. Configure the Oracle Server and Net service (if used) according to the
instructions in the Oracle documentation. Verify the Oracle Server
configuration on page 63 provides more information.
Without NMO installed on the Oracle Server host, it should be possible to
perform a backup and restore by using the allocate channel t1 type disk
command.
3. Install and configure the NetWorker server and client software.
The following sources provide more information:
NetWorker installation guide
NetWorker administration guide
Chapter 2, Software Configuration
4. Install and enable the NMO software according to the instructions in the
NetWorker Module for Oracle installation guide.
To relink the library file on UNIX, use the linking commands listed in the
installation guide. Use the correct libnwora.* library file.
To verify the version of NMO installed, check the version of the nsrnmostart
program file or libnwora.* library file:
On UNIX, use one of the following commands, where filenm is either the
nsrnmostart or libnwora.* filename:
what filenm
strings filenm | grep @(#)
pkginfo -l LGTOnmo (Solaris only)
On Windows:
a. Find the nsrnmostart.exe or libwora.dll file.
b. Right-click the file icon and select Properties.
c. In the Properties window, click the Version tab and view the file version
information.
Compare the library file with the libnwora.* file in the NMO software package;
the two files should be identical. Ensure that Oracle is not linked to another
libnwora.*, libobk.* (NetWorker BusinesSuite Module for Oracle version of
libnwora.*), or liblsm.* (from Legato Storage Manager or Legato Single Server
Version) file.
220
5. Perform a manual Oracle backup by using NMO and the proper RMAN script.
Set the required NSR* parameters in either the RMAN backup script or the rman
send command on the operating system command line. Appendix A,
Parameters in an RMAN Session, provides information on how to set the NSR*
parameters. RMAN scripts for manual backups on page 75 provides a simple
startup RMAN script.
If the manual backup fails, check the debug files for NMO and the NetWorker
server. For NMO debug information, set the parameters NSR_DEBUG_FILE and
NSR_DEBUG_LEVEL. NMO error messages on page 222 provides more
information.
If the backup fails with the following error, ensure that both NMO and Oracle
have the same bitness, and refer to the RMAN user guide for details on how to
test that the media management library is integrated correctly:
ORA-19554: error allocating device, device type: SBT_TAPE, device
name:
ORA-27211: Failed to load Media Management Library
Additional information: 25
6. Perform a scheduled Oracle backup by using NMO and the proper RMAN and
nsrnmo scripts.
In the working RMAN manual backup script, add the connect target and connect
rcvcat commands, as described in RMAN scripts for scheduled backups on
page 77. Customize the nsrnmo script, as described in Customize the nsrnmo
script on page 79.
If the manual backup succeeds but the scheduled backup fails, set the parameter
NSR_SB_DEBUG_FILE to generate debug information for the scheduled backup.
RMAN error messages on page 221 provides more information.
For a manual Oracle backup, specify the msglog option in the rman command on
the command line:
rman target ... rcvcat ... msglog filename
For a scheduled Oracle backup, specify the msglog option in the parameter
NSR_RMAN_ARGUMENTS in the nsrnmo script.
NSR_RMAN_ARGUMENTS on page 82 provides more information.
The appropriate Oracle error messages guide provides more information on specific
RMAN error messages and recommended courses of action.
Note: During a backup on AIX or Windows, if an NMO parameter is set to an invalid value, the
resulting error message might be truncated in the RMAN output. This is due to an Oracle
RMAN limitation.
221
On UNIX: /nsr/applogs/nmo.messages.raw
If the parameter NSR_SB_DEBUG_FILE is not set in the nsrnmo script file, the debug
information is not written. NSR_SB_DEBUG_FILE on page 83 provides more
information.
222
The NetWorker server also writes diagnostic information from the manual or
scheduled Oracle backup to specific log files on the NetWorker server. The
NetWorker administration guide provides more information on these log files.
NMO error messages can be grouped into categories, according to the program that
generates the message and the message format:
where:
function_name is the name of the NMO function that produced the error.
error_type, error_code, error_number are internal numbers that represent an error type
or code. Their significance for the user is as follows:
If error_code is 1, the system is out of memory.
If error_code is 3, 13, or 17, a code-level error has occurred. Report the error
message to Technical Support.
Table 14
Error message
Description
Resolution
223
Table 14
Error message
Description
Resolution
224
Table 14
Error message
Description
Resolution
225
Table 14
Error message
Description
Resolution
The call to nsr_start() failed with the message: A call of the NetWorker core function, nsr_rtart(),
failed due to the given reason.
reason
The current time could not be obtained (errno). NMO could not obtain the current time due to an
operating system error.
The data could not be XDR'd from the stream. The incoming recover stream of data could not be
decoded due to a possible network error or data
corruption.
226
Table 14
Error message
Description
Resolution
227
Table 14
Error message
Description
Resolution
A proxy backup failed because the file filename is Perform a proxy backup of a supported type of
not a data fileneither a raw file nor a regular file. data file only.
228
Table 14
Error message
Description
Resolution
229
Table 14
Error message
Description
Resolution
230
Table 14
Error message
Description
Resolution
where error_message is the text of the error message, as shown in the table.
Table 15
Error message
Description
Command line arguments are not understood. The nsrnmoadmin command included one or
more invalid options.
Resolution
Use the nsrnmoadmin command with the correct
options. Configuring the NWORA resource file
with the nsrnmoadmin program on page 188
provides details.
Could not open resource file 'filename' (errno). The nsrnmoadmin command could not open the
NWORA resource file, possibly due invalid
permissions.
231
Table 15
Error message
Description
Resolution
232
Table 15
Error message
Description
Resolution
where error_message is the text of the error message, as shown in the table.
233
Table 16
Error message
Description
Resolution
234
Error message
Description
Resolution
235
Error message
Description
Resolution
Authentication denied
or
Authentication denied for user username
236
Glossary
This glossary contains the definitions of terms found in this manual. Most of the
terms are specific to the NetWorker Module for Oracle (NMO) software. For terms
specific to the NetWorker software, refer to the latest NetWorker administration
guide.
A
?
administrator
Administrators group
API (application
programming
interface)
Oracle placeholder for the main directory of the Oracle database instance identified as
$ORACLE_HOME.
Person who normally installs, configures, and maintains software on network
computers, and who adds users and defines user privileges.
Microsoft Windows user group whose members have the rights and privileges of
users in other groups, plus the ability to create, modify, and manage the users and
groups in the domain.
Agreed-upon set of computer library routines, protocols, and tools used to
communicate and accomplish tasks within software applications.
ASM (application
specific module)
Program that, when used in a directive, specifies the way a set of files or directories is
to be backed up and recovered.
Archived copy of a filled online Oracle redo log that preserves older redo log data for
recovery operations. See also redo log.
attribute
auto media
management
autochanger
B
backup
Operation that saves data to a volume. An Oracle backup of several datafiles may
include several backup sets.
237
Glossary
backup cycle
backup group
See group.
backup host
backup level
Backup Operators
group
backup piece
backup set
backup volume
bootstrap
browse policy
C
catalog
synchronization
client
client file index
cluster
connection port
238
Process that removes a proxy Oracle backup entry from the RMAN catalog when the
corresponding backup piece is removed from the NetWorker indexes. See NWORA
resource file.
Computer, workstation, or fileserver whose data can be backed up and restored.
Database maintained by the NetWorker server that tracks every data object, file, or
file system backed up. The NetWorker server maintains a single index file for each
client computer.
Two or more independent network servers that operate and appear to clients as if
they are a single unit. The cluster configuration enables work to be shifted from one
server to another, providing "high availability" that allows application services to
continue despite most hardware or software failures. See also high-availability
system.
See offline backup.
Line on a display screen, also known as a command prompt or shell prompt, where
you type software commands.
Port that NetWorker processes use to perform backup and restore sessions through a
firewall.
Glossary
D
daemon
Process on UNIX systems that runs in the background and performs a specified
operation at predefined times or in response to certain events.
database
DBA
DBMS
Abbreviation for database administrator, the person that is typically responsible for
installing, configuring, and maintaining Oracle database systems.
Abbreviation for database management system, which refers to the primary
architecture of an Oracle database.
deduplication
backup
device
Storage unit that reads from and writes to backup volumes (see volume) during
backups and restores. The storage unit can be a tape device, optical drive,
autochanger, or file connected to the server or storage node.
When dynamic drive sharing (DDS) is enabled, refers to the access path to the
physical drive.
directive
Instruction that directs NetWorker software to take special actions on a given set of
files for a specified client during a backup or recovery operation. Directives are
ignored in manual (unscheduled) backups.
drive
Hardware device through which media can be read or written to. See also device.
E
enabler code
event-based backup
exit code
expiration date
expired save set
Special code that activates the software. The enabler code that unlocks the base
features for software is called a base enabler. Enabler codes for additional features or
products (for example, library support) are called add-on enablers.
See probe-based backup.
Indicator that specifies whether a backup or restore session succeeded.
Nonzero exit code indicates the session did not complete successfully.
Date when the status of a volume changes from read/write to read-only.
Save set whose browse time has been reached. The save set can no longer be browsed
because it has been removed from the client file index.
239
Glossary
F
failover
file index
file system
fileserver
firewall
full backup
Software interface used to save, retrieve, and manage files on storage media by
providing directory structures, data transfer methods, and file association.
Entire set of all files.
Computer with disks that provides services to other computers on the network.
System designed to prevent unauthorized access to or from a private network. All
messages entering or leaving the intranet pass through the firewall, which examines
each message and blocks those that do not meet the specified security criteria. There
are several types of firewall techniques. The NetWorker software supports client
backups from computers that are protected by packet filtering.
See level.
G
group
H
high-availability
system
host
hot Oracle backup
I
I18N
(internationalization)
immediate live
backup
Type of proxy Oracle backup where a point-in-time copy (snapshot) is created during
an instant backup and immediately backed up to secondary storage, such as tape. The
snapshot is automatically deleted from the primary storage.
incremental backup
index policy
instance
240
See level.
Policy that specifies how long file and data index entries should remain valid. Clients
specify which index policies they wish to use.
Combination of processes that runs each time a database starts up.
Glossary
instant backup
Type of proxy backup that creates a snapshot of Oracle data as a point-in-time copy
on a primary storage unit. See proxy backup.
instant restore
Type of proxy restore that restores Oracle data from a mounted point-in-time copy
that was created during an instant backup. See proxy restore.
L
L10N (localization)
Capability of the NMO software to generate non-ASCII character and numeric data
based on the locale of the user, and output the data to the user interface. This
capability requires the installation of the appropriate NMO language packs in
non-English locales. See also I18N (internationalization).
level
Backup configuration option that specifies how much data is saved during a
scheduled or manual backup. An NMO backup level is specified by an RMAN
command in the RMAN backup script only:
A full NMO backup backs up all of the data blocks in the database, regardless of
when they last changed.
An incremental NMO backup backs up only data blocks that have changed since
the last backup.
library
license enabler
live backup
Hardware device containing one or more removable media drives, as well as slots for
pieces of media, media access ports, and a robotic mechanism for moving pieces of
media between these components. Libraries automate media loading and mounting
functions during backup and recovery. The term library is synonymous with
autochanger, autoloader, carousel, datawheel, jukebox, and near-line storage.
Enabler code that is required to run a feature or product.
One of the following two types of proxy Oracle backup:
deferred live backup
M
manual backup
Backup that a user performs from the client, also known as an unscheduled backup.
The user specifies the files, file systems, and directories to be backed up. A manual
backup does not generate a bootstrap save set.
media
Physical storage, such as magnetic tape, optical disk, or file system, to which backup
data is written. See also volume.
media database
media index
media manager
media pool
MML (media
management library)
Database that contains indexed entries about the storage volume location and the
lifecycle status of all data and volumes the NetWorker server manages. See also
volume.
See media database.
NetWorker database that tracks save sets stored on backup volumes.
Feature to sort backup data to selected storage volumes.
Library of media management routines provided by the NMO software and linked
with the Oracle kernel software during the installation of NMO on the Oracle Server
host.
241
Glossary
mount
multiplexing
To make a database available for use, or to place a removable tape or disk volume
into a drive for reading or writing.
Set time required to perform an instance or media recovery for an Oracle database.
For example, you might set 10 minutes as the goal for media recovery from a disk
failure.
NetWorker feature that permits data from more than one save set to be
simultaneously written to the same storage device.
N
NetWorker
NetWorker client
NetWorker Module for
Oracle
NetWorker resource
NetWorker server
NetWorker storage
node
NMO
notification
nsrhost
NWORA resource file
Network-based EMC software product that backs up and restores file systems.
See client.
NetWorker add-on module for the NetWorker server software that enables backups
and restores of an Oracle DBMS. See also NMO.
See resource.
See server.
See storage node.
Abbreviation for NetWorker Module for Oracle.
Message generated and sent to the NetWorker administrator about important
NetWorker events.
Logical hostname of the computer that is the NetWorker server.
Resource file installed during the NMO installation, which must be extended to
include specific additional resources to enable proxy Oracle backups and (optionally)
catalog synchronization.
O
offline backup
Offline Oracle backup performed while the Oracle instance is shut down and
unavailable to users.
online backup
Online Oracle backup performed while the Oracle instance is running and available
to users.
online indexes
Databases located on the NetWorker server that contain all the information
pertaining to the client backups (client file index) and backup volumes (media
database).
operator
242
Person who monitors the server status, loads backup volumes into storage devices,
and executes the day-to-day NetWorker tasks.
Oracle Enterprise
Manager
Oracle10g Server
Glossary
Oracle11g Server
override
P
parallelism
Method that backs up or restores data for multiple clients, or multiple save sets for
one client, at the same time.
pathname
An absolute pathname indicates how to find a file starting from the root directory
and working down the directory tree.
A relative pathname indicates how to find a file starting from the current location.
physical host
point-in-time copy
Fully usable copy of a defined collection of data, such as a consistent file system,
database, or volume, which contains an image of the data as it appeared at a single
point in time. A point-in-time (PiT) copy is also called a shadow copy or a snapshot.
A snapshot of Oracle data is created on a supported type of primary storage during
an instant backup.
policy
Set of constraints that specify how long the save sets for a client are available for
recovery:
For a regular Oracle backup and proxy live backup, the NetWorker Client
resource specifies a browse policy and a retention policy. The nsr_policy(5) man
page and NetWorker command reference guide provide more information.
For a proxy instant backup, the NetWorker Group resource specifies a snapshot
policy that is configured with a Snapshot Policy resource. The NetWorker
PowerSnap Module documentation provides more information.
policy uniformity
pool
PowerSnap
PowerSnap Module
preconfigured
primary storage
probe
Consistency of the browse and retention policies in a group of co-dependent save sets
from the same scheduled backup cycle or save set bundle, enforced by NMO to
ensure that incremental backups do not persist after other backups they depend on
have expired.
Feature to sort backup data to selected storage volumes.
EMC technology that provides point-in-time snapshots of data to be backed up.
Applications that are running on the host system continue to write data during the
snapshot operation, and data from open files is included in the snapshots.
EMC software module that exports services of a storage subsystem by interfacing
with vendor-specific APIs. The module is independent of applications and backup
and recovery interfaces. NMO operates with a PowerSnap Module to perform proxy
Oracle backups.
Initial default selections or configurations for software features.
Server storage subsystem that contains the Oracle source data and any persistent
snapshot backups of the data. The NetWorker PowerSnap Module documentation
provides information on the supported types of primary storage.
Query operation to determine if a specified condition is met on a client.
243
Glossary
probe-based backup
proxy client
Host used in proxy Oracle backups that is separate from the Oracle Server host, with
access to the primary storage unit. During a proxy live backup, either the Oracle
Server host or proxy client host backs up an Oracle database point-in-time copy
(snapshot) to secondary storage.
proxy backup
proxy restore
Restore of Oracle data from a proxy Oracle backup through the PowerSnap Module.
Three types of proxy Oracle restore are the instant restore, rollback restore, and
restore from secondary storage.
purging
Process of deleting all entries for files on a volume from the client file index, but
allowing entries for the save sets to remain in the media database.
R
RDBMS (relational
database
management system)
recover
Recovery Catalog
To apply archived redo logs and online redo logs to an Oracle database to make the
database consistent with a given point in time.
Collection of Oracle database tables maintained by RMAN, including information
about Oracle backup sets and pieces, image and proxy copies, archived redo logs,
stored scripts, and the target database schema.
Save set whose browse and retention policies have expired. Recyclable save sets are
removed from the media database.
recyclable volume
Volume whose data has exceeded both its browse and retention policies and is now
available to be relabeled and reused.
redo log
remote device
resource
244
Online log of an Oracle database, consisting of at least two redo log files (separate
from the datafiles) that record all the most current changes made in the database
instance. See also archived redo log.
Storage device that is attached to a NetWorker storage node.
Component of either the NetWorker server configuration or the NWORA resource
file:
The NWORA resource file contains resources that enable proxy backups and
(optionally) catalog synchronization.
Glossary
resource database
restore
restore from
secondary storage
retention policy
RMAN (Recovery
Manager)
Oracle utility that acts as an intelligent interface to Oracle databases and works with
third-party media management products, such as NMO, to back up and restore
Oracle database objects.
RMAN catalog
RMAN repository that stores information about each Oracle backup piece in either a
control file of the target database or an RMAN Recovery Catalog.
RMAN script
rollback restore
Type of proxy Oracle restore that restores a specific point-in-time copy (snapshot) of
Oracle data to the source location by using the hardwares particular capabilities. A
rollback is a destructive save set restore. See proxy restore.
Save set that is backed up to tape from a snapshot. Whether this snapshot is retained
or not depends on a snapshot policy. When a snapshot is rolled over to tape, entries
are made in the client file index and media database, which enable the save set to be
browsed for restore.
root
RPC (remote
procedure call)
Protocol that the NetWorker server uses to perform client requests over a network.
S
save
NetWorker command that backs up client files to backup volumes and makes data
entries in the online index.
save set
Group of files or a file system from a single client computer, which is backed up on
storage media.
Group of co-dependent save sets from the same scheduled backup cycle of an Oracle
database object, assembled by NMO into a bundle according to configuration
settings.
Creation, during an incremental scheduled NMO backup, of a combined save set
bundle from co-dependent save sets in different save set bundles.
Process whereby NMO automatically creates a save set bundle for each scheduled
backup cycle of an Oracle database object, by grouping all the dependent save sets
from the same backup cycle into a save set bundle.
245
Glossary
save set ID
save set status
save stream
Data and save set information that is written to a storage volume during a backup. A
save stream originates from a single save set.
scanner
NetWorker command used to read a backup volume when the online indexes are not
available.
scheduled backup
scheduled backup
cycle
Full or level 0 backup of an Oracle database object and all the subsequent incremental
backups that are dependent on the level 0 backup. If save set bundling is enabled, a
separate save set bundle is created for each scheduled backup cycle.
secondary storage
Storage library attached to the NetWorker server or storage node, used to store
traditional or snapshot backups.
server
Computer on a network that runs the NetWorker server software, contains the online
indexes, and provides backup and restore services to the clients and storage nodes on
the same network.
server index
File that lists all the server files backed up during a scheduled backup.
service port
Port used by a server or storage node to listen for backup and restore requests from
clients through a firewall.
shared disk
shell prompt
silo
Unique name for an Oracle database instance. This value is typically set in an
ORACLE_SID parameter.
Repository for holding hundreds or thousands of volumes. Silo volumes are
identified by barcodes, not by slot numbers.
skip
Backup level in which designated files are skipped and not backed up. See also
level.
snap set
Group of files, volumes, or file systems from a single client that describes the
collection of data for which a point-in-time copy is created on an external disk
subsystem, such as a storage array.
snapshot
snapshot policy
246
Glossary
ssid
staging
stand-alone device
storage device
storage node
system administrator
T
tablespace
target database
temporary enabler
Code that enables operation of the NMO software for an additional 45 days beyond
the evaluation period.
TNS (Transparent
Network Substrate)
traditional restore
traditional storage
Type of proxy Oracle restore, performed as a regular Oracle restore that restores a
point-in-time copy from a secondary storage medium, such as tape. See proxy
restore.
See secondary storage.
U
unscheduled backup
user
V
versions
volume
Backup volume used to store backup data. Backup data cannot be stored on an
archive volume or a clone volume.
volume ID
volume name
volume pool
247
Glossary
248
Index
A
ADDRESS_LIST parameter 144
Administrator attribute
in Server resource 63
Administrator program, NetWorker
Stop button 111
Administrator, NetWorker
Client resource 87, 170
Device resource 66
Group resource 86, 169
Label Template resource 67
Pool resource 66, 169
Schedule resource 87
Server resource 63
Snapshot Policy resource 150, 154, 169
User Group resource 64
AES encryption 122, 201
allocate channel command
parms option 215
API, SBT 52, 57, 58
archived redo log
backup 20, 131, 147
restore 148
sharing across RAC nodes 147
attributes for resources
Client resource 87
Server resource 63
autochanger 66, 105, 123
automatic catalog synchronization for proxy backups 181,
191
automatic channel allocation 26, 75, 77
Schedule resource 87
sessions 54
backup and recovery system 49, 50, 152
Backup Command attribute
in Client resource 88, 170, 195, 196
backup copies during manual backups 27
backup current control file command 132
Backup Snapshots attribute
in Snapshot Policy resource 158
backup spfile command 132
backup types
archived redo log 20, 131, 147
control file 130, 132
deduplication 21, 93
deferred live 150, 158, 173
immediate live 150, 156
instant 150, 154, 173, 182
manual 21, 48, 54, 104
NetWorker bootstrap 48, 53, 106, 155
NWORA resource file 173, 176
password file 130
probe-based 23, 97
proxy 24, 150, 154, 171
registry files 130
scheduled 21, 48, 110, 154
BACKUP_TAPE_IO_SLAVES parameter 216
bootstrap, NetWorker 48, 53, 106, 155
Browse Policy attribute
in Client resource 88, 170
browse policy uniformity 37
bundling, save set 39
backup
Client resource 87, 170
command 165, 214
command (pool option) 210
command (trace option) 217
copies 27
devices, multiple 47
error messages 221, 222
Group resource 86, 169
level (full or incremental in RMAN script) 66
canceling
manual backup 107
nonresponding backup 107
proxy backup 174
scheduled backup 78, 111
catalog synchronization for proxy backups 181, 191
change backuppiece...unavailable command 216
change...crosscheck command 210, 216
change...delete command 192
channel option, send command 212
249
Index
250
Server resource 63
Snapshot Policy resource 150, 154, 169
User Group resource 64
configuration wizard 62
configure channel command
parms option 167, 200
connection file, for catalog synchronization 184, 186, 188
control file
backup 130, 132
control files, mirrored 130
crosscheck command 210, 216
D
database
manual backup 48, 54, 104
scheduled backup 48, 110, 154
Datazone pass phrase attribute
in Server resource 63
DBID 130, 131
deduplication
backup 21, 93
restore 21
deferred live backup 150, 158, 173
delete expired backup command 210
destructive restores
overview 151
Device resource 66
device_type option, send command 212
devices, multiple 47
disaster recovery
preparation 130
types 133
E
email notification 91
enabling
policy uniformity 93
save set bundling 92
encryption
AES encryption 122, 201
environment variable
LC_ALL 68
NLS_LANG 68
error messages
NetWorker Module for Oracle 222
RMAN 221
F
failover
backup 139, 140, 145
connect-time 139, 144
proxy backup 194
FAILOVER parameter 144
force_rollback option, not supported 178
G
Group attribute
in Client resource 88, 170
Index
I
I18N (internationalization) 33, 35, 67, 68
immediate live backup 150, 156
initialization parameter file
initoracle_sid.ora 145
PFILE 130, 131, 132
SPFILE 130, 132
INSTANCE_NAME parameter 145
instant backup 150, 154, 173, 182
instant restore 151, 160, 177
internationalization (I18N) 33, 35, 67, 68
L
L10N (localization) 35, 69
Label Template resource 67
LC_ALL environment variable 68
LD_LIBRARY_PATH parameter 81, 82
LIBPATH parameter 82
live backup
deferred 150, 158, 173
immediate 150, 156
LOCAL_LISTENER parameter 145
localization (L10N) 35, 69
LOG_THRESHOLD parameter 98
M
mandatory parameters 81, 98, 202, 203, 204, 206, 207
manual backup 48, 54, 104
canceling 107
monitoring 108
procedure for running 104
roadmap 104
manual catalog synchronization for proxy backups 191
media database 47, 175, 176
media management
storage devices 66
volume pools 66
media management library (MML) 52, 153, 160, 161
mirrored
control files 130
online redo logs 130
MML 52, 153, 160, 161
MML catalog 181
monitoring
manual backup 108
scheduled backup 112
multiple backup devices 47
N
Name attribute
in Client resource 88
in Probe resource 98
in Server resource 63
network files
251
Index
O
online NetWorker indexes 47
online redo logs, mirrored 130
Oracle
backup and recovery system 49, 50, 152
DBID 130, 131
manual backup script 75, 165, 214
252
P
parallel save stream 47
Parallelism attribute
in Client resource 170
in Server resource 63
parameter
ADDRESS_LIST 144
FAILOVER 144
INSTANCE_NAME 145
LOCAL_LISTENER 145
SERVICE_NAME 144, 145
SID_LIST_LISTENER 144, 145
parameter resources
NSR_ORACLE_NLS_LANG 185
NSR_ORACLECAT_DEBUG_FILE 184
NSR_ORACLECAT_LOG_FILE 184
NSR_ORACLECAT_MODE 185, 193
NSR_REMOVE_ON_FAILURE 185
parameters
BACKUP_TAPE_IO_SLAVES 216
in nsrnmo script 79, 80
LD_LIBRARY_PATH 81, 82
LIBPATH 82
LOG_THRESHOLD 98
mandatory 81, 98, 202, 203, 204, 206, 207
NSR_AES_ENCRYPTION 76, 201
NSR_BUNDLING 92
NSR_CHECKSUM 201
NSR_CLIENT 126, 178, 201
NSR_COMPRESSION 201
Index
NSR_DATA_MOVER 167
NSR_DATA_VOLUME_POOL* 67, 78, 202, 216
NSR_DEBUG_FILE 83, 98, 203
NSR_DEBUG_LEVEL 203
NSR_DEDUP_BACKUP 203
NSR_DEDUP_CACHE_ENABLED 203
NSR_DEDUP_CACHE_TAG 204
NSR_DEDUP_CHUNK_SIZE 204
NSR_DEDUP_NODE 204
NSR_DPRINTF 204
NSR_ENCRYPTION_PHRASES 122, 205
NSR_GROUP 78, 205
NSR_INCR_EXPIRATION 93
NSR_MAX_STREAMS 168
NSR_MMDB_RETRY_TIME 205
NSR_NO_BUSY_ERRORS 205
NSR_NO_MULTIPLEX 205
NSR_NWPATH 184, 206
NSR_ORACLE_CONNECT_FILE 98, 186
NSR_ORACLE_HOME 186
NSR_ORACLE_LIB_PATH 187
NSR_ORACLE_NLS_LANG 69
NSR_ORACLE_SID 187
NSR_ORACLE_TNS_ADMIN 187
NSR_PROXY_PFILE 206
NSR_PS_SAVE_PARALLELISM 167
NSR_RECOVER_POOL 206
NSR_RETENTION 89
NSR_RETENTION_DISABLED 206
NSR_RMAN_ARGUMENTS 82
NSR_SAVESET_BROWSE 88, 206
NSR_SAVESET_RETENTION 207
NSR_SB_DEBUG_FILE 83
NSR_SERVER 78, 126, 207
NSR_SERVER_NIC 207
ORACLE_HOME 81, 83, 98
ORACLE_SERVICE 98
ORACLE_SID 83
ORACLE_USER 83
PATH 81
POSTCMD 85
PowerSnap 165, 166, 167
PRECMD 84
RESTORE_TYPE_ORDER 168, 177, 178, 179
scheduled backup 110
SHLIB_PATH 82
TNS_ADMIN 86
parms option
allocate channel command 215
configure channel command 167, 200
password file 78
backup 130
PATH parameter 81
persistent settings 25, 26, 77
PFILE 130, 131, 132
physical cluster client, proxy backups from 196
point-in-time copy 24, 150, 151, 160, 169, 170, 175
policy
browse 88
retention 89
policy uniformity 37
pool option, backup command 210
Pool resource 66, 169
pool, volume
defined 66
label template for 66
pool types 66
POSTCMD parameter 85
postcommand script 85, 131, 134
postprocessing scripts 85
PowerSnap Modules 24, 48, 65, 150, 163
PowerSnap parameters 165, 166, 167
precedence rules for send command 215
PRECMD parameter 84
preprocessing scripts 84
primary storage 24, 150, 153, 163, 171
Probe resource
attributes
Command 98
Command Options 98
Name 98
probe-based
backup 23, 97
processes
restore 163
program
nsrd 53, 54, 57, 154, 156
nsrexecd 53, 154
nsrindexd 55, 57, 155
nsrmmd 54, 57
nsrmmdbd 55, 58, 155
nsrnmo 53, 154, 157
nsrnmoadmin 185, 187, 188, 190
nsrnmoprobe 24, 98, 99
nsrnmostart 53, 154, 157
nsroraclecat 182, 191, 194
nsrsnapck 154, 157, 191, 192, 194
savefs 53, 154, 156
savegrp 53, 154, 156
proxy
backup 24, 150, 154, 171
restore 151, 159, 177
psrollback.res file 179
R
RAC nodes as storage nodes 142
RAC systems 29, 138, 140
recover 20, 127
Recovery Catalog 49, 50, 51, 152
Recovery Catalog database
connection to 78
Recovery Catalog, backup 130, 132
Recovery Manager (RMAN) 49, 52, 57, 152, 159
backup scripts 75
commands 209
error messages 221
features 50
manual backup scripts 76
proxy backup scripts 165
proxy restore scripts 177
253
Index
S
Save Set attribute
in Client resource 89, 170, 195
save set bundling 39
savefs command 53, 154, 156
savegroup completion report for proxy backup 173
savegrp command 53, 106, 154, 156
SBT API 52, 57, 58
254
Index
su command 84, 85
synchronization
automatic catalog 181, 191
manual catalog 191
System Backup to Tape (SBT) API 52, 57, 58
T
tablespace
manual backup 48, 54, 104
scheduled backup 48, 110, 154
target database
connection to 78
TNS_ADMIN parameter 86
trace option, backup command 217
troubleshooting
manual backup 221
NetWorker Module for Oracle 220, 221
scheduled backup 79, 221
types of backup
archived redo log 20, 131, 147
manual 48, 54, 104
NetWorker bootstrap 48, 53, 106, 155
scheduled 48, 110, 154
U
uniformity, policy 37
User Group resource 64
V
virtual cluster client, proxy backups from 195
volume pool
Default pool 78
defined 66
resource 66, 169
specifying 78
types 66
volumes, determining for restore 123
W
wizard, configuration 62
255
Index
256