| Oracle® Secure Backup Installation Guide Release 10.1 Part Number B14235-02 |
|
|
View PDF |
| Oracle® Secure Backup Installation Guide Release 10.1 Part Number B14235-02 |
|
|
View PDF |
As part of installing Oracle Secure Backup and configuring your administrative domain, you will need to configure libraries and tape drives for use with Oracle Secure Backup. Collecting this information should be considered part of planning your administrative domain.
Oracle Secure Backup supports both SCSI and Fibre Channel devices for Linux and UNIX. The process of collecting the required parameters is the same for both device types.
To prepare for configuring each SCSI device, collect the device parameters required for your platform. On Linux this includes:
The host bus adapter number for the SCSI adapter
The SCSI bus address
The SCSI target ID
The SCSI logical unit number (or SCSI LUN)
On Solaris this includes:
The SCSI bus name-instance
The SCSI target ID
The SCSI logical unit number (or SCSI LUN)
Also assign each tape library and each tape device an Oracle Secure Backup logical unit number, as described in "Assigning Oracle Secure Backup Logical Unit Numbers to Devices".
|
Note: Do not confuse the SCSI logical unit number with the Oracle Secure Backup logical unit number. The Oracle Secure Backup logical unit number is a number you assign that is used in generating device special file names. |
The following sections describe how to probe different operating systems for the required SCSI parameters.
To obtain device information on Linux, use the cat command to view the contents of /proc/scsi/scsi. For example:
# cat /proc/scsi/scsi
Example 5-1 shows sample output for a host called storabck05 with two attached devices.
Example 5-1 Sample /proc/scsi/scsi Contents
Attached devices: Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: IBM Model: ULTRIUM-TD2 Rev: 4772 Type: Sequential-Access ANSI SCSI revision: 03 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: ADIC Model: Scalar 24 Rev: 237A Type: Medium Changer ANSI SCSI revision: 02
Devices of type Sequential-Access, such as the first device in the list, are tape drives. Devices of type Medium Changer, such as the second device, are tape libraries.
For each device, the information needed is found in the line that reads:
Host: scsi0 Channel: 00 Id: 02 Lun: 00
The output can be interpreted as follows:
The host bus adapter number is the numeric part of the value scsin. For example, for both devices in this output the host bus adapter number is 0.
The value for Channel is the SCSI bus address. For example, in this output the SCSI bus address is 0.
The value for Id is the target ID. For example, in this output the ID of the tape drive is 2, and the ID of the tape library is 4.
The value for Lun is the SCSI LUN. For example, in this output the SCSI LUN of both devices is 0.
By convention, the tape library and tape drive can each be assigned 0 as the Oracle Secure Backup logical unit number.
Based on the output shown in Example 5-1, Table 5-1 summarizes the device information for storabck05.
To determine the SCSI device parameter information on Solaris, there are two major tasks required:
To identify the SCSI target ID and SCSI LUN for each device, you must probe the SCSI bus of your system for attached devices using commands at the console in the Open Boot PROM. This task is described in "Probing SCSI Target ID and LUN for Media Devices From Solaris Open Boot PROM".
|
Note: Accessing the Open Boot PROM requires shutting down and rebooting the operating system. |
To determine the SCSI bus name-instance for each device, you must install the Oracle Secure Backup Solaris device driver, and then view the devices that were recognized by the driver and associate them with the device information gathered in the first step.
|
Note: Installing the Oracle Secure Backup device driver is performed after loading Oracle Secure Backup withsetup, as described in "Loading Oracle Secure Backup Software on Solaris or Linux Using setup Script", but prior to installing Oracle Secure Backup as described in "Installing Oracle Secure Backup on Linux or UNIX with installob". |
This task is described in "Viewing SCSI Bus Name-Instance Parameter Values in Solaris".
To view SCSI target ID and SCSI LUN parameters for media devices from the Solaris Open Boot PROM:
Log into the media server as root.
Bring the host to run level 0. For example:
# init 0
The system shuts down and eventually the Open Boot PROM ok prompt is displayed on the console.
At the ok prompt, set the Open Boot auto-boot? variable to false. For example:
ok setenv auto-boot? false auto-boot? = false ok
At the ok prompt, run the Open Boot reset-all command. For example:
ok reset-all
The system resets and eventually returns to an ok prompt again.
At the ok prompt, run the Open Boot probe-scsi-all command to display the SCSI parameters for all devices attached to this host. For example:
ok probe-scsi-all
Find the information in the output that corresponds to your SCSI devices. For example, this excerpt from the output for dlsun1976 includes the following information for the tape library and drive:
/pci@1f,4000/scsi@3,1
Target 0
Unit 0 Removable Tape EXABYTE EXB-85058SQANXR1
Target 1
Unit 0 Removable Device type 8 EXABYTE EXB-10e 1.8
The output can be interpreted as follows:
The device tree path for the SCSI bus to which both devices are attached is /pci@1f,4000/scsi@3,1. Make a note of this value.
|
Note: This value is not used directly in Oracle Secure Backup device configuration, but is needed when determining the SCSI bus name-instance parameter for each device, using the process in "Viewing SCSI Bus Name-Instance Parameter Values in Solaris". |
The value for Target is the target ID. For example, in this output the target ID of the tape drive is 0, and the target ID of the tape library is 1.
The value for Unit is the SCSI LUN. For example, in this output the SCSI LUN of both devices is 0.
For this example, assign each device the Oracle Secure Backup logical unit number 0.
Record the discovered parameters and the assigned Oracle Secure Backup logical unit number for each device.
To reboot the host into Solaris, enter the following commands at the ok prompt:
ok setenv auto-boot? true ok reset-all
To determine the SCSI Bus name-instance parameter to use for each device in Oracle Secure Backup:
Log into your media server as root.
Change directory to the install subdirectory under the Oracle Secure Backup home. For example:
# cd /usr/local/oracle/backup/install
Run the installdriver script to install the Oracle Secure Backup driver. For example:
# installdriver NOTE: /usr/local/oracle/backup/.drv.solaris64/ob copied to /usr/kernel/drv/ob NOTE: /usr/local/oracle/backup/.drv.solaris64/ob.conf copied to /usr/kernel/drv/ob.conf NOTE: /usr/local/oracle/backup/.drv.solaris64/ob64 copied to /usr/kernel/drv/sparcv9/ob NOTE: The Oracle Secure Backup device driver has been successfully installed.
Once installed, the Oracle Secure Backup driver is associated with the media devices that it can control on this media server.
Run the following command to view devices associated with the Oracle Secure Backup driver:
# du -a /devices|grep ob|cut -f2 /devices/pci@1f,4000/scsi@3,1/ob@0,0:glm1 /devices/pci@1f,4000/scsi@3,1/ob@1,0:glm1
The output contains the needed device information.
Parse the output from Step 4 using information from the output of probing the SCSI bus in "Probing SCSI Target ID and LUN for Media Devices From Solaris Open Boot PROM". For example, consider the line of output that reads:
/devices/pci@1f,4000/scsi@3,1/ob@1,0:glm1
To identify the SCSI bus used for each device in the du output, match the device tree paths in the probe-scsi-all output to the device tree paths in the output from Step 4 for each device.
For example, in this case the bus used for both media devices is identified in the probe-scsi-all output as /pci@1f,4000/scsi@3,1, and in the du output as /devices/pci@1f,4000/scsi@3,1.
The ob@ in the path from the du output indicates that the device is controlled by the Oracle Secure Backup driver.
The two numbers (in this case, 1,0) following the ob@ are the SCSI target ID and SCSI LUN for each device. For this example, the SCSI target ID is 1 and the SCSI LUN is 0. These values correspond to the Exabyte tape library on dlsun1976, as identified in "Probing SCSI Target ID and LUN for Media Devices From Solaris Open Boot PROM".
The value following the colon (:) is the needed SCSI bus name-instance value for this device. For this example, the value is glm1.
For host dlsun1976, parsing both lines of output from Step 4 leads to the final SCSI parameters shown in Table 5-2.
