Valid questions. While waiting, I'll just say that other methods may not work in your situation, but that doesn't make them worse.
My front ends had a backup procedure to do two things: backup the data that was entered that day, plus download new production data so as to be ready for the morning shift. Windows Task Scheduler running on a dedicated pc that was never turned off opened the db with a special command line switch (it can be anything you want - I called it Otto Mayshun). The db opened and the autoexec ran the startup code. If the database Command argument had a value (Otto Mayshun) the code knew it was the dedicated pc that just logged in so the update/backup process began. A batch file called by this procedure was used to back up (copy) the be to a network location, which just over-wrote the prior one since incremental backups were not the goal. There was more to it but I won't bore anyone with the details. Suffice to say my point is that Task Scheduler is an option whether one uses a command line switch or not and the entire be file can be copied in one operation. That makes it more "automated" IMHO . I suspect not many people know about the db Command function or argument since in all the time I've been poking around here, I'm the only one who's ever mentioned it before - AFAIK.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.