| VM storage policies not getting attached back to VMs after failback |
380 |
| A snapshot restore operation incorrectly identified additional log jobs, causing the restore to be skipped when both data and log snapshots were present.
Snapshot restore operation incorrectly identified additional log jobs, causing the restore to be skipped when both data and log snapshots were present. |
379 |
| Introduced a new report that provides a centralized view of threat scan status, risk levels, scan coverage, and compliance, helping users monitor and prioritize security across their resources. |
378 |
| Fixing false positive detections from system defined yara rules. |
374, 375, 376, 377 |
| Backup system now accepts personal site URLs instead of requiring active user accounts |
366, 367, 368 |
| Morpheus restore operation may fail due to an error parsing virsh pool-dumpxml output |
365 |
| During cumulative updates, the installer fails to upgrade the Web Console Legacy package because it attempts to process updates for this package even when the necessary configuration mappings or files are missing, leading to installation failures and partial rollbacks.
Installer attempts to update Web Console Legacy package even when necessary configuration mappings or files are missing, resulting in failed installations or rollbacks Upgrade failures or rollbacks occur during cumulative update installations when the Web Console Legacy package is included in the update process but lacks required configuration entries, leaving the system in a partially updated state. |
357 |
| The system will now use the control host name instead of the array name when cleaning up snapshots during Isilon NDMP backups to resolve an issue.
Isilon NDMP backups fail during snapshot cleanup because the system incorrectly uses the array name instead of the control host name. |
356 |
| The request is to enable AIX 7.3 Block-Level Backup (BLB) support for additional agents, such as File System iDA |
355 |
| Process VCS content only when default SC content is root |
354 |
| MySQL - Allow edit credential even when old association is missing |
352 |
| Overview and listing page slowness issue |
350, 351 |
| Threat scan: Add check for browse permission for threat page |
345 |
| VSA restore: fix guest credential and impersonation in Restore To VM flow Java Console Restore to Virtual Machine dropdown is not working Guest file restore still has old username and password field instead of credential manager |
344 |
| This request is to implement a restore fix for the MongoDB agent''s Ops Manager configuration.
MongoDB Ops Manager configuration restore fails. |
342 |
| SP46 SharePoint : Service account creation not working |
341 |
| Restoration from deduplicated backups containing device files may fail if the option to include device data is not selected. |
340 |
| Remote copy operations to an Azure cloud library are failing when utilizing a SAS token for authentication. |
338 |
| Failure to generate CommCell Console job summary report. |
336, 337 |
| The requested change adds logic to clear the `pg_wal` directory on restore before starting the server to address observed issues.
Restore operations fail to start the PostgreSQL server due to residual data in the `pg_wal` directory Restores of PostgreSQL databases may fail or encounter errors if the `pg_wal` directory is not cleared before server startup. |
335 |
| Show schedule tab for the SQL instance details page |
333 |
| To prevent unnecessary data tier shifts during IntelliSnap backups, cloned volumes for NetApp will be set with a cloud retrieval policy. |
332 |
| Resolved incorrect validation errors for scripts using relative paths during remote execution, ensuring smoother operation and fewer false error messages. |
326, 327, 328 |
| VM customization is failing because the initial wait time is not long enough to complete the process.
VM customization failures due to insufficient initial wait time Failures during VM customization process. |
325 |
| Fix resource orchestration failure in US gov region |
324 |
| The installer's automatic cleanup process will be updated to remove outdated Salesforce IDA third-party binaries, which are no longer needed and contain critical security vulnerabilities.
The system may report critical errors related to Commvault VA Outdated third-party binaries that contain critical security vulnerabilities are present and not being removed. |
316, 317, 318, 320 |
| Storage Utilization Report chart moved to the next line in exports Charts now remain inline with other content in exports, resulting in cleaner and more compact layouts. Exported reports display correctly without unwanted line breaks. |
319 |
| Navigation preferences are now applied consistently and load faster after first login, resulting in improved performance and a smoother user experience. |
314, 315 |
| Improved security measures in the listing of schedule policies. |
312, 313 |
| custom daterange: set seconds to 0 Seconds set to current time since the datetime picker does not have a seconds input |
309 |
| The PostgreSQL application manager cache was not updating on disk cache instances when instance properties were modified, leading to data inconsistencies.
PostgreSQL application manager cache not updating on disk instances when instance properties are modified causing data inconsistencies. |
307, 308 |
| Azure VSA: Handled case where upper layers pass "None" in the name and ID fields of the... |
306 |
| Resolved issues with browsing files on tape media when multiple jobs request the same file. File access is now reliable and stable during simultaneous or sequential operations. |
304 |
| Exchange | Database | Exchange DB Message level and folder level browse-restore issues when containing non-english characters. |
303 |