Skip to content

Commit 71d554a

Browse files
committed
Correcting links with planning guide re-work
1 parent d35be96 commit 71d554a

6 files changed

+55
-80
lines changed

articles/sap/workloads/deployment-guide.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -151,9 +151,9 @@ ms.author: sedusch
151151
[deployment-guide-install-vm-agent-windows]:deployment-guide.md#b2db5c9a-a076-42c6-9835-16945868e866
152152
[deployment-guide-troubleshooting-chapter]:deployment-guide.md#564adb4f-5c95-4041-9616-6635e83a810b (Checks and Troubleshooting)
153153

154-
[deploy-template-cli]:../../../resource-group-template-deploy-cli.md
155-
[deploy-template-portal]:../../../resource-group-template-deploy-portal.md
156-
[deploy-template-powershell]:../../../resource-group-template-deploy.md
154+
[deploy-template-cli]:../../resource-group-template-deploy-cli.md
155+
[deploy-template-portal]:../../resource-group-template-deploy-portal.md
156+
[deploy-template-powershell]:../../resource-group-template-deploy.md
157157

158158
[dr-guide-classic]:https://go.microsoft.com/fwlink/?LinkID=521971
159159

@@ -179,13 +179,13 @@ ms.author: sedusch
179179
[msdn-set-Azvmaemextension]:/powershell/module/az.compute/set-azvmaemextension
180180

181181
[planning-guide]:planning-guide.md (Azure Virtual Machines planning and implementation for SAP)
182-
[planning-guide-1.2]:planning-guide.md#e55d1e22-c2c8-460b-9897-64622a34fdff (Resources)
182+
[planning-guide-1.2]:planning-guide.md#resources (Resources)
183183
[planning-guide-11]:planning-guide.md#7cf991a1-badd-40a9-944e-7baae842a058 (High availability and disaster recovery for SAP NetWeaver running on Azure Virtual Machines)
184184
[planning-guide-11.4.1]:planning-guide.md#5d9d36f9-9058-435d-8367-5ad05f00de77 (High availability for SAP Application Servers)
185185
[planning-guide-11.5]:planning-guide.md#4e165b58-74ca-474f-a7f4-5e695a93204f (Using Autostart for SAP instances)
186186
[planning-guide-2.1]:planning-guide.md#1625df66-4cc6-4d60-9202-de8a0b77f803 (Cloud-only - Virtual Machine deployments in Azure without dependencies on the on-premises customer network)
187187
[planning-guide-2.2]:planning-guide.md#f5b3b18c-302c-4bd8-9ab2-c388f1ab3d10 (Cross-premises - Deployment of single or multiple SAP VMs in Azure fully integrated with the on-premises network)
188-
[planning-guide-3.1]:planning-guide.md#be80d1b9-a463-4845-bd35-f4cebdb5424a (Azure regions)
188+
[planning-guide-3.1]:planning-guide.md##azure-geographies-and-regions (Azure regions) [dfla](./planning-guide.md#resources)
189189
[planning-guide-3.2.1]:planning-guide.md#df49dc09-141b-4f34-a4a2-990913b30358 (Fault domains)
190190
[planning-guide-3.2.2]:planning-guide.md#fc1ac8b2-e54a-487c-8581-d3cc6625e560 (Upgrade domains)
191191
[planning-guide-3.2.3]:planning-guide.md#18810088-f9be-4c97-958a-27996255c665 (Azure availability sets)
@@ -224,10 +224,10 @@ ms.author: sedusch
224224
[planning-guide-figure-600]:media/virtual-machines-shared-sap-planning-guide/600-s2s-details.png
225225
[planning-guide-figure-700]:media/virtual-machines-shared-sap-planning-guide/700-decision-tree-deploy-to-azure.png
226226
[planning-guide-figure-800]:media/virtual-machines-shared-sap-planning-guide/800-portal-vm-overview.png
227-
[planning-guide-microsoft-azure-networking]:planning-guide.md#61678387-8868-435d-9f8c-450b2424f5bd (Microsoft Azure networking)
228-
[planning-guide-storage-microsoft-azure-storage-and-data-disks]:planning-guide.md#a72afa26-4bf4-4a25-8cf7-855d6032157f (Storage: Microsoft Azure Storage and data disks)
227+
[planning-guide-microsoft-azure-networking]:planning-guide.md#azure-networking (Microsoft Azure networking)
228+
[planning-guide-storage-microsoft-azure-storage-and-data-disks]:planning-guide-storage.md (Storage: Microsoft Azure Storage and data disks)
229229

