VPG Statuses and Synchronization Triggers
The following topics are described in this section:
| • | VPG Statuses |
| • | VPG Synchronization Triggers |
During normal operations the VPG status can change. For example, a change can be made to the VPG definition, or an operation such as move or failover is performed on the VPG, or an external event impacts the system such as the WAN going down. When the status changes, resulting in the VPG being synchronized, for example with a Delta Sync, the estimated time to complete the synchronization is displayed under the VPG status, and if relevant, the synchronization trigger, such as Network Congestion.
See also:
| • | Copy VPG Settings |
| • | Editing a VPG |
| • | Adding Virtual Machines to a VPG - Overview |
| • | Removing Virtual Machines from a VPG |
| • | Removing Virtual Machines from a vCD vApp |
| • | Removing Protected Virtual Machines from the Hypervisor Inventory |
| • | Modifying Protected Virtual Machine Volumes |
| • | Pausing and Resuming the Protection of a VPG |
| • | Forcing the Synchronization of a VPG |
| • | Handling a VPG in an Error State |
| • | Deleting a VPG |
| • | Ensuring Application Consistency – Checkpoints |
| • | Running Scripts Before or After Recovering a VPG |
| • | Exporting and Importing VPG Definitions |
| • | Managing Protection When the Recovery Datastore Will Be Unavailable (Datastore Maintenance) |