General execution flow for a backup plan:

1. Check if the system allows Backups to run - see Configurable Parameters and Settings to learn how to enable or disable all backups
2. Check if the current system time is within the maintenance window timeframe that was defined for the plan
3. Check if the backup store destination path is mounted
4. Check if there is enough space in the destination path for downloading and storing the files - see Configurable Parameters and Settings to lean how to determine the check threshold value
5. Go over all the activities defined for the plan, and split them into executable tasks.
   For example, the plan have two activities, one to Secure Backup devices QA* and a second to export domain DOMAIN* on device TEST8 and on an unavailable device - TEST9,
   Six tasks will be created:
   a. Secure Backup task for device QA1
   b. Secure Backup task for device QA2
   c. Secure Backup task for device QA3
   d. Export Domain task for Device TEST8 and Domain DOMAIN1
   e. Export Domain task for Device TEST8 and Domain DOMAIN2
   f.  Since the device TEST9 is unavailable - an Export Domain task for Device TEST9 and domain DOMAIN* will be created with a "Skipped" status 
6. If all the created tasks are in "Skipped" state (because the devices are not available, or because no devices or domains matched the input patterns) - the plan will stop
7. If there are any tasks waiting to be executed - the Pre-Plan Script will be executed - if requested in the plan settings, the plan will stop if the script's return code is larger than 0
   
   
   

The tasks will start to execute ןn the order they were created, which corresponds to the order which the activities were defined.