Jon,
We only used Exclude.dir statements. Here is a small example of those 
enviroments.

\\Server1\DFSROOT
\\Server1\Software\
\\Server2\Software\

In the case above we replicated the software install folder.  On Server1 we 
backed up the entire thing.  On server2 the software folder was on F:\Software. 
 So for the dsm.opt on Server2 we have exclude.dir F:\Software.

Modifying your domain statement should only need to be done if you have an 
entire drive that you do not want to back up.  Also the system state will be 
backed up with all-local unless you add -systemstate (ex. ALL-LOCAL 
-SYSTEMSTATE).

Also remember one other thing on the server that you have your DFSRoot on you 
had to create a share for that DFSRoot.  Under it you will also see the DFS 
Links. If you try to click on any of these folders in Windows explorer you 
should get an access denied message.  Based on what you said below I'm 
wondering if you are seeing these folders get backed up and are thinking it is 
backing up all the data under the link. Backing up these folders should not 
result in the entire DFS link being backed up.

Jon Adams <Jon.Adams AT PREMERA DOT COM> wrote:
Absolutely, we are using DFS replication, so our intent is not to backup
each of the DFS links. What is the best way to have TSM do that? After
talking with technical support, it seems as though you need to use a
modified DOMAIN statement and an EXCLUDE.DIR in tandem in order to avoid
having a DFS backed up. Is there a way to use one or the other to
accomplish the same thing? The subdirectories under the DFS root
(E:\DFS\ENTDFS01) point to shares on the same system; specifically the MSI
directory under the DFS root uses a share that resolves to E:\DSF\MSI.
Currently the DOMAIN statement has "C: D: E:" and the EXCLUDE.DIR has
E:\DFS. One of the things I noticed is that the DOMAIN statement now
excludes the system state and system services, which are typically covered
with the ALL-LOCAL value. Should I be able to use the default ALL-LOCAL for
the DOMAIN and the EXCLUDE.DIR to accomplish this? Thanks for your help.

Through TSM support, we also noted that DOMAIN statements are cumulative.
So, a DOMAIN statement in the client options set and one in the dsm.opt work
in tandem. We're wondering if that is causing some conflict here as well.

Thanks for the note about backing up the DFS root. I'll work on that
shortly after this issue is resolved.


___________________________
With regards,

- Jon

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
TSM_User
Sent: Wednesday, August 18, 2004 3:22 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM, Windows and DFS

You say you are trying to exclude the DFS shares for obviouse reasons.
There isn't any obviouse reasons to me. It is real user data that should be
backed up. Now if you are using DFS replication and what you mean is you
don't want to back data in a DFS link that is a replica of data somewhere
else then send us the path name for the folder that is shared. Then send us
your exclude that you think doesn't work.

I have set up multiple large Server based and active directory based DFS
roots. I have done this with both Windows 2000 and Windows 2003. In all
cases we were using TSM to backup the data. In many cases the DFS Root was
on one of the file servers. The data itself was on multiple file servers as
you would expect with DFS. Each server had a TSM client and each client was
expected to backup all of the data on the server it was running on. We only
excluded shares that were linked to through DFS when they were a replica of
data that was somewhere else. For those we did have excludes on the file
servers were the replica's were so that we did not back up that data twice.

On a side note one extra thing we did was use the DFSCMD to backup the DFS
root and links as documented by MS. Here is a sample of what we did.

DFSCMD /VIEW \\ad.corp1.com\Root1 /BATCH >> "C:\DFSBackup\DFSRestore.bat"

Jon Adams wrote:
This would be the DFS shares on the target clients.


___________________________
With regards,

- Jon

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
TSM_User
Sent: Tuesday, August 17, 2004 6:53 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM, Windows and DFS

Are you talking about the server with the DFS Root and the DFS links? Or do
you mean the server that the shares are on? If the shares are being backed
up via another system then it might be that someone manaully backed it up
while the links were mapped.

More clarification please?


Jon Adams wrote:
Anyone have anything on TSM and Windows DFS? We're trying to exclude the DFS
shares (for obvious reason) and not having any luck. Interestingly enough,
we get this when querying includes/excludes, but can find no documentation
that states how you would provide a DFS include/exclude:

Excl All *\Pagefile.sys Operating System Excl All *\hiberfil.sys Operating
System Excl All *\...\*.crmlog Operating System No DFS include/exclude
statements defined.


With regards,
_______________________________________________

Jon R. Adams
Systems Engineer II
Infrastructure Technical Support, OSS
Premera Blue Cross
Work: 425-918-5770 / mailto:jon.adams AT premera DOT com



"There are only 10 kinds of people in this world - those that know binary
and those that do not."

-author unknown


---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!


---------------------------------
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!


---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!