File Availability
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
File Availability

 
Post new topic   Reply to topic    Windows Server Forum Index -> DFS and FRS
Author Message
Dawn NM
Guest





Posted: Wed Oct 13, 2004 1:51 am    Post subject: File Availability Reply with quote

I have a DFS pair that I have set up, so that each server has a root target
and also hosts link targets.

I.e.
Server 1: rootA, linkA, linkB
Server 2: rootB, linkA, linkB

Let's suppose there are two clients, and client1 writes a file to linkA. It
is my understanding that clientA could be pointed to rootA, linkA and clientB
could be pointing to rootB, linkA.

Does clientB have to wait until the file is replicated to rootB, linkA
before they can see the file, or will they be "repointed" to rootA?

Thanks,

Dawn
Back to top
Jill Zoeller [MSFT]
Guest





Posted: Wed Oct 13, 2004 9:03 pm    Post subject: Re: File Availability Reply with quote

DFS doesn't keep track of whether replication has completed to LinkA on each
server. So it is possible that a client could end up on a target that hasn't
fully replicated. Disabling the referral to that target is one way to
prevent clients from accessing it until the files are completely replicated.

If you want to learn more about the DFS referral process, see "How DFS
Works" in the DFS Technical Reference link on www.microsoft.com/dfs.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Dawn NM" <DawnNM@discussions.microsoft.com> wrote in message
news:BD9D2C2E-85EC-4A76-B3AB-21C37A8C3C19@microsoft.com...
Quote:
I have a DFS pair that I have set up, so that each server has a root target
and also hosts link targets.

I.e.
Server 1: rootA, linkA, linkB
Server 2: rootB, linkA, linkB

Let's suppose there are two clients, and client1 writes a file to linkA.
It
is my understanding that clientA could be pointed to rootA, linkA and
clientB
could be pointing to rootB, linkA.

Does clientB have to wait until the file is replicated to rootB, linkA
before they can see the file, or will they be "repointed" to rootA?

Thanks,

Dawn
Back to top
Dawn NM
Guest





Posted: Wed Oct 13, 2004 9:13 pm    Post subject: Re: File Availability Reply with quote

So if clientA places a file, and clientB is looking at the other target,
clientB will not see the file until it has been completely replicated?

Thanks,

Dawn

"Jill Zoeller [MSFT]" wrote:

Quote:
DFS doesn't keep track of whether replication has completed to LinkA on each
server. So it is possible that a client could end up on a target that hasn't
fully replicated. Disabling the referral to that target is one way to
prevent clients from accessing it until the files are completely replicated.

If you want to learn more about the DFS referral process, see "How DFS
Works" in the DFS Technical Reference link on www.microsoft.com/dfs.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Dawn NM" <DawnNM@discussions.microsoft.com> wrote in message
news:BD9D2C2E-85EC-4A76-B3AB-21C37A8C3C19@microsoft.com...
I have a DFS pair that I have set up, so that each server has a root target
and also hosts link targets.

I.e.
Server 1: rootA, linkA, linkB
Server 2: rootB, linkA, linkB

Let's suppose there are two clients, and client1 writes a file to linkA.
It
is my understanding that clientA could be pointed to rootA, linkA and
clientB
could be pointing to rootB, linkA.

Does clientB have to wait until the file is replicated to rootB, linkA
before they can see the file, or will they be "repointed" to rootA?

Thanks,

Dawn


Back to top
Jill Zoeller [MSFT]
Guest





Posted: Wed Oct 13, 2004 10:39 pm    Post subject: Re: File Availability Reply with quote

Correct. DFS has no knowledge of the data that's actually on the target.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dawn NM" <DawnNM@discussions.microsoft.com> wrote in message
news:0B6D3192-2F6E-4882-A98D-3AE33C4A898A@microsoft.com...
Quote:
So if clientA places a file, and clientB is looking at the other target,
clientB will not see the file until it has been completely replicated?

Thanks,

Dawn

"Jill Zoeller [MSFT]" wrote:

DFS doesn't keep track of whether replication has completed to LinkA on
each
server. So it is possible that a client could end up on a target that
hasn't
fully replicated. Disabling the referral to that target is one way to
prevent clients from accessing it until the files are completely
replicated.

If you want to learn more about the DFS referral process, see "How DFS
Works" in the DFS Technical Reference link on www.microsoft.com/dfs.

--
This posting is provided "AS IS" with no warranties, and confers no
rights.


"Dawn NM" <DawnNM@discussions.microsoft.com> wrote in message
news:BD9D2C2E-85EC-4A76-B3AB-21C37A8C3C19@microsoft.com...
I have a DFS pair that I have set up, so that each server has a root
target
and also hosts link targets.

I.e.
Server 1: rootA, linkA, linkB
Server 2: rootB, linkA, linkB

Let's suppose there are two clients, and client1 writes a file to
linkA.
It
is my understanding that clientA could be pointed to rootA, linkA and
clientB
could be pointing to rootB, linkA.

Does clientB have to wait until the file is replicated to rootB, linkA
before they can see the file, or will they be "repointed" to rootA?

Thanks,

Dawn


Back to top
Dawn NM
Guest





Posted: Thu Oct 14, 2004 12:39 am    Post subject: Re: File Availability Reply with quote

