LogPolicy equivalent in Plans ?

In the Command Center, as of Service Pack 36, there is no direct option to assign different storage policies or plans specifically for transaction logs and archive logs within a single plan for databases like oracle or sql.  Plans in Command Center are designed to simplify management but currently do not support the granular level of configuration that was possible with Storage Policies in the CommCell Console. For Oracle databases, the storage policy for log backups is generally set at the instance level, and this policy applies to both transaction logs and archive logs.

To manage different storage targets for logs and database backups, you might need to use the CommCell Console where you can configure separate subclients or use instance-level settings for more granular control.

Reference: arlie.commvault.com

Hi ​@sbhatia ,

Thanks for the explanation.

Beginning with new installation of 11.34, the CommCell Console is no longer (generally) available.

To enable the CommCell Console, I heart, that it is required to open a support ticket to get it enabled for a limited period of time.

How does Commvault plan to handle this in the future ?

Removing options to simplify the use of plans, and in the same step removing legacy configuration tools that are required to implement the complexer configurations again.

If transactionlog backups in general are not stored deduplicated ( no hashes created and added to the DDBs ), I don’t have a problem with this behavior. But if transactionlogs are written deduplicated they fill up the DDBs with unique hashes and reduce the amount of addressable backend capacity for a DDB/Pool.

rgds
Klaus