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: articles/backup/azure-kubernetes-service-backup-troubleshoot.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -174,7 +174,7 @@ These error codes appear due to issues on the Backup Extension installed in the
174
174
2. CPU: requests - 500m, limits - 1000m
175
175
```
176
176
177
-
However, if the number of resources in the cluster exceeds 1000, the pods may require additional CPU and memory beyond the default reservation. If the required resources exceed the allocated limits, you might encounter an BackupPluginPodRestarted due to OOMKilled (Out of Memory) error during backup jobs.
177
+
However, if the number of resources in the cluster exceeds 1000, the pods may require additional CPU and memory beyond the default reservation. If the required resources exceed the allocated limits, you might encounter a BackupPluginPodRestarted error due to OOMKilled (Out of Memory) error during backup jobs.
178
178
179
179
**Recommended action**: To ensure successful backup and restore operations, manually update the resource settings for the extension pods by following these steps:
180
180
@@ -316,23 +316,23 @@ These error codes can appear while you enable AKS backup to store backups in a v
316
316
317
317
**Cause**: Namespaces provided in Backup Configuration is missing while performing backups. Either the namespace was wrongly provided or has been deleted.
318
318
319
-
**Recommended action**: Check if the Namespaces to be backedup are correctly provided.
319
+
**Recommended action**: Check if the Namespaces to be backed-up are correctly provided.
320
320
321
321
### UserErrorPVCHasNoVolume
322
322
323
323
**Error code**: UserErrorPVCHasNoVolume
324
324
325
-
**Cause**: The Persistent Volume Claim (PVC) in context doesn't have a Persistent Volume attached to it. So, the PVC won't be backedup.
325
+
**Cause**: The Persistent Volume Claim (PVC) in context doesn't have a Persistent Volume attached to it. So, the PVC won't be backed-up.
326
326
327
-
**Recommended action**: Attach a volume to the PVC, if it needs to be backedup.
327
+
**Recommended action**: Attach a volume to the PVC, if it needs to be backed-up.
328
328
329
329
### UserErrorPVCNotBoundToVolume
330
330
331
331
**Error code**: UserErrorPVCNotBoundToVolume
332
332
333
-
**Cause**: The PVC in context is in *Pending* state and doesn't have a Persistent Volume attached to it. So, the PVC won't be backedup.
333
+
**Cause**: The PVC in context is in *Pending* state and doesn't have a Persistent Volume attached to it. So, the PVC won't be backed-up.
334
334
335
-
**Recommended action**: Attach a volume to the PVC, if it needs to be backedup.
335
+
**Recommended action**: Attach a volume to the PVC, if it needs to be backed-up.
336
336
337
337
### UserErrorPVNotFound
338
338
@@ -362,7 +362,7 @@ These error codes can appear while you enable AKS backup to store backups in a v
362
362
363
363
**Error code**: LinkedAuthorizationFailed
364
364
365
-
**Cause**: To perform a restore operation, user needs to have a **read** permission over the backedup AKS cluster.
365
+
**Cause**: To perform a restore operation, user needs to have a **read** permission over the backed-up AKS cluster.
366
366
367
367
**Recommended action**: Assign Reader role on the source AKS cluster and then proceed to perform the restore operation.
0 commit comments