Where do I look for backup files?

Archives AWX Project
,
1

I am wondering if there is a problem with my backup of my AWX server. As per the README file I created this file:
BP22006:BACKUP_RESTORE red.crik$ cat backup-awx.yml — apiVersion: awx.ansible.com/v1beta1 kind: AWXBackup metadata: name: awxbackup-2023-04-13 namespace: awx spec: deployment_name: awx-backup-rbc
And then executed:
BP22006:BACKUP_RESTORE red.crik$ kubectl apply -f backup-awx.yml awxbackup.awx.ansible.com/awxbackup-2023-04-13 created
According to the README file the above command created a “backup object in your cluster” and “The resulting pvc will contain a backup tar that can be used to restore to a new deployment. Future backups will also be stored in separate tars on the same pvc.” So I go to my k8 dashboard and I see this new PVC: kubectl describe pvc awx-backup-rbc-backup-claim Name: awx-backup-rbc-backup-claim Namespace: awx StorageClass: local-path Status: Bound Volume: pvc-1be2ff00-767f-4151-afbb-8047f934a221 Labels: app.kubernetes.io/component=awx app.kubernetes.io/managed-by=awx-operator app.kubernetes.io/name=awxbackup-2023-04-13 app.kubernetes.io/operator-version=1.1.0 app.kubernetes.io/part-of=awxbackup-2023-04-13 Annotations: pv.kubernetes.io/bind-completed: yes pv.kubernetes.io/bound-by-controller: yes volume.beta.kubernetes.io/storage-provisioner: rancher.io/local-path volume.kubernetes.io/selected-node: rocky-k3-2 volume.kubernetes.io/storage-provisioner: rancher.io/local-path Finalizers: [kubernetes.io/pvc-protection] Capacity: 5Gi Access Modes: RWO VolumeMode: Filesystem Used By: Events: So I logon to rocky-k3-2, the node that PVC is on, like this:

$ ssh rocky-k3-2 -l rocky
[rocky@rocky-k3-2 ~]$ cd /var/lib/rancher/k3s/storage/
[rocky@rocky-k3-2 storage]$ sudo ls -l
total 0
drwxrwxrwx 3 root root 18 Dec 15 10:53 pvc-0c3eff85-7329-4fde-a00b-e327129046fd_awx_postgres-13-awx-demo-postgres-13-0
drwxrwxrwx 2 root root 6 Apr 13 08:11 pvc-1be2ff00-767f-4151-afbb-8047f934a221_awx_awx-backup-rbc-backup-claim
[rocky@rocky-k3-2 storage]$ sudo ls -laR pvc-1be2ff00-767f-4151-afbb-8047f934a221_awx_awx-backup-rbc-backup-claim
pvc-1be2ff00-767f-4151-afbb-8047f934a221_awx_awx-backup-rbc-backup-claim:
total 0
drwxrwxrwx 2 root root 6 Apr 13 08:11 .
drwx-----x 4 root root 173 Apr 13 08:11 …
[rocky@rocky-k3-2 storage]$
So why are there any files there? I don’t trust this back up I made.

2

I see what I did wrong now. I miss understood what to use for the deployment_name. I the problem is that I used “deployment_name: awx-backup-rbc” thinking that would make a backup called “awx-backup-rbc” that I would “back up from”. But what I should have used was the name of my awx kubernets deployment with is ‘awx-demo’. Then the backup produceded the expected files on the rocky-k3-2 node.