SadiJr opened a new pull request, #6582: URL: https://github.com/apache/cloudstack/pull/6582
### Description Using the VMWare hypervisor, with the Veeam plugin active, ACS tries to find, in Veeam, VBRViDatastore using the UUID of this storage in ACS, and VBRServer using the IP of the host in ACS. But, in some scenarios, the VBRViDatastore/VBRServer, in Veeam, can use the name of this component, which causes an exception in ACS. This PR aims to fix this behavior, improving the search of VBRViDatastore and VBRServer by using the name. ### Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [ ] Bug fix (non-breaking change which fixes an issue) - [x] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [ ] Major - [x] Minor ### How Has This Been Tested? It was tested in a local lab: 1. I added new storage and host in my lab, and make sure the component, in Veeam, are identified by their names; 2. I created a VM (the volume is in the new storage, and VM is in the new host) and added this VM to a backup offering; 3. I make some manual backups; 4. I tried to restore a backed-up volume of this VM; 5. Before, an exception occurs because ACS can't find both VBRViDatastore/VBRServer in Veeam; 6. Now, ACS can restore volume with no problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