Thank you. One of my co-workers was arguing that you would be "sent" to the
server with the data on it because somehow DFS knows where the most recent
data is kept. Thanks for provinding a concrete answer.

"Jill Zoeller [MSFT]" wrote:

Quote:
Correct. DFS has no knowledge of the data that's actually on the target.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dawn NM" <DawnNM@discussions.microsoft.com> wrote in message
news:0B6D3192-2F6E-4882-A98D-3AE33C4A898A@microsoft.com...
So if clientA places a file, and clientB is looking at the other target,
clientB will not see the file until it has been completely replicated?

Thanks,

Dawn

"Jill Zoeller [MSFT]" wrote:

DFS doesn't keep track of whether replication has completed to LinkA on
each
server. So it is possible that a client could end up on a target that
hasn't
fully replicated. Disabling the referral to that target is one way to
prevent clients from accessing it until the files are completely
replicated.

If you want to learn more about the DFS referral process, see "How DFS
Works" in the DFS Technical Reference link on www.microsoft.com/dfs.

--
This posting is provided "AS IS" with no warranties, and confers no
rights.


"Dawn NM" <DawnNM@discussions.microsoft.com> wrote in message
news:BD9D2C2E-85EC-4A76-B3AB-21C37A8C3C19@microsoft.com...
I have a DFS pair that I have set up, so that each server has a root
target
and also hosts link targets.

I.e.
Server 1: rootA, linkA, linkB
Server 2: rootB, linkA, linkB

Let's suppose there are two clients, and client1 writes a file to
linkA.
It
is my understanding that clientA could be pointed to rootA, linkA and
clientB
could be pointing to rootB, linkA.

Does clientB have to wait until the file is replicated to rootB, linkA
before they can see the file, or will they be "repointed" to rootA?

Thanks,

Dawn





Back to top
TK
Guest





Posted: Thu Oct 14, 2004 2:36 pm    Post subject: Re: File Availability Reply with quote

Jill,
Won't disabling the referral also cancel out any fault tolerance since the
target will no longer appear to the Client computer requesting the file in
question?
TK

"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:eylm74TsEHA.3604@TK2MSFTNGP15.phx.gbl...
Quote:
DFS doesn't keep track of whether replication has completed to LinkA on
each
server. So it is possible that a client could end up on a target that
hasn't
fully replicated. Disabling the referral to that target is one way to
prevent clients from accessing it until the files are completely
replicated.

If you want to learn more about the DFS referral process, see "How DFS
Works" in the DFS Technical Reference link on www.microsoft.com/dfs.

--
This posting is provided "AS IS" with no warranties, and confers no
rights.


"Dawn NM" <DawnNM@discussions.microsoft.com> wrote in message
news:BD9D2C2E-85EC-4A76-B3AB-21C37A8C3C19@microsoft.com...
I have a DFS pair that I have set up, so that each server has a root
target
and also hosts link targets.

I.e.
Server 1: rootA, linkA, linkB
Server 2: rootB, linkA, linkB

Let's suppose there are two clients, and client1 writes a file to linkA.
It
is my understanding that clientA could be pointed to rootA, linkA and
clientB
could be pointing to rootB, linkA.

Does clientB have to wait until the file is replicated to rootB, linkA
before they can see the file, or will they be "repointed" to rootA?

Thanks,

Dawn

Back to top
Jill Zoeller [MSFT]
Guest





Posted: Thu Oct 14, 2004 8:52 pm    Post subject: Re: File Availability Reply with quote

If there are only two targets, and you disable a referral to one, then yes,
fault tolerance is gone if the "referralled" server goes down. The
administrator would need to manually enable the referral to the other
server. In essence, disabling referrals allows you to control whether users
access one of the servers, such as a hot standby or a server that doesn't
hold the complete data set yet. The downside is that you need to take some
immediate action if one of the servers goes down.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"TK" <sprdthword@hotmail.com> wrote in message
news:%23c$cIFdsEHA.3200@TK2MSFTNGP09.phx.gbl...
Quote:
Jill,
Won't disabling the referral also cancel out any fault tolerance since the
target will no longer appear to the Client computer requesting the file in
question?
TK

"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:eylm74TsEHA.3604@TK2MSFTNGP15.phx.gbl...
DFS doesn't keep track of whether replication has completed to LinkA on
each
server. So it is possible that a client could end up on a target that
hasn't
fully replicated. Disabling the referral to that target is one way to
prevent clients from accessing it until the files are completely
replicated.

If you want to learn more about the DFS referral process, see "How DFS
Works" in the DFS Technical Reference link on www.microsoft.com/dfs.

--
This posting is provided "AS IS" with no warranties, and confers no
rights.


"Dawn NM" <DawnNM@discussions.microsoft.com> wrote in message
news:BD9D2C2E-85EC-4A76-B3AB-21C37A8C3C19@microsoft.com...
I have a DFS pair that I have set up, so that each server has a root
target
and also hosts link targets.

I.e.
Server 1: rootA, linkA, linkB
Server 2: rootB, linkA, linkB

Let's suppose there are two clients, and client1 writes a file to
linkA.
It
is my understanding that clientA could be pointed to rootA, linkA and
clientB
could be pointing to rootB, linkA.

Does clientB have to wait until the file is replicated to rootB, linkA
before they can see the file, or will they be "repointed" to rootA?

Thanks,

Dawn



Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> DFS and FRS All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB