Click slide for next, or goto previous, first, last slides or back to thumbnail layout.
RCDS tries hard to be robust and fault-tolerant.
Clients aren't bound to any single server of any kind. (except for http proxy servers, which are considered a stopgap measure to deal with clients lacking RCDS support.)
Likewise, file servers aren't bound to any particular location or catalog server. They can send updates to any location server for their domain, and the results will be propagated to the other servers. Even in the event of a network partitioning, the servers will maintain a strict consistency model.
Each file server attempts to keep its own collection intact, periodically checking its files against their descriptions. When damage is found, the file server autonomously repairs it by obtaining a correct copy of the file from another server.
A file server, catalog server, or location server should also be able to detect and recover from a system crash or disk crash and restore its proper state.
Click slide for next, or goto previous, or back to thumbnail layout.