You might not want to run every missed iteration. For example, if you missed two daily Inc backups of the same job, do you really want to create 2 Incs afterward, one immediately after the other? If you just want a fast way to queue a single iteration of multiple specific jobs manually, I can think of two options:
- Generate desktop shortcuts for each of your jobs by right-clicking the definition file in Reflect and selecting "Create desktop shortcut". They don't have to stay on your desktop, fyi. You'll then be able to click those one immediately after the other to queue everything, and Reflect will run them sequentially. This works because the desktop shortcut's path specifies the "-w" parameter to cause this behavior. Note however that if you choose to have the shortcut prompt you to specify backup type (Full/Diff/Inc) rather than choosing a specific type for that shortcut, you won't be prompted for your backup type until the job is actually ready to run, which wouldn't work for your needs.
- If you wanted to cut down on clicks even further, you could create a single batch file that contains the appropriate commands to run each of your definition files, then run that file (as administrator). Or you could just keep that list as a reference and copy/paste the individual lines you need at any given time into a Command Prompt window, although in this case you'd need to open a second Command Prompt window to queue subsequent jobs since the first window will be "held" to display the progress of the running job rather than immediately accepting additional commands. Anyhow, you can find guidance for the correct command line syntax here
-- note the "-w" parameter that will queue jobs, and from looking at the desktop shortcut's path, apparently there's a "-prompt" option not mentioned on that page in addition to "full/diff/inc" that you can use if you really want to, although again that prompt wouldn't appear until the job was ready to run.@Macrium
, any way that the backup type prompt could be displayed when the command is first executed rather than when the job is ready to run, in order to allow that decision to be made upfront for multiple jobs that will be queued?