[henns]

You can couple Rendezvous Hashing with a redundancy method like replication or erasure coding.

The default for Tahoe-LAFS (a distributed filesystem that uses a form of Rendezvous Hashing) uses erasure coding to split each file into (by default) 10 segments of which any 3 are necessary to reconstruct the file. Those 10 segments are then stored across the first 10 servers in the list. [https://tahoe-lafs.readthedocs.io/en/latest/architecture.htm...]

That way, even when servers go away with your data (whether due to crash or even network partitions(!)), you still have a decent chance to locate your data.