Oracle DOCUCOLOR 242, DOCUCOLOR 252, DOCUCOLOR 260 User Manual

Download

Oracle® Secure Backup

Installation and Configuration Guide

Release 10.3

E12835-06

December 2010

How to install, uninstall, and manage hardware and network configuration in Oracle Secure Backup

Oracle Secure Backup Installation and Configuration Guide, Release 10.3

E12835-06

Primary Author: Craig B. Foch

Contributing Author: Lance Ashdown, Padmaja Potineni

Contributors: Anand Agrawal, Tammy Bednar, George Claborn, Michael Chamberlain, Sumit Chougule, Donna Cooksey, Rhonda Day, Senad Dizdar, Tony Dziedzic, Judy Ferstenberg Panock, Steven Fried, Geoff Hickey, Ashok Joshi, Cris Pedregal-Martin, Chris Plakyda, George Stabler, Radhika Vullikanti, Joe Wadleigh, Steve Wertheimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Preface ................................................................................................................................................................. ix

Audience....................................................................................................................................................... ix

Documentation Accessibility..................................................................................................................... ix

Related Documents ..................................................................................................................................... x

Conventions ................................................................................................................................................. x

1 Introduction to Oracle Secure Backup

What Is Oracle Secure Backup? ............................................................................................................. 1-1

Oracle Secure Backup Concepts............................................................................................................ 1-2

Oracle Secure Backup Administrative Domains and Hosts........................................................ 1-2

Host Roles in an Administrative Domain ............................................................................... 1-2

Host Naming in an Administrative Domain .......................................................................... 1-3

Oracle Secure Backup Host Access Modes ............................................................................. 1-3

Oracle Secure Backup Administrative Domain: Examples.......................................................... 1-4

Tape Devices....................................................................................................................................... 1-5

Tape Drives.................................................................................................................................. 1-5

Tape Libraries.............................................................................................................................. 1-7

Virtual Tape Libraries ................................................................................................................ 1-9

Device Names and Attachments ........................................................................................... 1-10

Oracle Secure Backup Interfaces........................................................................................................ 1-10

System Requirements for Oracle Secure Backup ........................................................................... 1-11

Disk Space Requirements for Oracle Secure Backup................................................................. 1-11

Other System Requirements for Oracle Secure Backup ............................................................ 1-12

Linux Media Server System Requirement: SCSI Generic Driver............................................. 1-12

Acquiring Oracle Secure Backup Installation Media .................................................................... 1-12

Installation and Configuration Overview........................................................................................ 1-13

About Upgrade Installations............................................................................................................... 1-14

Preparing Administrative Domain Hosts for Upgrade to Release 10.3.................................. 1-14

2 Installing Oracle Secure Backup on Linux or UNIX

Overview of Oracle Secure Backup Linux and UNIX Installation................................................. 2-1

Prerequisites for Installing Oracle Secure Backup on Linux and UNIX....................................... 2-2

Prerequisites for Installation on Linux............................................................................................ 2-2

Required SCSI Tape Device Parameters on Linux and UNIX..................................................... 2-3

Assigning Oracle Secure Backup Logical Unit Numbers to Devices.................................. 2-3

iii

Extracting Oracle Secure Backup from OTN Download on Linux or UNIX ................................ 2-4

Preparing to Install Oracle Secure Backup on Linux and UNIX..................................................... 2-5

Creating the Oracle Secure Backup Home .......................................................................................... 2-5

Loading Oracle Secure Backup Software on Linux or UNIX Using setup Script........................ 2-6

Configuring Installation Parameters in the obparameters File....................................................... 2-7

Installing Oracle Secure Backup on Linux or UNIX with installob............................................... 2-8

Installing or Uninstalling Oracle Secure Backup on AIX ............................................................. 2-12

Installing or Uninstalling Oracle Secure Backup on HP-UX........................................................ 2-12

Creating Attach Points with makedev .............................................................................................. 2-12

Identifying and Configuring AIX Devices .................................................................................. 2-13

Identifying and Configuring AIX Devices in a Switched Fibre Channel Configuration .........

2-13

Identifying and Configuring AIX Devices in a Point-to-Point or FC-AL Configuration.........

2-15

Identifying and Configuring HP-UX Devices............................................................................. 2-16

Identifying and Configuring Linux Attach Points..................................................................... 2-18

Configuring the Solaris sgen Driver to Provide Oracle Secure Backup Attach Points......... 2-18

Enabling the Solaris sgen Driver for Changer and Sequential Devices........................... 2-19

Utilizing sgen Attach Points................................................................................................... 2-20

Performing an Upgrade Installation on Linux or UNIX ................................................................ 2-20

Uninstalling Oracle Secure Backup on Linux or UNIX................................................................. 2-20

3 Installing Oracle Secure Backup on Windows

Preliminary Steps ..................................................................................................................................... 3-1

Disabling Removable Storage Service on Windows Media Servers ............................................. 3-2

Extracting Oracle Secure Backup from OTN Download on Windows.......................................... 3-2

Running the Oracle Secure Backup Windows Installer ................................................................... 3-3

Configuring Oracle Secure Backup ................................................................................................... 3-14

Configuring Firewalls for Oracle Secure Backup on Windows................................................... 3-18

Upgrade Installation on Windows 32-Bit ......................................................................................... 3-19

Upgrade Installation on Windows x64.............................................................................................. 3-20

Uninstalling Oracle Secure Backup on Windows........................................................................... 3-20

4 Oracle Secure Backup User Interfaces

Using Oracle Secure Backup in Enterprise Manager........................................................................ 4-1

Enabling Oracle Secure Backup Links in Oracle Enterprise Manager....................................... 4-2

Registering an Administrative Server in Oracle Enterprise Manager........................................ 4-3

Accessing the Web Tool from Enterprise Manager....................................................................... 4-3

Using the Oracle Secure Backup Web Tool ......................................................................................... 4-4

Starting a Web Tool Session ............................................................................................................. 4-4

Web Tool Home Page........................................................................................................................ 4-5

Persistent Page Links ................................................................................................................. 4-6

Web Tool Configure Page................................................................................................................. 4-7

Web Tool Manage Page..................................................................................................................... 4-8

Web Tool Backup Page................................................................................................................... 4-10

Web Tool Restore Page................................................................................................................... 4-10

Using obtool ........................................................................................................................................... 4-11

Displaying Help for Invoking obtool........................................................................................... 4-11

Starting obtool in Interactive Mode.............................................................................................. 4-11

Running obtool Commands in Interactive Mode....................................................................... 4-12

Redirecting obtool Input from Text Files ............................................................................ 4-12

Executing obtool Commands in Noninteractive Mode............................................................. 4-12

Running Multiple Commands in Noninteractive Mode.................................................... 4-12

Redirecting Input in Noninteractive Mode.......................................................................... 4-12

Ending an obtool Session............................................................................................................... 4-13

Starting obtool as a Specific User.................................................................................................. 4-13

5 Configuring and Managing the Administrative Domain

Administrative Domain Configuration Overview ............................................................................ 5-1

Administrative Domain Configuration Steps: Outline................................................................. 5-1

Configuring the Administrative Domain with Hosts....................................................................... 5-2

About Administrative Domain Host Configuration..................................................................... 5-2

Viewing the Hosts in the Administrative Domain........................................................................ 5-3

Adding a Host to the Administrative Domain.............................................................................. 5-3

Adding the Media Server Role to an Administrative Server....................................................... 5-6

Adding Backup and Restore Environment Variables to an NDMP Host.................................. 5-8

Configuring Preferred Network Interfaces (PNI) ......................................................................... 5-8

Pinging a Host .................................................................................................................................... 5-9

Viewing or Editing Host Properties ................................................................................................ 5-9

Updating a Host ................................................................................................................................. 5-9

Removing a Host............................................................................................................................. 5-10

Adding Tape Devices to an Administrative Domain..................................................................... 5-10

Tape Device Names ........................................................................................................................ 5-11

About Configuring Tape Drives and Libraries........................................................................... 5-11

Updating a Tape Device Inventory....................................................................................... 5-12

Displaying the Devices Page ......................................................................................................... 5-13

Configuring a Tape Library........................................................................................................... 5-14

Configuring Automatic Tape Cleaning for a Library......................................................... 5-16

Configuring a Tape Drive.............................................................................................................. 5-17

Discovering Tape Devices Automatically on NDMP Hosts..................................................... 5-19

Configuring an NDMP Copy-Enabled Virtual Tape Library................................................... 5-20

Adding a Tape Device Attachment.............................................................................................. 5-21

Pinging a Device Attachment................................................................................................. 5-22

Displaying Device Attachment Properties........................................................................... 5-22

Multiple Attachments for SAN-Attached Tape Devices ........................................................... 5-23

Configuring Multihosted Device Objects.................................................................................... 5-23

Creating Attach Points for Solaris 10 SCSI and Fibre Channel Devices ................................. 5-24

Verifying and Configuring Added Tape Devices ........................................................................... 5-24

Pinging a Tape Device.................................................................................................................... 5-24

Displaying Device Properties........................................................................................................ 5-24

Editing Device Properties .............................................................................................................. 5-25

Verifying Tape Device Configuration.......................................................................................... 5-25

Setting Serial Number Checking................................................................................................... 5-26

6 Managing Security for Backup Networks

Backup Network Security Overview.................................................................................................... 6-1

Planning Security for an Administrative Domain............................................................................. 6-2

Identifying Assets and Principals.................................................................................................... 6-2

Identifying Your Backup Environment Type ................................................................................ 6-3

Single System............................................................................................................................... 6-3

Data Center .................................................................................................................................. 6-4

Corporate Network..................................................................................................................... 6-6

Choosing Secure Hosts for the Administrative and Media Servers........................................... 6-6

Determining the Distribution Method of Host Identity Certificates.......................................... 6-7

Trusted Hosts............................................................................................................................................. 6-8

Host Authentication and Communication .......................................................................................... 6-9

Identity Certificates and Public Key Cryptography ..................................................................... 6-9

Authenticated SSL Connections.................................................................................................... 6-10

Certification Authority................................................................................................................... 6-10

Automated and Manual Certificate Provisioning Mode ................................................... 6-11

Oracle Wallet.................................................................................................................................... 6-11

Oracle Secure Backup Encryption Wallet............................................................................. 6-12

Web Server Authentication............................................................................................................ 6-13

Revoking a Host Identity Certificate............................................................................................ 6-13

Encryption of Data in Transit.............................................................................................................. 6-14

Default Security Configuration.......................................................................................................... 6-15

Configuring Security for the Administrative Domain .................................................................. 6-16

Providing Certificates for Hosts in the Administrative Domain ............................................. 6-16

Configuring the Administrative Server................................................................................ 6-16

Configuring Media Servers and Clients............................................................................... 6-17

Setting the Size for Public and Private Keys............................................................................... 6-18

Setting the Key Size in obparameters.................................................................................... 6-18

Setting the Key Size in the certkeysize Security Policy ...................................................... 6-19

Setting the Key Size in mkhost............................................................................................... 6-19

Enabling and Disabling SSL for Host Authentication and Communication.......................... 6-20

Managing Certificates with obcm ...................................................................................................... 6-21

Exporting Signed Certificates........................................................................................................ 6-21

Importing Signed Certificates ....................................................................................................... 6-21

A Oracle Secure Backup Directories and Files

Oracle Secure Backup Home Directory .............................................................................................. A-1

Administrative Server Directories and Files...................................................................................... A-1

Media Server Directories and Files...................................................................................................... A-4

Client Host Directories and Files ......................................................................................................... A-5

B Oracle Secure Backup obparameters Installation Parameters

customized obparameters ...................................................................................................................... B-1

start daemons at boot.............................................................................................................................. B-2

identity certificate key size.................................................................................................................... B-2

create preauthorized oracle user........................................................................................................... B-2

default UNIX user ................................................................................................................................... B-3

default UNIX group ................................................................................................................................ B-3

linux ob dir and solaris64 ob dir .......................................................................................................... B-3

linux db dir and solaris64 db dir.......................................................................................................... B-4

linux temp dir and solaris64 temp dir................................................................................................. B-4

linux links and solaris64 links.............................................................................................................. B-4

ask about ob dir ...................................................................................................................................... B-5

default protection .................................................................................................................................... B-5

run obopenssl........................................................................................................................................... B-6

C Determining Linux SCSI Parameters

Determining SCSI Device Parameters on Linux............................................................................... C-1

D Oracle Secure Backup and ACSLS

About ACSLS ........................................................................................................................................... D-1

ACSLS and Oracle Secure Backup....................................................................................................... D-2

Communicating with ACSLS................................................................................................................ D-3

Drive Association .................................................................................................................................... D-3

Volume Loading and Unloading .......................................................................................................... D-3

Imports and Exports................................................................................................................................ D-3

Access Controls........................................................................................................................................ D-4

Scratch Pool Management ..................................................................................................................... D-4

Modified Oracle Secure Backup Commands..................................................................................... D-4

Unsupported Oracle Secure Backup Commands.............................................................................. D-5

Installation and Configuration............................................................................................................. D-5

Index

vii

viii

This Preface contains these topics:

■ Audience

■ Documentation Accessibility

■ Related Documents

■ Conventions

Audience

This guide is intended for system administrators and database administrators who install the Oracle Secure Backup software. These administrators might also perform backup and restore operations. To use this document, you must be familiar with the operating system environment on which you plan to use Oracle Secure Backup. To perform Oracle database backup and restore operations, you should also be familiar with Recovery Manager concepts.

Documentation Accessibility

Preface

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit

http://www.oracle.com/accessibility/support.html if you are hearing

impaired.

Conventions

■ Oracle Database Backup and Recovery Advanced User's Guide

This book provides an overview of backup and recovery and discusses backup and recovery strategies. It provides instructions for basic backup and recovery of your database using Recovery Manager (RMAN).

The Oracle Secure Backup product site is located at the following URL:

http://www.oracle.com/technology/products/secure-backup

The Oracle Secure Backup download site is located at the following URL:

http://www.oracle.com/technology/software

The following text conventions are used in this document:

Convention Meaning

boldface Boldface type indicates graphical user interface elements associated

with an action, or terms defined in text or the glossary.

italic Italic type indicates book titles, emphasis, or placeholder variables for

which you supply particular values.

monospace Monospace type indicates commands within a paragraph, URLs, code

in examples, text that appears on the screen, or text that you enter.

Introduction to Oracle Secure Backup

This chapter provides an introduction to Oracle Secure Backup and includes advice on planning and configuring your administrative domain.

This chapter contains these sections:

■ What Is Oracle Secure Backup?

■ Oracle Secure Backup Concepts

■ Oracle Secure Backup Interfaces

■ System Requirements for Oracle Secure Backup

■ Acquiring Oracle Secure Backup Installation Media

■ Installation and Configuration Overview

■ About Upgrade Installations

See Also: Oracle Secure Backup Administrator's Guide for conceptual

information about Oracle Secure Backup

What Is Oracle Secure Backup?

Oracle Secure Backup enables reliable data protection through file-system backup to tape. It supports every major tape drive and tape library in SAN, Gigabit Ethernet (GbE), and SCSI environments using standard tape formats.

Oracle Secure Backup supports Internet Protocol v4 (IPv4), Internet Protocol v6 (IPv6), and mixed IPv4/IPv6 environments on all platforms that support IPv6.

Using Oracle Secure Backup on your network enables you to take data from a networked host running Oracle Secure Backup or a NAS device that support NDMP, and back up that data on a tape device on the network. That data can include ordinary file-system files and databases backed up with Recovery Manager (RMAN).

As part of the Oracle storage solution, Oracle Secure Backup provides scalable distributed backup and recovery capabilities. It reduces complexity of your backup solution, by:

■ Integrating with the Oracle stack for maximum ease of use in a single Oracle

solution to back up your data from disk to tape

■ Employing single-vendor technical support for database and file-system backup

and recovery to tape

■ Using existing or new hardware, with broad tape device support in SCSI, GbE,

and SAN environments with dynamic tape drive sharing for maximum tape drive utilization

Introduction to Oracle Secure Backup 1-1

Oracle Secure Backup Concepts

Oracle Secure Backup eliminates integration challenges with ready-to-use tape management software that provides single-vendor support. Oracle Secure Backup also reduces your costs. When using Oracle Secure Backup with RMAN to back up and recover databases and files to and from tape, no third-party tape management software is required. Oracle Secure Backup provides the media management layer needed to use tape storage with RMAN.

Centralized administration, heterogeneous network support, and flexible scheduling simplify and automate protection of the entire Oracle environment, including database data and file-system data such as the contents of the Oracle home.

Oracle Secure Backup Concepts

This section discusses Oracle Secure Backup concepts that enable you to better understand the installation process.

This section contains these topics:

■ Oracle Secure Backup Administrative Domains and Hosts

■ Oracle Secure Backup Administrative Domain: Examples

■ Tape De vices

Oracle Secure Backup Administrative Domains and Hosts

Oracle Secure Backup organizes hosts and tape devices into an administrative domain, representing the network of hosts containing data to be backed up, hosts with attached tape devices on which backups are stored, and each tape device with its attachment to the hosts. A host can belong to only one administrative domain.

Host Roles in an Administrative Domain

Each host in an administrative domain must be assigned one or more of the following Oracle Secure Backup roles:

■ Administrative server

Each administrative domain must have exactly one administrative server. During postinstallation configuration, the administrative server must be configured with complete data regarding the other hosts in the administrative domain, their roles, and their attached tape devices. This configuration information is maintained in a set of configuration files stored on the administrative server.

The administrative server runs the scheduler, which starts and monitors each

backup job. The scheduler also keeps a backup catalog with metadata for all

backup and restore operations performed in the administrative domain.

■ Media server

A media server is a host with at least one tape device attached to it. A media server transfers data to or from a volume loaded on one of these tape devices. A media server has at least one attachment to a tape drive or library. It might have attachments to multiple tape libraries.

You specify the attachments between media servers and tape devices during postinstallation configuration of Oracle Secure Backup.

■ Client

The client role is assigned to any host that has access to file-system or database data that can be backed up or restored by Oracle Secure Backup. Any host where

1-2 Oracle Secure Backup Installation and Configuration Guide

Oracle Secure Backup Concepts

Oracle Secure Backup is installed can be a client, including hosts that are also media servers or the administrative server. A network-attached storage device that Oracle Secure Backup accesses through NDMP can also serve the client role.

Note: A host can be assigned multiple roles in an administrative

domain. For example, a host with a tape drive attached could be both the administrative server and media server for a network that includes several other clients. For more examples of administrative domains, see "Oracle Secure Backup Administrative Domain:

Examples" on page 1-4.

See Also: "Choosing Secure Hosts for the Administrative and Media

Servers" on page 6-6

Host Naming in an Administrative Domain

You must assign each host in an administrative domain a unique name to be used in Oracle Secure Backup operations. Typically, the host name in your DNS for this host is a good choice for the Oracle Secure Backup host name. However, you can assign a different name to a host.

Oracle Secure Backup Host Access Modes

Communication among hosts in an administrative domain is always based on NDMP, but implementations and versions of NDMP vary. Oracle Secure Backup supports two host access modes: primary access mode and NDMP access mode.

Primary access mode is used among hosts on which Oracle Secure Backup is installed. Oracle Secure Backup daemons run in the background on the host, communicate with the administrative server using the Oracle Secure Backup implementation of NDMP, and perform backup and restore tasks. Hosts on which databases reside are typically accessed using primary access mode.

Note: In Oracle Enterprise Manager, primary access mode is referred

to as native access mode. In the Oracle Secure Backup Web tool and the output of some obtool commands such as lshost, primary mode is referred to as OB access mode.

