Hi Rick, 

Yes, we have it explicitly YES. If it is NO, TSM gives an error message. If it 
is YES, TSM backs up the first file of the conflicting "group" and logs a 
warning for the other ones (they are not backed up).

Met vriendelijke groet / With kind regards,

Paul van Dongen


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Rick Harderwijk
Sent: Monday, May 06, 2013 15:04
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM client vs Windows SFU

Paul,

CASESENSITIVEAWARE default value is NO (as per 
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r2/index.jsp?topic=%2Fcom.ibm.itsm.client.doc%2Fr_opt_casesensitiveaware.html
),
so the option should explicitly be set to YES, I understand from that document. 
Is the option explicitly set to YES in the dsm.opt ?

Kind regards,

Rick


On Mon, May 6, 2013 at 2:20 PM, Paul van Dongen <Paul.vanDongen AT vancis DOT 
nl>wrote:

> Hi TSMers,
>
> I am once more try to make use of your combined knowledge to answer a 
> question that I could not.
>
> We have a few new Windows Servers that are, amongst other things, used 
> to export NFS shares. The administrators of these servers have 
> activated a setting that allows Windows to create two files with 
> almost identical names differing only in case (the whole POSIX 
> stuff...). Now they want to backup these file servers with TSM, but 
> the client refuses to backup files whose name differs only in case. I 
> have already told them about the CASESENSITIVEAWARE option, but this 
> has only the effect of making TSM back up the first file with a 
> "conflicting" name. Of course the admins want to backup ALL files.
>
> Has any of you seen/used a better way to back up this kind of 
> configuration?
>
> BTW, the clients are Windows 2008R2 and they run TSM client 6.4.0.1
>
>
> Thank you all.
>
> Met vriendelijke groet / With kind regards, Paul van Dongen System 
> Expert Cloud Strategy
>