We’re rewarding the question askers & reputations are being recalculated! Read more.
3

can CommVault continue to take its log backups for reliable point-in-time recovery and at the same time that either of the high availability options is enabled, or is there a risk of interference? You can only have one log chain, so Log Shipping and your CommVault log backups will conflict. Log Shipping can co-exist with full/differential backups, and with ...


2

I think you need to revise your question with clarity: Olas scripts meant for following, not for restoring database. Backup DBCC - Integrity Check Maintenance - Index and Statistics Aside from this, you cannot DROP or RESTORE a database while it's part of Availability Group. You can remove a database from availability group with following commands: ...


2

what controls the switching of connections to the new primary node? The Availability group (AG) listener directs incoming connections to either primary or read replica depending on how the AG is configured (whether it allows read requests or not). When a failover occurs, a role reversal happens and a secondary replica transitions to the primary role and ...


2

Log Shipping is taking Log Backups as part of its process, so you don't want another process doing them as well. Just have Commvault pick up those files that the LS_Backup job created. Standard edition 2017 is limited to one DB for AG...not even sure if you can have an on-prem and cloud for the nodes. If your RPO allows it, for this case Log Shipping is ...


1

As far as I know, Service Packs on same major version ( 2014 ) does not have any impacts on these features.


1

Compression is not listed as a restriction in the documentation at Prerequisites, Restrictions, and Recommendations for Always On availability groups, so that is the official reference that indicates it is supported with availability groups. There are no special considerations for configuration, and it does not matter whether synchronous or asynchronous ...


1

"Readable Secondary" AG setting for all the replicas associated to Always On(including current Primary replica) should have setting either as “NO” or “Read-Intent Only” or it should be "NO" only? There should not be any Standalone Database? (not even any third party backup tool database such as "LiteSpeedLocal"). Also the backup should not be ...


1

Log shipping is what we end up using. However licensing dictates that we pay for additional licenses if we use the secondary in any way at all (even to take backups from)...


Only top voted, non community-wiki answers of a minimum length are eligible