Managing VPGs : VPG Statuses and Synchronization Triggers : VPG Synchronization Triggers
  
VPG Synchronization Triggers
The following synchronization triggers can be applied:
Trigger
Description
Force Sync
The user requested to synchronize the VPG, as described in Forcing the Synchronization of a VPG.
Network Congestion
The network bandwidth is not wide enough to handle all the data, causing some of the data to be backed up.
Recovery or Journal Storage Error
There was an I/O error either to the recovery storage or journal, for example if the journal was full and the size was increased. Once the problem is resolved a synchronization is required.
Recovery Storage Congestion
The recovery storage is being written to a lot, causing a delay for some of the data passed from the protected site to be written to disk.
Recovery VRA Communication Problem
A network error, such as the network being down for a period, requires a synchronization of the VPG between the two sites, for example a bitmap sync.
VPG Configuration Changed
The configuration of the VPG changed resulting in a synchronization being required. For example, the size of the journal was changed.