Regarding SAP HANA, we’ve got two sites, first one being replicating its SAP HANA to the second (using HANA replication).
With commvault, how can we manage this type of scenario ? Do we only need to back up data in the first site, or do we need to implement another MA on the second site to back up the replicated data also ? It's more of a design concern.
If you are not worried about your DB failing over to the secondary node and don’t need to run backups on the second, you can simply backup on the first node.
However, if your DB is designed to be failed over to the secondary(either planned or unplanned), and you don’t want the backups to be interrupted when a failover occurs, you would need to configure replication aware instance as it’s documented below.
And if your primary and secondary are in different physical locations and need to use different MA and storage for backups, you can also configure the Region based backups using the below procedure.
If you are not worried about your DB failing over to the secondary node and don’t need to run backups on the second, you can simply backup on the first node.
However, if your DB is designed to be failed over to the secondary(either planned or unplanned), and you don’t want the backups to be interrupted when a failover occurs, you would need to configure replication aware instance as it’s documented below.
And if your primary and secondary are in different physical locations and need to use different MA and storage for backups, you can also configure the Region based backups using the below procedure.
If you are not worried about your DB failing over to the secondary node and don’t need to run backups on the second, you can simply backup on the first node.
However, if your DB is designed to be failed over to the secondary(either planned or unplanned), and you don’t want the backups to be interrupted when a failover occurs, you would need to configure replication aware instance as it’s documented below.
And if your primary and secondary are in different physical locations and need to use different MA and storage for backups, you can also configure the Region based backups using the below procedure.
If you are not worried about your DB failing over to the secondary node and don’t need to run backups on the second, you can simply backup on the first node.
However, if your DB is designed to be failed over to the secondary(either planned or unplanned), and you don’t want the backups to be interrupted when a failover occurs, you would need to configure replication aware instance as it’s documented below.
And if your primary and secondary are in different physical locations and need to use different MA and storage for backups, you can also configure the Region based backups using the below procedure.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.