Before reading this article, you should read the above attached article to get the basic understanding about "DFS Replication Database Cloning". If you any questions regarding this article, please let me know. But make sure, your doubts should be clear before going further.
Cloning database can cause some problems when you have multiple Replicated Folders on a volume. Lets say, you have volume by the name of "Department" and on it you Replicated Folders like: Finance, Sales and Marketing and you are going to create one more Replicated Folder by the name "HR". Hope this small example make sense about multiple Replicated Folders on a single volume.
Here is the scenario to make you more understand with help of above example. You have three servers in your organisation, Server1, Server2, and Server3. Replicated Folders "Finance", "Sales", "Marketing" and "HR" already available on Server1 and Server2. Even on Server3, "Finance", "Sales" and "Marketing" are also there and in sync with Server1 and Server 2 but you need to add "HR" now on Server3. It means, you will first robocopy entire "HR" folder from Server1/Server2 to Server3 and then import replication database.
As per my first article about Database Cloning, i will export the replication database from Server1 as all replicated folders of the volume are in Normal state. While exporting i don't have much to do and i will end-up with the complete clone of the replication database and a configuration xml file from Server. In short, the replication database which i got after run the command, it belongs to all Replicated folders of the same volume. But i am in process to work only on "HR" folder and i don't want other Replicated Folders to be impacted.
I apologize to make it little lengthy, i just want you to make clear about the situation and scenario. Now here is the solution.
0 comments:
Post a Comment