C H A P T E R 4

Upgrade and Configuration Tasks

This chapter describes the procedures for upgrading a server to a new release of the Sun StorEdge SAM-FS software. Use these procedures if you are upgrading your Sun StorEdge SAM-FS environment. You must perform all the tasks in this chapter as superuser.

This chapter contains the following sections:

- Preparing for an Upgrade

- Removing the Existing Software

- Adding the Upgrade Packages

- Restoring the File System

- Upgrading Hardware

- Upgrading the Solaris OS

##

Preparing for an Upgrade

Follow the instructions in this section to prepare for a Sun StorEdge SAM-FS software upgrade.

### Backing Up the File System

Back up your existing file system if the following conditions exist:

- You are currently using a version 1 superblock with a Sun StorEdge SAM-FS 4U0 system and you want to reinitialize your file systems with a version 2 superblock. In To Reinitialize and Restore the File Systems, you reinitialize the file systems and restore your data.

- You suspect that your current `samfsdump`(1M) file is incorrect or outdated.

The following subsections explain the differences between these two superblocks and present the procedure for backing up your file systems:

- Using the Version 1 and Version 2 Superblocks

- To Back Up a File System

CODE EXAMPLE 4-1 shows the `samfsinfo`(1M) command you use to retrieve information about the `samfs4` file system. The second line of output indicates that this file system is using a version 2 superblock.

CODE EXAMPLE 4-1 Using `samfsinfo` (1M)
    # samfsinfo samfs4
    samfsinfo: filesystem samfs4 is mounted.
    name:     samfs4       version:     2
    time:     Sat Sep 20 08:24:34 2003
    count:    1
    capacity:      04b00000          DAU:         16
    space:         02e22ff0
    ord  eq   capacity      space   device
      0  41   04b00000   02e22ff0   /dev/dsk/c9t50020F2300010570d0s1

#### Using the Version 1 and Version 2 Superblocks

Sun StorEdge SAM-FS 4U1 and later releases support both a version 1 superblock and a version 2 superblock. Only the version 2 superblock supports Access Control Lists (ACLs).

The Sun StorEdge SAM-FS 4U1 and later releases support both the version 1 and version 2 superblocks. You can use the `sammkfs`(1M) command to create a version 2 superblock, but you cannot initialize any file systems with version 1 superblocks. In addition, it is not possible to move files from a file system with a version 2 superblock back to a file system with a version 1 superblock.

After you reinitialize a file system, you can use the `samfsrestore`(1M) command to restore files to the new file system from the snapshot file created during the backup procedure.

If you are upgrading from a Sun StorEdge SAM-FS 4U0 system, note that the Sun StorEdge SAM-FS 4U0 file system allows you to initialize file systems with either a version 1 or a version 2 superblock. If you want to reinitialize any of the file systems that have a version 1 superblock and remake them with a version 2 superblock, back up these file systems now.

Note - Sun StorEdge SAM-FS 4U2 and later releases do not allow you to initialize a file system with a version 1 superblock. These more recent versions enable you to initialize file systems only with the version 2 superblock.

To Back Up a File System

1. Become superuser from a console connection.

If you have not already logged in as `root`, do so now.

2. Make sure that all files are archived.

The following example assumes that `sam1` is the mount point of the file system. You can complete this step by entering a command similar to the following:

    # sfind /sam1 ! -type d ! -archived > /tmp/notarchived.list

The preceding command finds all files that are not archived and sends the output to a file. Depending on the size of your file system, this command can take a long time to complete.

3. Examine this command's output, and do one of the following:

- If you want any of these unarchived files to appear in the dump file, archive them now.

- Use the `-u` option to the `samfsdump`(1M) command to dump unarchived data if you suspect that some files have not yet been archived. The `-u` option can create very large dump files, however, so consider space limitations when using this option.

4. Use the `samfsdump`(1M) command to back up each Sun StorEdge SAM-FS file system's metadata. See About Metadata Snapshots.

Dump each file system's metadata to a location outside the Sun StorEdge SAM-FS file system.

CODE EXAMPLE 4-2 assumes that you have a file system mounted at `/sam1` that you want to back up to `samfs1.dump`, which exists outside of the Sun StorEdge SAM-FS file systems.

CODE EXAMPLE 4-2 Using `samfsdump` (1M)
    # cd /sam1
    # samfsdump -f /csd_dump_dir/samfs1.dump

The `samfsdump`(1M) command dumps file names and inode information, not data. For more information, see the `samfsdump`(1M) man page.

