5 Administrative Domain Configuration and Management

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 of the steps, such as "Adding a Host to the Administrative Domain", are also useful when managing an existing Oracle Secure Backup administrative domain.

This chapter contains these 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 Oracle Secure Backup Web tool. The same tasks can be performed using the obtool command-line interface to Oracle Secure Backup.

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, and security options as well as some configuration of 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.

Administrative Domain Configuration Steps: Outline

The required steps to configure Oracle Secure Backup after installation are as follows:

Use your Web browser to connect to the Oracle Secure Backup Web tool running on the administrative server as the admin user. This task is described in "Using the Oracle Secure Backup Web Tool".
For each host in your domain to be set up for the role of media server, perform the following steps:
1. Add the host to the administrative domain. This task is described in "Configuring the Administrative Domain with Hosts".
  
  Note:
  If the administrative server is also assigned the media server role, then it is already part of the administrative domain.
2. Configure the administrative domain to include each tape device attached to this host. This task is described in "Adding Tape Devices to an Administrative Domain".
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".

After configuring each client host, ping it to ensure that it is reachable.
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".

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:

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.

See Also:

"Pinging a Host"

For hosts that use NDMP access mode, such as network-attached storage devices, you have to configure the following additional attributes:

NDMP authorization type
NDMP password
TCP port number for use with NDMP

See Also:

Oracle Secure Backup Reference for a complete account of host attributes

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

Description of "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 new host to an administrative domain:

From the Home page, click the Configure tab.
Click Hosts in the Basic section to display the Hosts page.
Click Add to add a host.

The Oracle Secure Backup Web tool displays a form for entering configuration information about the host.
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.
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 that will be used 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)" for details.
In the Status list, select one of the following:
- 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.
In the Roles list, select the roles for this host: admin, client or mediaserver.
In the Access method field, select one of the following:
- OB
  
  Select this option for Windows, Linux and UNIX hosts that have Oracle Secure Backup installed.
