Showing posts with label DFSR. Show all posts
Showing posts with label DFSR. Show all posts

27 August, 2012

Who Is Responsible For Read Only Connection In DFSR On Windows 2008 R2

Now since enough discussion has been done on Read Only Connections in DFSR on Windows 2008 R2, I am sure you all would like to know who is responsible of making this happen...
Lets start this Journey.....

So, We have 2 Servers involved in Replication. One Server (MyRODC) has a Read Only Connection


Proof???? Again

OK... See.... I am trying to create a file on the server in the RF "Two Way data" and getting Access Denied... Happy now :)


FLTMC - Utility to Load/Unload/Display MiniFilter drivers


FLTMC - Showing the minifilter Drivers installed on this Server....

DfsrRo.Sys - This is the driver which is responsible for creating Read Only Connections


Proof????

I am going to unload this driver by using the command FLTMC.Exe UnLoad DfsrRo


Done...

Now running the FLTMC Command doesn't displays the DfsrRo.Sys as it has been Unloaded


And Yes... Now I am able to create file/folders in the same folder where I was earlier unable to create any File/Folder... Reason??? (U still need one???)


Loading the DfsrRo.Sys Driver Again by running the Command FLTMC.Exe Load DfsrRo



And again.... I am unable to create a file/folder in that folder.... :)

Want to Change Read Only to Read Write in DFSR??? (Read This...)

I can confidently say that this is one of my best Post...

Reason? Guys you asks so many questions... Anyways... I have to answer.... As if I have an option :(

One of the Best Post because usually the other posts just involves recreating the environment... They do not involve much of thinking... But for this post I had to think a lot...

In my earlier two posts, I discussed about how to change a connection from read Only to Read Write and Vice Versa... Even though there is an option to do so and we have seen in those posts that it works like a charm, but then.... There is a Flaw...

Let`s try to discover what`s there behind that option... Why should`nt we choose that way to change the connection type... WHY

Lab

1. One Writable Domain Controller - MyDC
2. One Read Only Domain Controller - MyRODC

3. One Replication Group - Two Way Replication
4. One Replicated Folder - Two Way Data

Currently, we have a RG named Two Way Replication which has a RF named Two Way Data. The RG consist of two servers involved in Replication - MyDC and MyRODC


I have created a file on the server MyDC


And the file is replicated on the other server MyRODC


We have got the Event ID 4112 on the server "MyDC" which was designated as Primary


On the other server, we got Event ID 4102 and 4104 stating that the Initial Replication has been completed



Now making a Move.... Changing the Connection Type from Read-Write to Read Only


Actually, to show what I want to, I have to stop DFSR Service on the other Server... My Apologies Friends :)


The connection has been made "Read Only"


AND.... I created a file on the other server "MyRODC"


The file hasn't got replicated on to the other "MyDC" as the DFSR sservice was stopped on the other server "MyRODC" where I have created the file


Starting the DFSR service on MyRODC


Hey...... Look at this.... OMG.... Where is my file????? Am I on the right server????
Yes I am... :(.... My Poor File.....


And the file is not even on the other server "MyDC"... I know I know... U must be saying if the file is not on the server where it was created and the file hasn't replicated so this is quite obvious....huh


Checking ConflictAndDeleted Folder on MyRODC... Empty


Ahhh..... I found my file.... Its here... here????

Now what the hell this file is doing in Pre-Existing.... Strange... A file/folder is moved into Pre-Existing when the server is in Non-Authoritative State.... Something fishy here....


On the Primary Server, we still have only one 4112


But what`s this.... This time on the other server "MyRODC", we have another set of 4102/4104....hmmm



THE BOTTOM LINE OF THIS STORY

Guys.... Remember this.... When you change the Connection Type from Read Only to Read Write or Vice Versa, the Server becomes Non-Authoritative....

That`s why I said in my earlier post... Please make sure you take backup from both the servers (upstream and downstream) before making this change... Else

Get ready to Loose your DATA... :)

Changing Two Way Replication to One Way in DFSR on RODC

In my earlier post, we discussed about how to configure One-Way Replication and Two-Way Replication in DFSR on Windows m2008 R2 Server (Even though the post were related to RODC, but they do apply the same even on a writable domain controllers)

Configuring One Way Replication in RODC
http://www.adshotgyan.com/2012/07/configuring-one-way-replication-in-rodc.html

Configuring Two Way Replication in RODC
http://www.adshotgyan.com/2012/08/configuring-two-way-replication-in-rodc.html

In this post, we will dicuss what if we want to change Two way replication (Already configured) to a One Way Replication

So Guys.... What are we waiting for.... Let`s get started :)

