RAID1 surely? Take one out and the array keeps working (though perhaps at lower performance).<p>This sort of job-share is not uncommon in some office environments, and it is part of how &quot;zero hours contracts&quot; work for companies like restaurants and so forth. Employ more people than you absolutely need for knowledge redundancy but don&#x27;t give them full time hours. Then as people leave others take up the slack until replacement devices (sorry, people) can be brought online or a temporarily offline device is repaired (i.e. a sick&#x2F;injured person gets better and returns to work) and resynced.<p>Sometimes it is very convenient for the workers as well as the companies, particularly those who can&#x27;t, or don&#x27;t want to, work full time for one of many reasons. But it can also be used to keep wages&#x2F;conditions artificially low because from the companies PoV everyone is relatively easy to replace, temporarily from within the rest of the workforce and long term by bringing someone new in who the other part(s) of the job-share train on-the-job (I&#x27;ve actually seen this referred to as a Redundant Array of Inexpensive People - with the sound of the acronym a deliberate statement of how some feel about the situation).<p>IMO the problem with explicitly taking on two people at the same time to job-share like that is that they are more likely to chose to leave at the same time (or close to) which kills a chunk of the skill&#x2F;knowledge sharing benefit.