A centralized backup plan can be deployed to a machine that does not have data meeting the selection rules. No error or warning will be logged during the plan deployment because it is assumed that the data may appear in the future. A backup plan is created as usual and the plan state is changed to Deployed.
If no data to back up is found at the time when the backup task starts, the task will fail and the plan status will turn to Error. If at least one of the data items is found, the backup task will succeed with a warning. The plan status will change accordingly.
The backup tasks will start on schedule as specified by the plan and produce a similar result until all data items appear on the machine or the plan is edited to exclude the non-existent data items.
Examples
Assume the selection rule states that the plan has to back up volumes D: and F:. The plan is deployed to both Linux and Windows machines. Once the first backup is started, the plan gets the Error status on the Linux machines and on the Windows machines that do not have such volumes. The plan gets the Warning status on Windows machines that have either a D: or F: volume, unless an event that will result in an error occurs.
The plan that has to back up the [SYSTEM] and the /dev/sda1 volumes will get the Warning status on the Windows machines (since /dev/sda is not found) and on the Linux machines that have the /dev/sda1 volume. This is because the [SYSTEM] volume is not found. The plan will get the Error status on Linux machines that do not have a SCSI device.