To avoid the Rule Blocked status, do not change device targets frequently. Use a device pool instead. Also, try to avoid adding or removing managed Backup Exec servers.

 

 

 

In a CASO (Central Admin Server Option) environment that has more than one managed Backup Exec server, the Rule Blocked status may appear after changing the target for a job in a backup definition. If a backup definition is setup with multiple jobs, for example with a full, an incremental, and a differential, the initial full backup runs on a managed Backup Exec server that has access to all of the target devices for the backup definition. All jobs for this backup definition will have "server affinity" for the managed Backup Exec server on which the initial full backup ran. In other words, all jobs are targeted to that managed Backup Exec server when possible. After changing the target for a job in that backup definition, the Rule Blocked status will appear when running that job. After changing the target, Backup Exec requires another full backup to run again. The Rule Blocked status indicates that a job cannot run until another job has completed. In this case, an incremental or differential job cannot run until the full job runs again.