Filter
Top Products
to all nodes or unexpected results may occur.
• The Mover must be built with the LFT option. This is the default option for all Movers. If not all
Movers have been built with this option, clients must explicitly specify a class of service which is
valid for a Mover supporting the local file transfer option.
• The Mover must be running as root. If there are other Movers running on the same node, they
must also run as root to take advantage of the Mover-to-Mover shared memory data transfer.
• A new configuration file (/var/hpss/etc/hpss_mvr_localfilepath.conf) is
required on all nodes running an enhanced Mover.
The configuration file contains a list of UNIX paths. These paths specify which files are allowed to be
moved using this special data transfer protocol. Any UNIX file on the Mover node whose path starts with
a path in the list of entries is allowed to be transferred using the special data protocol.
If the configuration file does not exist, then the SSM will issue a minor alarm when the Mover starts, and
no UNIX files will be transferred with the special protocol.
Here is an example configuration file:
# This file contains Unix paths that can be accessed by the
# local Movers on this node. If the client wishes to make a
# local file transfer and the start of the client path matches
# any of the paths in this list then the transfer will proceed,
# otherwise the Mover will not transfer the file.
#
# The format of this file is simply a list of paths, one per
# line.
/gpfs
/local/globalfilesystem
In the above sample configuration, any file under the path, /gpfs or the path /local/globalfilesystem can
be transferred using the special data protocol subject to the caveats specified above.
Extreme care should be taken when using this feature. The Mover will move data from any file in its list.
If the UNIX file system is not global to all Mover nodes, the request will fail.
The following commands have been added to the HPSS Parallel FTP Clients to take advantage
of these new features: lfget, lfput, mlfget, mlfput, lfappend. See the HPSS User’s Guide for more
details. The hpss_ReadList and hpss_WriteList Client APIs can also be used to utilize the local
file transfer capability. See the HPSS Programmer’s Reference - I/O Supplement for more
details.
5.1.1. Physical Volume Repository (PVR) Specific Configuration
The PVR specific configuration entry can be created and managed using the PVR Server Configuration
window. If changes are made while the server is running, the server must be recycled in order for the
changes to become effective.
If you are configuring a PVR for StorageTek, IBM 3494/3584, ADIC AML, LTO, or generic SCSI: before
proceeding with PVR configuration you should read the PVR-specific section (Section 5.1.1.1: STK PVR
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 109