Oracle Secure Backup uses default values for most configuration parameters that are required during the installation process. This includes parameters such as the identify certificate key size, minimum length for user passwords, and so on. In most cases, the default values are sufficient. However, you can provide new values for the parameters by configuring advanced settings during the installation.

To configure advanced settings, the setup script displays a numbered list containing the parameters that can be configured. To modify a particular parameter, enter the number adjacent to that parameter and provide the required values. For example, to modify the minimum length for user passwords, type 2. The default setting is displayed in brackets beside the option name. Enter the new minimum password length that you wish to use.

Only one advanced parameter can be modified at a time. If you want to make multiple changes, you need to enter them separately.

Configuring a Linux host as an Oracle Secure Backup media server requires that the SCSI Generic driver be installed on that host. The driver enables Oracle Secure Backup to interact with tape and library devices. The host must be configured to automatically reload the driver after a restart. It is also recommended that persistent bindings be configured. By using persistent bindings, the Host Bus Adapter pairs the SCSI targets and LUNs for each device with their WWNs, thus preventing the attach points from being shuffled among devices during a reboot. Without persistent bindings, devices can become inaccessible by Oracle Secure Backup until their attach points are updated to reflect their new values. Please consult your system administrator or operating system documentation for information on how to configure persistent bindings on your Linux media server systems.

To identify the /dev/sg that corresponds to the specific tape device you are interested in, obtain the sg_map output by executing the following Linux command:

# sg_map -i -x

/dev/sg0 5 0 0 0 8 STK SL3000 4.00

/dev/sg1 5 0 0 1 8 STK SL3000 4.00

/dev/sg2 5 0 1 0 8 STK SL500 1466

/dev/sg3 5 0 3 0 1 /dev/nst2 HP Ultrium 5-SCSI I11V

/dev/sg4 5 0 4 0 1 /dev/nst3 STK T10000C 1.57

/dev/sg5 5 0 5 0 1 /dev/nst4 HP Ultrium 5-SCSI I3AS

/dev/sg6 5 0 6 0 1 /dev/nst5 HP Ultrium 5-SCSI I3AS

/dev/sg7 5 0 7 0 1 /dev/nst6 STK T10000C 1.57

Once these attach points are present on the system, Oracle Secure Backup's discoverdev will be able to use them in creating devices.

Here is an example showing the use of discoverdev to create devices:

ob> lsh
storabck06       admin,mediaserver,client          (via OB)   in service
 
ob> discoverdev -ic -h storabck06
   Device-Type   Device-Model            Serial-Number        Attachpoint
   Library       STK     SL3000           464970G+1333SY1401   storabck06:/dev/sg0
create device object storabck06_lib_1? (a, n, q, y, ?) [y]:
   Tape          HP      Ultrium 5-SCSI  HU1328WGF6           storabck06:/dev/sg3
create device object storabck06_tape_1? (a, n, q, y, ?) [y]:
   Tape          STK     T10000C HU1327WEYJ           storabck06:/dev/sg4
create device object storabck06_tape_2? (a, n, q, y, ?) [y]:
Checking each library to associate discovered drive(s) with DTE...
    Assigning DTE 1 in library storabck06_lib_1 for drive storabck06_tape_1 with serial number: HU1328WGF6
    Assigning DTE 2 in library storabck06_lib_1 for drive storabck06_tape_2 with serial number: HU1327WEYJ
ob>
 
ob> lsd -l
storabck06_lib_1:
    Device type:            library
    Model:                  STK     SL3000
    Serial number:          464970G+1333SY1401
    In service:             yes
    Debug mode:             no
    Barcode reader:         default (hardware-selected)
    Barcodes required:      no
    Auto clean:             no
    Clean interval:         (not set)
    Clean using emptiest:   no
    Ejection type:          ??
    Min writable volumes:   0
    UUID:                   9a9c2982-1b34-1032-9c3e-aad50196aa4f
    Attachment 1:
        Host:               storabck06
        Raw device:         /dev/sg0
 
