Update Workflows/Windows/Windows Server/Roles/DFS/Setting Up DFS Across Multiple File Servers.md
All checks were successful
GitOps Automatic Deployment / GitOps Automatic Deployment (push) Successful in 8s
All checks were successful
GitOps Automatic Deployment / GitOps Automatic Deployment (push) Successful in 8s
This commit is contained in:
@@ -22,7 +22,7 @@ The first step you want to perform is installing the necessary roles on *both se
|
||||
The next step in the process is to ensure that the network shares that will be shared via DFS have sane permissions. You will want to ensure the following minimum permissions are configured.
|
||||
|
||||
!!! warning "Replicate Folders and Permissions Across all File Servers"
|
||||
It is important for you to understand that every member server of the DFS namespaces and replication need to be configured identically, with the same local drive letters and folder structures.
|
||||
It is important for you to understand that every member server of the DFS namespaces and replication need to be configured identically, with the same shared folder structures. To clarify, you can have the underlying files in different locations on-disk, but they need to have the same permissions and paths on the network shares themselves under `\\SERVER\<share$>`
|
||||
|
||||
**NOTE**: The data for the shares only needs to exist on one server to ensure it can be replicated across to the other member servers of the DFS namespaces. During DFS configuration, this server is designated as the "Primary Member". This server's folder contents are treated as authoritative for the initial sync and replicate to the other members of the DFS namespace.
|
||||
|
||||
@@ -42,7 +42,7 @@ At this point, we need to create a DFS "Namespace". This is basically a logical
|
||||
### DFS Configuration
|
||||
Now, we need to start working on actually setting up DFS now that the shares exist (and are configured identically) on all member servers. You can choose to do these steps on any of the member servers, but I recommend using the lowest number server (e.g. `LAB-FPS-01`). The configurations will be automatically replicated across to all member servers from the server you choose to configure, so in reality, it really doesn't matter which server you choose.
|
||||
|
||||
#### Create Namespace(s)
|
||||
#### Create Namespace
|
||||
- Navigate to "**Server Manager > Tools > DFS Management**"
|
||||
- In the left-hand sidebar, right-click "Namespaces" > "**New Namespace...**"
|
||||
- Choose a member server (e.g. `LAB-FPS-01`) then click "**Next**"
|
||||
@@ -54,5 +54,21 @@ Now, we need to start working on actually setting up DFS now that the shares exi
|
||||
- Click "**Next**"
|
||||
- At this point, the namespace was created and you can move onto linking folders to the namespace to make their data appear inside of it and replicate to other member servers.
|
||||
|
||||
#### Link Folders to Namespace(s)
|
||||
At this point, we need to configure
|
||||
#### Link Folders to Namespace
|
||||
At this point, we need to configure folders on every member server to be linked to the namespace we created. In this context, the "Folders" are the subfolders of the network share we want to share and replicate in DFS.
|
||||
|
||||
- Right-click the namespace we just created (e.g. `\\bunny-lab.io\Projects`)
|
||||
- Click on "**New Folder**"
|
||||
- This is the point where we link subfolders to folders inside of the namespace. For example, if we have a folder located at `\\LAB-FPS-01\Projects\Scripting`, the folder name we create here would be named `Scripting`.
|
||||
- Under "Folder Targets" you will click on the "**Add**" button
|
||||
- Browse the "Path to folder target" and navigate to the equivalant location on all member servers, one entry per server:
|
||||
- `\\LAB-FPS-01\Projects$\Scripting`
|
||||
- `\\LAB-FPS-02\Projects$\Scripting`
|
||||
- Click the "**OK**" button
|
||||
- You will be prompted with "*A replication group can be used to synchronize the folder targets of the folder you just created. Do you want to create a replication group?*". You will click the "**Yes**" button and proceed to the next section.
|
||||
- *Be patient, it takes a few seconds to load the replication wizard*
|
||||
|
||||
#### Configure Replication Group
|
||||
As mentioned in the previous section, you clicked "**Yes**" to the automatic replication group wizard and arrived at the replication wizard. Follow the steps below to finalize replication for the share.
|
||||
|
||||
-
|
||||
Reference in New Issue
Block a user