Skip Headers
Oracle® Secure Backup Reference
Release 10.1

Part Number B14236-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

E RMAN Media Management Parameters

This appendix describes Oracle Secure Backup-specific media management parameters that you can specify in RMAN backup and restore jobs. You can specify media management parameters in RMAN backup jobs by the following means:

This section describes Oracle Secure Backup parameters that are valid in RMAN jobs.

This section contains the following topics:

Database Backup Storage Selectors and RMAN Media Management Parameters

You can configure device and media family restrictions in both database backup storage selectors, which are created with the mkssel command, and the OB_DEVICE and OB_MEDIA_FAMILY RMAN media management parameters. Table E-1 explains the criteria used by Oracle Secure Backup when choosing the media family and device for an RMAN backup job.

Table E-1 Determining Media Family and Device Settings

Matching Selector Device Set in Selector OB_DEVICE Set in Job OB_MEDIA_FAMILY Set in Job Result

Yes

Yes

No

No

Oracle Secure Backup uses the device and media family settings in the backup storage selector.

Yes

Yes or No

Yes

Yes

Oracle Secure Backup uses the device and media family settings in the RMAN channel parameters.

Yes

Yes or No

Yes

No

Oracle Secure Backup uses the OB_DEVICE setting and the media family specified in the selector.

Yes

Yes

No

Yes

Oracle Secure Backup uses the device settings in the selector and media family settings in the RMAN channel parameters.

Yes

No

No

Yes

Oracle Secure Backup does not restrict the device (that is, chooses any device in the domain) and uses the media family setting in the RMAN channel parameters.

No

N/A

Yes

No

Oracle Secure Backup uses the OB_DEVICE setting and RMAN-DEFAULT media family.

No

N/A

No

No

Oracle Secure Backup does not restrict the device (that is, chooses any device in the domain) and uses the RMAN-DEFAULT media family.


OB_DEVICE[_n]

Use the OB_DEVICE[_n] parameter to define which tape drives can be used for backups.

Restrictions and Usage Notes

Before specifying OB_DEVICE[_n] in an RMAN job, note the following:

Syntax

OB_DEVICE::=
OB_DEVICE[_n][=]drive_name

Semantics

_n

Specifies the copy number of duplexed backups. For duplexed backups, OB_DEVICE_1 is for the first copy, OB_DEVICE_2 is for the second copy, and so on.

drive_name

Specifies the name of the tape drive to which the backup should be restricted.

Examples

Example E-1 uses the SEND command to specify a tape drive. Note that no equal sign is inserted between the parameter OB_DEVICE and the names of the tape drives.

Example E-1 SBT Backup with SEND Command

RUN
{
  ALLOCATE CHANNEL c1 DEVICE TYPE sbt;
  SEND 'OB_DEVICE tape2';
  BACKUP TABLESPACE users;
}

Example E-2 makes the same backup as Example E-1, but uses PARMS to set the Oracle Secure Backup media family parameter. Note that an equal sign is inserted between the parameter OB_DEVICE and the value my_full_backups.

Example E-2 SBT Backup with ENV Parameter

RUN
{
   ALLOCATE CHANNEL c1 DEVICE TYPE sbt
     PARMS 'ENV=(OB_DEVICE=tape2)';   
   BACKUP TABLESPACE users;
}

OB_MEDIA_FAMILY[_n]

Use the OB_MEDIA_FAMILY[_n] parameter to define which media can be used for backup jobs.

Restrictions and Usage Notes

Before specifying OB_MEDIA_FAMILY[_n] in an RMAN job, note the following:

Syntax

OB_MEDIA_FAMILY::=
OB_MEDIA_FAMILY[_n][=]media_family_name

Semantics

_n

Specifies the copy number of duplexed backups. For duplexed backups, OB_MEDIA_FAMILY_1 is for the first copy, OB_MEDIA_FAMILY_2 is for the second one, and so on.

media_family_name

Specifies the name of the media family.

Examples

Example E-3 uses the SEND command to specify the my_full_backups media family in an RMAN database backup. Note that there is no equal sign between the parameter OB_MEDIA_FAMILY and the value datafile_mf.

Example E-3 SBT Backup with SEND Command

SEND 'OB_MEDIA_FAMILY datafile_mf';
BACKUP TABLESPACE users;

Example E-4 makes the same backup as Example E-3, but uses PARMS to set the Oracle Secure Backup media family parameter. Note that there is an equal sign between the parameter OB_MEDIA_FAMILY and the value datafile_mf.

Example E-4 SBT Backup with ENV Parameter

CONFIGURE CHANNEL DEVICE TYPE sbt PARMS  
  'ENV=(OB_MEDIA_FAMILY=datafile_mf)';
BACKUP TABLESPACE users;

OB_RESOURCE_WAIT_TIME

Use the OB_RESOURCE_WAIT_TIME parameter to specify the duration for which a backup or restore job should wait for the required resources to become available.

Restrictions and Usage Notes

Note that you can specify RMAN resource wait times in the following locations, each of which overrides the preceding specifications in the list:

  1. The rmanresourcewaittime policy

  2. The waittime attribute in a database backup storage selector that matches an RMAN backup job

  3. The RMAN channel configuration parameter OB_RESOURCE_WAIT_TIME

Syntax

OB_RESOURCE_WAIT_TIME::=
OB_RESOURCE_WAIT_TIME=duration

Semantics

duration

Specifies how long Oracle Secure Backup should wait for the tape resources to become available. For valid values, refer to the description of the duration placeholder in "duration".

Examples

Example E-5 uses the SEND command to specify that the restore job should wait no longer than 10 minutes for tape resources to become available. Note that there is no equal sign between the parameter OB_RESOURCE_WAIT_TIME and the value.

Example E-5 SBT Restore with SEND Command

RUN
{
  ALLOCATE CHANNEL c1 DEVICE TYPE sbt;
  SEND 'OB_RESOURCE_WAIT_TIME 1minute';
  RESTORE ARCHIVELOG ALL;
}

Example E-6 uses the ENV parameter to specify the wait time on a configured channel. Note that there is an equal sign between the parameter OB_RESOURCE_WAIT_TIME and the value.

Example E-6 SBT Restore with ENV Parameter

CONFIGURE CHANNEL DEVICE TYPE sbt PARMS
  'ENV=(OB_RESOURCE_WAIT_TIME=1minute)';
RESTORE ARCHIVELOG ALL;