SadiJr opened a new pull request, #6320:
URL: https://github.com/apache/cloudstack/pull/6320

   ### Description
   
   Using the VMWare hypervisor with Veeam integration enabled, ACS uses a 
hard-coded timeout of 600 seconds (10 minutes) to monitor restore process 
status in Veeam. If the restore does not finish in this time, ACS throws an 
exception; however, the restore process continues in Veeam. This PR aims to 
externalize a global configuration to allow operators to define the timeout 
value in Veeam restore backups process. Thus, making it adaptable to different 
needs.
   
   
   ### 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 created a new huge VM and attached this VM to a Backup Offering;
   2. I performed a manual backup;
   3. I tried to restore this VM using the backup;
   4. Before, an exception was thrown, but the restore backup process keep 
running in Veeam;
   5. Now, with a bigger timeout value, the restore process finish with success.


-- 
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]

Reply via email to