How to Create and Monitor Backups Using the Backup Daemon

The backup daemon operates on the box level of an unmanaged box, a CC-managed box, and a Control Center and always must be configured on the box level. Configure the Backup Daemon to perform scheduled backups on storage that can be either locally on your firewall / Control Center or on remote Cloud storage.

Step 1. Enable the Backup Daemon and Create a Storage Backend

1. Log in to your Firewall or Control Center on box level.

2. Go to CONFIGURATION > Configuration Tree > Infrastructure Services > Config Backup Daemon.

3. Click Lock.

4. For Enable Backup Daemon, select Enable.

5. (Optional) If you want to change the default preset for Log-level, select another entry from the list

6. Click + for Storage backends.

Step 2. Configure the Storage Backend and Create a Backup Job

1. The Storage backends window is displayed.

2. For Unique backend ID, enter a unique name for your back-end storage.

3. For Backend type, select whether to create a local or remote storage:

   1. Local – Allocate space storage on your firewall/Control Center.

   2. S3 Bucket – Allocate space on an AWS Cloud storage. This option will enable the edit fields for Backend user and Backend key.

   3. Azure Blob – Allocate space on an Azure Cloud storage. This option will enable the edit fields for Backend user and Backend key.

4. In order to access the storage space, your firewall/Control Center must be authorized. You have two options:

   1. (Option #1) Authorize using explicit credentials

      1. For Credential type, select Explicit.

   2. (Option #2) Authorize using system Cloud credentials.

      1. For Credential type, select Use system cloud credentials.

5. If you have selected remote backend type (S3 Bucket, Azure Blob):

   1. Add the name of the Backend user.

   2. Add the password of the Backend key.

6. Add the path for the Backend url so that the backup daemon can connect to the storage space. This is a mandatory field.

   Local Storage Example	AWS Storage Example	Azure Storage Example
   /myLocalStorage	https://s3.amazonaws.com/bucket-backups	containerbackup:/folder-backups

7. For encrypting your backup, you must enter an encryption password. The indicator for Strength should display a green color:

   1. If you have already configured a valid password anytime before, the edit field for Current will display multiple black bullets hiding your current password.

   2. For New, enter your new password.

   3. For Confirm, re-enter the password to check whether it matches the previous input for New.

8. Click + for Backup jobs.

Step 3. Configure and Schedule the Backup Job

1. The Backup jobs window is displayed.

2. Enter a unique name into the edit field for Unique ID.

3. Select on which level the backup must be performed.

   1. Box – The backup will be created for a firewall's/Control Center's configuration on the box level.

   2. CC – The backup will be created for the configurations of all Control Center-managed firewalls.

   3. CC and Box – Both previous options for Box and CC will apply.

4. For Compress backup, select Compressed if you want to have the backup compressed, otherwise select Uncompressed.

5. For Execution triggers, click + to create a new execution trigger:

   1. The Execution triggers window is displayed.

   2. Enter the timestamp in Unix-like time format following the template 'Minute - Hour - Day of Month - Month - Day of the Week', e.g. every 31st of December at 18:00:
      0 18 31 12 *

6. Click OK.

7. For User tags, click + to add tags to the backup job.

8. The User tags window is displayed.

9. For tag, enter a single tag into the edit field.

10. Click OK.

11. (Optional) If you want to add more tags, repeat all previous steps starting at point 7.

12. If you want to modify the retention time of the backups, configure the following parameters. Leaving all fields blank or setting all edit fields to '0' will keep the backup unlimited.

    1. Retain last – Keep the #n most recent backups. (The default value is 5).

    2. Retain hourly – For the last #n hours with a backup, keep the most recent for each hour.

    3. Retain daily – Keep the latest #n daily backups.

    4. Retain weekly – Keep the latest #n weekly backups.

    5. Retain monthly – Keep the latest #n monthly backups.

    6. Retain yearly – Keep the latest #n yearly backups.

    7. Retain tagged – If you want to exempt certain backups from being deleted after surpassing the configured limits above, click + to add the Retain tag that must match at least one of the User tags. If you want, you can add further retain tags.

13. Click OK.

14. Click OK.

15. Click OK.

16. Click Send Changes/Activate.

You have now configured the backup daemon to perform backup jobs.