Configuring NAS Libraries and Tape Drives on Linux and UNIX

This section explains how to configure the libraries and tape drives attached to a Network Attached Storage (NAS) Filer so that the filer can communicate with Oracle Secure Backup.

Libraries and tape devices attached to NAS filers are automatically configured by the operating system on which the NAS device runs. Both SCSI device and Fibre Channel configuration occur behind the scenes, transparent to the user.

Nevertheless, you must still make libraries and tape drives accessible to the Oracle Secure Backup software. You accomplish this task by performing device discovery on each of the NAS filers in the administrative domain.

Note:

An administrative server can use an NAS filer with attached devices as a media server.

Making NAS Device Names Accessible to Oracle Secure Backup

Oracle Secure Backup can detect devices attached to NAS filers that are part of an administrative domain and, based on this information, automatically update the domain's device configuration.

See Also:

Oracle Secure Backup Administrator's Guide to learn how to use the Oracle Secure Backup Web tool to perform this task

To discover NAS device names and make them accessible to Oracle Secure Backup, log on to the administrative server as root and start obtool. Then complete the following steps:

Use the obtool discoverdev command to detect changes in NAS device configuration and update the administrative domain with the correct information about your devices.

This example illustrates using discoverdev in obtool on a NAS device called mynasfiler5, which was configured previously using mkhost.

See "Configuring Administrative Domain NAS Filers Using obtool" for information on configuring hosts.

ob> discoverdev --verbose --host mynasfiler5

The command generates the following output:

Info: beginning device discovery for mynasfiler5.
Info: connecting to mynasfiler5

Info: devices found on mynasfiler5:
   Info: ATL     1500            ...
      Info: mc3  attrs= [none]
         Info: WWN: [none]
         Info: SN:  PMC13A0007
   Info: Quantum SDLT220...
      Info: nrst7a  attrs= norewind raw
         Info: WWN: [none]
         Info: SN:  CXB45H1313
   Info: Quantum SDLT220...
      Info: nrst8a  attrs= norewind raw
         Info: WWN: [none]
         Info: SN:  PKB51H0286
 
   mynasfiler5_mc3  (new library)
      WWN: [none]
      new attach-point on mynasfiler5, rawname mc3
 
   mynasfiler5_nrst7a  (new drive)
      WWN: [none]
      new attach-point on mynasfiler5, rawname nrst7a
 
   mynasfiler5_nrst8a  (new drive)
      WWN: [none]
      new attach-point on mynasfiler5, rawname nrst8a

Note:

By convention, NAS library names are characterized by mc and NAS tape drives are characterized by nrst.
For help on an obtool command, enter:
```
ob> help command
```

List summary device information. For example:

ob> lsdev

The command generates the following output:

library    mynasfiler5_mc3      not in service
drive      mynasfiler5_nrst7a   not in service
drive      mynasfiler5_nrst8a   not in service
library    tc-lib               in service
  drive 1  tc-tape              in service

Unless you change the default policy value for a device, every newly discovered NAS device is by default placed in the not in service state.

Note:

The device names assigned automatically by Oracle Secure Backup are generated from the library and tape drive names reported by the NAS device. These names tend to be long and unwieldy. Consider renaming NAS library and tape drives to more concise names.

The long names are used in this example.

Specify the name of the library in which the first tape drive resides. For example:
```
ob> chdev --library mynasfiler5_mc3 --dte 1 mynasfiler5_nrst7a
```
Specify the name of the library in which the second tape drive resides. For example:
```
ob> chdev --library mynasfiler5_mc3 --dte 2 mynasfiler5_nrst8a
```

Put the library and tape drives in service.

ob> chdev --inservice mynasfiler5_mc3 mynasfiler5_nrst7a mynasfiler5_nrst8a

List the library and devices now in service. For example:

ob> lsdev mynasfiler5_mc3

The command generates the following output:

library    mynasfiler5_mc3      in service
  drive 1  mynasfiler5_nrst7a   in service
  drive 2  mynasfiler5_nrst8a   in service

You may choose to take another inventory of your system at this point.