This demand I also posted to the gpfs-forum !
I set up a TSM-for Spacemanagement (HSM)-Service integrating a gpfs-filesystem with about 100 different filesets.
After testing manually with various dsmmigrate-, dsmrecall-, dsmreconcile-jobs
and adjusting appropriate TSM-service-,-HSM- and gpfs-settings,
the HSM-tools worked without problems.
Than I migrated "gpfs-policy-driven"
about 60 TB of gpfs-data (located in different storage pools and filesets)
=> no problems also with the recall of part of it through "user-access".
dsmreconcile-tool (that worked for the small data-ammount before)
every evening at 19:02 o'clock ran into an error:
Reconciling '/gpfs/airsat' file system:
Querying the TSM server for a list of migrated files...
(=> at 19:02 independent from the start)
ANS8049E A connection with the server cannot be established due to a communications time-out.
ANS9082W dsmreconcile: error encountered while reconciling file system /gpfs/airsat.
=> The reconcilation stopped
changing different parameters in the dsm.sys (RECOncileinterval to 0 / 9999 etc.)
than restarting everytimes the TSM-service
=> same behaviour.
Is there any parameter to adjust (server or client) ?
Can anybody give me a hint on this behaviour and how to prevent it ?