storabck06_tape_1:
    Device type:            tape
    Model:                  HP      Ultrium 5-SCSI
    Serial number:          HU1328WGF6
    In service:             yes
    Automount:              yes
    Position interval:      [undetermined]
    Debug mode:             no
    Blocking factor:        (default)
    Max blocking factor:    (default)
    UUID:                   9aa59b5c-1b34-1032-9c3e-aad50196aa4f
    Attachment 1:
        Host:               storabck06
        Raw device:         /dev/sg3
 
storabck06_tape_2:
    Device type:            tape
    Model:                  STK     T10000C 
    Serial number:          HU1327WEYJ
    In service:             yes
    Automount:              yes
    Position interval:      [undetermined]
    Debug mode:             no
    Blocking factor:        (default)
    Max blocking factor:    (default)
    UUID:                   9aa59f4e-1b34-1032-9c3e-aad50196aa4f
    Attachment 1:
        Host:               storabck06
        Raw device:         /dev/sg4

You must enable the Solaris sgen driver for changer (library) and sequential (tape) devices before a host can access SCSI & Fibre Channel attached devices and be configured as an Oracle Secure Backup media server.

To enable sgen drivers

1. If you have sgen.conf file in /kernel/drv/ then, copy /kernel/drv/sgen.conf to /etc/driver/drv/sgen.conf by issuing the following:

   cp /kernel/drv/sgen.conf /etc/driver/drv/sgen.conf

2. Enable sequential (01) and changer (01) devices by adding the following line to the /kernel/drv/sgen.conf file:

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

   Note:

   If device-type-config-list is already defined for other devices, add sequential and changer to the existing list in the sgen.conf file.

3. Verify that an entry for an sgen file exists in the /etc/minor_perm. For example:

   sgen * 0600 root sys

4. Verify that an entry for an sgen file exists in the /etc/name_to_major. For example:

   sgen 151

5. Remove any old sgen drivers by using the following commands:

   rm -r /dev/scsi/changer

   rm -r /dev/scsi/sequential

6. In the /kernel/drv/sgen.conf file, add a line for each device’s target and LUN parameters.

   You can obtain these details from the output of the prtconf -Dv and dmseg commands. An example is shown here.

   name="sgen" class="scsi" target=0 lun=0; name="sgen" class="scsi" target=1 lun=0; name="sgen" class="scsi" target=2 lun=0; name="sgen" class="scsi" target=3 lun=0;
   .....
   name="sgen" class="scsi" target=13 lun=0; name="sgen" class="scsi" target=14 lun=0; name="sgen" class="scsi" target=15 lun=0;

7. Run the following to remove any existing active sgen device configuration.

    rem_drv sgen
    rem_drv st
    rem_drv sas

8. Use the following command, typed all on one line, to configure the sgen drivers:

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

9. To check whether the sgen attachments are created, run the following commands as the root user:

   # ls -latr /dev/scsi/seq*
   total 10
   drwxr-xr-x 5 root sys 512 Jan 29 17:01 ..
   lrwxrwxrwx 1 root sys 57 Jan 29 17:01 c1t1d0 -> ../../../devices/pci@1f,4000/scsi@3,1/sgen@1,0:sequential
   lrwxrwxrwx 1 root sys 57 Jan 29 17:01 c1t2d0 -> ../../../devices/pci@1f,4000/scsi@3,1/sgen@2,0:sequential
   lrwxrwxrwx 1 root sys 57 Jan 29 17:01 c1t5d0 -> ../../../devices/pci@1f,4000/scsi@3,1/sgen@5,0:sequential
   drwxr-xr-x 2 root sys 512 Jan 29 17:01 .
    
   # ls -latr /dev/scsi/cha*
   total 8
   lrwxrwxrwx 1 root sys 54 Jan 29 17:01 c1t0d0 -> ../../../devices/pci@1f,4000/scsi@3,1/sgen@0,0:changer
   drwxr-xr-x 5 root sys 512 Jan 29 17:01 ..
   lrwxrwxrwx 1 root sys 54 Jan 29 17:01 c1t4d0 -> ../../../devices/pci@1f,4000/scsi@3,1/sgen@4,0:changer
   drwxr-xr-x 2 root sys 512 Jan 29 17:01 .

10. If you do not find the sgen driver entries, reboot your system using the following commands:

    # touch /reconfigure

    # reboot

