[gpfsug-discuss] TSM and re-linked filesets

Laurence Horrors-Barlow laurence at qsplace.co.uk
Wed May 4 18:49:31 BST 2016


Hi Richard,

That's correct, TSM will only look at the path and compare files it doesn't understand the file set. Once the path has changed it will then start expiring the missing files.

What are you trying to achieve here as you might be able to update the expiration or fudge the DB.

-- Lauz

Sent from my iPad

> On 4 May 2016, at 16:35, Sobey, Richard A <r.sobey at imperial.ac.uk> wrote:
> 
> 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: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Sobey, Richard A
> Sent: 04 May 2016 16:33
> To: 'gpfsug-discuss at spectrumscale.org' <gpfsug-discuss at spectrumscale.org>
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160504/4e625d03/attachment-0002.htm>


More information about the gpfsug-discuss mailing list