| Sun StorEdge SAM-FS Installation and Upgrade Guide |    
|
| Sun StorEdge SAM-FS Installation and Upgrade Guide |
|
| 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:
Follow the instructions in this section to prepare for a Sun StorEdge SAM-FS software upgrade.
Back up your existing file system 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 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.
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 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.
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:
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:
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.
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.
The procedures in this section show how to halt Sun StorEdge SAM-FS operations.
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:
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.
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:
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:
3. Use the samd(1M) stop command to stop all operations.
|
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:
You can unmount a file system using any of the methods described in this section. After the file system is unmounted, you can proceed toRemoving the Existing Software.
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.
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.
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:
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.
For all Sun StorEdge SAM-FS 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 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.
|
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.
The following example command removes the SUNWsamfsu and the SUNWsamfsr packages from a 4U1 release:
|
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:
|
Note - The SUNWsamfs package must be the last package removed. |
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.
|
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 SUNWsamfsr and SUNWsamfsu packages.
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:
|
Note - The tools package, SUNWsamtp, is available separately. Contact your Sun sales representative for information about obtaining the 4U4 version of the SUNWsamtp package. |
Perform the task described in this section if you want to be able to use 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.
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.
6. Answer the questions as prompted by the fsmgr_setup script.
During the installation procedure, you are asked questions about your environment. The script prompts you to enter passwords for the SAMadmin role and for the samadmin and samuser login IDs.
The fsmgr_setup script automatically installs the following:
The installation scripts prompt you to specify whether you want to install localized packages.
After installing the packages, it starts the Tomcat Web Server, enables logging, and creates the SAMadmin role.
7. Use vi(1) or another editor to edit your system setup files to include the correct paths to commands and man pages.
CODE EXAMPLE 4-3 shows how your .profile file might look after editing.
PATH=$PATH:/opt/SUNWfsmgr/bin MANPATH=$MANPATH:/opt/SUNWfsmgr/man export PATH MANPATH |
When you have finished editing, the path statement in your .cshrc file might look like the following line:
CODE EXAMPLE 4-4 shows how the MANPATH in your .login file might after you have finished editing.
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:
10. 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 rpcbind service:
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:
For more information, see the fsmadm(1M) man page.
The instructions in this section cover the tasks involved in restoring the Sun StorEdge SAM-FS environment after an upgrade.
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.
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.
Complete the following tasks in order to reinitialize, and verify the configuration of, the Sun StorEdge SAM-FS file system.
The following file exists on your Sun StorEdge SAM-FS server:
The following additional files might 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. Enter the sam-fsd(1M) command.
2. Examine the output for errors, as follows:
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.
Enter the archiver(1M) -lv (lowercase L) command to verify the archiver.cmd file:
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.
|
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.
|
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.
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:
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:
|
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.
You can mount the Sun StorEdge SAM-FS file system using File System Manger or the CLI.
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.
In the following example, samfs1 is the name of the file system to be mounted:
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. |
The following sections describe the steps that must be taken when upgrading the hardware in a Sun StorEdge SAM-FS environment.
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.
Before starting the upgrade process, be sure to do the following:
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.
You can idle the archiver in one of the following ways:
For more information, see the samcmd(1M) man page.
Support for x86 hardware platforms was added in the 4U4 version of the software. 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 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).
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.
This section describes how to upgrade the hardware within your existing Sun StorEdge SAM-FS environment. The following topics are presented:
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:
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.
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:
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:
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:
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:
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:
15. Initialize the Sun StorEdge SAM-FS system by mounting the file system or by issuing the following command:
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.
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:
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:
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:
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:
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:
10. Start your Sun StorEdge SAM-FS system.
You can now continue to use the existing Sun StorEdge SAM-FS tapes.
The following section describes how to upgrade the Solaris OS when running the Sun StorEdge SAM-FS software.
|
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.
For instructions, see Unmounting File Systems.
5. Issue the samd(1M) stop command to stop all archiving and SAM-FS activity:
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.
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.
| Sun StorEdge SAM-FS Installation and Upgrade Guide | 819-2754-10 |
|
Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.
To Back Up a File System