You must back up the metadata information for each file system, so repeat the preceding steps for each file system in your Sun StorEdge SAM-FS environment.

For more information about backing up your file systems, see the Sun StorEdge SAM-FS Troubleshooting Guide.

### Stopping the Sun StorEdge SAM-FS Software

The procedures in this section show how to halt Sun StorEdge SAM-FS operations.

To Stop the File System From File System Manager

You can idle or stop archiving activity from the File System Manager software.

1. From the Servers page, click the name of the server for which you want to control archiving activity.

The File Systems Summary page is displayed.

2. Click the Archive Management tab and click the Activity Management local tab.

The Activity Management page is displayed.

3. In the Archiving section of the page, select the radio button next to the option that you want to control, and click Submit Job:

- Idle - Stops archiving after it reaches a logical point in the process.

- Stop - Immediately stops the archiving process.

4. To view the progress of the archiving activity, click the Jobs tab and look for the job that you submitted.

For complete information about controlling archiving activity from File System Manager, see the File System Manager online help.

To Stop the File System From the Command Line

1. Use the `samcmd`(1M) `idle` command to idle each removable media drive configured in your `mcf` file.

This step enables the archiver, stager, and other processes to complete current operations. Use this command in the following format:

    samcmd idle eq

For eq, specify the Equipment Ordinal of the device as defined in your `mcf` file.

You can also idle the drives by using the `samu`(1M) operator utility. For more information about the `samcmd`(1M) command, see the `samcmd`(1M) man page.

2. If you are upgrading from a Sun StorEdge SAM-FS 4U0 system, use the `samcmd`(1M) `aridle` command to idle the archiver:

    # samcmd aridle

3. Use the `samd`(1M) `stop` command to stop all operations.

For example:

    # samd stop

### To Unshare File Systems

Perform this task if your Sun StorEdge SAM-FS file systems are NFS-shared file systems.

Use the `unshare`(1M) command on the Sun StorEdge SAM-FS file system.

For example, the following command unshares the `samfs1` file system:

    # unshare samfs1

### Unmounting File Systems

You can unmount a file system using any of the methods described in this section. After the file system is unmounted, you can proceed to Removing the Existing Software.

To Unmount Using File System Manager

1. From the Servers page, click the name of the server on which the file system is located.

The File System Summary page is displayed.

2. Select the radio button next to the file system that you want to unmount.

3. From the Operations menu, choose Unmount.

To Unmount Using CLI Commands

Use the `umount`(1M) command to unmount each Sun StorEdge SAM-FS file system.

If necessary, use the `-f` option to the `umount`(1M) command. The `-f` option forces a file system to unmount. Before using this option, verify that all archiving operations have been completed, if possible.

If `umount`(1M) is not successful, it might be because the files in the file system are being used or because you have used the `cd` command to change to a directory that is within the file system. In this case, follow these steps:

1. Use the `fuser`(1M) command to determine whether any processes are still busy.

For example, the following command queries the `samfs1` file system:

    # fuser -uc /samfs1

2. If any processes are still busy, use the `kill`(1M) command to terminate them.

3. Use the `umount`(1M) command to unmount each Sun StorEdge SAM-FS file system.

To Unmount By Editing the `/etc/vfstab` File and Rebooting

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

For all Sun StorEdge SAM-FS file systems, change the Mount at Boot field from `yes` or `delay` to `no`.

2. Reboot the system.

##

Removing the Existing Software

Use the `pkgrm`(1M) command to remove the existing software. You must remove the existing Sun StorEdge SAM-FS package before installing the new package.

If you are using any optional Sun StorEdge SAM-FS packages, you should make sure that you remove these packages before removing the main `SUNWsamfs` packages. The installation script prompts you to confirm several of the removal steps.

### To Remove Existing Software

1. Use the `pkginfo`(1) command to determine which Sun StorEdge SAM-FS packages are installed on your system.

For example:

    # pkginfo | grep sam

2. Use the `pkgrm`(1M) command to remove the existing Sun StorEdge SAM-FS software.

The following example command removes the `SUNWsamfsu` and the `SUNWsamfsr` packages from a 4U1 release:

    # pkgrm SUNWsamfsu SUNWsamfsr

Note - The `SUNWsamfsr` package must be the last package removed. The 4U1 release does not include any localized software packages.

The following example command removes the `SUNWcsamf`, the `SUNWfsamf`, the `SUNWjsamf` localized packages and the `SUNWsamfs` package from a 4U0 release:

    # pkgrm SUNWcsamf SUNWfsamf SUNWjsamf SUNWsamfs

