| Issue | Hotfix |
|---|---|
| Server startup is now faster and more reliable, with reduced initialization delays and fewer failures caused by external service timeouts. |
281, 282 |
| Backups may report an incorrect number of collected files when all hard-linked files prepared for backup have a size of zero, causing multiple sub-clients to fail.
Backups incorrectly report the number of collected files when all hard-linked files have a zero size, leading to sub-client failures |
280 |
| PVC capacity is now reported based on actual allocated storage, ensuring more accurate volume size information in monitoring and usage displays. |
279 |
| Failed file processing for Object Storage agent is being enhanced. |
277 |
| The system is being updated to support Java 17 for Cassandra, which may impact existing operations. Cassandra operations fail or exhibit unexpected behavior after system update; Existing operations are impacted by Java 17 support for Cassandra. |
275 |
| The system will now correctly select the appropriate access node for reverse replication jobs. Reverse replication jobs may select an incorrect access node. |
273, 274 |
| Lack of support for KMS, IAM, and cycle based retention on Bigtable backups |
269, 270, 271, 272 |
| Issue observed with revert operations when multiple mount points are tied to a single Azure NetApp volume. The root cause is repeated calls to the revert API for the same snapshot. |
263 |
| VM guest size calculation is inaccurate when the VM is configured with storage spaces |
260 |
| Plugin recall through the Explorer interface may fail if access to certain files is restricted to a limited number of users. Explorer plugin recall encounters issues when specific files have restricted access for select users. Recalling plugins through the Explorer interface may experience failures when access to files is limited to certain users. |
252 |
| Worker pod runs as user 65534 (nobody) instead of the expected user (e.g., 26) specified at the pod-level securityContext, causing permission issues. A "nobody" user is present at the container level, overriding the intended user specified at the pod level, potentially leading to unexpected operational outcomes. |
250 |
Included from Maintenance Release 11.44.8 (Jun 19, 2026)