NDMP access mode is used to communicate with devices such as storage appliances that do not run Oracle Secure Backup natively. For example, devices from third-party vendors such as Network Appliance and EMC are supported only in NDMP access mode. Each NDMP host uses a vendor-specific implementation of the NDMP protocol to back up and restore file systems. Some devices support older versions of the NDMP protocol. When adding such devices to the administrative domain, extra parameters might be required.

Oracle Secure Backup supports NDMP versions 3 and 4, and various extensions to version 4. It automatically negotiates with other, non-Oracle NDMP components to select a mutually supported protocol version. Between its own components, Oracle Secure Backup uses NDMP version 4. When communicating with hosts that are not running Oracle Secure Backup, Oracle Secure Backup usually chooses the protocol version proposed by that host when the connection is established. You can change the NDMP protocol version with which Oracle Secure Backup communicates to a specific host. You might want to do this when testing or troubleshooting.

Introduction to Oracle Secure Backup 1-3

Oracle Secure Backup Concepts

Oracle Secure Backup Administrative Domain: Examples

Figure 1–1 shows a minimal administrative domain, in which a single host is

administrative server, media server, and client. An Oracle database also runs on the same host.

Figure 1–1 Administrative Domain with One Host

Administrative Server, Media Server, and Client

Linux

Oracle

Database

Recovery Manager

Backup

Restore

. . . . . .

Tape Library

Tape

Offsite

Storage

Figure 1–2 shows a possible Oracle Secure Backup administrative domain that

includes three client hosts, one administrative server, and one media server. A NAS appliance contains ordinary file data. One client based on UNIX and another based on Windows contain databases and other file data. Oracle Secure Backup can back up to tape the non-database files on file systems accessible on client hosts. RMAN can back up to tape database files through the Oracle Secure Backup SBT interface.

1-4 Oracle Secure Backup Installation and Configuration Guide

Figure 1–2 Oracle Secure Backup Administrative Domain with Multiple Hosts

Oracle Secure Backup Concepts

Oracle Secure Backup Clients

Recovery Manager

NAS Appliance

Linux

Windows

NDMP

Oracle

Database

Oracle Secure

Backup Administrative Server

Oracle Secure Backup Catalog

Control Flow

Data Flow

Oracle Secure Backup

UNIX Linux

Media Server

RestoreBackup

. . . . . .

Tape Library

Tape

Offsite

Storage

Recovery Manager

Tape Devices

Oracle

Database

Oracle Secure Backup maintains information about each tape library and tape drive so that you can use them for local and network backup and restore operations. You can configure tape devices during installation or add a new tape device to an existing administrative domain. When configuring tape devices, the basic task is to inform Oracle Secure Backup about the existence of a tape device and then specify which media server can communicate with this tape device.

This section contains these topics:

■ Tape Dr ives

■ Tape Libraries

■ Device Names and Attachments

Tape Dr i v es

A tape drive is a tape device that uses precisely controlled motors to wind a tape from one reel to another. The tape passes a read/write head as it winds. Most magnetic tape systems use small reels fixed inside a cartridge to protect the tape and make handling of the tape easier.

Introduction to Oracle Secure Backup 1-5

Oracle Secure Backup Concepts

A magnetic cassette or tape is sequential-access storage. It has a beginning and an end, which means that to access data in the middle of the tape, a tape device must read through the beginning part of the tape until it locates the desired data.

In a typical format, a tape drive writes data to a tape in blocks. The tape drive writes each block in a single operation, leaving gaps between the blocks. The tape runs continuously during the write operation.

The block size of a block of data is the size of the block in bytes as it was written to tape. All blocks read or written during a given backup or restore operation have the same block size. The blocking factor of a block of data expresses the number of 512-byte records contained in the block. For example, the Oracle Secure Backup default blocking factor (128) results in a tape block size of 128*512 bytes or 64 KB.

The maximum blocking factor is an upper limit on the blocking factor that Oracle Secure Backup uses. This limit comes into play particularly during restores, when Oracle Secure Backup must pick an initial block size to use without knowing the actual block size on the tape. The maximum blocking factor limits this initial block size to a value that is acceptable to both the tape device and the underlying operating system.

When Oracle Secure Backup starts a backup, it decides what block size to use based on several factors. Listed in order of precedence, these factors are:

■ Blocking factor specified using the obtar -b option

This option can also be specified as part of the operations/backupoptions policy. If this option is specified, then it overrides all other factors.

See Also: Oracle Secure Backup Reference for more information on the

obtar -b option and the operations/backupoptions policy

■ Configuration of the tape drive to be used

You can specify what blocking factor, maximum blocking factor, or both that Oracle Secure Backup should use for a particular tape drive when you configure that drive. You might want to do this if you have tape drives with very different block size limits.

See Also: "Configuring a Tape Drive" on page 5-17

■ Domain-wide blocking factors or maximum blocking factors set with the

media/blockingfactor and media/maxblockingfactor policies.

See Also: Oracle Secure Backup Reference for more information on the

media/blockingfactor and media/maxblockingfactor policies

■ The default blocking factor (128) and maximum blocking factor (128), resulting in

a block size of 64K

When a blocking factor has been nominated by one or another of these factors, it must pass the following tests:

■ The block size must be less than or equal to the maximum block size (blocking

factor) put in effect by whatever policies or tape drive configuration attributes are in force.

■ The block size must be supported by the tape drive and attach point in question.

Sometimes a tape drive, device driver, or kernel operating system has a limitation that supersedes all other considerations.

1-6 Oracle Secure Backup Installation and Configuration Guide

Oracle Secure Backup Concepts

When Oracle Secure Backup begins a restore operation, it does not know what block size was used to write a given tape. Because issuing a read for a too-small block would result in an error condition and a tape reposition, Oracle Secure Backup always starts a restore operation by reading the largest possible block size. This is either the current setting of the media/maxblockingfactor policy or the tape drive configuration attribute. The maximum blocking factor, therefore, must always be greater than or equal to the largest block size you ever want to restore.

After the first read from the backup image, Oracle Secure Backup compares the amount of data requested to the actual size of the block and adjusts the size of subsequent reads to match what is on the tape.

Each tape drive supports a specific tape format. Typical tape formats include:

■ 8mm

■ 4mm, or Digital Audio Tape (DAT)

■ Advanced Intelligent Tape (AIT)

■ Digital Data Storage (DDS)

■ Digital Linear Tape (DLT) and Super DLT (SDLT)

■ Linear Tape-Open (LTO), an open alternative to the proprietary DLT format

Information about the tape formats of tape devices supported by Oracle Secure Backup is available at the following URL:

http://www.oracle.com/technology/products/secure-backup

Tape Libraries

A tape library is a robotic tape device that accepts SCSI commands to move a volume between a storage element and a tape drive. A tape library is often referred to as a robotic tape device, autochanger, or medium changer.

A tape library contains one or more tape drives, slots to hold tape cartridges, and an automated method for loading tapes. Figure 1–3 illustrates a tape library that contains four tape drives.

Introduction to Oracle Secure Backup 1-7

Oracle Secure Backup Concepts

Figure 1–3 Tape Library

Tape Library

Robotic Control

Drive

. . . . . .

Drive

. . . . . .

Drive

. . . . . .

Drive

. . . . . .

Storage elements (se) house tapes

Device connectivity varies by device: SCSI, Fibre, and

Library robotics (mte) move tape to and from drives to slots

Type drive (dte) writes data to and reads data from tape volumes

SCSI

Oracle Secure Backup automates the management of tape libraries, thereby enabling efficient and reliable use of their capabilities. Oracle Secure Backup controls the tape library robotics so that tapes can be managed easily.

Oracle Secure Backup supports the following features of tape libraries:

■ Automatic loading and unloading of volumes

When you add a tape library to your administrative domain, it is configured in automount mode by default. In this mode, Oracle Secure Backup sends commands to the robotic arm of the tape library to mount tapes for backup and restore operations. When a new volume is needed, Oracle Secure Backup scans the tape library until it finds a suitable volume. If sufficient eligible tapes are contained in the tape library storage elements, then no operator intervention is required to load the volumes needed to store the complete backup image.

■ Barcode readers

A barcode is a symbol code that is physically applied to volumes for identification purposes. Some tape libraries have an automated barcode reader. Oracle Secure Backup can use barcodes to identify tapes in a tape library.

■ Automatic tape drive cleaning

Oracle Secure Backup checks for cleaning requirements when a tape is loaded into or unloaded from a tape drive. If cleaning is required, then Oracle Secure Backup loads a cleaning cartridge, waits for the cleaning cycle to complete, replaces the cleaning cartridge in its original storage element, and continues with the requested load or unload. You can also schedule a cleaning interval.

As shown in Figure 1–3, a tape library has a set of addressable elements, each of which can contain or move a tape. Libraries can contain the following types of elements:

■ Storage element (se)

1-8 Oracle Secure Backup Installation and Configuration Guide

Oracle Secure Backup Concepts

This element is an internal slot in a tape library where a tape cartridge can reside.

■ Data transfer element (dte)

This element represents a tape device capable of reading or writing the physical volume. Typically, a data transfer element (DTE) is a tape drive used to back up or restore data on a tape.

■ Medium transport element (mte)

This element represents the robotics mechanism used to move tapes between other elements in the tape library. Typically, a medium transport element is a robot arm that moves tape cartridges from tape library slots to tape drives.

■ Import/export element (iee)

This is an element by which media can be imported to and exported from the tape library. Typically, an import/export element is a door-like mechanism that an operator uses to transfer tapes into and out of the library. After the door is closed, the robotic arm transfers cartridges to internal slots in the library. Because the library itself is not opened during this procedure, no re-inventory is required.

Many of the Oracle Secure Backup tape library commands require you to specify one or more tape library elements, in particular, storage elements and import/export elements. Except in the inventory display, media transport elements are never referenced. Data transfer elements are referenced only in the inventory display and indirectly by the tape drive (if any) that you select for an operation.

Oracle Secure Backup refers to elements by their abbreviation (mte, se, iee, or dte) followed by the number of the element, for example, se5, iee2, dte1. When multiple elements of a type exist, element numbering starts at 1. When only one element of a type exists, the number can be omitted. Thus, iee1 and iee both refer to the first and only import/export element. If the abbreviation is omitted, then a storage element is assumed. For example, se4 and 4 both refer to the fourth storage element. For some commands, you can specify a range of storage elements, for example, 1-5.

Oracle Secure Backup supports several tape library operations. The following operations are the most basic:

■ Inserting and extracting volumes

■ Loading and unloading volumes

■ Moving volumes

■ Importing and exporting volumes

See Also:

■ Oracle Secure Backup Reference for a description of the tape library

commands that you can run in obtool

Virtual Tape Libraries

A virtual tape library is one or more large-capacity disk drives partitioned into virtual physical tape volumes. To Oracle Secure Backup the virtual tape library appears to be a physical tape library with at least one volume and at least one tape drive. The volumes and tape drives in the virtual tape library can be configured to match common physical tapes and tape drives.

Backup operations performed to a virtual tape library complete faster than backup operations to actual tape drives, because the underlying storage device is direct access media. But a virtual tape library is not suitable for long time storage, because it has

Introduction to Oracle Secure Backup 1-9

Oracle Secure Backup Interfaces

limited storage capacity. If you back up to a virtual tape library, then you can take advantage of its faster backup and then use the volume migration feature of Oracle Secure Backup to migrate the data to tapes at a later point of time.

Device Names and Attachments

Because Oracle Secure Backup manages tape drive operations, it must be able to identify the tape drive and determine whether the tape drive is housed in a tape library. Oracle Secure Backup must further determine if a storage element is available for storing a volume while not in use by the tape drive. Thus, each tape device must be uniquely identified within Oracle Secure Backup by a user-defined name.

Oracle Secure Backup distinguishes a tape device and the means by which the tape device connects to a host. To be usable by Oracle Secure Backup, each tape device must have at least one attachment, which describes a data path between a host and the tape device. An attachment usually includes the identity of a host plus a attach point name in Linux or UNIX, a device name in Windows, or a NAS device name. In rare cases, additional information is needed for the attachment definition.

See Also:

■ "Adding Tape Devices to an Administrative Domain" on

page 5-10 to learn how to configure a tape device

■ Oracle Secure Backup Reference for a description of the mkdev

command aspec placeholder, which describes the syntax and naming conventions for device attachments

Oracle Secure Backup Interfaces

There are four different interfaces for accessing different elements of Oracle Secure Backup:

■ The obtool command line utility provides the fundamental interface for Oracle

Secure Backup functions, including configuration, media handling, and backup and restore of file-system files.

■ Oracle Enterprise Manager offers access to most Oracle Secure Backup functions

available through obtool as part of its Database Control and Grid Control interfaces.

■ Oracle Secure Backup includes its own Web-based interface, called the Oracle

Secure Backup Web t o ol, which exposes all functions of obtool. The Oracle Secure Backup Web tool is primarily intended for use in situations where Oracle Secure Backup is being used independently of an Oracle Database instance. It does not provide access to database backup and recovery functions.

The Oracle Secure Backup Web tool supports Internet Protocol v4 (IPv4), Internet Protocol v6 (IPv6), and mixed IPv4/IPv6 environments on all platforms that support IPv6.

■ Backup and restore operations for Oracle Database instances and configuration of

the Oracle Secure Backup media management layer are performed through the RMAN command-line client or through Oracle Enterprise Manager.

Note: Oracle Secure Backup documentation focuses on the use of

Enterprise Manager wherever possible, and describes the Oracle Secure Backup Web Tool only when there is no equivalent functionality in Enterprise Manager, as in a file-system backup.

1-10 Oracle Secure Backup Installation and Configuration Guide

System Requirements for Oracle Secure Backup

Disk Space Requirements for Oracle Secure Backup

When you install Oracle Secure Backup on Linux or UNIX, you load an install package for a particular operating system and perform the installation with the install package.

Tab le 1– 1 describes approximate disk space requirements.

Table 1–1 Disk Space Requirements for Oracle Secure Backup on Linux and UNIX

Oracle Secure Backup Installation Disk Space

Linux 75 MB

Solaris 130 MB

HP-UX 130 MB

AIX 610 MB

Tab le 1– 2 describes approximate disk space required for an installation of Oracle

Secure Backup on Windows with and without the administrative server.

Table 1–2 Disk Space Requirements for Oracle Secure Backup on Windows

Oracle Secure Backup Installation Disk Space

Administrative server (can include the media server, client, or both) 48 MB

Media server, client, or both (no administrative server) 31 MB

The disk space required for the

Oracle Secure Backup catalog depends on many

factors. But as a general rule, plan for catalog space equal to 250% of your largest index created after a backup.

Introduction to Oracle Secure Backup 1-11

Acquiring Oracle Secure Backup Installation Media

See Also: Oracle Secure Backup Administrator's Guide for guidelines

on the growth of the Oracle Secure Backup catalog over time

Other System Requirements for Oracle Secure Backup

Each host that participates in a Oracle Secure Backup administrative domain must run

TCP/IP. Oracle Secure Backup uses this protocol for all communication within each of

its components and between its components and other system components. Each appliance that employs a closed operating system, such as Network Attached

Storage (NAS) and tape servers, must support a version of Network Data Management Protocol (NDMP) described in "Oracle Secure Backup Host Access

Modes" on page 1-3.

Each host that participates in an Oracle Secure Backup administrative domain must also have some preconfigured way to resolve a host name to an IP address. Most systems use DNS, NIS, WINS, or a local hosts file to do this. Oracle Secure Backup does not require a specific mechanism. Oracle Secure Backup only requires that, upon presenting the underlying system software with an IP address you have configured, it obtains an IP address corresponding to that name.

The use of DHCP to assign IP addresses is not supported for hosts that participate in an Oracle Secure Backup administrative domain. Static IP addresses should be assigned to all hosts. If you cannot use static IP addresses, then you must ensure that the DHCP server guarantees that a given host is always assigned the same IP address.

Note: You can change the static IP of a host from one address to

another, but you must restart the Oracle Secure Backup

administrative server for the change to take effect.

On Oracle Secure Backup network installations, it is important that there be no duplicate host names. Index catalog data is stored in a directory based on the name of the client host. Duplicate host names would result in information related to backups from multiple clients being combined in a manner that could prevent successful restore operations from backup files.

You can configure Oracle Secure Backup to use WINS, the Microsoft Windows name resolution protocol, from UNIX hosts. Although this configuration is atypical, WINS name resolution from UNIX hosts can be a practical solution.

Linux Media Server System Requirement: SCSI Generic Driver

Configuring a Linux host for the Oracle Secure Backup media server role requires that the SCSI Generic driver be installed on that host. This driver is required for Oracle Secure Backup to interact with a tape device. The host must also be configured to automatically reload the driver after a restart.

See Also: "Prerequisites for Installation on Linux" on page 2-2

Acquiring Oracle Secure Backup Installation Media

Oracle Secure Backup installation media for each supported platform is available as a CD-ROM or as a ZIP file downloaded from the Oracle Technology Network (OTN) Web site for Oracle Secure Backup:

http://www.oracle.com/technology/products/secure-backup

1-12 Oracle Secure Backup Installation and Configuration Guide

The contents of the CD-ROM and download archive are identical. If you download the software from OTN, then you must store the downloaded file in a

temporary directory and extract the contents of the installation file.

Note: If you are installing Oracle Secure Backup on multiple

platforms, then you must download the ZIP file or acquire the CD-ROM for each platform.

Installation and Configuration Overview

You must install Oracle Secure Backup on your administrative server and on each

media server and client host in your administrative domain. During installation, the

installation software asks you to specify the roles played by each host. An administrative domain typically includes an administrative server, one or more media servers, and one or more client hosts.

The following steps provide an overview of Oracle Secure Backup installation and configuration:

1. Create an Oracle Secure Backup administrative server. a. Select a host to be the administrative server. This is the host you use to initiate

and manage backup and restore jobs.

Installation and Configuration Overview

b. Verify that this host meets the physical and network security requirements

discussed in "Choosing Secure Hosts for the Administrative and Media

Servers" on page 6-6

c. Verify that this host meets the system requirements discussed in "Disk Space

Requirements for Oracle Secure Backup" on page 1-11.

d. Install Oracle Secure Backup software on this host.

When this step is complete, the administrative domain is initialized. But the only host included in the administrative domain at this point is the administrative server.

2. Create Oracle Secure Backup media servers. a. Select one or more hosts to be media servers. These hosts must have a tape

device or other secondary storage device attached.

b. Verify that this host meets the physical and network security requirements

discussed in "Choosing Secure Hosts for the Administrative and Media

Servers" on page 6-6

c. Verify that this host meets the system requirements discussed in "Disk Space

Requirements for Oracle Secure Backup" on page 1-11.

d. Install Oracle Secure Backup software, including the Oracle Secure Backup

device driver, on each of these hosts. On UNIX and Linux platforms you are prompted during this step for Small

Computer System Interface (SCSI) device information. You obtain this

information using operating system-specific utilities, as described in

Appendix C, "Determining Linux SCSI Parameters".

3. Create Oracle Secure Backup clients.

Install Oracle Secure Backup software on each host with data to be backed up.

4. Configure the Oracle Secure Backup administrative domain.

Introduction to Oracle Secure Backup 1-13

About Upgrade Installations

The administrative server requires complete information about:

■ Each media server

■ Each tape device

■ Each attachment that associates a tape device with a media server

■ Client hosts, including any Network Data Management Protocol (NDMP)

clients such as Network Attached Storage (NAS) appliances

This step is documented in Chapter 5, "Configuring and Managing the

Administrative Domain". When this step is complete, Oracle Secure Backup is

ready to back up any data stored on clients in the administrative domain.

About Upgrade Installations

If you are upgrading an existing Oracle Secure Backup release 10.1 installation to release 10.3.0.x, then you must upgrade every host in the Oracle Secure Backup administrative domain to the same version. Oracle Secure Backup release 10.3 is incompatible with Oracle Secure Backup release 10.1.

