Group: Forum Members
^ Correct. Even if you're backing up the same source data at both times, if you want to make sure that one time always uses Destination A and the other always uses Destination B, then you would have to use separate definition files. You can just duplicate the one you already have, then switch the destination in the duplicated definition file and make sure the schedules for each are correct.
HOWEVER, if you can safely assume that only one of those drive letters will be available at any given time, you could instead use Reflect's "Alternative locations" feature. You'll see a link for that directly below the field where you specify a destination. In there you can specify fallback destinations. If you do that, then you can schedule both job run times in a single definition file, because each time the job runs, Reflect will back up to whichever destination is available at that time. If both are available, I believe it backs up to whichever destination is higher in the list.