Hi,
I want to use I/O Control to reduce storage load from vsphere MSSQL VM.
when vbt started backup, DB Sql TPS Significantly reduced.
According to Document(https://helpcenter.veeam.com/docs/vbr/u ... tings.html), I/O Control is measure storage latency.
what real-time metric collect from vsphere hypervisor? I want to know what metrics are used from vsphere.
and I want to go low I/O pressure from the moment the backup starts. How do I configure backup job with low I/O?
-
jisulove
- Novice
- Posts: 6
- Liked: never
- Joined: Feb 26, 2024 6:02 am
- Full Name: Byungjoon Jun
- Contact:
-
david.domask
- Veeam Software
- Posts: 3143
- Liked: 720 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: about I/O Control feature
Hi jisulove,
To add automatic throttling based on datastore latency, simply set the option you identified and the job will automatically begin throttling tasks based on what you configured.
Just to be clear, we're talking about backups of the MSSQL VMs themselves, correct? If so my guess is that the VMware snapshot more than anything contributes to the performance impact, and you can test this by simply taking a VMware snapshot and waiting for the same amount of time that the backup job takes to perform the backup.
Consider using our MSSQL Plugin for snapshot sensitive machines, as you can protect the MSSQL data directly without the need for a hypervisor snapshot, and the restore narrative is pretty much the same.
To add automatic throttling based on datastore latency, simply set the option you identified and the job will automatically begin throttling tasks based on what you configured.
Just to be clear, we're talking about backups of the MSSQL VMs themselves, correct? If so my guess is that the VMware snapshot more than anything contributes to the performance impact, and you can test this by simply taking a VMware snapshot and waiting for the same amount of time that the backup job takes to perform the backup.
Consider using our MSSQL Plugin for snapshot sensitive machines, as you can protect the MSSQL data directly without the need for a hypervisor snapshot, and the restore narrative is pretty much the same.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Amazon [Bot] and 5 guests