If you are upgrading an existing Oracle Secure Backup release 10.2 installation to Oracle Secure Backup release 10.3.0.x, you must upgrade every host in your administrative domain to Oracle Secure Backup release 10.3.0.x. For example, you can upgrade your administrative server to Oracle Secure Backup 10.3.0.3 and upgrade your media servers and clients to Oracle Secure Backup 10.3.0.1.

In an upgrade installation, the Oracle Secure Backup catalogs (contained in the admin directory) are preserved, retaining configuration information and backup metadata for your administrative domain. This state information for your administrative domain, such as the backup catalog, host, user and device configuration information, and any scheduled backup jobs, is stored in the admin directory under the Oracle Secure Backup home on your administrative server.

Note: Oracle recommends backing up the administrative server

before upgrading.

Before upgrading an existing administrative domain to Oracle Secure Backup release

10.3, you must shut down drivers and background processes related to Oracle Secure Backup on all hosts. Upgrade the administrative server host first, and then the other hosts in the domain.

Brief instructions on each step are described in the following sections.

Preparing Administrative Domain Hosts for Upgrade to Release 10.3

Before performing an upgrade installation, you must stop the daemons and services related to Oracle Secure Backup on all hosts in your administrative domain. The preferred commands for stopping the Oracle Secure Backup daemons on Linux and UNIX are described in Oracle Secure Backup Reference.

On both Linux and Solaris administrative servers, it is also necessary to stop the Oracle Secure Backup Web tool processes and Oracle Secure Backup httpd daemon processes. Use the ps command to confirm that all the Oracle Secure Backup processes are stopped:

# /bin/ps -ef | grep ob

1-14 Oracle Secure Backup Installation and Configuration Guide

About Upgrade Installations

Use the kill -9 command to stop each process. On Windows hosts, you must stop the Oracle Secure Backup service:

1. Open the Services applet.

2. Right-click the Oracle Secure Backup Services service.

3. Select Stop.

Introduction to Oracle Secure Backup 1-15

About Upgrade Installations

1-16 Oracle Secure Backup Installation and Configuration Guide

Installing Oracle Secure Backup on Linux or

UNIX

This chapter explains how to install Oracle Secure Backup on hosts running Linux or UNIX.

This chapter contains the following sections:

■ Overview of Oracle Secure Backup Linux and UNIX Installation

■ Prerequisites for Installing Oracle Secure Backup on Linux and UNIX

■ Extracting Oracle Secure Backup from OTN Download on Linux or UNIX

■ Preparing to Install Oracle Secure Backup on Linux and UNIX

■ Creating the Oracle Secure Backup Home

■ Loading Oracle Secure Backup Software on Linux or UNIX Using setup Script

■ Configuring Installation Parameters in the obparameters File

■ Installing Oracle Secure Backup on Linux or UNIX with installob

■ Installing or Uninstalling Oracle Secure Backup on AIX

■ Installing or Uninstalling Oracle Secure Backup on HP-UX

■ Creating Attach Points with makedev

■ Performing an Upgrade Installation on Linux or UNIX

■ Uninstalling Oracle Secure Backup on Linux or UNIX

Overview of Oracle Secure Backup Linux and UNIX Installation

There are three steps to installing Oracle Secure Backup on a Linux or UNIX host:

1. Loading

Files required for installing Oracle Secure Backup are staged on the administrative

server, in a directory called the Oracle Secure Backup home. This step is

performed by a script named setup.

2. Installing

Oracle Secure Backup executables are deployed correctly for use on the host. This step is performed by a script named installob.

Installing Oracle Secure Backup on Linux or UNIX 2-1

Prerequisites for Installing Oracle Secure Backup on Linux and UNIX

Note: On a Solaris media server, installob also performs some

tape device configuration tasks, including installation of a required

device driver, and, optionally, attach point creation required for Oracle Secure Backup to access tape devices.

Creating attach points on each media server

This step is required for the Oracle Secure Backup device driver to access tape devices. You need the SCSI device parameters to perform this task.

Note: If you are installing Oracle Secure Backup in an Oracle Real

Application Clusters (Oracle RAC) environment, then you must install Oracle Secure Backup on each node in the cluster.

Prerequisites for Installing Oracle Secure Backup on Linux and UNIX

The prerequisites for installing Oracle Secure Backup on Linux and UNIX operating systems are:

■ Each host must have a network connection with a static IP address and run

TCP/IP.

■ The uncompress utility must be installed on your system.

Note: If the uncompress utility is not installed on your system, then

you can create an uncompress symbolic link pointing to the gunzip utility with the following command:

ln -s /bin/gunzip uncompress

■ You must have the SCSI parameters for each tape drive and tape library attached

to your Linux or UNIX media server. You can find them using the procedures in

Appendix C, "Determining Linux SCSI Parameters". You need this information

when creating an attach point for each tape device.

■ On a Redhat Linux system, ensure that you install the sg3_utils and the

sg3_utils-libs RPM packages. These packages are required for successfully running the sg_map command.

■ You must be able to log in to each host with root privileges to perform the

installation.

Prerequisites for Installation on Linux

For each Linux media server, ensure that the SCSI Generic (SG) driver is installed. This driver is required for Oracle Secure Backup to interact with a tape device.

Kernel modules are usually loaded directly by the facility that requires them, if the correct settings are present in the /etc/modprobe.conf file. However, it is sometimes necessary to explicitly force the loading of a module at start time.

For example, on RedHat Enterprise Linux, the module for the SCSI Generic driver is named sg. Red Hat Enterprise Linux checks at start time for the existence of the /etc/rc.modules file, which contains various commands to load modules.

2-2 Oracle Secure Backup Installation and Configuration Guide

Prerequisites for Installing Oracle Secure Backup on Linux and UNIX

Note: The rc.modules file is necessary, and not rc.local,

because rc.modules runs earlier in the start process.

On RedHat Enterprise Linux, you can use the following commands to add the sg module to the list of modules configured to load as root at start time:

# echo modprobe sg >> /etc/rc.modules # chmod +x /etc/rc.modules

An Oracle Secure Backup user must be mapped to a Linux or UNIX user that has read/write permissions to the /dev/sg devices. One way to accomplish this goal is to set the permissions to 666 for the /dev/sg devices.

Required SCSI Tape Device Parameters on Linux and UNIX

Oracle Secure Backup supports both SCSI and Fibre Channel devices for Linux and UNIX. To configure a media server to communicate with its attached tape devices, you must have the SCSI parameters for each tape device.

Tab le 2– 1 lists the required SCSI parameters for each platform.

Table 2–1 Required SCSI Parameters

Platform Linux HP-UX AIX

Host bus adapter x x

SCSI bus address

SCSI bus name-instance x x x

Target I D x x x

SCSI LUN x x x

In Linux, SCSI bus addresses are referred to as channels.

You must also assign each tape drive and tape library an Oracle Secure Backup

logical unit number, as described in "Assigning Oracle Secure Backup Logical Unit

Numbers to Devices" on page 2-3.

Note: Do not confuse the SCSI LUN with the Oracle Secure Backup

LUN. The SCSI LUN is part of the hardware address of the tape device, while the Oracle Secure Backup logical unit number is part of the device special filename.

Assigning Oracle Secure Backup Logical Unit Numbers to Devices

Each tape drive and tape library must be assigned an Oracle Secure Backup LUN during the configuration process. This number is used to generate unique device names during device configuration. Oracle Secure Backup logical unit numbers are assigned as needed automatically on Windows. For each UNIX or Linux media server, however, you must select Oracle Secure Backup logical unit numbers for each device as part of planning your administrative domain.

There is no required order for assigning Oracle Secure Backup logical unit numbers. They are typically assigned sequentially, starting at 0, for each tape device of a given type, whether tape library or tape drive. That is, tape libraries are typically numbered

Installing Oracle Secure Backup on Linux or UNIX 2-3

Extracting Oracle Secure Backup from OTN Download on Linux or UNIX

0, 1, 2 and so on, and tape drives are also numbered 0, 1, 2 and so on. The maximum value for an Oracle Secure Backup logical unit number is 31.

On Linux or UNIX, the resulting device special file names for tape libraries are

/dev/obl1, /dev/obl2, /dev/obl3 and so on, and the names for tape drives are /dev/obt1, /dev/obt2, /dev/obt3 and so on. On Windows, the resulting tape

library names are //./obl1, //./obl2, //./obl3 and so on, and the names for tape drives are //./obt1, //./obt2, //./obt3 and so on, where these names are assigned automatically during the installation of Oracle Secure Backup on Windows.

See Also: "Identifying and Configuring Linux Attach Points" on

page 2-18

Note: The Oracle Secure Backup logical unit number should not be

confused with the SCSI LUN. The latter is part of the hardware address of the tape device, while the Oracle Secure Backup logical unit number is part of the device special filename.

Extracting Oracle Secure Backup from OTN Download on Linux or UNIX

This section explains how to download the Oracle Secure Backup software. To download and extract the Oracle Secure Backup installation software:

1. Log in to your host as a user with root privileges.

2. Create a directory called osbdownload on a file system with enough free space to

hold the downloaded installation file:

mkdir /tmp/osbdownload

3. Open a Web browser and go to the Oracle Secure Backup Web site on Oracle

Technology Network (OTN):

http://www.oracle.com/technology/products/secure-backup

4. Click Free Download.

The Oracle Technology Network Developer License Terms page appears.

5. Read Export Controls on the Programs and select the Yes, I accept... option.

Read the Oracle Technology Network Development License Agreement and click I Accept.

The Oracle Secure Backup Downloads page appears.

6. Select the Accept License Agreement option, and click the link for the version of

Oracle Secure Backup release 10.3 specific to your operating system.

Note: If you have multiple operating systems in your environment,

then you must perform multiple downloads of the Oracle Secure Backup release 10.3 software.

7. Save the Oracle Secure Backup release 10.3 installation software to a temporary

directory.

8. Expand the compressed installation software to the osbdownload directory you

created in step 2.

2-4 Oracle Secure Backup Installation and Configuration Guide

Creating the Oracle Secure Backup Home

You now have all of the files required to install Oracle Secure Backup release 10.3.

Preparing to Install Oracle Secure Backup on Linux and UNIX

Perform the following actions before installing Oracle Secure Backup:

■ Select hosts for the administrative server, media server, and client roles, as

described in "Installation and Configuration Overview" on page 1-13.

■ Collect the SCSI parameters for each tape drive and tape library attached to your

Linux and UNIX media servers. You need this information when creating an attach point for each tape device.

■ Disable any system software that scans and opens arbitrary SCSI targets before

adding Oracle Secure Backup tape devices to an administrative domain. If Oracle Secure Backup must contend with other system software (such as monitoring software) for access to tape libraries and drives, then unexpected behavior can result.

■ If you are installing Oracle Secure Backup in an Oracle RAC environment, then

you must install Oracle Secure Backup on each node in the cluster.

Creating the Oracle Secure Backup Home

You must create an Oracle Secure Backup home. The Oracle Secure Backup setup program uses this directory to store installation files specific to your host.

Note: Oracle recommends that you use

/usr/local/oracle/backup as your Oracle Secure Backup home. If you use a different directory, then the setup program prompts you to confirm your selected directory.

Note: To enable users other than root to use obtool or the Oracle

Secure Backup Web tool, install Oracle Secure Backup to a file system that can use the suid mechanism. You can do this by excluding the nosuid option from the /etc/fstab file entry for that file system.

See also: "Oracle Secure Backup Home Directory" on page A-1 and

Oracle Secure Backup Administrator's Guide for more details about the Oracle Secure Backup home.

To create the Oracle Secure Backup home:

1. Log into the host as root.

2. Run the following command:

# mkdir -p /usr/local/oracle/backup

Installing Oracle Secure Backup on Linux or UNIX 2-5

Loading Oracle Secure Backup Software on Linux or UNIX Using setup Script

The setup script performs the loading process, in which packages of files required to install Oracle Secure Backup are extracted from the installation media and staged in the Oracle Secure Backup home for later use by the installob installation script.

To load Oracle Secure Backup into an Oracle Secure Backup home directory for later installation on one or more Linux or UNIX platforms:

1. Log into your Linux or UNIX operating system as root.

2. Change to the Oracle Secure Backup home directory created in "Creating the

Oracle Secure Backup Home" on page 2-5. For example:

# cd /usr/local/oracle/backup

3. Run the setup script from your installation media or extracted archive directory.

Enter the following command, where /media_dir is the CD-ROM mount point or the directory containing the files extracted from the downloaded archive:

# /media_dir/setup

For example, if you downloaded an archive from Oracle Technology Network (OTN) and extracted the setup software to the /tmp/osbdownload/OB directory, then you would run setup as follows:

# /tmp/osbdownload/OB/setup

Oracle Secure Backup expands compressed files in a temporary directory during installation. To specify a directory for this expansion, you can use the -t option to the setup command. The following example specifies that setup should use directory_name for the expansion:

# /media_dir/setup -t directory_name

The setup script displays the following messages:

■ A welcome message stating the Oracle Secure Backup version number and

then displays progress messages

■ A message stating the platform

■ Various progress messages as it loads the package

When the script finishes, it prompts you to unmount and remove the installation CD-ROM.

Note: At this point the loading process is complete. The files

required to install Oracle Secure Backup are stored in the Oracle Secure Backup home on this host.

4. The setup script prompts you to start the installob script to install Oracle

Secure Backup on the local host. Choose one of these options:

■ Enter no to run installob later, or if you must customize some aspect of

your installation process using the obparameters file, as described in

"Configuring Installation Parameters in the obparameters File" on page 2-7.

If you enter no, then setup tells you how to continue installation later, and setup exits.

2-6 Oracle Secure Backup Installation and Configuration Guide

Configuring Installation Parameters in the obparameters File

See Also: "Installing Oracle Secure Backup on Linux or UNIX with

installob" on page 2-8 for instructions on starting installob

■ Enter yes to start the installob script. The steps for running installob

are described in "Installing Oracle Secure Backup on Linux or UNIX with

installob" on page 2-8.

Note: If the setup script is interrupted, then some temporary files,

named OBnnnn or OBnnnn.Z, might remain in /usr/tmp. You can safely delete these files.

Configuring Installation Parameters in the obparameters File

The setup script creates a file called obparameters in the install subdirectory of the Oracle Secure Backup home. For example, if the Oracle Secure Backup home is in the default location /usr/local/oracle/backup, then the obparameters file is located at /usr/local/oracle/backup/install/.

During the installation process the setup script gives you the choice of accepting the default settings in the obparameters file or customizing those settings. In most cases, it is not necessary to change the defaults in the obparameters file. However, you should review the parameters you can control in this file as part of planning your installation, and determine whether any of them should be changed.

The obparameters file is plain text that can be edited using any standard text editor. Reasons to change the parameters in the obparameters file include:

■ You can specify a different key size for enhanced security or performance

See Also: "Setting the Key Size in obparameters" on page 6-18

■ You can customize installation directories and symbolic links created during

installation on different platforms.

■ If you are using Oracle Secure Backup to back up Oracle Database files to tape,

then you can create an Oracle Secure Backup user named oracle for use in RMAN backups. You can associate this user with Linux or UNIX operating system credentials by setting parameters in obparameters.

Note:

■ You can also configure a preauthorized oracle user later. Before

electing to create an Oracle Secure Backup oracle user, be aware that this choice involves a trade-off between convenience and security.

■ If you intend to use Oracle Secure Backup to perform one-time,

RMAN-initiated, or unprivileged backup operations on Windows clients, then you must modify the Oracle Secure Backup admin and oracle users to assign them Windows credentials (a domain, user name and password) that are valid at the client with required privileges after you complete the Oracle Secure Backup installation. Otherwise, Oracle Secure Backup cannot perform these types of backup operations. This requirement applies regardless of the platform that acts as the administrative server.

Installing Oracle Secure Backup on Linux or UNIX 2-7

Installing Oracle Secure Backup on Linux or UNIX with installob

See Also:

■ Oracle Secure Backup Administrator's Guide for more information

about the preauthorized oracle user and RMAN backups.

■ Appendix B, "Oracle Secure Backup obparameters Installation

Parameters"

Installing Oracle Secure Backup on Linux or UNIX with installob

To install the Oracle Secure Backup software on Linux or UNIX:

1. Ensure that the SCSI parameters for each tape device available.

You can enter these parameters to create an attach point for each SCSI device as part of the initial installation. Solaris 10 systems have special device configuration procedures. See "Configuring the Solaris sgen Driver to Provide Oracle Secure

Backup Attach Points" on page 2-18.

2. Start the installob script.

The Oracle Secure Backup setup script ends by asking to start the installation process using the installob script. If you enter yes to this question, then the setup script runs the installob script for you.

Otherwise, start installob from the command prompt. While logged in as

root, go to the Oracle Secure Backup home and enter the following command:

install/installob

The installob script displays a welcome message and tells you that most of its questions have default answers, which you can select by simply pressing Enter.

3. Confirm the settings in the obparameters file.

This step depends upon the value of the customized obparameters parameter in the obparameters file described in "Configuring Installation Parameters in the

obparameters File" on page 2-7. The two possibilities are:

■ You have edited the obparameters file and set customized

obparameters to yes.

In this case, the installob script assumes that you have made the changes you want in the obparameters file and uses those parameters during the installation. Continue to step 4.

■ The customized obparameters parameter is set to no, which is the default.

In this case, the installob script asks if you have reviewed and customized the obparameters file. Choose one of these options:

– Enter yes or press the Enter key to indicate that you do not want to

customize the obparameters file. Continue to step 4.

– Enter no to indicate that you do want to customize the obparameters

file. The installob script tells you to rerun the script after reviewing obparameters. The installob script then exits.

See Also: "customized obparameters" on page B-1 for details about

the customize obparameters parameter.

4. Specify the host role.

2-8 Oracle Secure Backup Installation and Configuration Guide

Installing Oracle Secure Backup on Linux or UNIX with installob

You de term ined the roles for each host when planning your administrative domain. Choose one of these options:

■ Enter a to install the software for an administrative server.

If you choose this option, then installob also installs the software required for the media server and client roles.

■ Enter b to install the software for a media server.

If you choose this option, then installob also installs the software required for the client role.

■ Enter c to install the software for a client.

You can add or remove a role later with the chhost command in obtool.

Note:

■ If you choose an administrative server or media server

installation, then installob installs the software necessary for the media server role. However, the host does not have the media server role until the admin user grants that role with the chhost command after Oracle Secure Backup is installed.

■ To add the media server role to an administrative server or client

after initial installation, you must create attach points using makedev or installob. See Oracle Secure Backup Reference for details.

See Also: "Installation and Configuration Overview" on page 1-13 to

learn more about the roles of administrative server, media server and client in Oracle Secure Backup

This procedure describes installation for an administrative server.

5. Create a password for the Oracle Secure Backup keystore.

The installob script prompts for a password for the keystore and then prompts you to re-enter the password. Oracle recommends that you choose a password of at least 8 characters in length that contains a mixture of alphabetic and numeric characters. When you enter the password, the password is not echoed to the display.

6. Create a password for the Oracle Secure Backup administrative server.

The installob script asks for a password for the admin user, and then asks you to reenter it for confirmation. Oracle recommends that you choose a password of at least 8 characters in length, containing a mixture of alphabetic and numeric characters. When you type in the password, your entry is not echoed to the display.

The minimum password length is determined by the minuserpasswordlen security policy. Its default value is 0, which means a null password is permitted. You can change the value of minuserpasswordlen by setting the minimum user password length parameter in the obparameters file.

See Also: Oracle Secure Backup Reference for more information on the

minuserpasswordlen security policy

