Maintenance Release 11.40.8 (Jul 01, 2025)

SaaS metering and usage: Azure Database Usage is double counted

Restore is failing in restore to PST or Disk while fetching admin accounts credentials.

When running HyperScale X v2 to v3 upgrade via cloud UCS console, the session can timeout during node imaging.
HyperScale v2 to v3 upgrade may fail if the flachedata lv was shrunk or removed.
CVFS version can occasionally take up to 30 min to update in Command Center after successful upgrade.

VM backup sets and subclients showing incorrect status flags (bit 2) after reconfigure operations

After CCM's name change, if SourceCS has CSLivesync package installed, the client service may go down after some time.

When performing a restore-based security scan on virtual machines, mounted virtual machines from different subscriptions or hypervisor types, specifically Linux-based hypervisors, may fail if mounted in parallel

VSA backup may fail with error "Failed to run archive index logs"

App aware - Application restore is failing when the VM is backed up using BIOS Guid.

Unable to perform test failover if vm is part of multiple vm group with different storage policy.

Improved NAS Storage vServer detection by filtering out invalid entries without a zapiHostName property, preventing unintended modifications to existing Storage Virtual Machines.

Enhancement to support EBS volumeInitializationRate property during backup and restore.

show enabled Remote Caches for sync

MySQL - Job might be marked as success even when no database is backed up.

Sorting during FS browse from Command center is not working

Improvement in recall logging to streamline troubleshooting efforts.

Addressed a bug where workflows weren't executing from schedule policy, leading to potential errors during schedule policy submission.

Customer may not able to run backups if CS is on foreign locale like Thai locale

FSO jobs running on backed up content may fail

Application backup might fail for Amazon Appaware snap backup

NetApp IntelliSnap snap operations may fail with large rule indexes.

Restore job could fail on scale setup under certain condition

In place restore over existing Azure VMs may fail if the existing VM has a VM ID that differs from the one in the VM backup metadata. This only happens when there are delete restrictions on the existing VM.

GitHub restore jobs are unable to complete because of repository creation failure.

The data for the VM group content tile in Command Center: VSA failed to load.

For MySQL restores, setting the MEB --backup-dir option to the staging directory.

DB2 backups may fail with vendor code error -1 as Commvault binaries are linked to different libatomic.a version than the one loaded by DB2 process.

LiveUpdateJob playback fails when there is an end user erase

Tenants are unable to login when AD connection is configured via proxy

File Server with archiver driver is becoming unresponsive

SAML logins are not working when showLoginEula flag is not enabled

Attachments may not be visible in compliance-search preview, however the attachments are available on restoring the messages

Restore jobs may encounter a pending status due to a technical issue with the update feed API.
Jobs may complete with errors caused by a failure in metadata retrieval during the backup process.

Some clients may experience Linux VG mounting issues when systemid cannot be cleared.

Salesforce INCR does not complete even after several attempts

Unable to access support portal when logging in for the first time

When proxies are configured, customers may notice incorrect login attempts being recorded on the Active Directory side, potentially leading to premature account disablement before the actual invalid login attempts occur.

Backup copy jobs may encounter issues if there are duplicate buckets present in different indexes.

Improved user experience by aligning package options with vendor capabilities. Enhanced FREL package handling for specific virtualization platforms. Updated icons package.

- Changed HPE VME (Morpheus) visibility to be enabled by default in software deployments

Arbiter nodes may be automatically selected as master node for MongoDB instances

MySQL Instant Clone operation might fail for Indexing v2 client

Remote cache clients that are disabled do not appear in the CommCell Console.

Failback operation on continuous replication pairs may encounter issues. This enhancement ensures that the new pair being created will have a unique UUID assigned to the destination VM during its creation.

Backup copy jobs in Splunk encounter issues when exceeding 4 access nodes.

Email previews might fail for large excel attachments

HDFS backups are encountering issues and failing unexpectedly.

Filters added inside C:\Users were not getting honoured while running system state backup

Restore is failing in restore to PST or Disk while fetching admin accounts credentials.

Custom package creator app is not functioning properly.

Expiry date beyond 2038 does not work for access tokens. If a user attempts to create such a token, the created token has an expiry set to a past date

The backup of the d365 database table was unsuccessful.

Improved Gmail Restore to correctly handle Mail, Calendar, and Contacts selections, ensuring a reliable restore experience for users.

3rd party binaries had incorrect ELF headers causing RPM package creation to fail.

Scheduled Reports Job Status report is not functioning correctly in the cloud.

Updates to skip VMs from backup if its part of replication group

3rd party binaries had incorrect ELF headers causing RPM package creation to fail.

Emails are not being sent when SMTP server has authentication enabled

In place patch restore with direct upload to managed disk fails with an error.

Tunnels might experience dropped connections when network throttling is configured.

MySQL & Postgres DB user credentials might be lost when a user upgrades from older SPs to SP38.25 or above

Cloud requests may fail if the Azure server is identified as Azure Stack Hub with previous failed request.

NetApp snapshot paths are generating file not found errors for long paths, causing the scanning process to halt.

nbd module is not auto loaded on HPVME hosts HPVME vm restores may fail or the VM may fail to boot

The 'promote to FULL' conversion job submitted by the MSSQL automatic schedule is not getting resumed by either the job manager or the scheduler, if the CV services on the client are recycled.

Change to improve performance of HTML export output.

Data may be overwritten for DD Boost client library during restore/data verification.
DD Boost connection may not be reused after the request finished.

View failed items for dump backups may not work