| Sun StorEdge SAM-FS Installation and Upgrade Guide |    
|
| Sun StorEdge SAM-FS Installation and Upgrade Guide |
|
| C H A P T E R 3 |
|
Installation and Configuration Tasks |
This chapter describes the procedures for installing and configuring the Sun StorEdge SAM-FS software for the first time. Use these procedures if this is the initial installation of the Sun StorEdge SAM-FS software package at your site. If you are upgrading Sun StorEdge SAM-FS software on an existing server, see Chapter 4, Upgrade and Configuration Tasks.
You can install and configure the Sun StorEdge SAM-FS environment entirely using command-line interface (CLI) commands, or you can use a combination of CLI commands and the File System Manager browser interface tool.
You must have superuser (root) access to perform most of the tasks described in this chapter.
This chapter contains the following sections:
The Sun StorEdge SAM-FS 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.
|
2. Use the cd(1) command to change to the directory where the software package release files reside.
You obtained the release files as described in Obtaining the Release Files. Changing to the appropriate directory differs, depending on your release media, as follows:
3. Use the pkgadd(1M) command to add the SUNWsamfsr and SUNWsamfsu packages.
4. Enter yes or y as the answer to each of the questions.
When you install SUNWsamfsr and SUNWsamfsu, 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. Examine /tmp/SAM_install.log, the Sun StorEdge SAM-FS log file.
This file should show that the pkgadd(1M) command added the SUNWsamfsr and SUNWsamfsu software packages. Make sure that it also installed the Sun StorEdge SAM-FS samst driver. If all files installed properly, the following message appears:
|
In order to have access to the commands and man pages for the Sun StorEdge SAM-FS commands, you must modify your PATH and MANPATH environment variables.
1. For users who will need to access the Sun StorEdge SAM-FS 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-1 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-2 shows how the MANPATH in your .login file might look like after 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 and to change the session timeout.
The procedures in this section are as follows:
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 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 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-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 3-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.
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 Manger, 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 Sun Web Console framework has a default session timeout of 15 minutes. If File System Manger is the only application registered in the Sun 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 root password for the management station.
The root login grants you full administrator privileges to configure, monitor, control, and reconfigure the devices in your Sun StorEdge SAM-FS environment. Only the Sun StorEdge SAM-FS 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 StorEdge SAM-FS 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 StorEdge SAM-FS Storage and Archive Management 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:
# /usr/sbin/useradd/useradd bobsmith
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 functions. The following table lists the five levels of privileges 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:
# /usr/sbin/useradd/useradd guest
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 File System Manager 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. 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.
If you need help accomplishing this task, click Help.
Perform the tasks in this section if you plan to enable archiving to tape or magneto-optical media. You do not need to perform these tasks if you plan to archive to disk.
This section introduces you to the process of verifying, and perhaps updating, the following two files:
The Sun StorEdge SAM-FS package includes the /opt/SUNWsamfs/examples/st.conf_changes file. This file includes configuration information for the following kinds of tape drives:
This section includes the following procedures:
Before starting the configuration process, locate the list of devices that you created in Creating a List of Devices.
If you have not already taken an inventory of your devices and listed them in TABLE 2-2, do so now.
The procedures in this task include an example that is based on the inventory list shown in TABLE 3-2.
|
Note - The device names in TABLE 3-2 are as they appear in the discovery output. |
Depending on the devices on your inventory list, you must complete one or more of the following procedures:
|
Perform this procedure if you have tape drives that you want to include in your Sun StorEdge SAM-FS environment.
In this procedure, you make an entry in the st.conf file for each unique tape drive that is on your inventory list.
1. Use the cp(1) command to copy /kernel/drv/st.conf to a backup file.
2. Use vi(1) or another editor to open file /kernel/drv/st.conf.
3. Find the line that contains the tape-config-list string:
4. Remove the pound character (#) from column 1 of this line.
5. Use vi(1) or another editor to open file /opt/SUNWsamfs/examples/st.conf_changes.
6. Follow these steps for each tape drive on your inventory list that you want to configure.
a. Search the file to find the device definition for the device.
In the example inventory list, the first drive you need to find is the Quantum DLT 7000 tape drive. Find the line that contains the following entry:
b. Copy the line containing the device definition from st.conf_changes to st.conf so it appears after the tape-config-list line.
CODE EXAMPLE 3-5 shows how the st.conf file looks at this point.
... tape-config-list= "QUANTUM DLT7000", "DLT 7000 tape drive", "dlt7-tape", ... |
c. Examine the line you just copied and note the final string enclosed in quotation marks.
In this example, the final string is "dlt7-tape".
d. Search file /opt/SUNWsamfs/examples/st.conf_changes to find another line that begins with the final string you noted in Step c.
The line you are looking for is called the tape configuration value. In this example, it is as follows:
e. Copy the tape configuration value from Step d to file st.conf, placing it after the device definition line you copied in Step b.
CODE EXAMPLE 3-6 shows the lines now contained in the st.conf file.
CODE EXAMPLE 3-7 shows the st.conf file after you have added definitions for the Quantum DLT 7000, the StorageTek 9840, and the IBM ULT3580 tape drives.
7. Replace the comma (,) at the end of the last device definition line with a semicolon (;).
CODE EXAMPLE 3-8 shows the sample st.conf file, with the semicolon after "CLASS_3580".
You do not need to close out of the st.conf file at this point because you continue editing st.conf in the next procedure. It is a good idea to save your changes, however.
|
For each tape drive on your hardware inventory list that is attached through a SCSI or FC interface, you must confirm that an entry in the st.conf file defines that interface. This procedure shows how to verify and, if necessary, add target ID and LUN entries.
|
Note - Do not use this procedure to add interface information for magneto-optical drives. |
1. If the file /kernel/drv/st.conf is not open, use vi(1) or another editor to open it.
2. If you have tape drives to include that are attached through a SCSI interface, do the following:
a. In the st.conf file, find the list of SCSI target IDs and LUNs by looking for entries that have the following format:
target is the target ID for each SCSI drive found. lun is the corresponding LUN for each SCSI drive found.
b. In the list of SCSI targets and LUNs, find the entry that corresponds to each SCSI target and LUN that are on your inventory list.
If the entry is preceded by a pound character (#), delete the character. A pound character marks a line as a comment.
For example, CODE EXAMPLE 3-9 shows the two lines that correspond to the two Quantum DLT 7000 drives, which are attached to LUN 0 and have target IDs 1 and 2.
name="st" class="scsi" target=1 lun=0; name="st" class="scsi" target=2 lun=0; |
Note that an entry might extend over two lines if it contains return characters.
If a SCSI target and LUN line you need is not already listed in st.conf, create an entry for it, following the format shown in Step a.
3. If you have tape drives to include that are attached through an FC interface and you are not using the Sun StorEdge SAN Foundation Software I/O stack, create a line for each FC-attached device.
Place these lines at the end of the SCSI target ID and LUN list, using the following format:
For lun, specify the LUN for the drive.
For world-wide-name, specify the World Wide Name (WWN) for the drive.
For example, CODE EXAMPLE 3-10 shows lines added to support the StorageTek 9840 and IBM ULT3580 tape drives included in the sample inventory list in TABLE 3-2.
4. Save your changes and exit the st.conf file.
Proceed to To Add Device Support in samst.conf Using the CLI if you have any of the following devices in your inventory list:
The /kernel/drv/samst.conf file contains a list of SCSI and FC entries. The following procedures show you how to verify entries for your devices and to update the file if necessary. The samst.conf file works with the /opt/SUNWsamfs/examples/inquiry.conf file to define the devices that can be included in a Sun StorEdge SAM-FS environment. The inquiry.conf file lists all devices that are supported, so you do not need to verify or edit that file.
If you have automated libraries attached through a SCSI or FC interface, you must verify or update the samst.conf file. You can use File System Manager or the CLI to update the samst.conf file, depending on your environment:
|
Note - You do not need to verify device support if you have only network attached automated libraries. |
|
|
Repeat this procedure for each device in your environment.
1. From the File System Manager Servers page, click the name of the server to which you want to add a library.
The File Systems Summary page is displayed.
2. Click the Media Management tab.
The Library Summary page is displayed.
The Add a Library wizard is displayed.
4. Follow the steps in the Add a Library wizard to add the device.
When you have completed the wizard steps, the samst.conf file is automatically updated with the correct information.
1. Use the cp(1) command to copy the /kernel/drv/samst.conf file to a backup file.
2. Use vi(1) or another editor to open the /kernel/drv/samst.conf file.
3. If you have SCSI-attached magneto-optical drives or SCSI-attached libraries that you want to include, do the following:
a. In the samst.conf file, find the list of SCSI targets and LUNs by looking for entries that have the following format:
target is the target ID for each SCSI drive found. lun is the corresponding LUN for each SCSI drive found.
b. In the list of SCSI targets and LUNs, find the entry that corresponds to each SCSI target ID and LUN that are on your inventory list.
If the entry is deleted by a pound character (#), delete the character. A pound (#) character marks a line as a comment.
For example, the StorageTek 9730 automated library is attached to target 0 and LUN 0. The following line corresponds to that interface:
Note that an entry might extend over two lines if it contains return characters.
c. If a SCSI target and LUN line you need is not already listed in samst.conf, create an entry for it, using the format shown in Step a.
4. If you have FC-attached magneto-optical drives or FC-attached automated libraries that you want to include, create a line for each FC-attached device in your inventory list.
Place these lines at the end of the SCSI target and LUN list, using the following format:
For lun, specify the LUN for the drive.
For world-wide-name, specify the WWN for drive.
CODE EXAMPLE 3-11 shows the line added to support the StorageTek L700 tape drive in the sample inventory list in TABLE 3-2.
name="samst" parent="fp" lun=0 fc-port-wwn="500104f00041182b" |
5. Save your changes and exit the samst.conf file.
|
1. Use the cfgadm(1M) command to list the devices included in the Sun StorEdge SAM-FS environment.
2. Examine the output to make sure that it shows all the devices you want configured in your Sun StorEdge SAM-FS environment.
If a device is not shown as being configured, and it should be, you can use the cfgadm(1M) command to configure it. For more information, see the cfgadm(1M) man page.
Because of a bug in the cfgadm(1) command, you might receive a device busy error similar to the following:
# cfgadm -c configure -o force_update c4::500104f000489fe3 cfgadm: Library error: failed to create device node: 500104f00043abfc: Device busy |
Despite the error, the cfgadm(1M) command completely processes the request.
Errors can occur if the st.conf file is not configured properly during Sun StorEdge SAM-FS software installation.
For example, the following message might be found in the sam-log file:
The following device log messages correspond to the sam-log message:
The preceding messages indicate that the appropriate changes have not been made to /kernel/drv/st.conf. Follow the steps in To Add Tape Devices to the /kernel/drv/st.conf File to fix the error.
|
|
Note - You must reboot the system to enable the changes you have made to the st.conf and samst.conf files. |
Issue the touch(1) and init(1M) commands to reboot the system.
Changes to the st.conf and samst.conf files are enabled at this time.
Each Sun StorEdge SAM-FS software environment is unique. The system requirements and hardware differ from site to site. Sun StorEdge SAM-FS environments support a wide variety of tape and optical devices, automated libraries, and disk drives. It is up to you, the system administrator at your site, to set up the specific configuration for your environment.
The master configuration file, /etc/opt/SUNWsamfs/mcf, defines the equipment topology managed by the Sun StorEdge SAM-FS software. This file specifies the devices, automated libraries, and file systems included in the environment. You assign each piece of equipment a unique Equipment Identifier in the mcf file.
You can edit the mcf file in either of two ways:
The mcf file has two kinds of entries:
There are examples of mcf files in /opt/SUNWsamfs/examples. Example mcf file configurations can also be found Appendix D of this manual.
The following sections provide examples and describe activities related to creating and maintaining the mcf file:
|
Note - If you are configuring a SAM-QFS environment, the instructions for configuring a Sun StorEdge QFS file system the mcf file are contained in Sun StorEdge QFS Installation and Upgrade Guide. |
|
When you configure Sun StorEdge SAM-FS file systems using the File System Manager software, it creates or edits the appropriate Sun StorEdge SAM-FS configuration files, including the mcf file, on that server. You can use either File System Manager or the CLI to further edit these files later.
|
Note - If you want to use File System Manager to configure your Sun StorEdge SAM-FS environment and you want to include network attached libraries in this configuration, create your parameters file before you create your mcf file. For information on creating a parameters file, see Creating Parameters Files for Network Attached Automated Libraries. |
Follow these steps to add a server and create a file system:
1. Log in to the File System Manager browser interface as an administrator user.
The Servers page is displayed.
The Add Server page is displayed.
3. 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.
6. Complete the steps for creating a new file system.
When you have completed this process, the mcf file is created. For more information, see the File System Manager online help.
|
Use vi(1) or another editor to create the /etc/opt/SUNWsamfs/mcf file.
When you create the mcf file, follow these guidelines:
CODE EXAMPLE 3-12 shows the mcf file fields.
The mcf file can contain both comment lines and lines that pertain to a device. The types of lines that can pertain to a device are as follows:
TABLE 3-3 describes the information in each field and specifies whether the field is required or optional.
When your system boots, a series of messages is written to /var/adm/messages. These messages identify the Sun Solaris hardware path to each of the peripherals on your system. You can use this information to create the mcf file. To display information from the latest system reboot, search backward from the end of the file.
As CODE EXAMPLE 3-13 shows, each SCSI peripheral has three lines. The sixth field, samst2, indicates that these lines are associated with each other.
The first line displays the vendor and product information that the SCSI peripheral reported to the Sun Solaris kernel.
The second line displays the SCSI bus, SCSI target ID, and LUN of the peripheral.
The third line displays the peripheral's hardware path. This path is reflected in the /devices directory. Symbolic links (symlinks) to the /devices directory are set up in the /dev/st, /dev/samst, and /dev/rmt directories. Note that the third line wraps to the next line in CODE EXAMPLE 3-13.
Matching the symbolic link to the correct peripheral is the key to configuring a Sun StorEdge SAM-FS environment. Use the ls(1) command with the -l option in both the /dev/st, /dev/samst and /dev/rmt directories to display the path name of the peripheral.
You might also want to set up the device down notification script at this point. The dev_down.sh(1M) man page contains information about setting up this script, which sends email to root when a device is marked down or off. For more information, see the dev_down.sh(1M) man page.
|
Perform this procedure if you created your mcf file using a text editor. If you created your mcf file using File System Manager, you do not need to verify its syntax.
Enter the sam-fsd(1M) command to verify the mcf file.
If the mcf file is free of syntax errors, the sam-fsd(1M) output includes information about the file systems, archiving, and other system information. If the mcf file contains syntax or other errors, however, the output is similar to that shown in CODE EXAMPLE 3-14.
If the mcf file has errors, return to Setting Up the Environment Configuration and refer to the mcf(4) man page for information on how to create this file correctly. You can also refer to the mcf file examples shown in Appendix D, mcf File Examples.
Use the procedures in this section to specify mount parameters for the Sun StorEdge SAM-FS file system.
You can specify mount parameters in the following ways:
For a list of available mount options, see the mount_samfs(1M) man page.
This section describes how to edit the /etc/vfstab file.
TABLE 3-4 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.
|
|
The example in this task assumes that /samfs1 is the mount point of the samfs1 file system.
1. Use vi(1) or another editor to open the /etc/vfstab file.
2. Create an entry for each Sun StorEdge SAM-FS file system.
CODE EXAMPLE 3-15 shows header fields and entries for a Sun StorEdge SAM-FS file system.
3. Use the mkdir(1M) command to create the mount point.
You can create the /etc/opt/SUNWsamfs/samfs.cmd file as the place from which the system reads mount parameters. If you are configuring multiple Sun StorEdge SAM-FS systems with multiple mount parameters, consider creating this file.
For more information on the mount(1M) command, see the mount_samfs(1M) man page.
|
|
If you specify non-default mount options when creating a file system in File System Manager, the samfs.cmd file is created or updated with those mount options.
Follow these steps to edit a file system's mount options:
1. From the Servers page, click 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.
The new mount options are written to the samfs.cmd file.
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 StorEdge SAM-FS File System Configuration and Administration Guide, or see the samfs.cmd(4) man page.
This section tells you how to initialize the environment and the file system, and how to mount the file system.
|
Use the samd(1M) config command to initialize the Sun StorEdge SAM-FS environment.
|
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.
CODE EXAMPLE 3-16 shows the command to initialize a file system with the Family Set name of samfs1.
The actual numbers returned vary from file system to file system.
The mount(1M) command mounts a file system and reads the /etc/vfstab and samfs.cmd configuration files. For information on the mount(1M) command, see the mount_samfs(1M) man page.
1. From the Servers page, click 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.
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-17 shows the output from a mount(1M) command issued to verify whether example file system samfs1 is mounted.
3. (Optional) Issue 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. For example:
This section outlines additional tasks that you might need to complete in order to finish the configuration of the Sun StorEdge SAM-FS environment. Some of these tasks are optional, depending on your specific environment. The following tasks are covered:
Perform this task if you want the Sun StorEdge SAM-FS file system to be NFS shared.
This procedure uses 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 Sun Solaris OS when you enter init(1M) state 3.
1. Use vi(1) or another editor to add a share(1M) command to the /etc/dfs/dfstab file.
2. Use the ps(1) command to determine whether nfs.server is running.
In this sample output, the lines that contain /usr/lib/nfs indicate that the NFS server is mounted.
3. If nfs.server is not running, start it:
4. (Optional) Type the share(1M) command at a root shell prompt.
Perform this step if you want to NFS-share the file system immediately.
If no NFS-shared file systems exist when the Sun Solaris OS boots, the NFS server is not started. CODE EXAMPLE 3-18 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 - /samfs1 - "SAM-FS" |
Some NFS mount parameters can affect the performance of an NFS mounted Sun StorEdge SAM-FS file system. You can set these parameters in the /etc/vfstab file as follows:
For more information on these parameters, see the mount_nfs(1M) man page.
On the client systems, mount the server's Sun StorEdge SAM-FS file system at a convenient mount point.
1. On an 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 StorEdge SAM-FS file system at a convenient mount point.
The following example mounts server:/samfs1 on the /samfs1 mount point:
2. Save and close the /etc/vfstab file.
3. Enter the mount(1M) command.
For example, the following mount(1M) command mounts the samfs1 file system:
Alternatively, the automounter can do this, if you prefer. Follow your site procedures for adding server :/samfs1 to your automounter maps. For more information on automounting, see the automountd(1M) man page.
Perform the applicable procedure in this section if you want to include network attached automated libraries in your Sun StorEdge SAM-FS environment.
You can include automated libraries in a Sun StorEdge SAM-FS environment either by directly attaching them to the server or by attaching them to the environment's network. Libraries attached through a SCSI or Fibre Channel (FC) attachment are direct attached libraries. Libraries attached through a network attachment are network attached libraries. In this task, you create a parameters file for each network attached library to be included in your environment.
To configure a network attached library in your Sun StorEdge SAM-FS environment, find your library in the following list and go to the page indicated:
Typically, the Sun StorEdge SAM-FS processes have exclusive control over a library's drives as declared in the host system's mcf file. In many cases, however, drives are defined in individual mcf files that are used by independent copies of Sun StorEdge SAM-FS processes. If a process is not using a drive, the drive stays idle.
The shared-drives capability enables two or more mcf files to define the same drive, making the drive available to multiple Sun StorEdge SAM-FS processes. However, these multiple processes cannot share media. Each Sun StorEdge SAM-FS process must still maintain its own set of VSNs.
The shared-drives feature can be useful, for example, if a library is attached to more than one host system in a Sun StorEdge SAM-FS environment. The Sun StorEdge SAM-FS processes coordinate the use of a drive and keep the drives in a library busy.
You can configure some network attached libraries to share one or all media drives between multiple Sun StorEdge SAM-FS processes on multiple host systems. All of the StorageTek ACSLS-attached libraries support shared drives in Sun StorEdge SAM-FS environments.
To implement one or more shared drives, specify the shared keyword in the parameters file for each drive that is to be shared. The placement of the shared keyword is specific to each manufacturer's library, so see the following vendor-specific sections for more information.
By default, a cartridge in a shared drive can be idle for 60 seconds before being unloaded. To change this timing, specify the shared_unload directive in the defaults.conf file. For more information on this directive, see the defaults.conf(4) man page.
|
Note - The examples and the discussions in the following subsections mention both the parameters files for network attached automated libraries and the mcf file. The Sun StorEdge SAM-FS mcf file is the main configuration file for Sun StorEdge SAM-FS software. You created your mcf file in Setting Up the Environment Configuration. The parameters file and the mcf file are both mentioned in this section because the two files reference each other. |
The ADIC/Grau automated library operates within Sun StorEdge SAM-FS environments through the grauaci interface. This interface uses the DAS/ACI 3.10 interface supplied by ADIC/Grau. For more information on the DAS/ACI interface, see your ADIC/Grau documentation.
|
Note - ADIC/Grau network attached libraries are not supported by Sun StorEdge SAM-FS software on an x64 hardware platform. |
|
|
Follow this procedure to create a parameters file for each ADIC/Grau library that you want to configure.
1. Ensure that the ADIC/Grau automated library is prepared for inclusion in a Sun StorEdge SAM-FS environment.
Ensure that the following are true:
2. Use the cd(1) command to change to the /etc/opt/SUNWsamfs directory.
The parameters file can be written to any directory, but Sun recommends that you write it to /etc/opt/SUNWsamfs.
|
Note - When you created your mcf file, in Setting Up the Environment Configuration, you included the full path name to the parameters file in the mcf file. Make sure that the mcf file points to the correct location for the parameters file that you create in this procedure. |
3. Use vi(1) or another editor to open a new file.
It is a good idea to give the new file a name that corresponds to the library that you are configuring. For example, you might invoke vi(1) as follows:
4. Edit the ADIC/Grau parameters file to consist of a list of keyword = value parameter lines.
The various keyword values identify the ADIC/Grau automated libraries, the drives associated with the libraries, and the server name. All keyword and value entries are case sensitive, so enter them exactly as specified in the DAS configuration file and in the Sun StorEdge SAM-FS mcf file.
TABLE 3-5 shows the keyword = value parameters that must appear in the ADIC/Grau parameters file.
Comments can appear anywhere on any line, but they must begin with a pound sign (#). The system ignores characters to the right of the pound sign.
If the ADIC/Grau library contains various media types, there is a media changer for each media type. Each media changer has a unique client name in the DAS configuration, a unique library catalog, and a unique parameters file.
The sample ADIC/Grau parameters file shown in CODE EXAMPLE 3-19 defines one ADIC/Grau automated library supporting DLT tape and one ADIC/Grau automated library supporting a Hewlett-Packard optical drive.
|
Note - CODE EXAMPLE D-11 in Example mcf File Entries for Network Attached Libraries shows the mcf file that corresponds with the ADIC/Grau network attached automated library parameters file example that was created in this procedure. The example mcf points to the grau50 file in the /etc/opt/SUNWsamfs directory. |
The following directory contains diagnostic information that can be useful for troubleshooting:
The system creates files in this directory that are named graulog-eq, where eq is the Equipment Ordinal as defined in the mcf file. For more information, see the grauaci(7) and the mcf(4) man pages.
The Fujitsu LMF automated library operates in Sun StorEdge SAM-FS environments through the fujitsulmf interface supplied by Fujitsu. For more information on LMF, see the LMF MTL Server/Client User's Guide or the LMF SAM-FS Linkage Operations Guide. You can obtain both of these publications from the Fujitsu Corporation.
|
Note - Fujitsu LMF network attached libraries are not supported by Sun StorEdge SAM-FS software on an x64 hardware platform. |
|
|
Follow this procedure to create a parameters file for each Fujitsu LMF library that you want to configure.
1. Ensure that the Fujitsu LMF automated library is prepared for inclusion in a Sun StorEdge SAM-FS environment.
Ensure that the following are true:
2. Use the cd(1) command to change to the /etc/opt/SUNWsamfs directory.
The parameters file can be written to any directory, but Sun recommends that you write it to /etc/opt/SUNWsamfs.
|
Note - When you created your mcf file, in Setting Up the Environment Configuration, you included the full path name to the parameters file in the mcf file. Make sure that the mcf file points to the correct location for the parameters file that you create in this procedure. |
3. Use vi(1) or another editor to open a new file.
It is a good idea to give the new file a name that corresponds to the library that you are configuring. For example, you might invoke vi(1) as follows:
4. Edit the Fujitsu LMF parameters file to consist of a list of drivename = value parameter lines.
The parameters file consists of lmfdrive drivename = value definition lines and comment lines. There must be one lmfdrive line for each drive assigned to the client automated library.
All drivename and value information is case-sensitive. TABLE 3-6 shows the values that you can specify for drivename and value.
|
The path to the drive. This path must match the Equipment Identifier field of the mcf file. |
Comments can appear anywhere on any line, but they must begin with a pound sign (#). The system ignores characters to the right of the pound sign.
CODE EXAMPLE 3-20 shows a parameters file for a Fujitsu LMF automated library.
|
Note - CODE EXAMPLE D-12 in Example mcf File Entries for Network Attached Libraries shows the mcf file that corresponds with the Fujitsu LMF network attached automated library parameters file that was created in this procedure. The example mcf file points to file lmf50 in the /etc/opt/SUNWsamfs directory. |
The IBM 3494 automated tape library operates in Sun StorEdge SAM-FS environments with the assistance of the IBM lmcpd daemon package. You can obtain the IBM lmcpd daemon package from IBM.
|
Note - IBM 3494 network attached libraries are not supported by Sun StorEdge SAM-FS software on an x64 hardware platform. |
|
|
The IBM 3494 automated library can be used as a single physical library or as multiple logical libraries. If you divide this library into multiple logical libraries, create a parameters file for each logical library.
Follow this procedure to create a parameters file for each physical or logical library that you want to include in the Sun StorEdge SAM-FS environment.
1. Ensure that the IBM 3494 automated library is prepared for inclusion in a Sun StorEdge SAM-FS environment.
Ensure that the following are true:
2. Use the cd(1) command to change to the /etc/opt/SUNWsamfs directory.
The parameters file can be written to any directory, but Sun recommends that you write it to /etc/opt/SUNWsamfs.
|
Note - When you created your mcf file, in Setting Up the Environment Configuration, you included the full path name to the parameters file in the mcf file. Make sure that the mcf file points to the correct location for the parameters file that you create in this procedure. |
3. Use vi(1) or another editor to open a new file.
It is a good idea to give the new file a name that correspond to the library that you are configuring. For example, you might invoke vi(1) as follows:
4. Edit the IBM 3494 parameters file to consist of a list of keyword = value and pathname = value pairs.
All arguments are case-sensitive. TABLE 3-7 shows how to specify the parameters.
Comments can appear anywhere on any line, but they must begin with a pound sign (#). The system ignores characters to the right of the pound sign.
CODE EXAMPLE 3-21 shows an example /etc/ibmatl.conf file. Information for this file was obtained from the mtlib utility supplied by IBM.
# # This is file: /etc/ibmatl.conf # Set this file up according the documentation supplied by IBM. 3493a 198.174.196.50 test1 |
After the lmcpd daemon is running, you can use the IBM mtlib utility to obtain the device numbers. CODE EXAMPLE 3-22 shows output from mtlib.
# mtlib -l 3493a -D 0, 00145340 003590B1A00 1, 00145350 003590B1A01 |
CODE EXAMPLE 3-23 shows a sample parameters file for an IBM 3494 library.
|
Note - CODE EXAMPLE D-13 in Example mcf File Entries for Network Attached Libraries shows the mcf file that corresponds with the IBM 3494 network attached automated library parameters file that was created in this procedure. The example mcf file points to file ibm50 in the /etc/opt/SUNWsamfs directory. |
The Sony network attached automated library operates within the Sun StorEdge SAM-FS environment through the DZC-8000S Application Interface Library package. This software package provides the application programmer interface (API) to the PetaSite Controller (PSC). For more information on the DZC-8000S interface, see the Sony PetaSite Application Interface Library DZC-8000S, which is available from Sony.
|
Note - Sony network attached libraries are not supported by Sun StorEdge SAM-FS software on an x64 hardware platform. |
|
|
Follow this procedure to create a parameters file for each Sony network attached library that you want to configure.
1. Ensure that the Sony network attached automated library is prepared for inclusion in a Sun StorEdge SAM-FS environment.
Ensure that the following are true:
2. Use the cd(1) command to change to the /etc/opt/SUNWsamfs directory.
The parameters file can be written to any directory, but Sun recommends that you write it to /etc/opt/SUNWsamfs.
|
Note - When you created your mcf file, in Setting Up the Environment Configuration, you included the full path name to the parameters file in the mcf file. Make sure that the mcf file points to the correct location for the parameters file that you create in this procedure. |
3. Use vi(1) or another editor to open a new file.
It is a good idea to give the new file a name that correspond to the library that you are configuring. For example, you might invoke vi(1) as follows:
4. Edit the Sony parameters file to consist of a list of keyword = value parameter lines.
The various keyword values identify the Sony automated libraries, the drives associated with the libraries, and the host name. All keyword and value entries are case-sensitive, so enter them exactly as specified in the configuration file and in the Sun StorEdge SAM-FS mcf file.
TABLE 3-8 shows the keyword = value parameters that must appear in the Sony parameters file. All parameters are required.
Comments can appear anywhere on any line, but they must begin with a pound sign (#). The system ignores characters to the right of the pound sign.
CODE EXAMPLE 3-24 shows a parameters file for a Sony network attached automated library.
|
Note - CODE EXAMPLE D-14 in Example mcf File Entries for Network Attached Libraries shows the mcf file that corresponds with the Sony network attached automated library parameters file that was created in this procedure. The example mcf file points to file sonyfile in the /etc/opt/SUNWsamfs directory. |
In many respects, the way in which Sun StorEdge SAM-FS systems interoperate with StorageTek ACSLS-attached automated libraries is very similar to the way in which they interoperate with direct attached automated libraries. However, the installation and configuration procedure of a StorageTek ACSLS-attached automated library requires additional steps.
The StorageTek ACSLS software package controls the automated library. Daemon software controls the StorageTek automated library through the ACSAPI interface.
|
|
Follow this procedure to create a parameters file for each StorageTek ACSLS-attached library that you want to configure.
1. Ensure that the StorageTek ACSLS-attached automated library is prepared for inclusion in a Sun StorEdge SAM-FS environment.
Ensure that the following are true:
2. Use the cd(1) command to change to the /etc/opt/SUNWsamfs directory.
The parameters file can be written to any directory, but Sun recommends that you write it to /etc/opt/SUNWsamfs.
|
Note - When you created your mcf file, in Setting Up the Environment Configuration, you included the full path name to the parameters file in the mcf file. Make sure that the mcf file points to the correct location for the parameters file that you create in this procedure. |
3. Use vi(1) or another editor to open a new file.
It is a good idea to give the new file a name that correspond to the library that you are configuring. For example, you might invoke vi(1) as follows:
4. Edit the StorageTek parameters file to consist of a list of keyword = value parameter lines.
TABLE 3-9 shows the keywords to use.
|
(Optional) The user identification value used by the StorageTek software for access control. If the access = parameter is not supplied, the access control string is a null string, indicating that there is no userid. |
|
|
The host name of the server running the StorageTek ACSLS interface. |
|
|
The port number used for communication between ACSLS and the Sun StorEdge SAM-FS software. For information on what to enter for the portnum argument, see the stk(7) man page. |
|
|
The name of the Sun StorEdge SAM-FS server on the LAN that connects to the ACSLS host. Specify this directive only if you are including a multihomed Sun StorEdge SAM-FS server in your environment. The default is the name of the local host. |
|
|
The port on the ACSLS server to which the StorageTek SSI daemon is to send its ACSLS requests. Specify either 0 or a value from 1024 to 65535, inclusive. Setting this variable to 0 or leaving it unset causes the system to query the port mapper on the ACSLS server. |
|
|
The CAP (Cartridge Access Port), in terms of the StorageTek library, to be used when the export(1M) -f command is specified. The capid description starts with an open parenthesis followed by three keyword = value pairs followed by a closing parenthesis. Use a comma (as shown), a colon, or a space to separate the keyword = value pairs. For acsnum, specify the ACS number for this CAP as configured in the StorageTek library. For lsmnum, specify the LSM number for this CAP as configured in the StorageTek library. For capnum, specify the CAP number for this CAP as configured in the StorageTek library. |
|
|
The capacities of the supported cartridges. Use a comma to separate the index = value pairs, and enclose the string in parentheses. For index, specify the index of the supplied media_type file, located in the following ACSLS directory: /export/home/ACSSS/data/internal/mixed_media/media_types.dat. For value, specify the capacity of the cartridge type in units of 1024 bytes. In general, it is necessary to supply a capacity entry only for an index of new cartridge types or to override the supported capacity. |
|
|
device-path-name = (acs = value, lsm = value, panel = value, drive = value ) [shared ] |
|
|
The path to the device on the client. Specify one device-path-name = entry for each drive attached to this client. This parameter describes the drive within the StorageTek automated library. This description starts with an open parenthesis followed by four keyword = value pairs and a closing parenthesis. Use a comma (as shown), a colon, or a space to separate the keyword = value pairs. For the value arguments, use the information supplied by the ACSLS query drive command. The following are the value specifications:
The shared keyword is optional. It specifies that the drive can be shared between two or more Sun StorEdge SAM-FS processes from two or more hosts. For more information on implementing shared drives, see About Shared Drives or see the stk(7) man page. |
|
CODE EXAMPLE 3-25 shows a parameters file for a StorageTek ACSLS-attached automated library.
|
Note - CODE EXAMPLE D-15 in Example mcf File Entries for Network Attached Libraries shows the mcf file that corresponds with the StorageTek ACSLS-attached automated library parameters file that was created in this procedure. The example mcf file points to file stk50 in the /etc/opt/SUNWsamfs directory. |
Perform the tasks described in this section if you are archiving to removable media.
For libraries with more than a single drive, the order in which drive entries appear in the mcf file must match the order in which they are identified by the library controller. The drive that the library controller identifies as the first drive must be the first drive entry for that library in the mcf, and so on. The following sections describe methods for checking the drive order as seen by Sun StorEdge SAM-FS for a direct attached library.
The main objective of this task is to develop a list of drive number identifiers and the tape devices to which they are correlated.
The procedure varies, depending on whether your automated library has a front panel and whether it has tape or magneto-optical drives. Use one of the following procedures to check the drive order of each library:
|
|
Perform this procedure in order to verify the correct association between the remote devices and the drives.
This procedure has two main phases:
For information on the order in which the drives appear in the front panel, consult the documentation from the vendor. This differs from library to library.
The procedure that follows is a framework for an iterative process. The actual steps that you must perform depend on your specific library. Consult your vendor documentation for more information.
1. Use the samd(1M) start command to start the Sun StorEdge SAM-FS software:
2. Verify the order of the drives.
If the automated library contains more than one drive, list the drives in the mcf file in the same order in which the drives are viewed by the automated library's controller. The drive order that the media changer controller recognizes can be different from the order of the devices as reported in the /var/adm/messages file.
3. Verify the order in which the drives are recognized by the automated library's controller.
Check the SCSI target IDs or World Wide Names (WWNs) displayed by the control panel of the automated library. For optical drives, read the SCSI target IDs displayed on the control panel for your automated library. The order in which the drive targets are reported should be the order in which they are configured in the mcf file.
To determine whether the drives become active when loaded with a cartridge, you can visually inspect the drives or you can use the samu(1M) utility's r display.
Refer to your hardware maintenance manual for instructions on identifying and setting target addresses.
|
|
Follow the steps in this procedure for each drive in the library.
If your automated library contains more than one drive, list the drives in the mcf file in the same order in which the drives are viewed by the automated library's controller. The drive order that the media changer controller recognizes can be different from the order of the devices as reported in the /var/adm/messages file.
If you change any information in the mcf file as a result of this procedure, you must propagate the changes to the rest of the system. For information on propagating mcf file changes, see the Sun StorEdge SAM-FS File System Configuration and Administration Guide.
1. Use the samd(1M) start command to start the software:
2. Use the samcmd(1M) unavail command to make the drive state unavailable to the Sun StorEdge SAM-FS file system:
For eq, specify the Equipment Ordinal, as specified in the mcf file, of the drive you are testing.
For more information about the format of the samcmd(1M) command, see the samcmd(1M) man page.
3. Use the samload(1M) command to load a cartridge into the drive.
Use this command in one of the following formats:
TABLE 3-10 shows the arguments for these commands.
For more information about the format of the samload(1M) command, see the samload(1M) man page.
4. Use the mt(1) command to determine whether the correct drive responds while under Sun StorEdge SAM-FS control:
For x, specify the raw tape device entry as specified in the mcf file.
CODE EXAMPLE 3-27 shows mt(1) command output that indicates that a tape is in the drive.
# mt -f /dev/rmt/0 status DLT 7000 tape drive tape drive: sense key(0x2)= Not Ready residual= 0 retries= 0 file no= 0 block no= 0 |
If the tape did not load or the drive did not return a status, the drive might not be listed in the proper order in the mcf. Make sure that the order is correct in the mcf file, and repeat this test.
|
|
Follow the steps in this procedure for each drive in the library.
If your automated library contains more than one drive, list the drives in the mcf file in the same order in which the drives are viewed by the automated library's controller. The drive order that the media changer controller recognizes can be different from the order of the devices as reported in the /var/adm/messages file.
If you change any information in the mcf file, you must propagate the changes to the rest of the system. For information on propagating mcf file changes, see the Sun StorEdge SAM-FS File System Configuration and Administration Guide.
1. Use the samd(1M) start command to start the software:
2. Use the samcmd(1M) unavail command to make the drive state unavailable to the Sun StorEdge SAM-FS file system:
For eq, specify the Equipment Ordinal, as specified in the mcf file, of the drive you are testing.
For more information about the format of the samcmd(1M) command, see the samcmd(1M) man page.
3. Use the samload(1M) command to load a cartridge into the drive.
Use this command in one of the following formats:
TABLE 3-10 shows the arguments for these commands.
For more information about the format of the samload(1M) command, see the samload(1M) man page.
4. Use the dd(1M) command to determine whether the correct drive responds while under Sun StorEdge SAM-FS control:
For device-path, specify the samst device entry as specified in the mcf file.
CODE EXAMPLE 3-28 shows a status message that indicates that an optical cartridge is in the selected device.
# dd if=/dev/samst/c0t3u0 bs=2k iseek=3374 of=/tmp/junk count=10 10+0 records in 10+0 records out |
CODE EXAMPLE 3-29 shows a status message that indicates that an optical cartridge is not in the selected device.
# dd if=/dev/samst/c0t5u0 bs=2k iseek=3374 of=/tmp/junk1 count=10 read: I/O error 0+0 records in 0+0 records out |
If the optical cartridge did not load or if the device returned messages like those in CODE EXAMPLE 3-29, the drives might not be listed in the correct order in the mcf file. Make sure that the order is correct in the mcf file, and repeat this test.
The archiver copies files from a Sun StorEdge SAM-FS file system to volumes on removable media cartridges or to disk partitions in another file system. You can tune the archiver operations to suit the types of files at your site and to suit your site's data protection needs by creating an archiver command file to reside in /etc/opt/SUNWsamfs/archiver.cmd. This section guides you through the process of configuring an archiver.cmd file.
By default, the archiver automatically archives all files under all Sun StorEdge SAM-FS mount points. You are not required to create an archiver.cmd file, but the efficiency and performance of the archiver increase if you tune the archiver to your site. The default settings for the archiver are as follows:
You can divide your archiver.cmd file into two main areas, as follows:
Certain directives are typically specified globally and others are typically specified only for individual file systems.
CODE EXAMPLE 3-30 shows a simple archiver.cmd file that you can add to or change as needed. You should add directives only to accommodate more archive sets, copies, and VSN usage.
CODE EXAMPLE 3-31 shows a more complex archiver.cmd file.
For comprehensive information on the archiver.cmd directives, see the archiver.cmd(4) man page and see the information on the archiver in the Sun StorEdge SAM-FS Storage and Archive Management Guide.
When you create or edit an archive policy for a file system within the File System Manager interface, the archiver.cmd file is automatically created or edited.
Follow these steps to create a policy:
1. From the Servers page, click the name of the server for which you want to create a policy.
The File Systems Summary page is displayed.
2. Click the Archive Management tab.
The Archive Policies Summary page is displayed.
The New Archive Policy wizard is displayed.
4. Follow the steps in the wizard.
For detailed instructions on using the New Archive Policy wizard, see the File System Manager online help.
When you save the new archive policy, it is automatically written to the archiver.cmd file.
1. Use vi(1) or another editor to create file /etc/opt/SUNWsamfs/archiver.cmd.
2. Add directives to satisfy the archiving needs at your site.
For more information about the directives in this file, see About the archiver.cmd File.
3. Close the archiver.cmd file.
4. Verify the archiver.cmd file for correctness.
5. Correct any errors in the archiver.cmd file before proceeding to the next task.
Disk archiving is the process of writing archive copies of file data to an online disk in another file system. The file system to which the archive copies are written can be any UNIX file system; it does not have to be a Sun StorEdge SAM-FS or Sun StorEdge QFS file system. However, the host system to which archive files are written must have at least one Sun StorEdge SAM-FS or Sun StorEdge QFS file system installed on it.
Disk archiving differs from traditional archiving in several ways. For example, it does not use automated libraries or removable media cartridges. You can, however, specify that one set of archive copies be written to disk and another set be written to other archive media. For additional information on disk archiving, see the Sun StorEdge SAM-FS Storage and Archive Management Guide.
If you plan to enable disk archiving, complete the following procedures:
|
Note - You can use the File System Manager interface to enable disk archiving by specifying that an archive policy should archive to disk VSNs. This will automatically update both the archiver.cmd file and the diskvols.conf file. See To Create an archiver.cmd File Using File System Manager. |
|
|
1. Become superuser on the host system that contains the files you want to archive.
2. Use vi(1) or another editor to create or to open the file /etc/opt/SUNWsamfs/archiver.cmd.
3. Edit the archiver.cmd file to add disk archive set directives.
CODE EXAMPLE 3-32 shows a fragment from an archiver.cmd file that defines disk archive sets.
# vsns archset1.1 dk disk01 archset2.1 dk disk02 archset3.1 dk disk03 endvsns |
For more information on specifying archive sets, see the archiver.cmd(4) man page or see the Sun StorEdge SAM-FS Storage and Archive Management Guide.
4. Save and close the archiver.cmd file.
5. Use vi(1) or another editor to create a file named diskvols.conf.
6. In the diskvols.conf file, specify the online disk directories to which the archive copies will be written.
CODE EXAMPLE 3-33 shows a diskvols.conf file that archives files from three archive sets. The disk volumes named disk01 and disk02 reside in a file system on the server system named otherserver. Disk volume disk03 resides on the same host as the files to be archived.
As CODE EXAMPLE 3-33 shows, the diskvols.conf file must contain data in two fields: the VSN_name field and the path field. TABLE 3-12 shows the information that must appear in this file.
The following additional rules apply to the diskvols.conf file:
For more information about the diskvols.conf file, see the diskvols.conf(4) man page.
7. Save and close the diskvols.conf file.
8. Create directories in the file system to which the archive copies will be written.
9. Use the archiver(1M) command with its -lv options to verify the correctness of the syntax in the archiver.cmd(4) file:
10. If any errors are found, correct them before proceeding.
|
|
Perform this procedure only if you are writing your archive copies to a host system that is different from the host system upon which the source files reside. In this situation, you are creating a client/server environment:
1. Become superuser on the server system.
This is the system to which the archive copies will be written.
2. Use the cd(1) command to change to the file system to which you want to write the archive copies.
3. Create directories in the file system to which the archive copies will be written.
4. Use vi(1) or another editor to create the file /etc/opt/SUNWsamfs/diskvols.conf.
This file contains the clients and endclients directives and names the client system upon which the files to be archived reside, as shown in CODE EXAMPLE 3-34.
# This is # file destination_server:/etc/opt/SUNWsamfs/diskvols.conf # on the server # clients sourceserver endclients |
5. Save and close the diskvols.conf file.
The /opt/SUNWsamfs/examples/defaults.conf file contains directives that control automated library actions in a Sun StorEdge SAM-FS environment. You can change these settings at any time after the initial installation. You might change them to accommodate changes in your site's library information, for example. If you change the information in the defaults.conf file after the system is running, you must then issue commands to propagate the defaults.conf file changes to the file system. The procedures for propagating the defaults.conf file changes are described in the Sun StorEdge SAM-FS File System Configuration and Administration Guide.
CODE EXAMPLE 3-35 shows lines from an example defaults.conf file. This file shows several parameters that can affect the configuration of an automated library.
Another sample file is located in /opt/SUNWsamfs/examples/defaults.conf.
1. Read the defaults.conf(4) man page to determine the defaults you want to change.
2. Use the cp(1) command to copy /opt/SUNWsamfs/examples/defaults.conf to its functional location.
3. Use vi(1) or another editor to edit the file.
Edit the lines that control those aspects of the system that you want to change. Remove the pound character (#) from column 1 of the lines you change.
4. Use the pkill(1M) command to send a SIGHUP signal to 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(4) file.
This section describes two common features that you can control from the defaults.conf(4) file. For more information, see the defaults.conf(4) man page.
If you have a tape library that uses a barcode reader, you can configure the system to set the tape label equal to the first or last characters of the barcode label. You can accomplish this by setting the labels directive in the defaults.conf file, as shown in TABLE 3-13.
If labels = barcodes or labels = barcodes_low is in effect, the Sun StorEdge SAM-FS system writes a label before the write is started for any tape that is mounted for a write operation that is write enabled, is unlabeled, and has a readable barcode.
You can set the unload and unload wait time for devices using the dev_unload and dev_delay directives, respectively. These directives enable you to set values that meet your site's requirements.
The format of the dev_unload parameter is as follows:
For dev, specify the device type as specified in the mcf(4) man page.
For seconds, specify the number of seconds that you want the system to wait after an unload command is issued. This gives the automated library time to eject the cartridge, open the door, and perform other operations before the cartridge is removed. The default is 0.
The format of the dev_delay directive is as follows:
For dev, specify the device type as specified in the mcf(4) man page.
For seconds, specify the minimum number of seconds that you want to have elapse between the time when a cartridge is loaded and the time when the same cartridge is able to be unloaded. The default is 30.
If you have standalone tape or optical devices, or if your automated library has no barcode reader, you must label cartridges as described in this section.
To label cartridges, use the tplabel(1M) command for tapes or use the odlabel(1M) command for optical disks. These commands create a cartridge label that the Sun StorEdge SAM-FS software can read.
The tplabel(1M) command has the following format:
TABLE 3-14 shows the arguments for this command.
The odlabel(1M) command has the following format:
TABLE 3-15 shows the arguments for this command.
You can use the cartridges after you issue these commands. Both the tplabel(1M) and the odlabel(1M) commands accept a -old option that you can use to relabel previously labeled cartridges. For more information about these commands, see the tplabel(1M) and odlabel(1M) man pages.
If your library uses barcodes, labels = barcodes is set by default, and the result is that the first six characters are used for the volume serial number (VSN).
If your library uses barcodes, and you want the last six characters to become the VSN for the cartridge, edit the /etc/opt/SUNWsamfs/defaults.conf file and include the following line:
When the software loads a barcoded cartridge for a write operation, it writes a label on the cartridge before the write begins. The cartridge must be write enabled, be unlabeled, and have a readable barcode.
After you mount the Sun StorEdge SAM-FS file system, the software creates catalogs for each automated library configured in the mcf file. If you have a network attached automated library, however, you need to populate the library's catalog. There are several ways to populate an automated library. The appropriate method depends on the number of volumes you want to include in the catalog.
The following sections describe various methods for populating an automated library's catalog:
|
Note - The slot position of a tape in a network attached automated library has no relationship to the slot number of the volume in a Sun StorEdge SAM-FS library catalog. |
1. Use vi(1) or another editor to create an input file that contains the slot number, the volume's VSN, the barcode number, and the media type.
Note the following when creating the input file:
CODE EXAMPLE 3-36 shows the example file input_vsns.
0 TAPE01 "TAPE 01" lt 1 TAPE02 TAPE02 lt 2 TAPE03 TAPE03 lt |
2. Use the build_cat(1M) command to create the catalog.
The syntax for the build_cat(1M) command is as follows:
TABLE 3-16 shows the arguments for this command.
For example, you might specify the following build_cat(1M) command:
For more information, see the build_cat(1M) man page.
|
|
Perform this procedure for each cartridge that you want to include in the catalog. The cartridge must be physically present in the automated library for the import(1M) command to be successful. If the cartridge is not present, the entry goes into the historian.
Use the import(1M) command to import catalog entries into the default catalog:
For VSN, specify the VSN identifier for a volume. If a VSN name contains one or more space characters, enclose the VSN name in quotation marks (" ").
For eq, specify the Equipment Ordinal as specified for the device in the mcf file.
For more information on the import(1M) command, see the import(1M) man page.
Use this procedure to populate an IBM 3494 automated library for which access=private is specified in the IBM 3494 parameters file.
|
Note - If you have an IBM 3494 library that is divided into multiple logical libraries (for which access=shared is specified in the IBM 3494 parameters file), use one of the previous methods to populate the catalog: To Populate an Automated Library With Many Volumes or To Populate an Automated Library With a Small Number of Volumes. |
Insert into the mail slot the media cartridge that you want to include in this library's catalog.
The library automatically builds a catalog that includes the media cartridge that you put into the slot.
If you have a StorageTek ACSLS-attached library, you can use the import(1M) command with its -c and -s options to import from a pool of VSNs. This procedure is a faster method of populating a library catalog than the methods described in To Populate an Automated Library With Many Volumes and To Populate an Automated Library With a Small Number of Volumes.
For more information, see the import(1M) man page.
If errors exist in the configuration files for a StorageTek ACSLS-attached automated library, the system generates several error messages. The following examples show common problems and the messages that the system generates.
Example 1. CODE EXAMPLE 3-37 shows the messages generated when there are syntax errors in the StorageTek parameters file. Check your StorageTek parameters file for syntax errors and remember that each line must begin with a keyword or a comment. For more information on the StorageTek parameters file, see the stk(7) man page.
Example 2. Assume that you receive two sets of error messages. CODE EXAMPLE 3-38 shows the first set.
CODE EXAMPLE 3-39 shows the second set.
May 23 09:31:19 baggins stk-50[3854]: main: 2 drive(s) did not initialize. |
CODE EXAMPLE 3-40 shows the samu(1M) utility's :r display.
Drives that are hung in an initializing state or that do not initialize usually indicate a configuration error. Verify that ACSLS is up and running. Verify the host name. Determine whether you can you ping the host name using the ping(1M) command.
Check the portnum specification in the StorageTek parameters file. In ACSLS 5.3, for example, the default port number, 50004, is used for a different application. Try a higher port number, such as 50014.
Example 3. CODE EXAMPLE 3-41 shows messages generated after the import(1M) command was used to import a VSN to the library catalog, but the VSN was not in the StorageTek automated library. The cartridge must be present in the ACSLS-managed automated library before the import(1M) command can be successful.
The sam-stkd daemon uses the ssi.sh script to ensure that a copy of the SSI daemon, ssi_so, is running. If ssi_so exits, the daemon starts another. If your site has its own version of ssi.sh, you should modify it to wait for a SIGTERM signal and then exit. The daemon sends a SIGTERM signal to stop the process. File /opt/SUNWsamfs/examples/ssi.sh contains an example ssi.sh script. The system copies the ssi.sh script to /etc/opt/SUNWsamfs/scripts/ssi.sh during installation if one does not already exist.
The Sun StorEdge SAM-FS 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 within the software manages the exchange of information between network devices such as servers, automated libraries, and drives.
The Sun StorEdge SAM-FS Management Information Base (MIB) defines the types of problems, or events, that the Sun StorEdge SAM-FS software can detect. The software can detect errors in configuration, tapealert(1M) events, and other atypical system activity. For complete information on the MIB, see /opt/SUNWsamfs/mibs/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.
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 StorEdge SAM-FS 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 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. The line is as follows:
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 pkill(1M) command to send a SIGHUP signal to 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 the Sun StorEdge SAM-FS administrator commands. However, during installation you can supply an administrator group name. The pkgadd(1M) process prompts you for this group name during Sun StorEdge SAM-FS installation.
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. This action performs the same function as selecting an administrator group during the package installation. 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 on this command, see the set_admin(1M) man page.
1. Choose a group name, or select a group that already exists within your environment.
2. Use the groupadd(1M) command, or edit the /etc/group file.
The following is an entry from the group file designating an administrator group for the Sun StorEdge SAM-FS software. In this example, the samadm group consists of both the adm and operator users.
|
The Sun StorEdge SAM-FS systems log errors, cautions, warnings, and other messages using the standard Sun Solaris syslog(3) interface. By default, the Sun StorEdge SAM-FS facility is local7.
1. Use vi(1) or another editor to open the /etc/syslog.conf file.
2. From the file /opt/SUNWsamfs/examples/syslog.conf_changes, locate 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 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 StorEdge SAM-FS installation and configuration process is complete. You can configure other Sun StorEdge SAM-FS products at this time. For example, if you want to configure the Sun SAM-Remote software, see the Sun StorEdge SAM-FS Storage and Archive Management Guide.
This section describes the recommended procedures for regularly backing up important data and files in the Sun StorEdge SAM-FS environment.
It is important to use File System Manager or samfsdump(1M) command periodically to create a metadata snapshot file.
When using the samfsdump(1M) command, note the following:
For more information about using the samfsdump(1M) command, see the samfsdump(1M) man page. Also see the information on metadata, disaster preparation, and recovery in the Sun StorEdge SAM-FS Troubleshooting Guide.
This section describes the setup procedures for issuing the samfsdump(1M) command automatically.
Scheduling a metadata snapshot through the File System Manager interface is the equivalent of creating a crontab(1) entry that automates the Sun StorEdge SAM-FS software process.
Follow these steps to schedule a metadata snapshot:
1. From the Servers page, click the server on which the archiving file system that you want to administer is located.
The File Systems Summary page is displayed.
2. Select the radio button next to the archiving file system for which you want to schedule a metadata snapshot.
3. From the Operations menu, choose Schedule Metadata Snapshots.
The Schedule Metadata Snapshots page is displayed.
4. Specify values on the Schedule Metadata Snapshots page.
For instructions on using this page, see the File System Manager online help.
If you have multiple Sun StorEdge SAM-FS file systems, make similar crontab entries for each file system. Save each dump in a separate file.
Make an entry in the root user's crontab file so that the cron daemon runs the samfsdump(1M) command periodically.
CODE EXAMPLE 3-42 shows a cron(1) entry.
This example crontab entry uses a Sun StorEdge SAM-FS file system mounted on /sam. Replace /csd.directory with an existing directory of your choice. This entry causes the commands to execute each day at midnight. First, the old dumps are renamed and a new dump is created in /csd.directory/sam/yymmdd. After that, cron(1M) emails the samfsdump(1M) output to root.
This section describes the setup procedures for issuing the samfsdump(1M) command manually.
You can create a metadata snapshot from the File System Manager interface at any time.
Before starting this procedure, make a note of the path that is specified in the Snapshot File Path field on the Schedule Metadata Snapshot page for this file system. You will need this path during the procedure.
Follow these steps to create a metadata snapshot:
1. From the Servers page, click the server on which the file system that you want to administer is located.
The File Systems Summary page is displayed.
2. Select the radio button next to the file system for which you want to create a metadata snapshot.
3. From the Operations menu, choose Take Metadata Snapshots.
The Take Metadata Snapshot pop-up window is displayed.
4. In the Fully Qualified Snapshot File field, type the path and the name of the snapshot file that you noted from the Schedule Metadata Snapshot page.
|
Note - If you provide a different path, this snapshot file will not be displayed on the Restore File System page when you try to restore files for the file system. |
For more information on creating metadata snapshots, see the File System Manager online help.
1. Use the cd(1) command to go to the directory that contains the mount point for the file system.
2. Use the samfsdump(1M) command to write the output to a file system outside of the one that you are backing up.
The Sun StorEdge SAM-FS software regularly accesses several files that have been created as part of this installation and configuration procedure. 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 on the files that you should protect, see the Sun StorEdge SAM-FS Troubleshooting Guide.
| Sun StorEdge SAM-FS Installation and Upgrade Guide | 819-4330-10 |
|
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Add the Packages
