My current backup program of choice is Areca Backup which is open source and is hosted at sourceforge. I make a separate target profile for each piece of software that I’m backing up so I can backup only the necessary files. Areca handles this method without fail but because there isn’t a built in scheduling system it can be a hassle exporting each individual target backup. There’s an option to run a single export for every target in a group but I have a few targets that I don’t want to backup on a schedule in my main group.
One method of scheduling backups is to run the wizard “Generate backup strategy commands…” which is located in the right click context menu.
My current backup strategy is as follows:
One archive each 1 day, 7 times
Then one archive each 7 days, 3 times
Then one archive each 28 days, 1 time
The backup wizard then creates 3 .bat files in the location that you specify. For each target that you run the wizard on 3 new .bat files are generated. Normally, the next step would be to create a separate task for each .bat file using the Windows Task Scheduler. However this becomes very time consuming and rather sloppy with a large amount of individual target backups. It was for this reason that I created a .bat parser for Areca.
In my programs current state it only parses files which contain “1_days”, “7_days”, or “28_days” in the file name. If the program finds any matches then it takes the contents of the file and appends it to a master backup file titled every_1_days.bat, every_7_days.bat, or every_28_days.bat respectively. Then it’s only necessary to create one Windows task for each .bat file. every_1_days.bat would be scheduled to run once a day, every_7_days.bat once every 7 days, and every_28_days.bat once every 28 days. Each new .bat file is scanned and checked against its master .bat file before being appended in order to check for duplicates. If a duplicate is found then a notice appears alerting the user that the .bat file being imported is already in the master backup file.
To further automate this process you can use a program like Belvedere to scan the directory where Areca exports the .bat files and then launch the .bat parser when a new backup file is found.
Edit the first line of the script
SetWorkingDir, F:\Libraries to point to the directory where your .bat files are located.