Вы находитесь на странице: 1из 40

| Print | Contents | Close |

Introducing Oracle Secure Backup


Learning Objective

After completing this topic, you should be able to

recognize the basic principles of OSB

1. Basic principles of OSB


Oracle Secure Backup or OSB is a centralized tape-management software. It provides
reliable data protection to tape. It also supports major tape drives and libraries in a
Storage Area Network or SAN, Gigabit Ethernet or GbE, and Small Computer System
Interface or SCSI environments.
OSB enables you to

back up and restore data using a variety of machine architectures

control secondary storage-based data recording format and compression

use wildcards and exclusion lists to specify what you want to back up

perform full, incremental, or differential backups, and

support most popular tape drives and libraries

Supplement
Selecting the link title opens the resource in a new browser window.

Learning Aid
Use the learning aid Style Considerations for more information on the style
considerations for Oracle 11g Database used in this course.
OSB provides several additional benefits:

provides access to local and remote file systems and devices from any location in a network
without using Network File System or NFS or Common Internet File System or CIFS protocols

enables back up to and restore from Oracle Cluster File System or OCFS on Linux and Windows

provides duplex database backups that involve backing up the same files to multiple devices so
each data stream automatically goes to a separate device, and

maintains security and limits users who are authorized to perform data-management operations
Increased demands on the enterprise backup infrastructure require more rigorous
service-level agreements for backup windows and restoration time, while achieving
reliable data protection within the budget. The tape technology meets this challenge by
offering high-speed devices and high-capacity media with a throughput similar to that of a
disk generally, at a high cost.
OSB addresses this issue by providing centralized tape-backup management for Oracle
Database and file systems in mixed, diverse environments, thus reducing the cost and
complexity of tape backup and restoration. Oracle Databases are integrated via Recovery
Manager or RMAN with OSB and that UNIX, Linux, Windows, and Network Attached
Storage or NAS directly use OSB.
Some of the many options available for protecting your Oracle data are backing up solely
to disk, backing up to disk as a staging area for tape backups, or backing up directly to
tape.
Disk backup and restore operations are generally faster than the equivalent tape
operations. However, tape backups provide some advantages for long-term backup
requirements, such as off-site storage and portability, which allow you to move backups
from one data center to another.

Graphic
The backup and restore operation includes Oracle Beehive configuration files,
Oracle Application Server configuration files, Oracle Database, and file-system
data. For backup and restore, you use Oracle 9i and later database versions and
Real Application Clusters. For file-system data, you use Oracle home installations
and other nondatabase data.

Note
OSB has its own release cycle and version numbers; for example, OSB 10.2 is the
correct version for Oracle Database 11g (Release 1).
OSB provides tape backup management for all your files relating to Oracle products,
including

the Oracle Database backups stored on tape through integration with Recovery Manager

seamless support of Oracle Real Application Clusters or RAC

support for OCFS and Automatic Storage Management or ASM, and

central administration of distributed clients and media servers including Oracle Application Server,
Oracle Collaboration Suite, and Oracle home and binaries
The key benefits of RMAN and OSB integration over other third-party media management
libraries are

exclusive support of RMAN backup encryption to tape

faster, more reliable database backups to tape, and

a single technical support resource, expediting problem resolution


The Enterprise Manager integration, exclusive to OSB, provides a familiar interface for
Oracle customers, reducing any learning curves associated with other products. This
integration also helps the management of the entire Oracle Database backup and
recovery from disk or Flash Recovery Area to tape.
RMAN and OSB integration also provides advanced, effective security based on proven
Oracle technology.
Details about the security technology are Secure Sockets Layer or SSL and Embedded
Oracle wallets.
To configure OSB, you must define an administrative domain. An administrative domain is
a group of machines on your network that you manage as a common unit to perform
backup and restore operations. An administrative domain has one administrative server,
one or more clients, and one or more media servers.
Administrative server
The administrative server is a machine in your administrative domain that contains full
installation of the OSB software. This host maintains backup catalog files and other files for
configuration settings and administrative data. The administrative server runs the
scheduler, which starts and monitors jobs within the administrative domain. You need one
administrative server for each administrative domain at your site. To configure an
administrative server, choose an administrative server installation when installing OSB on
the host.
Media server
A media server is a machine that has one or more secondary storage devices, such as a
tape library, connected to it. The media server transfers data to and from its attached

storage devices. During installation, you can configure multiple secondary storage devices
on media servers.
Client
A client is a machine whose locally accessed data is backed up by OSB. Most of the
machines defined within the administrative domain are clients.
The OSB Architecture includes OSB catalog and daemons. The OSB catalog is a
directory structure with host-specific subdirectories. This means the contents vary
depending on the roles you assign to the host. An administrative server has the central
catalog with configuration and metadata.
Daemons or services are processes that run in the background and perform OSB
operations on behalf of an application.

Graphic
The client is connected to the administrative server, which is connected to the
media server. The central catalog of the administrative server contains
obscheduled, observiced, and obhttpd.

Question
Which element of the administrative domain runs the scheduler?
Options:
1.

Media server

2.

Client

3.

Administrative server

4.

OSB catalog

Answer
Option 1: This option is incorrect. A media server is a machine that has one or
more secondary storage devices, such as a tape library, connected to it.
Option 2: This option is incorrect. A client is a machine whose locally accessed
data is backed up by OSB.
Option 3: This option is correct. The administrative server is a machine in your
administrative domain that contains full installation of the OSB software. The
administrative server runs the scheduler, which starts and monitors jobs within the
administrative domain.

Option 4: This option is incorrect. OSB catalog is a directory structure with hostspecific subdirectories. The central catalog with configuration and metadata
resides on the administrative server.
Correct answer(s):
3. Administrative server
Some daemons run continually; others run only to perform specific work and then exit
when the work is complete. OSB daemons actively participate in managing backup and
restore operations.
Some of these daemons are
obscheduled
The obscheduled daemon initiates scheduled events and manages jobs.
observiced, and
On the administrative server, the observiced daemon runs jobs such as backup and
restore operations at the request of the obscheduled daemon.
obhttpd
The obhttpd or the Apache Web server daemon provides the Web tool GUI for OSB.
The OSB software offers centralized backup management of heterogeneous clients and
servers by storing backup and configuration data in a central repository called the OSB
administrative server.
The administrative server contains a consolidated backup catalog, providing a single
location for managing backup policies, scheduling backups for multiple platforms, and
managing local and remote tape devices.
The configured machines and devices managed by an administrative server make up the
OSB administrative domain.

