Me too. Sent from my iPhone
> On 20 Apr 2016, at 19:28, Bryan Banister <[email protected]> wrote: > > I voted for this! > -B > > From: [email protected] > [mailto:[email protected]] On Behalf Of Simon Thompson > (Research Computing - IT Services) > Sent: Wednesday, April 20, 2016 10:41 AM > To: gpfsug main discussion list > Subject: Re: [gpfsug-discuss] mmbackup and filenames > > OK, I might have managed to create a public RFE for this: > > https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=87176 > > Simon > From: [email protected] > [[email protected]] on behalf of Bryan Banister > [[email protected]] > Sent: 20 April 2016 16:28 > To: gpfsug main discussion list > Subject: Re: [gpfsug-discuss] mmbackup and filenames > > Well what a lame restriction… I don’t understand why all IBM products don’t > have public RFE options, > -B > > From: [email protected] > [mailto:[email protected]] On Behalf Of Simon Thompson > (Research Computing - IT Services) > Sent: Wednesday, April 20, 2016 10:27 AM > To: gpfsug main discussion list > Subject: Re: [gpfsug-discuss] mmbackup and filenames > > Hm. I can only log a public RFE against Scale ... and this is a change to > Protect ;-) > > Simon > From: [email protected] > [[email protected]] on behalf of Bryan Banister > [[email protected]] > Sent: 20 April 2016 16:19 > To: gpfsug main discussion list > Subject: Re: [gpfsug-discuss] mmbackup and filenames > > The Public RFE process sounds like a good way to go… somebody put it up and > I’ll vote for it! > -B > > From: [email protected] > [mailto:[email protected]] On Behalf Of Simon Thompson > (Research Computing - IT Services) > Sent: Wednesday, April 20, 2016 10:15 AM > To: gpfsug main discussion list > Subject: Re: [gpfsug-discuss] mmbackup and filenames > > 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: [email protected] > [[email protected]] on behalf of Marc A Kaplan > [[email protected]] > 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 > > ... > 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 ! > > > Note: This email is for the confidential use of the named addressee(s) only > and may contain proprietary, confidential or privileged information. If you > are not the intended recipient, you are hereby notified that any review, > dissemination or copying of this email is strictly prohibited, and to please > notify the sender immediately and destroy this email and any attachments. > Email transmission cannot be guaranteed to be secure or error-free. The > Company, therefore, does not make any guarantees as to the completeness or > accuracy of this email or any attachments. This email is for informational > purposes only and does not constitute a recommendation, offer, request or > solicitation of any kind to buy, sell, subscribe, redeem or perform any type > of transaction of a financial product. > > > Note: This email is for the confidential use of the named addressee(s) only > and may contain proprietary, confidential or privileged information. If you > are not the intended recipient, you are hereby notified that any review, > dissemination or copying of this email is strictly prohibited, and to please > notify the sender immediately and destroy this email and any attachments. > Email transmission cannot be guaranteed to be secure or error-free. The > Company, therefore, does not make any guarantees as to the completeness or > accuracy of this email or any attachments. This email is for informational > purposes only and does not constitute a recommendation, offer, request or > solicitation of any kind to buy, sell, subscribe, redeem or perform any type > of transaction of a financial product. > > > Note: This email is for the confidential use of the named addressee(s) only > and may contain proprietary, confidential or privileged information. If you > are not the intended recipient, you are hereby notified that any review, > dissemination or copying of this email is strictly prohibited, and to please > notify the sender immediately and destroy this email and any attachments. > Email transmission cannot be guaranteed to be secure or error-free. The > Company, therefore, does not make any guarantees as to the completeness or > accuracy of this email or any attachments. This email is for informational > purposes only and does not constitute a recommendation, offer, request or > solicitation of any kind to buy, sell, subscribe, redeem or perform any type > of transaction of a financial product. > _______________________________________________ > 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
