Table of Contents

Mixpost Backup CronJob

Meaning

These alerts monitor the Kubernetes Job created by the Mixpost backup CronJob.

Alerts:

Impact

* Success → Backup completed successfully. Mixpost data is safely stored in MinIO. * Failure → Mixpost database or storage files may not be backed up. Could affect disaster recovery if restoration is needed.

Diagnosis

1. Check Kubernetes Job status:

kubectl get job mixpost-backup-job -n <NAMESPACE>
kubectl describe job mixpost-backup-job -n <NAMESPACE>

2. Check logs of the Job pod:

kubectl logs job/mixpost-backup-job -n <NAMESPACE>

3. Verify backup in MinIO:

mc ls <MINIO_ALIAS>/mixpost-backups/
mc stat <MINIO_ALIAS>/mixpost-backups/<backup_file>

4. Check PVC mounts if used:

kubectl get pvc -n <NAMESPACE>
kubectl describe pvc <PVC_NAME> -n <NAMESPACE>

Possible Causes of Failure

* Pod in CrashLoopBackOff, OOMKilled, or Failed * PVC mount unavailable or insufficient space * MinIO credentials missing or misconfigured * Network issues preventing upload to MinIO * Disk space or permissions issues on the node * CronJob manifest misconfiguration * MySQL credentials invalid or inaccessible

Mitigation

1. Inspect Job pod logs to identify errors. 2. Verify MinIO credentials and connectivity. 3. Check PVC status and node disk availability. 4. Verify MySQL credentials and connectivity. 5. Retry backup manually if needed:

kubectl create job --from=cronjob/mixpost-backup-job mixpost-backup-job-manual -n <NAMESPACE>

6. Correct any misconfigurations in CronJob YAML, database, or MinIO bucket policy. 7. Escalate to SRE or admin team if repeated failures occur.

Escalation

* Escalate if backups fail for more than one consecutive run. * Notify on-call engineer if production Mixpost data may not be recoverable.

* MixpostBackupSucceeded * MixpostBackupFailed * HostOutOfDiskSpace (node running backup Job) * KubernetesPodCrashLooping

* Kubernetes → Jobs & CronJobs (namespace: <NAMESPACE>) * Grafana → Backup Job status metrics * MinIO → Backup object listings