What Happens After the VPG is Defined

The following topics appear in this section:

•

Recovery

•

File and Folder Recovery

After defining a VPG, the VPG is created. For the creation to be successful, the storage used for the recovery must have either 30GB free space or 15% of the size free. This requirement ensures that during protection the VRA, which manages the virtual machine journal and data, cannot completely fill the storage, which would result in the VRA freezing and stopping to protect all virtual machines using that VRA.The VRA in the remote site is updated with information about the VPG and then the data on the protected virtual machines are synchronized with the replication virtual machines managed by the VRA on the recovery site.

The synchronization process can take some time, depending on the size of the virtual machines, the amount of data in its volumes, and the bandwidth between the sites. During this synchronization, you cannot perform any replication task, such as adding a checkpoint.

During this synchronization, you cannot perform any replication task, such as adding a checkpoint.

For synchronization to work, the protected virtual machines must be powered on. The VRA requires an active IO stack to access the virtual machine data to be synchronized across the sites. If the virtual machine is not powered on, there is no IO stack to use to access the protected data to replicate to the target recovery disks and an alert is issued.

Once synchronized, the VRA on the recovery site includes a complete copy of every virtual machine in the VPG. After synchronization the virtual machines in the VPG are fully protected, meeting their SLA, and the delta changes to these virtual machines are sent to the recovery site.

For details of the screen, see Monitoring a Single VPG.