| 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 4 |
|
Sun StorEdge QFS Upgrade Procedure |
This chapter describes upgrading a server to a new release of the Sun StorEdge software. Use this procedure if you are upgrading your Sun StorEdge QFS file system. 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 QFS 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 that pertain to 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 QFS 3.5.0 system or a Sun QFS 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 qfsdump(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 4-1 shows using the samfsinfo(1M) command to retrieve information about the qfs2 file system. The second line of output indicates that this file system is using a version 2 superblock.
The Sun StorEdge QFS 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 QFS 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 qfsrestore(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 4.1 Sun StorEdge QFS file system:
|
1. Become superuser from a console connection. (Optional)
If you have not already logged in as root, do so now.
2. Use the boot(1M) command to boot the system in single-user mode.
3. Use the mount(1M) command to mount the Sun StorEdge QFS file system.
4. Use the qfsdump(1M) command to back up the file data and metadata of each Sun StorEdge QFS file system.
The qfsdump(1M) command dumps file names, inode information, and file data. The destination of the qfsdump(1M) output (generally a file) must be as large or larger than the Sun StorEdge QFS file system you are backing up. The destination location must have enough space (disk or tape) to hold the amount of file data and metadata you are dumping. For more information on using the qfsdump(1M) command, see Establishing Periodic Dumps Using qfsdump(1M) or see the qfsdump(1M) man page.
Dump each file system to a location outside of the Sun StorEdge QFS file system. For more information, see the qfsdump(1M) man page.
For example, if you have a file system named qfs1 (mounted at /qfs1) that you want to back up. Your choices are as follows:
a. You can write the qfsdump(1M) output to a tape device.
CODE EXAMPLE 4-2 shows how to write to a tape in device /dev/rmt/1cbn.
b. You can write the qfsdump(1M) output to a file in a UFS file system
CODE EXAMPLE 4-3 shows how to write to a file in a UFS file system.
# cd /qfs1 # qfsdump -f /save/qfs/qfs1.bak |
c. You can intialize a new Sun StorEdge QFS file system, using a Sun StorEdge QFS 4.1 or later release, and perform the qfsrestore(1M) directly into that new Sun StorEdge QFS file system.
This alternative is applicable only if you already have the Sun StorEdge QFS software installed and operational as a file system somewhere in your environment. Pursuing this alternative assumes that you want to use the features supported by the Sun StorEdge QFS 4.1 release and the version 2 superblock.
For example, assume that you want to write the dump file into a second Sun StorEdge QFS file system called qfs2 (mounted at /qfs2). Make sure that you initialized the qfs2 file system using Sun StorEdge QFS 4.1 software. CODE EXAMPLE 4-4 shows how to accomplish this using commands.
# mount /qfs2 # cd /qfs1 # qfsdump -f - | (cd /qfs2; qfsrestore -f -) |
5. Repeat these steps for each Sun StorEdge QFS file system in your environment.
For more information on backing up your file systems, see the Sun QFS, Sun SAM-FS, and Sun SAM-QFS Disaster Recovery Guide.
Perform this procedure if your Sun StorEdge QFS file systems are NFS shared file systems.
|
Use the unshare(1M) command on the Sun StorEdge QFS file system.
For example, the following command unshares the qfs1 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 to Removing Existing Sun StorEdge QFS Software.
|
Using the umount(1M) command, unmount each Sun StorEdge QFS 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 qfs1 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 QFS file system.
|
For all Sun StorEdge QFS file systems, change the Mount at Boot field from yes or delay to no.
The following section describes how to remove Sun StorEdge QFS software from a release prior to 4.1.
|
1. Use the pkginfo(1) command to determine which Sun StorEdge QFS software packages are installed on your system.
2. Use the pkgrm(1M) command to remove the existing Sun StorEdge QFS software.
You must remove all existing Sun StorEdge QFS packages before installing the new packages. If you are using any optional Sun StorEdge QFS packages, you should make sure that you remove these packages before removing the main SUNWqfs package. The install script prompts you to confirm several of the removal steps.
The following example command removes the SUNWcqfs, the SUNWfqfs, and the SUNWjqfs localized packages:
|
Note - The SUNWqfs 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 QFS software packages are installed on your system.
2. Use the pkgrm(1M) command to remove the existing Sun StorEdge QFS software.
You must remove all existing Sun StorEdge QFS packages before installing the new packages. If you are using any optional Sun StorEdge QFS packages, make sure that you remove these packages before removing the main LSCqfs package. The install script prompts you to confirm several of the removal steps.
The following example command removes the LSCdoc package and the LSCqfs package:
The Sun StorEdge QFS 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 Sun StorEdge QFS package.
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 SUNWqfsr and SUNWqfsu packages.
3. Enter yes or y as the answer to each of the questions.
A license key is required to run the Sun StorEdge QFS software. For information on license keys, see Obtaining a Software License Key.
The Sun StorEdge QFS file system uses an encrypted license key. The license key consists of an encoded alphanumeric string.
|
Perform this procedure if you are upgrading from the QFS 3.5.0 release.
You do not need to perform this procedure if you are upgrading from the Sun QFS 4.0 release. 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 QFS that enables you to configure many of the components in a Sun StorEdge QFS 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 QFS server:
The procedures in this task show you how to verify the correctness of these files.
|
1. Use the samd(1M) config to initialize the Sun StorEdge QFS software.
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 4-5, return to Updating the License Keys.
|
Enter the sam-fsd(1M) command to verify the mcf file.
Examine the output for errors, as follows:
If your mcf file has errors, refer to Defining the Sun StorEdge QFS Configuration by Creating the mcf File and to the mcf(4) man page for information on how to create this file correctly.
Perform this task if you modified the /etc/vfstab file in Unmounting the File Systems.
|
Edit this file again, and change the Mount at Boot field for all Sun StorEdge QFS 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 Existing File Systems (Optional). To accomplish this, use the sammkfs(1M) and qfsrestore(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 QFS file system.
The following example sammkfs(1M) command reinitializes a file system named qfs1 with Sun StorEdge QFS 4.1 feature capabilities:
For more information on the options to the sammkfs(1M) command, see the sammkfs(1M) man page.
3. Use the qfsrestore(1M) command to restore the dumped data into the new file system.
For example, the commands in CODE EXAMPLE 4-7 assume that you have a file system named qfs1 (mounted at /qfs1) that you want to back up from files dumped to qfs1.bak, which exists outside of the Sun StorEdge QFS file system:
# cd /qfs1 # qfsrestore -f /save/qfs/qfs1.bak |
Perform this task if you did not perform Reinitializing and Restoring the File Systems (Optional).
Use the samfsck(1M) command to check your existing file systems for inconsistancies.
Do this for each Sun StorEdge QFS 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, qfs1 is the name of the file system to be mounted:
If you are running applications that use the Sun StorEdge QFS 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 Each File System