[gpfsug-discuss] mmbackup and filenames

[Simon Thompson (Research Computing - IT Services)]

Hi Mark,

I appreciate its a limitation of the TSM client, but Scale (IBM product) and Protect (IBM product) and preferred (?) method of backing it up ...

I agree with Kevin that given the push for protocol support, and people will use filenames like this, IBM need to get it fixed.

Who should we approach at IBM as a user community to get this on the TSM fix list?

Simon
________________________________
From: gpfsug-discuss-bounces at spectrumscale.org [gpfsug-discuss-bounces at spectrumscale.org] on behalf of Marc A Kaplan [makaplan at us.ibm.com]
Sent: 20 April 2016 15:42
To: gpfsug main discussion list
Subject: Re: [gpfsug-discuss] mmbackup and filenames

The problem is that the Tivoli Storage Manager (Ahem Spectrum Protect) Filelist option has some limitations:

http://www.ibm.com/support/knowledgecenter/SS8TDQ_7.1.0/com.ibm.itsm.client.doc/r_opt_filelist.html<redir.aspx?REF=H1bgEVvFvlmCZJq3yvK1wr3auPxTbF-E-9vDxSgocOrAyVAJLmnTCAFodHRwOi8vd3d3LmlibS5jb20vc3VwcG9ydC9rbm93bGVkZ2VjZW50ZXIvU1M4VERRXzcuMS4wL2NvbS5pYm0uaXRzbS5jbGllbnQuZG9jL3Jfb3B0X2ZpbGVsaXN0Lmh0bWw.>

...
The files (entries) listed in the filelist must adhere to the following rules:

  *   Each entry must be a fully-qualified or a relative path to a file or directory. Note that if you include a directory in a filelist entry, the directory is backed up, but the contents of the directory are not.
  *   Each path must be specified on a single line. A line can contain only one path.
  *   Paths must not contain control characters, such as 0x18 (CTRL-X), 0x19 (CTRL-Y) and 0x0A (newline).
  *   By default, paths must not contain wildcard characters. Do not include asterisk (*) or question marks (?) in a path. This restriction can be overridden if you enable the option named ... AND SO ON...


IF TSM would implement some way of encoding or "escaping" special characters in filelists, we would happily fix mmbackup !
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160420/7a35c264/attachment.htm>