I don't know why, but full backups have increased a lot his backup time. Maybe anyone knows any issue. I use VB&R 7 with the last patch over vspehere 4.1. I post 2 images from before and after.
The difference seems to be related to amount of "Read" data. During second run a backup console read 1 TB more than it had done previously. (the main contributor is lgmweb3). Thanks.
I know that the read data increaed, but there is no reason the the amount of backup time increase. Look at this full backup done in the middle of this other two, it has the same read data of 2TB and less time of backup duration.
But what transport mode is effectively used by the proxy to retrieve VM data from the source datastore? You can find one of the ([san], [hotadd], [nbd]) tags next to the proxy server name selected for processing, if you select the particular VM in the job statistics.
Both for "fast" and "slow" job runs? What about the target storage? Were there any changes on it's side (note that bottleneck has shifted to the target)? Were there probably other tasks it was involved in that could potentially affect its performance?
Ok, after I downgraded the NAS to a previous firmware, the speed of the backup is ok again. It seem that the last firmware of lenovo for their NAS, 4.1.102.29716, have a problem with de veeam backups.
I have an ix2-200 and ix4-300d. Both had issues with that firmware.
The firmware that works fine is 4.0.8.23976, the firmware that has issues is 4.1.102.29716
Well, I told them my problem and they sent me the program to do the downgrade. They don't offer support for downgrade, so there is no information about downgrade on their website, in other way they give a way, through support, to the user for downgrading the NAS, but at the risk of the owner.
So they didn't tell anything regarding whether it is going to be addressed in subsequent firmware versions, right? Well, at least they know there's an issue.
Some user reported that there is a problem with the I/O check in the last firmware. I don't know what's the problem with Veeam, but maybe it's affected.