Graphic
The OSB administrative server schedules backups for NAS, UNIX or Linux, and
Windows platforms. The platforms and the administrative server are connected
through a LAN to Oracle Database and the OSB Cloud module. The media
servers are locally backed up to the tape library via Oracle Database and other
databases.
The OSB tape management system minimizes the complexity of managing diverse
architectures by offering

flexible tape device configuration with options for single and multi-hosted tape libraries

support for major tape libraries and tape drives in GbE and SCSI environments

client/server architecture providing centralized administration of distributed media servers over a


LAN or a WAN
The Storage Cloud enables users to take advantage of the virtually unlimited pool of
computing resources and storage over the Internet or the Cloud.
Unlike the traditional IT setup, users have little insight or control over the underlying
infrastructure. Their interaction with the Cloud is primarily governed through an abstracted
interface provided by the Cloud vendor. The Cloud is essentially disk storage.
With the OSB Cloud module, it is possible to send the local disk backups of the Oracle
Database directly to a storage cloud for off-site storage purposes. Amazon S3 is the first
Cloud vendor that Oracle has partnered with, to enable database backup in the Cloud.
This functionality may be extended to more Cloud platforms or vendors in the future.
Backup and recovery from the Cloud is performed by RMAN. OSB 10.2 cannot back up to
disk. So OSB 10.2 does not have an explicit integration with the Cloud. RMAN backup
encryption and advanced compression technologies may be used for Cloud backup
strategies.

Question
Which statements accurately describe OSB centralized tape backup
management?
Options:
1.

Its media server contains a consolidated backup catalog

2.

It offers flexible tape device configuration

3.

Its client/server architecture provides centralized administration of distributed media


servers

4.

It is explicitly integrated with the Cloud

Answer
Option 1: This option is incorrect. The administrative server contains a
consolidated backup catalog, providing a single location for managing backup
policies, scheduling backups for multiple platforms, and managing local and
remote tape devices.

Option 2: This option is correct. The OSB tape management system minimizes
the complexity of managing diverse architectures by offering flexible tape device
configuration with options for single and multi-hosted tape libraries.
Option 3: This option is correct. The OSB client/server architecture provides
centralized administration of distributed media servers over a LAN or a WAN.
Option 4: This option is incorrect. OSB 10.2 cannot back up to disk and does not
have explicit integration with the Cloud. RMAN backup encryption and advanced
compression technologies may be used for Cloud backup strategies.
Correct answer(s):
2. It offers flexible tape device configuration
3. Its client/server architecture provides centralized administration of distributed
media servers
OSB supports SAN environments. In a typical SAN environment, one or more servers are
attached to a SAN, along with one or more tape devices. Each of the tape devices
attached to a SAN appears local to the servers using SAN. Clients within the
administrative domain are backed up over the network to the tape devices on the
configured media servers.
OSB automatically manages resource contention for tape drives within the SAN. During a
backup or a restore operation, a server engages a tape drive, thereby making it
temporarily unavailable to other servers. When the operation completes, the tape drive is
again available for use by any of the servers using the SAN, as permitted by your
configuration.

Graphic
The SAN environment is connected to the administrative server via a LAN.
When configuring tape devices, you are asked to configure attachments, where each
attachment describes a data path between the host and the device itself. A device must
have at least one attachment. In a SAN environment, a tape device may have multiple
attachments, one for each host that can access the device.
The Fiber fabric and switches within a SAN are transparent to OSB. Therefore, SAN
interoperability becomes important at the hardware level. When configuring a SAN, it is
recommended to confirm that hardware components have been tested and certified to
work together.

Question

Identify the tasks you can perform with OSB.


Options:
1.

Manually manage resource contention for tape drives within the SAN

2.

Perform backup and recovery from the Cloud to a disk

3.

Use exclusion lists to specify what is backed up

4.

Limit the users authorized to perform data management operations

Answer
Option 1: This option is incorrect. OSB automatically manages resource
contention for tape drives within the SAN. During a backup or a restore operation,
a server engages a tape drive, which makes it temporarily unavailable to other
servers.
Option 2: This option is incorrect. Backup and recovery from the Cloud is
performed by RMAN. OSB 10.2 cannot back up to disk.
Option 3: This option is correct. OSB enables you to use wildcards and exclusion
lists to specify what you want to back up.
Option 4: This option is correct. OSB enables you to maintain security and limit
the users who are authorized to perform data management operations.
Correct answer(s):
3. Use exclusion lists to specify what is backed up
4. Limit the users authorized to perform data management operations
You can access OSB in four different ways depending on what you want to do:
using Enterprise Manager
Enterprise Manager provides a graphical interface to OSB for users who elect to perform
database backup and restore operations through integration with RMAN. You can also
perform administrative tasks such as managing media and devices within the OSB
administrative domain. The Enterprise Manager console includes a link to the OSB Web
tool for performing file-system backup and restore operations.
using RMAN
You can use RMAN to back up your databases directly to tape. RMAN can be accessed
either through the RMAN executable or through Enterprise Manager. RMAN
communicates with OSB through the system backup to tape or SBT interface.
using the Web tool, and

The Web tool is a GUI application that enables you to configure administrative domains,
manage operations, browse the backup catalog, and back up and restore data. It provides
a graphical and interactive interface to access the obtool utility. You should use this
interface when making backups of file-system data.
using the obtool utility
The obtool utility provides a command-line interface to OSB. This interface gives you the
same functionality as the GUI interface.

Summary
In this topic, you've learned to recognize the basic principles of OSB.

Table of Contents
| Top of page |
| Learning Objective |
| 1.Basic principles of OSB |
| Summary |
Copyright 2009 SkillSoft. All rights reserved.
SkillSoft and the SkillSoft logo are trademarks or registered trademarks of SkillSoft in the United States and certain other countries.
All other logos or trademarks are the property of their respective owners.

| Print | Contents | Close |

Oracle Secure Backup Media Concepts


Learning Objectives

After completing this topic, you should be able to

recognize how the OSB backup hierarchy works


recognize how OSB enables secondary storage devices, tape libraries, and tape drives to be used
for backup and restore operations
recognize how to manage and secure data with OSB and RMAN

1. The OSB backup hierarchy

Oracle Secure Backup or OSB organizes the backups it creates in a simple hierarchy.
This hierarchy comprises the following logical concepts:
backup image
A backup image is the product of a backup operation. A backup image is a file that consists
of one or more backup sections. A backup image can be contained within a single volume,
or it can span multiple volumes. The part of a backup image that fits on a single volume is
called a backup section.
volume
A volume is a single unit of media, such as an LTO-3 tape. It can store many backup
images.
volume set, and
A volume set is a group of one or more volumes that contain a complete backup image.
media family
A media family is a named classification of volumes that share some common attributes,
such as the volume naming method, the policies used for writing data to volumes, and the
length of time volumes are retained in the media family.
When you back up files using OSB, you generate a volume set that has some common
characteristics defined by the media family that you have associated with your backup
operation.

