This repository was archived by the owner on Sep 10, 2025. It is now read-only.
Releases: ViveTheModder/custom-backup-tool
Releases · ViveTheModder/custom-backup-tool
Release list
Custom Backup Tool v1.5.1
Added Unix support AND fixed Windows support.
Again, requires Java SE 8 or higher.
Custom Backup Tool v1.4
Changelog:
- Added the following features as options that can be changed from the
dirs.txtfile:
- Blacklisted directories (ones that will be skipped by the program);
- Hidden files (ones that may or may not be skipped);
- Hidden operating system files (for Windows, that may or may not be skipped).
- When an exception is encountered, the program immediately opens the created
errors.logfile.
Custom Backup Tool v1.3
Changelog
- Program no longer uses hardcoded paths for the
javaw.exeexecutable.
Not sure why I even used them in the first place, other than to be technical. - The backup frequency can now be changed as intended.
Originally, it would not apply the/MOargument to thescheduler.batfile at all. - When
backup.jarlaunches as a scheduled task, it will briefly displaytaskeng.exeand then leave.
Before, it would stay on the screen no matter what.
Custom Backup Tool v1.2
Changelog:
- Multiple folders can be backed up now.
- The date & time after the backup folder names feature can be enabled/disabled by editing the
dirs.txtfile.
This was done to assure weekly/monthly backups don't pile up, and can instead have one backup overwrite most of its files continuously. - Message box results are fixed. Before, the minutes would actually display the seconds, and the seconds could be greater than 60.
- The
errors.logfile will no longer delete & remake itself each time it finds an exception.
Instead, all the exceptions stack up, and each one includes the date & time during which it occured. - Unlikely to happen, but if the user provides the same directory as both the input/source and output/destination, the backup method will return/terminate early.
To prevent this from happening anyway, the user must assure the backup folder has NOTHING to do with the input directories.
It needs to be stored separately, which means it cannot be a subfolder of any input directory.
Custom Backup Tool v1.1
Changelog:
- The program will now copy files, even if they are in use by another process, thanks to the ROBOCOPY command on Windows.
- The program now works as intended - it no longer puts the copied files in folders named after the files themselves.
Not even I know how that got by me, considering the prior testing I did, but oh well. - Specified two more hardcoded paths (Program Files (x86), and Program Files).
If this still leads to issues, then I will borrow some code from my Accurate File Finder and have it search for any instance ofjavaw.exein the computer. - Whenever it encounters any exceptions, the program will put their messages (not the whole stack) on a file named
errors.log, instead of displaying an error message, which would interfere with automatic backups.
Custom Backup Tool v1.0
Requires Java SE 8 or higher.
scheduler.jar only works on Windows at the moment, but otherwise, backup.jar should run on any OS.
Before running, to prevent errors with the backup procedure, make sure to specify 1 input & 1 output directory in the dirs.txt file.