| Sun StorEdge QFS & Sun StorEdge SAM-FS Software Installation & Configuration Guide |    
|
| Sun StorEdge QFS & Sun StorEdge SAM-FS Software Installation & Configuration Guide |
|
| C H A P T E R 6 |
|
Sun StorEdge SAM-FS Upgrade Procedure |
This chapter explains how to upgrade a server to a new release of the Sun StorEdge SAM-FS software. Use this procedure if you are upgrading your Sun StorEdge SAM-FS environment. You must perform all the tasks in this chapter as superuser.
The main tasks, which must be completed in order, are as follows:
The chapter called System Requirements and Preinstallation Tasks describes the items you need to verify before you upgrade to the Sun StorEdge SAM-FS 4.1 release. If you have not yet completed the system verification steps, complete them now before you proceed. The steps described in that chapter for verifying the system requirements for your upgrade to 4.1 are as follows:
Perform this procedure if you are currently using a version 1 superblock with either a SAM-FS 3.5.0 system or a Sun SAM-FS 4.0 system and you want to reinitialize your file systems with a version 2 superblock. In Reinitializing and Restoring the File Systems (Optional), you reinitialize the file systems and restore your data.
Perform this task as a precautionary measure if you suspect that your current samfsdump(1M) file is incorrect or outdated.
The following sections explain the differences between these two superblocks and present the procedure for backing up your file systems:
CODE EXAMPLE 6-1 shows using the samfsinfo(1M) command to retrieve information about the samfs4 file system. The second line of output indicates that this file system is using a version 2 superblock.
The Sun StorEdge SAM-FS 4.0 and 4.1 releases support both a version 1 superblock and a version 2 superblock. Only the version 2 superblock supports the following features:
The Sun StorEdge SAM-FS 4.1 release supports 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 dump file created in this installation task.
The following paragraphs describe the effects of these superblocks when upgrading to the Sun StorEdge SAM-FS file system:
|
1. Become superuser from a console connection. (Optional)
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:
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.
Examine this command's output. The files in this output are those that have not been archived. If you want any of these files to appear in the dump file, archive them now before you proceed to the next step. Alternatively, you can use the -u option to the samfsdump(1M) command to dump unarchived data if you suspect some files have not yet been archived. The -u option can create very large dump files, however, so you need to weigh space considerations when using this option.
3. Use the samfsdump(1M) command to back up each Sun StorEdge SAM-FS file system's metadata.
Dump each file system's metadata to a location outside the Sun StorEdge SAM-FS file system.
CODE EXAMPLE 6-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.
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 QFS, Sun SAM-FS, and Sun SAM-QFS Disaster Recovery Guide.
|
1. Use the samcmd(1M) idle command to idle the drives in your system.
This step enables the archiver, stager, and other processes to complete current operations. Use this command in the following format:
For eq, specify the Equipment Ordinal of a device 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.
Repeat this step for each removable media drive eq configured in your mcf file:
2. Use the samcmd(1M) aridle command to idle the archiver. (Optional)
Perform this step only if you are upgrading from a Sun StorEdge SAM-FS 4.0 system.
3. Issue the samd(1M) stop command to stop all operations.
Perform this procedure 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:
There are several ways to unmount a file system. Any of the following methods can accomplish this task. The easiest method is presented first. After the file system is unmounted, you can proceed toRemoving Existing Sun StorEdge SAM-FS Software.
|
Using the umount(1M) command, unmount each Sun StorEdge SAM-FS file system.
If you are unmounting a file system from a Solaris 8 or 9 OS, you can use the -f option to the umount(1M) command. The -f option forces a file system to unmount.
|
If umount(1M) is not successful, it might be because you or another user are using files or because you or another user have changed to directories in the file system.
1. Use the fuser(1M) command to determine whether or not any processes are still busy.
For example, the following command queries the samfs1 file system:
2. If any processes are still busy, use the kill(1M) command to terminate them.
3. Using the umount(1M) command, unmount each Sun StorEdge SAM-FS file system.
|
For all Sun StorEdge SAM-FS file systems, change the Mount at Boot field from yes or delay to no.
The following section describes how to remove Sun StorEdge SAM-FS software from a release prior to 4.1.
|
1. Use the pkginfo(1) command to determine which Sun StorEdge SAM-FS packages are installed on your system.
2. Use the pkgrm(1M) command to remove the existing Sun StorEdge SAM-FS software.
You must remove all existing Sun StorEdge SAM-FS packages before installing the new packages. 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 package. The install script prompts you to confirm several of the removal steps.
The following example command removes the SUNWcsamf, the SUNWfsamf, and the SUNWjsamf localized packages in addition to the SUNWsamfs package:
|
Note - The SUNWsamfs package must be the last package removed. The 4.1 release does not include any localized software packages. |
|
1. Use the pkginfo(1) command to determine which Sun StorEdge SAM-FS software packages are installed on your system.
2. Use the pkgrm(1M) command to remove the existing Sun StorEdge SAM-FS software.
You must remove all existing Sun StorEdge SAM-FS packages before installing the new packages. If you are using any optional Sun StorEdge SAM-FS packages, make sure that you remove these packages before you remove the main LSCsamfs package. The install script prompts you to confirm several of the removal steps.
The following example removes all of the SAM-FS 3.5.0 packages:
|
Note - The LSCsamfs package must be the last package removed. |
As part of the installation process, the system copies the existing mcf file and the catalog files to /etc/opt/SUNWsamfs/samfs.old.date.
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 or not you want to continue with the installation. You can go to another window and copy the files you want to save to an alternate location.
|
1. Use the cd(1) command to change to the directory where the software package release files reside.
When you completed your preinstallation tasks, you obtained the release files as described in Obtaining the Release Files. Use the cd(1) command to change to the directory that contains the release files. Changing to the appropriate directory differs, depending on your release media, as follows:
2. Use the pkgadd(1M) command to upgrade the SUNWsamfsr and SUNWsamfsu packages.
3. Enter yes or y as the answer to each of the questions.
When you install SUNWsamfsr and SUNWsamfsu, the system asks you if you want 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.
4. Examine /tmp/SAM_install.log .
File /tmp/SAM_install.log is the Sun StorEdge SAM-FS log file.
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 installed properly, the following message appears:
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 6-3 shows the warning message issued if these files differ.
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 6-4 shows the beginning of the warning message issued if these files differ.
A license key is required to run the Sun StorEdge SAM-FS software. For information on license keys, see Obtaining a Software License Key.
The Sun StorEdge SAM-FS software uses encrypted license keys. The license keys consist of encoded alphanumeric strings. You receive one or more license keys depending on the system configuration and the products being licensed.
|
Perform this procedure under the following circumstances:
You do not need to perform this procedure if you are upgrading from the Sun SAM-FS 4.0 release to the Sun StorEdge SAM-FS 4.1 release with the same equipment that you used in 4.0. The system copies your 4.0 license to the correct location when the upgrade is complete.
1. Verify whether the license file exists.
The license file is as follows:
/etc/opt/SUNWsamfs/LICENSE.4.1
2. If the /etc/opt/SUNWsamfs/LICENSE.4.1 file does not exist, create it.
3. Starting in column one, place the license key you have obtained from your ASP or from Sun Microsystems on the first line in the /etc/opt/SUNWsamfs/LICENSE.4.1 file.
The key must start in column one. No other keywords, host IDs, comments, or other information can appear in the /etc/opt/SUNWsamfs/LICENSE.4.1 file.
The license keys allow the system to run indefinitely unless you were issued a temporary license. Use the samcmd(1M) l command to determine whether you were issued a temporary license.
Perform this step if you want to be able to use the SAM-QFS Manager.
The SAM-QFS Manager is an online interface to Sun StorEdge SAM-FS 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.
For information on enabling the SAM-QFS Manager, see Enabling the SAM-QFS Manager (Optional).
The following files exist on your Sun StorEdge SAM-FS server:
The following additional files can also exist on your Sun StorEdge SAM-FS server:
The procedures in this task show you how to verify the correctness of these files.
|
1. Use the samd(1M) config command to initialize the Sun StorEdge SAM-FS environment.
2. Enter the samcmd(1M) l (lowercase L) command to verify the license file.
The samcmd(1M) output includes information on features that are enabled. If the output you receive is not similar to that shown in CODE EXAMPLE 6-5, return to Updating the License Keys.
|
Enter the sam-fsd(1M) command to verify the mcf file.
If your mcf file is free from 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 6-6.
If your mcf file has errors, refer to Defining the Sun StorEdge SAM-FS Configuration by Creating the mcf File and to the mcf(4) man page for information on how to create this file correctly.
|
Perform this procedure only if you are upgrading from Sun StorEdge SAM-FS 3.5.0 to Sun StorEdge SAM-FS 4.1.
1. Examine your archiver.cmd and stager.cmd files and look for tracing directives.
If tracing is implemented in your archiver.cmd file or stager.cmd file, edit these files now to remove the tracing directives. All system tracing in Sun StorEdge SAM-FS 4.1 is implemented in the defaults.conf file. Archiving and tracing are inhibited if tracing directives are present in the archiver.cmd file or stager.cmd file on a 4.1 system. For more information about these files, see the archiver.cmd(4), stager.cmd(4), and defaults.conf(4) man pages.
2. Edit your archiver.cmd and stager.cmd files to remove all directives that start with trace =.
3. Edit your defaults.conf file to reenable tracing.
For information on how to enable tracing, see the defaults.conf(4) man page.
|
Perform this step 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.
Enter the archiver(1M) -lv (lowercase L) command to verify the archiver.cmd file. (Optional)
The output from this command can be quite lengthly. Examine it and verify that the archiving directives are as expected. If you have questions, see Creating the archiver.cmd File (Optional) and see the archiver.cmd(4) man page.
If you modified the /etc/vfstab file in Unmounting the File System, you must complete this task.
|
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.
In this task, you reinitialize your file systems and restore the saved data into the new file systems. This task completes the process initiated in Backing Up Each File System (Optional). To accomplish this, use the sammkfs(1M) and samfsrestore(1M) commands on each file system.
|
1. Use the samfsinfo(1M) command to retrieve information on the file system.
You can examine the output from the samfsinfo(1M) command to determine the DAU size specified on the sammkfs(1M) command when the file system was created. The DAU size is in the samfsinfo(1M) output. Use this DAU size again when you perform Step 2.
2. Use the sammkfs(1M) command to initialize a new Sun StorEdge SAM-FS file system.
The following example sammkfs(1M) command reinitializes a file system named samfs1 with Sun StorEdge SAM-FS 4.1 feature capabilities.
For more information on the options to the sammkfs(1M) command, see the sammkfs(1M) man page.
3. Use the samfsrestore(1M) command to restore the dumped data into the new file system.
CODE EXAMPLE 6-7 assumes that you have a file system named samfs1 (mounted at /samfs1) that you want to back up from files dumped to samfs1.bak, which exists outside of the Sun StorEdge SAM-FS file system.
If you did not perform Reinitializing and Restoring the File Systems (Optional), you are encouraged to complete this task.
Use the samfsck(1M) command to check your existing file systems for inconsistancies.
Do this for each Sun StorEdge SAM-FS file system.
Use the mount(1M) command to mount your Sun StorEdge QFS file system.
|
Use the mount(1M) command to mount the file systems.
In the following example, samfs1 is the name of the file system to be mounted:
If you are running applications that use the Sun StorEdge SAM-FS application programming interface (API), you need to complete this task.
Because file headers, the calling sequence, and other elements of the API can change from release to release, you should recompile all applications that depend on the API at this time.
|
Caution - Failure to recompile API-dependent applications at this point can cause your applications to generate unexpected results. |
| Sun StorEdge QFS & Sun StorEdge SAM-FS Software Installation & Configuration Guide | 817-4092-10 |
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.
To Back Up File Systems