Extended DB Backup Options

[tomjn]

Originally, DB backups and restores were added so that if you destroyed the VM you could create it again without data loss. Options were added

At the moment you can back up databases to SQL files, or not back up. All or nothing:

general:
  db_backup: true
  db_restore: true

t's time we give people finger control over DB backup behaviours. Here's a proposed schema:

general:
  db_backup:
    # Compress usiing gzip, db.sql becomes db.sql.gz when true
    gzip: true

    # When do we run backups?
    on:
      halt: false
      destroy: true

    # Always back up these databases
    include:
      - firstdb
      - second

    # Never back up these databases
    exclude:
      - fourth
      - fifth

    # If a database doesn't appear in the above lists, do we back it up?
    backup_by_default: true

  db_restore:
    # when do we restore?
    on:
      provision: true

    # Always restore these:
    include:
      - firstdb
      - second

    # Never restore these:
    exclude:
      - fourth
      - fifth

    # Default for databases not mentioned above
    restore_by_default: true

I don't expect all of these to be implemented at once. So this will act as the umbrella ticket for:

• backup include list
• backup exclude list Backup database exclusion list #2340
• backup default
• restore include list
• restore exclude list
• restore default
• backup gzip compression GZip backups #2342
• backup trigger controls

[Mte90]

The idea is to have db backup as default just on destroy.