Could you do something really nasty in the tsm db2 database to update the paths?
-----Original Message----- From: Sobey, Richard A [[email protected]<mailto:[email protected]>] Sent: Wednesday, May 04, 2016 04:35 PM GMT Standard Time To: gpfsug main discussion list Subject: Re: [gpfsug-discuss] TSM and re-linked filesets A quick Google has given me the answer I dreaded: “Attention: If you are using the TSM Backup-Archive client you must use caution when you unlink filesets that contain data backed up by TSM. TSM tracks files by pathname and does not track filesets. As a result, when you unlink a fileset, it appears to TSM that you deleted the contents of the fileset. Therefore, the TSM Backup-Archive client inactivates the data on the TSM server which may result in the loss of backup data during the expiration process.” So I need to relink it to the original place I think. Oh well. Not a disaster. From: [email protected] [mailto:[email protected]] On Behalf Of Sobey, Richard A Sent: 04 May 2016 16:33 To: '[email protected]' <[email protected]> Subject: [gpfsug-discuss] TSM and re-linked filesets This is more a TSM question than GPFS but it involves GPFS to a point so I hope I’m ok asking this. I’ve unlinked a fileset and relinked it at a different junction point. Will this cause TSM to see a “new” fileset and back up all its content? This is very undesireable so if I need to put it back where it belongs then I need to do this before tonight. GPFS 3.5 and TSM 7.1. Does anyone know? Cheers Richard
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
