Upgrading from GPFS 4.2.x to GPFS 4.2.y should not "break" TSM. If it
does, someone goofed, that would be a bug. (My opinion)
Think of it this way. TSM is an application that uses the OS and the
FileSystem(s). TSM can't verify it will work with all future versions of
OS and Filesystems,
Hi all,
Where should I start looking for a compatibility matrix between TSM and GPFS?
Specifically, we are currently running TSM 7.1.6-2 and GPFS 4.2.1-2 with the
intent to upgrade to GPFS 4.2.3-latest in early July.
I've spent 30 minutes looking over various documents and the best I can find
It has been a while since I used HSM with GPFS via TSM, but as far as
I can remember, unprivileged users can run dsmmigrate and dsmrecall.
Based on the instructions on the link, dsmrecall may now leverage the
Recommended Access Order (RAO) available on enterprise drives, however
root would
Thanks Jaime,
How do you get around Optimised recalls?
from what I can see the optimised recall process needs a root level account to retrieve a list of files
https://www.ibm.com/support/knowledgecenter/SSSR2R_7.1.1/com.ibm.itsm.hsmul.doc/c_recall_optimized_tape.html
Regards,
Andrew
We have that situation.
Users don't need to login to NSD's
What you need is to add at least one gpfs client to the cluster (or
multi-cluster), mount the DMAPI enabled file system, and use that node
as a gateway for end-users. They can access the contents on the mount
point with their own
