HP File System Extender (FSE) manual OmniORB.cfg file, configure the parameters in the section

Page 41

The following is an example of a correctly configured services.cfg file in an FSE implementation using a private network. The server variable is redundant in such FSE implementation:

hostname = fseserver.fsenet

server = fseserver.fsenet

2.In the omniORB.cfg file, configure the parameters in the section

--- Private network parameters --- with the following information:

the FQDN that identifies the system inside the private network

the IP address of the system

the subnet mask

All these parameters must be verified against the actual private network configuration. Ensure that the FQDN you specify in omniORB.cfg matches the FQDN specified for the hostname variable in the

services.cfg file.

The following example is an excerpt from a properly configured omniORB.cfg file:

#--- Private network parameters ---

#Which interface omniORB uses for IORs

endPoint = giop:tcp:fseserver.fsenet:

#The order of network interfaces to use for accepting connections:

#Only localhost and private network. Others are denied.

clientTransportRule = localhost tcp clientTransportRule = 192.168.240.0/255.255.255.0 tcp clientTransportRule = * none

#The order of network interfaces to use for opening new server connections:

#Only localhost and private network. Others are denied.

serverTransportRule = localhost tcp serverTransportRule = 192.168.240.0/255.255.255.0 tcp serverTransportRule = * none

The following is an example excerpt from the local /etc/hosts file that matches the above services.cfg and omniORB.cfg files:

123.45.67.89fse-server1.company.com fse-server1

192.168.240.1

fseserver.fsenet

fseserver

123.45.67.90fse-client1.company.com fse-client1

192.168.240.2

fseclient.fsenet

fseclient

HP StorageWorks File System Extender Software installation guide for Linux 41

Image 41
Contents Part number T3648-96011 First edition October File System Extender Software installation guide for Linux Contents Troubleshooting Uninstalling FSE softwareGeneral problems Upgrading from previous FSE releasesInstallation problems FSE system maintenance releases and hot fixesIntegrating existing file systems in the FSE implementation Integrating existing file systemsPage About this guide Document conventions and symbolsIntended audience Related documentationHP technical support Subscription serviceHP web sites Documentation feedbackFSE implementation options Introduction and preparation basicsConsolidated implementation This chapter includes the following topicsConsolidated 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 detailsPreparing the operating system environment Required operating system updatesPreparing the operating system Suse Linux Enterprise ServerPackage file name Rhel Package Package name in the rpm -qa output RhelPackage PackageName is not installed Installing Firebird SuperServer on an FSE server# rpm --install FirebirdSS-1.0.3.972-0.64IO.i386.rpm 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 Installation overview Installing FSE softwareInstalling an FSE release PrerequisitesMonitoring the installation Installation procedureConsolidated PackagesPage Repairing the FSE software installation Verifying and repairing the installed FSE softwareDetermining the build number Server = fseserver.company.netConfiguring the FSE interprocess communication Preparing the FSE backup configuration fileModifying the Path environment variable Modifying the Ldlibrarypath 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 implementationStarting FSE clients Starting the FSE serverBottom part of the output should match the following Consolidated FSE systemRestarting local FSE processes Restarting FSE processesFS Event Manager Mounting File SystemsChecking Firebird SuperServer Checking the status of a running FSE implementationExternal FSE client If the reported line isChecking Firebird SuperServer on Red Hat Enterprise Linux Checking the omniNames daemonChecking FSE Processes Configuring and starting Log Analyzer Configuring and starting HSM Health MonitorInstalling the FSE Management Console server Installing the FSE Management ConsoleInstalling the FSE Management Console client Automating the mounting of HSM file systemsPost-start script Configuring the post-start and pre-stop helper scriptsAdd the following line to the /etc/fstab file Dev/mapper/vgfsefs-fsefs01 Fse/fsefs01 Hsmfs noauto 0Example Pre-stop scriptInstalling FSE software Upgrading from previous FSE releases Upgrade overview# /etc/init.d/guisrv stop Shutting down the FSE implementation# cd /var/opt/fse/log # rm -f checkhsmfsfsc Var/opt/fse/log/checkhsmfsfscPartitionName.log# fsecheck --fsc-hsmfs PartitionName # hhm stopUpgrading 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 Upgrading Windows FSE clients Installing FSE release 3.4 software on a Linux FSE clientStarting up a Linux FSE client Starting the HSM Health Monitor daemon on Linux systemsStarting the Log Analyzer service on Windows systems Starting the HSM Health Monitor service on Windows systemsUpgrading the FSE Management Console 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 FSE software Uninstalling FSE softwareUninstalling the FSE Management Console Uninstalling basic FSE softwareResource Manager Stopping # omninames --stop Stopping omniORB Naming Service# rpm -e `rpm -qa grep fse- grep -v fse-gui` Var/opt/fse/rmdbOpt/fse Entity Location directory Location FSE host typeUninstalling FSE software General problems TroubleshootingInstallation problems General problems, Installation problems,Systems, see the latest support matrices AdapterLine helps you determine if the adapter is connected to LAN Page Troubleshooting Integrating existing file systems Integrating existing file systems in the FSE implementation# tune2fs -j /dev/fsesda/fs1 HSMFileSystemRoot # find * -type f xargs -n1 head -n0Integrating existing file systems in the FSE implementation FSE system maintenance releases FSE system maintenance releases and hot fixesFSE releases FSE hot fixesInstalling a system maintenance release FSE system maintenance releases and FSE hot fixesDetermining the installed system maintenance release Uninstalling a system maintenance releaseUninstalling a hot fix Determining the installed hot fixCommand will display an output similar to the following # fsesystem --versionFSE system maintenance releases and hot fixes Media pool FSE media pool GlossaryConfiguration file FSE configuration file templateExternal client FSE external client File System Catalog FSCOwn deletion policy Needs cleaning or servicingDisk buffer 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 Library Offline mediumOnline medium Set to unusableRecovery job An FSE users request with the fserecover commandInstallPath%\var\rmdb directory on Windows platform Recall, recall jobSee media pool FSE media pool FSE implementationUltrium Is set by enabling the drive with the fsedrive commandSee 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.