HP File System Extender (FSE) manual Modifying the Path environment variable

Page 39

Use the rpm -Vcommand to check whether the software installation is corrupt. Note that applied FSE hot fixes change individual binaries and other files making it difficult to determine whether or not the installation is corrupt. Proceed as follows:

1.Change the current directory to one with the FSE installation packages and reinstall the packages:

#cd PathToFSEPackageDirectory

#rpm -F --force fse*.rpm

2.Verify the reinstalled packages using the following command:

#rpm -V `rpm -qa grep fse`

If all FSE release or FSE system maintenance release files were correctly updated, the command output is empty.

Preparing the environment for the first startup of the FSE implementation

Preparing the environment consists of modifying environment variables, updating the FSE backup configuration files, and configuring the FSE interprocess communication.

Modifying the PATH environment variable

To be able to execute FSE commands, FSE tools, the omninames command, and start the FSE Management Console client from any location, change the search path as follows:

# export PATH=$PATH:/opt/fse/sbin:/opt/fse/sbin/tools:/opt/fse/bin

You can permanently extend the executable search path by adding the above line to your .bashrc shell startup file. The changes in .bashrc become effective after your next logon to the system as root.

Modifying the LD_LIBRARY_PATH environment variable

To enable Log Analyzer to run, set the variable for paths to shared libraries as follows:

# export LD_LIBRARY_PATH=/usr/local/lib

You can permanently extend the executable search path by adding the above line to your .bashrc shell startup file. The changes in .bashrc become effective after your next logon to the system as root.

Modifying the MANPATH environment variable

To read the FSE man pages, extend the search path for man pages as follows:

# export MANPATH=$MANPATH:/opt/fse/man

You can permanently extend the man page search path by adding the above line to your .bashrc shell startup file. The changes in .bashrc become effective after your next logon to the system as root.

Preparing the FSE backup configuration file

Configure the parameter SNAPSHOT_PCT in the backup configuration file /etc/opt/fse/backup.cfg.

The line from backup.cfg with SNAPSHOT_PCT configured with its default value is the following:

SNAPSHOT_PCT=10

For details, see the FSE user guide, chapter ”Backup, restore, and recovery”, section ”Backup”, subsection ”How it works?”.

Configuring the FSE interprocess communication

FSE interprocess communication is configured according to the FSE implementation (consolidated, distributed, or mixed FSE implementation) and the network type used for FSE interprocess communication (ordinary LAN, private network). In this context, the term ordinary LAN means the common company LAN to which systems are attached using their primary network adapters, and the term private network means a dedicated network to which systems are attached using their secondary network adapters.

HP StorageWorks File System Extender Software installation guide for Linux 39

Image 39
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 LicensingReasons 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 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 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 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 sectionConfiguring communication on external FSE clients Server = fse-server1.company.comHostname = 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 the omniNames daemon Checking FSE ProcessesChecking 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 followingInstalling FSE release 3.4 software on the Linux FSE server Upgrading the Linux FSE serverAbove example, the value of DeviceFilePathname is Starting up the FSE server Starting OmniORB Naming Service FSE ServiceFor the above example, the command output is Upgrading the Windows FSE serverUpgrading 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 ConsoleVerifying availability of the configured FSE partitions # rpm -U fse-gui-client-3.4.0-Build.i386.rpmFsepartition --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 problemsAdapter Line helps you determine if the adapter is connected to LANSystems, 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 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 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.