1.On all systems that host either an internal (part of the consolidated FSE system) or an external FSE client, close all applications that access files or directories on HSM file systems and make sure that all non-FSE processes which have had locks to objects on these file systems are terminated.

You can use the fuser or lsof command to find out which files are being accessed on the HSM file system. For details, refer to the fuser and lsof man pages.

2.Optionally, check the consistency of the File System Catalogs (FSCs) by comparing them with the corresponding HSM file systems.

Proceed as follows:

a.Before starting the consistency check, make sure that all consistency checking processes that might have already been running on FSE partitions have completed. Inspect the following log files:

/var/opt/fse/log/check_hsmfs_fsc_PartitionName.log

You can proceed with the next steps only if the log files show no current consistency checking activity.

b.On all systems that host FSE partitions, remove old consistency check log files. Run the following commands:

#cd /var/opt/fse/log/

#rm -f check_hsmfs_fsc_*

c.Start the consistency check for all configured FSE partitions. For each FSE partition, invoke the following command:

#fsecheck --fsc-hsmfs PartitionName

Search the resulting log files for inconsistency indicators. Before proceeding with shutting down the FSE implementation, you are urged to eliminate all inconsistencies found. For details, see the FSE user guide, chapter ”Monitoring and maintaining FSE”, section ”Checking the consistency of the File System Catalog”.

3.If you are upgrading your FSE product with an FSE system maintenance release or an FSE hot fix, on each external FSE client on which FSE utility daemons are running, you need to stop the FSE utility daemons:

a.To stop the HSM Health Monitor daemon on the local system, run the following command:

#hhm stop

b.To stop the Log Analyzer daemons on the local system, run the following commands:

#/etc/init.d/loganalyzer stop

#/etc/init.d/loganalyzer_messages stop

4.On each external FSE client, shut down the currently running FSE processes using the fse --stopcommand. The shut-down progress is shown in the command output:

# fse --stop

 

 

 

 

 

Unmounting HSM File Systems:

[

OK

]

Stopping

HSM

FS

Event Manager:

[

OK

]

Unloading HSMFS

Filter module:

[

OK

]

Stopping

FSE

Service:

[

OK

]

5.Verify that all FSE processes have been terminated properly: Run the following command. Its output should be empty:

#ps -ef grep fse

6.If you are upgrading your FSE product with an FSE system maintenance release or an FSE hot fix, if the FSE utility daemons are running on the consolidated FSE system or the FSE server, you need to stop them:

HP StorageWorks File System Extender Software installation guide for Linux 55