Veeam plugin – Deleting single backup from CloudStack UI removes entire backup chain in UI while data remains in Veeam

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

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

Bắt đầu từ luồng xóa Instance → Backup trong CloudStack UI và cảnh báo của Veeam provider được hiển thị trong báo cáo; tái hiện với CloudStack 4.21.0.0 và Veeam 12.3.2.3617, rồi theo dõi xem việc xóa bản ghi trên UI có khớp với việc xóa ở phía provider hay không. Báo cáo không định nghĩa hành vi mong đợi, vì vậy hãy làm rõ các tiêu chí xóa một restore point riêng lẻ và dọn dẹp retention trước khi lập trình.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.