When planning for WAN acceleration, review the backup mode used on the primary backup job. To calculate possible savings and needed bandwidth you may use the following calculator. Note: Approximate savings ratio can be assumed as of 10x. The actual savings rate equals 3.9x in this relatively static demo infrastructure, whilst it would typically be significantly higher in real-life scenarios. In the example above, 283 MB would have been transferred over the WAN link in Direct Transfer mode, while only 72.8 MB were transferred after enabling WAN acceleration. The amount of Transferred data is the amount of data actually transferred over the WAN link.Ĭomparing Direct Mode with WAN Accelerated ModeĬonsider that the savings rate (18.5x) displayed in the GUI is based on Processed data ("re-hydrated" data blocks).
For this reason, this metric can be ignored. The number of Read blocks for the backup copy job is typically higher than the amount of Processed - this is due to the backup copy job using a differing fingerprinting algorithm that works with a different block size compared to the fingerprinting algorithm and block size used by backup jobs that created the original backup file. This is the most important metric, as it is the amount of data that has to be processed by the WAN accelerator. The amount of Processed blocks in the backup copy job session is equal to the amount of Read blocks in the backup job session. Comparing the backup copy job with WAN acceleration enabled and the backup job, it is possible to correlate the information in both outputs. When analyzing a backup copy job you can see the same metrics in the job session Data: Processed, Read and Transferred. This is the amount of data that will be processed by the backup copy job running in Direct Transfer mode (without WAN acceleration), assuming all VMs from the backup job are included in the backup copy job. Transferred - amount of data written to the backup repository after applying compression and deduplication. This is the amount of data that will be optimized by the WAN accelerator.
Read - amount of data read from the production storage prior to applying any compression and deduplication. Transfer and WAN accelerated mode, examine the Read and Transferred values: To better understand the difference between direct data
#Veeam backup and replication user guide full
Analyzing Backup Jobĭuring both full and incremental job sessions, three metrics are displayed in the session data: Processed, Read and Transferred. With the WAN accelerated backup copy job log and statistics. The daily changes of the primary backup job statistics (as the same data is transported in a standard backup copy job without WAN acceleration) To determine how much data has to be transferred over the WAN link with and without WAN acceleration enabled in a backup copy job, you can compare This is the reason why the WANĪccelerator consumes significant amounts of CPU and RAM resources. The WAN acceleratorĬomponent will then process those data blocks with much more efficient data deduplication and compression algorithms.
The WAN accelerator uses its own digests based on the hashes of the blocks inside a VM disk, which means that it reads data from the backup files and re-hydrating them on the fly, or it reads directly from the source VM in case of replication. For more information, refer to the WAN Acceleration section of the Veeam Backup & Replication User Guide. When using WAN acceleration on links with very poor bandwidth, you may have to manually seed the initial copy to the target. To determine whether WAN acceleration is necessary in an environment, it is important to understand what particular savings can be achieved. Any other WAN acceleration technology should be disabled for Veeam traffic. This technology is specifically designed to accelerate Veeam job. Variable block size deduplication and global caching, WAN acceleration provides sufficient capability whilst the required network bandwidth is dramatically reduced when performing Backup Copy and Replication jobs. By combining multiple technologies such as network compression, multi-threading, dynamic TCP window size,
0 kommentar(er)
