Overview
Size a Global Center separately from a Local Center because synchronization activity and aggregate component count create different workload patterns.
A Global Center provides a central view of multiple Centers. It must be sized for synchronization volume, registered Center count, synced component count, storage growth, and replay behavior.
Planning inputs
Number of registered Centers.
Aggregate synchronization activity.
Total synced component count.
Storage growth over time.
WAN behavior during normal operation and recovery.
Use 20 registered Centers and up to 150,000 synced components as Release 5.5.x planning inputs.
Scale planning
Use CV-CNTR-M6N or VM resources equivalent to M6N for Release 5.5.x Global Center deployments that support up to 20 registered Centers and 150,000 synced components. Size Global Center for synchronization scale and recovery behavior, not only for steady-state visibility.
Center-to-Global-Center synchronization is driven primarily by registered Center count, synced component count, activity changes, and recovery backlog. Do not size Global Center resources only from aggregate Sensor ingress traffic.