Back up SystemLink Enterprise to avoid data loss.

Note Some SystemLink Enterprise services depend on multiple data stores. To avoid data stores getting out of sync, back up and restore all data stores at once. Where possible, back up data stores to the same point in time using a point-in-time feature. If point-in-time is not available for a data store, use a snapshot instead. Ensure you back up data stores in the order listed.
  1. PostgreSQL
  2. MongoDB
  3. Kubernetes, including persistent data stores
  4. S3 compatible storage
Refer to the following table to find information on backing up the most common data stores.
Service Resources Details
Velero
  • Backup Storage Locations and Volume Snapshot Locations
  • Backup Reference
  • Kubernetes Container Storage Interface (CSI) Documentation
  • Amazon Elastic Block Store (EBS) CSI driver
 NI recommends installing Velero on your cluster and using it to back up Kubernetes.
AWS S3
  • Using versioning in S3 buckets
  • S3 point in time restore
  • What is AWS Backup?
 —
AWS RDS
  • Enabling automated backups
  • Restoring a DB instance to a specified time
  • Creating a DB snapshot
 —
External MongoDB
  • MongoDB Ops Manager - Back up a Deployment
  • MongoDB Atlas - Backup, Restore, and Archive
  • Creating a DB snapshot
 Use this service for SystemLink Enterprise deployments using a dedicated MongoDB database outside of the Kubernetes cluster. Otherwise, Velero backs up the databases within the Kubernetes cluster.
External PostgreSQL PostgreSQL Backup and Restore —