HP File System Extender (FSE) manual Create the four remaining directories

Page 32

3.To ensure that the file system is automatically mounted at system startup, add the appropriate entry to the file system table in the file /etc/fstab. When adding the entry, note that the device name in the first column corresponds to the device file that you retrieved in the previous step:

/dev/mapper/vg_fse-fsevar

/var/opt/fse

ext3 defaults

1 2

4.Manually mount the corresponding file system for the directory /var/opt/fse. You must use the device (logical volume) name from your actual LVM configuration:

#mount /dev/mapper/vg_fse-fsevar

5.Create the four remaining directories:

#mkdir /var/opt/fse/part

#mkdir /var/opt/fse/fri

#mkdir /var/opt/fse/log

#mkdir -p /var/opt/fse/diskbuf/FileSystemMountPoint

FileSystemMountPoint should be a unique subdirectory name.

6.Invoke the following commands to retrieve the names of the device files. Use the symbolic links from the step 1 of section ”Creating file systems on top of LVM logical volumes”:

# ls -la /dev/vg_fse/fsepart

lrwxrwxrwx 1 root root 25 Aug 17 09:12 /dev/vg_fse/fsepart -> /dev/mapper/vg_fse-fsepart

# ls -la /dev/vg_fse/fsefri

lrwxrwxrwx 1 root root 25 Aug 17 09:12 /dev/vg_fse/fsefri -> /dev/mapper/vg_fse-fsefri

# ls -la /dev/vg_fse/fselog

lrwxrwxrwx 1 root root 25 Aug 17 09:12 /dev/vg_fse/fselog -> /dev/mapper/vg_fse-fselog

# ls -la /dev/vg_fse/fsediskbuf

lrwxrwxrwx 1 root root 25 Aug 17 09:12 /dev/vg_fse/fsediskbuf -> /dev/mapper/vg_fse-fsediskbuf

7.Add the appropriate entries to the file system table in the file /etc/fstab. When adding the entries, note that the device names in the first column correspond to the device files that you retrieved in the previous step:

/dev/mapper/vg_fse-fsepart

/var/opt/fse/part

ext3 data=journal

1

2

/dev/mapper/vg_fse-fsefri

/var/opt/fse/fri

ext3

defaults

 

1

2

/dev/mapper/vg_fse-fselog

/var/opt/fse/log

ext3

defaults

 

1

2

/dev/mapper/vg_fse-fsediskbuf

/var/opt/fse/diskbuf/FileSystemMountPoint \

 

ext3 defaults

1

2

 

 

NOTE: The keyword data=journal must be specified in the fourth column in /etc/fstab for correctly mounting the file system on the /var/opt/fse/part directory. This improves file system stability and performance.

Note that all parameter entries must be entered in the proposed order.

NOTE: If you created an Ext2 file system for the FSE disk buffer, modify the fstab entry in the above example accordingly.

32 Preparing file systems for FSE

Image 32
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 FSEStorage 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 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 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 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.fsenetHostname = fseclient.fsenet Server = fseserver.fsenet Configuring communication on external FSE clientsServer = fse-server1.company.com 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 Firebird SuperServer on Red Hat Enterprise Linux Checking the omniNames daemonChecking FSE Processes 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 hostsAbove example, the value of DeviceFilePathname is Installing FSE release 3.4 software on the Linux FSE serverUpgrading the Linux FSE server Starting OmniORB Naming Service FSE Service Starting up the FSE serverUpgrading Linux FSE clients For the above example, the command output isUpgrading the Windows FSE server 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 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 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,Systems, see the latest support matrices AdapterLine helps you determine if the adapter is connected to LAN 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 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 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.