Creating Device Special Files on Solaris and Linux

Device special files are required before devices can be configured for use with Oracle Secure Backup. Specifically, device special files are links that will be referenced as attachments when devices are configured for use with Oracle Secure Backup.

After the device special files are created for devices, you can use the mkdev command in obtool, the Oracle Secure Backup Web tool, or the Oracle Secure Backup interface in Oracle Enterprise Manager to configure devices for use with Oracle Secure Backup.

This section assumes that you have already performed the following tasks:

Established your administrative domain so that media servers can be associated with their attached devices. See "Configuring an Administrative Domain on Linux and UNIX with obtool".
Determined the operating system-specific SCSI (or Fibre Channel) device data required for device configuration. See "Determining SCSI Device Parameters on Linux and UNIX".

You can create the device special files either by using the installob script or the makedev tool.

Follow the instructions in the appropriate section:

Creating Device Special Files with makedev
Creating Device Special Files with installob

Note:

It is generally most convenient to use installob to configure all SCSI devices immediately after the installation process.

Creating Device Special Files with makedev

The makedev tool is used to create device special files for a single media device that Oracle Secure Backup uses to access the device.

The makedev tool provides an alternative to creating device special files with installob. makedev does not require you to run the installob script again. It handles only device special file creation and configuration, and does not relate to other installation and configuration tasks. makedev can be used on media servers before they are added to the administrative domain. makedev only creates device special files for a single device at a time, so if you have multiple devices to configure, consider using installob.

Creating Device Special Files with installob

You can create device special files using the installob installation script. The advantages of doing so include:

You can perform this task immediately after the software installation process, if you have collected the SCSI device parameters for your platform as described in "Determining SCSI Device Parameters on Linux and UNIX".
You can enter SCSI parameters for all of your devices during one session. Using makedev requires that you perform this task separately for each device.

Follow the instructions appropriate for your operating system:

Configuring SCSI Devices on Solaris with installob
Configuring SCSI Devices on Linux with installob

Configuring SCSI Devices on Solaris with installob

Note:

Although the following example describes SCSI libraries and tape drives, the same procedures apply to Fibre Channel devices.

To create device special files with installob on Solaris:

Start the installob script. From a shell prompt, change your working directory to the Oracle Secure Backup home, and start installob in interactive mode. For example:

# cd /usr/local/oracle/backup
# install/installob
Welcome to installob, Oracle Secure Backup's UNIX installation program.
.
.
.
You can choose to install Oracle Secure Backup in one of two ways:
    (a) interactively, by answering questions asked by this program, or
    (b) in batch mode, by preparing a network description file
 
Which installation method would you like to use (a or b) [a]? a

Enter a to run the script in interactive mode.

installob now prompts you about whether to reinstall the software. For example:
```
Oracle Secure Backup is already installed on this machine (dlsun1976).
Would you like to re-install it here [no]?
 
```
Enter no to leave the current software installation intact and move on to device configuration.
installob now prompts for whether to configure tape libraries and tape drives on this host. For example:
```
Would you like to configure (or reconfigure) any Oracle Secure Backup devices that
are attached to dlsun1976 [no]? 
```
Enter yes at this prompt to configure tape drives or libraries.
installob now prompts for the number of tape libraries attached to your host. For example:
```
How many Oracle Secure Backup SCSI tape libraries are attached to dlsun1976 [1]?
```
Enter the number of tape libraries to configure (or press Enter to accept the default). If there are no tape libraries, enter 0.
If you have tape libraries to configure, installob now prompts you for information about each library. installob displays the following output:
```
Please describe each tape library by answering the following questions.
```
For each library, enter the device information you collected in "Determining SCSI Device Parameters on Solaris".

For this example, the single tape library attached to dlsun1976 is assigned Oracle Secure Backup logical unit number 0, and has SCSI bus name-instance glm1, target ID 1, and logical unit number 0.

Note:
When entering these values, do not confuse the Oracle Secure Backup logical unit number with the SCSI LUN.

