This configuration, which provides high-availability production cache if you choose to run  balanced mode with three copies (R-R-D for both Cluster 0 and Cluster 1), is shown in  Figure 5-6. Draft Document for Review February 7, 2020 3:15 pm 8464ch05_DisasterRecovery.fm TS7700C or TS7700T  Cluster 2 TS7700D  Cluster 0 TS7700D  Cluster 1 Copy Export  (Optional) object store Figure 5-6 Three-cluster high availability and DR with two TS7700Ds and one TS7700T  Another variation of this model uses a TS7700D and a TS7700T or TS7700C for the  production site (as shown in Figure 5-7), both replicating to a remote TS7700T or TS7700C  with optional object store in the cloud shared by both sites.  In both models, if a TS7700D reaches the upper threshold of usage, the PREFER REMOVE  data, which was replicated to the TS7700T or TS7700C, is removed from the TS7700D cache  followed by the PREFER KEEP data. PINNED data can never be removed from a TS7700D  cache or a TS7700T CP0. In the example that is shown in Figure 5-7, you can have particular workloads that favor the  TS7700T or TS7700C, and others that favor the TS7700D, suiting a specific workload to the  cluster best equipped to perform it.  Chapter 5. Disaster recovery  215 Figure 5-7 Three-cluster high availability and DR with two TS7700T/TS7700C and one TS7700D  TS7700C or TS7700T  Cluster 2 TS7700D  Cluster 0 TS7700C or TS7700T  Cluster 1 Copy Export  (Optional) Copy Export  (Optional) object store