Installing Oracle Secure Backup on Linux or UNIX 2-9

Installing Oracle Secure Backup on Linux or UNIX with installob

Note: The practice of supplying a password in clear text on a

command line or in a command script is not recommended by Oracle. It is a security vulnerability. The recommended procedure is to have the user be prompted for the password.

Enter an e-mail address for notifications.

The installob script asks for an e-mail address to which Oracle Secure Backup sends notifications.

Note: The default from address for e-mails generated by Oracle

Secure Backup is root@fqdn, where fqdn is the fully qualified domain name of the Oracle Secure Backup administrative server. You can change this default from address after installation. See Oracle Secure Backup Reference for more information.

The installob script now displays informational messages as it installs and configures the Oracle Secure Backup software on this host. This process might take several minutes to complete.

8. If you are installing Oracle Secure Backup on an administrative server or media

server, then the installob script asks to configure a tape drive or tape library.

Note: In installob, the term configuring refers to creating the

attach points required for Oracle Secure Backup to communicate with the tape devices. Do not confuse this step with configuring the administrative domain with information about tape devices and media servers, as described in Chapter 5, "Configuring and Managing

the Administrative Domain".

The installob script includes software required for both the administrative server and media server roles in an administrative server installation. Therefore, this prompt is displayed when installing on an administrative server even if there are no attached tape drives or tape libraries.

Although this procedure discusses SCSI tape libraries and tape drives, it also applies to a Fibre Channel tape device.

Choose from these options:

■ Enter no if you do not want to create attach points for your tape devices now,

or if you are installing on an administrative server with no tape devices attached.

Note: On Linux and Solaris systems Oracle recommends that you

enter no when asked to configure tape libraries or drives during installation.

On Linux, the recommended method is to use the /dev/sg devices for attach points, as described in "Identifying and Configuring Linux

Attach Points" on page 2-18. For Solaris systems, see "Configuring the Solaris sgen Driver to Provide Oracle Secure Backup Attach Points" on

page 2-18.

2-10 Oracle Secure Backup Installation and Configuration Guide

Installing Oracle Secure Backup on Linux or UNIX with installob

If you choose to create attach points later, or if you add a tape device to a media server in the future, then see "Creating Attach Points with makedev" on page 2-12 for two alternative methods of completing this task.

■ Enter yes to configure tape devices now.

To create attach points, the installob script asks if tape libraries are connected to this host, and if so, what the SCSI parameters are for each tape library. After you have entered the tape library SCSI parameters, the installob script asks you to confirm your entries.

When you have entered information about tape libraries attached to this host, the installob script asks the same questions about standalone tape drives.

Tab le 2– 2 lists the information required by installob for each platform. For

the device type, enter a d for a tape drive or l (lowercase L) for a tape library.

Table 2–2 Information Required by installob

Platform Linux HP-UX Solaris AIX

Oracle Secure Backup LUN

Device type x x x x

Host bus adapter x x

SCSI bus address

SCSI bus name-instance x x x x

Target I D x x x x

xxxx

SCSI LUN x x x x

Do not confuse the Oracle Secure Backup logical unit number with the SCSI LUN.

In Linux, SCSI bus addresses are referred to as channels.

Enter each parameter value in response to the prompts from the installob script. You can press Enter to accept a default value, but the default SCSI parameters offered by the script might not be correct.

When you have entered the SCSI parameters for all tape libraries and tape drives attached to this host, the installob script begins device driver configuration and device special file creation.

Record the name of the device special file created for each tape device. The filename is needed when you configure the attachment for the tape device, as part of configuring the Oracle Secure Backup domain. The filename should be /dev/obtn for tape drives, and /dev/obln for tape libraries, where n is the Oracle Secure Backup LUN you entered for the tape device.

If you enter the wrong parameters, then device special file creation fails. To resolve the resulting errors, run installob again, entering the correct values, or use the makedev script described in "Creating Attach Points with

makedev" on page 2-12.

When the installob script has created attach points for all tape devices attached to this host, it reminds you that you must configure these tape devices through the Oracle Secure Backup Web interface or the command line using the mkdev command in obtool.

Installing Oracle Secure Backup on Linux or UNIX 2-11

Installing or Uninstalling Oracle Secure Backup on AIX

The installob script displays a summary of installation activities during this

session and exits. This installation summary does not include any information about device special file creation performed during the installob session.

Installing or Uninstalling Oracle Secure Backup on AIX

The installation and uninstallation procedures for AIX and Linux/UNIX are identical. During Oracle Secure Backup installation, the Oracle Secure Backup admin user is

mapped by default to UNIX user root and UNIX group root. In this configuration, Oracle Secure Backup requires that the user root be a member of the group root to back up the file system successfully. AIX does not define a group root by default. If the group root does not exist on your AIX system, then you must create it and make user root a member of it.

Note: You can change this mapping of the Oracle Secure Backup

admin after installation.

See Also:

■ "Installing Oracle Secure Backup on Linux or UNIX with

installob" on page 2-8 and "Uninstalling Oracle Secure Backup on Linux or UNIX" on page 2-20

■ "Identifying and Configuring AIX Devices" on page 2-13

Installing or Uninstalling Oracle Secure Backup on HP-UX

The installation and uninstallation procedures for HP-UX and Linux/UNIX are identical.

See Also:

■ "Installing Oracle Secure Backup on Linux or UNIX with

installob" on page 2-8 and "Uninstalling Oracle Secure Backup on Linux or UNIX" on page 2-20

■ "Identifying and Configuring HP-UX Devices" on page 2-16

Creating Attach Points with makedev

The makedev script in Oracle Secure Backup is used to create an attach point for a

single tape drive. Internally, the installob script calls makedev once for each tape device specified during installation. Alternatively, you can run makedev outside of installob to create all required attach points.

The makedev script can also replace an old attach point, rather than creating a new one. If you reuse an Oracle Secure Backup LUN for a tape library or drive, then the attach point for the old tape device is overwritten.

If you must create attach points for several tape devices, then it may be more convenient to use the installob script.

Tab le 2– 3 lists the information required by makedev for each platform. For the device

type, enter a d for a tape drive or l (lowercase L) for a tape library.

2-12 Oracle Secure Backup Installation and Configuration Guide

Table 2–3 Information Required by makedev

Platform Linux HP-UX AIX

Oracle Secure Backup LUN

Device type x x x

Host bus adapter x x

SCSI bus address x x

SCSI bus name-instance x x x

Target I D x x x

SCSI LUN x x x

Do not confuse the Oracle Secure Backup logical unit number with the SCSI LUN.

xxx

See Also: Oracle Secure Backup Reference for makedev syntax

Identifying and Configuring AIX Devices

To access SCSI or Fibre Channel tape devices, Oracle Secure Backup requires the following identifying information about how the devices are attached to their hosts:

Creating Attach Points with makedev

■ SCSI bus name

■ Target I D

■ LUN

This information may not be readily available for all attached devices using standard operating system commands.

Identifying and Configuring AIX Devices in a Switched Fibre Channel Configuration

If you use Fibre Channel tape and media changer devices in a switched environment on AIX, you can use the standalone tool obscan to assist with gathering device information. The SCSI ID and LUN are required to correctly configure the devices for use by Oracle Secure Backup.

The obscan tool is provided as an optional tool for device identification in AIX environments. The obscan executable is located in the cdtools directory of the

Oracle Secure Backup CD or CD image. The syntax is as follows, where dname is

the device file name of the SCSI bus or Fibre Channel fabric to scan:

obscan dname

The obscan tool determines the SCSI ID and LUN for every tape and media changer device in a switched configuration.

To identify and configure AIX devices with obscan and makedev:

1. Log on as root.

You must have operating system privileges to access devices, which is often root access, to run obscan.

2. Run obscan for each SCSI and Fibre Channel adapter with tape devices to be

used by

Oracle Secure Backup.

In the following example, obscan gathers information about the tape devices connected to the SCSI bus identified by the device file /dev/scsi2:

Installing Oracle Secure Backup on Linux or UNIX 2-13

Creating Attach Points with makedev

obscan /dev/scsi2

DEVICE information for /dev/scsi2

Target-id : 0, Lun : 0 Vendor : ADIC Product : FastStor 2

Target-id : 5, Lun : 0 Vendor : HP Product : Ultrium 2-SCSI

Total count of Media Changers and/or Tape devices found : 2

In this second example, obscan gathers information about the tape devices connected to the Fibre Channel fabric identified by /dev/fssci0:

obscan /dev/fscsi0

DEVICE information for /dev/fscsi0

Target-id : 6423827, Lun : 0 Vendor : ADIC Product : Scalar 24 World Wide Name : 2001006045175222

Target-id : 6423827, Lun : 1 Vendor : IBM Product : ULTRIUM-TD2 World Wide Name : 2001006045175222

Target-id : 6423827, Lun : 2 Vendor : IBM Product : ULTRIUM-TD2 World Wide Name : 2001006045175222

Target-id : 6491411, Lun : 0 Vendor : ADIC Product : Scalar i500 World Wide Name : 2400005084800672

Target-id : 6491411, Lun : 1 Vendor : IBM Product : ULTRIUM-TD3 World Wide Name : 2400005084800672

Target-id : 6491411, Lun : 2 Vendor : IBM Product : ULTRIUM-TD3 World Wide Name : 2400005084800672

Target-id : 6491411, Lun : 3 Vendor : IBM Product : ULTRIUM-TD3 World Wide Name : 2400005084800672

Target-id : 6491411, Lun : 4 Vendor : IBM Product : ULTRIUM-TD3 World Wide Name : 2400005084800672

Total count of Media Changers and/or Tape devices found : 8

3. Navigate to the install directory in your Oracle Secure Backup home. For

example:

# cd /usr/local/oracle/backup/install

4. Enter the makedev command at the shell prompt:

# makedev

5. At the prompts, enter the information required to create attach points used within

Oracle Secure Backup to identify devices for backup and restore operations.

2-14 Oracle Secure Backup Installation and Configuration Guide

Creating Attach Points with makedev

In the following example, the attach point /dev/obl8 is created for the ADIC FastStor 2 library attached to scsi2 having the target id 0 and lun 0:

makedev Enter logical unit number 0-31 [0]: 8 Enter 'd' if this device is a tape drive or 'l' if a SCSI-2 addressable tape library [d]: l Enter SCSI bus name: scsi2 Enter SCSI target id 0-16777215: 0 Enter SCSI logica l unit number (lun) 0-7 [0]: 0 /dev/obt8 created

In this second example, the attach point /dev/obl9 is created for the ADIC Scalar 24 library attached to fsci0 having the target id 6423827 and lun 0:

makedev Enter logical unit number 0-31 [0]: 9 Enter 'd' if this device is a tape drive or 'l' if a SCSI-2 addressable tape library [d]: l Enter SCSI bus name: fscsi0 Enter SCSI target id 0-16777215: 6423827 Enter SCSI logical unit number (lun) 0-7 [0]: 0 /dev/obl9 created

The makedev script creates the attach point, displaying messages indicating its progress.

Identifying and Configuring AIX Devices in a Point-to-Point or FC-AL Configuration

In a point-to-point or FC-AL configuration, no tool is provided to help you determine the SCSI ID and LUN. However, for IBM-supported devices in these configurations, you can use the lsattr command.

To identify and configure AIX devices with lsattr and makedev:

1. Log on as root.

You must have operating system privileges to access devices, which is often root access, to run lsattr.

2. Run lsattr for each SCSI and Fibre Channel adapter with tape devices to be

used by The following lsattr example displays the attribute names, current values,

descriptions, and user-settable flag values for the rmt0 device:

user: lsattr -El rmt0 block_size 512 BLOCK size (0=variable length) True delay 45 Set delay after a FAILED command True density_set_1 0 DENSITY setting #1 True density_set_2 0 DENSITY setting #2 True extfm yes Use EXTENDED file marks True location Location Label True lun_id 0x1000000000000 Logical Unit Number ID False mode yes Use DEVICE BUFFERS during writes True node_name 0x1000006045175222 FC Node Name False res_support no RESERVE/RELEASE support True ret_error no RETURN error on tape change or reset True rwtimeout 144 Set timeout for the READ or WRITE commandTrue scsi_id 0x2 SCSI ID False var_block_size 0 BLOCK SIZE for variable length support True ww_name 0x2001006045175222 FC World Wide Name False

Oracle Secure Backup.

Installing Oracle Secure Backup on Linux or UNIX 2-15

Creating Attach Points with makedev

You can convert the hexadecimal values of lun_id and scsi_id (shown in bold) to decimal so that they are usable by the Oracle Secure Backup makdev command. After conversion, the SCSI LUN ID is 281474976710656 and the SCSI ID is 2.

3. Navigate to the install directory in your Oracle Secure Backup home. For

example:

# cd /usr/local/oracle/backup/install

4. Enter the makedev command at the shell prompt:

# makedev

5. At the prompts, enter the information required to create attach points used within

Oracle Secure Backup to identify devices for backup and restore operations. The makedev script creates the attach point, displaying messages indicating its

progress.

Identifying and Configuring HP-UX Devices

To access SCSI or Fibre Channel tape devices on HP-UX using the makedev script,

Oracle Secure Backup requires the following identifying information about how the

devices are attached to their hosts:

■ SCSI bus number instance

■ Target I D

■ LUN

To gather device information in HP-UX, you can use the ioscan utility located in /usr/sbin on the HP-UX operating system. The ioscan command searches the system and lists any devices that it finds. You must have root access to run ioscan.

Note: The ioscan tool is provided as an optional tool for device

identification in HP-UX environments. The ioscan tool is not included as part of any

Oracle Secure Backup installation.

To identify and configure HP-UX devices:

1. Log on as root.

2. Execute the following command:

/usr/sbin/ioscan -f

Running the command with the -f option displays full information about the system configuration including device class, instance number, device or interface driver, software state, and hardware type.

Example 2–1 shows sample output for ioscan -f. The bus number instance,

target ID, SCSI LUN, and device description for each device are shown in bold.

Example 2–1 ioscan -f

$ /usr/sbin/ioscan -f

Class I H/W Path Driver S/W State H/W Type Description ... ext_bus 3 0/1/1/1 mpt CLAIMED INTERFACE SCSI Ultra320 target 11 0/1/1/1.1 tgt CLAIMED DEVICE

2-16 Oracle Secure Backup Installation and Configuration Guide

Creating Attach Points with makedev

autoch 4 0/1/1/1.1.0 schgr CLAIMED DEVICE ADIC FastStor 2 target 10 0/1/1/1.2 tgt CLAIMED DEVICE tape 8 0/1/1/1.2.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI ... fcp 2 0/2/1/0.99 fcp CLAIMED INTERFACE FCP Domain ext_bus 9 0/2/1/0.99.15.255.1 fcpdev CLAIMED INTERFACE FCP Device Interface target 1 0/2/1/0.99.15.255.1.3 tgt CLAIMED DEVICE

autoch 8 0/2/1/0.99.15.255.1.3.0 schgr CLAIMED DEVICE ADIC Scalar 24 tape 19 0/2/1/0.99.15.255.1.3.1 stape CLAIMED DEVICE IBM ULTRIUM-TD3 tape 20 0/2/1/0.99.15.255.1.3.2 stape CLAIMED DEVICE IBM ULTRIUM-TD3

3. Using the ioscan output, make a note of the bus number, target ID, and SCSI

LUN for the tape devices.

Tab le 2– 4 shows the relevant information from Example 2–1.

Table 2–4 Information Required by makedev

Device Type Name

Tape lib ra ry

SCSI ADIC FastStor 2 3 1 0

Instance Target ID SCSI LUN

(autoch)

Tape drive (tape) SCSI HP Ultrium 2 3 2 0

Bus Number

Tape lib ra ry

FC ADIC Scalar 24 9 3 0

(autoch)

Tape drive (tape) FC IBM ULTRIUM-TD3 9 3 1

Tape drive (tape) FC IBM ULTRIUM-TD3 9 3 2

4. Use makedev to create attach points so that Oracle Secure Backup can identify

devices for backup and restore operations. The following example runs makedev using the information in Tab le 2– 4. The

example creates the attach point /dev/obl/8 for the ADIC FastStor 2 library on SCSI bus instance 3 with the target ID 1 and SCSI LUN 0.

% makedev Enter logical unit number 0-31 [0]: 8 Enter 'd' if this device is a tape drive or 'l' if a SCSI-2 addressable tape library [d]: l Enter SCSI bus instance: 3 Enter SCSI target id 0-16777215: 1 Enter SCSI logical unit number (lun) 0-7 [0]: 0 /dev/obl/8 created

The following example runs makedev using the information in Tab le 2– 4. The example creates the attach point /dev/obt/9m for the HP Ultrium 2 tape drive on SCSI bus instance 3 with the target ID 2 and SCSI LUN 0.

% makedev Enter logical unit number 0-31 [0]: 9 Enter 'd' if this device is a tape drive or 'l' if a SCSI-2 addressable tape library [d]: d Enter SCSI bus instance: 3 Enter SCSI target id 0-16777215: 2 Enter SCSI logical unit number (lun) 0-7 [0]: 0 /dev/obt/9m created

Installing Oracle Secure Backup on Linux or UNIX 2-17

Creating Attach Points with makedev

Identifying and Configuring Linux Attach Points

Oracle recommends that you use the /dev/sg devices as attach points with Oracle

Secure Backup on Linux. The use of the Oracle Secure Backup /dev/ob devices

has certain limitations that may not be acceptable in some environments. For example, the LUN cannot be greater than 7, and the SCSI bus number cannot be greater than 1. The existing method of using /dev/ob* devices continues to work for a tape device that does not fall into the limitation category.

To identify the /dev/sg that corresponds to the tape device you are interested in, you can use the sg_map command.

To configure Linux attach points:

1. Execute the following Linux command:

sg_map -i -x

Example 2–2 shows sample output.

Example 2–2 sg_map -i -x

sg_map -i -x /dev/sg0 0 0 0 0 0 /dev/sda DELL PERC Stripe V1.0 /dev/sg1 0 0 1 0 0 /dev/sdb DELL PERC Stripe V1.0 /dev/sg2 0 0 2 0 0 /dev/sdc DELL PERC Volume V1.0 /dev/sg3 1 0 1 0 8 ADIC FastStor 2 G12r /dev/sg4 1 0 2 0 1 /dev/nst0 HP Ultrium 2-SCSI F53A /dev/sg5 2 0 0 0 1 /dev/nst1 IBM ULTRIUM-TD2 5AT0 /dev/sg6 2 0 0 1 8 ADIC Scalar 24 310A /dev/sg7 2 0 1 0 1 /dev/nst2 IBM ULTRIUM-TD2 5AT0 /dev/sg8 2 0 1 1 8 ADIC Scalar 24 310A /dev/sg9 2 0 2 0 1 /dev/nst3 IBM ULTRIUM-TD3 54K1 /dev/sg10 2 0 3 0 1 /dev/nst4 IBM ULTRIUM-TD3 54K1 /dev/sg11 2 0 3 1 8 ADIC Scalar 24 310A

2. Using the sg_map output, make a note of the attach point for each tape device that

you want to configure.

Tab le 2– 5 shows a tape library and tape drive from Example 2–2.

Table 2–5 Information Required by mkdev

Device Type Name Path

Tape library ADIC FastStor 2 /dev/sg3

Tape drive HP Ultrium 2 /dev/sg4

3. Use the mkdev command in obtool to create attach points so that Oracle Secure

Backup can identify devices for backup and restore operations. The following example creates attach points for the tape library and tape drive

shown in Tab le 2– 5.

ob> mkdev -t library -o -a node1:/dev/sg3 lib1 ob> mkdev -t tape -o -a node1:/dev/sg4 -l lib1 -d 1 tape1

Configuring the Solaris sgen Driver to Provide Oracle Secure Backup Attach Points

