HP File System Extender (FSE) manual Checking the omniNames daemon, Checking FSE Processes

Page 47

Checking Firebird SuperServer on Red Hat Enterprise Linux

You can check if the FirebirdSS process is running with the command below. This example also displays its output with FirebirdSS running.

#/etc/init.d/firebird status ibserver (pid 2260) is running...

If the reported line is:

ibserver is stopped

you need to start Firebird manually using the following command. This command also displays its output when FirebirdSS is successfully started:

# /etc/init.d/firebird start

Starting ibserver:

[ OK ]

If this does not resolve the problem, consult Firebird SuperServer documentation for alternative troubleshooting steps.

Checking the omniNames daemon

You can check the status of the omniNames daemon with the omninames --statuscommand. If you followed the steps in section ”Modifying the PATH environment variable” on page 39, the omninames location should be in the command search path. Enter the following:

# omninames --status

The command should generate an output similar to the following example:

omniNames ( pid 842 ) is running...

If the reported line is:

omniNames is stopped

you need to start omniNames manually using the following command. This command also displays its output when the omniNames daemon is successfully started:

# omninames --start

 

Starting omniORB Naming Service:

[ OK ]

Checking FSE Processes

The status of FSE daemons can be monitored using the fse command. Apart from checking the status, this command is also used for starting and stopping the FSE daemons. Starting and stopping actions are only allowed to be executed by an FSE administrator, but all users can do a status check.

You can check the status of locally running FSE daemons by running the fse command with the --statusoption:

# fse --status

The output of this command depends on the type of FSE implementation.

The next section contains outputs of the fse --statuscommand when it is run on a particular component of the FSE implementation. You should check the status of the FSE daemons and verify that the output you get corresponds to the appropriate example.

Checking FSE daemons is the last step of the basic installation process. However, it is strongly recommended that you also perform the post-installation steps described in the next section.

For a description of configuration procedures, see the FSE user guide.

HP StorageWorks File System Extender Software installation guide for Linux 47

Image 47
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 LicensingStorage 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 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 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 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 sectionHostname = fseclient.fsenet Server = fseserver.fsenet Configuring communication on external FSE clientsServer = fse-server1.company.com # 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 Firebird SuperServer on Red Hat Enterprise Linux Checking the omniNames daemonChecking FSE Processes 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 followingAbove example, the value of DeviceFilePathname is Installing FSE release 3.4 software on the Linux FSE serverUpgrading the Linux FSE server Starting up the FSE server Starting OmniORB Naming Service FSE ServiceUpgrading Linux FSE clients For the above example, the command output isUpgrading the Windows FSE server 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 ConsoleFsepartition --list Verifying availability of the configured FSE partitions# rpm -U fse-gui-client-3.4.0-Build.i386.rpm 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 problemsSystems, see the latest support matrices AdapterLine helps you determine if the adapter is connected to LAN 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 bufferAlso 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 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.