Figure 9-3 illustrates the case where, starting from the steady state shown in Figure 9-1, a single string fails. When String 1 fails, the mediator hosts on both phys-hahost1 and phys-hahost2 will be updated to reflect the event, and the system will continue to run as follows:
No takeover occurs.
Sun Cluster node phys-hahost1 continues to own the diskset.
Because String 1 failed, it must be resynchronized with String 2. For more information on the resynchronization process, refer to the Solstice DiskSuite User's Guide and the metareplace(1M) man page.
The commit count is incremented and the mediators remain golden.
The administration required in this scenario is the same that is required when a single string fails in the three or more string configuration. Refer to the relevant chapter on administration of your disk expansion unit for details on these procedures.