HP File System Extender (FSE) manual Troubleshooting

Page 70

70 Troubleshooting

Image 70

Contents Part number T3648-96011 First edition October File System Extender Software installation guide for Linux Contents General problems Uninstalling FSE softwareTroubleshooting Upgrading from previous FSE releasesIntegrating existing file systems in the FSE implementation FSE system maintenance releases and hot fixesInstallation problems Integrating existing file systemsPage Intended audience Document conventions and symbolsAbout this guide Related documentationHP web sites Subscription serviceHP technical support Documentation feedbackConsolidated implementation Introduction and preparation basicsFSE implementation options This chapter includes the following topicsDistributed implementation Consolidated FSE implementationMixed implementation Licensing Preparing file systems for FSEOrganizing the file system layout Reasons for organizing file systemsStorage space for FSE debug Estimating the size of file systems Formula for the expected HSM file system size Formula for the expected size of Fast Recovery InformationFormula for the expected File System Catalog size Introduction and preparation basics Space requirements of FSE disk buffer Storage space for FSE debug files Var/log/FSEDEBUG Tmp/FSEDEBUGInstallation overview Installing the FSE Management Console onAction Comments & where to find details Etc/fstabPreparing the operating system Required operating system updatesPreparing the operating system environment Suse Linux Enterprise ServerPackage Package name in the rpm -qa output Rhel Package file name Rhel# rpm --install FirebirdSS-1.0.3.972-0.64IO.i386.rpm Installing Firebird SuperServer on an FSE serverPackage PackageName is not installed Verifying third-party packagesDisabling Acpi with Lilo boot loader Disabling Acpi with Grub boot loaderDisabling Acpi Page Preparing the operating system environment Preparing file systems for FSE Preparing Logical Volume Manager LVM volumesPreparing file systems Create and initialize LVM logical volumes Create and initialize LVM logical volume groups# pvcreate /dev/cciss/c0dp1 # pvcreate /dev/cciss/c0dp2 # lvcreate -L 20G -n fsediskbufNumber vgfse Create LVM logical volumes for HSM file systems# lvcreate -L 400G -n fsefs01 vgfsefs Creating file systems for FSE databases and system files Creating file systems on top of LVM logical volumes# mkfs.ext3 -b 4096 -N 1000000 /dev/vgfsefs/examplefs Mounting file systems for FSE databases and system files Command generates an output similar to the followingCreating HSM file systems Create the four remaining directories Dev/mapper/vgfse-fsevar Var/opt/fse Ext3 defaults# mount /dev/mapper/vgfse-fsevar Dev/mapper/vgfse-fsediskbufNumber\ # mkdir /var/opt/fse/diskbuf/NewFileSystemMountPoint# mount /dev/mapper/vgfse-fsediskbufNumber Creating a symbolic link for debug files directory Installing an FSE release Installing FSE softwareInstallation overview PrerequisitesConsolidated Installation procedureMonitoring the installation PackagesPage Determining the build number Verifying and repairing the installed FSE softwareRepairing the FSE software installation Server = fseserver.company.netModifying the Path environment variable Preparing the FSE backup configuration fileConfiguring the FSE interprocess communication Modifying the Ldlibrarypath environment variableServices.cfg Etc/opt/fse OmniORB.cfg No external FSE clients or ordinary LAN connectionOmniORB.cfg file, configure the parameters in the section Hostname = fseserver.fsenet Server = fseserver.fsenetServer = fse-server1.company.com Configuring communication on external FSE clientsHostname = fseclient.fsenet Server = fseserver.fsenet Starting the FSE implementation # fse --startBottom part of the output should match the following Starting the FSE serverStarting FSE clients Consolidated FSE systemFS Event Manager Mounting Restarting FSE processesRestarting local FSE processes File SystemsExternal FSE client Checking the status of a running FSE implementationChecking Firebird SuperServer If the reported line isChecking FSE Processes Checking the omniNames daemonChecking Firebird SuperServer on Red Hat Enterprise Linux Configuring and starting HSM Health Monitor Configuring and starting Log AnalyzerInstalling the FSE Management Console client Installing the FSE Management ConsoleInstalling the FSE Management Console server Automating the mounting of HSM file systemsAdd the following line to the /etc/fstab file Configuring the post-start and pre-stop helper scriptsPost-start script Dev/mapper/vgfsefs-fsefs01 Fse/fsefs01 Hsmfs noauto 0Pre-stop script ExampleInstalling FSE software Upgrade overview Upgrading from previous FSE releasesShutting down the FSE implementation # /etc/init.d/guisrv stop# fsecheck --fsc-hsmfs PartitionName Var/opt/fse/log/checkhsmfsfscPartitionName.log# cd /var/opt/fse/log # rm -f checkhsmfsfsc # hhm stopCommand displays a report similar to the following Upgrading the operating system on Linux hostsUpgrading the Linux FSE server Installing FSE release 3.4 software on the Linux FSE serverAbove example, the value of DeviceFilePathname is Starting OmniORB Naming Service FSE Service Starting up the FSE serverUpgrading the Windows FSE server For the above example, the command output isUpgrading Linux FSE clients Starting up a Linux FSE client Installing FSE release 3.4 software on a Linux FSE clientUpgrading Windows FSE clients Starting the HSM Health Monitor daemon on Linux systemsUpgrading the FSE Management Console Starting the HSM Health Monitor service on Windows systemsStarting the Log Analyzer service on Windows systems Starting the Log Analyzer daemons on Linux systems# rpm -U fse-gui-client-3.4.0-Build.i386.rpm Verifying availability of the configured FSE partitionsFsepartition --list Uninstalling the FSE Management Console Uninstalling FSE softwareUninstalling FSE software Uninstalling basic FSE software# rpm -e `rpm -qa grep fse- grep -v fse-gui` # omninames --stop Stopping omniORB Naming ServiceResource Manager Stopping Var/opt/fse/rmdbEntity Location directory Location FSE host type Opt/fseUninstalling FSE software Installation problems Troubleshooting General problems General problems, Installation problems,Line helps you determine if the adapter is connected to LAN AdapterSystems, see the latest support matrices Page Troubleshooting # tune2fs -j /dev/fsesda/fs1 Integrating existing file systems in the FSE implementationIntegrating existing file systems HSMFileSystemRoot # find * -type f xargs -n1 head -n0Integrating existing file systems in the FSE implementation FSE releases FSE system maintenance releases and hot fixesFSE system maintenance releases FSE hot fixesDetermining the installed system maintenance release FSE system maintenance releases and FSE hot fixesInstalling a system maintenance release Uninstalling a system maintenance releaseCommand will display an output similar to the following Determining the installed hot fixUninstalling a hot fix # fsesystem --versionFSE system maintenance releases and hot fixes Glossary Media pool FSE media poolExternal client FSE external client FSE configuration file templateConfiguration file File System Catalog FSCDisk buffer Needs cleaning or servicingOwn deletion policy See media duplicationSee recovery FSE recovery, recovery job See recovery FSE recoveryAlso Data Location Catalog DLC and Name Space Catalog NSC Mode LAM Job It, you must use forced initializationFSE job Medium See Medium Auxiliary Memory MAMRetention time Online medium Offline mediumLibrary Set to unusableInstallPath%\var\rmdb directory on Windows platform An FSE users request with the fserecover commandRecovery job Recall, recall jobFSE implementation See media pool FSE media poolSee LTO Ultrium Is set by enabling the drive with the fsedrive commandUltrium Unusable mediumPage Index Ldlibrarypath environment variable Subscribers Choice, HP 8 Suse Linux Enterprise Server Web sites HP HP Subscribers Choice for Business

Related manuals

Manual 99 pages 2.23 Kb

Manual 115 pages 39.56 Kb

Manual 328 pages 27.8 Kb

Manual 26 pages 22.37 Kb