You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-stack/operator/azure-site-recovery-known-issues.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: ronmiab
5
5
ms.author: robess
6
6
ms.topic: troubleshooting
7
7
ms.custom: linux-related-content
8
-
ms.date: 04/03/2025
8
+
ms.date: 04/25/2025
9
9
ms.reviewer: rtiberiu
10
10
ms.lastreviewed: 04/25/2024
11
11
---
@@ -31,20 +31,20 @@ When you try to protect a VM with a disk of 1023Gb, the following behavior occur
31
31
32
32
The current workaround for this issue is to create a new disk (of 1,022 GB or less), attach it to your source VM, copy the data from the 1,023 GB disk to the new one, and then remove the 1,023 GB disk from the source VM. Once this procedure is done, and the VM has all disks smaller or equal to 1,022 GB, you can enable the protection using Azure Site Recovery.
33
33
34
-
## Re-protection: available data disk slots on appliance
34
+
## Reprotection: available data disk slots on appliance
35
35
36
-
1. Ensure the appliance VM has enough data disk slots, as the replica disks for re-protection are attached to the appliance.
36
+
1. Ensure the appliance VM has enough data disk slots, as the replica disks for reprotection are attached to the appliance.
37
37
38
-
2. The initial allowed number of disks being re-protected at the same time is 31. The default size of the appliance created from the marketplace item is [Standard_DS4_v2](../user/azure-stack-vm-sizes.md#dsv2-series), which supports up to 32 data disks, and the appliance itself uses one data disk.
38
+
2. The initial allowed number of disks being reprotected at the same time is 31. The default size of the appliance created from the marketplace item is [Standard_DS4_v2](../user/azure-stack-vm-sizes.md#dsv2-series), which supports up to 32 data disks, and the appliance itself uses one data disk.
39
39
40
40
3. If the sum of the protected VMs is greater than 31, perform one of the following actions:
41
-
- Split the VMs that require re-protection into smaller groups to ensure that the number of disks re-protected at the same time doesn't exceed the maximum number of data disks the appliance supports.
41
+
- Split the VMs that require reprotection into smaller groups to ensure that the number of disks reprotected at the same time doesn't exceed the maximum number of data disks the appliance supports.
42
42
- Increase the size of the Azure Site Recovery appliance VM.
43
43
44
44
>[!NOTE]
45
45
> We don't test and validate large VM SKUs for the appliance VM.
46
46
47
-
4. If you're trying to re-protect a VM, but there aren't enough slots on the appliance to hold the replication disks, the error message **An internal error occurred** displays. You can check the number of the data disks currently on the appliance, or sign in to the appliance, go to **Event Viewer**, and open logs for **Azure Site Recovery** under **Applications and Services Logs**:
47
+
4. If you're trying to reprotect a VM, but there aren't enough slots on the appliance to hold the replication disks, the error message **An internal error occurred** displays. You can check the number of the data disks currently on the appliance, or sign in to the appliance, go to **Event Viewer**, and open logs for **Azure Site Recovery** under **Applications and Services Logs**:
48
48
49
49
:::image type="content" source="../operator/media/azure-site-recovery/known-issues/event-viewer.png" alt-text="Sample screenshot of Event Viewer for Azure Site Recovery."lightbox="media/azure-site-recovery/known-issues/event-viewer.png":::
50
50
@@ -83,9 +83,9 @@ The current workaround for this issue is to create a new disk (of 1,022 GB or le
83
83
84
84
:::image type="content" source="../operator/media/azure-site-recovery/known-issues/mobility-agent-update.png" alt-text="Sample screenshot of mobility agent update check."lightbox="media/azure-site-recovery/known-issues/mobility-agent-update.png":::
85
85
86
-
## Re-protect manual resync isn't supported yet
86
+
## Reprotect manual resync isn't supported yet
87
87
88
-
After the re-protect job is complete, the replication is started in sequence. During replication, there may be cases that require a resync, which means a new initial replication is triggered to synchronize all the changes.
88
+
After the reprotect job is complete, the replication is started in sequence. During replication, there may be cases that require a resync, which means a new initial replication is triggered to synchronize all the changes.
89
89
90
90
There are two types of resync:
91
91
@@ -103,7 +103,7 @@ There are two types of resync:
103
103
104
104
## Known issues in PowerShell automation
105
105
106
-
- If you leave `$failbackPolicyName` and `$failbackExtensionName` empty or null, the re-protect can fail. See the following examples:
106
+
- If you leave `$failbackPolicyName` and `$failbackExtensionName` empty or null, the reprotect can fail. See the following examples:
107
107
108
108
:::image type="content" source="../operator/media/azure-site-recovery/known-issues/reprotect-fail-error-1.png" alt-text="Sample screenshot of a VM failed to perform operation error."lightbox="media/azure-site-recovery/known-issues/reprotect-fail-error-1.png":::
109
109
@@ -147,5 +147,5 @@ To avoid this issue, make sure to first remove the protection from all items in
147
147
148
148
## Next steps
149
149
150
-
-[Azure Site Recovery on Azure Stack Hub](azure-site-recovery-overview.md)
151
-
-[Azure Site Recovery on Azure Stack Hub capacity planning](azure-site-recovery-capacity-planning.md)
150
+
-[Azure Site Recovery on Azure Stack Hub](azure-site-recovery-overview.md).
151
+
-[Azure Site Recovery on Azure Stack Hub capacity planning](azure-site-recovery-capacity-planning.md).
Copy file name to clipboardExpand all lines: azure-stack/user/pattern-highly-available-kubernetes.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: High availability Kubernetes pattern using Azure and Azure Stack Hub
3
3
description: Learn how a Kubernetes cluster solution provides high availability using Azure and Azure Stack Hub.
4
4
author: ronmiab
5
5
ms.topic: article
6
-
ms.date: 04/03/2025
6
+
ms.date: 04/25/2025
7
7
ms.author: robess
8
8
ms.reviewer: bryanla
9
9
ms.lastreviewed: 12/03/2020
@@ -115,7 +115,7 @@ The Kubernetes cluster itself consists of, and is built on top of Azure (Stack)
115
115
-[Control plane nodes](/azure/aks/concepts-clusters-workloads#control-plane) (master) provide the core Kubernetes services and orchestration of application workloads.
116
116
-[Worker nodes](/azure/aks/concepts-clusters-workloads#nodes-and-node-pools) (worker) run your application workloads.
117
117
118
-
When selecting VM sizes for the initial deployment, there are several considerations:
118
+
When you select VM sizes for the initial deployment, there are several considerations:
119
119
120
120
-**Cost** - When planning your worker nodes, keep in mind the overall cost per VM you incur. For example, if your application workloads require limited resources, you should plan to deploy smaller sized VMs. Azure Stack Hub, like Azure, is normally billed on a consumption basis, so appropriately sizing the VMs for Kubernetes roles is crucial to optimizing consumption costs.
121
121
@@ -125,7 +125,7 @@ When selecting VM sizes for the initial deployment, there are several considerat
125
125
126
126
Scaling is done manually using the AKS Engine helper VM that was used to deploy the Kubernetes cluster initially. For more information, see [Scaling Kubernetes clusters](https://github.com/Azure/aks-engine/blob/master/docs/topics/scale.md)
127
127
128
-
-**Quotas** - Consider the [quotas](/azure-stack/operator/azure-stack-quota-types) you've configured when planning out an AKS deployment on your Azure Stack Hub. Make sure each [subscription](/azure-stack/operator/service-plan-offer-subscription-overview) has the proper plans and the quotas configured. The subscription needs to accommodate the amount of compute, storage, and other services needed for your clusters as they scale out.
128
+
-**Quotas** - Consider the [quotas](/azure-stack/operator/azure-stack-quota-types) you configure when planning out an AKS deployment on your Azure Stack Hub. Make sure each [subscription](/azure-stack/operator/service-plan-offer-subscription-overview) has the proper plans and the quotas configured. The subscription needs to accommodate the amount of compute, storage, and other services needed for your clusters as they scale out.
129
129
130
130
-**Application workloads** - Refer to the [Clusters and workloads concepts](/azure/aks/concepts-clusters-workloads#nodes-and-node-pools) in the Kubernetes core concepts for Azure Kubernetes Service document. This article helps you scope the proper VM size based on the compute and memory needs of your application.
131
131
@@ -151,7 +151,7 @@ For the application layer, the most important consideration is whether the appli
151
151
152
152
Exposing an application using a public IP via a Load Balancer or an Ingress Controller doesn't nessecarily mean that the application is now accessible via the Internet. It's possible for Azure Stack Hub to have a public IP address that is only visible on the local intranet - not all public IPs are truly Internet-facing.
153
153
154
-
The previous block considers ingress traffic to the application. Another topic that must be considered for a successful Kubernetes deployment is outbound/egress traffic. Here are a few use cases that require egress traffic:
154
+
The previous block considers ingress traffic to the application. Another consideration for a successful Kubernetes deployment is outbound/egress traffic. Here are a few use cases that require egress traffic:
155
155
156
156
- Pulling Container Images stored on DockerHub or Azure Container Registry
157
157
- Retrieving Helm Charts
@@ -191,7 +191,7 @@ In our architecture, these layers were considered:
191
191
192
192
**Configuration**
193
193
194
-
Configuration includes the configuration of Azure Stack Hub, AKS Engine, and the Kubernetes cluster itself. The configuration should be automated as much as possible, and stored as Infrastructure-as-Code in a Git-based version control system like Azure DevOps or GitHub. These settings cannot easily be synchronized across multiple deployments. Therefore we recommend storing and applying configuration from the outside, and using DevOps pipeline.
194
+
Configuration includes the configuration of Azure Stack Hub, AKS Engine, and the Kubernetes cluster itself. The configuration should be automated as much as possible, and stored as Infrastructure-as-Code in a Git-based version control system like Azure DevOps or GitHub. These settings can't easily be synchronized across multiple deployments. Therefore we recommend storing and applying configuration from the outside, and using DevOps pipeline.
195
195
196
196
**Application**
197
197
@@ -372,7 +372,7 @@ There are Microsoft Partner solutions that can extend the capabilities of Azure
372
372
373
373
## Storage and data solutions
374
374
375
-
As described in [Data and storage considerations](#data-and-storage-considerations), Azure Stack Hub currently doesn't have a native solution to replicate storage across multiple instances. Unlike Azure, the capability of replicating storage across multiple regions does not exist. In Azure Stack Hub, each instance is its own distinct cloud. However, solutions are available from Microsoft Partners that enable storage replication across Azure Stack Hubs and Azure.
375
+
As described in [Data and storage considerations](#data-and-storage-considerations), Azure Stack Hub currently doesn't have a native solution to replicate storage across multiple instances. Unlike Azure, the capability of replicating storage across multiple regions doesn't exist. In Azure Stack Hub, each instance is its own distinct cloud. However, solutions are available from Microsoft Partners that enable storage replication across Azure Stack Hubs and Azure.
0 commit comments