Hi Mike,

thanks for the link, I'll look into it. One thing I can add is that there is, 
or should be, in fact only one target, so every time my client connects it 
should effectively connect to the same share on the same device. It is worth 
looking into though. I'll ask the sysadmin.

Op 19 mrt. 2014, om 13:14 heeft Ryder, Michael S <michael_s.ryder AT ROCHE DOT 
COM> het volgende geschreven:

> Remco
> 
> The first thing that comes to mind is that when it fails, the backup client
> is connecting to a namespace's remote folder target remote DFS share that
> has an exclusion that prevents connection.
> 
> For example, there could be Share permissions on that remote folder target
> that exclude connection by your TSM client computer... or a referral
> override that places the desired target at a lower priority.
> 
> Each time the TSM client computer connects to this DFS share, unless it is
> cached and current, it is directed to the most appropriate folder target
> based on a number of factors.
> 
> Here's a link that explains how DFS works, which may shed some light on the
> problem - look for the section entitled "How Target Selection Works" in
> http://technet.microsoft.com/en-us/library/cc782417(v=WS.10).aspx
> 
> Best regards,
> 
> Mike, x7942
> RMD IT Client Services
> 
> 
> On Wed, Mar 19, 2014 at 5:41 AM, Remco Post <r.post AT plcs DOT nl> wrote:
> 
>> Hi all,
>> 
>> I have a customer who insists on backing up a few shares via DFS.
>> Sometimes the DFS seems to work, but quite frequently we get messages like:
>> 
>> ANS1071E Invalid domain name entered '\\domain\root\share'
>> 
>> does anyone have a clue as to what might be causing the DFS shares to
>> sometimes backup perfectly, and sometimes just appear to be completely
>> absent from the entire domain?
>> 
>> --
>> 
>> Met vriendelijke groeten/Kind Regards,
>> 
>> Remco Post
>> r.post AT plcs DOT nl
>> +31 6 248 21 622
>> 

-- 

 Met vriendelijke groeten/Kind Regards,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622