HP File System Extender (FSE) manual See LTO Ultrium, Unusable medium, Worm file system

Page 87

tool

A command that communicates directly with FSE daemons (services) and agents besides

(FSE tool)

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. FSE tools are located in the directory /opt/fse/sbin/tools (on

 

Linux platform) or in the directory %InstallPath%\bin (on Windows platform).

Ultrium

See ”LTO Ultrium”.

unreliable medium

An FSE medium to which further writing is disabled, but from which FSE is still able to read

 

data. As soon as the first write error is detected while the Back End Agent is writing data to the

 

medium, the medium is automatically marked as unreliable in the Resource Management

 

Database. Such errors usually occur because of an excessive use of the medium.

unusable medium

An FSE medium which has been disabled for both writing to and reading from. As soon as the

 

first read error is detected while the Back End Agent is reading data from the medium, the

 

medium is automatically marked as unusable in the Resource Management Database. Such

 

errors usually occur because of an extremely excessive use of the medium.

user

A computer system user who uses one or more HSM file systems for managing data.

(FSE user)

 

utility

An add-on FSE component that provides additional functionality and complements basic FSE

(FSE utility)

components. In current FSE release, two FSE utilities are part of the FSE software: HSM Health

 

Monitor and Log Analyzer. See also ”HSM Health Monitor (HHM)”, ”Log Analyzer (LA)”.

verified drive

An FSE drive that is put back in operation after its problems have been resolved. This is done

 

by changing its status in the Resource Management Database to online. The online status

 

is set by enabling the drive with the fsedrive command.

WORM file system

A file system on which a file can be written only once, but can be read many times. A WORM

 

(Write Once Read Many) file system prevents both files and their metadata from being

 

modified, regardless of their access permissions. Consequently, it is not possible to remove files

 

from directories or rename them; it is only possible to add new files (as on a regular file

 

system). Files and directory operations are restricted to read-only after a period of time. A

 

WORM partition must be related to WORM media pools containing WORM media only.

WORM medium

On a WORM (Write Once Read Many) medium, data can be recorded only once. Once

 

recorded, the WORM medium cannot be overwritten, reformatted, or reinitialized, but new

 

data can be appended to the existing contents. A WORM medium can only be initialized in a

 

WORM media pool.

HP StorageWorks File System Extender Software installation guide for Linux 87

