Storage I/O Control (SIOC) and Veeam

KB ID: 1847
Product: Veeam Backup & Replication
Version: 6.x, 7.x
Published: 2014-01-02
Last Modified: 2020-08-13
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Veeam will cause additional IOPS on the datastore of the source VM (and a target VM, in a replication job) potentially impacting other VMs in the same datastore.

In some cases this may cause the performance of other neighboring VMs (on the same datastore) to decrease during this heavy I/O period.


Solution

This heavy I/O may be either the result of a Veeam backup or conversely, may negatively impact the performance of a Veeam backup. If some VM(s) (not being backed up) is monopolizing the datastore with heavy I/O this may cause Veeam to have small slice of the disk I/O available during backup processes.


User-added image


This is not specific to Veeam and the issue can be addressed by VMware by use of Storage I/O Control (SIOC).

Note: The Storage I/O Control feature requires VMware Enterprise Plus licensing.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022091

SIOC is actually using a congestion algorithm to determine a normal latency for storage devices in a datastore and then spread this evenly across all VMs to assure an equal share of the available IOPS for each device.


More information

Note: NFS storage is now supported in vSphere 5.x.

SIOC protects all virtual machines from unwarranted negative performance impact due to I/O-heavy virtual machines. SIOC prevents a single virtual machine from monopolizing the I/O throughput of a datastore. Storage I/O Control (SIOC) was introduced in vSphere 4.
 
Storage I/O Control Technical Overview and Considerations for Deployment http://www.vmware.com/files/pdf/techpaper/VMW-vSphere41-SIOC.pdf
 
SIOC cannot be controlled within a Veeam job, but merely is part of a well-designed VMware environment that will be taken advantage of by Veeam.
 
Other Related links:

Dynamically Allocate I/O Capacity Across Multiple Hosts - See more at: http://www.vmware.com/products/vsphere/features/storage-io-control.html#sthash.uJXpAGGZ.dpuf
 
Unmanaged I/O workload detected on shared datastore running Storage I/O Control (SIOC) for congestion management (1020651) http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1020651

Troubleshooting Storage I/O Control (1022091) http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022091



Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.