Changes in Long-Term Support Release 11.40

Azure SQL Database

Introduced in Product Change Learn more
11.40 Azure SQL Database Backup By default, the Commvault software skips backing up Azure SQL databases with sizes larger than 2 TB. This limitation arises because very large databases have a high rate of failure due to Azure's limitations, especially when the data export operation to the Azure cloud exceeds 20 hours. Backing Up SQL Databases on an Azure Cloud

Backup and Restore Agents

Introduced in

Product

Change

Learn more

11.40

Mac OS File Archiving

Starting Commvault Long-Term Support Release 11.40, the File Archiving feature for Mac OS is no longer available.

Deprecation Notice for Mac OS File Archiving

11.40

Oracle

If you redirect a database or individual table spaces during a restore, the default redirect file name generation now uses %f_%b for the file name format for a backup piece, rather than the default of %U. This avoids file name conflicts.

N/A

Data Management

Introduced in

Product

Change

Learn more

11.40

Storage Policy

Starting Commvault Long-Term Support Release 11.40, the DAConfigDisableCycleRetention additional setting is enabled by default on new installations for CommCell Console.

If you disable this additional setting, the data aging process will honor cycle-based retention across all storage policies, copies, and storage pools. The cycle retention configuration fields will be available in the UI.

N/A

11.40

Restore By Job

Starting Commvault Long-Term Support Release 11.40, the Restore By Job (index free restore) feature is no longer available.

Install and Deployment

Introduced in

Product

Change

Learn more

11.40

Installs

You can no longer install the Commvault control plane on Windows, which includes only the CommServe server, the Web Server, and the Command Center components.

Commvault strongly encourages you to transition to a Linux environment for Control plane components. The Linux platform offers significantly better performance, enhanced stability, and superior resource efficiency when running Commvault.

Deprecation Notice for Commvault Control Plane on Windows

Storage

Introduced in

Product

Change

Learn more

11.38

Web Console

The manual process of moving a deduplication database is no longer required. You can now use a predefined workflow to automate and streamline the move operation.

Moving a Deduplication Database Using Workflow

11.40

Disk, Cloud and Air Gap Protect Storages

In this release, several usability and configuration improvements have been introduced for disk, Air Gap Protect and cloud storage, deduplication database management, and storage resource pooling.

For disk storage, the configuration option previously labeled Deduplication DB Location has been renamed to DDB MediaAgent. This field now supports multi-selection, allowing users to choose multiple MediaAgents during configuration. Additionally, the deduplication database (DDB) path is now automatically derived from the selected MediaAgents, removing the need for manual path specification.

Similar enhancements apply to cloud storage and Air Gap Protect storage. Both the MediaAgent and DDB MediaAgent fields are now multi-select dropdowns, enabling the selection of multiple MediaAgents to optimize data distribution and redundancy. When configuring storage for a specific region that has a defined storage resource pool, the system automatically assigns MediaAgents based on the pool configuration. The Automatic option is selected by default in such cases, but users retain the flexibility to override this and manually select their preferred MediaAgents.

The Deduplication DB Location section now provides a more structured view of the DDB disks configured for each MediaAgent. By default, one DDB disk (created during installation) is displayed. Users can add new DDB disks or reassign partitions between existing disks through the user interface. Deletion of a DDB location is restricted unless all partitions within it are removed. Once a DDB location has no remaining partitions, it is automatically cleaned up—unless it is the only DDB location remaining for the MediaAgent. New locations can be added by specifying a valid disk path.

A new concept introduced in this release is the Storage Resource Pool, which allows logical grouping of MediaAgents by region. This structure simplifies region-based storage provisioning. Administrators can easily manage these pools through the Command Center, with options to add or delete pools based on operational requirements.

11.40

Deduplication

Version 4 deduplication databases (DDBs) are not supported in the current software release. Before upgrading to the current version, you must convert all Version 4 DDBs to Version 5. Version 5 DDBs support enhanced data management capabilities, including garbage collection and journal pruning. Use the Convert DDB to V5 workflow to complete the conversion.

Converting a Deduplication Database to V5

Web Console

Introduced in

Product

Change

Learn more

11.38

Web Console

Starting in Innovation Release 11.38, the Web Console will no longer be available on new or upgraded installations.

Migrate to the Command Center, which offers most of the same features, such as Reports.

×

Loading...