Group: Forum Members
First it's probably important to draw a distinction between "backups", which is what Reflect generates, and "file replication", which is what you're doing now. They're often conflated, but they're different. A backup results in a point-in-time archive of your data at a specific time, and future backups will either be created independently of that backup or can be "appended" to that backup to include changes relative to the previous backup -- but the previous backup still exists as a separate entity that can be accessed and restored from if desired. By comparison, file replication like you're doing simply makes a another copy of your data, and if you run the job again, the updated contents will overwrite the previous copy.
So the first question to ask is whether you in fact want to switch from file replication to backups. If you don't, then if you provide more information about the specific Robocopy errors you're encountering, chances are they can be resolved fairly easily, and then you can absolutely store and periodically run a Robocopy command that uses the /MIR switch to have the destination "mirror" the source. In that scenario, Robocopy only copies files that are new or have changed on the source compared to the existing destination copy.
If you do in fact want backups, it sounds like the Incrementals Forever with Synthetic Fulls strategy might be what you want if you only want to copy your whole data set once and then have future jobs only capture changes relative to the last backup. In that case, the setup is fairly straightforward. You'd create a new File & Folder backup, specifying the source folder(s) you want to back up. You can choose to back up everything in a single job, or you may prefer to use different jobs for different source folders, especially if you want to back them up under separate schedules and or have different retention periods for different kinds of data. But either way, in the next step of the wizard that deals with scheduling and retention, select "Incrementals Forever" from the template dropdown at the top. That will pre-create a schedule entry for an Incremental job, which you can modify to fit your schedule preferences or even delete if you just want to keep this job defined for future execution on a manual, on-demand basis. (Note: The first backup will automatically be a Full, so there's no need to schedule that separately.) From there, the only remaining decision to make is how many Incrementals you want to retain in your backup set. Then click Finish, and your job will be saved as a definition file. From that point on, the job will run as scheduled, and/or you can go to the Backup Definition Files tab to see your job listed, from which you can right-click it and select Run Now > Incremental.
But yes, Reflect should be immune to any security-related issues because it runs as the SYSTEM account, which has more privileges than Robocopy running under your regular user account, and if the security issues are actually lock issues caused by files being open, then Reflect would also sidestep those issues because it creates a snapshot of your data before the backup occurs, which Robocopy doesn't do.