Backup stores only log files in Azure Blob Storage

[patrickheinzelmann]

Hi,

I’m trying to use Velero with Azure Blob Storage for the first time. When I run following command velero backup create default-202103081305 --include-namespaces default" , Velero created the folder in the blob storage containing the log.gz.

I tested it with different namespaces. Only one time, Velero has created velero-backup.json and the tar.gz with the data. In all other tests, the backup info had the value Failed for the phase. The log failed contained only messages of type info.

Name:         default-202103081305
Namespace:    velero
Labels:       velero.io/storage-location=default
Annotations:  velero.io/source-cluster-k8s-gitversion=v1.17.13
              velero.io/source-cluster-k8s-major-version=1
              velero.io/source-cluster-k8s-minor-version=17
Phase:  Failed (run `velero backup logs default-202103081305` for more information)
Errors:    0
Warnings:  1
Namespaces:
  Included:  default
  Excluded:  <none>
Resources:
  Included:        *
  Excluded:        <none>
  Cluster-scoped:  auto
Label selector:  <none>
Storage Location:  default
Velero-Native Snapshot PVs:  auto
TTL:  720h0m0s
Hooks:  <none>
Backup Format Version:  1.1.0
Started:    2021-03-08 14:05:41 +0100 CET
Completed:  2021-03-08 14:05:50 +0100 CET
Expiration:  2021-04-07 15:05:41 +0200 CEST
Total items to be backed up:  76
Items backed up:              76
Velero-Native Snapshots: <none included>

The connection to Azure blob Storage seems to be ok as the Velero is creating the folders and logs. One run contained also the backup info (velero-backup.json and xxxxx.tar.gz).

time="2021-03-08T21:32:27Z" level=info msg="Checking for existing backup locations ready to be verified; there needs to be at least 1 backup location available" controller=backupstoragelocation logSource="pkg/controller/backupstoragelocation_controller.go:58"
time="2021-03-08T21:32:28Z" level=info msg="Checking for existing backup locations ready to be verified; there needs to be at least 1 backup location available" controller=backupstoragelocation logSource="pkg/controller/backupstoragelocation_controller.go:58"
time="2021-03-08T21:32:28Z" level=info msg="No backup locations were ready to be verified" controller=backupstoragelocation logSource="pkg/controller/backupstoragelocation_controller.go:120"
time="2021-03-08T21:33:28Z" level=info msg="Checking for existing backup locations ready to be verified; there needs to be at least 1 backup location available" controller=backupstoragelocation logSource="pkg/controller/backupstoragelocation_controller.go:58"
time="2021-03-08T21:33:28Z" level=info msg="Checking for existing backup locations ready to be verified; there needs to be at least 1 backup location available" controller=backupstoragelocation logSource="pkg/controller/backupstoragelocation_controller.go:58"
time="2021-03-08T21:33:28Z" level=info msg="No backup locations were ready to be verified" controller=backupstoragelocation logSource="pkg/controller/backupstoragelocation_controller.go:120"

Here is the info from velero backup-location get

NAME      PROVIDER   BUCKET/PREFIX   PHASE       LAST VALIDATED                  ACCESS MODE
default   azure      velero          Available   2021-03-08 22:36:29 +0100 CET   ReadWrite

As I understand the log entries related to the backup location is related to following issue: vmware-tanzu/helm-charts#168

Any idea why Velero is only adding the log files at the Azure Blob Storage?

Patrick

[dsu-igeek]

Check the memory limit on the Velero pod ( kubectl describe -n velero deployment.apps/velero). You should see:
Limits:
cpu: 1
memory: 512Mi

If it's 256Mi, it needs to be increased for the Azure plug-in to work properly. This was fixed in Velero 1.5.3.