Hallo JAB, the main problem here is that the inode is changeing for the same file in the same directory. The mmbackup generate and execute at first the expirelist from the same file with the old inode number and afterward the selective backup for the same file with the new inode number. We want to test now to increase the version deleted Parameter here. In contrast to the ba incr in a local fs TSM make these steps in one and handle these issue. My hope now the mmbackup people can enhance these to generate a comparison list is the Filename in the selection list and the filename already in expirelist and check these first, skip these file from expire list, before the expire list will be executed.
Regards Renar Renar Grunenberg Abteilung Informatik – Betrieb HUK-COBURG Bahnhofsplatz 96444 Coburg Telefon: 09561 96-44110 Telefax: 09561 96-44104 E-Mail: [email protected] Internet: www.huk.de ======================================================================= HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021 Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin. Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas. ======================================================================= Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet. This information may contain confidential and/or privileged information. If you are not the intended recipient (or have received this information in error) please notify the sender immediately and destroy this information. Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden. ======================================================================= -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Jonathan Buzzard Gesendet: Donnerstag, 21. Juni 2018 09:33 An: [email protected] Betreff: Re: [gpfsug-discuss] mmbackup issue 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 _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
