https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyODA1IiwiaGFzaCI6IjUxMGRiMGM0LWIxOTQtNDgxNi04ZWVlLTg5NzQ4N2VmZDY2OCJ9
"Failed to detach SCSI lun" errors in vSphere after finishing Instant Recovery or File-level restore from storage snapshots
Challenge
You might see "Failed to detach SCSI lun" errors in vSphere during the unexport phase when restoring items (file-level restore) from storage snapshot or doing an Instant Recovery from storage snapshot because of certain VMware behaviour. Both types of the restores include a step when storage snapshot clone is presented as a temporary datastore which should be unmounted or detached when the restore is finished.
Cause
By default when the device is detached, it stays in an unmounted state even if the device is re-presented (that is, the detached state is persistent). That positively means that it's possible to exhaust the limit of 512 detached devices which can lead to aforementioned error message
Solution
To clean up the list please refer to this kb article: https://kb.vmware.com/s/article/2004605
KB ID:
2805
Product:
Veeam Backup & Replication
Version:
9.x
Published:
2018-11-29
Last Modified:
2020-08-13
Languages:
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!
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
