Part number T3648-96011 First edition October
 File System Extender Software installation guide for Linux
 Contents
 Upgrading from previous FSE releases
Uninstalling FSE software
Troubleshooting
General problems
 Integrating existing file systems
FSE system maintenance releases and hot fixes
Installation problems
Integrating existing file systems in the FSE implementation
Page
 Related documentation
Document conventions and symbols
About this guide
Intended audience
 Documentation feedback
Subscription service
HP technical support
HP web sites
 This chapter includes the following topics
Introduction and preparation basics
FSE implementation options
Consolidated implementation
 Consolidated FSE implementation
Distributed implementation
 Mixed implementation
 Preparing file systems for FSE
Licensing
 Reasons for organizing file systems
Organizing the file system layout
Storage space for FSE debug
 Estimating the size of file systems
 Formula for the expected size of Fast Recovery Information
Formula for the expected HSM file system size
Formula for the expected File System Catalog size
 Introduction and preparation basics
 Space requirements of FSE disk buffer
 Var/log/FSEDEBUG Tmp/FSEDEBUG
Storage space for FSE debug files
 Installing the FSE Management Console on
Installation overview
 Etc/fstab
Action Comments & where to find details
 Suse Linux Enterprise Server
Required operating system updates
Preparing the operating system environment
Preparing the operating system
 Package file name Rhel
Package Package name in the rpm -qa output Rhel
 Verifying third-party packages
Installing Firebird SuperServer on an FSE server
Package PackageName is not installed
# rpm --install FirebirdSS-1.0.3.972-0.64IO.i386.rpm
 Disabling Acpi with Grub boot loader
Disabling Acpi with Lilo boot loader
Disabling Acpi
Page
 Preparing the operating system environment
 Preparing Logical Volume Manager LVM volumes
Preparing file systems for FSE
Preparing file systems
 Create and initialize LVM logical volume groups
Create and initialize LVM logical volumes
# pvcreate /dev/cciss/c0dp1 # pvcreate /dev/cciss/c0dp2
 Create LVM logical volumes for HSM file systems
# lvcreate -L 20G -n fsediskbufNumber vgfse
# lvcreate -L 400G -n fsefs01 vgfsefs
 Creating file systems on top of LVM logical volumes
Creating file systems for FSE databases and system files
# mkfs.ext3 -b 4096 -N 1000000 /dev/vgfsefs/examplefs
 Command generates an output similar to the following
Mounting file systems for FSE databases and system files
Creating HSM file systems
 Dev/mapper/vgfse-fsevar Var/opt/fse Ext3 defaults
Create the four remaining directories
# mount /dev/mapper/vgfse-fsevar
 # mkdir /var/opt/fse/diskbuf/NewFileSystemMountPoint
Dev/mapper/vgfse-fsediskbufNumber\
# mount /dev/mapper/vgfse-fsediskbufNumber
 Creating a symbolic link for debug files directory
 Prerequisites
Installing FSE software
Installation overview
Installing an FSE release
 Packages
Installation procedure
Monitoring the installation
Consolidated
Page
 Server = fseserver.company.net
Verifying and repairing the installed FSE software
Repairing the FSE software installation
Determining the build number
 Modifying the Ldlibrarypath environment variable
Preparing the FSE backup configuration file
Configuring the FSE interprocess communication
Modifying the Path environment variable
 No external FSE clients or ordinary LAN connection
Services.cfg Etc/opt/fse OmniORB.cfg
 Hostname = fseserver.fsenet Server = fseserver.fsenet
OmniORB.cfg file, configure the parameters in the section
 Configuring communication on external FSE clients
Server = fse-server1.company.com
Hostname = fseclient.fsenet Server = fseserver.fsenet
 # fse --start
Starting the FSE implementation
 Consolidated FSE system
Starting the FSE server
Starting FSE clients
Bottom part of the output should match the following
 File Systems
Restarting FSE processes
Restarting local FSE processes
FS Event Manager Mounting
 If the reported line is
Checking the status of a running FSE implementation
Checking Firebird SuperServer
External FSE client
 Checking the omniNames daemon