11. Create devices in Solaris using the sgen drivers by running discoverdev:

    ob> lsh
    storabck18       admin,mediaserver,client          (via OB)   in service
    ob> discoverdev -ic -h storabck18
       Device-Type   Device-Model            Serial-Number        Attachpoint
       Library       STK     SL150           464970G+1333SY1401   storabck18:/dev/scsi/changer/c2t500104F000D14F89d1
    create device object storabck18_lib_1? (a, n, q, y, ?) [y]: y
       Tape          HP      Ultrium 5-SCSI  HU1328WGF6           storabck18:/dev/scsi/sequential/c2t500104F000D14F89d0
    create device object storabck18_tape_1? (a, n, q, y, ?) [y]: y
       Tape          HP      Ultrium 5-SCSI  HU1327WEYJ           storabck18:/dev/scsi/sequential/c2t500104F000D14F8Cd0
    create device object storabck18_tape_2? (a, n, q, y, ?) [y]: y
     
    Checking each library to associate discovered drive(s) with DTE...
        Assigning DTE 1 in library storabck18_lib_1 for drive storabck18_tape_1 with serial number: HU1328WGF6
        Assigning DTE 2 in library storabck18_lib_1 for drive storabck18_tape_2 with serial number: HU1327WEYJ
    ob>
     
    ob> lsd -l
    storabck18_lib_1:
        Device type:            library
        Model:                  STK     SL150
        Serial number:          464970G+1333SY1401
        In service:             yes
        Debug mode:             no
        Barcode reader:         default (hardware-selected)
        Barcodes required:      no
        Auto clean:             no
        Clean interval:         (not set)
        Clean using emptiest:   no
        Ejection type:          ??
        Min writable volumes:   0
        UUID:                   9a9c2982-1b34-1032-9c3e-aad50196aa4f
        Attachment 1:
            Host:               storabck18
            Raw device:         /dev/scsi/changer/c2t500104F000D14F89d1
     
    storabck18_tape_1:
        Device type:            tape
        Model:                  HP      Ultrium 5-SCSI
        Serial number:          HU1328WGF6
        In service:             yes
        Automount:              yes
        Position interval:      [undetermined]
        Debug mode:             no
        Blocking factor:        (default)
        Max blocking factor:    (default)
        UUID:                   9aa59b5c-1b34-1032-9c3e-aad50196aa4f
        Attachment 1:
            Host:               storabck18
            Raw device:         /dev/scsi/sequential/c2t500104F000D14F89d0
     
    storabck18_tape_2:
        Device type:            tape
        Model:                  HP      Ultrium 5-SCSI
        Serial number:          HU1327WEYJ
        In service:             yes
        Automount:              yes
        Position interval:      [undetermined]
        Debug mode:             no
        Blocking factor:        (default)
        Max blocking factor:    (default)
        UUID:                   9aa59f4e-1b34-1032-9c3e-aad50196aa4f
        Attachment 1:
            Host:               storabck18
            Raw device:         /dev/scsi/sequential/c2t500104F000D14F8Cd0
    ob>

Oracle Secure Backup no longer requires that AIX attach points be pre-configured using makedev before obtool discoverdev can find and utilize them.

To configure devices on AIX:

1. Complete the steps in

2. Add the mediaserver role to the host

   ob> chhost --addrole mediaserver osblp01

