| Sun StorageTek QFS Installation and Upgrade Guide |    
|
| Sun StorageTek QFS Installation and Upgrade Guide |
|
| C H A P T E R 5 |
|
Upgrading Sun StorageTek QFS |
This chapter describes the procedures for upgrading a server to a new release of the Sun StorageTek QFS software. Use these procedures if you are upgrading your Sun StorageTek QFS file system. You must perform all the tasks in this chapter as superuser.
This chapter contains the following sections:
Follow the instructions in this section to prepare for a Sun StorageTek QFS upgrade.
When it comes time to upgrade the host system being used for the file system, consider the following:
If you are about to add or change disks, controllers, or other equipment in your environment, it can be difficult to correct or regenerate all the file system descriptions in the mcf file. The samfsconfig(1M) command can help you by generating information about your file system and file system components after you make these changes.
The samfsconfig(1M) command examines the devices you specify, determines whether any of them have Sun StorageTek QFS superblocks on them, and writes this information to stdout. It uses information from the discovered superblocks and aggregates the devices into a format similar to an mcf file. You can save this format and edit it to re-create a damaged, missing, or incorrect mcf file.
The command can retrieve the Family Set number of the base device (the file system itself), the file system type (ma or ms), and whether the file system is a Sun StorageTek QFS shared file system.
Irregularities are flagged with one of the following:
The following examples show output from the samfsconfig(1M) command.
In this example, the system administrator has put a list of device names into a file. These device names were for devices that were not accounted for in the environment and that the system administrator therefore wanted to examine for Sun StorageTek QFS family sets. The results displayed in CODE EXAMPLE 5-1 show some old fragments of family sets and several complete instances.
In the output shown in CODE EXAMPLE 5-2, the devices flagged with a greater-than sign (>) are duplicated. The s0 slice starts at the start of disk, as does the whole disk (s2) slice. This is the style of output obtained in a Solaris 9 OS.
This section prepares you for hardware upgrades to devices within your environment.
Before starting the upgrade process, be sure to do the following:
Examples of changes that require a software upgrade include changes to the class of your server or significant increases in storage capacity. Examples of changes that do not require a software upgrade include additions to memory and increases in disk cache.
You can idle the archiver in one of the following ways:
For more information, see the samcmd(1M) man page.
The following are some important considerations if you are combining or changing between SPARC and x86 hardware platforms:
|
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 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 whenever 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 StorageTek 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 StorageTek 3510 FC array with a 128K block size should have starting sectors that are multiples of 1280 for all disk slices ((5 * 128 * 1024) / 512 = 1280).
Back up your existing file systems if the following conditions exist:
The following subsections explain the differences between these two superblocks and present the procedure for backing up your file systems:
CODE EXAMPLE 5-3 shows the samfsinfo(1M) command you use to retrieve information about the qfs2 file system. The second line of output indicates that this file system is using a version 2 superblock.
Sun StorageTek QFS 4U1 and later releases support both a version 1 superblock and a version 2 superblock. Only the version 2 superblock supports the following features:
The Sun StorageTek QFS 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 qfsrestore(1M) command to restore files to the new file system from the dump file created during the backup process.
If you are upgrading from a Sun QFS 4U0 system, note that the Sun StorageTek QFS 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.
Follow these steps for each Sun StorageTek QFS file system in your environment.
1. Become superuser from a console connection.
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 StorageTek QFS file system.
4. Use the qfsdump(1M) command to back up the file data and metadata of the Sun StorageTek 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 as or larger than the Sun StorageTek QFS file system that you are backing up. The destination location (disk or tape) must have enough space to hold the amount of file data and metadata that you are dumping. For more information about using the qfsdump(1M) command, see Setting Up Dump Files or see the qfsdump(1M) man page.
Dump each file system to a location outside of the Sun StorageTek 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:
CODE EXAMPLE 5-4 shows how to write to a tape in device /dev/rmt/1cbn.
CODE EXAMPLE 5-5 shows how to write to a file in a UFS.
# cd /qfs1 # qfsdump -f /save/qfs/qfs1.bak |
This alternative is applicable only if you already have the Sun StorageTek QFS software installed and operational as a file system somewhere in your environment. This alternative also assumes that you want to use the features supported by the Sun StorageTek QFS 4U2 or later release and the version 2 superblock.
For example, assume that you want to write the dump file into a second Sun StorageTek QFS file system called qfs2 (mounted at /qfs2) and that you initialized the qfs2 file system using Sun StorageTek QFS 4U2 or later software. CODE EXAMPLE 5-6 shows how to accomplish this using commands.
# mount /qfs2 # cd /qfs1 # qfsdump -f - | (cd /qfs2; qfsrestore -f -) |
For more information about backing up your file systems, see Setting Up Dump Files.
|
Perform this task if your Sun StorageTek QFS file systems are NFS shared file systems.
Use the unshare(1M) command on the Sun StorageTek QFS file system.
For example, the following command unshares the qfs1 file system:
You can unmount a file system using any of the following methods described in this section. After the file system is unmounted, you can proceed to Removing Existing Sun StorageTek QFS Software.
|
Note - To unmount a Sun StorageTek QFS shared file system, follow the instructions in the Sun StorageTek QFS File System Configuration and Administration Guide. |
1. From the Servers menu, select 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.
Use the umount(1M) command to unmount each Sun StorageTek QFS file system.
If necessary, 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 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 qfs1 file system:
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 StorageTek QFS file system.
For all Sun StorageTek QFS file systems, change the Mount at Boot field from yes or delay to no.
Use the pkgrm(1M) command to remove the existing software. You must remove the existing Sun StorageTek QFS package before installing a new package.
If you are using any optional Sun StorageTek QFS packages, make sure that you remove these packages before removing the main SUNWqfs packages. The installation script prompts you to confirm several of the removal steps.
|
Note - The samu utility must be closed before removing the Sun StorageTek QFS software. |
|
1. Use the pkginfo(1) command to determine which Sun StorageTek QFS software packages are installed on your system.
2. Use the pkgrm(1M) command to remove the existing Sun StorageTek QFS software.
The following example command removes the SUNWqfsu and the SUNWqfsr packages from a 4U1 release:
|
Note - The SUNWqfsr package must be the last package removed. The 4U1 release does not include any localized software packages. |
The following example command removes the SUNWcqfs, the SUNWfqfs, and the SUNWjqfs localized packages from a 4U0 release:
|
Note - The SUNWqfs package must be the last package removed. |
The Sun StorageTek 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 StorageTek QFS package.
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.
|
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:
2. Use the pkgadd(1M) command to upgrade the SUNWqfsr and SUNWqfsu packages.
3. Enter yes or y in response to each of the questions.
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 any files you want to save to an alternate location.
Perform the task described in this section if you want to be able to use the File System Manager interface.
File System Manager is an online interface that enables you to configure many of the components in a Sun StorageTek QFS environment. You can use this tool to control, monitor, configure, and reconfigure the environment's components.
|
1. 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 SUNWqfsr and SUNWqfsu packages.
3. Use the cd(1) command to change to the directory where the software package release files reside on your server.
4. Execute the fsmgr_setup script to start the installation process.
5. 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:
After installing the packages, it starts the Tomcat Web Server and enables logging.
6. Log in to the Sun StorageTek QFS server and become superuser.
7. Use the ps(1) and grep(1) commands to make sure that the rpcbind service is running.
8. Examine the output from the preceding commands.
The output should contain a line similar to the following:
If rpcbind does not appear in the output, enter the following command to start the rcpbind service:
9. (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:
For more information, see the fsmadm(1M) man page.
10. (Optional) Give additional users access to File System Manager.
If you are upgrading from version 2.0 or earlier, 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 access to all File System Manager operations, or access to only a subset of operations.
To give an additional user access to File System Manager, use the useradd command. See To Add Users and Assigning Privilege Levels for information about adding users and assigning File System Manager user privilege levels.
For information about using File System Manager see Using the File System Manager Software, or see the File System Manager online help.
The instructions in this section cover the tasks involved in restoring the Sun StorageTek QFS file system after an upgrade.
|
1. Enter the sam-fsd(1M) command.
2. Examine the output for errors, as follows:
If your 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.
|
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 StorageTek QFS file systems from no to yes or delay.
|
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 Existing File Systems. To accomplish this, use the sammkfs(1M) and qfsrestore(1M) commands on each file system.
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. You will use this DAU size again in Step 2.
2. Use the sammkfs(1M) command to initialize a new Sun StorageTek QFS file system.
The following example command reinitializes a file system named qfs1 with a DAU size of 512 kilobytes:
For more information about the options to the sammkfs(1M) command, see the sammkfs(1M) man page.
3. Use the qfsrestore(1M) command to restore the dumped data in the new file system.
For example, suppose you had a file system named qfs1 (mounted at /qfs1) that you wanted to restore from files dumped to qfs1.bak, which existed outside of the Sun StorageTek QFS file system. In this case, you would issue the following commands:
|
Perform this task if you did not reinitialize and restore the file system as just described.
Use the samfsck(1M) command to check each existing file system for inconsistencies.
For more information, see the samfsck(1M) man page.
You can mount the Sun StorageTek QFS file system using File System Manager or the CLI.
1. From the Servers menu, select 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.
In the following example, qfs1 is the name of the file system to be mounted:
File headers, the calling sequence, and other elements of the Sun StorageTek QFS application programming interface (API) can change from release to release. If you are running applications that 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. |
The following section describes how to upgrade the Solaris OS when running the Sun StorageTek QFS software.
|
Many of the steps involved in upgrading your Solaris OS level are identical to the steps involved in upgrading your Sun StorageTek QFS environment. Some of the steps in this procedure reference procedures in the previous sections.
1. Obtain the Sun StorageTek QFS and Solaris OS software upgrades.
Sun StorageTek QFS software supports various levels of the Solaris OS. Do not reinstall your old Sun StorageTek QFS 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, defaults.conf, samfs.cmd, the shared hosts files, and so on. Back up these files for all file systems in your Sun StorageTek QFS environment. Also make sure that you have backup copies of files in the /etc/opt/SUNWsamfs directory.
3. Ensure that each affected file system is backed up.
The file systems should be backed up regularly according to your site's policies and 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.
For instructions, see Unmounting File Systems.
5. Remove the existing Sun StorageTek QFS software.
You must remove the existing Sun StorageTek QFS package before installing either the new package or the new operating system level. For instructions, see Removing Existing Sun StorageTek QFS Software.
Install the new Solaris OS revision using the corresponding Sun Solaris upgrade procedures.
7. Add the upgrade packages that you obtained in Step 1.
The Sun StorageTek QFS software package uses 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 StorageTek QFS package. For instructions, see Adding the Upgrade Packages.
8. (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.
9. 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.
| Sun StorageTek QFS Installation and Upgrade Guide | 819-7936-10 |
|
Copyright © 2007, Sun Microsystems, Inc. All Rights Reserved.
To Back Up a File System
