We are unable to restore from SAN Snapshots on any of our Unity arrays, it appears Veeam is attempting to bind it on an unused FCOE adapter instead of the correct FC HBA.
The Veeam snapshot is visible when looking at devices attached to the FC HBA, but it is as if Veeam isn't able to see this.
We have a Pure array where this works without issues and binds to the correct vmhba, then proceeds resignaturing the LUN etc.
ESXi version is 6.7, Unity OE 5.x
SR# 04805523
-
- Influencer
- Posts: 15
- Liked: 1 time
- Joined: Aug 29, 2016 10:54 pm
- Contact:
-
- Product Manager
- Posts: 14844
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Unable to restore from Unity SAN Snapshot
Hello,
please remember that the forum is mainly run by Veeam Product Managent... I see that the case is some weeks old and that tier2 engineers are actively working on it (looks okay for the kind of issue you describe). If you think that things went "off-track", then there is the "talk to manager" button in my.veeam.com.
Best regards,
Hannes
PS: opening severity 1 cases for non-critical issues is usually slowing down support as it leads to re-routing between teams
please remember that the forum is mainly run by Veeam Product Managent... I see that the case is some weeks old and that tier2 engineers are actively working on it (looks okay for the kind of issue you describe). If you think that things went "off-track", then there is the "talk to manager" button in my.veeam.com.
Best regards,
Hannes
PS: opening severity 1 cases for non-critical issues is usually slowing down support as it leads to re-routing between teams
-
- Influencer
- Posts: 15
- Liked: 1 time
- Joined: Aug 29, 2016 10:54 pm
- Contact:
Re: Unable to restore from Unity SAN Snapshot
Hi,
The cause of this was found today, after adjusting the permissions for the the integration account used between the SAN & vCenter from "Storage Administrator" to "Administrator" in vCenter, the issue is resolved.
The cause of this was found today, after adjusting the permissions for the the integration account used between the SAN & vCenter from "Storage Administrator" to "Administrator" in vCenter, the issue is resolved.
Who is online
Users browsing this forum: No registered users and 11 guests