HP File System Extender (FSE) manual Licensing, Preparing file systems for FSE

Page 12

IMPORTANT: In a mixed FSE implementation, if the FSE processes on the consolidated FSE system are restarted, you must restart the FSE processes on all external FSE clients to resume the normal FSE operation.

Licensing

There are both per machine and capacity-based licenses for HP File System Extender.

For every machine that runs an FSE client, you need an FSE client license appropriate to the operating system.

For every machine that runs the FSE server, you need a base license appropriate to the operating system. The base license includes a license to migrate 1 TB to secondary storage managed by the FSE server.

To migrate more than 1 TB to the secondary storage, you need additional FSE server capacity licenses. These are available in 1 TB increments. The migrated capacity is the sum of all capacity migrated to the secondary storage from all associated FSE clients, including all copies where two or more copies of migrated files are configured, and all versions of modified migrated files.

To upgrade the FSE client-managed file system to WORM you need a capacity-based license. This is available in 1 TB increments. The capacity for this WORM license is based on the physical capacity occupied by the upgraded FSE file system on the production disk.

Preparing file systems for FSE

In order to optimize operation of the FSE implementation and increase its reliability, you should organize file systems on the host that will become the FSE server, as well as on the FSE client. If you intend to use disk media, you also need to prepare file systems to hold disk media files.

The following sections explain the importance of preparing file systems for FSE operation and provide formulas to estimate the required space for FSE components. These explanations and formulas apply generally when configuring an FSE implementation. The preparation is described in ”Preparing file systems” on page 27.

The following table summarizes the main parameters to be considered when setting up the environment. These parameters are discussed later in this chapter.

Table 2 Pre-installation size considerations

Parameter

Description

Reference

 

 

 

HSM file system size

Determine the minimum HSM file

Formula for the expected HSM

 

system size using such data as

file system size” on page 15

 

expected number of files and

 

 

average file size.

 

 

 

 

Fast Recovery Information (FRI) size

Determine the expected size of FRI.

Formula for the expected size of

 

 

Fast Recovery Information” on

 

 

page 15

 

 

 

File System Catalog (FSC) size

FSC contains location history and

Formula for the expected File

 

metadata. Determine expected size

System Catalog size” on page 15

 

of FSC.

 

 

 

 

HSM database (HSMDB) size

Determine expected HSM database

Formula for the expected

 

size

Hierarchical Storage Manager

 

 

Database (HSMDB) size” on

 

 

page 16

 

 

 

12 Introduction and preparation basics

Image 12
Contents Part number T3648-96011 First edition October File System Extender Software installation guide for Linux Contents Uninstalling FSE software TroubleshootingGeneral problems Upgrading from previous FSE releasesFSE system maintenance releases and hot fixes Installation problemsIntegrating existing file systems in the FSE implementation Integrating existing file systemsPage Document conventions and symbols About this guideIntended audience Related documentationSubscription service HP technical supportHP web sites Documentation feedbackIntroduction and preparation basics FSE implementation optionsConsolidated implementation 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/fstabRequired operating system updates Preparing the operating system environmentPreparing the operating system Suse Linux Enterprise ServerPackage Package name in the rpm -qa output Rhel Package file name RhelInstalling Firebird SuperServer on an FSE server Package PackageName is not installed# rpm --install FirebirdSS-1.0.3.972-0.64IO.i386.rpm 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 FSE software Installation overviewInstalling an FSE release PrerequisitesInstallation procedure Monitoring the installationConsolidated PackagesPage Verifying and repairing the installed FSE software Repairing the FSE software installationDetermining the build number Server = fseserver.company.netPreparing the FSE backup configuration file Configuring the FSE interprocess communicationModifying the Path environment variable 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 --startStarting the FSE server Starting FSE clientsBottom part of the output should match the following Consolidated FSE systemRestarting FSE processes Restarting local FSE processesFS Event Manager Mounting File SystemsChecking the status of a running FSE implementation Checking Firebird SuperServerExternal FSE client 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 Installing the FSE Management Console serverInstalling the FSE Management Console client Automating the mounting of HSM file systemsConfiguring the post-start and pre-stop helper scripts Post-start scriptAdd the following line to the /etc/fstab file 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 stopVar/opt/fse/log/checkhsmfsfscPartitionName.log # cd /var/opt/fse/log # rm -f checkhsmfsfsc# fsecheck --fsc-hsmfs PartitionName # 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 Installing FSE release 3.4 software on a Linux FSE client Upgrading Windows FSE clientsStarting up a Linux FSE client Starting the HSM Health Monitor daemon on Linux systemsStarting the HSM Health Monitor service on Windows systems Starting the Log Analyzer service on Windows systemsUpgrading the FSE Management Console 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 FSE software Uninstalling FSE softwareUninstalling the FSE Management Console Uninstalling basic FSE software# omninames --stop Stopping omniORB Naming Service Resource Manager Stopping# rpm -e `rpm -qa grep fse- grep -v fse-gui` Var/opt/fse/rmdbEntity Location directory Location FSE host type Opt/fseUninstalling FSE software Troubleshooting General problemsInstallation problems General problems, Installation problems,Adapter Line helps you determine if the adapter is connected to LANSystems, see the latest support matrices Page Troubleshooting Integrating existing file systems in the FSE implementation Integrating existing file systems# tune2fs -j /dev/fsesda/fs1 HSMFileSystemRoot # find * -type f xargs -n1 head -n0Integrating existing file systems in the FSE implementation FSE system maintenance releases and hot fixes FSE system maintenance releasesFSE releases FSE hot fixesFSE system maintenance releases and FSE hot fixes Installing a system maintenance releaseDetermining the installed system maintenance release Uninstalling a system maintenance releaseDetermining the installed hot fix Uninstalling a hot fixCommand will display an output similar to the following # fsesystem --versionFSE system maintenance releases and hot fixes Glossary Media pool FSE media poolFSE configuration file template Configuration fileExternal client FSE external client File System Catalog FSCNeeds cleaning or servicing Own deletion policyDisk buffer 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 Offline medium LibraryOnline medium Set to unusableAn FSE users request with the fserecover command Recovery jobInstallPath%\var\rmdb directory on Windows platform Recall, recall jobFSE implementation See media pool FSE media poolIs set by enabling the drive with the fsedrive command UltriumSee LTO Ultrium 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.