Question
OSB organizes the backups it creates in a simple hierarchy, which is composed of
logical media concepts. Match each concept to its description.
Options:
A.

Backup image

B.

Media family

C.

Volume

D.

Volume set

Targets:
1.

A group of one or more volumes that contain a complete backup image

2.

A single unit of media

3.

The product of a backup operation

4.

A named classification of volumes that share some common attributes

Answer
A volume set is a group of one or more volumes that contain a complete backup
image. You generate a volume set when you back up files using OSB.
A volume is a single unit of media, such as an LTO-3 tape. It can store many
backup images.
A backup image is the product of a backup operation. A backup image is a file that
consists of one or more backup sections.
A media family is a named classification of volumes that share some common
attributes, such as the volume naming method, the policies used for writing data to
volumes, and the length of time volumes are retained in the media family.
Correct answer(s):
Target 1 = Option D
Target 2 = Option C
Target 3 = Option A
Target 4 = Option B
The backup of Oracle Database, created by Recovery Manager or RMAN, results in an
RMAN-specific logical structure that acts as a backup set. This structure contains at least
one backup piece that is an RMAN-specific physical file containing the backed up data.
OSB backs up and maintains backup metadata for each RMAN backup piece written to
tape within its own catalog. You can browse backup pieces with the obtool command line
or the OSB Web tool.

Note
Use RMAN for the management of RMAN backup pieces.
If you manage the backup pieces stored on tape using OSB utilities instead of RMAN, the
OSB catalog and the RMAN repository can become unsynchronized. The best practice is
for backup pieces to be updated through RMAN and not manually by the use of OSB.
Consider an overview of how RMAN and OSB work together. Data files are at the OS
level. These data files are related to RMAN image copies and backup pieces, which are
connected to OSB backup images. File-system files, which of course do not have an
RMAN equivalent, relate directly to OSB backup images.

OSB backup images are stored as backup image sections on a volume, within a volume
set, which belongs to a media family in a tape library.

Graphic
Two or more backup pieces form a backup set.
Media families provide a way to establish write periods and retention policies for data
backed up to various kinds of tapes. Media families are used to classify and characterize
backup types. They are commonly associated with backup levels, which generally
correspond to retention times such as full, incremental, and archive log.
You can, for example, establish a media family for all of your backups that remain on-site,
and a separate media family for your backups that are to be stored off-site.
A media family is a classification of backup media that share the same
volume identification sequence
The volume ID consists of a fixed portion followed by a sequence number assigned and
updated by OSB. When you create a media family, you specify how to generate volume
IDs that become part of the volume label.
write window, and
The beginning of the write window is the time at which OSB first writes to a volume in the
volume set. The write window is a user-specified time interval that applies to all volumes in
the set. OSB continues to append backups to the volume set until the end of this interval.
When the write window closes, OSB does not allow further updates to the volume set until
it expires, is relabeled, reused, unlabeled, or overwritten.
expiration policy
When a volume set expires, OSB automatically considers each volume in the set eligible to
be overwritten. A media family is either content managed (default) or time managed. These
two policies are mutually exclusive.

2. Backup and restore operations


OSB maintains information about secondary storage devices, tape libraries, and tape
drives so they can be used for local and network backup and restore operations. These
devices are easily configured during the installation process, or a new device can be
easily added to an existing OSB environment.

Graphic

Tape library robotics move tapes between drives and slots. Storage elements or
slots store the tapes. A barcode reader scans labels on cartridges.
The various types of tape drives, including maintd1, maintd2, and maintd3, refer to
its tape format such as LTO-3 or SDLT600. Device connectivity varies by devices,
such as SCSI, Fiber, and iSCSI.
Each tape drive and tape library is uniquely identified within an OSB administrative
domain by a user-defined name, for example, mainlib and maintd1.
Because OSB manages tape drive operations, it must explicitly be able to identify the
tape drive as well as understand if the tape drive is housed within a tape library.
OSB must further determine which tape slots, or storage elements, are available for
storing tapes when they are not loaded on a tape drive.
Before you can use tape drives or tape libraries with OSB, you must add the device to the
administrative domain. OSB maintains a distinction between a device and the means by
which the device is connected to a host.
Each device you configure can have one or more attachments, where each attachment
describes a data path between a host and the device itself. Often an attachment includes
the identity of a host plus a UNIX device special file name, a Windows device name, or a
Network Attached Storage or NAS device name. In rare cases, additional information is
needed to complete the attachment definition.
A Fiber channel-attached tape drive or tape library often has multiple attachments, one for
each host that can directly access it.
When a device is attached to multiple hosts, OSB automatically manages contention for
the device so that only one host is permitted access to it at a time. For example, Storage
Area Network or SAN-attached devices often have multiple attachments, one for each
host that has local access to the device through its Fiber channel interface.
A virtual tape library or VTL leverages traditional tape backup with disk technology to
create an optimized backup and recovery infrastructure. Tape emulation software on the
disk appliance emulates popular tape devices and formats. Because VTLs identify
themselves as tape equipment, for the backup software, they appear identical to the
actual tape device that is emulated.
VTLs offer the performance advantages of disk backup, and they may be seamlessly
deployed in a system environment, without changing the backup infrastructure. VTLs are
increasingly being adopted into IT environments because of their flexible configuration
with user-defined options for number and type of tape emulation.

Most popular VTLs are supported by OSB and are attached to the network or servers,
depending on the manufacturer.

Question
Which statements accurately describe tape drives and libraries in relation to OSB?
Options:
1.

Devices are easily configured during the installation process

2.

An engaged tape drive is available for use by any of the servers on the SAN as
permitted by your configuration

3.

There's no distinction between a device and the means by which it connects to a


host

4.

You must manually identify the tape slots that are available for storing tapes

Answer
Option 1: This option is correct. Storage devices such as tape libraries and drives
are easily configured during the installation process, or a new device can be easily
added to an existing OSB environment.
Option 2: This option is correct. When a device is attached to multiple hosts, OSB
automatically manages contention for the device so that only one host is permitted
access to it at a time.
Option 3: This option is incorrect. OSB maintains a distinction between a device
and the means by which it is connected to a host. Each device you configure can
have one or more attachments, where each attachment describes a data path
between a host and the device itself.
Option 4: This option is incorrect. Because OSB manages tape drive operations,
it must explicitly be able to identify the tape drive as well as understand whether
the tape drive is housed within a tape library. OSB must further determine which
tape slots are available for storing tapes when they are not loaded in a tape drive.
Correct answer(s):
1. Devices are easily configured during the installation process
2. An engaged tape drive is available for use by any of the servers on the SAN as
permitted by your configuration

