AWS sap documentation change
Summary
Reformatted table structure, updated link syntax from markdown to alternative format, and adjusted line breaks. Content changes include minor reorganization of disaster recovery scenarios (e.g., moving 'malicious activities' reference) but no substantive security additions.
Security assessment
The changes primarily involve formatting adjustments and link syntax updates. While 'malicious activities' is mentioned in disaster recovery context, this was already present in the original text. No new security vulnerabilities, mitigations, or features are introduced.
Diff
diff --git a/sap/latest/sap-hana/hana-ops-ha-dr-testing.md b/sap/latest/sap-hana/hana-ops-ha-dr-testing.md index c161dbbad..8fa610f7d 100644 --- a//sap/latest/sap-hana/hana-ops-ha-dr-testing.md +++ b//sap/latest/sap-hana/hana-ops-ha-dr-testing.md @@ -30,4 +30,3 @@ The following table provides an overview of different failures scenarios for the -Availability Zone/network failure | Low | ~o (uncommitted transactions) | Time to detect failure and failover (automated) | Region -Core service failure | Low | o | Dependent on failure | Region -**Disaster recovery** | Corruption/accidental deletion/malicious activities/faulty code deployment | Low | Last consistent restore point before failure | Time to detect failure and failover (manual) | Cross-Region -Region failure | Very low | Replication delay | Time to detect failure and make a decision to invoke disaster recovery and takeover | Cross-Region +Availability Zone/network failure | Low | ~o (uncommitted transactions) | Time to detect failure and failover (automated) | Region | Core service failure +Low | o | Dependent on failure | Region | **Disaster recovery** | Corruption/accidental deletion/malicious activities/faulty code deployment +Low | Last consistent restore point before failure | Time to detect failure and failover (manual) | Cross-Region | Region failure | Very low @@ -37 +36 @@ For SAP HANA systems without high availability implementation, the core critical - * Use Amazon EC2 automatic recovery or host recovery to bring the SAP HANA system up on new host. For more information, see [Amazon EC2 recovery options](https://docs.aws.amazon.com/sap/latest/sap-hana/hana-ops-ha-dr.html#ec2-recovery-hana-hadr). + * Use Amazon EC2 automatic recovery or host recovery to bring the SAP HANA system up on new host. For more information, see {https---docs-aws-amazon-com-sap-latest-sap-hana-hana-ops-ha-dr-html-ec2-recovery-hana-hadr}[Amazon EC2 recovery options]. @@ -94 +93 @@ For SAP HANA high availability deployment with pacemaker cluster on **RHEL** on -You can start by preparing a client connections or interfaces list that includes all critical connections to the target SAP system. Identify the modifications required in your connection configuration to point to a virtual IP address or load balancing mechanism. During testing, each connection must be validated for connectivity, time taken to detect new connection, and loss of locks set by the application, before the cluster performs a failover. For more information, see [Client redirect options](https://docs.aws.amazon.com/sap/latest/sap-hana/hana-ops-ha-dr-hsr.html#hsr-client-redirect). +You can start by preparing a client connections or interfaces list that includes all critical connections to the target SAP system. Identify the modifications required in your connection configuration to point to a virtual IP address or load balancing mechanism. During testing, each connection must be validated for connectivity, time taken to detect new connection, and loss of locks set by the application, before the cluster performs a failover. For more information, see {https---docs-aws-amazon-com-sap-latest-sap-hana-hana-ops-ha-dr-hsr-html-hsr-client-redirect}[Client redirect options]. @@ -98 +97 @@ You can start by preparing a client connections or interfaces list that includes -When a failover is triggered in a multi-tier SAP HANA system replication setup and the secondary database takes over the role of primary, the replication continues on the tertiary system. However, once the fault with the original primary system is rectified and the system is made available again, manual intervention are be required to complete the reverse replication requirements from the new primary SAP HANA database to the original primary. These manual steps are needed for SAP HANA databases that do not support (lower than SAP HANA 2.0) multi-target replication. For more information, see [SAP HANA multi-target replication](https://docs.aws.amazon.com/sap/latest/sap-hana/hana-ops-ha-dr-hsr.html#hsr-multi-target). +When a failover is triggered in a multi-tier SAP HANA system replication setup and the secondary database takes over the role of primary, the replication continues on the tertiary system. However, once the fault with the original primary system is rectified and the system is made available again, manual intervention are be required to complete the reverse replication requirements from the new primary SAP HANA database to the original primary. These manual steps are needed for SAP HANA databases that do not support (lower than SAP HANA 2.0) multi-target replication. For more information, see {https---docs-aws-amazon-com-sap-latest-sap-hana-hana-ops-ha-dr-hsr-html-hsr-multi-target}[SAP HANA multi-target replication].