hossein306 opened a new issue, #12707:
URL: https://github.com/apache/cloudstack/issues/12707

   ### problem
   
   We recently completed the integration between Veeam Backup & Replication and 
Apache CloudStack by following the official documentation, and the backup 
workflow is generally operational. However, we have encountered an unexpected 
behavior in the backup deletion process.
   
   When attempting to delete a single backup from the CloudStack UI (Instance → 
Backup section), the following message is displayed:
   
   Veeam backup provider does not have a safe way to remove a single restore 
point, which results in all backup chain being removed. Use forced:true to skip 
this verification and remove the complete backup chain.
   
   After proceeding with force delete, all backup entries for the VM are 
removed from the CloudStack UI. However, the actual backup files still remain 
intact on the Veeam server and are not physically deleted.
   
   Observed issues:
   
   1.CloudStack UI removes the entire backup chain when deleting a single 
backup.
   
   2.This creates operational problems for quota management. For example, with 
a backup limit of 20, users should be able to delete older restore points 
individually.
   
   3.Even when the Veeam job is configured for full backups (not incremental), 
the same behavior occurs.
   
   4.Although the retention policy on the Veeam template job is set to 7 days, 
backups older than one month are still present and not automatically cleaned up 
in either CloudStack or Veeam.
   
   Could you please advise how this situation should be properly handled or 
configured to avoid this behavior?
   
   <img width="1169" height="689" alt="Image" 
src="https://github.com/user-attachments/assets/568eed31-bea5-476a-ac1e-3707743e1a6b";
 />
   <img width="1161" height="539" alt="Image" 
src="https://github.com/user-attachments/assets/28b746cc-1be3-406c-8ef5-086a7c8f3b8f";
 />
   
   ### versions
   
   CloudStack 4.21.0.0 
   veeam 12.3.2.3617
   
   ### The steps to reproduce the bug
   
   1.
   2.
   3.
   ...
   
   
   ### What to do about it?
   
   _No response_


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