![]() ![]() If we zoom in on the Processing Rate and look at the Read speed (green line) and the Transfer speed (red line) and have a look at the graph behind it (Throughput (All Time)) we can see that there is an easy to spot trend. This is pretty low, especially for this environment. Like you can see, the Processing Rate was around 78MB/s for this particular job. Have a look at the below Veeam Backup job history for one of the jobs on the platform: Veeam Backup job performance insight When looking at the past Veeam backup job history I did notice a certain trend, which is why I discovered this issue at the first place. The customers that we have in VCD are able to use the Veeam Backup plugin for VCD to create and edit backup jobs and restore their VMs with it. A HPE Apollo XL450 Gen 9 with a 256TB logical volume in a RAID 60 configuration.vSAN Environment cosisting out of a dozen or more HPE Gen 10 D元80 servers with NVME cache drives and very quick SSD Capacity drives.Which is pretty slow if you imagine that the following hardware is used in this specific environment: ![]() ![]() Even worse, the single stream IO performance looked like it was bottlenecked or capped at or around 50MB/s. The issue we had on this environment was that the backup performance hasn’t been on a level that you would think it would be on. On this environement a multitude of products are used such as Veeam, VMware Cloud Director (VCD) and vSAN as main products. The last two weeks I’ve been working on a big issue on our environment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |