Skip Headers
Oracle® Secure Backup Installation Guide
Release 10.1

Part Number B14235-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

Configuring NAS Libraries and Tape Drives on Windows

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

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 configurations occur automatically.

Libraries and tape drives must still be made 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.

To discover NAS device names and make them accessible to Oracle Secure Backup, complete the following steps:

  1. If you are already logged on to Oracle Secure Backup, skip to Step 3.

    Otherwise, log on to Windows as the Administrator user or as a user that is a member of the Administrators group.

  2. To open Oracle Secure Backup, click the Start button and select Programs, Oracle Secure Backup, and Oracle Secure Backup Command Line Interface.

    The ob> prompt displays.

  3. Detect changes in device configuration and update the administrative domain for a media server called mynasfiler5, which was configured previously using mkhost. See "Configuring NAS Filers" for more information.

    ob> discoverdev --verbose --host mynasfiler5
    
    

    In this example, the command displays 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.

  4. List summary device information. For example:

    ob> lsdev
    
    

    obtool displays output similar to the following:

    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 a device's default policy value, every newly discovered device is by default placed in the not in service state.


    Note:

    The device names assigned automatically by Oracle Secure Backup are predicated on 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.

  5. Specify the name of the library in which the first tape drive resides. For example:

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

    ob> chdev --library mynasfiler5_mc3 --dte 2 mynasfiler5_nrst8a
    
    
  7. Notice that none of the devices are in service. Put the library and tape drives in service. For example:

    ob> chdev --inservice mynasfiler5_mc3 mynasfiler5_nrst7a mynasfiler5_nrst8a
    
    
  8. List the library and devices now in service. For example:

    ob> lsdev mynasfiler5_mc3
    
    

    In this example, the command displays 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. For instructions, see "Taking Inventory of Tape Devices on Windows".