Just when you think you've covered the good majority of content for an exam objective...
Having cleared down DFS over two servers in my home lab, I;
1. Created a brand-new, domain-based namespace
2. Created a folder structure (3 separate work department folders)
3. Linked a folder target for each of those respective folders
4. Created a replication group to sync the contents of the folder targets, between both DFS servers
5. Designated the second DFS server as an additional namespace server for fault tolerance
I was able to access the namespace from another member server with no issue.
I then disabled the NIC on one of the DFS boxes, fully expecting to be able to access the namespace with no issues, after providing fault tolerance in the form of the second box being a namespace server.
I found I could access the root of the namespace, and was able to view the folder structure, but when accessing each of those folders, explorer hung before eventually stating that the folders couldn't be accessed. 'Why hasn't the second namespace server allowed me to view the contents of the namespace when one of the DFS servers is down?', I asked myself.
So after enabling the card again for the first server, all was good again.
I then realised that despite ensuring that folder contents have been synced across both servers, that when reviewing the folder targets for each of the top level department folders, I hadn't actually added in the target for the same data on the second DFS server.
My question is, when configuring folder targets for a top-level folder in the hierarchy, is there any clever way of making sure for each namespace server, that the folder is linked to each copy of the same data that is hosted across X no. of DFS servers? Not sure how DFS could do this!
Or, is it just a case of manually ensuring that each 'top-level' folder as it were, is linked to all the possible folders containing the correct data, across each server?
Have I missed something in my study? Just thinking of the implications if I were to repeat such a thing again, in production..!
Many thanks.
Having cleared down DFS over two servers in my home lab, I;
1. Created a brand-new, domain-based namespace
2. Created a folder structure (3 separate work department folders)
3. Linked a folder target for each of those respective folders
4. Created a replication group to sync the contents of the folder targets, between both DFS servers
5. Designated the second DFS server as an additional namespace server for fault tolerance
I was able to access the namespace from another member server with no issue.
I then disabled the NIC on one of the DFS boxes, fully expecting to be able to access the namespace with no issues, after providing fault tolerance in the form of the second box being a namespace server.
I found I could access the root of the namespace, and was able to view the folder structure, but when accessing each of those folders, explorer hung before eventually stating that the folders couldn't be accessed. 'Why hasn't the second namespace server allowed me to view the contents of the namespace when one of the DFS servers is down?', I asked myself.
So after enabling the card again for the first server, all was good again.
I then realised that despite ensuring that folder contents have been synced across both servers, that when reviewing the folder targets for each of the top level department folders, I hadn't actually added in the target for the same data on the second DFS server.
My question is, when configuring folder targets for a top-level folder in the hierarchy, is there any clever way of making sure for each namespace server, that the folder is linked to each copy of the same data that is hosted across X no. of DFS servers? Not sure how DFS could do this!
Or, is it just a case of manually ensuring that each 'top-level' folder as it were, is linked to all the possible folders containing the correct data, across each server?
Have I missed something in my study? Just thinking of the implications if I were to repeat such a thing again, in production..!
Many thanks.