Checking FSE Processes
Checking Firebird SuperServer on Red Hat Enterprise Linux
 Configuring and starting Log Analyzer
Configuring and starting HSM Health Monitor
 Automating the mounting of HSM file systems
Installing the FSE Management Console
Installing the FSE Management Console server
Installing the FSE Management Console client
 Dev/mapper/vgfsefs-fsefs01 Fse/fsefs01 Hsmfs noauto 0
Configuring the post-start and pre-stop helper scripts
Post-start script
Add the following line to the /etc/fstab file
 Example
Pre-stop script
 Installing FSE software
 Upgrading from previous FSE releases
Upgrade overview
 # /etc/init.d/guisrv stop
Shutting down the FSE implementation
 # hhm stop
Var/opt/fse/log/checkhsmfsfscPartitionName.log
# cd /var/opt/fse/log # rm -f checkhsmfsfsc
# fsecheck --fsc-hsmfs PartitionName
 Upgrading the operating system on Linux hosts
Command displays a report similar to the following
 Installing FSE release 3.4 software on the Linux FSE server
Upgrading the Linux FSE server
Above example, the value of DeviceFilePathname is
 Starting up the FSE server
Starting OmniORB Naming Service FSE Service
 For the above example, the command output is
Upgrading the Windows FSE server
Upgrading Linux FSE clients
 Starting the HSM Health Monitor daemon on Linux systems
Installing FSE release 3.4 software on a Linux FSE client
Upgrading Windows FSE clients
Starting up a Linux FSE client
 Starting the Log Analyzer daemons on Linux systems
Starting the HSM Health Monitor service on Windows systems
Starting the Log Analyzer service on Windows systems
Upgrading the FSE Management Console
 Verifying availability of the configured FSE partitions
# rpm -U fse-gui-client-3.4.0-Build.i386.rpm
Fsepartition --list
 Uninstalling basic FSE software
Uninstalling FSE software
Uninstalling FSE software
Uninstalling the FSE Management Console
 Var/opt/fse/rmdb
# omninames --stop Stopping omniORB Naming Service
Resource Manager Stopping
# rpm -e `rpm -qa grep fse- grep -v fse-gui`
 Opt/fse
Entity Location directory Location FSE host type
 Uninstalling FSE software
 General problems, Installation problems,
Troubleshooting
General problems
Installation problems
 Adapter
Line helps you determine if the adapter is connected to LAN
Systems, see the latest support matrices
Page
 Troubleshooting
 HSMFileSystemRoot # find * -type f xargs -n1 head -n0
Integrating existing file systems in the FSE implementation
Integrating existing file systems
# tune2fs -j /dev/fsesda/fs1
 Integrating existing file systems in the FSE implementation
 FSE hot fixes
FSE system maintenance releases and hot fixes
FSE system maintenance releases
FSE releases
 Uninstalling a system maintenance release
FSE system maintenance releases and FSE hot fixes
Installing a system maintenance release
Determining the installed system maintenance release
 # fsesystem --version
Determining the installed hot fix
Uninstalling a hot fix
Command will display an output similar to the following
 FSE system maintenance releases and hot fixes
 Media pool FSE media pool
Glossary
 File System Catalog FSC
FSE configuration file template
Configuration file
External client FSE external client
 See media duplication
Needs cleaning or servicing
Own deletion policy
Disk buffer
 See recovery FSE recovery
See recovery FSE recovery, recovery job
Also Data Location Catalog DLC and Name Space Catalog NSC
 Mode LAM
 It, you must use forced initialization
Job
FSE job
 See Medium Auxiliary Memory MAM
Medium
Retention time
 Set to unusable
Offline medium
Library
Online medium
 Recall, recall job
An FSE users request with the fserecover command
Recovery job
InstallPath%\var\rmdb directory on Windows platform
 See media pool FSE media pool
FSE implementation
 Unusable medium
Is set by enabling the drive with the fsedrive command
Ultrium
See LTO Ultrium
Page
 Index
 Ldlibrarypath environment variable
 Subscribers Choice, HP 8 Suse Linux Enterprise Server
 Web sites HP HP Subscribers Choice for Business