HP File System Extender (FSE) manual External client FSE external client, Configuration file

Page 78

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

An FSE command-line interface command that communicates with FSE system components

(FSE command)

through the Management Interface. FSE commands are used to configure, monitor, and

 

maintain the FSE implementation.

command-line

A set of FSE commands that are available to FSE users.

interface

 

(FSE command-line

 

interface (FSE CLI))

 

Configuration

A directory in the FSE directory layout which contains the currently used and old revisions of the

Database (CfgDB)

FSE configuration files for configured FSE resources.

configuration file

A plain text file used to configure or modify the configuration of an FSE resource. FSE

(FSE configuration

configuration files are stored in the Configuration Database. The Configuration Database is

file)

located in the directory /var/opt/fse/cfg (on Linux platform) or in the directory

 

%InstallPath%\var\cfg (on Windows platform). See also ”configuration file template

 

(FSE configuration file template)”.

configuration file

A pre-designed document for an FSE configuration file, included in the FSE package. It contains

template

default configuration values for configuring an FSE resource. These values should be modified

(FSE configuration file before the FSE administrator can apply the template. FSE configuration file templates are

template)

located in the directory /opt/fse/newconfig (on Linux platform) or in the directory

 

%InstallPath%\newconfig (on Windows platform). See also ”configuration file (FSE

 

configuration file)”.

configuration revisionRevision of an FSE configuration file. Each configured FSE resource has its own set of

(FSE configuration

configuration revisions stored in the Configuration Database. This set represents the

revision)

configuration history of that resource.

consistency check of

A process executed for a particular FSE partition that checks the consistency of the

FSC

corresponding File System Catalog (FSC). It compares the contents of the FSC either with the

 

corresponding HSM file system or with Fast Recovery Information (FRI) for that FSE partition.

 

Any inconsistencies found are reported to the shell output and to the FSE check log. The FSC

 

consistency check is performed by an appropriate type of maintenance job.

CORBA

CORBA is the acronym for Common Object Request Broker Architecture. This is an architecture

 

and infrastructure that computer applications use to work together over networks.

critical watermark

A user-defined value for the critical level of disk space usage on an HSM file system. When this

 

value is reached, a forced release process is started for all files on the Hierarchical Storage

 

Manager’s release candidate list.

daemon (service)

An FSE process that runs on the FSE implementation to provide basic functionality. FSE

(FSE daemon

daemons (services) are: File System Event Manager, Hierarchical Storage Manager, Partition

(service))

Manager, Management Interface, Resource Manager and Service.

Data Location

A part of a File System Catalog. Data Location Catalog contains information about locations of

Catalog (DLC)

the migrated file data on the FSE media. It maintains a full history of file locations. See also

 

File System Catalog (FSC)”.

database

A file or set of related files with important information on the current status of the FSE

(FSE database)

implementation, characteristics of the FSE implementation, or configuration of the FSE

 

implementation. FSE databases are the Resource Management Database, File System Catalogs,

 

Hierarchical Storage Management Databases, and Configuration Database.

78

Image 78
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 FSEReasons 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 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 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 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.fsenetConfiguring communication on external FSE clients Server = fse-server1.company.comHostname = 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 the omniNames daemon Checking FSE ProcessesChecking 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 hostsInstalling FSE release 3.4 software on the Linux FSE server Upgrading the Linux FSE serverAbove example, the value of DeviceFilePathname is Starting OmniORB Naming Service FSE Service Starting up the FSE serverFor the above example, the command output is Upgrading the Windows FSE serverUpgrading 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 systemsVerifying availability of the configured FSE partitions # rpm -U fse-gui-client-3.4.0-Build.i386.rpmFsepartition --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 TroubleshootingGeneral problems General problems, Installation problems,Adapter Line helps you determine if the adapter is connected to LANSystems, 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 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 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

File System Extender (FSE) specifications

HP File System Extender (FSE) is a sophisticated solution designed to optimize data storage management for enterprises that deal with large volumes of unstructured data. This technology addresses the challenges of data growth and the need for effective data retention strategies, enabling organizations to store and manage their information more efficiently.

One of the main features of HP FSE is its ability to intelligently migrate data between primary and secondary storage. By utilizing policies that determine when to move infrequently accessed files to lower-cost storage environments, FSE helps reduce the strain on primary storage systems and saves on costs associated with high-performance storage solutions. This tiered approach to data management ensures that organizations can access the data they need quickly while still maintaining an efficient overall storage architecture.

Another notable characteristic of HP FSE is its seamless integration with existing storage infrastructures. The solution works with a variety of storage systems, allowing organizations to utilize their current investments without the need for significant changes to their infrastructure. This interoperability is powered by advanced technologies that facilitate data migration and retrieval, ensuring a smooth transition for organizations looking to optimize their storage strategies.

Additionally, HP FSE is equipped with robust reporting and analytics capabilities. This functionality provides organizations with insights into their storage usage, helping them understand data patterns and optimize their storage environments accordingly. By having visibility into which files are accessed most frequently and which are rarely used, organizations can make informed decisions on data retention policies and storage management.

Security is paramount in data management, and HP FSE addresses this concern by implementing advanced data protection features. This includes data encryption, secure access controls, and compliance with industry regulations, ensuring that sensitive information is safeguarded throughout its lifecycle.

Overall, HP File System Extender is a comprehensive data storage solution that combines intelligent data management, seamless integration, insightful analytics, and robust security features. By leveraging these capabilities, organizations can efficiently manage their unstructured data, lower costs, and enhance operational efficiency, making it an invaluable tool in today’s data-driven landscape.