1-800-691-1991 | 9am - 8pm ET

SureBackup Best Practices


You are experiencing performance issues with SureBackup jobs, FLR, or Instant Recovery.


Insufficient system resources or improper job configuration.


To get the best performance out of SureBackup, you can check to make sure the following are in place:

  • Veeam server will need as much Ram as possible. If booting more than 2 VM’s, it is recommended to have at least 6-8 GB of memory free, especially if you also plan on doing a restore which consumes memory as well.
  • Also, the closer the storage is to the Veeam server, and the less retention points you have to go through, the faster it will come up. Local storage is best if available. Keep in mind that the VM’s are booting from the backup files themselves, so the more hops it goes through or the slower the storage, the slower the read speed is for the VM that’s booting. This also comes into play when accessing a retention point that requires access to more files. For instance using forward incremental that has not had a synthetic full for a Month or a reverse incremental from 2 weeks ago, without an active full in between.
  • Some things to watch out for are trying to run from dedupe appliances. They often have decent write speeds, but when trying to access the full disk all at once to start a VM can cause severe latency due to the files having to be undeduped and presented to the Veeam server, for us to present to the VM.
  • The VM’s will also consume resources on the host you are booting them up on as well, and choosing a host that is already over utilized will not only affect the SureBackup VM’s, but also the rest of the production VMs.
Veeam Backup & Replication
5.x, 6.x, 7.x
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later