Archive is Not Created #906
Labels
bug
Something isn't working
Comments
|
I test on my cluster with my k8up resources (I don't know exactly what your k8up resources are used for to generate an archive). However, when I didn't have any backup in my cluster, this problem occurred. No archive was created. P.S: Maybe your problem because of no backup files exist in s3 bucket Without any backupWith exist at least one backupCould you please share more about backup and archive resources? |
|
Seems like the k8up errors out when the bucket is empty (and no restic repository is initialized). Here's a k8s job spec that can be used to initialize buckets as a workaround: apiVersion: batch/v1
kind: Job
metadata:
namespace: '<k8s_namespace>'
name: 'bucket-initialization'
spec:
backoffLimit: 3
template:
spec:
restartPolicy: Never
volumes:
- name: tmp
emptyDir: {}
initContainers:
- name: file-creation
image: busybox:1.28
command: ['sh', '-c', 'echo "$(date)" > /files/initialized.txt']
volumeMounts:
- mountPath: /files
name: tmp
containers:
- name: initialize-bucket
image: 'ubuntu:24.04'
imagePullPolicy: IfNotPresent
volumeMounts:
- mountPath: /init-files
name: tmp
command: [ "/bin/bash", "-c" ]
args:
- |
set -ux; \
apt update; \
apt upgrade -y --no-install-recommends; \
apt install -y --no-install-recommends ca-certificates; \
update-ca-certificates; \
apt install -y --no-install-recommends wget; \
apt install -y --no-install-recommends jq; \
apt install -y --no-install-recommends restic;
wget "https://github.com/peak/s5cmd/releases/download/v2.2.2/s5cmd_2.2.2_Linux-arm64.tar.gz"
tar xzf s5cmd_2.2.2_Linux-arm64.tar.gz
mv s5cmd /usr/local/bin/.
s5cmd cp /init-files/initialized.txt s3://<bucket_name>/initialized.txt
# restic guards against initializing a repo that is already initialized so this can be run multiple times
restic init
# only keep 1 snapshot of a dummy backup to ensure a single backup exists in restic repo
restic forget $(restic snapshots --json --latest 1 --path "/init-files" | jq -r '.[0].id')
restic --verbose backup /init-files
envFrom:
- secretRef:
name: '<secret_that_contains_aws_access_key_id_and_aws_secret_key>'
env:
- name: 'S3_ENDPOINT_URL'
value: 'https://<domain>'
- name: RESTIC_REPOSITORY
value: "s3:https://<domain>/<bucket_name>"
- name: RESTIC_PASSWORD
valueFrom:
secretKeyRef:
name: "backup-cred"
key: "password"
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Archive created but empty
Additional Context
In #868 a bug fix for Archive was introduced.
Now tested looks like the archive isn't properly created. It exists on the cloud provider but it is empty after backup run.
Logs
kubectl -n company-example-prod logs archive-example-backup-archive-manual-xyz 2023-10-11T15:47:54Z INFO k8up Starting k8up... {"version": "2.7.2", "date": "2023-10-09T10:13:29Z", "commit": "45d99dd90dbb2a080e6832c34e96b371216a3e0b", "go_os": "linux", "go_arch": "amd64", "go_version": "go1.19.13", "uid": 1000880000, "gid": 0} 2023-10-11T15:47:54Z INFO k8up.restic initializing 2023-10-11T15:47:54Z INFO k8up.restic setting up a signal handler 2023-10-11T15:47:54Z INFO k8up.restic.restic using the following restic options {"options": [""]} 2023-10-11T15:47:54Z INFO k8up.restic.restic.RepoInit.command restic command {"path": "/usr/local/bin/restic", "args": ["init", "--option", ""]} 2023-10-11T15:47:54Z INFO k8up.restic.restic.RepoInit.command Defining RESTIC_PROGRESS_FPS {"frequency": 0.016666666666666666} 2023-10-11T15:47:56Z INFO k8up.restic.restic.RepoInit.restic.stdout created restic repository 9bb6c7f16c at s3:https://objects.cloudprovider.tld/erpprod-archive 2023-10-11T15:47:56Z INFO k8up.restic.restic.RepoInit.restic.stdout 2023-10-11T15:47:56Z INFO k8up.restic.restic.RepoInit.restic.stdout Please note that knowledge of your password is required to access 2023-10-11T15:47:56Z INFO k8up.restic.restic.RepoInit.restic.stdout the repository. Losing your password means that your data is 2023-10-11T15:47:56Z INFO k8up.restic.restic.RepoInit.restic.stdout irrecoverably lost. 2023-10-11T15:47:56Z INFO k8up.restic.restic.unlock unlocking repository {"all": false} 2023-10-11T15:47:56Z INFO k8up.restic.restic.unlock.command restic command {"path": "/usr/local/bin/restic", "args": ["unlock", "--option", ""]} 2023-10-11T15:47:56Z INFO k8up.restic.restic.unlock.command Defining RESTIC_PROGRESS_FPS {"frequency": 0.016666666666666666} 2023-10-11T15:47:57Z INFO k8up.restic.restic.snapshots getting list of snapshots 2023-10-11T15:47:57Z INFO k8up.restic.restic.snapshots.command restic command {"path": "/usr/local/bin/restic", "args": ["snapshots", "--option", "", "--json"]} 2023-10-11T15:47:57Z INFO k8up.restic.restic.snapshots.command Defining RESTIC_PROGRESS_FPS {"frequency": 0.016666666666666666} 2023-10-11T15:47:58Z INFO k8up.restic.restic.snapshots getting list of snapshots 2023-10-11T15:47:58Z INFO k8up.restic.restic.snapshots.command restic command {"path": "/usr/local/bin/restic", "args": ["snapshots", "--option", "", "--json"]} 2023-10-11T15:47:58Z INFO k8up.restic.restic.snapshots.command Defining RESTIC_PROGRESS_FPS {"frequency": 0.016666666666666666} 2023-10-11T15:47:59Z INFO k8up.restic.restic.archive archiving latest snapshots for every hostExpected Behavior
Archive size > 0Bytes
Steps To Reproduce
archive created with schedule:
Archive could be run manually
Version of K8up
2.7.2
Version of Kubernetes
v1.26.9
Distribution of Kubernetes
OpenShift
The text was updated successfully, but these errors were encountered: