Trigger | Description |
Force Sync | The user requested to synchronize the VPG, as described in “Forcing the Synchronization of a VPG”, on page 195. |
Network Congestion | The network bandwidth is not wide enough to handle all the data, causing some of the data to be backed up. |
Protected Storage Error | An I/O error occurred to a protected virtual machine, after the data was sent to the recovery side. |
Protected VRA Congestion | The host where the VRA is installed is highly loaded: many updates are made to the protected machines at the same time, causing a time lapse before the updates are passed to the recovery site. |
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 datastore 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. |