Note - The `SUNWsamfs` package must be the last package removed.

##

Adding the Upgrade Packages

The Sun StorEdge SAM-FS software packages use the Sun Solaris packaging utilities for adding and deleting software. The `pkgadd`(1M) command prompts you to confirm various actions necessary to upgrade the packages.

During the installation, the system detects the presence of conflicting files and prompts you to indicate whether you want to continue with the installation. You can go to another window and copy the files that you want to save to an alternate location.

### To Add the Packages

1. Use the `cd`(1) command to change to the directory where the software package release files reside.

This is one of the following, depending on your release media:

- If you downloaded the release files as described in Obtaining the Release Files, change to the directory to which you downloaded the files.

- If you obtained the release files from a CD-ROM, change to the directory on the CD-ROM that corresponds to your OS version.

2. Use the `pkgadd`(1M) command to upgrade the `SUNWsamfsr` and `SUNWsamfsu` packages.

For example:

    # pkgadd -d . SUNWsamfsr SUNWsamfsu

3. In response to questions about conflicting files, enter `yes` or `y` .

During the installation, the system detects the presence of conflicting files and prompts you to indicate whether or not you want to continue with the installation. You can go to another window and copy the files you wish to save to an alternate location.

4. When prompted to define an administrator group, select `y` to accept the default (no administrator group), or select `n` if you want to define an administrator group.

You can use the `set_admin`(1M) command to reset permissions on certain commands later. For more information, see the `set_admin`(1M) man page.

5. Examine the Sun StorEdge SAM-FS log file, `/tmp/SAM_install.log`.

This file should show that the `pkgadd`(1M) command added the `SUNWsamfsr` and `SUNWsamfsu` software packages. Make sure that it also installed Sun StorEdge SAM-FS `samst` driver. If all files were installed properly, the following message appears:

    Restarting the sysevent daemon

Note - The tools package, `SUNWsamtp`, is available separately. Contact your Sun sales representative for information about obtaining the 4U5 version of the `SUNWsamtp` package.

### To Install File System Manager

File System Manager is an online interface that enables you to configure many of the components in a Sun StorEdge SAM-FS environment. You can use this tool to control, monitor, configure, and reconfigure the environment's components.

Perform this task if you want to be able to use File System Manager to configure, control, monitor, or reconfigure your Sun StorEdge SAM-FS environment.

1. Ensure that you have met the installation requirements described in Verifying Requirements for File System Manager.

2. Log in to the server that you want to use as the management station.

This can be the same server on which you installed the `SUNWsamfsr` and `SUNWsamfsu` packages or a different server on the same network.

3. Become superuser.

4. Use the `cd`(1) command to change to the directory where the software package release files reside on your server.

5. Execute the `fsmgr_setup` script to start the installation process.

For example:

    # fsmgr_setup

6. Answer the questions as prompted by the `fsmgr_setup` script.

During the installation procedure, you are asked questions about your environment.

The `fsmgr_setup` script automatically installs the following:

- The Tomcat, Java Runtime Environment (JRE), JATO, and Java Web Console packages. If you have existing versions of these software packages that are not compatible with File System Manager, the installation software asks you whether you want the appropriate levels to be installed at this time.

- The `SUNWfsmgrr` package.

- The `SUNWfsmgru` package.

The installation scripts prompt you to specify whether you want to install localized packages.

After installing the packages, it starts the Tomcat Web Server and enables logging.

7. Use `vi`(1) or another editor to edit your system setup files to include the correct paths to commands and man pages.

- In the Bourne or Korn shell, edit the `.profile` file, change the `PATH` and `MANPATH` variables, and export the variables.

CODE EXAMPLE 4-3 shows how your `.profile` file might look after editing.

CODE EXAMPLE 4-3 Finished `.profile` File
    PATH=$PATH:/opt/SUNWfsmgr/bin
    MANPATH=$MANPATH:/opt/SUNWfsmgr/man
    export PATH MANPATH

- In the C shell, edit the `.login` and `.cshrc` files.

When you have finished editing, the `path` statement in your `.cshrc` file might look like the following line:

    set path = ($path /opt/SUNWfsmgr/bin)

CODE EXAMPLE 4-4 shows how the `MANPATH` in your `.login` file might after you have finished editing.

CODE EXAMPLE 4-4 Finished `MANPATH` in the `.login` File
    setenv MANPATH /usr/local/man:opt/SUNWspro/man:/$OPENWINHOME/\
    share/man:/opt/SUNWsamfs/man:/opt/SUNWfsmgr/man