3. Manage and secure data

Managing the backup infrastructure of file-system data and Oracle Database data is
easily administered with OSB and RMAN. Defining what data to back up is conceptually
similar for file-system and database data. Both require that you, the user, define what to
include in the backup.
For the database, you use RMAN backup sets created using RMAN or Enterprise
Manager. For file systems, OSB uses datasets. Use the OSB Web tool to define filesystem datasets.
After defining what data to back up, you must determine what type of backup is most
appropriate to meet your backup and restore requirements. OSB offers multiple backup
levels for file-system backups including full backup levels, multiple incremental levels,
and an off-site backup level. The off-site level is actually a full backup performed without
interfering with any incremental backup strategies. OSB also provides flexible scheduling
options that enable you to determine ongoing backup schedules based on day and time
granularity.
For Oracle Database, RMAN offers full and incremental backup levels that are backed up
to tape by OSB.
After you have defined what, how, and how often to back up your data through
scheduling, OSB can automatically implement your backup schedules, only requiring
manual intervention for hardware errors or media needs.

Question
When managing the data to be protected, what tasks must be performed by the
user?
Options:
1.

Defining what to include in the backup

2.

Determining what type of backup is the most appropriate

3.

Implementing backup schedules

4.

Using RMAN to define file-system datasets

Answer
Option 1: This option is correct. Defining what data to back up is conceptually
similar for file-system and database data. Both require that you, the user, define
what to include in the backup.
Option 2: This option is correct. After defining what data to back up, you must
determine what type of backup is the most appropriate to meet your backup and
restore requirements. OSB offers multiple backup levels for file-system backups.

Option 3: This option is incorrect. After you have defined what, how, and how
often to back up your data through scheduling, OSB can automatically implement
your backup schedules, only requiring manual intervention for hardware errors or
media needs.
Option 4: This option is incorrect. For file systems, OSB uses datasets. You use
the OSB Web tool to define file-system datasets.
Correct answer(s):
1. Defining what to include in the backup
2. Determining what type of backup is the most appropriate
To secure data and access to the backup domain, OSB provides these features:
access control
To access the OSB software, you must enter a username and password or you must use
preauthorization. Each OSB user is assigned to a class, which defines the actions that are
permitted for that user.
host authentication, and
All hosts in the administrative domain use Secure Sockets Layer or SSL and X.509
certificates for identity verification and authentication. Sensitive data is encrypted before
transmittal over the network. The Web server requires a signed X.509 certificate and
associated public and private keys to establish an SSL connection with a client browser.
The X.509 certificate for the Web server is self-signed by the installation script when you
install OSB on the administrative server. Currently, the Network Data Management
Protocol or NDMP does not include a mechanism to accommodate the negotiation of an
SSL connection to NDMP filers.
encryption
For your database backups, you have a choice of RMAN and OSB encryption. For your
file-system backups, use OSB encryption. You can also use OSB encryption for data in
transport and on tape.
OSB provides several advantages for Oracle Database:
inexpensive tape backup utility
Since Oracle 8.0, RMAN is the recommended backup utility for Oracle Database. It is
known for reliable, automated, online protection of data to disk and is integrated with
numerous third-party media management products for backups to tape. OSB provides an
alternative to expensive, third-party tape backup utilities by providing the media
management layer for RMAN tape utilization.
maximum return on investment

OSB increases customer return on investment by providing end-to-end tape data


protection for your Oracle environment at a fraction of the cost of other tape products.
backup encryption
OSB exclusively provides RMAN encrypted backup to tape.
fast and efficient tape backup, and
To deliver the fastest database tape backup, OSB backs up only used blocks from Oracle
Database 10.2.0.2 and later. This process makes the backups faster and smaller, which
also saves space on tape.
single vendor for data backup
OSB as part of the Oracle technology stack offers a single-vendor technical resource
for complete Oracle Database protection. OSB installation automatically links the system
backup to tape or SBT libraries for RMAN tape backups.

Summary
In this topic, you've learned how the OSB backup hierarchy works, and how it enables
secondary storage devices, tape libraries, and tape drives to be used for backup and
restore operations. You've also learned how to manage and secure data with OSB and
RMAN.

Table of Contents
| Top of page |
| Learning Objectives |
| 1.The OSB backup hierarchy |
| 2.Backup and restore operations |
| 3.Manage and secure data |
| Summary |
Copyright 2009 SkillSoft. All rights reserved.
SkillSoft and the SkillSoft logo are trademarks or registered trademarks of SkillSoft in the United States and certain other countries.
All other logos or trademarks are the property of their respective owners.

| Print | Contents | Close |

Installing Oracle Secure Backup on Linux

Learning Objective

After completing this topic, you should be able to

recognize how to install OSB

1. OSB installation tasks


Before installing Oracle Secure Backup or OSB on Linux, there are certain preinstallation
tasks that need to be performed. However, there is no required sequence between these
preinstallation tasks.
You must check the supported device list on the Oracle Technology Network or OTN to
confirm that your environment is supported. Check that the platform is supported by the
host role, and that tape library, tape drive, and connectivity are supported.
During preinstallation, you plan disk space for OSB and obtain the OSB software via OTN
download or CD. You also plan your administrative domain by determining which host will
be the administrative server, which will be the media server(s), and which will be the
client(s). Additionally, you obtain SCSI device information.
Each host that participates in an OSB administrative domain must have a network
connection and run TCP/IP. OSB uses this protocol for all inter and intra-server
communication between its own and other system components.
Each appliance that employs a closed operating system, such as Network Attached
Storage or NAS and tape servers, is backed up using Network Data Management
Protocol or NDMP. This protocol enables OSB to access primary and secondary storage
controlled by the appliance.
Each host that participates in an OSB administrative domain must also have some
preconfigured way to resolve a host name to an IP address. Most systems use one of the
name resolution mechanisms Domain Name Service or DNS, Network Information
Service or NIS, Windows Internet Name Service or WINS, or a local hosts file.
OSB does not require a specific mechanism. OSB requires only that upon presenting the
underlying system software with an IP address you have configured, OSB obtains an IP
address corresponding to that name.

Question
Identify the true statements about performing OSB preinstallation tasks.
Options:

1.

You should check the supported device list on OTN to confirm that your environment
is supported

2.

OSB uses TCP/IP for all inter and intra-server communication

3.

Each host in an administrative domain must use a local hosts file for name
resolution

4.

DNS enables OSB to access primary and secondary storage controlled by the
appliance