Prior to Oracle Secure Backup 10.3.0.3, Oracle Secure Backup provided a loadable kernel driver to control the library (changer) and tape (sequential) devices. Starting with Oracle Secure Backup 10.3.0.3, this kernel driver is removed. The standard sgen

2-18 Oracle Secure Backup Installation and Configuration Guide

Creating Attach Points with makedev

driver that is included with Solaris now provides the functionality provided by the kernel driver.

Enabling the Solaris sgen Driver for Changer and Sequential Devices

You need to enable the Solaris sgen driver for changer and sequential devices before you install Oracle Secure Backup.

Use the following steps to enable the Solaris sgen driver for sequential and changer devices:

1. If your host does not have a previous installation of Oracle Secure Backup, skip to

Step 2. When you enable the Solaris sgen driver on a host that already has Oracle Secure

Backup installed, the attach points and device configuration will be lost. You need to first uninstall Oracle Secure Backup using the steps described in "Uninstalling

Oracle Secure Backup on Linux or UNIX" on page 2-20.

While uninstalling, it is recommended that you remove the backup directory. You can retain that admin directory.

2. Enable sequential (01) and changer (01) devices by adding the following line in the

/kernel/drv/sgen.conf file:

device-type-config-list="sequential","changer";

Note: If device-type-config-list is already defined for other

devices, add "sequential" and "changer" to the existing list in the sgen.conf file.

3. Verify that there is an entry for the sgen driver in /etc/minor_perm.

An example of an entry in this file is as follows:

"sgen * 0600 root sys"

4. Verify that there is an entry for the sgen driver in /etc/name_to_major.

The following is an example of an entry in this file:

"sgen 151"

5. Remove the links in /dev/scsi/changer and /dev/scsi/sequential using

the following commands:

rm -r /dev/scsi/changer rm -r /dev/scsi/sequential

6. Unconfigure the st driver for type 01 devices using the following command:

update_drv -d -i '"scsiclass,01"' st

7. Configure sgen driver for the types 01 and 08 using the following command:

add_drv -m '*0666 bin bin' -i '"scsiclass,01" "scsiclass,08" "scsa,01.bmpt" "scsa,0.8.bmpt"' sgen

After you complete the steps to enable the sgen driver, there must be entries in /etc/scsi/changer for every library and /etc/scsi/sequential for every tape

Installing Oracle Secure Backup on Linux or UNIX 2-19

Performing an Upgrade Installation on Linux or UNIX

device. If you do not find these entries, reboot your host system using the following commands:

touch /reconfigure reboot

Utilizing sgen Attach Points

The entries that are made in the /dev/scsi/changer and /dev/scsi/sequential directories when you enable the Solaris sgen driver must

be used as Oracle Secure Backup targets for /dev/ob links. These entries vary depending on the version of Solaris.

It is recommended that you create links in /dev in the form /dev/obln and

/dev/obtn that point to the entries in /dev/scsi/changer or /dev/scsi/sequential. There must be a unique /dev/obln or /dev/obtn entry

for each device that Oracle Secure Backup utilizes. These entries in /dev will be used in the obtool mkdev command during Oracle Secure Backup device configuration.

Performing an Upgrade Installation on Linux or UNIX

In preparation for an upgrade, Oracle recommends that you do the following:

1. Copy your $OSB_HOME/admin directory to a secure but easily accessed location.

2. If you customized the obparameters file, then save a copy of it.

3. Cancel all active and pending jobs.

4. Stop all Oracle Secure Backup daemons.

5. Run the setup scripts from the new CD-ROM.

6. During the upgrade process, the installer displays the following prompt:

Oracle Secure Backup is already installed on this machine (myhostname). Would you like to re-install it preserving current configuration data[no]?

Enter yes to perform the upgrade installation, retaining your previous configuration.

Uninstalling Oracle Secure Backup on Linux or UNIX

This section explains how to uninstall Oracle Secure Backup from a Linux or UNIX host. In this procedure Oracle Secure Backup is uninstalled from the administrative server. The procedure is the same when using the administrative server to uninstall Oracle Secure Backup from other hosts.

1. Log on as root to the administrative server.

2. Use the following command to identify processes related to Oracle Secure Backup:

# /bin/ps -ef |grep ob

3. Shut down processes related to Oracle Secure Backup, such as the http processes

for the Oracle Secure Backup Web tool. The appendix "Startup and Shutdown of Oracle Secure Backup Services" in Oracle

Secure Backup Reference lists operating system-specific commands for shutting down and starting Oracle Secure Backup processes on Linux and UNIX.

2-20 Oracle Secure Backup Installation and Configuration Guide

Uninstalling Oracle Secure Backup on Linux or UNIX

Alternatively, you can terminate observiced, which stops all processes. Use the following command to end each process in the list associated with Oracle Secure Backup, where pid is the process ID of observiced:

kill pid

4. Change directory to the Oracle Secure Backup home directory. For example:

# cd /usr/local/oracle/backup

Note: If you uninstall Oracle Secure Backup from the administrative

server, then the uninstallob script removes the Oracle Secure Backup home directory at the end of the uninstall process.

5. Run the uninstallob script:

# ./install/uninstallob

The uninstallob script displays a welcome message and then asks for the name of the host from which you want to remove Oracle Secure Backup.

6. Enter the name of a host from which you want to uninstall Oracle Secure Backup.

7. The uninstallob script asks for the name of the obparameters file used for

installation. If you created an obparameters file in a location other than the default, then

enter the correct path information. Otherwise, press the Enter key to accept the default value install/obparameters.

8. The uninstallob script asks to remove the Oracle Secure Backup home

directory. Select one of the following options:

■ no

Select this option if you do not want to remove the Oracle Secure Backup home directory.

■ yes

Select this option to remove the Oracle Secure Backup home directory. All files in the home directory are deleted. The only exception is the admin directory, which you can elect to retain by answering yes at the next prompt.

This procedure assumes you are saving the Oracle Secure Backup home directory.

9. The uninstallob script asks to save the Oracle Secure Backup admin directory,

even if you have chosen not to save the entire Oracle Secure Backup home directory. Select one of these options:

■ no

Select this option to remove the admin directory.

■ yes

Select this option to save the admin directory. If you keep the admin directory, then you can reinstall the Oracle Secure Backup software later without destroying your administrative domain.

This procedure assumes you are saving the Oracle Secure Backup admin directory.

Installing Oracle Secure Backup on Linux or UNIX 2-21

Uninstalling Oracle Secure Backup on Linux or UNIX

The uninstallob script displays the choices you have made and asks to

10.

continue with the uninstallation on this host. Select one of the following options:

■ yes

If you select this option, then the uninstallob script displays progress messages as it uninstalls Oracle Secure Backup. When it is finished, it displays the following message:

Oracle Secure Backup has been successfully removed from host_name.

■ no

If you select this option, then the uninstallob script does not uninstall Oracle Secure Backup from this host.

2-22 Oracle Secure Backup Installation and Configuration Guide

Installing Oracle Secure Backup on Windows

This chapter explains how to install Oracle Secure Backup on hosts that run the Windows operating system.

This chapter contains these sections:

■ Preliminary Steps

■ Disabling Removable Storage Service on Windows Media Servers

■ Extracting Oracle Secure Backup from OTN Download on Windows

■ Running the Oracle Secure Backup Windows Installer

■ Configuring Oracle Secure Backup

■ Configuring Firewalls for Oracle Secure Backup on Windows

■ Upgrade Installation on Windows 32-Bit

■ Upgrade Installation on Windows x64

■ Uninstalling Oracle Secure Backup on Windows

Preliminary Steps

Perform these preliminary steps before you begin installation of Oracle Secure Backup software:

■ Decide which roles to assign the hosts in your network, as described in

"Installation and Configuration Overview" on page 1-13.

■ Ensure that each host has a network connection and runs TCP/IP.

■ If you are installing Oracle Secure Backup on a media server, then physically

attach each tape library and tape drive that you intend to make available for use by Oracle Secure Backup. Restart the media server if required.

■ Disable any system software that scans and opens arbitrary SCSI targets before

adding a tape device to an administrative domain. If Oracle Secure Backup has to contend with other system software (such as monitoring software) for access to tape libraries and drives, then unexpected behavior can result.

■ Log on to your host as either the Administrator user or as a user that is a member

of the Administrators group.

■ For hosts to be used in the media server role, follow the steps in "Disabling

Removable Storage Service on Windows Media Servers" on page 3-2 to prevent

conflicts between Oracle Secure Backup and other software on your system.

Installing Oracle Secure Backup on Windows 3-1

Disabling Removable Storage Service on Windows Media Servers

Note: If you are installing Oracle Secure Backup in an Oracle Real

Application Clusters (Oracle RAC) environment, then you must install Oracle Secure Backup on each node in the cluster.

Disabling Removable Storage Service on Windows Media Servers

The Removable Storage service is used to manage removable media, drives, and libraries. On Windows hosts configured for the media server role, this service must be disabled for the Oracle Secure Backup device driver to correctly control a tape device.

To disa ble t he Rem ovable Storage service:

1. From the Windows Control Panel, double-click Administrative Tools.

2. Double-click Services to view the list of services on your host.

3. Right-click the Removable Storage service and choose Properties.

4. In the Properties window, if the service is running, then click Stop to stop the

service. Set the Startup Type field to Disabled.

5. Click OK.

Extracting Oracle Secure Backup from OTN Download on Windows

If you do not have the Oracle Secure Backup distribution CD-ROM, then you must download the installation package as a Zip file from Oracle Technology Network (OTN) and extract it into a directory on your local hard drive.

To download and extract the Oracle Secure Backup installation Zip file on Windows:

1. Log on to your host as a user with Administrator privileges.

2. In Windows Explorer, create a temporary folder called osbdownload on a file

system with enough free space to hold the downloaded installation file.

3. Open a Web browser and go to the Oracle Secure Backup Web site on Oracle

Technology Network (OTN):

http://www.oracle.com/technology/products/secure-backup

4. Click Free Download.

The Oracle Technology Network Developer License Terms page appears.

5. Read Export Controls on the Programs and select the Yes, I accept... option.

Read the Oracle Technology Network Development License Agreement and click I Accept.

The Oracle Secure Backup Downloads page appears.

6. Select the Accept License Agreement option, and click the link for the version of

Oracle Secure Backup release 10.3 specific to your operating system.

Note: If you have multiple operating systems in your environment,

then you must perform multiple downloads of the Oracle Secure Backup release 10.3 software.

3-2 Oracle Secure Backup Installation and Configuration Guide

Running the Oracle Secure Backup Windows Installer

The Oracle Secure Backup release 10.3 installation software is compressed. Save it

to a temporary directory, and expand it to the osbdownload directory you created in step 2.

You now have all of the files required to install Oracle Secure Backup release 10.3.

Running the Oracle Secure Backup Windows Installer

Complete the following steps to install Oracle Secure Backup on a Windows host:

Note: If you are installing Oracle Secure Backup in an Oracle RAC

environment, then you must install Oracle Secure Backup on each node in the cluster.

1. Select one of these install options:

■ If you are installing Oracle Secure Backup from a CD-ROM, then insert the

CD-ROM. If AutoPlay is enabled, then the setup.exe program starts automatically and opens the Oracle Secure Backup Setup Wizard.

If Windows AutoPlay is not enabled, then open the drive containing the installation CD-ROM using Windows Explorer and run the setup.exe program.

■ If you are installing Oracle Secure Backup from an Oracle Technology

Network (OTN) download, then run the setup.exe program from the folder into which the download Zip file contents were extracted.

The Oracle Secure Backup Setup Wizard starts and the Welcome screen appears.

2. Click Next to continue.

Installing Oracle Secure Backup on Windows 3-3

Running the Oracle Secure Backup Windows Installer

If you have uninstalled Oracle Secure Backup software before beginning this installation, or if you have never installed it on this computer, then the Clean Install page appears.

3. Click Next to continue.

The Customer Information screen appears.

3-4 Oracle Secure Backup Installation and Configuration Guide

Running the Oracle Secure Backup Windows Installer

Enter your customer information as follows:

a. Enter a user name in the User Name field. b. Enter the name of your company in the Organization field. c. Select one of these options:

– Anyone who uses this computer

This option allows anyone who has access to this computer to use Oracle Secure Backup.

– Only for me

This option limits use of Oracle Secure Backup to you. Click Next to continue. The Oracle Secure Backup Setup screen appears.

Installing Oracle Secure Backup on Windows 3-5

Running the Oracle Secure Backup Windows Installer

A single host can have multiple roles, which are are additive rather than exclusive. You have the following options when choosing roles:

■ To install the Windows host as client only, click Next and go to step 9.

Note: Every installation of Oracle Secure Backup on Windows

includes a client installation.

■ If you want this Windows host to serve as a media server, then select the

Configure locally attached media devices option, click Next, and go to step 9. Oracle Secure Backup always installs the software required for the media

server role. But if you want this Windows host to have the media server role in your Oracle Secure Backup administrative domain, then you must complete the Oracle Secure Backup software installation, configure any tape devices attached to this host, and then add the media server role.

If you select the Configure locally attached media devices option, then the Oracle Secure Backup Configuration utility enables you to configure the tape devices attached to this computer. If you do not select this option, then the Oracle Secure Backup Configuration utility ignores any attached tape devices.

3-6 Oracle Secure Backup Installation and Configuration Guide

Running the Oracle Secure Backup Windows Installer

See Also:

■ "Configuring Oracle Secure Backup" on page 3-14

■ Chapter 5, "Configuring and Managing the Administrative

Domain"

■ To install the Windows host as an administrative server, click the

Administrative Server list and select This feature will be installed on local hard drive.

Selecting this option removes the X from the administrative server icon and includes the administrative server role in the installation.

Installing Oracle Secure Backup on Windows 3-7

Running the Oracle Secure Backup Windows Installer

6. If you plan to perform Oracle Database backup and restore operations with

RMAN, then enable the action for Create "oracle" user in the administrative server submenu.

3-8 Oracle Secure Backup Installation and Configuration Guide

Running the Oracle Secure Backup Windows Installer

If this option is enabled, then the installer creates an Oracle Secure Backup user called oracle (with the rights of the oracle class) whose purpose is to facilitate Oracle Database backup and restore operations with Recovery Manager (RMAN).

Installing Oracle Secure Backup on Windows 3-9

Running the Oracle Secure Backup Windows Installer

Note:

■ You are required to create the oracle user only if you plan to use

Oracle Secure Backup with RMAN.

■ If you intend to use Oracle Secure Backup to perform one-time,

RMAN-initiated, or unprivileged backup operations on Windows clients, then you must modify the

Oracle Secure Backup admin

and oracle users to assign them Windows credentials (a domain, user name and password) that are valid at the client with required privileges after you complete the Oracle Secure Backup installation. Otherwise, Oracle Secure Backup cannot perform the backup operation. This requirement applies regardless of the platform that acts as the administrative server.

■ The installer assigns a random password to the oracle user. In

most cases you are not required to change the assigned password, because it is not usually necessary to log in to Oracle Secure Backup using this user account.

■ Before electing to create an Oracle Secure Backup oracle user, be

aware that this choice involves a trade-off between convenience and security.

See Also: Oracle Secure Backup Reference for more information about

the oracle class

3-10 Oracle Secure Backup Installation and Configuration Guide

Running the Oracle Secure Backup Windows Installer

If you do not plan to use Oracle Secure Backup to back up your databases, then leave the Create "oracle" user option unselected. This is the default.

In addition to the options described in step 6, you can perform the following actions in the Oracle Secure Backup Setup screen:

■ Click Help for detailed descriptions of the installation options.

■ Click Change to change the destination folder for the installation.

■ Click Space to display the disk space required for the installation.

Click Next to continue. The Oracle Secure Backup Encryption Key Store Password screen appears.

7. Enter a password for the Oracle Secure Backup encryption wallet in the Password

for encryption wallet field.

Enter the password again in the Re-type password for verification field. Click Next. The Oracle Secure Backup Admin User Password and Email screen appears.

Installing Oracle Secure Backup on Windows 3-11

Running the Oracle Secure Backup Windows Installer

Enter a password for the Oracle Secure Backup admin user in the Password for 'admin' user field.

Enter the password again in the Re-type password for verification field. The minimum password length is determined by the minuserpasswordlen

security policy. Its value at installation time is 0, which means a null password is permitted. After the installation has completed, you can change this policy to enforce a different minimum password length.

See Also: Oracle Secure Backup Reference for more information on the

minuserpasswordlen security policy

Note: Oracle suggests that you choose an administrative user

password of at least eight characters in length, containing a mixture of alphabetic and numeric characters. The maximum length is 16 characters.

The practice of supplying a password in clear text on a command line or in a command script is not recommended by Oracle. It is a security vulnerability. The recommended procedure is to have the user be prompted for the password.

Enter an e-mail address in the Email address for 'admin' user: field. Entering an email address for the admin user enables Oracle Secure Backup to

send notifications of important events. Setting this field is optional.

3-12 Oracle Secure Backup Installation and Configuration Guide

Running the Oracle Secure Backup Windows Installer

Note: The default from address for e-mails generated by Oracle

Secure Backup is SYSTEM@fqdn, where fqdn is the fully qualified domain name of the Oracle Secure Backup administrative server. You can change this default from address after installation. See Oracle Secure Backup Reference for more information.

Click Next. The Ready to Install the Program screen appears.

9. Click Install to start copying files.

A progress bar appears. When the files are copied the InstallShield Completed screen appears.

Installing Oracle Secure Backup on Windows 3-13

Configuring Oracle Secure Backup

10.

Click Finish. The Oracle Secure Backup software installation on this Windows host is complete.

You can now configure this installation, using the Oracle Secure Backup Configuration utility that starts automatically. Instructions on using this utility appear in "Configuring Oracle Secure Backup" on page 3-14.

Configuring Oracle Secure Backup

This section explains how to configure Oracle Secure Backup using the Oracle Secure Backup Configuration utility. This utility starts automatically when you click Finish on the final Installshield Wizard screen during the installation of Oracle Secure Backup.

If you complete this initial configuration and subsequently want to view or change your configuration settings, then you can revisit the Oracle Secure Backup Configuration utility in either of two ways:

■ Select Start > All Programs > Oracle Secure Backup > Oracle Secure Backup

Configuration

■ Enter obcfg at the command line

Complete the following steps to configure Oracle Secure Backup on a Windows host:

1. Start the Oracle Secure Backup Configuration utility.

Note: This step is unnecessary if you are configuring Oracle Secure

Backup on a Windows host for the first time, because the Oracle Secure Backup Configuration utility starts automatically after the Oracle Secure Backup software installation process.

The Oracle Secure Backup Configuration welcome screen appears.

3-14 Oracle Secure Backup Installation and Configuration Guide

Configuring Oracle Secure Backup

2. Click Next.

The Oracle Secure Backup Service Startup screen appears.

3. Select one of these modes in which to start the Oracle Secure Backup service:

■ Automatic

The Oracle Secure Backup service starts automatically when you restart your host.

Installing Oracle Secure Backup on Windows 3-15

Configuring Oracle Secure Backup

■ Manual

The Oracle Secure Backup service must be started manually by a user who is a member of the Administrators group.

■ Disabled

The Oracle Secure Backup service is disabled. Click Next. The Oracle Secure Backup Service Logon screen appears.

4. By default, the Oracle Secure Backup service logs on as the Local System account,

which is an administrative account. You can select option This Account to specify a different account for the Oracle Secure Backup Service.

Select one of these options:

■ System Account

Select this option if you plan to run the Oracle Secure Backup service daemon

(and associated subordinate daemons) with full privileges.

■ This Account

Select this option if you plan to run the Oracle Secure Backup service daemon

