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

   ### Description
   
   Currently, the backup compression process is always performed 
asynchronously; the existing backup is compressed into a new file, which then 
replaces the original. However, when using immutable storage, this behavior 
increases storage usage because the original backup file cannot be deleted.
   
   To address this, the `compress_async` flag, defaulting to `true`, has been 
added to backup offerings. The default setting maintains the current behavior. 
When the flag is set to `false`, compression occurs during backup creation, 
resulting in only a single file copy. However, enabling synchronous backup 
compression slows down the backup creation process and makes it prone to 
timeouts unless the timeout settings are adjusted accordingly.
   
   It is important to note that the flag only applies to backup offerings that 
have the `compress` flag set to `true`.
   
   ### 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)
   - [ ] Build/CI
   - [ ] Test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [X] Minor
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [ ] Minor
   - [ ] Trivial
   
   ### Screenshots (if appropriate):
   
   ### How Has This Been Tested?
   
   ### Test description
   
   1. I created a new backup offering with `compressasync` = false, and another 
without specifying `compressasync`.
   2. I created the "sync" and "async" VMs and assigned the respective 
offerings to each VM.
   3. I created backups using each of the VMs. I observed that the backups 
created with the "async" VM maintained the previous behavior, whereas the 
backups created with the "sync" VM were compressed during creation.


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