Answer
Option 1: This option is correct. You should check the device list on OTN to
confirm that the platform support by host role, tape library and tape drive, and
connectivity are supported.
Option 2: This option is correct. Each host that participates in an OSB
administrative domain must have a network connection and run TCP/IP. OSB uses
this protocol for all inter and intra-server communication between its own and
other system components.
Option 3: This option is incorrect. Each host that participates in an OSB
administrative domain must also have some preconfigured way to resolve a host
name to an IP address. Most systems use one of the name resolution
mechanisms DNS, NIS, WINS, or a local hosts file.
Option 4: This option is incorrect. NDMP enables OSB to access primary and
secondary storage controlled by the appliance.
Correct answer(s):
1. You should check the supported device list on OTN to confirm that your
environment is supported
2. OSB uses TCP/IP for all inter and intra-server communication
The installation and configuration of your administrative domain includes installing the
OSB software itself on each of your hosts except NDMP-enabled hosts such as NAS
filers. You then define your administrative domain on the administrative server. This step
involves defining all media servers, clients, and NAS filers.
When installing a media server, OSB device attachments are created as part of the
device driver installation process. These attachments are used during the device
definition. Make the administrative server aware of the tape devices that exist in your
administrative domain. On each defined media server, you configure the directly attached
SCSI and Fiber channel devices (tape libraries and tape drives).
If you use a NAS filer with attached tape libraries and tape drives, you can use OSB

commands to discover these devices; this allows OSB to recognize and communicate
with NAS-attached devices.
You perform these steps to install the OSB software:

Code
[stage] $ su
Password:
[stage]# mkdir -p /usr/local/oracle/backup
[stage]# cd /usr/local/oracle/backup
[backup]# /stage/osb_installmedia/setup
1. log in as the root user
The code to do this is the following:
[stage] $ su
Password:
Code
[stage] $ su
Password:
[stage]# mkdir -p /usr/local/oracle/backup
[stage]# cd /usr/local/oracle/backup
[backup]# /stage/osb_installmedia/setup

2. create an OSB home directory


The code to do this is the following:
[stage]# mkdir -p /usr/local/oracle/backup
Code
[stage] $ su
Password:
[stage]# mkdir -p /usr/local/oracle/backup
[stage]# cd /usr/local/oracle/backup
[backup]# /stage/osb_installmedia/setup

3. change your directory to the <OSB_Home> directory, and


The code to do this is the following:
[stage]# cd /usr/local/oracle/backup
Code

[stage] $ su
Password:
[stage]# mkdir -p /usr/local/oracle/backup
[stage]# cd /usr/local/oracle/backup
[backup]# /stage/osb_installmedia/setup

4. run the setup program from your


<OSB_Home> directory and respond to the prompts
The code to do this is the following:
[backup]# /stage/osb_installmedia/setup
Code
[stage] $ su
Password:
[stage]# mkdir -p /usr/local/oracle/backup
[stage]# cd /usr/local/oracle/backup
[backup]# /stage/osb_installmedia/setup

The recommended directory for installing the OSB software is /usr/local/oracle/backup.


You can install the software in a different directory, if desired. However, then the printed
and online documentation for OSB may not agree with your actual commands, output,
and GUI screens. For users new to OSB, this can add an unwanted layer of confusion.
Here you use the default directory /usr/local/oracle/backup as OSB_Home.
After your OSB_Home directory is created, change your current directory to the
OSB_Home directory and execute the setup program from your staging area, which in
this example, is the /stage/osb_installmedia directory. If you use your CD-ROM drive as
your staging area, use a command similar to /cdrom/cdrom0/setup. In this example,
a stage directory is used instead of a CD-ROM drive.

Code
[stage] $ su
Password:
[stage]# mkdir -p /usr/local/oracle/backup
[stage]# cd /usr/local/oracle/backup
[backup]# /stage/osb_installmedia/setup

Note

There is no default OSB_Home environment variable, which is used to refer to this


directory, unlike the ORACLE_HOME variable used with Oracle Database
installations.
OSB analyzes the host on which you start the installation; then it loads the relevant
software.
installob is the primary installation script for OSB. It can be called in a stand-alone
fashion by invoking the installob shell script.

Code
Welcome to Oracle's setup program for Oracle Secure Backup.
This program loads Oracle Secure Backup software from the
CD-ROM
to a file-system directory of your choosing.
This CD-ROM contains Oracle Secure Backup version
10.2.0.2.0_linux32.
Please wait a moment while I learn about this host... done.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1. Linux32 administrative server, media server, client
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - Loading Oracle Secure Backup installation tools... done.
Loading linux32 administrative server, media server,
client...
done.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - Loading of Oracle Secure Backup software from CD-ROM is
complete. You may unmount and remove the CD-ROM.
Would you like to continue Oracle Secure Backup installation
with 'installob' now? (The Oracle Secure Backup Installation
Guide contains complete information about installob.)
Please answer 'yes' or 'no' [yes]: no
The obparameters file is preconfigured. If you want a default installation, answer no once
to the question about customizing this file.
If you wish to customize it, then you can use a text editor to edit the obparameters file in
the /usr/local/oracle/backup/install/ directory, referred to as the OSB_Home/install
directory.

Graphic
In this example, the answer to the questions Have you already reviewed and
customized install/obparameters for your Oracle Secure Backup installation [yes]?
and Would you like to do this now [yes]? is no.

Code
Welcome to installob, Oracle Secure Backup's UNIX
installation
program.
It installs Oracle Secure Backup onto one or more UNIX or
Linux
systems on your network. (Install Oracle Secure Backup for
Windows using the CD-ROM from which you loaded this
software.)
For most questions, a default answer appears enclosed in
square
brackets. Press Enter to select this answer.
Please wait a few seconds while I learn about this
machine...
done.
Have you already reviewed and
install/obparameters
for your Oracle Secure Backup
Would you like to do this now
- - - - - - - - - - - - - - - -

customized
installation [yes]? no
[yes]? no
- - - - - - - - - - - - - - -

Various parameters are defined that you can configure to meet the needs of your
business.
For example, you can modify parameters for

Code
Welcome to installob, Oracle Secure Backup's UNIX
installation
program.
It installs Oracle Secure Backup onto one or more UNIX or

Linux
systems on your network. (Install Oracle Secure Backup for
Windows using the CD-ROM from which you loaded this
software.)
For most questions, a default answer appears enclosed in
square
brackets. Press Enter to select this answer.
Please wait a few seconds while I learn about this
machine...
done.
Have you already reviewed and
install/obparameters
for your Oracle Secure Backup
Would you like to do this now
- - - - - - - - - - - - - - -

customized
installation [yes]? no
[yes]? no
- - - - - - - - - - - - - - -

