You can build a batch file, schedule it to start whenever, then force it to stop after the task has been running for x number of hours (an option within the task), then repeat the task each day starting at your specified time. each day check on the destination folder size until it has been completed.
Here are some options from searching.:
Windows has a built-in feature called DFS-R (Distributed File System Replication). The system syncs files between servers at some set interval.
There is a recommendation that I highly advise you to follow which is pre-seeding the target server with the initial data sync. Ideally, this would be done locally where you can 1) halt any file changes or do it at hours when users are not making changes to files, and 2) you're taking advantage of the local network's speed.
If you cannot move the target server to be in the same location as the source server, you can get a large external hard drive and use that to pre-seed the data using Robocopy. Then take the drive over to the other location to copy the data over. Robocopy is used as it will copy all file attributes.
One of the big things you need to be cognizant of is the issue of file locking. You can have a situation where if users at both ends are making changes to the file, the changes can cause file syncing/versioning control issues.
One of the nice things about DFS-R is it only copies the change blocks for any data that changes. So it provides some efficiency in replicating data across limited bandwidth WAN/Internet connections.
Best practices would be to have a VPN tunnel established between the two sites.
Scheduling-wise, you will have to look into the granularity of the scheduling DFS-R offers.
Other considerations.....your experience will be totally dependent on the change rate and what files do get changed/added. For video files, these are the worst to replicate as these files don't compress or dedupe well. The DFS-R database has to be synced between the two servers so be aware of this. In some situations, the file syncs are never complete due to the sheer volume of the number of new/changed files having to be indexed where the syncing of the database doesn't complete or consumes the replication window before the file transfers begin or can be completed.
Also, there are som straightforward backup tools that can do these requirements with just a few steps automatically, take a look at GoodSync, Gs Richcopy 360, and AllwaySync,