I'd like to be able to add several backups to be run "soon"

Right now I have to go to the schedule for each one and add a one-time run, enter a time in the future, and repeat for each backup, too much work, and it leaves a useless event in the schedule to clutter up the list. I'd  like a quick way to say - run this backup 10 minutes from now.

I end up doing a batch of intense work,  that I don't want to lose and then taking a break (or finishing work for the day) and want a checkpoint backup, usually files and folders.

Is there any consistent "pattern" in running those additional backups?  If so, scheduling a script that includes some time delay (rather than scheduling the backup task directly) might provide a solution.

Regards, Richard V. ("Arvy")

No  real pattern

I might have randomly decided to do some programming on a project and after several hours need to break and leave the office - in the simple case I just run the backup definition file and it starts and I leave. Works fine right now.

But if I also want to run a backup of my accounting system that I had made changes to earlier in the day, I need to schedule that to run later before I start the programming backup

The issue happens mostly when I take a lunch break or end work for the day  and I want backups of areas that have had substantial  changes.

Right now I do this with SynvBackPro - I just go to it and do ctrl+q  on each backup profile I need and it queues them up.

Well, running any of Reflect's defined backup tasks by direct command is quite easy.  As I understand it, you just want to be able to run a selected backup task (or several) X minutes after you issue the command (or click the button, or whatever) and a simple time delay script should be able to handle that without any problem I would think.  Even a single script could be coded to accept various (task filename, delay time, etc.) input parameters.  Am I missing something?

Regards, Richard V. ("Arvy")