3. Run discoverdev:

   ob> discoverdev -ic -h osblp01
      Device-Type   Device-Model            Serial-Number        Attachpoint
      Library       STK     SL150           464970G+1333SY1401   osblp01:/dev/obl0
   create device object osblp01_lib_1? (a, n, q, y, ?) [y]: y
      Tape          HP      Ultrium 5-SCSI  HU1327WEYJ           osblp01:/dev/obt0
   create device object osblp01_tape_1? (a, n, q, y, ?) [y]: y
      Tape          HP      Ultrium 5-SCSI  HU1328WGF6           osblp01:/dev/obt1
   create device object osblp01_tape_2? (a, n, q, y, ?) [y]: y
    
   Checking each library to associate discovered drive(s) with DTE...
       Assigning DTE 1 in library osblp01_lib_1 for drive osblp01_tape_2 with serial number: HU1328WGF6
       Assigning DTE 2 in library osblp01_lib_1 for drive osblp01_tape_1 with serial number: HU1327WEYJ
    
   ob> lsd -l
   osblp01_lib_1:
       Device type:            library
       Model:                  STK     SL150
       Serial number:          464970G+1333SY1401
       In service:             no
       Debug mode:             no
       Barcode reader:         default (hardware-selected)
       Barcodes required:      no
       Auto clean:             no
       Clean interval:         (not set)
       Clean using emptiest:   no
       Ejection type:          ??
       Min writable volumes:   0
       UUID:                   eed24e34-15e2-1032-bdb8-000000000000
       Attachment 1:
           Host:               osblp01
           Raw device:         /dev/obl0
    
   osblp01_tape_2:
       Device type:            tape
       Model:                  HP      Ultrium 5-SCSI
       Serial number:          HU1328WGF6
       In service:             no
       Library:                osblp01_lib_1
       DTE:                    1
       Automount:              yes
       Position interval:      [undetermined]
       Debug mode:             no
       Blocking factor:        (default)
       Max blocking factor:    (default)
       Current tape:           [unknown]
       Use list:               [not set]
       Drive usage:            [not set]
       Cleaning required:      [unknown]
       UUID:                   01832346-15e3-1032-bdb8-000000000000
       Attachment 1:
           Host:               osblp01
           Raw device:         /dev/obt1
    
   osblp01_tape_1:
       Device type:            tape
       Model:                  HP      Ultrium 5-SCSI
       Serial number:          HU1327WEYJ
       In service:             no
       Library:                osblp01_lib_1
       DTE:                    2
       Automount:              yes
       Position interval:      [undetermined]
       Debug mode:             no
       Blocking factor:        (default)
       Max blocking factor:    (default)
       Current tape:           [unknown]
       Use list:               [not set]
       Drive usage:            [not set]
       Cleaning required:      [unknown]
       UUID:                   0183170c-15e3-1032-bdb8-000000000000
       Attachment 1:
           Host:               osblp01
           Raw device:         /dev/obt0
   ob>

To access SCSI or Fibre Channel tape devices on HP-UX using the makedev script, Oracle Secure Backup requires the following identifying information about how the devices are attached to their hosts:

• SCSI bus number instance

• Target ID

• LUN

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

To identify and configure HP-UX devices:

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

There is no required order for assigning Oracle Secure Backup logical unit numbers. They are typically assigned sequentially, starting at 0, for each tape device of a given type, whether tape library or tape drive. That is, tape libraries are typically numbered 0, 1, 2 and so on, and tape drives are also numbered 0, 1, 2 and so on. The maximum value for an Oracle Secure Backup logical unit number is 31.

On Linux or UNIX, the resulting device special file names for tape libraries are /dev/obl1, /dev/obl2, /dev/obl3 and so on, and the names for tape drives are /dev/obt1, /dev/obt2, /dev/obt3 and so on. On Windows, the resulting tape library names are //./obl1, //./obl2, //./obl3 and so on, and the names for tape drives are //./obt1, //./obt2, //./obt3 and so on, where these names are assigned automatically during the installation of Oracle Secure Backup on Windows.

It is mandatory to enable IOCP on your AIX systems to be able to perform Oracle Secure Backup operations successfully.

To configure IOCP:

1. Run the lslpp command to ensure that IOCP module was installed on your system during the database install.

   $ lslpp -l bos.iocp.rte

   The output should look similar to this:

   Fileset                     Level     State       Description
   ----------------------------------------------------------------------------
   Path: /usr/lib/objrepos
     bos.iocp.rte              5.3.9.0   APPLIED     I/O Completion Ports API
    
   Path: /etc/objrepos
     bos.iocp.rte              5.3.0.50  COMMITTED   I/O Completion Ports API

2. Run the lsdev command to check the status of the IOCP port.

   $ lsdev -Cc iocp

   The required IOCP port status is Available.

   If the IOCP port status is Defined, change this to Available by completing the following steps:

   1. Log on as root.

   2. Run the following command:

      # smitty iocp

   3. Select Change/Show characteristics of the I/O Completion Ports.

   4. Change the configured state from Defined to Available.

   5. Restart the system for this change to reflect.