Overview
Use this decision flow to size a Global Center for registered Centers, synced components, and recovery behavior.
Global Center sizing depends on registered Center count, synced component count, WAN behavior, and synchronization recovery.
Summary
Plan a Global Center separately from a Local Center because synchronization scale, recovery behavior, and aggregate storage growth create a distinct workload.
Workflow
Use these stages to evaluate Global Center scale:
- Identify the number of Centers to register.
- Estimate the projected synced component count.
- If WAN paths are constrained or outage-prone, prioritize replay testing and storage headroom.
- If the design approaches 20 registered Centers or 150,000 synced components, use CV-CNTR-M6N or VM resources equivalent to M6N and validate it separately.
- If the design does not approach 20 registered Centers or 150,000 synced components, size for growth and replay, not only steady state.
Result
The Global Center design accounts for synchronization scale, recovery stress, and storage growth.