230-
[resource-group-authoring-templates]:../../../resource-group-authoring-templates.md
230+
[resource-group-authoring-templates]:../../resource-group-authoring-templates.md
231231
[resource-group-overview]:../../azure-resource-manager/management/overview.md
232232
[resource-groups-networking]:../../networking/network-overview.md
233233
[sap-pam]:https://support.sap.com/pam (SAP Product Availability Matrix)
@@ -307,15 +307,15 @@ ms.author: sedusch
307307
[howto-assign-access-powershell]:../../active-directory/managed-identities-azure-resources/howto-assign-access-powershell.md
308308
[howto-assign-access-cli]:../../active-directory/managed-identities-azure-resources/howto-assign-access-cli.md
309309

310-
[!INCLUDE [learn-about-deployment-models](../../../includes/learn-about-deployment-models-rm-include.md)]
310+
[!INCLUDE [learn-about-deployment-models](../../includes/learn-about-deployment-models-rm-include.md)]
311311

312312
Azure Virtual Machines is the solution for organizations that need compute and storage resources, in minimal time, and without lengthy procurement cycles. You can use Azure Virtual Machines to deploy classical applications, like SAP NetWeaver-based applications, in Azure. Extend an application's reliability and availability without additional on-premises resources. Azure Virtual Machines supports cross-premises connectivity, so you can integrate Azure Virtual Machines into your organization's on-premises domains, private clouds, and SAP system landscape.
313313

314-
In this article, we cover the steps to deploy SAP applications on virtual machines (VMs) in Azure, including alternate deployment options and troubleshooting. This article builds on the information in [Azure Virtual Machines planning and implementation for SAP NetWeaver][planning-guide]. It also complements SAP installation documentation and SAP Notes, which are the primary resources for installing and deploying SAP software.
314+
In this article, we cover the steps to deploy SAP applications on virtual machines (VMs) in Azure, including alternate deployment options and troubleshooting. This article builds on the information in [Azure Virtual Machines planning and implementation for SAP NetWeaver](./planning-guide.md). It also complements SAP installation documentation and SAP Notes, which are the primary resources for installing and deploying SAP software.
315315

316316
## Prerequisites
317317

318-
[!INCLUDE [updated-for-az](../../../includes/updated-for-az.md)]
318+
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
319319

320320
Setting up an Azure virtual machine for SAP software deployment involves multiple steps and resources. Before you start, make sure that you meet the prerequisites for installing SAP software on virtual machines in Azure.
321321

