Configure NFS Backup Settings in the globals.yaml.gotmpl File

Enable NFS backup settings for datastores in the globals.yaml.gotmpl file.

  1. Enable the fs section for each datastore that you want to back up using the NFS server. See globals.yaml.gotmpl file.
    Elasticsearch
    CODE 
    # Backup config for datastores
backup:
  elasticsearch:
    fs:
      enabled: true
      storage: 5Gi
    PostgreSQL
    CODE 
    # Backup config for datastores
backup:
  postgresql:
    fs:
      enabled: true
      repoName: repo3
      storage: 5Gi
    MySQL
    CODE 
    # Backup config for datastores
backup:
  mysql:
    fs:
      enabled: true
      repoName: repo3
      storage: 5Gi
      backupType: xtrabackup
      xtrabackup:
        # Maximum number of full backups to retain in S3/FS (0 = unlimited)
        retentionMaxFull: 3
        # Set to false to skip --lock-ddl (use only if MySQL is quiesced or DDL won't run during backup)
        lockDdl: true
        schedule:
          # Cron expression for full backups (empty string disables)
          full: ""
          # Cron expression for incremental backups (empty string disables)
          incr: ""
          # MySQL pod to backup from
          pod: "appd-mysql-0"
  2. (Optional) Create a repository for Elasticsearch backups on the NFS server.
    Note:

    • In a standard deployment, Elasticsearch data is stored within the Virtual Appliance. The Elasticsearch backup and restore steps apply only to a standard deployment.

    • You can create a repository only for Elasticsearch backups.

      By default, the globals.yaml.gotmpl file uses the repo3 repository for MySQL and PostgreSQL.

    CODE 
    appdcli backup elasticsearch create-fs-repo repo3
  3. Synchronize the changes across nodes.
    CODE 
    appdcli sync appd <profile>