Preparing Hardware for Archiving

This section provides information about preparing the hardware for archiving.

Verifying Archive Media

If you plan to perform disk archiving to archive to disk space in another file system, verify the following:

• The host system to which the disks are attached has at least one file system created that is compatible with the SAM-QFS software

• The disk has enough space available to accommodate the archive copies

If you plan to archive to removable media devices, your environment must include the following:

• At least one removable media device for archiving files.

  This device can be a single tape or optical drive, or it can be multiple devices, such as the drives within an automated library.

• Tape or magneto-optical cartridges to which archive files can be written.

For most SCSI-attached and FC-attached libraries, the SAM-QFS software supports only one media type. If you have a tape library that can be partitioned logically into two or more libraries, you can use one media type in one logical library and a different media type in another. The SAM-QFS software records the cartridges used for each library in a library catalog. You cannot mix the tape media types in a library catalog, so plan to use only one media type per library or logical library.

The SAM-QFS environment supports a wide variety of removable media devices. You can obtain a list of currently supported drives and libraries from your Oracle sales or support staff.

To ensure that your devices are attached and enumerated in an easily retrieved list, perform one or both of the following procedures:

• If your removable media devices are not attached to your server, see Verifying Archive Media.

• Enumerate your devices. See Creating a List of Devices. You will use this list again in Installing the Software Packages.

How to Attach Removable Media Devices

The following steps are general guidelines for attaching removable media hardware to a server. For explicit instructions on how to connect these peripherals to a server, see the hardware installation guide supplied by the vendor.

1. Ensure that you are on a console connection to the server.
2. Power off the server.
3. Ensure that the removable media devices and the disks to be used for the Sun QFS file system are connected and properly addressed.
4. If you have libraries attached to the host system through a SCSI interface, ensure that the SCSI target IDs are unique for each SCSI initiator (host adapter).

   Avoid setting SCSI target IDs for peripherals to IDs that are already in use. In addition, if you are using a SCSI host adapter with a previously attached disk drive, any additional peripheral connected to this bus must have a different ID. Typically, the initiator uses ID 7, and the internal disk drive uses ID 3 for SPARC systems and ID 0 for UltraSPARC systems.

5. Power on the peripherals according to the manufacturer's recommended sequence.

   Typically, you power on the outermost peripherals first, working toward more central components in sequence.

6. Disable autobooting, and then reset the system.

   >ok setenv auto-boot? false
   >ok reset

7. Conduct an inventory of target IDs and logical unit numbers (LUNs) for each device that is connected to the host system.

   Save the output as you will need it later. See Creating a List of Devices.

   Do one of the following:

   • If you have libraries attached to the host system through a SCSI interface, use the probe-scsi-all command.

     You should see output similar to the following example:

     {0} ok probe-scsi-all
     /pci@6,400/scsi@2,1
     Target 0
       Unit 0   Removable Device type 8     STK 9730        1700
     Target 1
       Unit 0   Removable Tape   type 7     QUANTUM DLT7000 2565
     Target 2
       Unit 0   Removable Tape   type 7     QUANTUM DLT7000 2565
     /pci@1f,4000/scsi@3
     Target 0
       Unit 0   Disk     SEAGATE ST318404LSUN18G 4207
     Target 6
       Unit 0   Removable Read Only device   TOSHIBA XM6201TASUN32XCD1103

   • If libraries or tape drives are attached to the host system through an FC interface, use the show-devs command.

     For example:

     {0} ok show-devs
     /SUNW,ffb@1e,0
     /SUNW,UltraSPARC-II@2,0
     /SUNW,UltraSPARC-II@0,0
     /counter-timer@1f,1c00
     /pci@1f,2000
     /pci@1f,4000
     /virtual-memory
     /memory@0,a0000000
     /aliases
     /options
     /openprom
     /chosen
     /packages
     /pci@1f,2000/SUNW,qlc@1
     /pci@1f,2000/SUNW,qlc@1/fp@0,0
     /pci@1f,2000/SUNW,qlc@1/fp@0,0/disk
     /pci@1f,4000/SUNW,ifp@2
     /pci@1f,4000/scsi@3,1
     /pci@1f,4000/scsi@3
     /pci@1f,4000/network@1,1
     /pci@1f,4000/ebus@1
     /pci@1f,4000/SUNW,ifp@2/ses
     {0} ok select /pci@1f,2000/SUNW,qlc@1
     {0} ok show-children
     LiD HA LUN  --- Port WWN ---  ----- Disk description -----
      2  7e   0  500104f00041182b  STK     L700            0236
     7c  7e   0  500104f00043abfc  STK     9840            1.28
     7d  7e   0  500104f00045eeaf  STK     9840            1.28
     6f  7e   0  500104f000416304  IBM     ULT3580-TD1     16E0
     6e  7e   0  500104f000416303  IBM     ULT3580-TD1     16E0

   If the server does not acknowledge all the known devices (disk drives, tape or optical drives, the automated library, and so on), check the cabling. Do not proceed until all devices appear in the list when probed.

8. Reenable autobooting, and then boot the system.

   >ok setenv auto-boot? true
   >ok boot

9. Review system files.

   • Check /var/adm/messages to ensure that all devices were recognized.

   • Check /dev/rmt for expected tape devices.

   • Check the /dev/dsk and /dev/rdsk directories for expected disks.

   ---

   Note - Due to special driver requirements, no device information appears in /var/adm/messages for magneto-optical devices or libraries until after you install the SAM-QFS software packages.

   ---

10. Disable autocleaning and autoloading.

    If your automated library supports autocleaning or autoloading, disable those features when using that library with the Sun Storage Archive Manager software. Consult the documentation from your library's manufacturer for information about disabling autocleaning and autoloading.

    ---

    Note - You can only use autoloading during the initial loading of cartridges and when the SAM-QFS software is not running. Remember to disable autoloading when the SAM-QFS system is running.

    ---

Creating a List of Devices

The devices that you intend to use must be attached and recognized by the server upon which you intend to install the SAM-QFS software. To configure the SAM-QFS software, you need to know the device type, manufacturer, and model number of your devices. You also need to know the mechanism by which the device is attached to the server.

You can attach devices in one of the following ways:

• Drives can use either a SCSI attachment or an FC attachment. Each drive accepts either tape cartridges or magneto-optical cartridges.

• For SCSI-attached drives, you need to know each drive's SCSI target ID and logical unit number (LUN).

• For FC-attached drives, you need to know each drive's LUN and node World Wide Name (WWN).

• Automated libraries can use a SCSI attachment, an FC attachment, or a network attachment.

Libraries that use SCSI or FC attachments are called direct-attached libraries. For SCSI-attached libraries, you need to know each library's SCSI target ID and LUN. For FC-attached libraries, you need to know each library's LUN and node WWN.

Libraries that use a network attachment are called network-attached libraries. You cannot configure network attached libraries in the existing system configuration files. Instead, you must create a parameters file for each network attached library. This process is explained later.

Use the following table to note the name, manufacturer, model, and connection types for each device that you want to include in your SAM-QFS environment. Retain this list for future use in the configuration procedure.