@@ -561,10 +561,10 @@ The wizard guides you through setting the required parameters to create the virt
561561
* **Username and password** or **SSH public key**: Enter the username and password of the user that is created during the provisioning. For a Linux virtual machine, you can enter the public Secure Shell (SSH) key that you use to sign in to the machine.
562562
* **Subscription**: Select the subscription that you want to use to provision the new virtual machine.
563563
* **Resource group**: The name of the resource group for the VM. You can enter either the name of a new resource group or the name of a resource group that already exists.
564-
* **Location**: Where to deploy the new virtual machine. If you want to connect the virtual machine to your on-premises network, make sure you select the location of the virtual network that connects Azure to your on-premises network. For more information, see [Microsoft Azure networking][planning-guide-microsoft-azure-networking] in [Azure Virtual Machines planning and implementation for SAP NetWeaver][planning-guide].
564+
* **Location**: Where to deploy the new virtual machine. If you want to connect the virtual machine to your on-premises network, make sure you select the location of the virtual network that connects Azure to your on-premises network. For more information, see [Microsoft Azure networking](./planning-guide.md#azure-networking) in [Azure Virtual Machines planning and implementation for SAP NetWeaver][planning-guide].
565565
1. **Size**:
566566

567-
For a list of supported VM types, see SAP Note [1928533]. Be sure you select the correct VM type if you want to use Azure Premium Storage. Not all VM types support Premium Storage. For more information, see [Storage: Microsoft Azure Storage and data disks][planning-guide-storage-microsoft-azure-storage-and-data-disks] and [Azure storage for SAP workloads](./planning-guide-storage.md) in [Azure Virtual Machines planning and implementation for SAP NetWeaver][planning-guide].
567+
For a list of supported VM types, see SAP Note [1928533]. Be sure you select the correct VM type if you want to use Azure Premium Storage. Not all VM types support Premium Storage. For more information, see [Azure storage for SAP workloads](./planning-guide-storage.md).
568568

569569
1. **Settings**:
570570
* **Storage**
@@ -575,7 +575,7 @@ The wizard guides you through setting the required parameters to create the virt
575575
* **Public IP address**: Select the public IP address that you want to use, or enter parameters to create a new public IP address. You can use a public IP address to access your virtual machine over the Internet. Make sure that you also create a network security group to help secure access to your virtual machine.
576576
* **Network security group**: For more information, see [Control network traffic flow with network security groups][virtual-networks-nsg].
577577
* **Extensions**: You can install virtual machine extensions by adding them to the deployment. You do not need to add extension in this step. The extensions required for SAP support are installed later. See chapter [Configure the Azure Extension for SAP][deployment-guide-4.5] in this guide.
578-
* **High Availability**: Select an availability set, or enter the parameters to create a new availability set. For more information, see [Azure availability sets][planning-guide-3.2.3].
578+
* **High Availability**: Select an availability set, or enter the parameters to create a new availability set. For more information, see [Azure availability sets](./planning-guide.md#availability-sets).
579579
* **Monitoring**
580580
* **Boot diagnostics**: You can select **Disable** for boot diagnostics.
581581
* **Guest OS diagnostics**: You can select **Disable** for monitoring diagnostics.

articles/sap/workloads/disaster-recovery-overview-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.date: 12/06/2022
1616

1717
Many organizations running critical business applications on Azure set up both High Availability (HA) and Disaster Recovery (DR) strategy. The purpose of high availability is to increase the SLA of business systems by eliminating single points of failure in the underlying system infrastructure. High Availability technologies reduce the effect of unplanned infrastructure failure and help with planned maintenance. Disaster Recovery is defined as policies, tools and procedures to enable the recovery or continuation of vital technology infrastructure and systems following a geographically widespread natural or human-induced disaster.
1818

19-
To achieve [high availability for SAP workload on Azure](sap-high-availability-guide-start.md), virtual machines are typically deployed in an [availability set](planning-guide.md#18810088-f9be-4c97-958a-27996255c665) or in [availability zones](planning-guide.md#availability-zones) to protect applications from infrastructure maintenance or failure within region. But the deployment doesn’t protect applications from widespread disaster within region. So to protect applications from regional disaster, disaster recovery strategy for the applications should be in place. Disaster recovery is a documented and structured approach that is designed to assist an organization in executing the recovery processes in response to a disaster, and to protect or minimize IT services disruption and promote recovery.
19+
To achieve [high availability for SAP workload on Azure](sap-high-availability-guide-start.md), virtual machines are typically deployed in an [availability set](planning-guide.md#availability-sets) or in [availability zones](planning-guide.md#availability-zones) to protect applications from infrastructure maintenance or failure within region. But the deployment doesn’t protect applications from widespread disaster within region. So to protect applications from regional disaster, disaster recovery strategy for the applications should be in place. Disaster recovery is a documented and structured approach that is designed to assist an organization in executing the recovery processes in response to a disaster, and to protect or minimize IT services disruption and promote recovery.
2020

2121
This document provides details on protecting SAP workloads from large scale catastrophe by implementing structured DR approach. The details in this document are presented at an abstract level, based on different Azure services and SAP components. Exact DR strategy and the order of recovery for your SAP workload must be tested, documented and fine tuned regularly. Also, the document focuses on the Azure-to-Azure DR strategy for SAP workload.
2222

0 commit comments

Comments
 (0)