| Sun StorageTek QFS Installation and Upgrade Guide |    
|
| Sun StorageTek QFS Installation and Upgrade Guide |
|
| C H A P T E R 3 |
|
Installing and Configuring Sun StorageTek QFS |
This chapter describes the procedures for installing and configuring Sun StorageTek QFS software for the first time. Use these procedures if this is the initial installation of the Sun StorageTek QFS software package at your site. If you are upgrading Sun StorageTek QFS software on an existing server, see Chapter 5, Upgrading Sun StorageTek QFS.
You can install and configure the Sun StorageTek QFS file system the File System Manager browser interface tool, or by using command-line interface (CLI) commands.
If you are installing a Sun StorageTek QFS shared file system or a Sun StorageTek QFS file system in a Sun Cluster environment, you must also follow the additional installation instructions in the next chapter, Configuring a Shared or Sun Cluster Configuration.
You must be logged in as superuser to complete most of the procedures in this chapter.
This chapter contains the following sections:
The following instructions are a high-level overview of the installation process. For more detailed instructions, refer to the following sections in this chapter.
|
1. Insert the installation CD into your computer.
2. Select the correct package for your environment:
cd StorageTek_QFS_4.5_sparc
or
cd StorageTek_QFS_4.5_x64
3. Select the correct Solaris version:
cd 2.9
or
cd 2.10
4. Install the packages:
pkgadd -d . SUNWqfsr SUNWqfsu (Sun StorageTek QFS)
or
pkgadd -d . SUNWsamfsr SUNWsamfsu (Sun StorageTek SAM)
|
Note - If you want to use the Sun StorageTek WORM-FS package for Write-Once, Read-Many (WORM) functionality, install the SUNWsamfswm package as well. |
5. Verify the installation:
pkginfo |grep qfs
pkginfo -l SUNWqfsr
or
pkginfo |grep sam
pkginfo -l SUNWsamfsr
|
1. Edit the /etc/syslog.conf file by adding the following lines:
# SAM-QFS logging
local7.debug /var/adm/sam-log
# use a tab
2. Issue the following commands:
|
1. Copy the example defaults.conf file into the correct location.
cp -i /opt/SUNWsamfs/examples/defaults.conf /etc/opt/SUNWsamfs
2. Edit the defaults.conf file to enable tracing.
/etc/opt/SUNWsamfs/defaults.conf:
|
Edit the /.profile file to set up the PATH variables:
PATH=$PATH:/opt/SUNWsamfs/bin:/opt/SUNWsamfs/sbin:/opt/SUNWsamfs/ toolsMANPATH=/opt/SUNWsamfs/man:/opt/SUNWsan/man:$MANPATHexport PATH MANPATH |
|
1. Create the mcf file:
cd /etc/opt/SUNWsamfs
cp -i /opt/SUNWsamfs/examples/mcf .
mcf:
2. Create the vfstab file:
/etc/vfstab:
3. Create the mount point and mount the file system:
|
2. Create the hosts files:
cp -i /opt/SUNWsamfs/examples/hosts* .
A hosts file is required for each file system. You must include a server priority for any server that will be a metadata server.
3. Create the vfstab file:
/etc/vfstab:
#device device mount FS fsck mount mount#to mount to fsck point type pass at boot options#sqfs1 - /sqfs1 samfs - no sharedsqfs2 - /sqfs2 samfs - yes shared,stripe=2,bg |
4. Create the mount points and mount the file systems:
mkdir /sqfs1 # make sure to do this on all hosts
chmod 755 /sqfs1
mkdir /sqfs2 # make sure to do this on all hosts
chmod 755 /sqfs2
tail /etc/inet/services
/etc/inet/services:
sammkfs -S sqfs1 # -S is for shared FS
sammkfs -S sqfs2
mount sqfs1
chmod 755 /sqfs1 # Set the appropriate permissions on the file system
First mount the file system on the server, then on the clients.
mount sqfs2
chmod 755 /sqfs2 # Set the appropriate permissions on the file system
First mount the file system on the server, then on the clients.
Run the following if the configuration changes:
samu, then N, then ctrl/f if there are multiple file systems
|
1. Edit the /etc/inet/ntp.conf file:
2. Issue the following commands:
|
1. Set up the network file system (NFS) server:
The remaining sections of this chapter are more detailed versions of the Sun StorageTek QFS software installation instructions. They cover the procedures in much greater depth than the Quick Start instructions.
The Sun StorageTek QFS software uses the Sun Solaris packaging utilities for adding and deleting software. The pkgadd(1M) utility prompts you to confirm various actions necessary to install the packages.
Follow these steps on each host in the file system.
2. Use the cd(1) command to change to the directory where the software package release files reside.
If you are using a CD, the packages reside in the /cdrom/cdrom0 directory organized by Sun Solaris version.
3. Use the pkgadd(1M) command to add the SUNWqfsr and SUNWqfsu packages.
|
Note - If you want to use the Sun StorageTek WORM-FS package for Write-Once, Read-Many (WORM) functionality, install the SUNWsamfswm package as well. |
4. Enter yes or y or a no or n as the answer to each of the questions.
When you install SUNWqfsr and SUNWqfsu, you are asked whether 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 reset permissions on certain commands later by using the set_admin(1M) command. For more information on this command, see Adding the Administrator Group or the set_admin(1M) man page.
5. Issue the pkginfo(1M) command and examine its output to make sure that the Sun StorageTek QFS packages are installed.
Each host must have the SUNWqfsr and SUNWqfsu packages installed on it.
CODE EXAMPLE 3-1 shows the required SUNWqfsr/SUNWqfsu packages.
If you are installing the Sun StorageTek QFS software onto Linux clients in a shared environment, see the Sun StorageTek QFS Linux Client Guide for instructions.
In order to have access to the commands and man pages for the Sun StorageTek QFS commands, you must modify your PATH and MANPATH environment variables.
Follow these steps on each host in the file system.
1. For users who will need to access the Sun StorageTek QFS user commands (for example, sls(1)), add /opt/SUNWsamfs/bin to the users' PATH variables.
2. Use vi(1) or another editor to edit your system setup files to include the correct paths to commands and man pages.
CODE EXAMPLE 3-2 shows how your .profile file might look after editing.
PATH=$PATH:/opt/SUNWsamfs/bin:/opt/SUNWsamfs/sbin MANPATH=$MANPATH:/opt/SUNWsamfs/man export PATH MANPATH |
When you have finished editing, the path statement in your .cshrc file might look like the following line:
CODE EXAMPLE 3-3 shows how the MANPATH in your .login file might look after you have finished editing.
setenv MANPATH /usr/local/man:opt/SUNWspro/man:/$OPENWINHOME/\ share/man:/opt/SUNWsamfs/man |
Perform the tasks in this section to install the File System Manager software, which is used to configure, control, monitor, or reconfigure your Sun StorageTek QFS environment.
The procedures in this section are as follows:
1. Ensure that you have met the installation requirements 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 SUNWqfsr and SUNWqfsu packages.
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 fsmgr_setup script automatically installs the following:
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.
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.
CODE EXAMPLE 3-4 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 3-5 shows how the MANPATH in your .login file might look 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 StorageTek QFS 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.
12. (Optional) Give additional users access to File System Manager.
By default, the root user has privileges to perform all operations available from the File System Manager software. You can assign other users full or partial access to File System Manager 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.
The Java Web Console framework has a default session timeout of 15 minutes. If File System Manager is the only application registered in the Java Web Console, the File System Manager installation program changes the session timeout to 60 minutes. You can change the session timeout to a different value, but it is recommended that you not set it to a value greater than 60 minutes in order to preserve security.
To change the session timeout value, enter the following command on the management station:
/opt/SUNWfsmgr/bin/fsmgr session <timeout-in-minutes>
For example, to change the timeout value to 45 minutes, type:
/opt/SUNWfsmgr/bin/fsmgr session 45
After File System Manager is installed, you can log in to the software using the root user name and the password for the management station.
The root login grants you full administrator privileges to configure, monitor, control, and reconfigure the devices in your Sun StorageTek QFS environment. Only the Sun StorageTek QFS administrator should log in using the root login. All other users should log in using another user name.
By default, File System Manager is set up to manage the server on which it is installed. It can also be used to manage other servers running Sun StorageTek QFS software, but those additional servers must first be configured to allow File System Manager access. For instructions on adding additional managed servers, see the Sun StorageTek QFS File System Configuration and Administration Guide or the File System Manager online help.
To add additional users for File System Manager, complete the following procedure.
1. Outside of the browser interface, log in to the management station server as root.
2. Use the useradd and passwd commands to add each user.
For example, to add a user with account name bobsmith, type the following:
Each user account that you add in this way has read-only viewing privileges for File System Manager functions. To add additional privileges see the following section, Assigning Privilege Levels.
You can assign users full or partial access to File System Manager operation. The following table lists the five levels of privileges that you can assign to File System Manager users.
To specify full or partial configuration privileges for a user, add the following line to the /etc/user_attr file:
account-name::::auths=privilege-level
account-name is the name of the user's account and privilege-level is the level of authorization that you want to assign to the user.
For example, to assign full privileges (privilege level com.sun.netstorage.fsmgr.config) for user account bobsmith, add the following line to the /etc/user_attr file:
bobsmith::::auths=com.sun.netstorage.fsmgr.config
To assign bobsmith privileges only for staging and restoring file systems (privilege level com.sun.netstorage.fsmgr.operator.file) and exporting, importing, and assigning VSNs (privilege level com.sun.netstorage.operator.media), add the following line to the /etc/user_attr file:
bobsmith::::auths=com.sun.netstorage.fsmgr.operator.file, com.sun.netstorage.fsmgr.operator.media
You can create a generic File System Manager account that can be used by multiple users, and then add a role with privileges that only some of those users can access.
1. Use the useradd and passwd commands to add the account.
For example, to add a user account called guest for multiple users, type the following:
2. Use the roleadd and passwd commands to add the role.
To create a role called admin with special privileges within the guest account, type the following:
3. Specify the privilege levels in the /etc/user_attr file.
To assign the admin role privileges to restore and stage file systems, add the following lines to the /etc/user_attr file:
admin::::auths=com.sun.netstorage.fsmgr.operator.file
guest::::type=normal;roles=admin
In this example, when a user logs in as guest, File System Manager prompts the user to select either No Role or Admin. If users know the Admin role password, they can select Admin, enter the Admin password, and have privileges to restore and stage file systems. All other users must select No Role and have read-only privileges.
Because multiple users with the same privilege level can be logged in to the software concurrently, there is a risk of one user's changes overwriting another user's previous changes. To prevent this, develop policies about who can make changes and how to notify others.
Perform this procedure if you want to invoke File System Manager and use it, rather than CLI commands, to perform some of the configuration steps.
1. Log in to the server where File System Manager is installed, or in to any computer that has network access to it.
2. If you upgraded from a previous version of the software, open the web browser and clear the browser cache.
3. From the web browser, invoke the File System Manager software:
For hostname, type the name of the host where the File System Manager software is installed. If you need to specify a domain name in addition to the host name, specify the hostname in this format: hostname.domainname.
Note that this URL begins with https, not http. The Java Web Console login screen appears.
4. At the User Name prompt, enter root or another valid File System Manager user name.
5. At the Password prompt, enter the password.
7. In the Storage section, click File System Manager.
You are now logged in to the File System Manager interface. Add the server that you want to administer.
If you need help accomplishing this task, click Help. After you add the servers, see the following sections for more information about configuring your environment using the File System Manager.
Each Sun StorageTek QFS environment is unique. The system requirements and hardware that are used differ from site to site. It is up to you, the system administrator at your site, to set up the specific configuration for your Sun StorageTek QFS environment.
The master configuration file, /etc/opt/SUNWsamfs/mcf, defines the topology of the equipment managed by the Sun StorageTek QFS file system. This file specifies the devices and file systems included in the environment and contains information that enables you to identify the disk slices to be used and to organize them into Sun StorageTek QFS file systems.
You can edit the mcf file in either of two ways:
There are examples of mcf files in /opt/SUNWsamfs/examples. Example mcf file configurations can also be found in Appendix D of this manual.
|
Note - For information about file system design considerations, see the Sun StorageTek QFS File System Configuration and Administration Guide. |
The following sections provide examples and describe activities related to creating and maintaining the mcf file:
When you configure Sun StorageTek QFS file systems using the File System Manager software, it creates or edits the appropriate Sun StorageTek QFS configuration files, including the mcf file, on that server. You can use either File System Manager or the CLI later to further edit these files.
To add a server and create a file system:
1. Log in to the File System Manager browser interface.
The File Systems Summary page is displayed.
2. Click Manage Servers at the top of the navigation tree.
The Servers page is displayed.
3. If you have not already added the server to be managed, click Add to add it now.
The Add Server page is displayed.
4. In the Server Name or IP Address field, type the name of the server or the IP address of the server.
The New File System wizard is displayed.
7. Follow the steps for creating a new file system.
When you complete this process, the mcf file is created. For more information, see the File System Manager online help.
1. Copy the example mcf file from /opt/SUNWsamfs/examples to /etc/opt/SUNWsamfs.
2. Use vi(1) or another editor to create the mcf file.
When you create the mcf file, follow these guidelines:
CODE EXAMPLE 3-6 shows the fields of each line entry in the mcf file.
For more information, see the mcf(4) man page.
CODE EXAMPLE 3-7 shows file system entries in an mcf file for a Sun StorageTek QFS file system that is local to one Solaris OS host.
For information about editing the mcf file on multiple hosts in a Sun StorageTek QFS shared file system or a file system in a Sun Cluster environment, see Editing mcf Files on Other Hosts.
The procedures in this section show you how to verify the correctness of the mcf configuration file.
Perform these verifications on all hosts if you are configuring a Sun StorageTek QFS shared file system or a Sun StorageTek QFS highly available file system.
1. Enter the sam-fsd(1M) command.
2. Examine the output for errors, as follows:
If your mcf file has errors, refer to the mcf(4) man page for information about how to create this file correctly. You can also refer to the example mcf files in Appendix D.
Use the procedures in this section to specify mount parameters for the Sun StorageTek QFS file system.
You can specify mount parameters in the following ways:
This section describes how to edit the /etc/vfstab file.
|
Note - Even though /global is used in this chapter's examples as the mount point for file systems mounted in a Sun Cluster environment, it is not required. You can use any mount point. |
TABLE 3-2 shows the values you can enter in the fields in the /etc/vfstab file.
When you create a file system using File System Manager, a default /etc/vfstab file is created. However, mount options specified in File System Manager are written to the samfs.cmd file rather than to the /etc/vfstab file. For more information, see To Create and Edit the samfs.cmd File Using File System Manager.
To edit the mount options in the /etc/vfstab file, use the following command-line procedure, To Update the /etc/vfstab File and Create the Mount Point Using a Text Editor.
|
|
Follow these steps on all hosts if you are configuring a Sun StorageTek QFS shared file system or a Sun StorEdge QFS highly available file system.
For debugging purposes, if you are configuring a Sun StorageTek QFS shared file system, the mount options should be the same on all hosts that can mount the file system.
1. Use vi(1) or another editor to open the /etc/vfstab file.
2. Create an entry for each Sun StorageTek QFS file system.
CODE EXAMPLE 3-9 shows header fields and entries for a local Sun StorageTek QFS file system.
TABLE 3-2 shows the various fields in the /etc/vfstab file and their contents.
If you are configuring a file system for a Sun Cluster environment, the required and recommended mount options vary according to the type of file system you are configuring. TABLE 3-3 explains the mount options.
|
Sun StorageTek QFS shared file system to support Oracle Real Application Cluster (RAC) database files |
||
You can specify most of the mount options listed in TABLE 3-3 in either the /etc/vfstab file or the samds.cmd file. The one exception is the shared option, which must be specified in the /etc/vfstab file.
|
Tip - In addition to the mount options mentioned in TABLE 3-3, you can also specify the trace mount option for configuration debugging purposes. |
3. Use the mkdir(1) command to create the file system mount point.
The mount point location varies, depending on where the file system is to be mounted. The following examples illustrate this.
Example 1. This example assumes that /qfs1 is the mount point of the qfs1 file system. This is a local file system. It can exist on a stand-alone server or on a local node in a Sun Cluster environment.
Example 2. This example assumes that /global/qfs1 is the mount point of the qfs1 file system, which is a Sun StorageTek QFS shared file system to be mounted in a Sun Cluster environment.
|
Note - If you configured multiple mount points, repeat these steps for each mount point, using a different mount point (such as /qfs2) and Family Set name (such as qfs2) each time. |
You can create the /etc/opt/SUNWsamfs/samfs.cmd file as the place from which the system reads mount parameters.
You can manage certain features more easily from a samfs.cmd file. These features include the following:
If you are configuring multiple Sun StorageTek QFS systems with multiple mount parameters, consider creating the samfs.cmd file.
|
|
If you specify non-default mount options when creating a file system in File System Manager, the samfs.cmd file is automatically created or updated with those mount options.
To edit a file system's mount options:
1. From the Servers menu, select the name of the server on which the file system is located.
The File Systems Summary page is displayed.
2. Select the radio button next to the file system whose mount options you want to edit.
3. From the Operations menu, choose Edit Mount Options.
The Edit Mount Options page is displayed.
4. Make your edits in the fields.
For more information about the fields on the Edit Mount Options page, see the File System Manager online help.
1. Use vi(1) or another editor to create the samfs.cmd file.
Create lines in the samfs.cmd file to control mounting, performance features, or other aspects of file system management. For more information about the samfs.cmd file, see the Sun StorageTek QFS File System Configuration and Administration Guide, or see the samfs.cmd(4) man page.
CODE EXAMPLE 3-10 shows a samfs.cmd file for a Sun StorageTek QFS file system.
low = 50 high = 75 fs = samfs1 high = 65 writebehind = 512 readahead = 1024 fs = samfs5 partial = 64 |
2. If you are creating a multihost file system, copy lines as necessary to the samfs.cmd file on other hosts.
If you have created a samfs.cmd file on one host in a Sun Cluster environment to describe a particular file system's mount parameters, copy those lines to the samfs.cmd files on all the nodes that can access that file system.
For debugging purposes, the samfs.cmd file, as it pertains to a specific file system, should be the same on all hosts. For example, if the qfs3 file system is accessible from all nodes in a Sun Cluster environment, then the lines in the samfs.cmd file that describe the qfs3 file system should be identical on all the nodes in the Sun Cluster environment.
Depending on your site needs, it might be easier to manage mount options from the samfs.cmd file rather than from the /etc/vfstab file. The /etc/vfstab file overrides the samfs.cmd file in the event of conflicts.
For more information about mount options, see the mount_samfs(1M) man page.
This section tells you how to initialize the environment and the Sun StorageTek QFS file system and how to mount the file system.
Use the samd(1M) config command to initialize the Sun StorageTek QFS environment:
Repeat this command on each host if you are configuring a Sun StorageTek QFS shared file system or a Sun StorEdge QFS highly available file system.
This procedure shows how to use the sammkfs(1M) command and the Family Set names that you have defined to initialize a file system.
Use the sammkfs(1M) command to initialize a file system for each Family Set name defined in the mcf file.
|
Caution - Running sammkfs(1M) creates a new file system. It removes all references to the data currently contained in the partitions associated with the file system in the /etc/opt/SUNWsamfs/mcffile. |
CODE EXAMPLE 3-11 shows the command to use to initialize a Sun StorageTek QFS file system with the Family Set name of qfs1.
Enter y in response to this message to continue the file system creation process.
If you are configuring a Sun StorageTek QFS shared file system, enter the sammkfs(1M) command on the metadata server only.
Enter the sammkfs(1M) command at the system prompt. The -S option specifies that the file system be a Sun StorageTek QFS shared file system. Use this command in the following format:
For example, you might use the following sammkfs(1M) command to initialize a Sun StorageTek QFS shared file system and identify it as shared:
If the shared keyword appears in the mcf file, the file system must be initialized as a shared file system with the -S option to the sammkfs(1M) command. You cannot mount a file system as shared if it was not initialized as shared.
If you are initializing a file system as a Sun StorageTek QFS shared file system, file /etc/opt/SUNWsamfs/hosts.fs-name must already exist when you issue the sammkfs(1M) command. The sammkfs(1M) command uses the hosts file when it creates the file system. You can use the samsharefs(1M) command to replace or update the contents of the hosts file at a later date. For more information, see Creating the Shared Hosts File.
The mount(1M) command mounts a file system. It also reads the /etc/vfstab and samfs.cmd configuration files. For information about the mount(1M) command, see the mount_samfs(1M) man page.
Use one or more of the procedures in this section to mount your file system.
1. From the Servers menu, select the name of the server on which the file system is located.
The File Systems 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.
Perform this procedure on all Sun StorageTek QFS file systems, as follows:
1. Use the mount(1M) command to mount the file system.
Specify the file system mount point as the argument. For example:
2. Use the mount(1M) command with no arguments to verify the mount.
This step confirms that the file system is mounted and shows how to set permissions. CODE EXAMPLE 3-12 shows the output from a mount(1M) command issued to verify whether example file system qfs1 is mounted.
3. (Optional) Use the chmod(1) and chown(1) commands to change the permissions and ownership of the file system's root directory.
If this is the first time the file system has been mounted, it is typical to perform this step.
If you are creating a Sun StorageTek QFS shared file system in either a Solaris OS or a Sun Cluster environment, perform this procedure to verify that the file system is configured so that you can change the metadata server.
If you are creating a Sun StorageTek QFS shared file system in a Solaris OS environment, perform these steps on each metadata server or potential metadata server.
If you are creating a Sun StorageTek QFS shared file system in a Sun Cluster environment, perform these steps on all hosts that can mount the file system.
1. Log in to the metadata server as superuser.
2. Use the samsharefs(1M) command to change the metadata server.
3. Use the ls(1) -al command to verify that the files are accessible on the new metadata server.
4. Repeat Step 2 and Step 3 to change back to the original metadata server.
For more information on completing the configuration of file systems in a shared or Sun Cluster Environment, see Configuring a Shared or Sun Cluster Configuration after completing the rest of the rest of the procedures in this chapter as needed.
This section outlines additional tasks that you might need to complete in order to finish the configuration of the Sun StorageTek QFS environment. Some of these tasks are optional, depending on your specific environment. The following tasks are covered:
Perform this task if you are configuring a file system and you want the file system to be NFS-shared.
The procedures in this section use the Sun Solaris share(1M) command to make the file system available for mounting by remote systems. The share(1M) commands are typically placed in the /etc/dfs/dfstab file and are executed automatically by the Solaris OS when you enter init(1M) state 3.
The following is a general description of how to NFS-share a file system in a Sun Cluster environment. For more information on NFS-sharing file systems that are controlled by HA Storage Plus, see the Sun StorageTek QFS File System Configuration and Administration Guide, the Sun Cluster Data Service for Network File System (NFS) Guide for Solaris OS, and your NFS documentation.
1. Locate the dfstab.resource-name file.
The Pathprefix property of HA Storage Plus specifies the directory in which the dfstab.resource-name file resides.
2. Use vi(1) or another editor to add a share(1M) command to the Pathprefix/SUNW.nfs/dfstab.resource-name file.
If you are configuring a Sun StorageTek QFS shared file system, you can perform this procedure from the metadata server or from one of the shared clients.
1. Use vi(1) or another editor to add a share(1M) command to the /etc/dfs/dfstab file.
For example, add a line like the following to direct the Solaris OS to NFS-share the new Sun StorageTek QFS file system:
2. Use the ps(1) and grep(1) commands to determine whether nfs.server is running.
In this sample output, the lines that contain /usr/lib/nfs indicate that the NFS server daemons are running.
3. If nfs.server is not running, start it.
|
Note - For Solaris 10, use the following command:
|
4. (Optional) Type the share(1M) command at a root shell prompt.
Perform this step if you want to NFS-share the new Sun StorageTek QFS file system immediately.
When you have finished NFS-sharing the file system, you are ready to mount it, as described in the next procedure, To Mount the File System on NFS Clients in a Solaris OS Environment.
If no NFS-shared file systems exist when the Sun Solaris OS boots, the NFS server is not started. CODE EXAMPLE 3-13 shows the commands to use to enable NFS sharing. You must change to run level 3 after adding the first share entry to this file.
# init 3 # who -r . run-level 3 Dec 12 14:39 3 2 2 # share - /qfs1 - "QFS" |
Some NFS mount parameters can affect the performance of an NFS-mounted Sun StorageTek QFS file system. You can set these parameters in the /etc/vfstab file as follows:
For more information about these parameters, see the mount_nfs(1M) man page.
|
|
If you are configuring a Sun StorageTek QFS shared file system, you can perform this procedure from the metadata server or from one of the shared clients.
1. On each NFS client system, use vi(1) or another editor to edit the /etc/vfstab file, and add a line to mount the server's Sun StorageTek QFS file system at a convenient mount point.
The following example mounts server:/qfs1 on the /qfs1 mount point:
2. Save and close the /etc/vfstab file.
3. Enter the mount(1M) command.
The following mount(1M) command mounts the qfs1 file system:
Alternatively, the automounter can do this, if you prefer. Follow your site procedures for adding server:/qfs1 to your automounter maps. For more information about automounting, see the automountd(1M) man page.
|
The /opt/SUNWsamfs/examples/defaults.conf file contains default settings for the Sun StorageTek QFS environment. You can change these settings at any time after the initial installation.
Before changing any default settings, examine the defaults.conf(4) man page to discern the types of behavior this file controls.
Follow these steps for each host that you want to include in a Sun StorageTek QFS shared file system or a Sun StorEdge QFS highly available file system.
|
Note - For debugging purposes, the defaults.conf file should be the same on all hosts. |
1. Use the cp(1) command to copy /opt/SUNWsamfs/examples/defaults.conf to its functional location.
2. Use vi(1) or another editor to edit the file.
Edit the lines that control aspects of the system that you want to change. Remove the pound character (#) from column 1 of the lines you change.
For example, if you are configuring a Sun StorageTek QFS shared file system in a Sun Cluster environment, you might specify the following settings, which are helpful during debugging:
3. Use the samd(1M) config command to restart the sam-fsd(1M) daemon and enable the daemon to recognize the changes in the defaults.conf file.
The Sun StorageTek QFS software can be configured to notify you when potential problems occur in its environment. The system sends notification messages to a management station of your choice. The Simple Network Management Protocol (SNMP) software manages the exchange of information between network devices such as servers, automated libraries, and drives.
The Sun StorageTek QFS Management Information Base (MIB) defines the types of problems, or events, that the Sun StorageTek QFS software can detect. The software can detect errors in configuration, tapealert(1M) events, and other atypical system activity. For complete information about the MIB, see /var/snmp/mib/SUN-SAM-MIB.mib.
The following procedures describe how to enable and disable remote notification.
1. Ensure that the management station is configured and known to be operating correctly.
Setting Up the Network Management Station describes this prerequisite.
2. Using vi(1) or another editor, examine the /etc/hosts file to ensure that the management station to which notifications should be sent is defined. If it is not defined, add a line that defines the appropriate host.
The following sample file defines a management station with a host name of mgmtconsole.
999.9.9.9 localhost 999.999.9.999 loggerhost loghost 999.999.9.998 mgmtconsole 999.999.9.9 samserver |
3. Save your changes to /etc/hosts and exit the file.
4. Using vi(1) or another editor, open the file /etc/opt/SUNWsamfs/scripts/sendtrap and locate the TRAP_DESTINATION='hostname' directive.
This line specifies that remote notification messages be sent to port 161 of the server upon which the Sun StorageTek QFS software is installed. Note the following:
5. Locate the COMMUNITY="public" directive in /etc/opt/SUNWsamfs/scripts/sendtrap.
This line acts as a password. It prevents unauthorized viewing or use of SNMP trap messages. Examine this line and do one of the following, depending on the community string value of your management station:
6. Save your changes to /etc/opt/SUNWsamfs/scripts/sendtrap and exit the file.
The remote notification facility is enabled by default. If you want to disable remote notification, perform this procedure.
1. If the file /etc/opt/SUNWsamfs/defaults.conf does not already exist, use the cp(1) command to copy file /opt/SUNWsamfs/examples/defaults.conf to /etc/opt/SUNWsamfs/defaults.conf.
2. Using vi(1) or another editor, open the file /etc/opt/SUNWsamfs/defaults.conf and find the line that specifies SNMP alerts.
3. Edit the line to disable SNMP alerts.
Remove the # symbol and change on to off. After editing, the line is as follows:
4. Save your changes and exit the file.
5. Use the samd(1M) config command to restart the sam-fsd(1M) daemon.
This command restarts the sam-fsd(1M) daemon and enables the daemon to recognize the changes in the defaults.conf file.
By default, only the superuser can execute Sun StorageTek QFS administrator commands. However, during installation you can create an administrator group. Members of the administrator group can execute all administrator commands except for star(1M), samfsck(1M), samgrowfs(1M), sammkfs(1M), and samd(1M). The administrator commands are located in /opt/SUNWsamfs/sbin.
After installing the package, you can use the set_admin(1M) command to add or remove the administrator group. You must be logged in as superuser to use the set_admin(1M) command. You can also undo the effect of this selection and make the programs in /opt/SUNWsamfs/sbin executable only by the superuser. For more information about this command, see the set_admin(1M) man page.
1. Choose an administrator group name, or select a group that already exists in your environment.
2. Use the groupadd(1M) command, or edit the /etc/group file.
The following is an entry from the /etc/group file that designates an administrator group for the Sun StorageTek QFS software. In this example, the samadm group consists of both the adm and operator users.
The Sun StorageTek QFS system logs errors, cautions, warnings, and other messages using the standard Sun Solaris syslog(3) interface. By default, the Sun StorageTek QFS facility is local7.
1. Use vi(1) or another editor to open the /etc/syslog.conf file.
2. In the file /opt/SUNWsamfs/examples/syslog.conf_changes, find the logging line, which is similar, if not identical, to the following:
|
Note - The preceding entry is all one line and has a TAB character (not a space) between the fields. |
The default facility is local7. If you set logging to something other than local7 in the /etc/syslog.conf file, edit the defaults.conf file and reset it there, too. For more information, see the defaults.conf(4) man page.
3. Append the logging line from /opt/SUNWsamfs/examples/syslog.conf_changes to the /etc/syslog.conf file.
# cp /etc/syslog.conf /etc/syslog.conf.orig # cat /opt/SUNWsamfs/examples/syslog.conf_changes >> /etc/syslog.conf |
4. Create an empty log file and send the syslogd process a HUP signal.
For example, to create a log file in /var/adm/sam-log and send the HUP to the syslogd daemon, type the following:
For more information, see the syslog.conf(4) and syslogd(1M) man pages.
5. (Optional) Use the log_rotate.sh(1M) command to enable log file rotation.
Log files can become very large, and the log_rotate.sh(1M) command can help in managing log files. For more information, see the log_rotate.sh(1M) man page.
The Sun StorageTek QFS installation and configuration process is complete. You can configure other Sun products at this time.
For example, if you want to configure an Oracle database, see the Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS. The Oracle Real Application Clusters application is the only scalable application that the Sun StorageTek QFS software supports in Sun Cluster environments.
This section describes the recommended procedures for regularly backing up important data and files in a Sun StorageTek QFS environment.
File systems are made up of directories, files, and links. The Sun StorageTek QFS file system keeps track of all the files in the .inodes file. The .inodes file resides on a separate metadata device. The file system writes all file data to the data devices.
It is important to use the qfsdump(1M) command periodically to create a dump file of metadata and file data. The dump process saves the relative path information for each file contained in a complete file system or in a portion of a file system. This protects your data in the event of a disaster.
You can create dump files as often as once or twice a day, depending on your site's requirements. By dumping file system data on a regular basis, you can restore old files and file systems. You can also move files and file systems from one server to another.
The following are some guidelines for creating dump files:
You can run the qfsdump(1M) command manually or automatically. Even if you implement this command to be run automatically, you might also need to run it manually from time to time, depending on your site's circumstances. In the event of a disaster, you can use the qfsrestore(1M) command to re-create your file system. You can also restore a single directory or file. For more information, see the qfsdump(1M) man page and see the Sun StorageTek Storage Archive Manager Troubleshooting Guide.
For more information about creating dump files, see the qfsdump(1M) man page. The following sections describe procedures for issuing this command both manually and automatically.
Perform this step for each Sun StorageTek QFS file system in your environment. Make sure you save each dump file in a separate file.
For each file system, make an entry in the root crontab file so that the cron daemon runs the qfsdump(1M) command periodically.
This entry executes the qfsdump(1M) command at 10 minutes after midnight. It uses the cd(1) command to change to the mount point of the qfs1 file system, and it executes the /opt/SUNWsamfs/sbin/qfsdump command to write the data to tape device /dev/rmt/0cbn.
|
|
1. Use the cd(1) command to go to the directory that contains the mount point for the file system.
2. Use the qfsdump(1M) command to write a dump file to a file system outside of the one you are dumping.
The Sun StorageTek QFS software regularly accesses several files that have been created as part of this installation and configuration procedure. You should back up these files regularly to a file system that is outside the file system in which they reside. In the event of a disaster, you can then restore these files from your backup copies.
The following files are among those that you should back up regularly and whenever you modify them:
For more information about the files you should protect, see the Sun StorageTek Storage Archive Manager Troubleshooting Guide.
| Sun StorageTek QFS Installation and Upgrade Guide | 819-7936-10 |
|
Copyright © 2007, Sun Microsystems, Inc. All Rights Reserved.
To Install the Packages
