Any good system administrator can do this, and this reqires no special consideration from the database designers. This strategy is fairly robust: if the master copy is lost, the mirrors can still operate, and the master can be reconstructed from the mirrors.
The drawbacks of this style of replication should be obvious: this model does not support distributed transactions. Transaction processing can only be done on the master, and thus the master is a critical componenet, and is also a bottleneck. The mirrors can be used only for viewing (reading).
The advantages of this style should also be obvious: by installing mirrors (which may be geographically separated by thousands of miles) performance for viewing is radically improved, since one machine does not have to handle all the load. The strength of this scheme is it's simplicity.
The disadvantage of this system is that it does not support transactions. There is no record locking during updates, and race conditions exist.