Lab

1. One Writable Domain Controller - MyDC
2. One Read Only Domain Controller - MyRODC

3. One Replication Group - Two Way Replication
4. One Replicated Folder - Two Way Data

Currently, we have a RG named Two Way Replication which has a RF named Two Way Data. The RG consist of two servers involved in Replication - MyDC and MyRODC


Looking at the Volume_.XML File on the server "MyDC", We can clearly see that the server MyDC for the RF "One Way Data" has a writable connection since its ReadOnly Attribute in the XML file is set to FALSE



Also, looking at the Volume_.XML File on the server "MyRODC", We can see that the server MyRODC for the RF "One Way Data" has a Read Only connection since its ReadOnly Attribute in the XML file is set to FALSE



Let`s the game begin....

We are now going to change the connection from Read Write to Read Only for the Server "MyRODC" for the RF "Two Way Data"



Done...



I know... As usual, You don't believe me.... You want a Proof?

Let`s go into the XML File on MyRODC and Lets check the value of "ReadOnly" attribute (Remember this value was earlier set to FALSE as this connection was Read Write)


Cool... So the RedOnly Attribute is Set to TRUE... Which means, this connection is Read Only


U still dont trust me... (Trust... hmm.... Its really tough to trust somebody....Just trust yourself...)

Coming back to DFSR :)

To prove my point, let me try to create a file in the folder which is now Read Only on the Server MyRODC

YES.... Again... RHS=LHS (I am unable to create a file since the folder is Read Only)


WAIT.... If you think that its over, then you are mistaken.... You have made a mistake in the above configuration, now rectify it by reading the following post... (Skip Reading this Post if you can afford to loose your data :))

Want to Change Read Only to Read Write in DFSR??? Really???
http://www.adshotgyan.com/2012/08/want-to-change-read-only-to-read-write.html

Changing One Way Replication to Two Way in DFSR on RODC

In my earlier post, we discussed about how to configure One-Way Replication and Two-Way Replication in DFSR on Windows m2008 R2 Server (Even though the post were related to RODC, but they do apply the same even on a writable domain controllers)

Configuring One Way Replication in RODC
http://www.adshotgyan.com/2012/07/configuring-one-way-replication-in-rodc.html

Configuring Two Way Replication in RODC
http://www.adshotgyan.com/2012/08/configuring-two-way-replication-in-rodc.html

In this post, we will dicuss what if we want to change One way replication (Already configured) to a Two Way Replication

So Guys.... What are we waiting for.... Let`s get started :)

Lab

1. One Writable Domain Controller - MyDC
2. One Read Only Domain Controller - MyRODC

3. One Replication Group - One Way Replication
4. One Replicated Folder - One Way Data

Currently, we have a RG named One way Replication which has a RF named One Way Data. The RG consist of two servers involved in Replication - MyDC and MyRODC


Looking at the Volume_.XML File on the server "MyDC", We can clearly see that the server MyDC for the RF "One Way Data" has a writable connection since its ReadOnly Attribute in the XML file is set to FALSE



Whereas looking at the Volume_.XML File on the server "MyRODC", We can see that the server MyRODC for the RF "One Way Data" has a Read Only connection since its ReadOnly Attribute in the XML file is set to TRUE


Let`s the game begin....

We are now going to change the connection from Read Only to Read Write for the Server "MyRODC" for the RF "One Way Data"


Done...



I know... As usual, You don't believe me.... You want a Proof?

So let me create a file on MyRODC and since this has been now set as "Read Write", it should allow me to create a file which it did not allowed earlier as it was "Read Only" (Configuring One Way Replication in RODC: http://www.adshotgyan.com/2012/07/configuring-one-way-replication-in-rodc.html)


Yupiiiiiiiii...... Hence Proved (RHS = LHS)....:)


And my dear file got replicated to the other server....



WAIT.... If you think that its over, then you are mistaken.... You have made a mistake in the above configuration, now rectify it by reading the following post... (Skip Reading this Post if you can afford to loose your data :))

Want to Change Read Only to Read Write in DFSR??? Really???
http://www.adshotgyan.com/2012/08/want-to-change-read-only-to-read-write.html