Skip to content

Commit a3940b3

Browse files
more updates
1 parent 468e9dc commit a3940b3

File tree

4 files changed

+7
-47
lines changed

4 files changed

+7
-47
lines changed

articles/backup/index.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -69,8 +69,8 @@ landingContent:
6969
url: blob-backup-overview.md
7070
- text: Selective Disk backup with Enhanced policy for Azure VM (preview)
7171
url: selective-disk-backup-restore.md
72-
- text: SAP HANA System Replication backup (preview)
73-
url: sap-hana-database-about.md#back-up-a-hana-system-with-replication-enabled-preview
72+
- text: SAP HANA System Replication backup
73+
url: sap-hana-database-about.md#back-up-a-hana-system-with-replication-enabled
7474
- text: Cross Region Restore for PostgreSQL (preview)
7575
url: backup-vault-overview.md#cross-region-restore-support-for-postgresql-using-azure-backup-preview
7676

@@ -122,7 +122,7 @@ landingContent:
122122
links:
123123
- text: Back up SAP HANA databases on Azure VMs
124124
url: backup-azure-sap-hana-database.md
125-
- text: Back up SAP HSR databases on Azure VMs (preview)
125+
- text: Back up SAP HSR databases on Azure VMs
126126
url: sap-hana-database-with-hana-system-replication-backup.md
127127
- text: Back up SAP HANA databases' instance snapshots on Azure VMs (preview)
128128
url: sap-hana-database-instances-backup.md

articles/backup/sap-hana-database-about.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ You can use [an Azure VM backup](backup-azure-vms-introduction.md) to back up th
7575

7676
1. Restore the database into the VM from the [Azure SAP HANA database backup](sap-hana-db-restore.md#restore-to-a-point-in-time-or-to-a-recovery-point) to your intended point in time.
7777

78-
## Back up a HANA system with replication enabled (preview)
78+
## Back up a HANA system with replication enabled
7979

8080
Azure Backup now supports backing up databases that have HSR enabled. This means that backups are managed automatically when a failover occurs, which eliminates the necessity for manual intervention. Backup also offers immediate protection with no remedial full backups, so you can protect HANA instances or HSR setup nodes as a single HSR container.
8181

articles/backup/sap-hana-database-with-hana-system-replication-backup.md

Lines changed: 2 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -237,47 +237,7 @@ Backups run in accordance with the policy schedule. Learn how to [run an on-dema
237237

238238
You can run an on-demand backup using SAP HANA native clients to local file-system instead of Backint. Learn more how to [manage operations using SAP native clients](sap-hana-database-manage.md#manage-operations-using-sap-hana-native-clients).
239239

240-
241-
## Possible scenarios to protect HSR nodes on Azure Backup
242-
243-
You can now switch the protection of SAP HANA database on Azure VM (standalone) on Azure Backup to HSR. If you’ve already configured HSR and protecting only the primary node using Azure Backup, you can modify the configuration to protect both primary and secondary nodes.
244-
245-
### Two standalone/HSR nodes never protected using SAP HANA Database backup on Azure VM
246-
247-
1. (Mandatory) [Run the latest preregistration script on both primary and secondary VM nodes](#run-the-preregistration-script).
248-
249-
>[!Note]
250-
>HSR-based attributes are added to the latest preregistration script - //link here )
251-
252-
1. Configure HSR manually or using any clustering tools, such as **pacemaker**,
253-
254-
Skip to the next step if HSR configuration is already complete.
255-
256-
1. Discover and configure backup for those VMs.
257-
258-
>[!Note]
259-
>For HSR deployments, Protected Instance cost is charged to HSR logical container (two nodes - primary and secondary) will form a single HSR logical container.
260-
261-
1. Before a planned failover, [ensure that both VMs/Nodes are registered to the vault (physical and logical registration)](sap-hana-database-manage.md#verify-the-registration-status-of-vms-or-nodes-to-the-vault).
262-
263-
### Two standalone VMs/ One standalone VM already protected using SAP HANA Database backup on Azure VM
264-
265-
1. To stop backup and retain data, go to the *vault* > **Backup Items** > **SAP HANA in Azure VM**, and then select **View Details** > **Stop backup** > **Retain backup data** > **Stop backup**.
266-
1. (Mandatory) [Run the latest preregistration script on both primary and secondary VM nodes](#run-the-preregistration-script).
267-
268-
>[!Note]
269-
>HSR-based attributes are added to the latest preregistration script - //link here )
270-
271-
1. Configure HSR manually or using any clustering tools like pacemaker.
272-
273-
1. Discover the VMs and configure backup on HSR logical instance.
274-
275-
>[!Note]
276-
>For HSR deployments, Protected Instance cost will be charged to HSR logical container (two nodes - primary and / secondary) will form a single HSR logical container.
277-
278-
1. Before a planned failover, [ensure that both VMs/Nodes are registered to the vault (physical and logical registration)](sap-hana-database-manage.md#verify-the-registration-status-of-vms-or-nodes-to-the-vault).
279-
280240
## Next steps
281241

282-
- [Restore SAP HANA System Replication databases on Azure VMs (preview)](sap-hana-database-restore.md)
283-
- [About backing up SAP HANA System Replication databases on Azure VMs (preview)](sap-hana-database-about.md#back-up-a-hana-system-with-replication-enabled-preview)
242+
- [Restore SAP HANA System Replication databases on Azure VMs](sap-hana-database-restore.md)
243+
- [About backing up SAP HANA System Replication databases on Azure VMs](sap-hana-database-about.md#back-up-a-hana-system-with-replication-enabled)

articles/backup/whats-new.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ For more information, see [Back up a HANA system with replication enabled](sap-h
7474

7575
Azure Backup allows you to replicate your backups to an additional Azure paired region by using Geo-redundant Storage (GRS) to protect your backups from regional outages. When you enable the backups with GRS, the backups in the secondary region become accessible only when Microsoft declares an outage in the primary region.
7676

77-
For more information, see [Cross Region Restore support for PostgreSQL using Azure Backup (preview)](backup-vault-overview.md#cross-region-restore-support-for-postgresql-using-azure-backup-preview).
77+
For more information, see [Cross Region Restore support for PostgreSQL using Azure Backup](backup-vault-overview.md#cross-region-restore-support-for-postgresql-using-azure-backup).
7878

7979
## Microsoft Azure Backup Server v4 is now generally available
8080

0 commit comments

Comments
 (0)