> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo-platform/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemo-platform/_mcp/server.

# Backup and Restore

NeMo Platform use several storage systems that require backup consideration:

1. **PostgreSQL database**: stores entity metadata and relationships
2. **Object storage**: stores model files, datasets, and other artifacts
3. **Persistent Volume Claims (PVC)**: stores Kubernetes persistent data

## PostgreSQL Backup

For PostgreSQL backup and restore procedures, refer to the official PostgreSQL documentation:

* [PostgreSQL Backup and Restore](https://www.postgresql.org/docs/current/backup.html)
* [Continuous Archiving and Point-in-Time Recovery (PITR)](https://www.postgresql.org/docs/current/continuous-archiving.html)

## Object Storage Backup

Backup procedures for object storage depend on your chosen storage solution:

* **Amazon S3**: See [AWS Backup documentation](https://docs.aws.amazon.com/AmazonS3/latest/userguide/backup-for-s3.html)
* **MinIO**: See [MinIO Data Recovery Guide](https://docs.min.io/enterprise/aistor-object-store/operations/failure-and-recovery/)
* **Azure Blob Storage**: See [Azure Backup documentation](https://learn.microsoft.com/en-us/azure/storage/common/storage-disaster-recovery-guidance)

## Kubernetes PVC Backup

For backing up Persistent Volume Claims in Kubernetes:

* **Velero**: See [Velero documentation](https://velero.io/docs/main/backup-hooks/)
* **Native solutions**: Refer to your cloud provider's Kubernetes backup solutions:
* [GKE Backup](https://docs.cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/concepts/backup-for-gke)
* [AKS Backup](https://learn.microsoft.com/en-us/azure/backup/azure-kubernetes-service-cluster-backup)
* [EKS Backup](https://docs.aws.amazon.com/eks/latest/userguide/disaster-recovery-resiliency.html)

## Best Practices

1. Schedule regular backups during low-usage periods
2. Test your restore procedures periodically
3. Store backups in a different physical location
4. Document your backup and restore procedures
5. Monitor backup job status and storage usage
6. Ensure consistent state across all storage systems when performing backups

For detailed implementation guidance, consult your storage provider's documentation and your organization's disaster recovery policies.