DFS - JadenGil/Jaden-Tech-Journal GitHub Wiki
A DFS (Distributed File System) is a system that allows multiple servers to work together to provide a single, unified file system to users. In a DFS, there are multiple servers that are organized into a hierarchy, with one or more primary servers at the top and one or more secondary servers below them.
When a primary DFS system goes down, the secondary DFS systems are still able to connect because the DFS architecture is designed to be fault-tolerant. The DFS system typically uses a replication mechanism to ensure that files are stored on multiple servers, so that if one server fails, the data can still be accessed from another server.
In addition, the DFS architecture includes mechanisms for load balancing and failover, which allow client requests to be redirected to other servers in the system if one server becomes unavailable. This means that even if the primary DFS system goes down, clients can still access the files they need from one of the secondary systems.
Overall, the fault-tolerant design of the DFS system allows it to continue to provide reliable access to files even if one or more servers in the system go down.
When you add a primary DFS system, it typically becomes the primary point of contact for clients accessing the file system. As a result, any changes made to files on the primary system are replicated to the secondary systems in the DFS.
If you made changes to a file on a secondary DFS system before adding the new primary system, those changes may not have been replicated to the new primary system. When you added the new primary system, the replication mechanism may have overwritten the version of the file on the primary system with the version from one of the secondary systems. This would result in any changes you made to the file on the secondary system being lost.
To avoid this situation, it's generally a good idea to ensure that all changes are made to files on the primary DFS system, rather than on secondary systems. This will help to ensure that changes are replicated properly and that there is no risk of data loss due to conflicts between different versions of the same file on different systems. Additionally, it's a good practice to have backups of important files to protect against data loss or corruption.