HP File System Extender (FSE) manual Own deletion policy, Needs cleaning or servicing, Disk buffer

Page 79

debug file

A log file of a single FSE process, which records the execution trace of operations inside the

(FSE debug file)

process. FSE debug files are created only if tracing in FSE is enabled (typically on request of

 

technical support personnel of FSE). FSE debug files are located in the directory

 

/var/opt/fse/log/debug (on Linux platform) or in the directory

 

%InstallPath%\var\log\debug (on Windows platform).

deletion policy

A set of rules that define expiration periods for groups of directories on an HSM file system.

 

Files which are older than the expiration period defined by the corresponding deletion policy

 

can be automatically deleted using the fsefile command. Configuration parameters for the

 

deletion policy are specified in the FSE partition configuration file. Each FSE partition has its

 

own deletion policy.

dirty file

A file on an HSM file system which has been recently created and not yet migrated, or a file

 

that has changed since the last migration or recall.

disabled drive

An FSE drive which is temporarily put out of operation and cannot be used by migration, recall,

 

administrative, maintenance and recovery jobs. This is done by changing its status in the

 

Resource Management Database to disabled. The status is set by an FSE administrator with

 

the fsedrive command. The example situation that calls for disabling the drive is when it

 

needs cleaning or servicing.

disk buffer

One or more file systems, located on the consolidated FSE system or the FSE server, which are

(FSE disk buffer)

configured to store temporary data used by some of the FSE processes. The FSE disk buffer is

 

managed by the Resource Manager. Separate file systems (on Linux platform) or volumes (disk

 

partitions, on Windows platform) are usually allocated for FSE disk buffer.

disk media pool An FSE disk media pool is a special type of FSE media pool where the migrated data is stored (FSE disk media pool)on disks rather than on tape media. FSE disk media therefore emulate FSE tape media, with the

advantage of being much faster for migrations and recalls. Using and managing FSE disk media pools is similar to using and managing FSE tape media pools. See also ”media pool (FSE media pool)”.

disk medium

A disk medium is one file system mounted to a subdirectory of the directory

(FSE disk medium)

/var/opt/fse/dm (on Linux platform) or the directory %InstallPath%\var\dm (on

 

Windows platform). Disk media emulates tape media and is used for regular archiving of the

 

data on HSM file systems. The advantage of using disk media is in shortened recall of offline

 

files. See also ”medium (FSE medium)”.

drive

A tape drive inside the FSE library, configured to be used by the FSE implementation.

(FSE drive)

 

duplication

See ”media duplication”.

enabled drive

An FSE drive which is put back in operation by changing its status in the Resource

 

Management Database to online. This status is set manually using the fsedrive command.

 

An enabled drive is fully available for FSE system operation.

erroneous drive

An FSE drive which is temporarily put out of operation and cannot be used by migration, recall,

 

administrative, maintenance and recovery jobs. Its status is automatically set in the Resource

 

Management Database to error as soon as the problems in the drive are detected by the

 

Back End Agent. Usually, such problems occur when the drive needs servicing.

error log

A file that records error messages of the running FSE processes. It stores information on all

(FSE error log)

major errors that occur during FSE system operation. These errors often require an intervention

 

of the FSE administrator. Major errors are, for example, failed initialization of an FSE medium,

 

erroneous FSE drive operation, migration job failure, and so on. The FSE error log also provides

 

usage statistics that can be used for fine tuning of the FSE configuration. The FSE error log,

 

named error.log, is located in the directory /var/opt/fse/log (on Linux platform) or in

 

the directory %InstallPath%\var\log (on Windows platform).

HP StorageWorks File System Extender Software installation guide for Linux 79

Image 79
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 LicensingOrganizing 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 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 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 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 sectionServer = fse-server1.company.com Configuring communication on external FSE clientsHostname = 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 FSE Processes Checking the omniNames daemonChecking 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 followingUpgrading the Linux FSE server Installing FSE release 3.4 software on the Linux FSE serverAbove example, the value of DeviceFilePathname is Starting up the FSE server Starting OmniORB Naming Service FSE ServiceUpgrading the Windows FSE server For the above example, the command output isUpgrading 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 Console# rpm -U fse-gui-client-3.4.0-Build.i386.rpm Verifying availability of the configured FSE partitionsFsepartition --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 problemsLine helps you determine if the adapter is connected to LAN AdapterSystems, 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, 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 Set to unusable Offline mediumLibrary 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

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.