2.1 KiB
2.1 KiB
Backup Architecture details
- we use restic to produce small & encrypted backups
- backup is scheduled at
schedule: "10 23 * * *"
- Cloud stores files on
/var/jira
, these files are backuped. If you create a jira xml backup located in /var/jira this file will also be backed up. - postgres db is backed up as pgdump
Manual init the restic repository for the first time
- Scale backup-restore deployment up:
kubectl scale deployment backup-restore --replicas=1
- exec into pod and execute restore pod
kubectl exec -it backup-restore -- /usr/local/bin/init.sh
- Scale backup-restore deployment down:
kubectl scale deployment backup-restore --replicas=0
Manual backup the restic repository for the first time
- Scale gateway and front deployment down:
kubectl scale deployment taiga-gateway-deployment --replicas=0
kubectl scale deployment taiga-front-deployment --replicas=0
- Scale backup-restore deployment up:
kubectl scale deployment backup-restore --replicas=1
- exec into pod and execute restore pod
kubectl exec -it backup-restore -- /usr/local/bin/backup.sh
- Scale backup-restore deployment down:
kubectl scale deployment backup-restore --replicas=0
- Scale gateway and front deployment up:
kubectl scale deployment taiga-gateway-deployment --replicas=1
kubectl scale deployment taiga-front-deployment --replicas=1
Manual restore
- Scale gateway and front deployment down:
kubectl scale deployment taiga-gateway-deployment --replicas=0
kubectl scale deployment taiga-front-deployment --replicas=0
- Scale backup-restore deployment up:
kubectl scale deployment backup-restore --replicas=1
- exec into pod and execute restore pod
kubectl exec -it backup-restore -- /usr/local/bin/restore.sh
- Scale backup-restore deployment down:
kubectl scale deployment backup-restore --replicas=0
- Scale gateway and front deployment up:
kubectl scale deployment taiga-gateway-deployment --replicas=1
kubectl scale deployment taiga-front-deployment --replicas=1