If you backup to a different nodename you will reset the CBT info. So you can
do that monthly full backup to the different nodename, but when you switch back
to the original, it will also require a full. So in essence you need to do 2
back to back fulls to get this done. I've been down this road
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.
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
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
back
