On 20/06/18 17:00, Grunenberg, Renar wrote:
Hallo Valdis, first thanks for the explanation we understand that, but this problem generate only 2 Version at tsm server for the same file, in the same directory. This mean that mmbackup and the .shadow... has no possibility to have for the same file in the same directory more then 2 backup versions with tsm. The native ba-client manage this. (Here are there already different inode numbers existent.) But at TSM-Server side the file that are selected at 'ba incr' are merged to the right filespace and will be binded to the mcclass >2 Version exist.
I think what you are saying is that mmbackup is only keeping two versions of the file in the backup, the current version and a single previous version. Normally in TSM you can control how many previous versions of the file that you can keep, for both active and inactive (aka deleted). You can also define how long these version are kept for.
It sounds like you are saying that mmbackup is ignoring the policy that you have set for this in TSM (q copy) and doing it's own thing?
JAB. -- Jonathan A. Buzzard Tel: +44141-5483420 HPC System Administrator, ARCHIE-WeSt. University of Strathclyde, John Anderson Building, Glasgow. G4 0NG _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
