Issue | Hotfix |
---|---|
Now with this form, on a linux system even a non root user can run .sh scripts without going through changeFileAttributes. |
598 |
Enhancement to create Secure Bulk Insert SP Wrapper using enumerator folder identifiers from which files can read from and avoid passing in an actual argument file path for better security |
595, 596, 597 |
Objects with special characters in their names or paths encounter backup failures, with an error stating the object is missing. |
594 |
In certain cases, the WebServer process does not initialize successfully following IIS recycling. |
593 |
SMTP addresses are not encoded correctly |
592 |
Failures may occur during NAS synthetic full backups when no data is protected in the incremental backup. |
591 |
Teams backup logging enhancement for better troubleshooting. |
588 |
Enhance resource filtering by adding disk filtering within application. |
587 |
VSA FI - Handle the VM status when the job is interrupted |
585 |
App aware - manually deconfigured instances are automatically getting configured |
584 |
VMs may fail to backup |
583 |
Post upgrade, services failed to initialize on macOS. |
582 |
Job Manager may become unresponsiveness when processing Kubernetes apps for creating VM jobs |
581 |
Unable to update the subclient policy associations on the CommCell Console |
578, 579 |
Uploading file may fail if not using S3 regional endpoint. |
577 |
AD users may observe incorrect login attempt counts on the AD side when proxies are configured. |
575, 576 |
Improved performance for CSV export functionality in FSO. |
574 |
Unable to list all Azure blob storage accounts when there is a tag starting with digit. |
573 |
vsbkp process crashes backing up VMWare VMs, vixdisklib.log shows VDDK panic messages |
571 |
UEFI boot not honored for replicated Nutanix VMs. |
570 |
Updating to Threat Scan SDK 4.15.26 and applying the latest VDF updates will eliminate false positives found in previous SDK version. |
568, 572 |
Health Report "Subclients Not Having Full backup in last 60 days" fails to load. |
567 |
Disable Threat Indicator alert by default. |
564, 565 |
Upgrading Apache Tomcat to apply the latest security fixes and other bug fixes. |
561 |
Billing script to retrieve a list of backup jobs, stored on Object Storage using Rest API may take longer time to complete. |
559, 560 |
TPPM HTTP2 connections are failing on Windows Server 2019 clients. |
558 |
For vcd organization account hypervisor, on setting the guest credentials, "adminInstanceId" and "enableAdminAccount" properties get populated with the default values. |
556 |
Handled a Crash - if job ctrl initialization fails during registering the job in JM |
553 |
Upgrading mongo DB binaries to latest minor version. |
551, 552 |
Improved Exchange DAG restore process by fixing data synchronization issues, enhancing error handling, and refining database selection logic for a smoother user experience. |
550 |
For description based event alerts, if the description was very long, suppress alert functionality was not working. |
549 |
Email settings may encounter token acquisition issues with modern authentication because of permission errors. |
546 |
Teams backup sometimes may complete with errors when items in the source are in accessible. |
548 |
CVDistributer may fail to launch on a machine which is used as Access Node |
542 |
Unable to download XML files during the OneTouch recovery process via REST API. |
541 |
Enhanced export functionality by adding a configurable retention period option. Administrators can now easily adjust data retention policies based on compliance needs. |
540 |
File system Epic backup of a VM with PRDM enabled disk may show SAN degradation after successful backup copy job |
539 |
The login banner lacks background and incorrect word wrapping. |
538 |
Excess redundant data may be produced on CVFS version 5.0.9 under certain conditions. |
537 |
Exchange Discovery may fail. |
532 |
Proxmox - Do not fail restore job if we fail to restore metadata disks |
514 |
Full VM restores from VMware backups may have boot issues |
510 |
AMI creation fails with error "Tag keys starting with 'aws:' are reserved for internal use" |
509 |