- NDMP
  
  Select this option for devices that support Network Data Management Protocol (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" for a discussion of access modes.
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.
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
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.
In the Password list, select one of the following options:
- Use default password
  
  Select this option to use the default NDMP password.
- Use text password
  
  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.
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.
In the Protocol Version list, select 2, 3, 4, or as proposed by server. See "Oracle Secure Backup Host Access Modes" for details on NDMP protocol versions.
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.
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.
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 obtool chhost command or the Oracle Secure Backup Web tool.

See Also:

Oracle Secure Backup Reference for complete syntax and semantics for the obtool chhost command

Follow these steps to add the media server role to an administrative server using the Oracle Secure Backup Web tool:

On the Configure page of the Oracle Secure Backup Web tool, click Hosts.

The Configure: Hosts page appears.

Description of the illustration ob_win19.gif
Select the administrative server and click Edit.

The Configure: Hosts > host_name page appears.

Description of the illustration ob_win20.gif
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.

Description of the illustration ob_win21.gif

Adding Backup and Restore Environment Variables to an NDMP Host

Some Network Data Management Protocol (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:

In the field that appears next to the Backup environment vars or Restore environment vars field, enter a name-value pair.
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).
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 Preferred Network Interface (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:

From the Configure page, select the host you want to configure and click Edit.

The Configure Hosts > host_name page appears.
Click Preferred Network Interfaces.

The Configure Hosts > host_name > Preferred Network Interface page appears.
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 will use when communicating with the server.
Select one or more clients to use this IP address or DNS name from the Host list field.
Click Add.

The Oracle Secure Backup Web tool displays the PNI in the IP Address: Host List field.

To remove a PNI:

In the IP Address: Host List field, select the name of the PNI that you want to remove.
Click Remove.

Pinging a Host

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 Network Data Management Protocol (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:

From the Hosts page, select a host to ping.
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:

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.
Click Edit.

The Oracle Secure Backup Web tool displays a page with details for the host you selected.
Make any desired changes to the host properties.
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 new 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.

Updating is useful only for hosts running Oracle Secure Backup natively. Hosts accessed in Network Data Management Protocol (NDMP) mode, such as Network Attached Storage (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:

From the Host page, select the name of the host to be updated.
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
Preferred Network Interface (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:

From the Hosts page, select the name of the host that you want to remove.

Check Suppress communication with host to remove a host that is not connected to the network.
Click Remove.

Oracle Secure Backup prompts you to confirm the removal of the host.
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 Device Names
About Configuring Tape Drives and Libraries
Displaying the Devices Page
Configuring a Tape Library
Configuring a Tape Drive
Automatic Discovery of Tape Devices on NDMP Hosts
Adding a Tape Device Attachment
Multiple Attachments for SAN-Attached Tape Devices
Creating Attach Points for Solaris 10 Fibre Channel Devices
Pinging a Tape Device
Displaying Device Properties
Editing Device Properties

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.

About Configuring Tape Drives and Libraries

T his section explains how to configure a tape drive or tape library for use with Oracle Secure Backup. You can add a new 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 Network Data Management Protocol (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
A storage element range that can be used by the tape device, 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 obtool 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:

Disable any system software that scans and opens arbitrary Small Computer System Interface (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.
Configure tape libraries locally attached to your media servers, as described in "Configuring a Tape Library".

Configure tape drives locally attached to your media servers, as described in "Configuring a Tape Drive"
Configure tape devices that are network-accessible but are not locally attached to hosts. 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 the same as configuring a tape device attached locally to a media server.
Perform automatic device discovery to add every tape device attached to hosts that use NDMP access mode, such as Network Attached Storage (NAS) filers. This task is described in "Automatic Discovery of Tape Devices on NDMP Hosts".
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 tape 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:

From the Oracle Secure Backup Web tool Home page, click Manage.

The Manage page appears.
In the Devices and Media section, click Libraries.

The Manage: Libraries page appears.

Description of the illustration obins008.gif
Select the tape drive or tape library you want to inventory in the Devices table.
Select Inventory (Library | Drive) in the Library commands list.
Click Apply.

A new page appears.

Description of the illustration obins009.gif
Ensure that the Library list is set to the device you want to inventory.
Select the Force option.

Instead of reading from its cache, the tape library updates the inventory by physically scanning all tape library elements.
Click OK.

When the inventory is complete, the Manage: Libraries page reappears and displays a success message. If you want to see the results of the inventory, then 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.

Figure 5-2 Devices Page

Description of "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:

Disable any system software that scans and opens arbitrary Small Computer System Interface (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.
From the Home page, click the Configure tab.
Click Devices in the Basic section to display the Devices page.
Click Add to add a tape device.
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.
In the Type list, select library.
In the Status list, select one of the following 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 as a result of a failed operation.
In the Debug mode list, select yes or no. The default is yes.
In the World Wide Name field, enter a worldwide name for the tape device, if required.

See Also:
"Tape Device Names" for more information on World Wide Names
In the Barcode reader list, select one of the following 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.
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.
Set whether the tape library should use automatic cleaning.

See Also:
"Configuring Automatic Tape Cleaning for a Library"
In the Unload required list, select yes or no to specify whether or not an unload operation is required before moving a tape from a tape drive to a storage element.

The default value is no.
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 will then wait 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 ejected and manually removes them. This option can be useful when the tape library has no import/export slots.
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 non-zero, and if the number of writable volumes in that tape library has fallen below 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.
Click OK to save your changes.

See Also:

"Adding a Tape Device Attachment"

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:

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.
In the Clean using emptiest field, select one of the following 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.
Click OK to save your changes.

See Also:
"Adding a Tape Device Attachment"

Configuring a Tape Drive

This section explains how to configure a tape drive for use with Oracle Secure Backup. If the tape drive you wish to configure is attached to a tape library, then you must configure the tape library first, as described in "Configuring a Tape Library".

To configure tape drives for use with Oracle Secure Backup:

Disable any system software that scans and opens arbitrary Small Computer System Interface (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 tape drives, then unexpected behavior can result.
From the Home page, click the Configure tab.
Click Devices in the Basic section to display the Devices page.
Click Add to add a tape device.
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.
In the Type list, select tape.
In the Status list, select one of the following 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 as a result of a failed operation.
In the Debug mode list, select yes or no. The default is yes.
In the World Wide Name field, enter a worldwide name for the tape device, if required.

See Also:
"Tape Device Names" for more information on World Wide Names
If the tape drive is located in a tape library, then select the tape library by name from the Library list.
In the DTE field, enter the data transfer element (DTE).

Note:
This option is not available for standalone tape drives.
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.
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.
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" for more information on blocking factors and maximum blocking factors
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.
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.
Leave the Current tape field empty during initial configuration. Update the tape drive inventory after configuration, as described in "Updating a Tape Device Inventory".
In the Use list group, select one of the following options to configure the use list:
- Storage element range or list
  
  Select this option for a numerical range of storage element addresses. Enter a range in the field, for example, 1-20.
- All
  
  Select this option to specify all storage elements. For tape libraries with single tape drives, you can select this option to use all tapes. This is the default setting.
- None
  
  Select this option to indicate that no storage elements have yet been specified. If you select All or Storage element range or list, then this option is no longer visible.
Oracle Secure Backup allows all tapes to be accessed by all tape drives. The use list enables you to divide the use of the tapes for tape libraries containing multiple tape drives in which you are using more than one tape drive to perform backups. For example, you might want the tapes in the first half of the storage elements to be available to the first tape drive, and those in the second half to be available to the second tape drive.
Click OK to save your changes.

Automatic Discovery of Tape Devices on NDMP Hosts

Oracle Secure Backup can detect changes in tape device configuration for some types of hosts accessed by Network Data Management Protocol (NDMP), such as a filer, and it can automatically update the administrative domain device configuration based on this information,.

Oracle Secure Backup detects and acts on these kinds of changes:

Tape devices that were not previously part of the administrative domain are discovered. For each such tape device, Oracle Secure Backup creates a new device with an internally-assigned name and configures a device attachment for it.
If a previously configured tape device has a new attachment, then Oracle Secure Backup adds an attachment to the existing device.
If a previously configured tape device has lost an attachment, then Oracle Secure Backup deletes the attachment from the device.

Oracle Secure Backup detects tape devices that have multiple attachments by comparing the serial numbers for each tape device reported by the operating system. Oracle Secure Backup also determines whether any discovered tape device is accessible by its serial number. If the tape device is accessible by serial number, then Oracle Secure Backup configures each device attachment to reference the serial number instead of any logical name assigned by the operating system.

To discover tape devices attached to an NDMP host:

On the Hosts page select the name of the NDMP host in the list of hosts.

Click Discover.

If new or changed tape devices are discovered, then the Oracle Secure Backup Web tool displays a message similar to the following:

Info: beginning device discovery for host_name
host_name_c0t0l0  (new library)
WWN: [none]
new attach-point on host_name, rawname c0t0l0
host_name_c0t0l1  (new drive)
WWN: [none]
new attach-point on host_name, rawname c0t0l1
host_name_c0t0l2  (new drive)
WWN: [none]
new attach-point on host_name, rawname c0t0l2

If there are no new or changed tape devices to discover, then the Oracle Secure Backup Web tool displays a message similar to the following:

Info: beginning device discovery for host_name.
Info: no device configuration changes found for host_name

Click OK to return to the Devices page. The list of tape devices now includes the discovered tape devices.

Adding a Tape Device Attachment

Oracle Secure Backup distinguishes between a tape device and a device attachment. A device attachment is the means by which that tape device is connected to a host. Each tape device can have one or more attachments, where each attachment describes a data path to the tape device from a host in the administrative domain.

An attachment is defined by the identity of the host to which the tape device is attached, and one of the following that represents the tape device on the host:

Linux or UNIX device special file name
Windows device name
Network Attached Storage (NAS) device name

Note:

For some older NAS devices, Oracle Secure Backup requires additional information to complete the attachment definition.

Before configuring a device attachment, refer to the description of the mkdev command in Oracle Secure Backup Reference. The description of the aspec placeholder describes the syntax and naming conventions for device attachments.

To configure a device attachment:

After adding or editing a device, click Attachments.
Select a host in the Host list.
In the Raw device field, enter the raw device name. This is the operating system's name for the device, such as a Linux or UNIX device special file or a Windows device file. For example, a tape library name might be /dev/obl0 on Linux and //./obl0 on Windows.
This step is required only for hosts running certain Network Data Management Protocol (NDMP) version 2 and 3 servers, such as Network Appliance Data ONTAP 5.1 or 5.2.
1. In the ST device field, enter a device name.
2. In the ST target field, enter a target number.
3. In the SCSI device field, enter a Small Computer System Interface (SCSI) device.
4. In the ST controller field, enter a bus target number.
In the ST lun field, enter a SCSI logical unit number (SCSI LUN) for the device.
Click Add to add the attachment.

Pinging a Device Attachment

You can ping a device attachment to determine whether the tape device is accessible to Oracle Secure Backup using that attachment. Pinging device attachments is a good way to test whether you set up the attachment properly.

When you ping a device, Oracle Secure Backup performs the following steps:

Establishes a logical connection to the device
Inquires about the device's identity data with the SCSI INQUIRY command
Closes the connection

If the attachment is remote from the host running the Oracle Secure Backup Web tool (or obtool), then Oracle Secure Backup establishes an Network Data Management Protocol (NDMP) session with the remote media server to effect this function.

To ping an attachment from the Attachments page:

Select the attachment to ping in the host:raw device field.
Click Ping.

The Oracle Secure Backup Web tool opens a new window that describes the status of the attachment.
Click Close to exit the page.

Displaying Device Attachment Properties

You can display device attachment properties from the Devices page.

To display attachment properties:

Select the name of the tape device whose attachment properties you want to view.
Click Show Properties.

The Oracle Secure Backup Web tool displays device attachments and other properties for the tape device you selected.
Click Close to exit the page.

Multiple Attachments for SAN-Attached Tape Devices

A tape device attached to a Storage Area Network (SAN) often has more than one attachment, one for each host with local access to the tape device through its Fibre Channel interface. A tape device attached to a SAN is also distinguished by a World Wide Name (WWN), an internal identifier that uniquely names the tape device on the SAN. Systems such as a Network Appliance filer permit access to tape devices attached to a SAN through their WWN. Oracle Secure Backup includes a reference to the WWN in the device attachment's raw device name.

Tape devices such as certain Quantum and SpectraLogic tape libraries appear to be connected directly to an Ethernet LAN segment and accessed through Network Data Management Protocol (NDMP). In fact, Oracle Secure Backup views these devices as having two discrete components:

A host, which defines the IP address and which you configure through the Oracle Secure Backup Web tool Hosts page or the obtool mkhost command
A tape device, which has one attachment to the single-purpose host that serves as the front end for the tape device

Devices such as DinoStor TapeServer use a single host to service multiple tape devices.

For NDMP servers that run version 2, other data might be required to define Small Computer System Interface (SCSI) parameters needed to access the tape device. These parameters are sent in an NDMP message called NDMP_SCSI_SET_TARGET. Oracle Secure Backup NDMP servers do not use this data or this message.

See Also:

The description of the mkdev command aspec placeholder in Oracle Secure Backup Reference, which describes the syntax and naming conventions for device attachments

Creating Attach Points for Solaris 10 Fibre Channel Devices

Oracle Secure Backup supports the use of Fibre Channel-attached tape devices on media servers running Solaris 10. The Oracle Secure Backup install script and makedev utility cannot be used to create the needed links in the /dev directory to the device special files for such devices.

The Solaris sgen driver must be disabled before installing Oracle Secure Backup. If it is not disabled, then it might attach to your media changer or tape devices and prevent Oracle Secure Backup from attaching to them.

To disable the Solaris sgen driver:

Comment out all entries in /kernel/drv/sgen.conf.
Check the /etc/driver_aliases file for any sgen entries and remove them using the update_drv command. Suppose, for example, that /etc/driver_aliases contains the following entries:
```
sgen "scsa,08.bfcp"
sgen "scsc,08.bvhci"
```
To remove these entries you would run the following commands:
```
/usr/sbin/update_drv -d -i '"scsa,08.bfcp'" sgen
/usr/sbin/update_drv -d -i '"scsa,08.bvhci'" sgen
```
Restart your system to release the tape devices.

During installation, the Oracle Secure Backup driver automatically identifies Fibre Channel-attached devices by their World Wide Names. After installing the driver, you must determine the World Wide Name for each device, and then manually create symbolic links in the /dev directory that point to the actual attach points for the devices.

To create device special files for Solaris 10 tape devices:

Run the Oracle Secure Backup install script on your media server.

When the Oracle Secure Backup driver is installed, the install script prompts:

NOTE: The Oracle Secure Backup device driver has been successfully installed.
Would you like to configure (or reconfigure) any Oracle Secure Backup devices that are attached to dlsun1976 [no]?

Enter no.

After install completes, run the dmesg command and examine the output.

The Oracle Secure Backup driver adds messages to the log that contain the World Wide Names for the Fibre Channel-attached tape devices. The attach points for tape drives contain the string sgen. The attach points for tape libraries contain the string st.

For example, the following output contains the World Wide Names and corresponding attach points for a tape drive and a tape library:

Dec 12 17:12:53 storabck22 scsi: [ID 799468 kern.info] ob30 at fp0: name
w500308c162680e24,1, bus address 6119e8
Dec 12 17:12:53 storabck22 genunix: [ID 936769 kern.info] ob30 is
/pci@1f,4000/fibre-channel@2/fp@0,0/sgen@w500308c162680e24,1
Dec 12 17:12:53 storabck22 scsi: [ID 799468 kern.info] ob31 at fp0: name
w500308c162680e24,0, bus address 6119e8
Dec 12 17:12:53 storabck22 genunix: [ID 936769 kern.info] ob31 is
/pci@1f,4000/fibre-channel@2/fp@0,0/st@w500308c162680e24,0

For each device listed in the dmesg output, assign an Oracle Secure Backup logical unit number.
Create symbolic links in the /dev directory that reference the attach points.

The name for the symbolic link should be /dev/obtn for tape drives and /dev/obln for tape libraries, where n is the Oracle Secure Backup logical unit number you assigned to the device in step 3.

For example, assume that you assign the devices listed in the output of step 2 the Oracle Secure Backup logical unit number 0. The resulting device names are /dev/obl0 for the tape library, and /dev/obt0 for the tape drive. The following commands create the required symbolic links in /dev:
```
ln –s /devices/pci@1f,4000/fibre-channel@2/fp@0,0/sgen@w500308c162680e24,1:fp0 /dev/obl0
ln –s /devices/pci@1f,4000/fibre-channel@2/fp@0,0/st@w500308c162680e24,0:fp0 /dev/obt0
```
Use the mkdev command in obtool or the Oracle Secure Backup Web tool to add these devices to your administrative domain.

Pinging a Tape Device

To determine whether a tape device is reachable by Oracle Secure Backup through any available attachment, ping the tape device. You should ping each tape device after it is configured or discovered, to verify that it is configured correctly.

To ping a tape device:

In the Devices page, select a tape device to ping.
Click the Ping button.

The Oracle Secure Backup Web tool displays the status of the operation.

Note:

Pinging a tape library causes each service member tape drive in the tape library to be pinged as well.

Displaying Device Properties

The Oracle Secure Backup Web tool can display tape device properties including:

Whether a tape device is in service
Which host or hosts the tape device is connected to
The tape device type

If a tape device is in service, then it can be used by Oracle Secure Backup; if it is not in service, then it cannot be used by Oracle Secure Backup. When a tape device is taken out of service, no more backups are dispatched to it.

To display tape device properties:

In the Device page, select the name of the tape device whose properties you want to display.
Click Show Properties.

The Oracle Secure Backup Web tool displays a page with the properties for the tape device you selected.

Editing Device Properties

If you make an error during installation, such as not configuring every attachment for a tape device or incorrectly configuring its properties, then you can edit its properties.

To edit the properties for an existing tape device:

From the Devices page, select the name of the tape device.
Click Edit.

The Oracle Secure Backup Web tool displays a page with details for the tape device you selected.
Make any required changes.
Click OK to save your changes.