HP File System Extender (FSE) manual Estimating the size of file systems

Page 14

Table 3 FSE server directory layout

Directory

Contents

File system type

LVM volume

 

 

 

 

/var/opt/fse/

Configuration Database, Resource

Ext3

required for the

 

Management Database, other

 

FSE backup

 

FSE system files

 

 

 

 

 

 

/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

Temporary files of the FSE disk

any

not required

/var/opt/fse/diskbuf/FS2

buffer

 

 

...

 

 

 

 

 

 

 

/var/opt/fse/log/

FSE log files, FSE debug files

any

required for the

 

 

 

FSE backup

 

 

 

 

/var/opt/fse/dm/Barcode/

FSE disk media

any

recommended

 

 

 

 

1.Mount points of file systems assigned to the FSE disk buffer, where /var/opt/fse/diskbuf/ is the root directory of the FSE disk buffer.

NOTE: You can assign additional file systems or volumes to the FSE disk buffer. These file systems must be mounted on subdirectories one level below the root directory of the FSE disk buffer. For details, see the FSE user guide, chapter ”Monitoring and maintaining FSE”, section ”Extending storage space of FSE disk buffer”.

IMPORTANT: To achieve a sufficient stability of the FSE disk media, a separate file system must be dedicated for each disk medium, and it must be mounted to the corresponding subdirectory of the FSE disk media directory. Thus, the FSE disk media directory itself does not need to be located on a separate file system.

Table 4 FSE client directory layout

Directory

Contents

File system type

LVM volume

 

 

 

 

/var/opt/fse/part/

Hierarchical Storage

Ext3

required

 

Management Databases

 

 

 

 

 

 

/var/opt/fse/log/

FSE log files, FSE debug

any

required, if the client is part of

 

files

 

the consolidated FSE system

 

 

 

 

Estimating the size of file systems

Each of the previously mentioned file systems holds large databases and/or system files. Therefore, you need to calculate the space requirement for all of them before they are created.

The sizes of the HSM file system, Fast Recovery Information (FRI) files, File System Catalog (FSC), and Hierarchical Storage Manager Database (HSMDB) files are all related to several parameters. Among these parameters are the number of files on an HSM file system and their average size.

By default, 32 MB of journal space is created on Ext3 file systems. This should be sufficient for the file systems of the following directories:

/var/opt/fse

/var/opt/fse/part

/var/opt/fse/diskbuf

14 Introduction and preparation basics

Image 14
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 FSEStorage space for FSE debug Reasons for organizing file systemsOrganizing the file system layout Estimating the size of file systems Formula for the expected File System Catalog size Formula for the expected size of Fast Recovery InformationFormula for the expected HSM file system 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 Disabling Acpi with Grub boot loaderDisabling Acpi with Lilo boot loader Page Preparing the operating system environment Preparing file systems Preparing Logical Volume Manager LVM volumesPreparing file systems for FSE # pvcreate /dev/cciss/c0dp1 # pvcreate /dev/cciss/c0dp2 Create and initialize LVM logical volume groupsCreate and initialize LVM logical volumes # lvcreate -L 400G -n fsefs01 vgfsefs Create LVM logical volumes for HSM file systems# lvcreate -L 20G -n fsediskbufNumber vgfse # mkfs.ext3 -b 4096 -N 1000000 /dev/vgfsefs/examplefs Creating file systems on top of LVM logical volumesCreating file systems for FSE databases and system files Creating HSM file systems Command generates an output similar to the followingMounting file systems for FSE databases and system files # mount /dev/mapper/vgfse-fsevar Dev/mapper/vgfse-fsevar Var/opt/fse Ext3 defaultsCreate the four remaining directories # mount /dev/mapper/vgfse-fsediskbufNumber # mkdir /var/opt/fse/diskbuf/NewFileSystemMountPointDev/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.fsenetHostname = fseclient.fsenet Server = fseserver.fsenet Configuring communication on external FSE clientsServer = fse-server1.company.com 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 Firebird SuperServer on Red Hat Enterprise Linux Checking the omniNames daemonChecking FSE Processes 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 hostsAbove example, the value of DeviceFilePathname is Installing FSE release 3.4 software on the Linux FSE serverUpgrading the Linux FSE server Starting OmniORB Naming Service FSE Service Starting up the FSE serverUpgrading Linux FSE clients For the above example, the command output isUpgrading the Windows FSE server 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 systemsFsepartition --list Verifying availability of the configured FSE partitions# rpm -U fse-gui-client-3.4.0-Build.i386.rpm 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,Systems, see the latest support matrices AdapterLine helps you determine if the adapter is connected to LAN 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 duplicationAlso Data Location Catalog DLC and Name Space Catalog NSC See recovery FSE recoverySee recovery FSE recovery, recovery job Mode LAM FSE job It, you must use forced initializationJob Retention time See Medium Auxiliary Memory MAMMedium 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.