(and associated subordinate daemons) with the privilege set associated with

an existing Windows user account. You must fill in the Windows user account

name and password.

If you choose this option, then you must ensure that the Windows user

account you select meets the following criteria:

– The account you choose must belong to the Backup Operators group.

– No change in password at login is required of the account.

– The account must be set so that the password never expires.

3-16 Oracle Secure Backup Installation and Configuration Guide

Configuring Oracle Secure Backup

– The account must have backup and restore rights. – The account must be able to restore files and directories. – The account must be able to log on as a service. – The account must be able to act as part of the operating system. – The account must be able to increase quotas. – The account must be able to replace a process level token.

Click Next or Finish to proceed. If you are configuring a media server, then proceed to step 5.

5. Select the tape library and tape drive to assign to the Oracle Secure Backup device

drivers. After a short delay, the devices are redisplayed with check marks in the first column and an Oracle Secure Backup device name for each of them in the last column. Make a note of the device name assigned to each device. You must have these device names when you set up the devices in Oracle Secure Backup later on.

Installing Oracle Secure Backup on Windows 3-17

Configuring Firewalls for Oracle Secure Backup on Windows

6. Click Finish.

When you have performed all of the preceding tasks, Oracle Secure Backup installation and configuration on this host is complete. Repeat this installation and configuration process for each Windows host in your administrative domain.

Configuring Firewalls for Oracle Secure Backup on Windows

Windows XP Service Pack 2 and Windows Server 2003 contain a built-in Windows Firewall which, in the default configuration, blocks inbound traffic on ports used by Oracle Secure Backup.

If your Windows host is protected by a firewall, then the firewall must be configured to permit Oracle Secure Backup daemons on the host to communicate with the other hosts in your administrative domain. Oracle Secure Backup includes daemon components that listen on port 400, port 10000, and other dynamically assigned ports.

Because the dynamically assigned ports used by Oracle Secure Backup span a broad range of port numbers, your firewall must be configured to allow executables for the Oracle Secure Backup daemons to listen on all ports.

The Oracle Secure Backup Windows installation provides a sample batch script called obfirewallconfig.bat in the bin directory under the Oracle Secure Backup home.

This script contains commands that make the required configuration changes for the Windows Firewall on Windows Server 2003 and Windows XP systems having a single network interface. Review the script to determine whether it is suitable for your environment. You can run the script after the installation completes.

For details on configuration of other firewalls, see the documentation provided by the vendor. You can refer to the sample script for the Windows Firewall to determine the names of executables that need permission to listen on ports.

3-18 Oracle Secure Backup Installation and Configuration Guide

Upgrade Installation on Windows 32-Bit

You can upgrade your Windows 32-bit administrative server, media servers, and clients from Oracle Secure Backup release 10.2 to Oracle Secure Backup release 10.3 simply by running the Oracle Secure Backup release 10.3 installer. This is called an upgrade installation. The installer detects the existing installation of Oracle Secure Backup and runs the uninstaller for the previous version automatically before beginning the installation of Oracle Secure Backup release 10.3.

When you upgrade your administrative server from Oracle Secure Backup release 10.2 to Oracle Secure Backup release 10.3, the uninstaller displays the following prompt:

This system was configured as an Oracle Secure Backup Administrative Server.

Oracle Secure Backup creates files specific to this administrative domain in the "admin" directory. Would you like to keep these files in case you reinstall Oracle Secure Backup?

If you choose "Delete" all files related to Oracle Secure Backup will be removed from this system. If you choose "Keep" the files specific to this administrative domain will be retained.

You must choose the Keep option for the admin directory files. Selecting the Delete option causes the installation to be incomplete, and then you must uninstall and reinstall Oracle Secure Backup to complete the installation. If you do not want to save the existing admin directory files, then you must exit the installation, uninstall Oracle Secure Backup release 10.2, and select the Delete option. After you have uninstalled Oracle Secure Backup release 10.2, you can install Oracle Secure Backup release 10.3 by running the Oracle Secure Backup release 10.3 installer.

Upgrade Installation on Windows 32-Bit

You can upgrade your Windows 32-bit administrative server and clients from Oracle Secure Backup release 10.1 to Oracle Secure Backup 10.3 with an upgrade installation, so long as the administrative server is not also a media server.

When you upgrade your administrative server from Oracle Secure Backup release 10.1 to Oracle Secure Backup release 10.3, you should select the Keep option to keep the existing configuration of your administrative domain. If you select the Delete option, then the Oracle Secure Backup release 10.3 installation succeeds, but you must to reenter all of your Oracle Secure Backup configuration settings.

An upgrade installation does not successfully upgrade a media server or an administrative server that is also a media server from Oracle Secure Backup release

10.1 to Oracle Secure Backup release 10.3. In this special case, you can use the following procedure:

1. Uninstall the existing Oracle Secure Backup software.

See Also: "Uninstalling Oracle Secure Backup on Windows" on

page 3-20

2. Select the Keep option if you are upgrading an administrative server that is also a

media server.

3. Restart the host.

4. Run the Oracle Secure Backup release 10.3 installer.

Installing Oracle Secure Backup on Windows 3-19

Upgrade Installation on Windows x64

Different upgrade installation procedures must be used for Windows x64 than those described in "Upgrade Installation on Windows 32-Bit" on page 3-19. You can use the following procedure to upgrade a Windows x64 administrative server or client, so long as the administrative server is not also a media server:

1. Uninstall the existing Oracle Secure Backup software, selecting the Keep option if

you are upgrading an administrative server.

See Also:

■ "Uninstalling Oracle Secure Backup on Windows" on page 3-20

■ "Upgrade Installation on Windows 32-Bit" on page 3-19 for more

information on the Keep option

2. Run the Oracle Secure Backup release 10.3 installer.

You can use the following procedure to upgrade a Windows x64 media server or administrative server that is also a media server:

1. Uninstall the existing Oracle Secure Backup software, selecting the Keep option if

you are upgrading an administrative server that is also a media server.

2. Restart the host.

3. Run the Oracle Secure Backup release 10.3 installer.

Uninstalling Oracle Secure Backup on Windows

Complete the following steps to uninstall Oracle Secure Backup on Windows:

1. Select Start > All Programs > Oracle Secure Backup > Uninstall Oracle Secure

Backup.

A confirmation dialog appears.

2. Click Yes to remove Oracle Secure Backup from your computer.

3. If you configured your host as an administrative server, then an additional

window opens asking whether you want to preserve the files specific to your administrative domain. Select one of these options:

■ Click Delete if you do not want to retain the administrative domain files.

■ Click Keep to retain the administrative domain files.

If you click Keep to retain the administrative domain files, then the

configuration of your administrative domain is preserved. This is useful for

reinstallation of the Oracle Secure Backup software later.

Oracle Secure Backup is now uninstalled from your host.

3-20 Oracle Secure Backup Installation and Configuration Guide

Oracle Secure Backup User Interfaces

This chapter introduces the interfaces that you can use with Oracle Secure Backup. The major interfaces to Oracle Secure Backup are:

■ Oracle Enterprise Manager

This is the primary graphical user interface for managing Oracle Secure Backup.

■ Oracle Secure Backup Web t o ol

This interface is used to manage file-system level backups and to perform certain other tasks not possible in Oracle Enterprise Manager.

■ obtool

This command line client exposes the full functionality of Oracle Secure Backup and is invoked by the Oracle Secure Backup Web Tool and Oracle Enterprise Manager.

Note:

■ Database backups are performed using Recovery Manager

(RMAN). Because backup and recovery activities are discussed in

Oracle Secure Backup Administrator's Guide and Oracle Database Backup and Recovery Advanced User's Guide, RMAN is not

discussed in this chapter.

■ All backup and restore operations in Oracle Secure Backup

ultimately call upon a command line tool called obtar. It is generally not necessary to call obtar directly. See Oracle Secure Backup Reference for more details about obtar.

This chapter contains these sections:

■ Using Oracle Secure Backup in Enterprise Manager

■ Using the Oracle Secure Backup Web Tool

■ Using obtool

Using Oracle Secure Backup in Enterprise Manager

You can use Oracle Enterprise Manager 10g (10.2) or Oracle Enterprise Manager 11g to perform most Oracle Secure Backup tasks, including administrative domain and hardware configuration, managing your media, and backing up and restoring databases. Oracle Enterprise Manager is the preferred Web interface for Oracle Secure Backup tasks.

Oracle Secure Backup User Interfaces 4-1

Using Oracle Secure Backup in Enterprise Manager

However, you cannot use Oracle Enterprise Manager to perform file-system backup and restore operations. The Maintenance page in Oracle Enterprise Manager includes a link to the Oracle Secure Backup Web tool for such tasks.

This document describes the use of Oracle Enterprise Manager for most tasks, and describes the Oracle Secure Backup Web Tool only when there is no equivalent functionality in Enterprise Manager.

This section contains these topics:

■ Enabling Oracle Secure Backup Links in Oracle Enterprise Manager

■ Registering an Administrative Server in Oracle Enterprise Manager

■ Accessing the Web Tool from Enterprise Manager

Enabling Oracle Secure Backup Links in Oracle Enterprise Manager

If you are using releases 10.2.0.1 or 10.2.0.2 of Oracle Enterprise Manager Grid Control or release 10.2.0.2 of Oracle Enterprise Manager Database Control, then the Maintenance page does not include the Oracle Secure Backup section by default. If the Oracle Secure Backup section does not appear in the Maintenance page, then you must configure Oracle Enterprise Manager to enable the links.

To enable the Oracle Secure Backup section in Oracle Enterprise Manager:

1. Go to the ORACLE_HOME/hostname_SID/sysman/config directory and open

the emoms.properties file in a text editor.

2. Set osb_enabled=true and save the file.

3. Stop and restart the Oracle Enterprise Manager Database Control console with the

emctl command:

emctl stop dbconsole emctl start dbconsole

4. Go to the Maintenance page and confirm that the Oracle Secure Backup section

appears, as shown inFigure 4–1.

Figure 4–1 Maintenance Page

4-2 Oracle Secure Backup Installation and Configuration Guide

Using Oracle Secure Backup in Enterprise Manager

Registering an Administrative Server in Oracle Enterprise Manager

You can make RMAN backups to the Oracle Secure Backup SBT interface three ways:

■ Oracle Enterprise Manager Database Control

■ Oracle Enterprise Manager Grid Control

■ RMAN command-line client

The Database Control console must run on the administrative server and can only back up an Oracle database on the administrative server. You can run the Grid Control console on any database host in the administrative domain and use it to back up any database. This section describes how to get started with Database Control.

To use Enterprise Manager to manage your backups, you must make Enterprise Manager aware of your administrative server, which stores the configuration data and

catalog for the Oracle Secure Backup administrative domain. To register the

administrative server in Oracle Enterprise Manager Database Control:

1. Log in to the Oracle Enterprise Manager Database Control console as a user with

database administrator rights.

2. In the Oracle Secure Backup section, click Oracle Secure Backup Device and

Media.

The Add Administrative Server page appears.

3. Log in to your Oracle Secure Backup administrative domain as follows: a. Enter the Oracle Secure Backup home directory in the Oracle Secure Backup

Home field. This directory is usually /usr/local/oracle/backup on UNIX and Linux and C:\Program Files\Oracle\Backup on Windows.

b. Enter the name of an Oracle Secure Backup administrative user in the

Username field. For example, enter admin.

c. Enter the password for the Oracle Secure Backup administrator in the

Password field.

d. Click OK.

The Host Credentials page appears.

4. Enter the username and password of the operating system user on the

administrative server. This user needs root privileges. The Oracle Secure Backup Device and Media: Administrative Server: hostname

page appears. You can use this page to load tapes.

After you have registered the administrative server, you are ready to use Oracle Enterprise Manager with Oracle Secure Backup.

See Also: Oracle Database 2 Day DBA for an introduction to using

Oracle Enterprise Manager for database backup and recovery with RMAN

Accessing the Web Tool from Enterprise Manager

The Oracle Enterprise Manager console for a database provides a link to the Oracle Secure Backup Web tool. You can use this link when you need access to Oracle Secure Backup Web tool functions, such as file-system backup information.

To access the Oracle Secure Backup Web tool through Oracle Enterprise Manager Database Control:

Oracle Secure Backup User Interfaces 4-3

Using the Oracle Secure Backup Web Tool

administrator rights.

2. Go to the Oracle Secure Backup section of the Maintenance page.

If the Oracle Secure Backup section does not appear in the Maintenance page, then see "Enabling Oracle Secure Backup Links in Oracle Enterprise Manager" on page 4-2.

3. Click File System Backup and Restore.

The Oracle Secure Backup Web tool interface opens, as described in "Starting a

Web Tool Session" on page 4-4.

Using the Oracle Secure Backup Web Tool

The Oracle Secure Backup Web tool is a browser-based interface that does not require installation of Oracle Enterprise Manager. It is also the only graphical interface to the file-system backup capabilities of Oracle Secure Backup.

Note: You can access all functionality of Oracle Secure Backup

through the Oracle Secure Backup Web Tool, including file-system level backups. However, Oracle Enterprise Manager is the preferred interface for most functionality, and provides the only graphical interface for Oracle Database backups to tape.

You can access the can connect to the administrative server through SSL. The Apache Web server supplied with Oracle Secure Backup must be running to respond to these requests. Supported browsers are listed on Certify on My Oracle Support, at the following URL:

http://support.oracle.com/

Note: The PHP software installed with Oracle Secure Backup is not

supported for direct use by customers. It is only supported for use in implementing the Oracle Secure Backup Web tool.

This section contains these topics:

■ Starting a Web Tool Session

■ Web Tool Home Page

■ Web Tool Configure Page

■ Web Tool Manage Page

■ Web Tool Backup Page

■ Web Tool Restore Page

Starting a Web Tool Session

This section explains how to use the Oracle Secure Backup Web tool to access your Oracle Secure Backup administrative domain.

Oracle Secure Backup Web tool from any supported browser that

To start an Oracle Secure Backup Web Tool session:

4-4 Oracle Secure Backup Installation and Configuration Guide

Using the Oracle Secure Backup Web Tool

Launch your Web browser and supply the URL of the host running Oracle Secure

Backup. Use the following syntax, where hostname can be a fully qualified domain name:

https://hostname

For example, you might invoke the following URL:

https://osblin1.oracle.com

2. The browser displays a warning that the certificate is not trusted. Oracle Secure

Backup installs a self-signed certificate for the Apache Web server. The Web server requires a signed certificate for data encryption purposes. The security warning appears because the browser does not recognize the signer as a registered

Certification Authority (CA). This alert does not mean that your data is not

encrypted, only that the CA is not recognized. Accept the certificate. It is not necessary to view the certificate or make any

configuration changes. The Oracle Secure Backup Login page appears.

3. Enter an Oracle Secure Backup user name in the User Name box and a password

in the Password box. If you are logging into the Oracle Secure Backup Web tool for the first time, then

4. Click Login. The Oracle Secure Backup Home page appears.

The Home, Configure, Manage, Backup, and Restore tabs are explained in detail in the following sections.

Web Tool Home Page

After you log in to the Oracle Secure Backup Web t oo l interface, the Oracle Secure Backup Home page appears. This page provides a summary of the current status of each Oracle Secure Backup job and tape device. Figure 4–2 shows an example of the Home page.

Note: Oracle recommends that you not use browser-based password

managers to store Oracle Secure Backup passwords.

Oracle Secure Backup User Interfaces 4-5

Using the Oracle Secure Backup Web Tool

Figure 4–2 Oracle Secure Backup Home Page

The main page includes the schedule times, status, job IDs, job type, and job level of recent jobs. Oracle Secure Backup provides a link for failed jobs, alerting users and administrators to potential trouble spots.

The Devices link lists the tape devices associated with each job along with information concerning tape device type, device name, and status. This page provides you with an overall picture of the various backup or restore processes that are going on.

Note: A status of "device not in use" means that the tape device is

present but is not currently being utilized for backup or restore operations.

A menu bar at the top of the Oracle Secure Backup Home page enables you to select among the Configure, Manage, Backup, and Restore tabs.

Note: When using the Oracle Secure Backup Web tool, ensure that

your browser is configured to reload the page every time it is viewed. Otherwise, the browser might display stale information. For example, changes made in obtool might not be visible in the browser.

Persistent Page Links

The top and bottom panels of the Home page, and every page of the Oracle Secure Backup Web tool interface, have the following persistent links:

■ Help

Use this link to access online documentation for Oracle Secure Backup in PDF format.

■ Logout

4-6 Oracle Secure Backup Installation and Configuration Guide

Using the Oracle Secure Backup Web Tool

Logs the current user out of the Oracle Secure Backup Web tool, clears user name and password cookies, and returns to the Login page.

■ Preferences

Use this link to access settings for the following options: – Extended command output

This option displays obtool commands used to perform actions and generate output pages for the Oracle Secure Backup Web Tool at the bottom of each page.

– Background timeout

This option sets the maximum idle time for obtool background processes used by the Oracle Secure Backup Web tool to retain state information across requests.

Operations such as catalog browsing, data restore operations, and on-demand

backup operations use a background obtool process to retain state

information across HTTP requests. When the time between requests exceeds this limit, the process exits gracefully and the associated user's session state is lost. The default is 24 hours.

– Select table size

This option sets the number of rows in the display window of the Oracle Secure Backup Web tool interface. The default is 8 rows.

■ About

This link displays information about the Oracle Secure Backup software, including release date, system information, administrative server name, and IP address.

Web Tool Configure Page

Click the Configure tab from the menu bar to display configuration options.

Figure 4–3 shows an example of the Configure page.

Figure 4–3 Oracle Secure Backup Configure Page

The Configure page is divided into basic and advanced sections. The basic section contains the following links:

■ Users

Click this link to configure one or more user accounts for logging into and employing Oracle Secure Backup.

Oracle Secure Backup User Interfaces 4-7

Using the Oracle Secure Backup Web Tool

■ Hosts

Click this link to configure one or more hosts. A host is a computer that participates in the Oracle Secure Backup administrative domain.

■ Devices

Click this link to configure a tape device for use with Oracle Secure Backup. A tape device is a tape drive or tape library identified by a user-defined name.

■ Media Families

Click this link to configure media families. A media family is a named classification of backup volumes. A volume is a unit of media, such as an 8mm tape.

■ Database Backup Storage Selectors

Click this link to configure one or more tape devices and media families for use during Oracle database backup and restore operations.

The advanced section contains the following links:

■ Classes

Click this link to configure classes. A class defines a set of rights that are granted to a user. A class can apply to multiple users; however, each user is assigned to exactly one class.

■ Job Summaries

Click this link to create a job summary schedule for generation of job summaries for email distribution.

A job summary is a generated text file report that tells you whether a backup operation was successful. Oracle Secure Backup can generate and email job summaries detailing the status of each scheduled backup.

■ Defaults and Policies

Click this link to edit defaults and policies. Defaults and policies are sets of configuration data that control how Oracle Secure Backup runs throughout an administrative domain.

Web Tool Manage Page

Click the Manage tab to display management options. Figure 4–4 shows an example of the Manage page.

4-8 Oracle Secure Backup Installation and Configuration Guide

Using the Oracle Secure Backup Web Tool

Figure 4–4 Oracle Secure Backup Manage Page

The Manage page is divided into two main sections. One is for Maintenance, and the other is for Devices and Media. The Devices and Media section includes the following links:

■ Drives

Click this link to determine the status of a volume or tape device or to mount or unmount a volume.

■ Libraries

Click this link to view and control libraries.

■ Device Reservations

Click this link to reserve and unreserve tape devices for private use.

The Maintenance section includes the following links:

■ Jobs

Click this link to manage jobs in an administrative domain. You can view the status of backup and restore jobs.

■ Vo l um e s

