PLANs and HANA databases ...

It sounds like strange behavior. I’d open a support case to figure out what is going on here, I would not expect this to happen.

Thanks Damian,

can you alos check, whether it is possible to assign the defined / associated log policy, that is assigned to the storage policy object of a plan (as possible in legacy configurations) ?

currently, once a assigning the plan to an instance, the log policy is forcibly changed to the same storage policy, ignoring any configured log policies.

This also applies to Oracle and MS SQL, which results in log backup assignments to a dedupe policyor worse, to a tape policy. (not really useable with persistent log backups) 

Any update on this request?

Aside from use cases: wanting use a different backup target for database or log backup, also wanting a different retention set for database or log backup.

According to our best practices, we should use different plans, 

https://documentation.commvault.com/2024e/expert/sap_hana_best_practices.html

Use the following guidelines when you assign a storage policies:

• Configure the following options for the data storage policy:

  • Enable deduplication

  • Compression

• If you are using a separate log storage policy:

  • Enable resource caching for log storage policy

  • Disable deduplication on log storage policy as logs are not deduped

​@Ledoesp as customers are moving more and more to Command Center it thus means that if Command Center does not allow customers to implement Commvault own best practices then something is going wrong, right? 

​@johanningk what version are you on? They have been making tons of changes over the last few platform releases, so it might be relevant. 

I would say there is room for improvement. I have tested this in 11.36 version.