+x dbminter - 27 February 2021 10:14 PMI was a bit confused over the did start at 2 AM statement myself.
+x jphughan - 27 February 2021 10:04 PMI'm not sure what you're asking here. Did you mean to say that your backup did NOT start at 2 AM? In your post above you say it "did start", in which case I don't see a problem. But if you have multiple completely separate jobs all set to start at the same time, Reflect will not run them all simultaneously. It will run them sequentially. Also, it appears you have many different definition files but you're using the exact same schedules for all of them. Unless you are using different retention policy settings for those jobs, then you might want to consider backing up all of those folders in the same job in order to simplify your configuration. A File & Folder backup job can include more than one source folder, even if they are on different drives, as shown below. If you need to use different retention policies for different data and/or want to back up that data to different locations, then you will want to have separate definition files. But if you are using the same schedule, retention policy, and destination folder for all of the jobs in your screenshot, then you should consolidate all of those into a single backup job. Also, you do not have to manually run a Full. If Reflect ever has a Differential or Incremental scheduled to occur and it isn't possible to create one of those because there is no Full available, then Reflect will automatically create a Full instead. And the job log will note that this happened and why it happened. Here is an example of a single File & Folder backup job that includes 3 completely different folders on 3 different drives. All of this will be backed up as a single job.