8. Log in to the Sun StorEdge SAM-FS server and become superuser.

9. Use the `ps`(1) and `grep`(1) commands to make sure that the `rpcbind` service is running:

    # ps -ef | grep rpcbind

10. Examine the output from the preceding commands.

The output should contain a line similar to the following:

    root   269     1  0   Feb 08 ?        0:06 /usr/sbin/rpcbind

If `rpcbind` does not appear in the output, enter the following command to start the `rpcbind` service:

    # /usr/sbin/rpcbind

11. (Optional) Start the File System Manager (`fsmgmtd`) daemon.

If you did not choose to start the File System Manager daemon automatically during the installation process, do one of the following:

- Enter the following command to start the File System Manager daemon and have it restart automatically every time the daemon process dies. With this configuration, the daemon also automatically restarts at system reboot.

    # /opt/SUNWsamfs/sbin/fsmadm config -a

- Enter the following command if you want the File System Manager daemon to run only once and not automatically restart:

    # /opt/SUNWsamfs/sbin/fsmadm start

For more information, see the `fsmadm`(1M) man page.

12. (Optional) Give additional users access to File System Manager.

When you upgrade from version 2.0 or before, the `samadmin` account from the previous software version will be preserved, but the `samuser` account will be deleted. Logging in with the `samadmin` user name and password will give you full access to all File System Manager features.

By default, the `root` login also has privileges to perform all operations available from the File System Manager software. You can assign other users full or partial access to all File System Manager operations.

To give an additional user access to File System Manger, see To Add Users and Assigning Privilege Levels.

For information about using File System Manager see Using the File System Manager Software, or see the File System Manager online help.

##

Restoring the File System

The instructions in this section cover the tasks involved in restoring the Sun StorEdge SAM-FS environment after an upgrade.

### Restoring File Changes (`inquiry.conf` and `samst.conf`)

Sun Microsystems does not guarantee correct operation with peripherals other than those included in the `/opt/SUNWsamfs/examples/inquiry.conf` file supplied with the release. The installation script compares this file with an existing one, if any, in `/etc/opt/SUNWsamfs`. CODE EXAMPLE 4-5 shows the warning message issued if these files differ.

CODE EXAMPLE 4-5 Warning Message for Differing `inquiry.conf` Files
    inquiry.conf has been updated.
    /opt/SUNWsamfs/examples/inquiry.conf is the latest version;
    please add your changes and copy this file to
    /etc/opt/SUNWsamfs/inquiry.conf

If you have modified `/kernel/drv/samst.conf`, you need to merge any changes to it that might be needed for your configuration. The installation script compares this file with an existing one, if any, in `/kernel/drv/samst.conf`. The exact error message issued if the files differ depends on your Sun Solaris OS level. CODE EXAMPLE 4-6 shows the beginning of the warning message issued if these files differ.

CODE EXAMPLE 4-6 Warning Messages for Differing `samst.conf` Files
    samst.conf has been updated.
    /opt/SUNWsamfs/examples/samst.conf is the latest version;
    please add your changes and copy it to /kernel/drv/samst.conf

### Reinitializing and Verifying the File System

Complete the following tasks in order to reinitialize, and verify the configuration of, the Sun StorEdge SAM-FS file system.

#### Verifying the `mcf`, `archiver.cmd`, and `stager.cmd` Files

The following file exists on your Sun StorEdge SAM-FS server:

- `/etc/opt/SUNWsamfs/mcf`

The following additional files might also exist on your Sun StorEdge SAM-FS server:

- `/etc/opt/SUNWsamfs/archiver.cmd`

- `/etc/opt/SUNWsamfs/stager.cmd`

The procedures in this task show you how to verify the correctness of these files.

To Verify the `mcf` File

1. Enter the `sam-fsd`(1M) command.

2. Examine the output for errors, as follows:

- If the `mcf` file is free of syntax errors, the `sam-fsd`(1M) output includes information about the file systems, archiving, and other system information. If your `mcf` file contains syntax or other errors, however, the output is similar to that shown in CODE EXAMPLE 4-7.

CODE EXAMPLE 4-7 Example `sam-fsd` (1M) Output
    # sam-fsd
    13: /dev/dsk/c1t1d0s0   10      md      samfs1  on      /dev/rdsk/c1t1d0s0
     *** Error in line 13: Equipment name '/dev/dsk/c1t1d0s0' already in use by eq 10
    72: /dev/rmt/3cbn       45      ug      l1000   on
     *** Error in line 72: Equipment name '/dev/rmt/3cbn' already in use by eq 44
    2 errors in '/etc/opt/SUNWsamfs/mcf'
    sam-fsd: Read mcf /etc/opt/SUNWsamfs/mcf failed.

