> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v2.0/technical/guides/installation/opencrvs-maintenance-tasks/backup-and-restore/manual-backup-creation.md). # Manual backup creation ### Before you begin Manual backup process assumes automated backup workflow is already configured and working properly. Manual backup process invokes same Kubernetes cronjobs as for automated process. Reasons for manual backup: * Before environment reset * Before OpenCRVS or dependencies upgrade * Migration to new hardware or cloud * Off-boarding from OpenCRVS Following components are backed up: * MongoDB * PostgreSQL * MinIO * InfluxDB ### Running all components backup 1. Connect to your cluster with `kubectl` 2. Change namespace to opencrvs-deps-\: ``` kubectl config set-context --current --namespace=opencrvs-deps- ``` 3. Run following command to trigger backup jobs for all components: ``` for cj in $(kubectl get cronjob -l job-type=backup -o jsonpath='{.items[*].metadata.name}'); do \ kubectl delete job $cj-job --ignore-not-found; \ kubectl create job --from=cronjob/$cj $cj-job; \ done ``` Example output: ``` job.batch "influxdb-backup-job" deleted job.batch/influxdb-backup-job created job.batch "minio-backup-job" deleted job.batch/minio-backup-job created job.batch "mongodb-backup-job" deleted job.batch/mongodb-backup-job created job.batch "postgres-backup-job" deleted job.batch/postgres-backup-job created ``` 4. Verify all jobs completed without issues:
``` kubectl get job -ljob-type=backup ``` Example output: Check job names like `*-backup-job` without ending number, jobs with number were triggered per schedule: ``` NB01NSTL012:~ vmudryi$ kubectl get job -ljob-type=backup NAME STATUS COMPLETIONS DURATION AGE influxdb-backup-29384700 Complete 1/1 12s 6h9m influxdb-backup-job Complete 1/1 12s 2m31s minio-backup-29384700 Complete 1/1 9s 6h9m minio-backup-job Complete 1/1 10s 2m30s mongodb-backup-29384700 Complete 1/1 18s 6h9m mongodb-backup-job Complete 1/1 16s 2m29s postgres-backup-29384700 Complete 1/1 12s 6h9m postgres-backup-job Complete 1/1 12s 2m28s ``` 5. SSH (Login) to backup server and verify backup was completed successfully. ### Running Single component (MongoDB) backup 1. Connect to your cluster with `kubectl` 2. Change namespace to opencrvs-deps-\: ``` kubectl config set-context --current --namespace=opencrvs-deps- ``` 3. Run following command to trigger MongoDB backup: ``` kubectl create job \ --from cronjob/mongodb-backup mongodb-backup-manual ``` Example output: ``` job.batch/mongodb-backup-manual created ``` 4. Verify MongoDB backup completed successfully: ``` kubectl logs -f job/mongodb-backup-manual ``` Example output: ``` [2025-11-12 07:01:38] Starting MongoDB backup script ... [2025-11-12 07:01:52] Encrypted backup file /tmp/mongo_backup_2025-11-12.tar.gz.enc transferred to backup host 10.2.0.3:/home/backup/production/2025-11-12 ``` ### Verify backup was created 1. SSH (Login) to backup server 2. Become backup user: ``` sudo -i su - backup ``` 3. Check backup directory content: ``` ls -l /home/backup/ ls -l /home/backup// ``` Example output: ``` backup@tmp-backup:~$ ls -l /home/backup/production/2025-11-12 total 25972 -rw-r--r-- 1 backup backup 74704 Nov 12 01:00 influxdb_backup_2025-11-12.tar.gz.enc -rw-r--r-- 1 backup backup 26506864 Nov 12 01:00 minio_backup_2025-11-12.tar.gz.enc -rw-r--r-- 1 backup backup 464 Nov 12 01:00 mongo_backup_2025-11-12.tar.gz.enc -rw-r--r-- 1 backup backup 448 Nov 12 01:00 postgres_backup_2025-11-12.tar.gz.enc ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.opencrvs.org/v2.0/technical/guides/installation/opencrvs-maintenance-tasks/backup-and-restore/manual-backup-creation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.