Skip to content

Operation

Warning

Pay attention when you launch the backup.yml or restore.yml because playbook automatically stop and start the container to keep all the data safe.

Backup guide

Requirements

On the OneForAll machine

  • Have an OneForAll instance running

Ansible Backup playbook

  • Launch the playbook to make your backup, like:
ansible-playbook -i hosts backup.yml

Note

You can change the release destination (default: /opt/OneForAll/backup) like so:

ansible-playbook -i hosts backup.yml --extra-vars 'allspark_backup_directory=/tmp/OneForAll_backup'

Restore guide

Requirements

On the OneForAll machine

  • Have the same installation of your backup to be able to restore your release

Warning

Pay attention:

  • A component disabled (on the OneForAll machine) won't be imported on restore
  • restore needs a running instance
  • Previous datas of the restored containers will be lost (and aligned on the backup ones)

Ansible Restore playbook

  • Launch the playbook Restore to make the restore
ansible-playbook -i hosts restore.yml

Note

You can launch a dry-run mode if you want to test your backup to restore, like so:

ansible-playbook -i hosts restore.yml --extra-vars 'allspark_restore_dry_run=true'