Hello,
The copytool is responsible of maintaining the lustre to backend entry
association, which seams to be the problem in you case.
So It sounds like a problem with the TSM copytool.
HTH,
Thomas
On 05/15/18 20:58, Darcy Hodgson wrote:
All,
I know this isn't a robinhood question but this seems like the best
place to ask. We are setting up robinhood on our lustre system to
automatically archive data to tape on our TSM. The problem we have is
in the way TSM stores data, as in it identifies the file based on it's
name/path. If a user moves or renames a released file they will "lose"
their data.
Has anyone encountered this issue and solved it in a way that still
makes the user experience acceptable?
Thanks,
Darcy
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
robinhood-support mailing list
robinhood-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/robinhood-support
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
robinhood-support mailing list
robinhood-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/robinhood-support