Click this link to filter and then view all volumes in the catalog. You can filter the results to scale down your search. A volume is a unit of media, such as 8mm tape. A volume can contain multiple backup images.

■ Backup Images

Click this link to manage backup images. A backup image is the work product of a single backup operation.

■ Backup Sections

Click this link to view and remove backup sections. A backup section is that part of a backup image that occupies one physical volume.

■ Checkpoints

Click this link to list and delete checkpoints describing certain in-progress, failed, and completed Network Data Management Protocol (NDMP) backups.

■ Daemons

Oracle Secure Backup User Interfaces 4-9

Using the Oracle Secure Backup Web Tool

Click this link to manage daemons and control and view daemon properties.

Web Tool Backup Page

Click the Backup tab to display backup image options. Figure 4–5 shows a sample page.

Figure 4–5 Oracle Secure Backup Backup Page

The Backup page is divided into Operations and Settings sections. The Operations section contains the following link:

■ Backup Now

Click this link to perform one-time backups of data described by an existing

dataset file.

The Settings section contains the following links:

■ Datasets

Click this link to configure dataset files. A dataset file describes the data to back up.

■ Schedules

Click this link to configure a backup schedule. The backup schedule describes the frequency with which a backup runs.

■ Backup Windows

Click this link to configure backup windows. A backup window is a time range for the execution of scheduled backup operations.

Web Tool Restore Page

Click the Restore tab to display restore options. Figure 4–6 shows a sample page.

Figure 4–6 Oracle Secure Backup Restore Page

The Restore page has a single Operations section with the following links:

■ Backup Catalog

Click this link to browse data associated with backup and restore operations.

■ Directly from Media

Click this link to perform raw restores, which require prior knowledge of the names of the file-system objects you want to restore. You must also know the volume IDs and the file numbers on which the volumes are stored.

4-10 Oracle Secure Backup Installation and Configuration Guide

Using obtool

obtool is the primary command-line interface to Oracle Secure Backup. The obtool

executable is located in the bin subdirectory of the Oracle Secure Backup home. You can start obtool on any host in the administrative domain, log in to the domain as an

Oracle Secure Backup user, and issue commands.

Note: All examples in this section assume that the bin subdirectory

of the Oracle Secure Backup home is in your PATH.

This section contains these topics:

■ Displaying Help for Invoking obtool

■ Starting obtool in Interactive Mode

■ Running obtool Commands in Interactive Mode

■ Executing obtool Commands in Noninteractive Mode

■ Ending an obtool Session

■ Starting obtool as a Specific User

See also: Oracle Secure Backup Reference for a more detailed

discussion of invoking obtool and for more information on obtar, which is mostly used internally by obtool

Displaying Help for Invoking obtool

Assuming that the bin subdirectory of the Oracle Secure Backup home is in your system path, you can obtain online help about obtool invocation options by running the following command at the operating system prompt:

% obtool help invocation

Starting obtool in Interactive Mode

Enter obtool at the command line to use obtool in interactive mode. The first time you invoke obtool, you are required to establish your identity as an

Oracle Secure Backup user. If you have not yet established a user identity, then

obtool prompts you for a user name and password.

Note: The installer for Oracle Secure Backup creates the admin user

automatically, and prompts for a password. Use these credentials when you log in to Oracle Secure Backup for the first time after installation.

Oracle Secure Backup User Interfaces 4-11

Using obtool

Running obtool Commands in Interactive Mode

You can enter the commands described in Oracle Secure Backup Reference at the obtool prompt. For example, the lshost command displays information about the hosts in your administrative domain:

ob> lshost brhost2 client (via OB) in service brhost3 mediaserver,client (via OB) in service br_filer client (via NDMP) in service stadv07 admin,mediaserver,client (via OB) in service

Redirecting obtool Input from Text Files

You can use the < command in interactive mode to read text files containing multiple

obtool commands. For example, you can create a file called my_script.txt with

multiple obtool commands and redirect the obtool input to this script as follows:

ob> < /my_dir/my_script.txt

obtool runs the commands from the file and then returns to the ob> prompt for your

next command.

Executing obtool Commands in Noninteractive Mode

You can run obtool in noninteractive mode from the Linux or UNIX shell or from the Windows command prompt with arguments that specify the command to run.

obtool runs the specified command immediately and exits. Use the following syntax:

obtool [ cl-option ]... command-name [ option ]... [ argument ]...

The following example runs the lshost command and then returns to the operating system prompt:

% obtool lshost Output of command: lshost brhost2 client (via OB) in service brhost3 mediaserver,client (via OB) in service br_filer client (via NDMP) in service stadv07 admin,mediaserver,client (via OB) in service %

Running Multiple Commands in Noninteractive Mode

You can run multiple commands in one invocation of obtool by separating the commands with a semicolon on the command line.

Note: Follow the quoting conventions of your host operating system

shell or command line interpreter when entering a semicolon in the command line. For example, in a bash shell session, quote the semicolon as follows:

$ obtool lshost ';' lsdev

Redirecting Input in Noninteractive Mode

You can use the < command in noninteractive mode to read text files containing multiple obtool commands. For example, you can create a file called my_script.txt

4-12 Oracle Secure Backup Installation and Configuration Guide

with multiple obtool commands and redirect the obtool input to this script as follows:

% obtool < /my_dir/my_script.txt

obtool runs the commands from the file and then returns to the operating system

prompt for your next command.

Ending an obtool Session

You can end an obtool session by using one of these commands:

■ exit

This command ends the obtool session, but a login token preserves your credentials, so that the next time you start obtool you are not prompted for a user name or password.

■ quit

This command is a synonym for exit.

■ logout

This command ends the obtool session and destroys the login token, so that you are prompted for credentials at the start of your next obtool session.

Using obtool

In the following example, login credentials are required for the first session, because the login token has expired. This first session is ended with an exit command, and a second session is started. No login credentials are required for this second session, because the login token was preserved. The second session is ended with a logout command, and a third session is started. The third session requires login credentials because the login token was destroyed by the logout command.

[cfoch@stbcs06-1 ~]$ obtool Oracle Secure Backup 10.3.0.0 Warning: auto-login failed - login token has expired login: admin ob> exit [cfoch@stbcs06-1 ~]$ obtool ob> logout [cfoch@stbcs06-1 ~]$ obtool Oracle Secure Backup 10.3.0.0 login: admin ob>

Starting obtool as a Specific User

You can force obtool to use different credentials when starting, destroying any existing login token. To do so, use the -u option with obtool, specifying the name of the user for the session. For example:

[root@osblin1 ~]# obtool -u admin Password: ob>

Note: The practice of supplying a password in clear text on a

command line or in a command script is not recommended by Oracle. It is a security vulnerability. The recommended procedure is to have the user be prompted for the password.

Oracle Secure Backup User Interfaces 4-13

Using obtool

4-14 Oracle Secure Backup Installation and Configuration Guide

Configuring and Managing the

Administrative Domain

This chapter explains the basic steps involved in setting up an Oracle Secure Backup

administrative domain after initial installation of the product on all of your hosts.

Some steps, such as "Adding a Host to the Administrative Domain" on page 5-3, are also useful when managing an existing administrative domain.

This chapter contains the following sections:

■ Administrative Domain Configuration Overview

■ Configuring the Administrative Domain with Hosts

■ Adding Tape Devices to an Administrative Domain

Administrative Domain Configuration Overview

This section describes the steps involved in configuring an Oracle Secure Backup administrative domain. It assumes you have installed the Oracle Secure Backup software on each host in the domain, as described in Chapter 2, "Installing Oracle

Secure Backup on Linux or UNIX" or Chapter 3, "Installing Oracle Secure Backup on Windows".

These instructions explain how to configure the administrative domain with host and

tape device information using the

the same tasks using the obtool command-line interface to The instructions set up administrative domain security in a default security

configuration that should be adequate for most users. Further configuration of users, user classes, security options, and the Oracle Secure Backup media management layer for use with Recovery Manager (RMAN) in backing up Oracle databases might be required in some cases. For details, see Oracle Secure Backup Administrator's Guide.

Oracle Secure Backup Web tool. You can perform

Administrative Domain Configuration Steps: Outline

The required steps to configure Oracle Secure Backup after installation are as follows:

1. Use your Web browser to connect to the Oracle Secure Backup Web tool running

on the administrative server as the admin user. "Using the Oracle Secure Backup

Web Tool" on page 4-4 describes this task.

2. For each host in your domain to be set up for the role of media server, perform the

following steps:

a. Add the host to the administrative domain. "Configuring the Administrative

Domain with Hosts" on page 5-2 describes this task.

Configuring and Managing the Administrative Domain 5-1

Oracle Secure Backup.

Configuring the Administrative Domain with Hosts

Note: If the administrative server is also assigned the media server

role, then it is part of the administrative domain.

Configure the administrative domain to include each tape device attached to this host. "Adding Tape Devices to an Administrative Domain" on page 5-10 describes this task.

3. For each host to be set up only for the client role, add the host to the

administrative domain, as described in "Configuring the Administrative Domain

with Hosts" on page 5-2.

After configuring each client host, ping it to ensure that it is reachable.

4. Initial configuration is complete. Oracle Secure Backup is installed on all hosts,

and all clients, media servers and tape devices are accessible by Oracle Secure Backup. Network communication among hosts in the administrative domain is configured with the default security configuration described in "Default Security

Configuration" on page 6-15.

Note: You must still identify files to be backed up, configure at least

one backup schedule, and set up users, classes, and security policies. These tasks are described in the Oracle Secure Backup Administrator's Guide.

Configuring the Administrative Domain with Hosts

This section explains how to configure your administrative domain to add your hosts. This section contains these topics:

■ About Administrative Domain Host Configuration

■ Viewing the Hosts in the Administrative Domain

■ Adding a Host to the Administrative Domain

■ Adding the Media Server Role to an Administrative Server

■ Adding Backup and Restore Environment Variables to an NDMP Host

■ Configuring Preferred Network Interfaces (PNI)

■ Pinging a Host

■ Viewing or Editing Host Properties

■ Updating a Host

■ Removing a Host

About Administrative Domain Host Configuration

The host configuration process makes the administrative server aware of a media server or client to be included in the administrative domain. You must perform this process for every host in the administrative domain, including each host running Oracle Secure Backup natively and each network-attached storage device managed by

Network Data Management Protocol (NDMP).

For any host to be added to the administrative domain, you must provide the following attributes:

5-2 Oracle Secure Backup Installation and Configuration Guide

Configuring the Administrative Domain with Hosts

■ Host name

■ IP address

■ Assigned roles: client, media server or both

■ Whether the host is in service or not in service at the moment

After adding a host to the administrative domain, Oracle recommends that you ping the host to confirm that it can be accessed by the administrative server.

Viewing the Hosts in the Administrative Domain

In the Oracle Secure Backup Web tool, on the Configure page, click Hosts to display

the Hosts page. The Hosts page lists the host name, configured host roles, and the current status of the host. Figure 5–1 shows a typical Hosts page.

Figure 5–1 Oracle Secure Backup Web Tool: Hosts Page

Note: You can also view the current list of hosts with the obtool

lshost command.

Adding a Host to the Administrative Domain

To add a host to an administrative domain:

1. From the Home page, click the Configure tab.

2. Click Hosts in the Basic section to display the Hosts page.

3. Click Add to add a host.

Configuring and Managing the Administrative Domain 5-3

Configuring the Administrative Domain with Hosts

The Oracle Secure Backup Web tool displays a form for entering configuration information about the host.

4. In the Host field, enter the unique name of the host in the Oracle Secure Backup

administrative domain. In most cases, this name is the host name resolvable to an IP address using the

host name resolution system (such as DNS or NIS) on your network. However, you can assign a different host name purely for use with Oracle Secure Backup.

The name you enter must start with an alphanumeric character. It can contain only letters, numerals, dashes, underscores, and periods. The maximum length of a host name is 127 characters.

5. You must enter a value in the IP Interface name(s) field in the following

situations:

■ The name of this host cannot be resolved to an IP address using a mechanism

such as DNS or NIS

■ The resolvable name of your host is different from the value entered in the

Host field.

■ Your host has multiple IP interface names or IP addresses to use with Oracle

Secure Backup

If any of the preceding conditions apply to this host, then enter one or more IP interface names in this field. Valid values are either resolvable host names or IP addresses. Separate multiple values with a comma.

For example, you can use myhost.oracle.com for a host name or

141.146.8.66 for an IP address. If a value is specified for this field, then Oracle Secure Backup tries the host names

or IP addresses in the order specified when it must contact this host, rather than using the name specified in the Host field.

Note: If some hosts should contact this host using a particular

network interface, then you can use the Preferred Network Interface

(PNI) capability to override this order for those hosts, after

completing the initial configuration of the administrative domain. See

"Configuring Preferred Network Interfaces (PNI)" on page 5-8 for

details.

6. In the Status list, select one of these:

■ in service

Select this option to indicate that the host is available to perform backup and restore operations.

■ not in service

Select this option to indicate that the host is unavailable to perform backup and restore operations.

7. In the Roles list, select the roles for this host: admin, client or mediaserver.

8. In the Access method field, select one of these:

■ OB

5-4 Oracle Secure Backup Installation and Configuration Guide

Configuring the Administrative Domain with Hosts

Select this option for Windows, Linux and UNIX hosts that have Oracle Secure Backup installed.

■ NDMP

Select this option for devices that support NDMP without an Oracle Secure Backup installation, such as a network-attached storage device.

Note: OB access mode is a synonym for primary access mode. See

"Oracle Secure Backup Host Access Modes" on page 1-3 for a

discussion of access modes.

9. In Public and private key sizes, select the size for the public/private key

associated with the identity certificate for this host. For hosts using the ob access mode, skip to Step 16. For hosts such as Network

Attached Storage (NAS) devices that must use NDMP mode, continue to Step 10.

Steps 10 through 15 apply only to hosts in NDMP mode.

10. In the NDMP authorization type list, select an authorization type. The

authorization type defines the way Oracle Secure Backup authenticates itself to the NDMP server. Typically, you should use the default setting.

Your choices are the following:

■ default

Select this option to use the value of the Authentication type for the NDMP policy.

■ none

Select this option to attempt to use the NDMP server from Oracle Secure Backup and provide no authentication data. This technique is usually unsuccessful.

■ negotiated

Select this option to negotiate with the NDMP server to determine the best authentication mode to use.

■ text

Select this option to use unencrypted text to authenticate.

■ md5

Select this option to use the MD5 digest algorithm to authenticate.

See Also: Oracle Secure Backup Administrator's Guide to learn about

NDMP-related policies

11. In the Username field, enter the name used to authenticate Oracle Secure Backup

to this NDMP server. If left blank, then Oracle Secure Backup uses the name in the NDMP policy.

12. In the Password list, select one of these options:

■ Use default password

Select this option to use the default NDMP password.

■ Use text password

Configuring and Managing the Administrative Domain 5-5

Configuring the Administrative Domain with Hosts

Select this option to enter a password.

■ Set to NULL

Check this to use a NULL password.

The password is used to authenticate Oracle Secure Backup to this NDMP server.

Note: The practice of supplying a password in clear text on a

command line or in a command script is not recommended by Oracle. It is a security vulnerability. The recommended procedure is to have the user be prompted for the password.

13. In the Backup type field, enter an NDMP backup type. A backup type is the name

of a backup method supported by the NDMP data service running on a host. Backup types are defined by each data service provider.

14. In the Protocol Version list, select 2, 3, 4, or as proposed by server. See "Oracle

Secure Backup Host Access Modes" on page 1-3 for details on NDMP protocol

versions.

15. In the Port field, enter a port number. Typically, the TCP port (10000) in the NDMP

policy is used. You can specify another port if this server uses a port other than the default.

16. If the host you are adding to the administrative domain is not currently accessible

on the network, then select the Suppress communication with host option.

17. Click OK to save your changes.

Adding the Media Server Role to an Administrative Server

If you choose both the administrative server and media server roles when installing Oracle Secure Backup on a host, then that host is automatically part of the administrative domain. But it is not recognized as a media server until that role is explicitly granted to it using the chhost command in obtool or the Oracle Secure Backup Web tool.

See Also: Oracle Secure Backup Reference for complete syntax and

semantics for the chhost command

Follow these steps to add the media server role to an administrative server using the Oracle Secure Backup Web tool:

1. On the Configure page of the Oracle Secure Backup Web tool, click Hosts.

The Configure: Hosts page appears.

5-6 Oracle Secure Backup Installation and Configuration Guide

Select the administrative server and click Edit. The Configure: Hosts > host_name page appears.

Configuring the Administrative Domain with Hosts

3. In the Roles list, shift-click to add the media server role and then click OK.

The Configure: Hosts page reappears with the media server role added to the administrative server host.

Configuring and Managing the Administrative Domain 5-7

Configuring the Administrative Domain with Hosts

Adding Backup and Restore Environment Variables to an NDMP Host

Some NDMP hosts might require that you add backup and restore environment variables before they function with Oracle Secure Backup.

To add backup and restore variables:

1. In the field that appears next to the Backup environment vars or Restore

environment vars field, enter a name-value pair.

2. Click Add to add the name-value pair as an environment variable.

If an environment variable name or value includes spaces, then you must use quotes around the name or value to ensure correct processing of the name or value. For example, enter A=B or "Name A"="Value B" (if the name or value includes spaces).

3. Select an existing environment variable pair and click Remove to remove the pair.

Configuring Preferred Network Interfaces (PNI)

Multiple physical data paths can exist between a client, which contains primary storage to be backed up or restored, a media server, which controls at least one secondary storage device that writes and reads the backup media, and the administrative server. For example, a host might have multiple network interfaces connected to the network containing the hosts in the administrative domain. You can specify a PNI that identifies the network interface on a host to use when transmitting backup or restore data to another specified host, or receiving data from that host.

To configure a preferred network interface:

1. From the Configure page, select the host you want to configure and click Edit.

The Configure Hosts > host_name page appears.

2. Click Preferred Network Interfaces.

The Configure Hosts > host_name > Preferred Network Interface page appears.

3. Select an IP address or name from the IP Address list.

This list shows each IP address or name by which this host can be referenced. Each is associated with a specific network interface. The IP address or name identifies the network interface that clients you select can use when communicating with the server.

5-8 Oracle Secure Backup Installation and Configuration Guide

Pinging a Host

Configuring the Administrative Domain with Hosts

Select one or more clients to use this IP address or DNS name from the Host list

field.

5. Click Add.

The Oracle Secure Backup Web tool displays the PNI in the IP Address: Host List field.

To remove a PNI:

1. In the IP Address: Host List field, select the name of the PNI to remove.

2. Click Remove.

You can use the Oracle Secure Backup ping operation to determine whether a host responds to requests from Oracle Secure Backup on each of its configured IP addresses.

Pinging a host attempts to establish a TCP connection to the host on each of the IP addresses you have configured for it. For hosts running Oracle Secure Backup, the connection occurs on TCP port 400. For hosts that use the NDMP access mode, connections occur through the configured NDMP TCP port, usually 10000.

Oracle Secure Backup reports the status of each connection attempt and immediately closes each connection that has been established successfully.

To ping a host:

1. From the Hosts page, select a host to ping.

2. Click Ping.

A status line appears on the page with the results of the operation.

Viewing or Editing Host Properties

If you are having difficulties in configuration, then you might be required to view or edit the configuration of a host. To display or edit host properties:

1. From the Hosts page, select the name of the host whose properties require editing.

Select the Suppress communication with host option to edit a host that is currently not accessible through the network.

2. Click Edit.

The Oracle Secure Backup Web tool displays a page with details for the host you selected.

3. Make any desired changes to the host properties.

4. Click OK to save your changes.

Updating a Host

