HP File System Extender (FSE) manual Resource Manager Stopping, Var/opt/fse/rmdb, Var/opt/fse/cfg

Page 64

Unloading HSMFS Filter module:

[

OK

]

Stopping FSE Management Interface:

[

OK

]

Stopping

FSE

Resource Manager:

[

OK

]

Stopping

FSE

Service:

[

OK

]

The fse --stopcommand executes the pre_stop script, if it exists. It also performs the following, depending on where it is run:

When used on a consolidated system or an external FSE client, the command unmounts all local mounted HSM file systems.

It terminates the respective consolidated FSE system, FSE server or FSE client operation by shutting down all locally running FSE processes on the belonging host.

4.Disable automatic mounting of local HSM file systems after subsequent restarts of the local FSE processes by commenting out the HSM file system entries in the file /etc/fstab.

For each such entry, add a hash characters followed by a single space at the beginning of the corresponding line, for example:

# /dev/mapper/vg_fsefs-fsefs_01

/fse/fsefs_01

hsmfs noauto 0 2

5.If you are uninstalling a consolidated FSE system or an FSE server, stop the omniNames daemon. The command and its output is shown below:

# omninames --stop

Stopping omniORB Naming Service

[ OK ]

6.Run the following command to remove all FSE packages from the system:

# rpm -e `rpm -qa grep "^fse-" grep -v fse-gui`

7.If FSE hot fixes have been installed, manually remove the backups of the original FSE release or FSE system maintenance release files from their backup location, the backup directory itself, and the hot fix ReadMe files from the /opt/fse/doc directory.

For details on FSE hot fixes, see appendix ”FSE system maintenance releases and hot fixes” on page 73.

8.The uninstallation process leaves the FSE databases and system files intact, and you must remove them manually.

CAUTION: Note that manual removal of the FSE databases and system files will permanently delete information about the FSE configuration and resources, and metadata of the FSE user files.

The set of entities that require manual removal depends on which FSE host is being uninstalled. Proceed as follows:

a.If there were separate file systems mounted for the FSE partition-specific files (to the directory /var/opt/fse/part) and the FSE log and debug files (to the directory /var/opt/fse/log), remove all directories and files from them, and then unmount them using the umount command.

b.Disable automatic mounting of these file systems by commenting out their file system entries in the file /etc/fstab, like you did in the step 2 for HSM file systems.

c.Remove the following entities by deleting the corresponding directories using the rm -rcommand:

Entity

Location (directory)

Location (FSE host type)

 

 

 

Resource Management Database

/var/opt/fse/rmdb

consolidated FSE system, FSE server

(RMDB)

 

 

 

 

 

File System Catalogs (FSCs)

/var/opt/fse/part

consolidated FSE system, FSE server

 

 

 

Hierarchical Storage Management

/var/opt/fse/part

consolidated FSE system, FSE client

Databases (HSMDBs)

 

 

 

 

 

Configuration database (CfgDB)

/var/opt/fse/cfg

consolidated FSE system, FSE server

 

 

 

64 Uninstalling FSE software

Image 64
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 FSEOrganizing 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 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 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 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.fsenetServer = fse-server1.company.com Configuring communication on external FSE clientsHostname = 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 FSE Processes Checking the omniNames daemonChecking 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 hostsUpgrading the Linux FSE server Installing FSE release 3.4 software on the Linux FSE serverAbove example, the value of DeviceFilePathname is Starting OmniORB Naming Service FSE Service Starting up the FSE serverUpgrading the Windows FSE server For the above example, the command output isUpgrading 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 systems# rpm -U fse-gui-client-3.4.0-Build.i386.rpm Verifying availability of the configured FSE partitionsFsepartition --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,Line helps you determine if the adapter is connected to LAN AdapterSystems, 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, 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 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.