Tie Breaker

Administrator's guide P 518 :

If the secondary Storage Center cannot communicate with the primary Storage Center, it
consults the tiebreaker to determine if the primary Storage Center is down. If the primary Storage Center is down, the
secondary Live Volume activates.

So the main foreseen problem would be that the primary storage is isolated but still running w/ some "autonomous" services .

The secondary site will be allowed by the tie breaker to become primary. There will be two diverging primary.

Unless I'm wrong this case is not solved by having the "best practice" recommendation to put the Tie Breaker on a third site.

This case can be avoided by having no active server on the secondary site (which has some other drawback in a resilient architecture design, of course). In that case Having the tie breaker on the secondary site seems to be OK. No need of a third site.