- If the `mcf` file has errors, refer to Setting Up the Environment Configuration and to the `mcf`(4) man page for information about how to create this file correctly.

Note - If you change the `mcf` file after the Sun StorEdge SAM-FS file system is in use, you must propagate the changes to the software. For information about propagating `mcf` file changes to the system, see the Sun StorEdge SAM-FS File System Configuration and Administration Guide.

To Verify the `archiver.cmd` File

Perform this task if you have an `archiver.cmd` file. If you do not have an `archiver.cmd` file and you are using the archiver's defaults, you do not need to perform this step.

Note - In software versions previous to 4U4, disk archiving was enabled in the `archiver.cmd` file using a `-disk_archive` parameter in the `params` section. This parameter is no longer used, and `archiver.cmd` files created with earlier software versions that use the `-disk_archive` parameter must be edited in order for archiving to work correctly in the 4U4 and later software. See the `archiver.cmd`(4) man page for details.

Enter the `archiver`(1M) `-lv` (lowercase L) command to verify the `archiver.cmd` file:

    # archiver -lv

The output from this command can be quite lengthy. Examine it to verify that the archiving directives are as expected. If you have questions, see Creating the archiver.cmd File, and see the `archiver.cmd`(4) man page.

### To Modify the `/etc/vfstab` File

Perform this task if you modified the `/etc/vfstab` file in Unmounting File Systems.

Edit this file again, and change the Mount at Boot field for all Sun StorEdge SAM-FS file systems from `no` to `yes` or `delay`.

### To Reinitialize and Restore the File Systems

In this task, you reinitialize the file systems and restore the saved data in the new file systems. This task completes the process initiated in Backing Up the File System. To accomplish this, use the `sammkfs`(1M) and `samfsrestore`(1M) commands on each file system.

| Caution - The Sun StorEdge SAM-FS 4U2 and later software does not allow you to initialize a file system with a version 1 superblock. The Sun StorEdge SAM-FS 4U2 or later file system enables file systems to be initialized only with the version 2 superblock. If you are upgrading from 4U0 using version 1 superblocks, be aware that using a 4U2 or later `sammkfs`(1M) command at this point reinitializes your file system with a version 2 superblock.

1. Issue the `samfsinfo`(1M) command and examine the output.

The output tells you the DAU size that was specified with the `sammkfs`(1M) command when the file system was created. The DAU size is in the `samfsinfo`(1M) output. You will use this DAU size in Step 2.

2. Use the `sammkfs`(1M) command to initialize a new Sun StorEdge SAM-FS file system.

The following example command reinitializes a file system named `samfs1` with a DAU size of 512 kilobytes:

    # sammkfs -a 512 samfs1

For more information about the options to the `sammkfs`(1M) command, see the `sammkfs`(1M) man page.

3. Use File System Manager or the `samfsrestore`(1M) command to restore the dumped data in the new file system.

For example, suppose you had a file system named `samfs1` (mounted at `/samfs1`) that you wanted to restore from files dumped to `samfs1.bak`, which existed outside of the Sun StorEdge SAM-FS file system. In this case, you would issue the following commands:

    # cd /samfs1
    # samfsrestore -f /save/samfs/samfs1.bak

### To Check the File System

Perform this task if you did not reinitialize and restore the file system as just described.

Use the `samfsck`(1M) command to check your existing file systems for inconsistencies.

### Mounting the File System

You can mount the Sun StorEdge SAM-FS file system using File System Manger or the CLI.

To Mount the File System Using File System Manager

1. From the Servers page, click the name of the server on which the file system is located.

The File System Summary page is displayed.

2. Select the radio button next to the file system that you want to mount.

3. From the Operations menu, choose Mount.

To Mount the File System Using the CLI

Issue the `mount`(1M) command.

In the following example, `samfs1` is the name of the file system to be mounted:

    # mount samfs1

### Recompiling API-Dependent Applications

File headers, the calling sequence, and other elements of the Sun StorEdge SAM-FS application programming interface (API) can change from release to release. If you are running applications the use the API, you should recompile them all at this time.

| Caution - Failure to recompile API-dependent applications at this point can cause your applications to generate unexpected results.

##

Upgrading Hardware

The following sections describe the steps that must be taken when upgrading the hardware in a Sun StorEdge SAM-FS environment.

