ProtecTIER can reserve local-backup-only space for the hub repository. You can use this  enhancement to exclusively assign a portion of a hub repository for local backups. This  enhancement was added to ensure that capacity is reserved only for local backup.  Replication cannot be written to this portion of the hub repository.  Error notifications display if the repository hub areas that are reserved for local backup or  replication are reaching maximum capacity. Figure 21-13 shows the window for this  enhancement. The planning process for ProtecTIER systems with replication deployed requires more input  and considerations beyond the individual capacity and performance planning that is needed  for a system that is used only as a local VTL, or FSI. When a multiple-site, many-to-one, or  many-to-many replication strategy is deployed, the entire configuration, including all spokes  and hubs, must be evaluated.  The planning of a many-to-one replication environment is similar to the planning of  a  one-to-one replication strategy. The only difference is that you must combine all replication  loads (and potentially a local backup) for the hub. The ProtecTIER Planner tool should be  used at the planning stages before any ProtecTIER deployment Bandwidth sizing and  requirements. For more details, see 7.1.1, “ProtecTIER Planner tool” on page 102. The ProtecTIER server replicates only the new or unique deduplicated data. Data that was  deduplicated on the primary server is not sent to the DR site. However, the DR site (hub) must  synchronize with all of the data on the primary server to ensure 100% data integrity.  21.10 Replication planning Figure 21-13 Current capacity Chapter 21. ProtecTIER replication  379