When you upgrade from a previous platform release, you will find that some features and options are updated and enhanced. To read more about the features in this platform release, click the link listed in the Learn more column.
Backup Agents
Introduced in |
Product |
Change |
Learn more |
---|---|---|---|
Commvault Platform Release 2024 (11.34) |
PostgreSQL |
PostgreSQL and EnterpriseDB Version 9.x is no longer supported. |
|
Commvault Platform Release 2024 (11.34) |
Teams |
The following new permissions are required for Azure APIs when you use the custom configuration option for Teams: |
Request and Grant Permissions to Azure APIs for the Azure App for Teams |
Commvault Platform Release 2024 (11.34) |
Azure Blob Storage Azure Data Lake Storage Gen2 |
You must create a cloud account with IAM AD authentication to discover the Azure Blob Storage and Azure Data Lake Storage Gen2 instances based on the configured rules. |
|
Commvault Platform Release 2024 (11.34) |
PostgreSQL |
PostgreSQL agent will be upgraded from Indexing Version 1 to Indexing Version 2 type. You need to complete the backup copy of IntelliSnap and block level snap jobs before upgrading the client. |
|
Commvault Platform Release 2024E (11.34) |
MongoDB |
If the master node for an instance is not available due to a network failure or any other reason and a backup is in progress, then the Commvault software picks another node as master node from the replica set for backup operation. This is applicable only for the replica set environments. |
|
Commvault Platform Release 2024E (11.34) |
MongoDB |
If an incremental backup fails for any reason like role change, then the Commvault converts the log backup to a full snapshot backup automatically. To disable the automatic conversion of an incremental log backup to a full backup, configure the bMongoDbConvertToFullOnLogBkpFailure additional setting. |
CommCell Management
Introduced in |
Product |
Change |
Learn more |
---|---|---|---|
Commvault Platform Release 2024 (11.34) |
Server Backup Plans |
Full Schedules apply to database backups. For other agents, each backup job will back up only the new and modified items and create a full recovery image. Therefore, running repeated full backup is not required. |
|
Commvault Platform Release 2024 (11.34) |
Multi-Person Authorization |
The following authorization operations are enabled by default on Command Center:
|
|
Commvault Platform Release 2024 (11.34) |
Policies in Command Center |
The showPolicies additional setting is no longer available and the users will not be able to view, add, delete or use any schedule, storage or subclient policies from Command Center. You can convert the storage policies to server plan. Also, the exisiting policies can be accessed from CommCell Console. |
Installation
Introduced in |
Product |
Change |
Learn more |
---|---|---|---|
Commvault Platform Release 2024 (11.34) |
Installation |
Severs that are configured with automatic updates and that have the Download software from internet option selected, will have updates automatically installed on them. |
Network
Introduced in |
Product |
Change |
Learn more |
---|---|---|---|
Commvault Platform Release 2024 (11.34) |
Network |
You can view and edit network configurations for server groups in the Command Center. |
Reports
Introduced in |
Product |
Change |
Learn more |
---|---|---|---|
Commvault Platform Release 2024 (11.34) |
Health Report |
In the Command Center, the Health report cannot be exported in CSV format. |
|
Commvault Platform Release 2024 (11.34) |
Metrics Report |
The Metrics Reporting feature is no longer available on Web Console and can be accessed from Command Center. |
|
Commvault Platform Release 2024 (11.34) |
Report Export |
From FR34, you can export reports, schedules, and emails in PDF format with a limit of 2000 rows per table and 500 characters per table cell. |
N/A |
Storage
Introduced in |
Product |
Change |
Learn more |
---|---|---|---|
Commvault Platform Release 2024 (11.34) |
HyperScale X |
When enabled, password-based root access is automatically disabled after 24 hours. |
|
Commvault Platform Release 2024 (11.34) |
Cloud Storage |
Prior to Commvault Platform Release (CPR) 2024 (11.34), Commvault suppported bucket lock on Google Cloud Storage. From CPR 2024, Commvault supports object lock on Google Cloud Storage, but only for new storage buckets. Upgraded storage buckets remain bucket lock enabled. |
|
Commvault Platform Release 2024 (11.34) |
Cloud Storage |
You can now configure cloud storage using the STS Assume Role with IAM Role Policy authentication type by using the Add Credentials window. |
|
Commvault Platform Release 2024 (11.34) |
Air Gap Protect |
Compliance lock is enabled by default for all new installations and upgrades and cannot be disabled. |
|
Commvault Platform Release 2024 (11.34) |
Disk Storage and Cloud Storage |
When the software creates new deduplication databases in a storage pool with horizontal scaling of deduplication databases (DDBs) and seal DDB operation, the software automatically selects DDB location and the MediaAgent with DDB role for optimal usage of resources. The location can be different from the existing location. |
|
Commvault Platform Release 2023E |
Disk Storage and Cloud Storage |
Data multiplexing is not supported for disk storage and cloud storage. It is supported only for tape storage. |
Virtualization
Introduced in |
Product |
Change |
Learn more |
---|---|---|---|
Commvault Platform Release 2024 (11.34) |
All virtualized workloads |
Starting with Commvault Platform Release 2024E (11.36), Virtual Server Agent (VSA) V1 will be end of life and not supported anymore. All new features will use VSA V2. If you are currently using VSA V1, consider upgrading (also called migrating) to V2. |
|
Commvault Platform Release 2024 (11.34) |
|
The Restore as Managed VM setting for new replication groups and new replication targets is removed in Commvault Platform Release 2024 because the setting is now the default restore mode. |
N/A |
Commvault Platform Release 2024 (11.34) |
Azure |
The copy latest snapshot feature is available by default for Azure hypervisors. |
N/A |