When you add or modify a host in an Oracle Secure Backup administrative domain, Oracle Secure Backup exchanges messages with that host to inform it of its changed state. If you select the Suppress communication with host option during an add or edit operation, however, then the host contains out-of-date configuration information. Use Update Host to send fresh state information to the host.

Configuring and Managing the Administrative Domain 5-9

Adding Tape Devices to an Administrative Domain

Updating is useful only for hosts running Oracle Secure Backup natively. Hosts accessed in NDMP mode, such as NAS devices, do not maintain any Oracle Secure Backup state data and therefore it is not necessary to update their state information.

To update a host:

1. From the Host page, select the name of the host to be updated.

2. Click Update.

Removing a Host

This section explains how to remove a host from an Oracle Secure Backup administrative domain. When you remove a host, Oracle Secure Backup destroys all information pertinent to that host, including:

■ Configuration data

■ Incremental backup state information

■ Metadata in the backup catalog for this host

■ Each device attachment

■ PNI references

When you remove a host, Oracle Secure Backup contacts that host and directs it to delete the administrative domain membership information it maintains locally. You can suppress this communication if the host is no longer accessible.

To remove a host:

1. From the Hosts page, select the name of the host to remove.

Check Suppress communication with host to remove a host that is not connected to the network.

2. Click Remove.

Oracle Secure Backup prompts you to confirm the removal of the host.

3. Click Yes to remove the host or No to leave the host undisturbed.

Oracle Secure Backup removes the host and returns you to the Host page.

Adding Tape Devices to an Administrative Domain

This section explains how to configure a tape drive or tape library for use with Oracle Secure Backup. This section contains these topics:

■ Tape De vice N ames

■ About Configuring Tape Drives and Libraries

■ Displaying the Devices Page

■ Configuring a Tape Library

■ Configuring a Tape Drive

■ Discovering Tape Devices Automatically on NDMP Hosts

■ Configuring an NDMP Copy-Enabled Virtual Tape Library

■ Adding a Tape Device Attachment

■ Multiple Attachments for SAN-Attached Tape Devices

5-10 Oracle Secure Backup Installation and Configuration Guide

■ Configuring Multihosted Device Objects

Tape Device Names

A tape device can be assigned a logical name by the host operating system (such as

nrst0a), but it also can have a worldwide name, such as nr.WWN[2:000:0090a5:0003f7]L1.a. On some platforms, such as a Fibre

Channel tape drive or tape library connected to a Network Appliance filer, the logical

name might vary at each operating system restart. Oracle Secure Backup supports such tape devices, but they must be referred to by their worldwide name, which does not change across operating system restarts.

Any substring of the raw device name for the attachment that is the string $WWN is replaced with the value of the WWN each time the tape device is opened. For example a usable raw device name for a Storage Area Network (SAN) Network Appliance filer is nr.$WWN.a, specifying a no-rewind, best-compression tape device having the World Wide Name found in the device object.

The WWN is usually automatically discovered by the device discovery function in Oracle Secure Backup. However, you can enter it manually if necessary.

Adding Tape Devices to an Administrative Domain

See Also: "Configuring the Solaris sgen Driver to Provide Oracle

Secure Backup Attach Points" on page 2-18 to learn how to create

attach points for tape devices on Solaris 10 systems

About Configuring Tape Drives and Libraries

This section explains how to configure a tape drive or tape library for use with Oracle Secure Backup. You can add a tape device in one of two ways:

■ Manually

A tape device connected to a media server on which Oracle Secure Backup is installed must be added to the administrative domain manually.

■ Automatically discovery

Oracle Secure Backup can automatically discover and configure each secondary storage device connected to certain types of NDMP servers, such as a Network Appliance filer.

Note: You must add the media server role to a host before adding

any tape devices whose attachment point references that host. Oracle Secure Backup does not do this automatically.

For both tape drives and tape libraries, you can configure the following attributes:

■ The name of the tape device

■ The attachment, which is the description of a physical or logical connection of a

tape device to a host

■ Whether the tape device is in service

For tape drives, you can configure the following additional attributes:

■ The tape library in which the tape drive is housed, if the tape drive is not

standalone

Configuring and Managing the Administrative Domain 5-11

Adding Tape Devices to an Administrative Domain

■ A storage element range that the tape device can use, if the tape drive is in a tape

library

Note: Oracle Secure Backup identifies each tape drive within a tape

library by its data transfer element (DTE) number. You must assign each tape device a DTE number if it is installed within a tape library. DTEs are numbered 1 through n. See the description of the --dte option to the mkdev command in Oracle Secure Backup Reference for more details on data transfer element numbers.

For tape libraries, you can configure the following additional attributes:

■ Whether automatic cleaning is enabled

■ The duration of a cleaning interval

■ Whether a barcode reader is present

See Also: Oracle Secure Backup Reference for a complete account of

tape device attributes.

To configure your administrative domain to include tape devices:

1. Disable any system software that scans and opens arbitrary SCSI targets before

configuring Oracle Secure Backup tape devices. If Oracle Secure Backup has to contend with other system software (such as

monitoring software) for access to tape libraries and tape drives, then unexpected behavior can result.

2. Configure tape libraries locally attached to your media servers, as described in

"Configuring a Tape Library" on page 5-14.

Configure tape drives locally attached to your media servers, as described in

"Configuring a Tape Drive" on page 5-17

3. Configure tape devices that are network-accessible but are not locally attached.

You must decide which media servers should control the tape devices and, for each media server, specify an attachment between the media server and the tape device. The procedure is identical to configuring a tape device attached locally to a media server.

4. Perform automatic device discovery to add every tape device attached to hosts

that use NDMP access mode, such as NAS filers.

"Discovering Tape Devices Automatically on NDMP Hosts" on page 5-19 describes

this task.

5. Inventory each tape library, and then list its volumes.

Each volume in a tape library should show either a barcode or the status unlabeled. If a library shows a slot as occupied, then this slot is in an invalid state.

Updating a Tape Device Inventory

To update a tape library or tape drive inventory using the Oracle Secure Backup Web tool:

1. From the Oracle Secure Backup Web tool Home page, click Manage.

The Manage page appears.

5-12 Oracle Secure Backup Installation and Configuration Guide

Adding Tape Devices to an Administrative Domain

In the Devices section, click Libraries.

The Manage: Libraries page appears.

3. Select the tape drive or tape library you want to inventory in the Devices table.

4. Select Inventory (Library | Drive) in the Library commands list.

In this example, lib1 is selected.

5. Click Apply.

The Manage: Libraries page appears.

6. Ensure that the Library list is set to the device you want to inventory.

7. Select the Force option.

Instead of reading from its cache, the tape library updates the inventory by physically scanning all tape library elements.

8. Click OK.

When the inventory is complete, the Manage: Libraries page reappears and displays a success message.

To see the results of the inventory, select the tape drive or tape library again and click List Volumes.

Displaying the Devices Page

The Devices page, illustrated in Figure 5–2, lists each tape library and tape drive that is currently in the administrative domain. The page lists the type, status, and name of every tape device.

Configuring and Managing the Administrative Domain 5-13

Adding Tape Devices to an Administrative Domain

Figure 5–2 Devices Page

Configuring a Tape Library

This section explains how to configure a tape library for use with Oracle Secure Backup.

To configure a tape library:

1. Disable any system software that scans and opens arbitrary SCSI targets before

adding a tape device to an administrative domain. If Oracle Secure Backup has to contend with other system software (such as monitoring software) for access to a tape library or tape drive, then unexpected behavior can result.

2. From the Home page, click the Configure tab.

3. Click Devices in the Basic section to display the Devices page.

4. Click Add to add a tape device.

5. In the Device field, enter a name for the tape device.

The name must start with an alphanumeric character. It can only contain letters, numerals, dashes, underscores, or periods. It can contain at most 127 characters.

The tape device name is of your choosing. It must be unique among all Oracle Secure Backup device names. It is unrelated to any other name used in your computing environment or the Oracle Secure Backup administrative domain.

6. In the Typ e list, select library.

7. In the Status list, select one of these options:

■ in service

Select this option to indicate that the tape device is available to perform Oracle Secure Backup backup and restore operations.

■ not in service

Select this option to indicate that the tape device is unavailable to perform backup or restore operations.

■ auto not in service

This option indicates that the tape device is unavailable to perform backup or restore operation and is set automatically for a failed operation.

8. In the Debug mode list, select yes or no. The default is yes.

5-14 Oracle Secure Backup Installation and Configuration Guide

Adding Tape Devices to an Administrative Domain

In the World Wide Name field, enter a worldwide name for the tape device, if

required.

See Also: "Tape Device Names" on page 5-11 for more information

on World Wide Names

10. In the Barcode reader list, select one of these options to indicate whether a barcode

reader is present:

■ yes

Select this option to indicate that the tape library has a barcode reader.

■ no

Select this option to indicate that the tape library does not have a barcode reader.

■ default

Select this option to indicate that Oracle Secure Backup should automatically determine the barcode reader using information reported by either the tape library, the external device file, or both.

11. In the Barcode required list, select yes or no. If you specify yes, then Oracle Secure

Backup refuses to use any tape that lacks a readable barcode. By default, Oracle Secure Backup does not discriminate between tapes with

readable barcodes and those without. This policy ensures that Oracle Secure Backup can always solicit a tape needed for a restore operation by using either the barcode or the volume ID.

12. Set whether the tape library should use automatic cleaning.

See Also: "Configuring Automatic Tape Cleaning for a Library" on

page 5-16

13. In the Unload required list, select yes or no to specify if an unload operation is

required before moving a tape from a tape drive to a storage element. The default value is no.

14. Select an ejection type. Your choices are:

■ Automatic

Whenever a volume becomes eligible to be ejected from the tape library, Oracle Secure Backup moves that volume to an export element and notifies the backup operator that it is available there. If no export elements are available, then Oracle Secure Backup requests operator assistance.

■ On demand

Whenever a volume becomes eligible to be ejected from the tape library, Oracle Secure Backup marks the volume to that effect. A media movement job then waits for the operator to reply to the job. The operator replies to the job through the job transcript. When the operator replies to the job to continue, Oracle Secure Backup ejects all such volumes through export elements.

■ Manual

No automation is used to eject volumes from the tape library. The backup operator determines which storage elements contain volumes ready to be

Configuring and Managing the Administrative Domain 5-15

Adding Tape Devices to an Administrative Domain

ejected and manually removes them. This option can be useful when the tape library has no import/export slots.

15. Enter a value in the Minimum writable volumes field.

When Oracle Secure Backup scans tape devices for volumes to be moved, it looks at this minimum writable volume threshold. If the minimum writable volume threshold is nonzero, and if the number of writable volumes in that tape library is less than this threshold, then Oracle Secure Backup creates a media movement job for the full volumes even if their rotation policy does not require it. When this happens, Oracle Secure Backup notes in the media movement job transcript that volumes have been moved early.

16. Click OK to save your changes.

See Also: "Adding a Tape Device Attachment" on page 5-21

Configuring Automatic Tape Cleaning for a Library

Oracle Secure Backup can automatically clean each tape drive in a tape library. A cleaning cycle is initiated either when a tape drive reports that it needs cleaning or when a specified usage time has elapsed.

Oracle Secure Backup checks for cleaning requirements when a cartridge is either loaded into or unloaded from a tape drive. If at that time a cleaning is required, then Oracle Secure Backup loads a cleaning cartridge, waits for the cleaning cycle to complete, replaces the cleaning cartridge in its original storage element, and continues with the requested load or unload.

To configure automatic cleaning for a tape library:

1. In the Auto clean list, select yes to enable automatic tape drive cleaning or no to

disable it. You can also manually request that a cleaning be performed whenever a tape drive is not in use.

Note: Not all tape drives can report that cleaning is required. For

those tape drives, you must define a cleaning interval.

In the Clean interval (duration) field, enter a value and then select the cleaning frequency from the adjacent list. This interval is the amount of time a tape drive is used before a cleaning cycle is initiated. If automatic tape drive cleaning is enabled, then this duration indicates the interval between cleaning cycles.

2. In the Clean using emptiest field, select one of these options:

■ yes

Select this option to specify the emptiest cleaning tape, which causes cleaning tapes to "round robin" as cleanings are required.

■ no

Select this option use the fullest cleaning tape, which causes each cleaning tape to be used until it fills, then the next cleaning tape fills, and so on.

If there are multiple cleaning tapes in a tape library, then Oracle Secure Backup must decide which to use. If you do not otherwise specify, then Oracle Secure Backup chooses the cleaning tape with the fewest number of cleaning cycles remaining.

3. Click OK to save your changes.

5-16 Oracle Secure Backup Installation and Configuration Guide

See Also: "Adding a Tape Device Attachment" on page 5-21

Configuring a Tape Drive

This section explains how to configure a tape drive for use with Oracle Secure Backup. If the tape drive you want to configure is attached to a tape library, then you must configure the tape library first, as described in "Configuring a Tape Library" on page 5-14.

To configure tape drives for use with Oracle Secure Backup:

1. Disable any system software that scans and opens arbitrary SCSI targets before

2. From the Home page, click the Configure tab.

3. Click Devices in the Basic section to display the Devices page.

4. Click Add to add a tape device.

5. In the Device field, enter a name for the tape device.

The name must start with an alphanumeric character. It can only contain letters, numerals, dashes, underscores, or periods. It can contain at most 127 characters.

Adding Tape Devices to an Administrative Domain

6. In the Serial number field, enter the serial number of the tape drive.

This step is not required. But if you do not enter a serial number, then Oracle Secure Backup reads and stores the tape drive serial number the first time it opens the tape drive.

If the checkserialnumbers policy is enabled and you change the tape drive hardware, then you must enter the serial number of the tape drive before using it.

See Also:

■ "Editing Device Properties" on page 5-25

■ Oracle Secure Backup Reference for more information on the

checkserialnumbers policy

7. In the Typ e list, select tape.

8. In the Status list, select one of these options:

■ in service

Select this option to indicate that the tape device is available to perform Oracle Secure Backup backup and restore operations.

■ not in service

Select this option to indicate that the tape device is unavailable to perform backup or restore operations.

■ auto not in service

This option indicates that the tape device is unavailable to perform backup or restore operation and is set automatically for a failed operation.

Configuring and Managing the Administrative Domain 5-17

Adding Tape Devices to an Administrative Domain

In the Debug mode list, select yes or no. The default is yes.

10. In the World Wide Name field, enter a worldwide name for the tape device, if

required.

See Also: "Tape Device Names" on page 5-11 for more information

on World Wide Names

11. If the tape drive is located in a tape library, then select the tape library by name

from the Library list.

12. In the DTE field, enter the data transfer element (DTE).

Note: This option is not available for standalone tape drives.

13. In the Automount field, select yes (default) or no to specify whether automount

mode is on or off. Enable the automount mode if you want Oracle Secure Backup to mount tapes for backup and restore operations without operator intervention.

14. In the Error rate field, enter an error rate percentage or leave this field blank to

accept the default setting. The default is 8. The error rate is the ratio of restored write errors that occur during a backup job

divided by the total number of blocks written, multiplied by 100. If the error rate for any backup is higher than this setting, then Oracle Secure Backup displays a warning message in the backup transcript.

Oracle Secure Backup also issues a warning if it encounters a SCSI error when trying to read or reset the tape drive error counters. Some tape drives do not support the SCSI commands necessary to perform these operations. To avoid these warnings, error rate checking can be disabled by selecting None.

15. In the Blocking factor field, enter the blocking factor or leave this field blank to

accept the default setting. The default is 128 bytes. The blocking factor value specifies how many 512-byte records to include in each

block of data written to tape. The default value is 128, which means that Oracle Secure Backup writes 64K blocks to tape.

See Also: "Tape Drives" on page 1-5 for more information on

blocking factors and maximum blocking factors

16. In the Max Blocking factor field, enter the maximum blocking factor.

The largest value supported for the maximum blocking factor is 4096. This represents a maximum tape block size of 2MB.

Note: Device and operating system limitations might reduce this

maximum block size.

17. In the Drive usage field, enter the amount of time the tape drive has been in use

since it was last cleaned and then select the time unit from the adjacent list.

18. Leave the Current tape field empty during initial configuration. Update the tape

drive inventory after configuration, as described in "Updating a Tape Device

Inventory" on page 5-12.

19. In the Use list group, select one of these options to configure the use list:

5-18 Oracle Secure Backup Installation and Configuration Guide

Oracle DOCUCOLOR 242, DOCUCOLOR 252, DOCUCOLOR 260 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Audience

Documentation Accessibility

Preface

Related Documents

Conventions

Introduction to Oracle Secure Backup

What Is Oracle Secure Backup?

Oracle Secure Backup Concepts

Oracle Secure Backup Administrative Domains and Hosts

Oracle Secure Backup Administrative Domain: Examples

Tape Devices

Oracle Secure Backup Interfaces

System Requirements for Oracle Secure Backup

Disk Space Requirements for Oracle Secure Backup

Acquiring Oracle Secure Backup Installation Media

Other System Requirements for Oracle Secure Backup

Linux Media Server System Requirement: SCSI Generic Driver

Installation and Configuration Overview

About Upgrade Installations

Preparing Administrative Domain Hosts for Upgrade to Release 10.3

Overview of Oracle Secure Backup Linux and UNIX Installation

Installing Oracle Secure Backup on Linux or UNIX 2-1

Prerequisites for Installing Oracle Secure Backup on Linux and UNIX

Prerequisites for Installation on Linux

Required SCSI Tape Device Parameters on Linux and UNIX

Extracting Oracle Secure Backup from OTN Download on Linux or UNIX

Creating the Oracle Secure Backup Home

Preparing to Install Oracle Secure Backup on Linux and UNIX

Loading Oracle Secure Backup Software on Linux or UNIX Using setup Script

Configuring Installation Parameters in the obparameters File

Installing Oracle Secure Backup on Linux or UNIX with installob

Installing or Uninstalling Oracle Secure Backup on AIX

Installing or Uninstalling Oracle Secure Backup on HP-UX

Creating Attach Points with makedev

Identifying and Configuring AIX Devices

Identifying and Configuring HP-UX Devices

Identifying and Configuring Linux Attach Points

Configuring the Solaris sgen Driver to Provide Oracle Secure Backup Attach Points

Performing an Upgrade Installation on Linux or UNIX

Uninstalling Oracle Secure Backup on Linux or UNIX

Installing Oracle Secure Backup on Windows

Preliminary Steps

Disabling Removable Storage Service on Windows Media Servers

Extracting Oracle Secure Backup from OTN Download on Windows

Running the Oracle Secure Backup Windows Installer

Configuring Oracle Secure Backup

Configuring Firewalls for Oracle Secure Backup on Windows

Upgrade Installation on Windows 32-Bit

Upgrade Installation on Windows x64

Uninstalling Oracle Secure Backup on Windows

Oracle Secure Backup User Interfaces

Using Oracle Secure Backup in Enterprise Manager

Enabling Oracle Secure Backup Links in Oracle Enterprise Manager

Registering an Administrative Server in Oracle Enterprise Manager

Accessing the Web Tool from Enterprise Manager

Using the Oracle Secure Backup Web Tool

Starting a Web Tool Session

Web Tool Home Page

Web Tool Configure Page

Web Tool Manage Page

Web Tool Backup Page

Web Tool Restore Page

Using obtool

Displaying Help for Invoking obtool

Starting obtool in Interactive Mode

Running obtool Commands in Interactive Mode

Executing obtool Commands in Noninteractive Mode

Ending an obtool Session

Starting obtool as a Specific User

Administrative Domain Configuration Overview

Administrative Domain Configuration Steps: Outline

Configuring and Managing the Administrative Domain 5-1

Configuring the Administrative Domain with Hosts

About Administrative Domain Host Configuration

Viewing the Hosts in the Administrative Domain