automatic startup at boot time of the observiced daemon


automatic creation of an OSB user, called oracle, that is assigned the oracle class and
preauthenticated to be used by RMAN, and
default certificate key size
Specify the role of this server. If you install OSB for the first time in a specific network,
then you should begin with an administrative server installation. By default, the
administrative server is also configured as a client.

Code
Oracle Secure Backup is not yet installed on this machine.
Oracle Secure Backup's Web server has been loaded, but is
not
yet configured.
You can install this host in one of the three ways:
(a) administrative server
(the host will also be able to act as a media server
or
client)
(b) media server
(the host will also be able to act as a client)

(c) client
If you are not sure which way to install, please refer to
the
Oracle Secure Backup Installation Guide. (a,b or c) [a]? a
Choose a password for the OSB encryption key store, which follows your security
strategies. Do not forget this password.

Graphic
In this example, the key store password, keypassword, is entered as the
placeholder.

Code
Beginning the installation. This will take just a minute and
will produce several lines of informational output.
Installing Oracle Secure Backup on edvmr1p0 (Linux version
2.6.9-67.0.7.0.1.ELxenU)
You must now enter a password for the Oracle Secure Backup
encryption key store. Oracle suggests you choose a password
of
at least 8 characters in length, containing a mixture of
alphabetic and numeric characters.
Please enter the key store password:keypassword <<not echoed>>
Re-type password for verification:keypassword <<not echoed >>

Note
In real development and production environments, use strong passwords.
Choose a password for the admin user, which follows your security strategies. If you
know the e-mail address of the admin user, you can enter it as well.

Graphic
In the example, the admin password, adminpassword, is entered as the
placeholder.

Code
You must now enter a password for the Oracle Secure Backup
'admin' user.
Oracle suggests you choose a password of at least 8
characters
in length, containing a mixture of alphabetic and numeric
characters.
Please enter the admin password:adminpassword << not echoed >>
Re-type password for verification:adminpassword <<not echoed>>
You should now enter an email address for the Oracle Secure
Backup 'admin user. Oracle Secure Backup uses this email
address to send job summary reports and to notify the user
when
a job requires input. If you leave this blank, you can set
it
later using the obtool's 'chuser' command.
Please enter the admin email address:
During software installation, you see the actions that are performed. An example is
displayed.

Code
generating links for admin installation with Web server
updating /etc/ld.so.conf
checking Oracle Secure Backup's configuration file
(/etc/obconfig)
setting Oracle Secure Backup directory to
/usr/local/oracle/backup in
/etc/obconfig
setting local database directory to /usr/etc/ob in
/etc/obconfig
setting temp directory to /usr/tmp in /etc/obconfig
setting administrative directory to
/usr/local/oracle/backup/admin in
/etc/obconfig
protecting the Oracle Secure Backup directory
creating /etc/rc.d/init.d/observiced
activating observiced via chkconfig
initializing the administrative domain
If you wish to see daemons or background processes, enter this code after the
installation.

Code
# ps -a |grep ob
13760 pts/0
00:00:00 observiced
13772 pts/0
00:00:00 obscheduled
After the OSB software has been installed, you are asked if you want to configure any
tape libraries or tape drives that might be attached to the current host.
After the software installation completes, an installation summary appears.

Code
*********************** N O T E ************************
On Linux systems Oracle recommends that you answer no to
the next two questions. The preferred mode of operation on
Linux systems is to use the /dev/sg devices for attach
points as described in the 'ReadMe' and in the
'Installation and Configuration Guide'.
Is edvmr1p0 connected to any tape libraries that you'd
like to use with Oracle Secure Backup [no]? no
Is edvmr1p0 connected to any tape drives that you'd like
to use with Oracle Secure Backup [no]? no
Installation summary:
Installation
Mode
admin

Host
Name
edvmr1p0

OS
Name
Linux

Driver
Installed?
no

OS Move
Required?
no

Reboot
Req?
no

Oracle Secure Backup is now ready for your use.

Question
When installing and configuring OSB on Linux, what step immediately follows
software installation?
Options:
1.

Configuring tape libraries and drives

2.

Choosing a password for the admin user

3.

Choosing a password for the encryption key store

4.

Specifying the role for the server

Answer
Option 1: This option is correct. After the OSB software has been installed, you
are asked if you want to configure any tape libraries or tape drives that might be
attached to the current host.
Option 2: This option is incorrect. During installation, you must specify the role of
the server. If you install OSB for the first time on a specific network, then you
should begin with administrative server installation.
Option 3: This option is incorrect. During installation, you need to choose a
password for the OSB encryption key store, which follows your security strategies.
Option 4: This option is incorrect. During installation, you need to choose a
password for the admin user, which follows your security strategies. If you know
the e-mail address of the admin user, you can enter it as well.
Correct answer(s):
1. Configuring tape libraries and drives
You can use either the GUI interface or the obtool command-line interface or CLI to
access OSB information. In all cases, you must use a valid username and password.
For example, if you want to view OSB users, you can choose any of these three
interfaces:
Web tool
You can start the Web tool by entering https://<host_name> into your Web browser. Click
the Configure tab, and then click Users.
Enterprise Manager, or
You can start Enterprise Manager by entering https://<host_name>:1158/em into your Web
browser. You then select Availability - Oracle Secure Backup Device and Media Configure - Users. Enterprise Manager is the recommended interface.
obtool
You can start the obtool command line by entering obtool in a terminal window and then
the lsuser command.
The Oracle Secure Backup Web tool Home page provides a snapshot of the current
status of OSB jobs and devices, presenting important summary information to
administrators and users.
The Home page includes the schedule times and status of recent jobs as well as job IDs,
job type, and job level. OSB provides a link for failed jobs, alerting users and

administrators to potential trouble spots.


The Devices link lists the devices associated with each job along with information
concerning device type, device name, and status. This page provides you with an overall
sense of the various backup or restore processes that are going on.

Graphic
The OSB Web tool interface contains five pages: Home, Configure, Manage,
Backup, and Restore. The Home page is selected.
The Web tool provides a graphic interface for just about all OSB features such as flexible
scheduling options for backups of file-system data. These options specify backups based
on the time of day and days of the week, month, quarter, or year. These options also
schedule backups to start immediately or at a future date.
The Web tool also provides backup windows to minimize impact on day-to-day backup
operations, and includes the ability to create off-site backups for remote storage without
disturbing currently scheduled incremental backups of the same data.
OSB provides some common obtool commands that you can use to query the OSB
administrative and catalog data. Depending on the information you want to retrieve, you
may use additional options to specify the amount of information returned, such as listing
all volumes for a particular media family or only listing the completed jobs.
These commands can assist you with troubleshooting your OSB installation and
configuration. For example, the lshost command displays the current roles of a host. If
you want to add a device to your OSB domain, the host must have the mediaserver
role, which is not installed by default.