### Preparing for a Hardware Device Upgrade

Whether upgrading a server, adding a new tape drive, adding an automated library, or installing a different drive into an existing automated library, it is best to plan in advance. This section prepares you for hardware upgrades to devices within your environment.

#### General Prerequisites

Before starting the upgrade process, be sure to do the following:

- Determine whether the hardware addition or change requires a software upgrade from Sun Microsystems.

Examples of changes that do not require a software upgrade include additions to memory and increases in disk cache. Examples of changes that require a software upgrade include changes to the class of your server or significant increases in storage capacity.

- If you are switching from a SPARC to an AMD server platform (or from AMD to SPARC), you must take precautions to prevent loss of data. See Switching Between SPARC and AMD Platforms for details.

- Read the hardware manufacturer's installation instructions carefully. Also read the documentation on adding hardware in your Solaris OS system administrator documentation.

- Check the Equipment Ordinal values in your old and new `mcf` files. For information about the `mcf` file, see the `mcf`(4) man page.

- Decide whether the backup copies you have on hand are sufficient. For information about backing up your data and metadata, see Backing Up the File System.

- In Sun StorEdge SAM-FS environments, the `samfsdump`(1M) command dumps all metadata. You must ensure that all files that need to be archived have an archive copy. Use the `archive_audit`(1) command on each Sun StorEdge SAM-FS file system to see which files do not have an archive copy. In the following example, `/sam` is the mount point.

    # archive_audit /sam

- Ensure that the system is quiet, with no users logged in.

- Ensure that the archiver is in `wait` mode. The archiver must be in `wait` mode, and not running, during an upgrade.

You can idle the archiver in one of the following ways:

- By inserting a `wait` directive into the `/etc/opt/SUNWsamfs/archiver.cmd` file. For more information about the `wait` directive and the `archiver.cmd` file, see the `archiver.cmd`(4) man page.

- By using the `samu`(1M) operator utility.

- By issuing the following command:

    # samcmd aridle

For more information, see the `samcmd`(1M) man page.

#### Switching Between SPARC and AMD Platforms

The following are some important considerations if you are combining or changing between SPARC and x86 hardware platforms:

- Sun StorEdge QFS and Sun StorEdge SAM-FS software is supported only for the Solaris 10 OS on x64 platforms (AMD64 architecture), not for the EM64T architecture. With the exception of the Sun StorEdge QFS shared Linux client, it is also not supported for any 32-bit x86 architectures.

- All functionality that is supported by Sun StorEdge QFS and Sun StorEdge SAM-FS on the SPARC platform is also supported on the x64 platform except for the following:

- The ADIC/Grau, Fujitsu LMF, IBM3494, and Sony network attached libraries are not supported on x64 platforms. StorageTek (STK) ACSLS-attached automated libraries are supported on x64 platforms.

- Optical (MO and UDO) storage libraries and drives are not supported on x64 platforms.

- SANergy software is not supported on x64 platforms.

- The multireader file system mount options are not supported in mixed architecture environments (SPARC and x64).

- EFI labels are required on all shared disks if your Sun StorEdge QFS shared file system configuration contains both the Solaris 10 OS on x64 platforms and the Solaris 9 or Solaris 10 OS on SPARC platforms. See Configuring EFI Labels for Shared x64 and SPARC Volumes for information on relabeling disks.

- You can add Sun StorEdge QFS shared file system Linux clients to Solaris SPARC configurations that are using SMI VTOC8 disk labels and to Solaris AMD64 configurations that are using SMI VTOC16 disk labels. You can also add Sun StorEdge QFS shared file system Linux clients to these configurations when they are using EFI disk labels, but you may need to rebuild the Linux kernel for this capability. This is dependent on the particular Linux distribution. See the Linux README on the Sun StorEdge QFS Linux client software CD for more details.

- You must exercise caution when accessing the same SAN attached storage from a Solaris environment on both SPARC and x64 platforms. The Solaris OS on x64 platforms cannot interpret the SMI VTOC8 disk label created by the Solaris OS on SPARC platforms, and the Solaris OS on SPARC platforms cannot interpret the SMI VTOC16 disk label created by the Solaris OS on x64. This can make it appear as though a disk is unlabeled, when in fact it is labeled and in use by a platform of a different architecture type. For example, a disk that is labeled with SMI VTOC8 may have mounted partitions in use by Solaris on a SPARC platform, but will appear as unlabeled when viewed with the `format`(1M) partition command by Solaris on an x64 platform. If you make the mistake of running `fdisk`(1M) as prompted by the `format`(1M) command, you will destroy the contents of that disk.