The installob program displays the following output:
```
Oracle Secure Backup logical unit number [0]:
```
If the default is correct, then press Enter. Otherwise, enter the desired Oracle Secure Backup logical unit number for this device.
```
SCSI bus name-instance  [glm1]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI bus name-instance for this device.

The installob program displays the following output:
```
SCSI target ID [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI target ID for this device.

The installob program displays the following output:
```
SCSI lun 0-7 [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI LUN for this device.

The installob program displays the following output:
```
Is the information you entered correct [yes]?
```
If the information is not correct, enter no. installob will prompt for the parameters for this library again. Otherwise, enter yes to continue to the next library.
Once you have entered parameters for all tape libraries, installob prompts for information about tape drives. For example:
```
Is dlsun1976 connected to any SCSI tape drives that you'd like to use with
Oracle Secure Backup [no]?
```
If there are tape drives to configure, enter yes. Otherwise, enter no.

If you entered yes, then installob prompts for the number of tape drives. For example:
```
How many Oracle Secure Backup SCSI tape drives are attached to dlsun1976 [1]?
```
For this example, there is one tape drive attached, so enter 1 and press Enter.
installob now displays the following output:
```
Please describe each tape drive by answering the following questions.
```
installob now prompts you for the parameters for each tape drive. Enter the device information you collected in"Determining SCSI Device Parameters on Solaris".

For this example, the single tape drive attached to dlsun1976 is assigned Oracle Secure Backup logical unit number 0, and has SCSI bus name-instance glm1, SCSI target ID 0, and SCSI logical unit number 0.

installob now displays the following output:
```
Oracle Secure Backup logical unit number [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct Oracle Secure Backup logical unit number for this device.

The installob program displays the following output:
```
SCSI bus name-instance  [glm1]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI bus name-instance value for this device.

The installob program displays the following output:
```
SCSI target ID [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI target ID for this device.

The installob program displays the following output:
```
SCSI lun 0-7 [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI LUN for this device.

The installob program displays the following output:
```
Is the information you entered correct [yes]?
```
If the information is not correct, enter no. installob will prompt for the parameters for this drive again. Otherwise, enter yes to continue to the next drive.

Once parameters are entered for all tape libraries and drives, installob configures the device drivers for the devices and creates the device special files. It displays the following output:

Beginning device driver configuration and device special file creation. 
This will likely take between one and five minutes.

installob generates descriptive output for each device it configures during this process. For example:

NOTE: table for devlinks...
   type=ddi_pseudo;name=ob;addr=0,0;minor=pci1000,f1    obt0
/dev/obt0 created
NOTE: table for devlinks...
   type=ddi_pseudo;name=ob;addr=0,1;minor=pci1000,f1    obl0
/dev/obl0 created
---------------------------------------------------------------------------

At the end of the process, device special files have been created for two devices: /dev/obt0 (the tape drive) and /dev/obl0 (the library).

When the process is complete, installob generates the following output:

NOTE: You must configure the new devices via the Web interface or via
      the command line using the obtool 'mkdev' command.

---------------------------------------------------------------------------

Note:

Note that the name of the tape library device special file /dev/obl0 contains a lower-case letter L, not a number 1.

installob now displays the following prompt:

Would you like to install Oracle Secure Backup on another machine [yes]?

Enter no. The installob script then displays the installation summary described in "installob Step 9: Final Installation Summary" and exits

Note:

As stated in the output of installob, you must complete configuration of the devices as part of the administrative domain before they can be used. These tasks cannot be performed until the media server and its devices have been added to the administrative domain.

The remaining tasks are described in the following sections:

Configuring SCSI Devices on Linux with installob

Note:

Although the following example describes SCSI libraries and tape drives, the same procedures apply to Fibre Channel devices.

To create device special files with installob on Linux:

Start the installob script. From a shell prompt, change your working directory to the Oracle Secure Backup home, and start installob in interactive mode. For example:

# cd /usr/local/oracle/backup
# install/installob
Welcome to installob, Oracle Secure Backup's UNIX installation program.
.
.
.
You can choose to install Oracle Secure Backup in one of two ways:
    (a) interactively, by answering questions asked by this program, or
    (b) in batch mode, by preparing a network description file
 
Which installation method would you like to use (a or b) [a]? a

Enter a to run the script in interactive mode.

installob now prompts you about whether to reinstall the software. For example:
```
Oracle Secure Backup is already installed on this machine (storabck05).
Would you like to re-install it here [no]?
 
```
Enter no to leave the current software installation intact and move on to device configuration.
installob now prompts for whether to configure tape libraries and tape drives on this host. For example:
```
Would you like to configure (or reconfigure) any Oracle Secure Backup devices that
are attached to storabck05 [no]? 
```
Enter yes at this prompt to configure tape drives or libraries.
installob now prompts for the number of tape libraries attached to your host. For example:
```
How many Oracle Secure Backup SCSI tape libraries are attached to storabck05 [1]?
```
Enter the number of tape libraries to configure (or press Enter to accept the default). If there are no tape libraries, enter 0.
If you have tape libraries to configure, installob now prompts you for information about each library. installob displays the following output:
```
Please describe each tape library by answering the following questions.
```
For each library, enter the device information you collected in "Determining SCSI Device Parameters on Linux".

For this example, the single tape library attached to storabck05 is assigned Oracle Secure Backup logical unit number 0, and has host SCSI adapter number 0, SCSI bus address 0, SCSI target ID 2, and SCSI logical unit number 0.

Note:
When entering these values, do not confuse the Oracle Secure Backup logical unit number with the SCSI LUN.

The installob program displays the following output:
```
Oracle Secure Backup logical unit number [0]:
```
If the default is correct, then press Enter. Otherwise, enter the desired Oracle Secure Backup logical unit number for this device. For this example, enter 0.

installob now displays the following output:
```
Host SCSI adapter number [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct host SCSI adapter number for this device. For this example, enter 0.
```
SCSI bus address [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI bus address for this device. For this example, enter 0.

The installob program displays the following output:
```
SCSI target ID [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI target ID for this device. For this example, enter 2.

The installob program displays the following output:
```
SCSI lun 0-7 [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI LUN for this device. For this example, enter 0.

The installob program displays the following output:
```
Is the information you entered correct [yes]?
```
If the information is not correct, enter no. installob will prompt for the parameters for this library again. Otherwise, enter yes to continue to the next library.
Once you have entered parameters for all tape libraries, installob prompts for information about tape drives. For example:
```
Is storabck05 connected to any SCSI tape drives that you'd like to use with
Oracle Secure Backup [no]?
```
If there are tape drives to configure, enter yes. Otherwise, enter no.

If you entered yes, then installob prompts for the number of tape drives. For example:
```
How many Oracle Secure Backup SCSI tape drives are attached to storabck05 [1]?
```
For this example, there is one tape drive attached, so enter 1 and press Enter.
installob now displays the following output:
```
Please describe each tape drive by answering the following questions.
```
installob now prompts you for the parameters for each tape drive. Enter the device information you collected in"Determining SCSI Device Parameters on Linux".

For this example, the single tape drive attached to storabck05 is assigned Oracle Secure Backup logical unit number 0, and has host SCSI adapter number 0, SCSI bus address 0, SCSI target ID 4, and SCSI logical unit number 0.

For example:
```
Oracle Secure Backup logical unit number [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct Oracle Secure Backup logical unit number for this device. For this example, enter 0.

installob now displays the following output:
```
Host SCSI adapter number [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct host SCSI adapter number for this device. For this example, enter 0.
```
SCSI bus address [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI bus address for this device. For this example, enter 0.

The installob program displays the following output:
```
SCSI target ID [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI target ID for this device. For this example, enter 4.

The installob program displays the following output:
```
SCSI lun 0-7 [0]:
```
If the default is correct, press Enter. Otherwise, enter the correct SCSI LUN for this device. For this example, enter 0.

The installob program displays the following output:
```
Is the information you entered correct [yes]?
```
If the information is not correct, enter no. installob will prompt for the parameters for this drive again. Otherwise, enter yes to continue to the next drive.

Once parameters are entered for all tape libraries and drives, installob configures the device drivers for the devices and creates the device special files. It displays the following output:

Beginning device driver configuration and device special file creation. 
This will likely take between one and five minutes.

installob generates descriptive output for each device it configures during this process. For example:

-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -
 
Beginning device driver configuration and device special file creation.
 
NOTE: table for devlinks...
   type=ddi_pseudo;name=ob;addr=0,0;minor=glm1  obt0
/dev/obt0 created
NOTE: table for devlinks...
   type=ddi_pseudo;name=ob;addr=1,0;minor=glm1  obl0
/dev/obl0 created
 
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -

At the end of the process, device special files have been created for two devices: /dev/obt0 (the tape drive) and /dev/obl0 (the library).

When the process is complete, installob generates the following output:

NOTE: You must configure the new devices via the Web interface or via
      the command line using the obtool 'mkdev' command.

Note:

Note that the name of the tape library device special file /dev/obl0 contains a lower-case letter L, not a number 1.

installob now displays the following prompt:

Would you like to install Oracle Secure Backup on another machine [yes]?

Enter no. The installob script then displays the installation summary described in "installob Step 9: Final Installation Summary" and exits.

Note:

The remaining tasks are described in the following sections: