HP StorageWorks File System Extender Software installation guide for Linux Part number: T3648-96011 First edition: October 2006
Legal and notice information © Copyright 2005, 2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Intended audience . . . . . . . . . . . . Related documentation . . . . . . . . . Document conventions and symbols HP technical support . . . . . . . . . . . Subscription service . . . . . . . . . . . HP web sites . . . . . . . . . . . . . . . . Documentation feedback . . . . . . . . ......................... . . . . . . . . .. .. .. .. .. .. .. .. . . . . . . . . .. .. .. .. .. .. .. .. . . . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . . . . . . . .. .. .. .. .. .. .. ..
Preparing the environment for the first startup of the FSE implementation . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the PATH environment variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the LD_LIBRARY_PATH environment variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the MANPATH environment variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 A Integrating existing file systems in the FSE implementation . . . . . . . . . . . . . . . . . . . . . . . 71 Integrating existing file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 B FSE system maintenance releases and hot fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this guide This guide provides information about: • Checking detailed software requirements • Preparing your environment prior to installing the FSE software • Installing, upgrading, and uninstalling the FSE software on the Linux platform • Performing mandatory and optional post-installation steps • Troubleshooting installation, upgrade, and uninstallation problems Intended audience This guide is intended for system administrators with knowledge of: • Linux platform Related documentation The followi
CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: NOTE: TIP: Provides clarifying information or specific instructions. Provides additional information. Provides helpful hints and shortcuts. HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/.
1 Introduction and preparation basics HP StorageWorks File System Extender (FSE) is a mass storage oriented software product, based on client-server technology. It provides large storage space by combining disk storage and a tape library with high-capacity tape media and implementing Hierarchical Storage Management (HSM). Refer to the FSE user guide for a detailed product description. This Installation Guide tells you how to prepare the environment and install the FSE software.
working FSE environment. User data from local HSM file systems is recorded on disk media or tape media in the attached tape library. Figure 1 Consolidated FSE implementation Distributed implementation A distributed implementation consists of a central FSE server with disk media and/or SCSI tape library attached and one or more external FSE clients that are connected to the server. External FSE clients can run on different operating systems.
services on the FSE server. User data from these remote file systems is transferred to the FSE server and recorded on the corresponding disk media or tape media in the attached tape library. Figure 2 Distributed FSE implementation NOTE: Communication between the components of a distributed FSE implementation is based on the CORBA technology (omniORB).
IMPORTANT: In a mixed FSE implementation, if the FSE processes on the consolidated FSE system are restarted, you must restart the FSE processes on all external FSE clients to resume the normal FSE operation. Licensing There are both per machine and capacity-based licenses for HP File System Extender. • For every machine that runs an FSE client, you need an FSE client license appropriate to the operating system.
Table 2 Pre-installation size considerations Parameter Description Reference Temporary files in FSE disk buffer Total storage space on file systems or volumes that are assigned to the FSE disk buffer should be at least 10% of total storage space on all HSM file systems in the FSE implementation. ”Space requirements of FSE disk buffer” on page 17 Debug files Debug files are optional but may grow and fill up the file system.
Table 3 FSE server directory layout Directory Contents File system type LVM volume /var/opt/fse/ Configuration Database, Resource Management Database, other FSE system files Ext3 required for the FSE backup /var/opt/fse/part/ File System Catalogs Ext3 required for the FSE backup /var/opt/fse/fri/ Fast Recovery Information (FRI) Ext3 required for the FSE backup /var/opt/fse/diskbuf/FS11 /var/opt/fse/diskbuf/FS2 ...
IMPORTANT: FSE includes the utility HSM Health Monitor, which helps preventing file systems for FSE databases and system files and HSM file systems from running out of free space. For details, see the FSE user guide, chapter ”Monitoring and maintaining FSE”, section ”Low storage space detection”.
NOTE: HP recommends that you add another 50% as a reserve when calculating the maximum FSC size. The following examples present space usage for typical configurations. Example 1: three copies, one generation: First generation takes (189 for FSC) + (36 x 3 for volume index) = 297 bytes Each additional generation takes 47 + (36 x 3) = 155 bytes Total size = ((297 + add. attr. size) x max. number of files) + (155 x number of add.
Sample calculation for the expected sizes of HSM file system, FSC and HSMDB The following is an example of a calculation of space required on an HSM file system and on the file systems holding File System Catalog (FSC), and HSM Database (HSMDB), and Fast Recovery Information (FRI) files.
• Total storage space on file systems or volumes that are assigned to FSE disk buffer should be at least 10% of total storage space on all HSM files systems in the FSE implementation. • Each file system or volume assigned to FSE disk buffer should be at least twice as large as the largest file that will be put under FSE control.
2 Installation overview This chapter provides an installation overview, which summarizes the steps necessary to prepare the system and to install the FSE software. Where appropriate, you are pointed to more detailed steps within this document. Action Comments & where to find details 1. Install the required operating system update. ” Required operating system updates” on page 21. 2. Install all necessary third-party packages.
Action Comments & where to find details 11. Mount HSM file systems: a. Create directories. b. Update the /etc/fstab file with required information. ”Automating the mounting of HSM file systems” on page 49. To mount HSM file systems, add entries for these file systems to the local file system table in the file /etc/fstab. NOTE: This step is similar to steps 3e and 3f where you mounted the FSE databases and system files. In this step, you are mounting HSM file systems.
3 Preparing the operating system environment This chapter describes the necessary changes that need to be made to the operating system environment on the computer that will host a consolidated FSE system (integrated server and client) or part of a distributed FSE implementation (separate server and separate client). It also lists the required third-party packages that must be installed prior to installing the FSE software.
Table 5 Packages and their relation to FSE components on SUSE Linux Enterprise server Package Package name in the rpm -qa output (SLES) FSE client FSE server Consolidated FSE system glibc C library glibc-2.3.3-98.61 glibc-2.3.3-98.61.i586.rpm glibc locale C library glibc-locale-2.3.3-98.61 glibc-locale-2.3.3-98.61.i586.rpm Package file name (SLES) Firebird SuperServer FirebirdSS-1.0.3.972-0.64IO FirebirdSS-1.0.3.972-0.64IO.i386.rpm sourceforge.
Table 6 Packages and their relation to FSE components on Red Hat Enterprise Linux Package Package name in the rpm -qa output (RHEL) FSE client FSE server Consolidated FSE system libstdc++ C++ library libstdc++-3.4.5-2 libstdc++-3.4.5-2.i386.rpm glibc C library glibc-2.3.4-2.19 glibc-2.3.4-2.19.i386.rpm Package file name (RHEL) Firebird SuperServer FirebirdSS-1.0.3.972-0.64IO FirebirdSS-1.0.3.972-0.64IO.i386.rpm sourceforge.
2. In the /etc directory, create a plain text file gds_hosts.equiv containing the following two lines: + +localhost 3. If you are installing FirebirdSS to a SUSE Linux Enterprise Server system, once the Firebird SuperServer is installed, open the file /etc/sysconfig/firebird with a text editor, search for the START_FIREBIRD variable, and set its value to "yes".
After you add this option to the LILO configuration file, run lilo to ensure that at the next boot, ACPI will be disabled.
Preparing the operating system environment
4 Preparing file systems for FSE In order to optimize the FSE implementation and increase its reliability, it may be necessary to re-organize the file systems on the host that will be dedicated to the FSE server as well as on the FSE client. When using disk media, you need to prepare file systems to hold disk media files.
NOTE: Commands for managing LVM physical volumes begin with the letters pv (physical volume) and are located in the /sbin directory. In the example below, the first partition of the first SCSI disk and the first partition on the second SCSI disk are initialized as LVM physical volumes and are dedicated to the LVM volumes.
NOTE: Commands for managing LVM logical volumes begin with the letters lv (logical volume) and are located in the /sbin directory.
Creating file systems on top of LVM logical volumes After the LVM logical volumes have been successfully initialized, you need to create file systems on top of them using the command mkfs.ext3. HP recommends that you use the mkfs.ext3 option -b 4096 for specifying a block size of 4096 bytes. TIP: If you want to check the properties your file system will have without actually creating it, you can run the command mkfs.ext3 with the switch -n.
# mkfs.ext3 -b 4096 /dev/vg_fse/fsefri # mkfs.ext3 -b 4096 /dev/vg_fse/fselog # mkfs.ext3 -b 4096 /dev/vg_fse/fsediskbuf If you will assign additional file systems to the FSE disk buffer, run the following command for each of them: # mkfs.ext3 -b 4096 /dev/vg_fse/fsediskbufNumber Each command reports the properties of the newly created file system. NOTE: To improve the performance of the FSE disk buffer, you can use Ext2 file systems for its storage space.
3. To ensure that the file system is automatically mounted at system startup, add the appropriate entry to the file system table in the file /etc/fstab. When adding the entry, note that the device name in the first column corresponds to the device file that you retrieved in the previous step: /dev/mapper/vg_fse-fsevar /var/opt/fse ext3 defaults 1 2 4. Manually mount the corresponding file system for the directory /var/opt/fse.
8. Manually mount the corresponding file systems for these four directories. You must use the device (logical volume) names from your actual LVM configuration: # mount /dev/mapper/vg_fse-fsepart # mount /dev/mapper/vg_fse-fsefri # mount /dev/mapper/vg_fse-fselog # mount /dev/mapper/vg_fse-fsediskbuf 9. In case of FSE disk buffer configuration with additional assigned file systems, follow the substeps for each additional file system: a.
Creating a symbolic link for debug files directory There are several possibilities where you may store the FSE debug files, as listed in ”Storage space for FSE debug files” on page 18. NOTE: When you make the decision about the placement of the FSE debug files, you need to make sure that the disk partition holding the target directory with the debug files has enough free space for eventually a large amount of the debugging data.
5 Installing FSE software This chapter describes steps you must follow to install FSE software. The installation procedure depends on the type of the FSE implementation component you want to install: a consolidated FSE system, an FSE server or external FSE client. NOTE: With mixed or distributed FSE system implementations you need to install external FSE clients after you have installed the consolidated FSE system or the FSE server, respectively.
The following table lists the three types of FSE implementation and the FSE packages required for each component, as well as the dependencies between the packages. The dependencies define the correct order in which the packages must be installed. Table 7 Installation packages FSE installation package Depends on package(s) FSE client FSE server Consolidated FSE system 1. fse-common-Version.Distr.Plat.rpm1 2. fse-server-Version.Distr.Plat.rpm common 3. fse-agent-Version.Distr.Plat.
system into the file /etc/opt/fse/services.cfg and start FSE services with command 'fse start' 2:fse-client ########################################### [29%] Setting FSE File System Filter module: [ OK ] NOTE: after successful installation write the correct name of FSE Server system into the file /etc/opt/fse/services.
chkconfig loganalyzer_messages on and start the services with commands hhm start loganalyzer start loganalyzer_messages start The initial content of the file /etc/opt/fse/services.cfg that you need to modify according to the actual host name is the following: server = fseserver.company.net Verifying and repairing the installed FSE software Once the FSE release software has been correctly installed, you can use the following procedure to identify the build number.
Use the rpm -V command to check whether the software installation is corrupt. Note that applied FSE hot fixes change individual binaries and other files making it difficult to determine whether or not the installation is corrupt. Proceed as follows: 1. Change the current directory to one with the FSE installation packages and reinstall the packages: # cd PathToFSEPackageDirectory # rpm -F --force fse*.rpm 2.
The initial configuration must be performed after the FSE software package installation, before the FSE implementation is put into operation for the first time. Afterwards, if the implementation or the network type is changed, the communication settings must be reconfigured. CAUTION: An appropriate configuration of the FSE interprocess communication is of crucial importance for normal FSE operation. Incorrectly configured interprocess communication may lead to a non-operating FSE implementation.
The following is an example of a correctly configured services.cfg file in an FSE implementation using a private network. The server variable is redundant in such FSE implementation: hostname = fseserver.fsenet server = fseserver.fsenet 2. In the omniORB.
NOTE: SUSE Linux Enterprise Server 9 (SLES 9) systems only: Do not run YaST2 after you have configured this FSE host to use a private network for the FSE interprocess communication. Running YaST2 modifies /etc/hosts in such a way that subsequent FSE system startups will fail. Alternatively, you can modify /etc/sysconfig/suseconfig by changing the line CHECK_ETC_HOSTS="yes" to CHECK_ETC_HOSTS="no". You can then run YaST2 without affecting the FSE system operation, but you cannot modify host names with it.
endPoint = giop:tcp:fseclient.fsenet: # The order of network interfaces to use for accepting connections: # Only localhost and private network. Others are denied. clientTransportRule = localhost tcp clientTransportRule = 192.168.240.0/255.255.255.0 tcp clientTransportRule = * none # The order of network interfaces to use for opening new server connections: # Only localhost and private network. Others are denied. serverTransportRule = localhost tcp serverTransportRule = 192.168.240.0/255.255.255.
The bottom part of the output should match the following: Starting omniORB Naming Service: [ OK ] Starting FSE Service: [ OK ] Starting FSE Resource Manager: [ OK ] Starting FSE Management Interface: [ OK ] Installing HSMFS Filter module: [ OK ] Loading HSMFS Filter module: [ OK ] Starting HSM FS Event Manager: [ OK ] Mounting HSM File Systems: [ OK ] Starting FSE processes in a distributed or mixed FSE implementation The general rule for starting the FSE system in a distribu
Starting HSM FS Event Manager: [ OK ] Mounting HSM File Systems: [ OK ] Restarting FSE processes Restart sequence in a distributed or mixed FSE implementation In a distributed or mixed FSE implementation, restart the FSE server or consolidated FSE system first. The FSE daemons (services) on each connected FSE client need to be restarted as soon as the FSE daemons (services) on the server or consolidated system are running again.
FSE server # fse --restart Stopping FSE Management Interface: [ OK ] Stopping FSE Resource Manager: [ OK ] Stopping FSE Service: [ OK ] Starting FSE Service: [ OK ] Starting FSE Resource Manager: [ OK ] Starting FSE Management Interface: [ OK ] Unmounting HSM File Systems: [ OK ] Stopping HSM FS Event Manager: [ OK ] Unloading HSMFS Filter module: [ OK ] Stopping FSE Service: [ OK ] Starting FSE Service: [ OK ] Loading HSMFS Filter module: [ OK ] Starting HSM
Checking Firebird SuperServer on Red Hat Enterprise Linux You can check if the FirebirdSS process is running with the command below. This example also displays its output with FirebirdSS running. # /etc/init.d/firebird status ibserver (pid 2260) is running... If the reported line is: ibserver is stopped you need to start Firebird manually using the following command. This command also displays its output when FirebirdSS is successfully started: # /etc/init.
Example outputs of the fse --status command If software installation was successful, you should get the following (typical) outputs with the fse --status command: Consolidated FSE system - FSE daemons running fse-svc ( pid 17399 ) is running... fse-rm ( pid 17411 ) is running... fse-mif ( pid 17427 ) is running... fse-fsevtmgr ( pid 17707 ) is running... FSE server - FSE daemons running fse-svc ( pid 17399 ) is running... fse-rm ( pid 17411 ) is running... fse-mif ( pid 17427 ) is running...
Installing the FSE Management Console This section describes how to install the FSE Management Console server and client components. To use the FSE graphical user interface, you need to install the Management Console server as well as the Management Console client. NOTE: You must install the FSE Management Console server on the system that hosts the FSE server.
2. Add the following line to the /etc/fstab file: /dev/mapper/vg_fsefs-fsefs_01 /fse/fsefs_01 hsmfs noauto 0 2 CAUTION: You must use the values in the third1, fourth2, fifth, and sixth column as specified above. You may use different values in the first and second column according to your actual LVM volume configuration. 3. If necessary, repeat the steps 1 and 2 for all other local HSM file systems that you plan to use. 4. Comment out each line that you added in step 2.
Example 1 /etc/init.d/nfsserver start Example 2 rcsmb start /usr/sbin/exportfs -a The pre-stop script The pre-stop script is executed by the fse --stop command before all locally mounted HSM file systems are unmounted and before all FSE processes that are running locally are shut down. The script runs the specified commands directly before this particular component of the FSE implementation is pulled out of its fully operational state. The pre-stop script must be named pre_stop.sh.
Installing FSE software
6 Upgrading from previous FSE releases In this chapter, you will be instructed how to upgrade an FSE implementation that currently uses a previous FSE product version to release version 3.4. Upgrading will add the new functionality that has been implemented in the new FSE release, and install the FSE utilities: HSM Health Monitor and Log Analyzer.
To stop FSE Management Console client process, you need to close its GUI window. To stop the FSE Management Console server process, invoke the following command on the consolidated FSE system or FSE server: # /etc/init.d/guisrv stop To stop the FSE Management Console server process, run the Services administrative tool, locate and right-click the entry File System Extender GUI Server, and click Stop.
1. On all systems that host either an internal (part of the consolidated FSE system) or an external FSE client, close all applications that access files or directories on HSM file systems and make sure that all non-FSE processes which have had locks to objects on these file systems are terminated. You can use the fuser or lsof command to find out which files are being accessed on the HSM file system. For details, refer to the fuser and lsof man pages. 2.
a. To stop the HSM Health Monitor daemon on the local system, run the following command: # hhm stop b. To stop the Log Analyzer daemons on the local system, run the following commands: # /etc/init.d/loganalyzer stop # /etc/init.d/loganalyzer_messages stop 7. On the consolidated FSE system or FSE server, shut down the currently running FSE processes using the fse --stop command.
lvscan -- 4 logical volumes with 25.80 GB total in 2 volume groups lvscan -- 4 active logical volumes 2. On the local system, upgrade the operating system. For a list of supported operating system versions, see the latest support matrices. CAUTION: Ensure that during or after the operating system upgrade, all LVM volumes on the local system are converted to LVM2 volumes. Failing to convert the LVM volumes to LVM2 volumes may result in loss of the data stored on these volumes.
If you are upgrading an FSE server, invoke the following commands: # rpm -Fvh fse-common-3.4.0* fse-server-3.4.0* fse-agent-3.4.0* \ fse-cli-admin-3.4.0* # rpm -ivh fse-util-3.4.0* In both cases, the second rpm command installs the FSE utilities: HSM Health Monitor and Log Analyzer. If you are upgrading the FSE release 3.
Starting FSE Resource Manager: [ OK ] Starting FSE Management Interface: [ OK ] 2. Update the FileSystemID parameter in each FSE partition configuration file as follows: a. Invoke the following command: # fsepartition --show PartitionName >ConfigurationFile a. In the file ConfigurationFile, locate the parameters Client and FileSystemID. The following is an example excerpt from an FSE partition configuration file: Client "FSE_client_01" { FileSystemID = 58:5 # e.g. 58:1, Linux or HP-UX client b.
Installing FSE release 3.4 software on a Linux FSE client To install FSE release 3.4 software over the installed previous FSE product appropriately, change the current directory to the one with the installation packages. Install all required FSE 3.4 RPM packages using two invocations of the rpm command. You need to pay regard to the proposed order of precedence: # rpm -Fvh fse-common-3.4.0* fse-client-3.4.0* fse-cli-user-3.4.0* # rpm -ivh fse-util-3.4.
Starting the HSM Health Monitor service on Windows systems For information on how to start HSM Health Monitor, see the FSE installation guide for Windows, chapter ”Upgrading from previous FSE releases”. Configuring and starting Log Analyzer If you decide to use Log Analyzer for monitoring the log files, you need to configure it and start its daemons on the hosts on which you want to monitor the log files.
1. Change the current directory to the one with the new FSE Management Console client package and run the command: # rpm -U fse-gui-client-3.4.0-Build.i386.rpm For information on how to upgrade the Management Console on Windows systems, see the FSE installation guide for Windows, chapter ”Upgrading from previous FSE releases”.
7 Uninstalling FSE software If you want to remove the FSE software from a system that is part of your FSE implementation, you need to uninstall all FSE components. NOTE: In a distributed FSE system the sequence of uninstalling from different hosts that are part of the FSE system matters. If external FSE clients are part of your FSE system, you need to uninstall the FSE software from the external clients before uninstalling the consolidated FSE system or FSE server.
Unloading HSMFS Filter module: [ OK ] Stopping FSE Management Interface: [ OK ] Stopping FSE Resource Manager: [ OK ] Stopping FSE Service: [ OK ] The fse --stop command executes the pre_stop script, if it exists. It also performs the following, depending on where it is run: • When used on a consolidated system or an external FSE client, the command unmounts all local mounted HSM file systems.
Entity Location (directory) Location (FSE host type) Fast Recovery Information (FRI) files /var/opt/fse/fri consolidated FSE system, FSE server Log and debug files /var/opt/fse/log consolidated FSE system, FSE server, FSE client Backup, trace and CORBA/omniORB configuration files /etc/opt/fse consolidated FSE system, FSE server Other files /opt/fse consolidated FSE system, FSE server, FSE client 9.
Uninstalling FSE software
8 Troubleshooting You may encounter problems during the FSE installation, upgrade, and uninstallation process. Before you contact HP technical support, you should verify that all the prerequisites are met and that you have followed the corresponding procedures as described in this guide, including, for example, the operating system preparation phase. See also the FSE release notes for additional problems related to installation, upgrade, and uninstallation.
Description After installation of SUSE Linux Enterprise Server 9 on a system with network adapters using both copper and fibre cabling and the same driver, the network is not accessible. (SUSE Linux Enterprise Server system specific) Explanation Even though the configuration of network adapters in YaST2 seemed to be successful, the network adapters are misconfigured. YaST2 apparently assigned a wrong ethX device to each adapter. Workaround 1.
HP StorageWorks File System Extender Software installation guide for Linux 69
Troubleshooting
A Integrating existing file systems in the FSE implementation When the FSE is installed on a system where user files are located on already existing file systems, you may want to bring these files under FSE control. This is to make FSE aware of the already-existing files and include them in standard operations such as migration and recall. The following procedure is for guidance only. Some of the steps are documented in the FSE user guide, chapter ”Configuring FSE”.
Integrating existing file systems in the FSE implementation
B FSE system maintenance releases and hot fixes This appendix contains the following topics: • FSE software: releases, hot fixes, and system maintenance releases, page 73 • FSE system maintenance releases and FSE hot fixes, page 74 IMPORTANT: In this appendix, the presented Major, Minor, SMRNumber, and Build numbers that form version strings may be fictitious and may not necessarily represent actual software versions.
NOTE: FSE hot fixes are designed to solve the problems that emerge between release dates of FSE releases and/or FSE system maintenance releases. If an FSE hot fix and a particular SMR containing this hot fix are available, you are recommended to use the SMR rather than the hot fix. FSE system maintenance releases and FSE hot fixes This section instructs you how to install, determine, and uninstall FSE system maintenance releases and FSE hot fixes.
Determining the installed hot fix To determine which FSE hot fix is installed on the system, proceed as follows: 1. At the command prompt, invoke the following command: # fsesystem --version The command will display an output similar to the following: File System Extender Copyright (C) 2002-2006 GRAU Data Storage Copyright (C) 2004-2006 Hewlett-Packard fsesystem 3.3.0.142 "Release Hotfix_02" libhsmui 3.3.0.142 "Release Hotfix_02" libhsmparser 3.3.0.142 "Release Hotfix_02" libhsmipc 3.3.0.
FSE system maintenance releases and hot fixes
Glossary This glossary defines terms used in this guide or related to this product and is not a comprehensive glossary of computer terms. administrative job (admin job) A process, executed by the Management Interface, which performs formatting and initialization of the FSE media. administrator (FSE administrator) A system administrator who installs, configures, monitors, and maintains an FSE implementation.
client (FSE client) A set of FSE daemons (services) responsible for managing the HSM file systems on the FSE partitions. These daemons (services) are: File System Event Manager, Hierarchical Storage Manager, and Service, with additional FSE Windows Service on Windows systems. See also ”external client (FSE external client)”. command (FSE command) An FSE command-line interface command that communicates with FSE system components through the Management Interface.
debug file (FSE debug file) A log file of a single FSE process, which records the execution trace of operations inside the process. FSE debug files are created only if tracing in FSE is enabled (typically on request of technical support personnel of FSE). FSE debug files are located in the directory /var/opt/fse/log/debug (on Linux platform) or in the directory %InstallPath%\var\log\debug (on Windows platform).
event log (FSE event log) A file that records relevant information on events happening in the FSE processes during the operation of the FSE implementation. FSE event log, named fse.log, is located in the directory /var/opt/fse/log (on Linux platform) or in the directory %InstallPath%\var\log (on Windows platform). explicit release Unconditional release, started for a file or set of files on the release candidate list, specified by an FSE user.
File System Event Manager A daemon (service) on the FSE client which receives notification about mount events for the HSM file system and triggers the startup of the appropriate Hierarchical Storage Manager. The File System Event Manager process name is fse-fsevtmgr. forced release Release of all files on an HSM file system, which are on the release candidate list, regardless of their retention time and file size.
HSM file system (HSM FS) A file system, controlled by the FSE software. It is used to store file metadata (name, attributes, permissions) and online files of an FSE partition. HSM file systems represent the primary storage space of an FSE implementation. On the Linux platform, HSM file systems are based on the Linux native Ext3 file system and FSE specific attributes are stored as Ext3 extended attributes. On the Windows platform, HSM file systems are based on the Windows native NTFS file system.
MAM See ”Medium Auxiliary Memory (MAM)”. Management Console (MC) An add-on to the basic FSE product that provides graphical user interface for most of the configuration, operation, monitoring, and management tasks in the FSE implementation. Management Console consists of two separate modules: Management Console server and Management Console client.
Network File System The file-sharing protocol used in UNIX networks. This is one of the protocols that can be used (NFS) for accessing files on an HSM file system from a remote machine, particularly a Linux client. offline file A file whose contents were migrated to one or more FSE media (according to the number of copies defined), and then removed from the HSM file system. The header and extended attributes of an offline file are left intact and remain on the HSM file system.
recall, recall job A process, executed by the Partition Manager, that copies the file contents from the FSE media to the HSM file system. Once the process is completed, the offline file becomes online again. Its file entry is then added to the release candidate list. recovery (FSE recovery) A process, executed by the Partition Manager, that recovers the HSM file system or the File System Catalog (FSC) without requiring FSE backup copies.
restore (FSE restore) A process that recreates complete and consistent state of the FSE server at a particular point in time, using data from the backup image. Restore is required after disaster causes data on the FSE server to be damaged or lost. restore log (FSE restore log) A file that stores information about activity of the FSE restore process. FSE restore log is named restore.
tool (FSE tool) A command that communicates directly with FSE daemons (services) and agents besides Management Interface, designed for low-level modifications and more extensive monitoring and troubleshooting tasks. FSE tools are only intended for use by experienced FSE users (typically on request of technical support personnel of FSE). Note that incorrect use of FSE tools can cause data corruption.
Index disk partitions available on the system 27 distributed FSE implementation starting FSE processes 44 distributed implementation 10 distributed system with separate server and external clients see distributed implementation 11 document conventions 7 related documentation 7 documentation providing feedback 8 A audience 7 available disk partitions 27 B benefits organizing file systems 13 build number installation 38 C capacity-based licensing 12 checking Firebird SuperServer status 46 FSE implementatio
FSE interprocess communication configuring 39 FSE Management Console uninstalling 63 FSE Management Console client installing 49 FSE Management Console clients upgrading 61 FSE Management Console server installing 49 upgrading 61 FSE partitions verifying 62 FSE processes status check 47 FSE related documentation 7 FSE releases 73 FSE server configuring communication 40 starting 44, 58 upgrading 57 FSE software hot fixes 73 releases 73 system maintenance releases 73 uninstalling 63 fse --status command examp
O S omniNames daemon status check 47 operating system upgrading 56 operating system updates Red Hat Enterprise Linux 21 SUSE Linux Enterprise Server 21 operating system upgrade 56 optimizing FSE implementation 12 organizing file systems benefits 13 overview upgrading 53 shutting down FSE implementation 54 standalone implementation see consolidated implementation 10 standalone implementation with external clients see mixed implementation 11 starting FSE clients 44, 60 FSE server 44, 58 starting FSE implem
W web sites HP 8 HP Subscriber's Choice for Business 8 92
