To achieve the RPO of eight hours, the replication jobs must be able to transfer 300 GB of data within that time frame. The available bandwidth is 40 Mbps, which means that the maximum amount of data that can be transferred in eight hours is about 144 GB (40 Mbps x 8 hours x 60 minutes x 60 seconds / 8 bits). Therefore, the replication jobs need to reduce the amount of data that needs to be transferred by using some compression or deduplication techniques. The best option for this scenario is to use WAN acceleration, which is a feature of Veeam Backup & Replication that optimizes data transfer over WAN or slow connections. WAN acceleration uses global data deduplication, caching, and compression to reduce the amount of data sent over the network and speed up the replication process. According to Veeam’s documentation1, WAN acceleration can reduce the amount of data transferred by up to 50 times and increase the data transfer speed by up to 20 times. Therefore, by using WAN acceleration, the replication jobs can easily achieve the RPO of eight hours.
The other options are not as effective as this one. Option A uses replication jobs with copy mode set to “Interval copy”, which is a new mode introduced in Veeam Backup & Replication v10 that copies restore points as soon as they appear in the source backup repository. However, this option does not use any compression or deduplication techniques, and it also depends on the backup job schedule, which may not match the RPO requirement. Option B uses replication jobs with copy mode set to “periodic copy”, which is the traditional mode that copies the latest source restore point according to a specified interval. However, this option also does not use any compression or deduplication techniques, and it may miss some restore points if there are network outages or failures. Option C uses replication jobs set to Direct Mode, which is a mode that replicates VMs directly from the source host without using any backup repository. However, this option also does not use any compression or deduplication techniques, and it may cause additional load on the source host and network. References: