Releases: ViktorJp/BACKUPMON
Releases · ViktorJp/BACKUPMON
BACKUPMON v1.8.20
v1.8.20 - (October 12, 2024)
- PATCH: Code improvements to allow blank space chars in directory paths.
- PATCH: Changed defaults to directory paths to show the correct router model.
- PATCH: Changed defaults containing an IP address to show the correct LAN IP address octets of
the router.
- PATCH: Various fixes and code improvements
BACKUPMON v1.8.19
v1.8.19 - (July 20, 2024)
- PATCH: Bugfix release to help fix missing shared email library error messages that popped up
due to the last release. Issue ended up being that the email library update wasn't properly
being called and therefore not loading into memory before the backupmon.cfg variables got
loaded. Shared Email Library script update is now a function, and is strategically called on
when needed to perform email functionality.
BACKUPMON v1.8.18
v1.8.18 - (July 19, 2024)
- PATCH: Small change to the way Shared Email Library updates are being handled. On startup, the
script will check if AMTM email is enabled before checking for updates, just to prevent this
feature from downloading if not being used. Secondarily, when enabling this feature under the
config menu, it will download and check for updates before it asks if you want to send a quick
test email to ensure AMTM is configured correctly.
BACKUPMON v1.8.17
v1.8.17 - (July 18, 2024)
- PATCH: With many thanks to @Martinski, he helped develop a new methodology to build in more
redudancy should we ever face another situation like this again, where the shared email libary
file location becomes unavailable. In this latest mod, he has built in the capability of using
three distinct file location URLs that the script will use to find and download the latest
version. HUGE THANK YOU for supporting this, @Martinski! :)
- PATCH: Based on some feedback and to reduce confusion, I have renamed "Backup Frequency" to
"Backup Retention". Thanks to @visortgw and @ExtremeFiretop for the suggestions. The word
"retention" word makes much more sense, since we're talking about what kinds of folders we're
leaving behind, and how long they will be around (ie. weekly, monthly, yearly, or perpetual
backups each day).
BACKUPMON v1.8.15
v1.8.15 - (July 7, 2024)
- PATCH: Implemented a workaround to continue providing AMTM email capabilities due to the shared
library source being hosted under @Martinski's github repo becoming unavailable. This should only
affect new installs, as having existing functionality in place should continue working as normal.
Will work with Martinki to move this back over to his repo when it becomes available again.
Thanks to @JimBobJay for bringing this to our attention!
BACKUPMON v1.8.14
v1.8.14 - (July 4, 2024)
- PATCH: Continuing with the enhancements of the -secondary switch, suggestion from @visortgw was
to be able to force a secondary backup (using the -secondary switch), even if the secondary backup
is marked as disabled in the config menu.
- PATCH: Running a -secondary switch backup apparently did not delete the error flag and would
continue showing the error warning in the setup menu and on screen. When running a -secondary
switch-based backup will now remove the error flag so you start with a clean slate next time. Also
thanks to @visortgw for this suggestion!
- PATCH: Nice catch by @JimbobJay, when a secondary backup successfully completed, it was referencing
the incorrect backup media (network/usb), and was using the primary media type. This has now also
been fixed. Thank you!
- PATCH: General cleanup and spacing logic added for the error flag message on the setup menu that
now takes into consideration the different timezone name lenghts so that spacing looks correct.
BACKUPMON v1.8.10
v1.8.10 - (July 2, 2024)
- PATCH: Based on a good suggestion by @visortgw, a secondary-only backup option was added. This
was prompted when possible issues could arise where you might be unable to back up to your primary
backup target, upon which BACKUPMON would exit in an error state by default. Now, a "-secondary"
switch has been added that simply runs a secondary backup (without any purges). Example usage:
"backupmon -secondary". As always, you can hit "backupmon -h" or "backupmon -help" for a full list
of commands.
- PATCH: @vibroverbus made a good observation on some inconsistencies in the y/n prompts within the
script compared to other scripts such as AMTM. It seems the function I'm using would automatically
accept the y or n keypress and keep running without needing to hit enter. This function has now
been changed so you can you change your mind after typing y or n, and lets you correct yourself
before needing to manually hit the enter key now.
BACKUPMON v1.8.8
v1.8.8 - (June 30, 2024)
- PATCH: Looks like my last update didn't take into consideration the folks using BACKUPMON to back
up their environment to their local USB drive. Thanks much to @Just Started for reporting this!
New logic added to only consider erroring out on blank UNC/UNCDRIVE values when the backup media
type is NOT a USB target.
BACKUPMON v1.8.7
v1.8.7 - (June 29, 2024)
- PATCH: In further compliance with the 3006 firmware and the new BE devices, @visortgw wisely
noted that a "modprobe cifs" might just fix everything... and it sure did. Thanks for that! As of
BACKUPMON v1.8.7, you should have full CIFS functionality on the 3006 level firmware. Also, thanks
to @RMerlin for adding the CIFS libraries back in and making BACKUPMON functional again. ;)
- PATCH: In further troubleshooting BACKUPMON on 3006 with his beefy GT-BE98_Pro, @ExtremeFiretop
came across a bug that allowed backups to run if the UNC path was blank, but the drive had been
manually mounted in the background. BACKUPMON will now come to a halt if it finds UNC or UNCDRIVE
values being blank. Thanks for the heads-up and the testing. A free bug bounty BACKUPMON swag shirt
is on its way to you!! (LOL jk)
BACKUPMON v1.8.5
v1.8.5 - (June 21, 2024)
- MINOR: Added a tweak to the config menu that will now display a RED <-- Action Needed! arrow in
place of the "Source EXT USB Drive Mount Point" entry if the default sample mount point name is
still in use (ie. "/tmp/mnt/<selectusbdrive>"). Thanks to @Gen10 for running into this issue, and
figuring out that backup failures were happening because this mount point had not been changed yet.
The default entry written to the config file is now "/tmp/mnt/<selectusbdrive>".