C H A P T E R 8

Upgrading the Hardware in Your Environment

This chapter describes how to upgrade the hardware within your existing Sun StorEdge SAM-FS environment. The following topics are presented:

- Adding Slots in an Automated Library

- Upgrading or Replacing a Library

- Upgrading DLT Tape Drives

Certain other types of operations and upgrades also need to be performed within a Sun StorEdge SAM-FS environment. The following publications describe these operations:

- The Sun StorEdge QFS and Sun StorEdge SAM-FS Software Installation and Configuration Guide describes upgrading Sun StorEdge QFS and Sun StorEdge SAM-FS software.

- The Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide describes the following types of operations and upgrades:

- Initializing a File System

- Propagating Configuration File Changes to the System

- Mounting a File System

- Unmounting a File System

- Checking File System Integrity and Repairing File Systems

- Preserving Information for an Upgrade

- Preparing for a Hardware Device Upgrade

- Adding Disk Cache to a File System

- Replacing Disks in a File System

- Upgrading a Host System

- Upgrading the Solaris OS

##

Adding Slots in an Automated Library

Your software license controls the number of cartridge slots managed by the Sun StorEdge SAM-FS system. To increase the number of slots, follow the steps in this section.

### To Add Slots In a Library

1. Determine whether you need to obtain a new set of license keys through your authorized service provider (ASP) or, if an ASP is not assigned to your account, through Sun Microsystems.

If you do not need new license keys, continue with Step 2.

If you need new license keys, perform the following steps:

a. Replace the existing license keys with the new license keys.

Perform this step if you obtained new license keys. License keys start in column 1 of the following file:

    /etc/opt/SUNWsamfs/LICENSE.4.1

No other keywords, host IDs, or other information can appear.

b. Issue the `samd`(1M) `config` command to enable the Sun StorEdge SAM-FS software to recognize the new license keys. (Optional)

Perform this step if you obtained new license keys. For example:

    # samd config

2. Unload the library catalog.

Use the `sacmd`(1M) `unload` command in the following format:

    samcmd unload eq

For eq, specify the Equipment Ordinal of the automated library as defined in the `mcf` file. This command moves the library catalog entries into the historian catalog and preserves the catalog information for each cartridge.

After this command executes, you can use `samu`(1M) `v` display to observe the automated library's `v` display empty and the historian's `v` display fill up with the VSNs that used to be in the automated library.

3. Bring down the Sun StorEdge SAM-FS system.

For information on how to perform this step, see Using Automated Libraries and Manually Loaded Drives in a Sun StorEdge SAM-FS Environment.

4. Power down the host system and the library according to the manufacturer's suggested procedure.

5. Have the library hardware engineer add slots to the automated library.

6. Power on the host system using your normal start-up procedure.

7. Start the Sun StorEdge SAM-FS system.

For information about how to perform this step, see Using Automated Libraries and Manually Loaded Drives in a Sun StorEdge SAM-FS Environment. The new license information appears in the `samu`(1M) utility's `l` display.

##

Upgrading or Replacing a Library

Prior to disconnecting and installing a different automated library, prepare for the upgrade as described in the Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide in the section called "Preparing for Hardware Upgrades."

### To Replace or Upgrade a Library

1. Unload the library catalog.

Use the `sacmd`(1M) `unload` command in the following format:

    samcmd unload eq

For eq, specify the Equipment Ordinal of the automated library as defined in the `mcf` file. This command moves the library catalog entries into the historian catalog and preserves the catalog information for each cartridge.

After this command executes, you can use `samu`(1M) `v` display to observe the automated library's `v` display empty and the historian's `v` display fill up with the VSNs that used to be in the automated library.

2. Update the `/etc/opt/SUNWsamfs/inquiry.conf` file. (Optional)

The new library should be identified in this file by the vendor, the automated library model, and a Sun StorEdge SAM-FS internal name.

For example, the released `inquiry.conf` file includes the following line:

    "HP",   "C1710T",  "hpoplib"   # HP optical library

This line indicates that if the system detects a SCSI device made by vendor `HP` of model `C1710T`, the system drives it as an `hpoplib`. The first two fields (vendor/product) are returned from the hardware devices. The last field, `hpoplib`, is a name that the system uses internally to determine how to communicate with the device. If the `inquiry.conf` file needs to be changed, the change does not become effective until the `sam-amld` daemon is restarted.

3. Save the current `/etc/vfstab` file as `/etc/vfstab.cur`.

4. Edit the `/etc/vfstab` file.

Change any Sun StorEdge SAM-FS mounts from yes to no.

5. Save the `/etc/opt/SUNWsamfs/archiver.cmd` file as `archiver.cmd.cur`.

6. Edit the `/etc/opt/SUNWsamfs/archiver.cmd` file

Add a `wait` directive as the first line.

7. Power off the host system and peripherals using the manufacturer's suggested procedure.

8. Disconnect the automated library.

9. Attach the connecting cable to the new automated library.

10. Power on the peripherals and the host system using the suggested power-on sequence.

11. Ensure that the host system identifies the new automated library.

Enter the following command:

    > probe-scsi-all

The new automated library and its drives must display prior to proceeding. If these devices are not identified, the automated library and its drives probably have a connection problem.

12. Boot the system.

Enter the following command to boot with the new configuration:

    > boot -rv

13. If the target numbers of the drives or automated library changed, or if the ordering or number of the drives in the automated library changed, modify the `/etc/opt/SUNWsamfs/mcf` file to reflect the new configuration. (Optional)

This is similar to an initial installation as described in the Sun StorEdge QFS and Sun StorEdge SAM-FS Software Installation and Configuration Guide.

