Hi,
Fellow networkers, i have moved on from backup duties to mostly storage duties
and another company, on your question on DFS
DFS is a microsoft implementation of publishing the share name that the users
connect to i.e \\ad\nas\sharename, on the DFS domian implementation server the
\\ad\nas\sharename has pointer to real file system, i.e \\filername\sharename,
therefore it directs the traffic coming to \\ad\nas\sharename , share to actual
phisical storage behind it ( NAS Filer or servershare).
The main reason to do DFS link is to isolate users from phsical server links,
so in future if a nas filer or server is retired updating the DFS link would
sheild the users from remaping the drive or changing scripts and no disruption
could be noticed by the end users.
In the past we did not backup remote filesystem via networker, unless
absulutely needed, i.e the filer itself should be backed up not the shares
being mapped on each server , that way ther performance and indexing is
relavent.
There should be no need to backup mapped drives on windows servers unless there
is a business reason, that is my openion.
Hope that helps
Fazil Saiyed
> Date: Tue, 3 Apr 2012 15:00:51 -0400
> From: Michael.Leone AT PHA.PHILA DOT GOV
> Subject: Re: [Networker] Windows DFS Junction warning messages
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>
> We haven't (yet) implemented DFS yet, but my understanding is:
>
> > I'm not a Windows guy, so I have to believe there's something going on
> > here that I don't understand. Why is it warning me about DFS
> mountpoints
> > on the Windows system? Is it that
> >
> > - DFS mountpoints work more like a symlink, in that the data actually
> > resides elsewhere on the system but it's presented to the user or
> > client system as if it was under K:?
>
> Yes. You define a DFS namespace, and then mount the volume into that name
> space. And the volume can come from non-local machines.
>
> Hence you can have a DFS namespace "Users", which does *not* have to be
> defined on one server; multiple servers can see it.
>
> And you can mount volumes from multiple non-local servers under it.
>
> So you define a DFS namespace "Users". And in there you mount drive H:
> from Server-#1, and drive G: from Server-#2, etc.
>
> And it all shows up as "\Users", for whatever clients have access to that
> namespace ...
>
> > or
> >
> > - DFS mountpoints are considered non-local volumes, akin to an NFS mount
> > on UNIX/Linux?
>
> AFAIK, yes. From NW's point of view, apparently.
>
> > Anyone care to clarify what's going on here?
> >
> > Thanks,
> >
> > Tim
> > --
> > Tim Mooney Tim.Mooney AT ndsu DOT edu
> > Enterprise Computing & Infrastructure 701-231-1076
> (Voice)
> > Room 242-J6, IACC Building 701-231-8541
> (Fax)
> > North Dakota State University, Fargo, ND 58105-5164
> >
> > To sign off this list, send email to listserv AT listserv.temple DOT edu
> > and type "signoff networker" in the body of the email. Please write
> > to networker-request AT listserv.temple DOT edu if you have any problems
> > with this list. You can access the archives at http://
> > listserv.temple.edu/archives/networker.html or
> > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with
> this list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|