hello ​@LiorRN 

we're doing a production maintenance failover to install a service pack on the production CommServe. So, what does that mean? The standby CommServe host will be brought online in READ-ONLY mode, so clients can only use it for restore operations, just like you mentioned.

In your case, you can proceed with a Production Failover, which will transfer the SQL log backup from the current production CommServe to the standby. This can be done temporarily until the service pack installation is complete on the production CommServe host 
https://documentation.commvault.com/2024/expert/planned_failovers.html

Best Regards,
Mohamed Ramadan
Data Protection Specialist

Thanks Mohamed for the quick response,

So all I need to do is production failover to the standby - than upgrade the main commserve SP version

and failback to the main commserve

thank you :) 

No problem ​@LiorRN 

Yes performing the production failover is the best way to ensure the SQL backup works smoothly during the upgrade.

If you run into any issues -hopefully not- just update the topic
Best Regards,
Mohamed Ramadan
Data Protection Specialist

I suggest reviewing and enabling Disk Caching for your SQL backups.  This feature will allow your SQL log backups to continue to run even when the CommServe is down.  There’s only 1 active CSDB so you cannot avoid it being impacted when applying a Feature Release.

Disk Caching for Frequent Database Log Backups
https://documentation.commvault.com/2024e/expert/disk_caching_for_frequent_log_backups.html

Thanks,
Scott

hello ​@Scott Moseman 
Thanks for sharing such an amazing feature

I didn’t know something like this existed (Ive tested it and documented it internally)

BTW ​@LiorRN I’ve tested it in VLab environment, and its working fine with the backup running every 5 minutes after i shutdown CS server .

Just a note: It works with databases using the Full Recovery model but doesn’t work with databases set to the Bulk Logged Recovery model.

Best Regards,
Mohamed Ramadan
Data Protection Specialist