Graphic
The common obtool commands table contains two columns: Category and Obtool
Command. To retrieve information about hosts, you use the lshost -l command,
and to display information about devices, you use the lsdev command. You use
lsssel command to display storage selectors used. If you want to retrieve user
info, you use the id, lsuser, and lsclass commands. For jobs and schedules, you
use the lsjob (-a | -c | -p) command, lsbw for backup windows, and the Lssched
command. You can use the lsds command for backing up dataset information, the
lspiece command for backing up RMAN backup pieces, lsbackup for file-system
backups, and lssection for backup image sections. To retrieve information about
media families, you can use the lsmf --long command. If you want to display
volumes, you use the lsvol --all or lsvol --library <libname> commands.

Note

For details of all command options, see the Oracle Secure Backup Reference on
the Oracle web site.
These examples illustrate how you can verify your installation with obtool commands.

Code
ps -e | grep ob
ob> lsuser
ob> lsmf --long
ps -e | grep ob
You can view OSB processes in Linux using this command.
ob> lsuser
ob> lsmf --long
You can view OSB users and default media family using these obtool commands.
This example depicts the use of obtool commands to verify your installation.

Code
ob> lsuser
admin
admin
oracle
oracle
ob> lsmf --long
OSB-CATALOG-MF:
Write window:
Keep volume set:
Appendable:
Volume ID used:
Comment:
RMAN-DEFAULT:
Keep volume set:
Appendable:
Volume ID used:
Comment:
family
ob> logout

7 days
14 days
yes
unique to this media family
OSB catalog backup media family
content manages reuse
yes
unique to this media family
Default RMAN backup media

2. Remove OSB installation


To remove OSB from a client or the administrative server, have all users log out of OSB
applications. Then close all sessions of the Web tool.

If you remove OSB from an administrative server, you are given the option of retaining the
administrative directory and its contents. This enables you to safely remove and reinstall
the product without deleting your administrative server data.
You must be logged in as the root user on UNIX or Linux systems to remove OSB
completely. If you are not logged in as root when you remove the software, you may not
have the privileges needed to delete files and shut down OSB daemons.
OSB-related processes such as the HTTP processes for the OSB Web tool should be
shut down before beginning the uninstallation process. To identify processes for OSB,
you can use this command.

Code
# /bin/ps -ef |grep ob
You can then use this command to kill each process in the list associated with OSB.

Code
kill -9 <pid>
If you remove OSB from the local machine, the uninstallob script removes the OSB
home directory when the script completes. For this reason, you should call the
uninstallob script from the parent directory of the OSB home directory.
If you encounter errors when removing the OSB software, or if the uninstallob script
fails to completely remove all files for OSB assuming you did not choose to save any
files correct the problem causing the error, if possible.
Then run the uninstallob script again until you receive this message.

Code
Oracle Secure Backup has been successfully removed from
<host>.

Summary
In this topic, you've learned how to install OSB on Linux.

Table of Contents

| Top of page |
| Learning Objective |
| 1.OSB installation tasks |
| 2.Remove OSB installation |
| Summary |
Copyright 2009 SkillSoft. All rights reserved.
SkillSoft and the SkillSoft logo are trademarks or registered trademarks of SkillSoft in the United States and certain other countries.
All other logos or trademarks are the property of their respective owners.

| Print | Contents | Close |

Installing Oracle Secure Backup on Windows


Learning Objective

After completing this topic, you should be able to

recognize how to install and configure OSB on Windows

1. Install OSB on Windows


Before beginning your installation of Oracle Secure Backup or OSB on Windows, check
the documentation for platform-specific details such as how to configure firewalls.
OSB supports configuring the administrative domain on a host running the Windows
operating system.
During the installation process, the Oracle Secure Backup Setup Wizard copies all OSB
files to the local host and generates Windows Registry entries.

Note
Every installation of OSB on Windows is a client installation and can additionally
be a media server or the administrative server installation. With OSB 10.2, it is not
necessary to stop tape device drivers before beginning your installation.
You first run the setup.exe program from the directory into which you originally
downloaded the software. The InstallShield Wizard opens. Click Next to continue.

A system check should inform you that this will be a clean installation of OSB. You
proceed to the next page.
The Customer Information dialog box is displayed. You specify your name and the name
of your company. You select a target user for the application, which may be all users or a
single user. Then you proceed to the next page.

Graphic
The Welcome to the InstallShield Wizard for Oracle Secure Backup page is open.
On the Oracle Secure Backup Setup page, you choose the program features to configure.
Media Server
To configure the Windows host as a media server, click the menu of the Media Server
icon. The menu displays several options. Selecting the This feature will be installed on
local hard drive option removes the X from the Media Server icon and installs the media
server software.
Administrative Server, or
To configure the Windows host as an administrative server, click the menu of the
Administrative Server icon and select the This feature will be installed on local hard
drive option. Again selecting this option removes the X from the Administrative Server icon
and installs the administrative server software.
Create "oracle" user
If you plan to perform Oracle Database backups and restores, repeat this process for
Create "oracle" user. Doing so creates an OSB user called oracle, with the rights and
privileges of the oracle class, whose purpose is to facilitate RMAN backup and restores
of Oracle Databases.
Click Next to continue. The Encryption Wallet Password page opens. Enter a strong
password for the encryption wallet and re-enter it for verification. Then click Next.

Graphic
The Encryption Wallet Password page contains two text boxes Password for
encryption wallet and Re-type password for verification.
On the Admin User Password and Email page, enter a strong password for the admin
user and re-enter it for verification. If possible, provide an e-mail address for the admin
user. OSB will send reports, such as the Job Summary, to this e-mail address. Click Next.

Clicking Install allows you to start copying files. A completion message will appear when
the files are copied, and you complete the Wizard.

Note
When the InstallShield Wizard is finished, it automatically calls the OSB
Configuration Wizard.
The Oracle Secure Backup Service Startup page opens.
Select a mode in which to start the OSB service, and then click Next to continue:

Automatic The Oracle Secure Backup service starts automatically when you reboot your host.
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.

Note
On the Windows operating system, the only daemon that runs as a Windows
service is the OSB service or observiced.
The Oracle Secure Backup Service Logon page is displayed. Select one of the following
options:

Graphic
The Service Logged On As section of the Oracle Secure Backup Service Logon
page contains two radio buttons System Account and This Account. The page
contains a note at the beginning. It states, "You may specify that the Oracle
Secure Backup service log on as the system account or another account that you
identify below. The account you choose must belong to the Backup Operators
group, must not be required to change password at logon, must have a password
that never expires, and must have the following rights: back up files and
directories, restore files and directories, log on as a service, act as part of the
operating system, increase quotas, replace a process level token."
System Account or
If you plan to run the OSB service daemon and associated subordinate daemons with full
privileges, click System Account.
This Account

If you plan to run the OSB service daemon and associated subordinate daemons with the
privilege set associated with an existing Windows user account, click This Account and
enter the Windows user account name and password. If you choose this option, ensure
that the account you select has enough backup and restore privileges. The required
privileges are listed in the Oracle Secure Backup Service Logon page.
Click Next. The SCSI Devices page is displayed. Note the OSB Name, which you need to
know when you manually configure devices.
Click Finish to complete the installation.
Repeat this installation process for each Windows host in your administrative domain.

Graphic
The note on the SCSI Devices page states, "This page shows the SCSI tape and
library devices that are active on your system. Checked devices are assigned to
the OSB device driver. To assign or remove a device from the OSB device driver,
simply click its checkbox."
This page contains three columns Device, Location, and OSB Name. The OSB
Name column contains entries such as //./obl1, //./obl2, and //./obt3.

Question
If you want to run the OSB service daemon with full privileges, what should you
specify when configuring service logon information?
Options:
1.

The system account

2.

An account username and password

3.

The automatic mode

4.

The manual mode

Answer
Option 1: This option is correct. If you plan to run the OSB service daemon and
associated subordinate daemons with full privileges, click System Account
when specifying service logon information.
Option 2: This option is incorrect. If you plan to run the OSB service daemon
and associated subordinate daemons with the privilege set associated with an

existing Windows user account, click This Account and enter the Windows user
account name and password when specifying service logon information.
Option 3: This option is incorrect. Automatic mode can be specified when starting
the OSB service. It causes the OSB service to start automatically when you reboot
your host.
Option 4: This option is incorrect. You specify Manual if you want the OSB service
to be started manually by a user who is a member of the Administrative group and
not when configuring service logon information.
Correct answer(s):
1. The system account
The OSB home directory is created on every host where you install OSB, although the
contents of the directory vary depending on the roles you assigned to the host.
The example depicts the installed directories that are common to an administrative server
on any operating system. However, an administrative server configured on a Linux host
will have additional directories created.
In addition to containing the OSB directory, each host on which OSB is installed, contains
a configuration file. The configuration file is called obconfig.txt in the db subdirectory
where you install OSB on Windows, and it is called obconfig in the /etc directory on UNIX
and Linux systems.

Graphic
The <OSB_Home> directory contains the admin, apache, bin, device, help, and
samples subdirectories. The admin subdirectory contains these files config,
history, log, and state. The apache subdirectory contains these files conf,
htdocs, images, logs, and modules.

Supplement
Selecting the link title opens the resource in a new browser window.

Job Aid
Access the job aid Oracle Secure Backup Installed Files to learn about types of
files in OSB directories.

Directories are created for a media server or a client. The bin and device subdirectories
are created on every computer, regardless of the operating system used. Other
directories are created for computers that use the Windows operating system.

Graphic
For a media server, the /usr/local/oracle/backup directory contains these
subdirectories .drv.<OS>, help, bin, and device. For a client, the
/usr/local/oracle/backup directory contains these subdirectories help, bin, and
device.

Supplement
Selecting the link title opens the resource in a new browser window.

Job Aid
Access the job aid Media Server and Client Directories to learn about the types
of directories created for a media server and client.

Summary
In this topic, you have learned how to install and configure OSB on Windows.

Table of Contents
| Top of page |
| Learning Objective |
| 1.Install OSB on Windows |
| Summary |
Copyright 2009 SkillSoft. All rights reserved.
SkillSoft and the SkillSoft logo are trademarks or registered trademarks of SkillSoft in the United States and certain other countries.
All other logos or trademarks are the property of their respective owners.

| Print | Contents | Close |

Installing and Configuring Oracle Secure Backup

Learning Objective

After completing this topic, you should be able to

install and configure OSB

Exercise overview
You have been promoted to Oracle Secure Backup administrator for your organization.
You first want to create your own training environment. You want to install Oracle Secure
Backup on only one server and confirm that each installation step is correctly executed.
You have already logged in as the root user and created /usr/local/oracle/backup as your
Oracle Secure Backup home directly. From the backup directory, you've ensured that the
uncompress utility is available.
In this exercise, you're required to install OSB and configure media for use with OSB.
This involves the following tasks:

installing OSB

configuring media for OSB

Task 1: Installing OSB


You now want to start the installation of Oracle Secure Backup from the staging
directory /stage/osb_installmedia. You have not yet reviewed and customized the
obparameters file and you do not want to do so during the installation. Choose the
installation type where the host can also act as the media server or client. Specify and
confirm a password of "oracle" for the key store and admin account. Do not specify an
admin email address. The host is not connected to any tape libraries or drives that should
be associated with OSB.

Steps list
Instructions
1. Type /stage/osb_installmedia/setup and press Enter
2. Type yes and press Enter
3. Type no and press Enter
4. Type no and press Enter
5. Type a and press Enter
6. Type oracle and press Enter at each of four prompts

Steps list
Instructions
7. Press Enter
8. Type no and press Enter
9. Type no and press Enter

Task 2: Configuring media for OSB


You have configured the mediaserver role for the current host and configured the virtual
test drives. You now want to view information about the configured devices, insert
volumes into both tape libraries, and confirm the correct configuration using the obtool
interface. View the virtual drives and libraries under the u01 directory using the ls
-l /u01 command. Start the obtool and then view all the roles of your host with the
lshost command. View the just created devices using the lsdev command. Insert
unlabeled volumes into both libraries by executing the config2.txt OSB script. List the
volumes in the vlib2 library using the lsvol -L vlib2 command. Then view the default
media families using the lsmf --long command.

Steps list
Instructions
1. Type ls -l /u01 and press Enter
2. Type obtool and press Enter
3. Type lshost and press Enter
4. Type lsdev and press Enter
5. Type < /home/oracle/labs/config2.txt and press Enter
6. Type lsvol -L vlib2 and press Enter
7. Type lsmf --long and press Enter

Table of Contents
| Top of page |
| Learning Objective |
| Exercise overview |
| Task 1: Installing OSB |
| Task 2: Configuring media for OSB |

Copyright 2009 SkillSoft. All rights reserved.


SkillSoft and the SkillSoft logo are trademarks or registered trademarks of SkillSoft in the United States and certain other countries.
All other logos or trademarks are the property of their respective owners.

Вам также может понравиться