14. Create new `/dev/samst` entries. (Optional)

Perform this step if you are adding new equipment. Enter the following command:

    # samdev

15. Initialize the Sun StorEdge SAM-FS system.

You can perform this step by either mounting a file system or by typing the following command:

    # samd start

When the system initializes, it recognizes that the number of slots in the automated library has changed. The system runs a full audit on the automated library to update the library catalog. A full audit must be completed before archiving is resumed.

If there are problems in the audit, the most likely reason is that the ordering of the drives in the automated library does not match the ordering in the `/etc/opt/SUNWsamfs/mcf` file. Remember, that drives have two attributes: the SCSI target ID and the position in the automated library. Both of these attributes must be correct both before and after the upgrade.

If the audit completes without problems, proceed to the next step.

16. Replace the `/etc/vfstab` and `/etc/opt/SUNWsamfs/archiver.cmd` files with the pre-upgrade versions.

Use the saved `/etc/vfstab.cur` and `/etc/opt/SUNWsamfs/archiver.cur` files, respectively.

17. Reboot the system to ensure that no errors exist in the configuration.

The automated library calls the drives by position number. When the system wants to load a cartridge into a drive, it must, for example, send a command to the automated library to load a cartridge from slot 123 into drive 3.

Drive 3 might be SCSI target 6 based on the third `mcf` entry. The system knows it is drive 3 because it is the third drive entry in the `mcf` file. The automated library knows that it is drive 3 because of the physical location it occupies in the automated library.

After the automated library receives a request to load the cartridge into the drive, the system tests the drive for unit ready status. Here, the system uses the SCSI target ID as defined in the `/dev/samst/`scsi-target entry in the `mcf` file. Therefore, it is important that the entry match the drive that was just loaded with the cartridge.

There is no good way to determine this information. Usually, the manufacturer ships the automated library set up with ascending SCSI IDs on the drives, but there is no guarantee of this. One way to determine this is to use the `samu`(1M) utility's `:load` command to load a cartridge, and then watch the `samu`(1M) utility's `s` display to see which drive shows the `r`, rather than the `p`, in the status flags of the `t` display.

##

Upgrading DLT Tape Drives

To take advantage of higher density and faster tape technology, you can upgrade DLT tape drives in an automated library or a standalone tape drive. For example, you can move from DLT 4000 drives to DLT 7000 drives.

In a Sun StorEdge SAM-FS environment, this is a matter of adding the new drive, rebooting the new configuration, and updating the mcf file as necessary prior to starting the Sun StorEdge SAM-FS environment. In addition, if you are upgrading the number of slots, you need to contact your authorized service provider (ASP) or Sun Microsystems because you might need an upgraded license.

Note the following restrictions and general information before upgrading drives:

- Sun StorEdge SAM-FS environments do not support mixed DLT tape drives within the same direct-attached automated library. For example, a Sun StorEdge SAM-FS system cannot differentiate between a DLT 4000 tape drive and a DLT 7000 tape drive in the same automated library. Therefore, you should plan on replacing all the DLT drives with the new drives at the same time.

- The lower-density tapes can coexist with higher-density tapes and tape drives. You can continue to read and write to the lower-capacity tapes using a higher-density drive.

- To take full advantage of the higher-density DLT tapes, you might want to recycle existing files and migrate them to a higher-density tape. You can accomplish this by marking all the lower-density tapes as read-only and then marking these tapes to be recycled. For information on recycling tape, see Recycling.

- As each tape is labeled, the density of the tape is acknowledged and recorded in the library catalog.

### To Upgrade Tape Drives

1. Decide whether or not your current dump files are sufficient. (Optional)

If you decide that they are not, perform a `samfsdump`(1M) on your file systems prior to proceeding to the next step.

2. Update the `/kernel/drv/st.conf` file to identify the new drives.

The tape drives are identified in this file by the vendor, the tape model, and a Sun StorEdge SAM-FS internal name. For example, the released `st.conf` file contains the following line:

    "QUANTUM DLT7000", "DLT 7000 tape drive",   "dlt7-tape"

An example file is provided in `/opt/SUNWsamfs/examples/st.conf_changes`. You can read in the entire file to `/kernel/drv/st.conf` or you can merge the necessary changes. For more information on updating the `st.conf` file, see the Sun StorEdge QFS and Sun StorEdge SAM-FS Software Installation and Configuration Guide.

3. Power off the host system and peripherals using the manufacturer's suggested procedure.

4. Replace the tape drives with the new drives.

5. Power on the peripherals and host system using the suggested power-on sequence.

6. Ensure that the host system identifies the new drives.

Enter the following command:

    > probe-scsi-all

The automated library and the new drives must be appear prior to proceeding. If these devices do not appear, a connection problem probably exists and needs to be corrected. After this command returns the expected information, you can proceed to the next step.

7. Boot the system.

Enter the following command to boot with the new configuration:

    > boot -rv

8. Modify the `/etc/opt/SUNWsamfs/mcf` file to reflect the new configuration. (Optional)

Perform this step if the target numbers of the drives or automated library changed, or if the ordering or number of the drives in the automated library changed. This is similar to an initial installation as described in the Sun StorEdge QFS and Sun StorEdge SAM-FS Software Installation and Configuration Guide.

9. Create new `/dev/samst` entries for the new equipment. (Optional)

To create these entries, enter the following command:

    # samdev

10. Start your Sun StorEdge SAM-FS system.

11. Mount the file systems.

You can now continue to use the existing Sun StorEdge SAM-FS tapes.

Copyright © 2004, Sun Microsystems, Inc. All rights reserved.