Image 87
Contents Part number T3648-96011 First edition October File System Extender Software installation guide for Linux Contents Upgrading from previous FSE releases Uninstalling FSE softwareTroubleshooting General problemsIntegrating existing file systems FSE system maintenance releases and hot fixesInstallation problems Integrating existing file systems in the FSE implementationPage Related documentation Document conventions and symbolsAbout this guide Intended audienceDocumentation feedback Subscription serviceHP technical support HP web sitesThis chapter includes the following topics Introduction and preparation basicsFSE implementation options Consolidated implementationConsolidated FSE implementation Distributed implementationMixed implementation Preparing file systems for FSE LicensingReasons for organizing file systems Organizing the file system layoutStorage 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 sizeFormula 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 filesInstalling the FSE Management Console on Installation overviewEtc/fstab Action Comments & where to find detailsSuse Linux Enterprise Server Required operating system updatesPreparing the operating system environment Preparing the operating systemPackage file name Rhel Package Package name in the rpm -qa output RhelVerifying third-party packages Installing Firebird SuperServer on an FSE serverPackage PackageName is not installed # rpm --install FirebirdSS-1.0.3.972-0.64IO.i386.rpmDisabling Acpi with Grub boot loader Disabling Acpi with Lilo boot loaderDisabling Acpi Page Preparing the operating system environment Preparing Logical Volume Manager LVM volumes Preparing file systems for FSEPreparing 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 filesCreating 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 softwareInstallation overview Installing an FSE releasePackages Installation procedureMonitoring the installation ConsolidatedPage Server = fseserver.company.net Verifying and repairing the installed FSE softwareRepairing the FSE software installation Determining the build numberModifying the Ldlibrarypath environment variable Preparing the FSE backup configuration fileConfiguring the FSE interprocess communication Modifying the Path environment variableNo external FSE clients or ordinary LAN connection Services.cfg Etc/opt/fse OmniORB.cfgHostname = fseserver.fsenet Server = fseserver.fsenet OmniORB.cfg file, configure the parameters in the sectionConfiguring communication on external FSE clients Server = fse-server1.company.comHostname = fseclient.fsenet Server = fseserver.fsenet # fse --start Starting the FSE implementationConsolidated FSE system Starting the FSE serverStarting FSE clients Bottom part of the output should match the followingFile Systems Restarting FSE processesRestarting local FSE processes FS Event Manager MountingIf the reported line is Checking the status of a running FSE implementationChecking Firebird SuperServer External FSE clientChecking the omniNames daemon Checking FSE ProcessesChecking Firebird SuperServer on Red Hat Enterprise Linux Configuring and starting Log Analyzer Configuring and starting HSM Health MonitorAutomating the mounting of HSM file systems Installing the FSE Management ConsoleInstalling the FSE Management Console server Installing the FSE Management Console clientDev/mapper/vgfsefs-fsefs01 Fse/fsefs01 Hsmfs noauto 0 Configuring the post-start and pre-stop helper scriptsPost-start script Add the following line to the /etc/fstab fileExample Pre-stop scriptInstalling 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 PartitionNameUpgrading the operating system on Linux hosts Command displays a report similar to the followingInstalling FSE release 3.4 software on the Linux FSE server Upgrading the Linux FSE serverAbove example, the value of DeviceFilePathname is Starting up the FSE server Starting OmniORB Naming Service FSE ServiceFor the above example, the command output is Upgrading the Windows FSE serverUpgrading Linux FSE clients Starting the HSM Health Monitor daemon on Linux systems Installing FSE release 3.4 software on a Linux FSE clientUpgrading Windows FSE clients Starting up a Linux FSE clientStarting the Log Analyzer daemons on Linux systems Starting the HSM Health Monitor service on Windows systemsStarting the Log Analyzer service on Windows systems Upgrading the FSE Management ConsoleVerifying availability of the configured FSE partitions # rpm -U fse-gui-client-3.4.0-Build.i386.rpmFsepartition --list Uninstalling basic FSE software Uninstalling FSE softwareUninstalling FSE software Uninstalling the FSE Management ConsoleVar/opt/fse/rmdb # omninames --stop Stopping omniORB Naming ServiceResource Manager Stopping # rpm -e `rpm -qa grep fse- grep -v fse-gui`Opt/fse Entity Location directory Location FSE host typeUninstalling FSE software General problems, Installation problems, TroubleshootingGeneral problems Installation problemsAdapter Line helps you determine if the adapter is connected to LANSystems, see the latest support matrices Page Troubleshooting HSMFileSystemRoot # find * -type f xargs -n1 head -n0 Integrating existing file systems in the FSE implementationIntegrating existing file systems # tune2fs -j /dev/fsesda/fs1Integrating existing file systems in the FSE implementation FSE hot fixes FSE system maintenance releases and hot fixesFSE system maintenance releases FSE releasesUninstalling a system maintenance release FSE system maintenance releases and FSE hot fixesInstalling a system maintenance release Determining the installed system maintenance release# fsesystem --version Determining the installed hot fixUninstalling a hot fix Command will display an output similar to the followingFSE system maintenance releases and hot fixes Media pool FSE media pool GlossaryFile System Catalog FSC FSE configuration file templateConfiguration file External client FSE external clientSee media duplication Needs cleaning or servicingOwn deletion policy Disk bufferSee recovery FSE recovery See recovery FSE recovery, recovery jobAlso Data Location Catalog DLC and Name Space Catalog NSC Mode LAM It, you must use forced initialization JobFSE job See Medium Auxiliary Memory MAM MediumRetention time Set to unusable Offline medium Library Online mediumRecall, recall job An FSE users request with the fserecover commandRecovery job InstallPath%\var\rmdb directory on Windows platformSee media pool FSE media pool FSE implementationUnusable medium Is set by enabling the drive with the fsedrive commandUltrium See LTO UltriumPage 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