|
1 | | -# Backup and Restore |
| 1 | +# Backup and restore |
| 2 | + |
| 3 | +For backup and restore procedures, refer to the documentation for each component: |
| 4 | + |
| 5 | +- [Wazuh manager](https://github.com/wazuh/wazuh/blob/v5.0.0/docs/ref/backup-restore.md) |
| 6 | +- [Wazuh agent](https://github.com/wazuh/wazuh-agent/blob/v5.0.0/docs/ref/backup-restore.md) |
| 7 | + |
| 8 | +## Kubernetes-specific considerations |
| 9 | + |
| 10 | +When backing up Wazuh deployments on Kubernetes, also consider: |
| 11 | + |
| 12 | +### PersistentVolume backups |
| 13 | + |
| 14 | +- Wazuh Manager and Indexer data are stored in PersistentVolumes. |
| 15 | +- The indexer PersistentVolume contains the index data and indexer security state (including internal users). |
| 16 | +- Use your storage provider's snapshot or backup capabilities: |
| 17 | + - **AWS EBS**: EBS snapshots via AWS Backup or manual snapshots |
| 18 | + - **GCP Persistent Disk**: Disk snapshots |
| 19 | + - **Azure Disk**: Disk snapshots |
| 20 | + - **On-premises**: Storage backend-specific backup tools |
| 21 | +- Consider using Kubernetes backup tools like Velero for automated PV backups. |
| 22 | + |
| 23 | +### Secrets and configuration |
| 24 | + |
| 25 | +Back up the following Kubernetes Secrets containing credentials and certificates: |
| 26 | + |
| 27 | +- `wazuh/secrets/wazuh-api-cred-secret.yaml` - Wazuh API credentials |
| 28 | +- `wazuh/secrets/dashboard-cred-secret.yaml` - Dashboard credentials |
| 29 | +- `wazuh/secrets/indexer-cred-secret.yaml` - Indexer credentials |
| 30 | +- `wazuh/secrets/wazuh-authd-pass-secret.yaml` - Agent enrollment password |
| 31 | +- `wazuh/secrets/wazuh-cluster-key-secret.yaml` - Cluster communication key |
| 32 | +- Certificate secrets generated by the `wazuh-certs-tool.sh` script |
| 33 | + |
| 34 | +Also back up any custom ConfigMaps you have created for configuration file persistence. |
| 35 | + |
| 36 | +Store backups securely and encrypt them if they contain sensitive data. |
| 37 | + |
| 38 | +### Manifest files |
| 39 | + |
| 40 | +- Maintain version-controlled copies of all Kubernetes manifests, including customizations in `envs/`. |
| 41 | +- This allows you to recreate the deployment configuration even if the cluster is lost. |
0 commit comments