- You cannot change the architecture type of the server responsible for control of the file system metadata operations (i.e. the server that was used to create the file system with the `sammkfs`(1M) command). For a Sun StorEdge QFS standalone file system, this means that you cannot mount the file system on a server that has a different architecture type from the one that created it. For a Sun StorEdge QFS shared file system, this means that you cannot change the architecture type of the metadata server or any potential metadata servers. This is because the different architectures use different byte-ordering schemes (endianness). However, you can migrate data from one architecture type to the other by copying the file system to temporary storage using either `qfsdump`(1M) or `samfsdump`(1M), re-creating the file system using `sammkfs`(1M), and then repopulating the file system with `qfsrestore`(1M) or `samfsrestore`(1M).

- The Sun StorEdge Traffic Manager I/O multipathing feature (MPxIO) is disabled by default for the Solaris 9 OS and 10 OS on the SPARC platform and enabled by default for the Solaris 10 OS on x64. This feature should be configured the same way for all systems in your Sun StorEdge QFS shared file system configuration. It is configured in `/kernel/drv/scsi_vhci.conf` for the Solaris 9 OS and in `/kernel/drv/fp.conf` for the Solaris 10 OS.

- In a Sun StorEdge QFS shared file system environment, a configuration error will be generated if you have potential metadata servers of different architecture types (SPARC and x64) defined in the `/etc/opt/SUNWsamfs/hosts.fs` file.

##### Configuring EFI Labels for Shared x64 and SPARC Volumes

| Caution - Relabeling a disk will destroy the contents of that disk.

Use the Solaris `prtvtoc`(1M) command to determine whether a disk contains SMI or EFI labels. Under the Dimensions section of the output, SMI labels list the number of accessible cylinders, whereas EFI labels list the number of accessible sectors.

To convert disk labels from the default SMI VTOC8 to EFI, copy the file system to temporary storage using `qfsdump`(1M) or `samfsdump`(1M), relabel the disks with EFI labels using the Solaris `format -e` command, re-create the file system using `sammkfs`(1M), and repopulate the file system with `qfsrestore`(1M) or `samfsrestore`(1M).

When using the Solaris `format -e` command to create EFI labels, you can select the partition command from the menu to create and modify partitions (slices). When doing this, you must specify a tag id name of `usr`, rather than `stand` or `unassigned`, for EFI labels.

Note that EFI labels reserve the first 34 sectors, which misaligns Sun RAID-5 storage from a performance perspective. Unless you realign the storage, you will incur a RAID-5 read/modify/write performance penalty when writing. You can avoid this performance penalty by selecting the proper starting sector for all disk partitions for your particular storage configuration. For example, an 8+P Sun StorEdge T3 array with a 64K block size should have starting sectors that are multiples of 1024 for all disk slices ((8 * 64 * 1024) / 512 = 1024). Similarly, a 5+P Sun StorEdge FC 3510 array with a 128K block size should have starting sectors that are multiples of 1280 for all disk slices ((5 * 128 * 1024) / 512 = 1280).

#### Verifying Drive Order

When the Sun StorEdge SAM-FS system is initialized after the addition of a new library, 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.

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.

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 file entry match the drive that was just loaded with the cartridge.

Usually, the manufacturer ships the automated library with ascending SCSI IDs on the drives. If you cannot determine a drive number, you can 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.

### Performing Hardware Upgrades

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

- To Add Slots in an Automated Library

- To Replace or Upgrade a Library

- Upgrading DLT Tape Drives

- Switching Between SPARC and AMD Platforms

To Add Slots in an Automated Library

To increase the number of cartridge slots managed by the Sun StorEdge SAM-FS system, follow these steps.

1. Use the `samcmd`(1M) `unload` command to unload the library catalog:

    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 become empty and the historian's `v` display fill up with the VSNs that used to be in the automated library.

2. Stop Sun StorEdge SAM-FS operations.

For instructions, see Stopping the Sun StorEdge SAM-FS Software.

3. Power off the host system and the library according to the manufacturer's suggested procedure.

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

5. Power on the host system using your normal startup procedure.

6. Start the Sun StorEdge SAM-FS system.

For instructions, see Reinitializing and Verifying the File System.

To Replace or Upgrade a Library

Before disconnecting one automated library and installing a different automated library, prepare for the upgrade as described in Preparing for a Hardware Device Upgrade.

