#1 Global Leader in Data Resilience

IBM SVC or IBM Storwize storage LUN can be deleted under specific circumstances

KB ID: 2831
Product: Veeam Backup & Replication
Version: 9.5
Published: 2018-12-19
Last Modified: 2020-08-25
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.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

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

Newly created LUNs on IBM storages that utilize the Spectrum Virtualize Software with Veeam B&R(IBM SVC or IBM FlashSystem), under very specific circumstances, can be deleted by Veeam B&R.

Cause

Spectrum Virtualize software has the ability to reuse LUN IDs, which are not set to be unique as with a UUID/GUID. This can potentially result in a situation where for a newly created LUN may receive the same LUN ID as that of a LUN which Veeam is attempting to remove (e.g., temporary Storage Snapshot LUN made for a Backup from Storage Snapshot job), resulting in the removal command being applied to the newly created LUN. The situations in which this issue has been identified had specific infrastructural issues which resulted in the accidental removal of the newly created LUN (i.e., infrastructural issues prevented the normal deletion of a temporary LUN for Backup from Storage Snapshot jobs).

Solution

To resolve this issue, please download the hotfix and follow the instructions to apply it;

Note: the hotfix is only applicable to Veeam Backup and Replication version 9.5 with update 3a installed (9.5.0.1922)

  1. Make sure no jobs/tasks are running and stop all Veeam Backup services on the Veeam server
  2. Navigate to Veeam installation directory (by default C:\Program files\Veeam\Backup and Replication\Backup)
  3. Make a backup of Veeam.Backup.SanPlugin.IbmLib.dll and Veeam.Backup.PublicStoragePlugin.Ibm.dll files
  4. Replace Veeam.Backup.SanPlugin.IbmLib.dll and Veeam.Backup.PublicStoragePlugin.Ibm.dll with those from hotfix package
  5. Start all Veeam Backup services

More Information

The problem will be permanently fixed in Veeam Backup and Replication Update 4.
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 hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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 hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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.