Skip to content

Commit 6d0781f

Browse files
authored
Update azure-kubernetes-service-backup-troubleshoot.md
1 parent ddefe1a commit 6d0781f

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/backup/azure-kubernetes-service-backup-troubleshoot.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -174,7 +174,7 @@ These error codes appear due to issues on the Backup Extension installed in the
174174
2. CPU: requests - 500m, limits - 1000m
175175
```
176176

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.
178178

179179
**Recommended action**: To ensure successful backup and restore operations, manually update the resource settings for the extension pods by following these steps:
180180

@@ -316,23 +316,23 @@ These error codes can appear while you enable AKS backup to store backups in a v
316316

317317
**Cause**: Namespaces provided in Backup Configuration is missing while performing backups. Either the namespace was wrongly provided or has been deleted.
318318

319-
**Recommended action**: Check if the Namespaces to be backed up are correctly provided.
319+
**Recommended action**: Check if the Namespaces to be backed-up are correctly provided.
320320

321321
### UserErrorPVCHasNoVolume
322322

323323
**Error code**: UserErrorPVCHasNoVolume
324324

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.
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.
326326

327-
**Recommended action**: Attach a volume to the PVC, if it needs to be backed up.
327+
**Recommended action**: Attach a volume to the PVC, if it needs to be backed-up.
328328

329329
### UserErrorPVCNotBoundToVolume
330330

331331
**Error code**: UserErrorPVCNotBoundToVolume
332332

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.
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.
334334

335-
**Recommended action**: Attach a volume to the PVC, if it needs to be backed up.
335+
**Recommended action**: Attach a volume to the PVC, if it needs to be backed-up.
336336

337337
### UserErrorPVNotFound
338338

@@ -362,7 +362,7 @@ These error codes can appear while you enable AKS backup to store backups in a v
362362

363363
**Error code**: LinkedAuthorizationFailed
364364

365-
**Cause**: To perform a restore operation, user needs to have a **read** permission over the backed up AKS cluster.
365+
**Cause**: To perform a restore operation, user needs to have a **read** permission over the backed-up AKS cluster.
366366

367367
**Recommended action**: Assign Reader role on the source AKS cluster and then proceed to perform the restore operation.
368368

0 commit comments

Comments
 (0)