Step 8: Source proxy performs additional processing when it copies VM data. The source proxy uses this metadata to detect blocks that have changed since the last job session.
Step 7: During a job session where the CBT is not available, the source proxy interacts with the backup repository to obtain replica metadata. The source proxy determines whether any blocks have changed so that only those blocks are retrieved during incremental job sessions using changed block tracking (CBT). Step 6: VM data is read from snapshots or checkpoints and copied by the source backup proxy. Step 5: A point-in-time copy of a VM is made by Veeam Backup & Replication utilizing Microsoft Hyper-V VSS.A VM checkpoint or volume snapshot is created by Microsoft Hyper-V VSS based on the hypervisor version. Step 4: Veeam Backup & Replication can attach to VM guest OSes, deploy non-persistent runtime components, or use (if necessary, deploy) persistent agent components, and perform in-guest processing on VM guest OSes. Step 3: VBR queries information from Microsoft Hyper-V about VMs and virtualization hosts through the source proxy, either located on or off-premises. As a result, Veeam Backup & Replication sets up connections to target host (on-host) and source proxy (off-host), and also sets access rules for data transfer, such as network traffic throttling rules. Step 2: Assigning backup proxies and backup repositories to tasks is done by Veeam Backup & Replication when it scans the backup infrastructure for available resources. Veeam Backup & Replication creates a separate task for every disk that is added to the job. Step 1: The configuration database is accessed whenever Veeam Backup & Replication creates a replication job session and the list of VMs to be processed is created.
0 kommentar(er)
