#1 Global Leader in Data Protection & Ransomware Recovery

Potential data loss when using Instant VM Recovery

KB ID: 3107
Product: Veeam Backup & Replication
Veeam Cloud Connect
Version: 9.5 U4b
Published: 2020-02-17
Last Modified: 2020-08-13
mailbox
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

Performing Instant VM Recovery in VMware vSphere environments may result in data loss when using the quick migration feature to move published VM disks to production storage to finalize the recovery. This issue was identified internally by Veeam quality control in late 2019, and the fix was included (among others) in version 20191210 of Update 4b. However, no support KB article was created to highlight that this particular issue was fixed, because its scope was originally thought to be much smaller.

Your environment is not affected if:
  • Your VMware vSphere license includes the Storage vMotion feature because in this case, Veeam will finalize Instant VM Recovery using this technology, OR
  • You installed Update 4b after the update availability notification in Veeam Backup & Replication console in January 2020 (or in December 2019 through the 20191210 distribution package).

If you aren’t in the situation described above, you are strongly advised to schedule a maintenance window promptly and apply the update as soon as possible.
  • If you upgraded to Update 4b prior to version 20191210 availability, or if you are not sure when you upgraded, please download and install the patch from this KB article.
  • If you are running Update 4a (build 9.5.4.2753) or Update 4 (build 9.5.4.2615), please download and install Update 4b 20191210 from KB2970 (or from Veeam web-site).

Solution

  1. Download the patch and extract ZIP file to your backup server.
  2. Check the current version of Veeam Backup & Replication. It must be 9.5.4.2866 (Update 4b).
  3. Make sure that no jobs are running and close the console.
  4. Right-click on the installation file and click "Run as administrator".
  5. Go through the setup wizard to deploy the patch.

More Information

This patch is a cumulative hotfix rollup for Veeam Backup & Replication Update 4b which also includes the following previously released hot fixes in the single package:
  • Backup to Tape Jobs fail with “Tape Error: 1117” (KB2983)
  • Potential data loss during Export Backup retention processing (KB3039)

DOWNLOAD PATCH



MD5 for kb3107.zip: 16e93eb835dfafceb6b60f31450de9d8
SHA-1 for kb3107.zip: ca9ee800f532a4dd2b240fdd19583db238d05fdb
To submit feedback regarding this article, please click this link: Send Article Feedback
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.

You have selected too large block!

Please try select less.

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.