Backup plans

There is an option to run missed task at machine startup if machine was turned off. However if task failed because of unavailable vault, you can try custom scheme with another schedule for monday specifically, with condition 'time since last backup' (greater than). If it doesn't run because of condition not met, it doesn't count as 'failed' task, iirc

Thanks for your help.
I configured new plan for testing - Full Backup with condition - Time since the last backup 2 day.
I added one machine to the plan - the last successful backup of this machine was the current time.
I ran the plan and the machine was backup although no two days has passed from the last backup of this machine.
Why?
Thanks!
Ido

"last backup" means last execution of exactly this backup plan. Other backup plans backing up to the same or other archives do not count. Also, manual execution of a plan overrides all conditions.

I want to be sure i understand , I will give an example.
I want to backup every machine ones a week full backup.
I will create a plan with 20 machines to run every day at Sunday, Monday and Tuesday with a condition Time since the last backup - 5 days.
All the machines in the plan didn't backup at least 5 days.
All the machines that are online at Sunday will be backup.
Tomorrow at Monday the plan will run again, and all the machines that backup on Sunday will not backup again (even the machines are online)?
however just all the machines that are online at Monday (and was offline at Sunday) will be backup?
Is it correct?
Thanks!

The scheme you described should work.

A machine was backup at Sunday but the backup didn't finish (90%), and tomorrow (at Monday) the backup started again from begining and not continued).
Is it possible to configure that the backup will continue from where it stopped?
Thanks!

Backup & Recovery can't continue canceled backup jobs, at all, even for file backups. If the job is not 100% complete, it is considered failed.