1. Use the `samcmd`(1M) command to unload the library catalog:

    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 become empty and the historian's `v` display fill up with the VSNs that used to be in the automated library.

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

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 to 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 to 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. Use the following command to verify that the host system identifies the new automated library:

    > probe-scsi-all

Make sure that the new automated library and its drives are displayed before you proceed. If these devices are not identified, the automated library and its drives probably have a connection problem.

12. Issue the following command to boot the system 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.

14. If you are adding new equipment, create new `/dev/samst` entries by using the following command:

    # samdev

15. Initialize the Sun StorEdge SAM-FS system by mounting the file system or by issuing the following command:

    # samd start

The system runs an audit on the library to update the library catalog. If the audit completes without problems, proceed to the next step. If there are problems in the audit, see Verifying Drive Order.

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.

#### Upgrading DLT Tape Drives

To take advantage of high-density and fast 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 before starting the Sun StorEdge SAM-FS software.

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.

- Low-density tapes can coexist with high-density tapes and tape drives. You can continue to read and write to the low-density tapes using a high-density drive.

- To take full advantage of the high-density DLT tapes, you might want to recycle existing files and migrate them to a high-density tape. You can accomplish this by marking all the low-density tapes as read-only and then marking these tapes to be recycled. For information on recycling tape, see the Sun StorEdge SAM-FS Storage and Archive Management Guide.

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

To Upgrade Tape Drives

1. If you determine that your current dump files are not sufficient, perform a `samfsdump`(1M) on your file systems.

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 Configuring Storage Devices.

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. Use the following command to verify that the host system identifies the new drives:

    > probe-scsi-all

Make sure that the automated library and the new drives are displayed before you proceed. If these devices do not appear, a connection problem probably exists.

7. Issue the following command to boot the system with the new configuration:

    > boot -rv

8. If the target numbers of the drives or the ordering or number of the drives in the automated library have changed, modify the `/etc/opt/SUNWsamfs/mcf` file to reflect the new configuration.

9. (Optional) Create new `/dev/samst` entries for the new equipment by using 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.

##

Upgrading the Solaris OS

The following section describes how to upgrade the Solaris OS when running the Sun StorEdge SAM-FS software.

### To Upgrade the Solaris OS in a Sun StorEdge SAM-FS Environment

Many of the steps involved in upgrading your Solaris OS level are identical to the steps involved in upgrading your Sun StorEdge SAM-FS environment.

1. Obtain the Sun StorEdge SAM-FS and Solaris OS software upgrades.

Sun StorEdge SAM-FS software supports various levels of the Solaris OS. You should not reinstall your old Sun StorEdge SAM-FS software on your newly upgraded Solaris OS unless you are sure they are compatible.

Contact your application service provider or Sun Microsystems to obtain new copies of the software.

2. Back up all site-customized system files and configuration files.

These files include `mcf`, `archiver.cmd`, `defaults.conf`, `samfs.cmd`,`inquiry.conf`, and so on. Back up these files for all file systems in your Sun StorEdge SAM-FS environment.

3. Ensure that each affected file system is backed up.

The file systems should be backed up regularly according to your site's policies as described in Backing Up Data. If you are comfortable with the backup files that already exist for your file systems, there is no need to back them up again now.

The `samfsdump`(1M) command issues warnings when creating the dump file if it encounters unarchived files in the file system. If warnings are issued, you must archive these files before unmounting the file systems.

4. Unmount the file systems.

For instructions, see Unmounting File Systems.

5. Issue the `samd`(1M) `stop` command to stop all archiving and Sun StorEdge SAM-FS activity:

    # samd stop

6. Remove the existing Sun StorEdge SAM-FS software.

You must remove all existing Sun StorEdge SAM-FS packages before installing either the new packages or the new operating system level. For instructions see Removing the Existing Software.

7. Upgrade the Solaris OS.

Install the new Solaris OS revision using the corresponding Sun Solaris upgrade procedures.

8. Add the upgrade packages that you obtained in Step 1.

The Sun StorEdge SAM-FS software packages use the Solaris OS packaging utilities for adding and deleting software. You must be logged in as superuser to make changes to software packages. The `pkgadd`(1M) command prompts you to confirm various actions necessary to upgrade the Sun StorEdge SAM-FS package. For instructions, see Adding the Upgrade Packages.

9. (Optional) Update the `mcf` file.

If device names have changed, it might be necessary to update the `mcf` file to match the new device names. Verify the new device names, and then follow the procedure in Restoring the File System.

10. If your `/etc/vfstab` file does not have `yes` in the Mount at Boot field, mount the file systems.

Use the procedure described in Mounting the File System.

Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.