Release Notes

Download

You can find the latest versions here:
https://www.back-me-up-scotty.com/docs/what-is-bmus/download/

2026-02-03

Update

Updated file(s):
bmus.sh (v. 27.1)
language.lang (26.8)

Not updated:
bmus.conf (v.25.5)
bmus_dashboard_pro.sh (v. 26.1)
bmus_dashboard.sh (v. 25.2)
bmus_encryption.sh (v.24.4)
.bmus_credentials (v.23.1)

Fix

Minor bug fixes for terminal commands
Duplicates removed and sorted

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

Important: Do not overwrite an existing bmus.conf. Instead, compare your old bmus.conf file with the new version and copy the new blocks and changes to version no.

2026-01-26

Update

Updated file(s):
bmus.sh (v. 27.0)
bmus.conf (v.25.5)
language.lang (26.7)

Not updated:
bmus_dashboard_pro.sh (v. 26.1)
bmus_dashboard.sh (v. 25.2)
bmus_encryption.sh (v.24.4)
.bmus_credentials (v.23.1)

Disk Space Safety Stop

No more full disks or quota limits crashing your backup!

Pre-Flight Check: Added MIN_FREE_SPACE_GB to bmus.conf. BmuS now checks available space on the destination before starting the backup process.
Quota Aware: Works with physical disk limits (USB/HDD) as well as NAS User Quotas.
Smart & Safe:
- If space is below the threshold, BmuS aborts immediately and performs a clean unmount to prevent file system corruption or “Disk Full” lockups.
- Correctly handles Encrypted backups (checks the physical underlying storage) and Flat/Deduplicated structures.

Docker Security Improvements

Permission Hardening: The Docker entrypoint.sh now automatically detects your CREDENTIALS_FILE (defined in config) and enforces strict chmod 600 permissions on startup. This ensures sensitive NAS and Database passwords remain secure within the container environment.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

Important: Do not overwrite an existing bmus.conf. Instead, compare your old bmus.conf file with the new version and copy the new blocks and changes to version no.

2026-01-20

Updated file(s):
bmus.sh (v. 26.9)
bmus.conf (v.25.4) (version no. has not changed)

Not updated:
bmus_dashboard_pro.sh (v. 26.1)
bmus_dashboard.sh (v. 25.2)
language.lang (26.6)
bmus_encryption.sh (v.24.4)
.bmus_credentials (v.23.1)

Fix

The check to see if the path to bmus_enctryption.sh exists has been improved.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

Important: Do not overwrite an existing bmus.conf. Instead, compare your old bmus.conf file with the new version and copy the new blocks.

2026-01-19 II

Updated file(s):
bmus.sh (v. 26.8)
bmus.conf (v.25.4)
bmus_dashboard_pro.sh (v. 26.1)
bmus_dashboard.sh (v. 25.2)

Not updated:
language.lang (26.6)
bmus_encryption.sh (v.24.4)
.bmus_credentials (v.23.1)

Updates

Added Privacy & Statistics.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

Important: Don’t overwrite an existing bmus.conf .Instead follow these steps:

2026-01-19

Updated file(s):
bmus.sh (v. 26.7)

Not updated:
bmus.conf (v.25.3)
language.lang (26.6)
bmus_dashboard_pro.sh (v. 26.0)
bmus_dashboard.sh (v. 25.1)
bmus_encryption.sh (v.24.4)
.bmus_credentials (v.23.1)

Updates

Added some more output from the GHS function to the backup log.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

Important: Don’t overwrite an existing bmus.conf .Instead follow these steps:

2026-01-17

Updated file(s):
bmus.sh (v. 26.6)
bmus.conf (v.25.3)
language.lang (26.6)
bmus_dashboard_pro.sh (v. 26.0)
bmus_dashboard.sh (v. 25.1)

Not updated:
bmus_encryption.sh (v.24.4)
.bmus_credentials (v.23.1)

Updates

Smart Retention Strategy (GFS)

This release introduced a major upgrade to the cleanup logic, moving from simple age-based deletion to a sophisticated “Grandfather-Father-Son” (GFS) rotation scheme.

Feature: Grandfather-Father-Son (GFS) Retention
- Concept: Instead of deleting every backup older than X days, the script now intelligently “tags” specific backups to be kept for longer periods.
- Implementation:
  - Daily: Keeps all backups for the last 7 days (configurable).
  - Weekly: Automatically identifies backups created on Sundays and tags them with a _RETENTION_WEEKLY_KEEP.txt marker file. These are kept for 4 weeks (configurable).
  - Monthly: Automatically identifies backups created on the 1st of the month and tags them with _RETENTION_MONTHLY_KEEP.txt. These are kept for 12 months (configurable).
- Benefit: This dramatically reduces storage consumption while maintaining a long historical history (up to a year) without requiring manual intervention.
Update: Universal Cleanup Logic
- Refactored cleanup_old_encrypted_backups and cleanup_old_unencrypted_backups to respect the new GFS tags.
- The cleanup logic now checks for the existence of the tag files before deciding to delete a folder, overriding the standard BACKUP_AGE_DAYS limit if a tag is present.

Cloud Persistence & Initialization Logic Overhaul

Feature: Persistent Rclone Configuration (RCLONE_CFG_PATH)
- Problem: In previous Docker versions, running rclone config inside the container saved the configuration to an internal path. When the container was recreated (update/reboot), the Cloud authentication tokens were lost.
- Solution: Introduced a smart persistence logic. You can now define a custom path (e.g., /config/rclone.conf) via the RCLONE_CFG_PATH variable.
- Auto-Import Logic: The script now checks three scenarios at startup:
  1. Found: If the custom config exists and CLOUD_BACKUP="1", it is used immediately.
  2. Import: If the custom config is missing or empty and CLOUD_BACKUP="1" but an internal config exists (e.g., after a fresh rclone config), the script automatically copies the internal config to the persistent location.
  3. Missing: Warns the user if CLOUD_BACKUP="1" and no configuration is found at all.

Dashboard pro update

In the “Deletion History” graph, you will see a line that shows how many files have been deleted. The dots on this line indicate now the GFS status of the backup on that day by their color and size:

A thick green dot means: “A monthly backup was marked on this day.”
A medium blue dot means: “This was a Sunday/weekly backup.”
The small red dots are the normal daily backups.

This helps you to immediately see when the important “milestones” (week/month) occurred in the graph.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

Important: Don’t overwrite an existing bmus.conf .Instead follow these steps:

Native installation

Copy this block tight after CLOUD_LOG_FILE="$HOME_PI/rclone_last_run.log":

# Custom Rclone Config Path (Optional)
# If set, BMUS will use this specific configuration file.
# Useful for Docker persistence (e.g., mapped volume) or custom locations.
# Logic: If this file does not exist, BMUS tries to copy the internal config here.
# Leave empty "" to use standard rclone behavior (default locations, native installation).
# For DOCKER version path would be /config/rclone.conf
RCLONE_CFG_PATH=""

Docker installation

Copy this block right after CLOUD_LOG_FILE="/config/rclone_last_run.log"":

# Custom Rclone Config Path (Optional)
# If set, BMUS will use this specific configuration file.
# Useful for Docker persistence (e.g., mapped volume) or custom locations.
# Logic: If this file does not exist, BMUS tries to copy the internal config here.
# Leave empty "" to use standard rclone behavior (default locations, native installation).
# For DOCKER version path would be /config/rclone.conf
RCLONE_CFG_PATH="/config/rclone.conf"

Copy this block right after BACKUP_AGE_DAYS="14".

# -------------------------------------------------------------------------
# SMART RETENTION STRATEGY (GFS - Grandfather-Father-Son)
# -------------------------------------------------------------------------
# Creates a smart backup history instead of strictly deleting everything 
# after X days. It uses marker files inside the backup folders to protect 
# specific backups (Sundays, 1st of Month) from deletion.
#
# REQUIREMENTS: 
# - Works best with DEDUP_ENABLE="1" or BACKUP_USE_DATE_FOLDERS="1".
# - It does not work with flat structure backups 
# - If enabled, BACKUP_AGE_DAYS above is ignored in favor of the settings below.
#
# 1 = Enabled / 0 = Disabled (Standard BACKUP_AGE_DAYS applies)
RETENTION_ENABLE="1"

# DAILY: How many days should ALL backups be kept?
# Example: "7" = Keep every single backup of the last 7 days.
RETENTION_KEEP_DAILY="14"

# WEEKLY: How many weeks should one backup per week (Sunday) be kept?
# Example: "4" = Keep the last 4 Sunday backups.
RETENTION_KEEP_WEEKLY="4"

# MONTHLY: How many months should one backup per month (1st of Month) be kept?
# Example: "12" = Keep the backup of the 1st day for 12 months.
RETENTION_KEEP_MONTHLY="12"

# -------------------------------------------------------------------------

2026-01-12

Updated file(s):
bmus.sh (v. 26.4)
bmus_encryption.sh (v.24.4)
language.lang (26.4)

Not updated:
bmus_conf (v.25.1)
bmus_dashboard_pro.sh (v. 25.9)
bmus_dashboard.sh (v. 25.0)
.bmus_credentials (v.23.1)

Update

1. Robust Interrupt Handling (CTRL+C Safety)

The Issue: Previously, interrupting BmuS (sending SIGINT via CTRL+C) while heavy processes like rsync were running could lead to “zombie” states where the script continued in the background or the termination message was swallowed by the output buffer.
The Fix: Implemented a dedicated ctrl_c_handler function.
- The handler now explicitly traps INT and TERM signals.
- It uses a carriage return (\r) technique to force the cursor to the beginning of the line, ensuring the “Interrupted by User” warning overwrites any pending rsync output and is clearly visible on the console.
- It bypasses standard buffers by writing directly to stderr, guaranteeing immediate visual feedback before performing a clean exit.

2. Local Backup Safety Mechanism

The Issue: When using BmuS for local backups (e.g., to a USB drive) by leaving NAS_IP empty, a missing mount could cause BmuS to write backup data directly to the root partition (SD card), potentially filling up the system drive.
The Fix: Added a proactive “Mountpoint Check” for local configurations.
- If NAS_IP is not set, the script now verifies if the defined BACKUP_PATH is a valid mountpoint.
- If the path is not a mountpoint (indicating the drive is missing), a prominent warning is displayed to the user (both in the log and on the console) before proceeding, preventing accidental system partition overflow.

3. Encryption Stability Improvements

The Issue: The encryption module passed the password file content directly to gocryptfs. If the password file existed but was empty (0 bytes), this could lead to undefined behavior or silent failures during the mount process.

The Fix: Added a pre-validation step in bmus_encryption.sh.
- BmuS now checks if the password file is valid and contains data (-s check) before attempting to pipe it to the encryption binary.
- If the file is empty, the process aborts immediately with a clear error message, preventing invalid mount attempts.

4. Enhanced Cleanup Logic

The Change: Separated the user-facing “Interrupt Handler” from the technical “Cleanup Function”.
The Benefit: The cleanup function (trap ... EXIT) now focuses solely on resource management (unmounting drives, removing lock files/temp files) without cluttering the output, while the interrupt handler manages user communication. This ensures that resources are always released correctly, regardless of whether the script finished successfully, failed with an error, or was killed by the user.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials.

2026-01-11

Updated file(s):
bmus.sh (v. 26.3)
bmus_conf (v.25.1)
bmus_dashboard_pro.sh (v. 25.9)
language.lang (26.3)
bmus_dashboard.sh (v. 25.0)

Not updated:
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Update

BmuS now supports cloud backups via rclone. Supported cloud hosters are:

1Fichier
Akamai NetStorage
Alias for an existing remote
Amazon Drive
Amazon S3 Compliant Storage Providers including AWS, Alibaba, Ceph, China Mobile, Cloudflare, ArvanCloud, Digital Ocean, Dreamhost, Huawei OBS, IBM COS, IDrive e2, IONOS Cloud, Lyve Cloud, Minio, Netease, RackCorp, Scaleway, SeaweedFS, StackPath, Storj, Tencent COS, Qiniu and Wasabi
Backblaze B2
Better checksums for other remotes
Box
Cache a remote
Citrix Sharefile
Combine several remotes into one
Compress a remote
Dropbox
Encrypt/Decrypt a remote
Enterprise File Fabric
FTP
Google Cloud Storage (this is not Google Drive)
Google Drive
Google Photos
Hadoop distributed file system
HiDrive
HTTP
In memory object storage system
Internet Archive
Jottacloud
Koofr, Digi Storage and other Koofr-compatible storage providers
Local Disk
Mail.ru Cloud
Microsoft Azure Blob Storage
Microsoft OneDrive
OpenDrive
OpenStack Swift (Rackspace Cloud Files, Memset Memstore, OVH)
Pcloud
premiumize.me
Put.io
seafile
Sia Decentralized Cloud
SMB / CIFS
SSH / SFTP
Sugarsync
Transparently chunk/split large files
Union merges the contents of several upstream fs
Uptobox
WebDAV
Yandex Disk
Zoho

If Cloud Backup is used, the dashboard (Standard Dashboard & Pro Version) will show the status.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

If so, overwrite.

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials. Instead copy following block to the bottom (right after BACKUP_FILETYPES=("*") of the file.

# ---------------------------------------------------------
# DOCKER CONTAINER SETTINGS
# ----------- --------------------------------------------------------------
# This section is ONLY evaluated by the Docker container (entrypoint.sh).
# The actual backup script ignores these lines.
#
# Schedule for automatic backups (cron format):
# Minute Hour Day Month Weekday
#
# Examples:
# “0 3 * * *”   = Daily at 3:00 a.m.
# “30 2 * * 0”  = Every Sunday at 2:30 a.m.
# “”            = Leave blank for manual mode (no automation)
#
CRON_SCHEDULE="0 3 * * *"

# -------------------------------------------------------------------------
# CLOUD BACKUP (via rclone)
# -------------------------------------------------------------------------
# BMUS can upload your data encrypted or unencrypted to the cloud.
# Prerequisite: 'rclone' is installed and configured via 'rclone config'.
#
# 1 = Enabled / 0 = Disabled
CLOUD_BACKUP="0"

# Path to Rclone-Log
CLOUD_LOG_FILE="$HOME_PI/rclone_last_run.log" # native installation
#CLOUD_LOG_FILE="/config/rclone_last_run.log" # docker installation

# What did you name the connection in 'rclone config'?
# IMPORTANT: Enter the exact name you chose during setup.
#
# Popular Providers:
# - Dropbox, Google Drive, OneDrive, Amazon S3, Nextcloud, pCloud, etc.
#
# Example: If you named your connection "dropbox", enter "dropbox" here.
CLOUD_REMOTE=""

# Destination path inside the cloud storage
# This folder will be created automatically.
CLOUD_TARGET_PATH="/Backups"

# Should the cloud upload be simulated in "Dry-Run" mode?
# 1 = Yes (shows what would happen)
# 0 = No
CLOUD_DRY_RUN_CHECK="1"

Change this block:

# -------------------------------------------------------------------------
# BACKUP EXCLUSIONS
# -------------------------------------------------------------------------
# Files/folders to be excluded from the backup. You can also put a 
# .backupignore file into a folder to exclude.

EXCLUDE_ITEMS=(
    ".git"
    "*.tmp"
    "*.cache"
)

to this:

# -------------------------------------------------------------------------
# BACKUP EXCLUSIONS
# -------------------------------------------------------------------------
# Files/folders to be excluded from the backup. You can also put a 
# .backupignore file into a folder to exclude.

EXCLUDE_ITEMS=(
    ".git"
    "*.tmp"
    "*.cache"
    ".DS_Store"       # Mac Metadata (Disallowed by Dropbox)
    ".~lock.*"        # Office Lock Files (Disallowed by Dropbox)
    "Thumbs.db"       # Windows Thumbnails
    "@eaDir/"         # Synology Indexing
)

2026-01-01

Updated file(s):
bmus.sh (v. 26.0)
bmus_conf (v.24.9)

Not updated:
bmus_dashboard_pro.sh (v. 25.8)
language.lang (26.1)
bmus_dashboard.sh (v. 24.9)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Update

1. In bmus.sh, the logic for searching for bmus.conf and the language files has been changed and made more universal. BmuS now automatically finds the language files in both the normal installation and the Docker installation. It is no longer necessary to maintain two versions of bmus.sh. In addition, it is no longer necessary to manually adjust the path to bmus.conf in bmus.sh. The manual has also been changed in this regard.

2. The MYSQL CONFIGURATION and BACKUP SOURCES blocks have been moved from the end of the configuration file to the top of bmus.conf.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

If so, overwrite the old version of bmus.sh.

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials. Instead move following blocks of your existing bmus.conf from the bottom to the top (right after HOME_PI="/home/user") of the file.

# -------------------------------------------------------------------------
# MYSQL CONFIGURATION
# -------------------------------------------------------------------------
# If you have mysql/mariaDb databases running on your machine, you can copy
# them. 
# Activate MySQL Backup: 1 = enabled, 0 = disabled
BACKUP_SQL="0"

# MySQL databases to be backed up (Array)
MYSQL_DBS=("database_1" "database_2")

# -------------------------------------------------------------------------
# BACKUP SOURCES
# -------------------------------------------------------------------------
# Array with all paths & files to be backed up
# Wildcards are possible, e.g. "/usr/local/bin/*.sh"
# Add your own paths here.

BACKUP_SOURCES=(
   # "/var/www/"
   # "/home/user/Desktop/"
   ) 

# -------------------------------------------------------------------------
# BACKUP EXCLUSIONS
# -------------------------------------------------------------------------
# Files/folders to be excluded from the backup. You can also put a 
# .backupignore file into a folder to exclude.

EXCLUDE_ITEMS=(
   # ".git"
   # "*.tmp"
   # "*.cache"
)

2025-12-31

BmuS is now available in a docker container

You need to download the starter pack:
https://www.back-me-up-scotty.com/download/Bmus-Docker.zip

Follow the README.txt in the zip archive to configure and install.

2025-12-29 – II

Updated file(s):
bmus_dashboard_pro.sh (v. 25.8)
language.lang (26.1)

Not updated:
bmus.sh (v. 25.9)
bmus_dashboard.sh (v. 24.9)
bmus_conf (v.24.8)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Update

Two more graphs has been added to the Dashboard-Pro.

1. File Type (count)

A pie chart showing the number of different file types that are stored.

2. Storage Usage (Top 10)

A pie chart showing the ratio of the file sizes of the individual file types to each other.

Note: With encryption, only available if READABLE_NAMES=1

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

If so, overwrite the old version of bmus_dashboard_pro.sh and language.lang with the new versions.

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials.

2025-12-29 – I

Updated file(s):
bmus_dashboard_pro.sh (v. 25.7)
language.lang (26.0)

Not updated:
bmus.sh (v. 25.9)
bmus_dashboard.sh (v. 24.9)
bmus_conf (v.24.8)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Update

The units of the Y-axes of various graphs have been changed from fixed values to variable values. For example, instead of 50,000 MB, 50 GB is now displayed. Adjustments are made when appropriate. 1000 MB -> 1 GB, 1000 GB -> 1 TB.

Installation

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials.

2025-12-25

Updated file(s):
bmus_dashboard_pro.sh (v. 25.6)
language.lang (25.9)

Not updated:
bmus.sh (v. 25.9)
bmus_dashboard.sh (v. 24.9)
bmus_conf (v.24.8)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Update

Two more graphs has been added to the Dashboard-Pro.

1. Cumulative Transfer Volume (30 Days):

How much traffic has been backed up in total last month? This cumulative graph shows the increase in data usage over the month. A steep curve means a lot of traffic, a flat curve means little traffic.

Advantage: Helps with capacity planning (e.g., “Approximately 500 GB of data transfer per month”).

2. Performance Consistency (Size vs. Duration):

This scatter plot shows the backup size (X-axis) in relation to the duration (Y-axis). Each point represents a backup run from the last 30 days.

The benefit:

Normal points: Ideally, these form a diagonal line from the bottom left to the top right (more data = takes longer).

Anomalies (this is the added value): A point at the top left (little data, but extremely long duration) immediately indicates a technical problem (network timeout, hard drive going to sleep, CPU load at its limit) that is difficult to identify as “unnatural” in the other graphs.

Fix

The pie chart “Result Overview” (also) displayed historical errors and not exclusively those (if any) from the current run.

Installation

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials.

2025-12-23

Updated file:
bmus.sh (v. 25.9)
bmus_dashboard_pro.sh (v. 25.4)
language.lang (25.7)

Not updated:
bmus_dashboard.sh (v. 24.9)
bmus_conf (v.24.8)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Update

A retention history has been added to Dashboard Pro, allowing you to track the deletion history for the last 30 days.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

If so, overwrite the old version of bmus.sh, bmus_dashboard_pro.sh and language.lang with the new versions.

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials.

2025-12-17

Updated file:
bmus.sh (v. 25.8)
bmus_dashboard.sh (v. 24.9)
bmus_dashboard_pro.sh (v. 25.3)
language.lang (25.6)

Not updated:
bmus_conf (v.24.8)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Fix

In dry run mode, with encryption enabled, an error could occur in which BmuS attempted to access non-existent paths or—if the paths existed locally—mounted a real encryption layer even though only a simulation was intended.

Fix

The function restart_network_interface (in the verify section) does not check for dry run mode. If a verify timeout were to occur during a dry run (unlikely, but possible), the script would actually restart the host’s network interface.

Fix

Orphaned variables in all language files have been removed.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

If so, overwrite the old version of bmus.sh, bmus_dashboard.sh, bmus_dashboard_pro.sh and language.lang with the new versions.

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials.

2025-12-15

Updated file:
bmus.sh (v. 25.6)
bmus_dashboard_pro.sh (v. 25.2)

Not updated:
bmus_conf (v.24.8)
bmus_dashboard.sh (v. 24.8)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)
language.lang (25.4)

Fix

Because the deduplication log remains empty when mount mode NAS_MOUNT_MODE="cifs_optimized" is active, the log will be now automatically hidden in the dashboard pro.

Installation

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials.

2025-12-13

Updated file:
bmus.sh (v. 25.5)
bmus_conf (v.24.8)
language.lang (25.4)

Not updated:
bmus_dashboard.sh (v. 24.8)
bmus_dashboard_pro.sh (v. 25.1)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Update

Three mount options have been added to bmus.conf: SMB Simple, SMB Optimized, and NFS, as a new protocol.

Fix

Numerous changes have been made to significantly improve performance.

Fix

The method used to calculate the deduplication rate and savings from deduplication has been changed.

Installation

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials. Compare the changes in bmus.conf with your existing bmus.conf and transfer them 1:1 to your bmus.conf.

2025-12-12

Updated file:
bmus.sh (v. 25.4)
language.lang (25.3)

Not updated:
bmus_dashboard.sh (v. 24.8)
bmus_dashboard_pro.sh (v. 25.1)
bmus_conf (v.24.7)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Fix

A minor bug has been fixed that caused a log message to appear incomplete.

Installation

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials.

2025-12-11

Updated file:
bmus.sh (v. 25.3)
language.lang (25.2)

Not updated:
bmus_dashboard.sh (v. 24.8)
bmus_dashboard_pro.sh (v. 25.1)
bmus_conf (v.24.7)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Fix

The verification logic had a minor bug, which has been fixed. In addition, detailed log outputs have been added to the verification logic.

Installation

Important: Don’t overwrite an existing bmus.conf or .bmus_credentials.

2025-12-10

Updated file:
bmus.sh (v. 25.2)
bmus_dashboard.sh (v. 24.8)
bmus_dashboard_pro.sh (v. 25.1)
bmus_conf (v.24.7)

Not updated:
language.lang (25.1)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Fix

Data mismatch. For example, the “New Directories” tile shows that 198 directories were backed up. However, the “📂 New Directories” section below the “Top 10 Changes” shows “No new directories in this backup.”

In the language file, LOG_PREFIX_NEW_DIR is usually defined as “[NEW] directory“.

This is where the error lies: By default, the grep command interprets the text in the brackets [NEW] as a regular expression (regex). For grep, [NEW] means “search for one of the letters N, E, or W.”

However, the log file contains the exact text [NEW]. Since grep searches for individual letters but finds a bracket, the search fails. The list remains empty, and the dashboard incorrectly states: “No new directories”.

The grep command hast to interpret the search term as a fixed string rather than a command. This is done now by using the -F switch.

Update

“📂 New Directories” section and “Top 10 Changes” sections is now scrollable. A new variable has been added to bmus.conf. DASHBOARD_LINE_NEW_DIRS="300". This variable can be used to specify the maximum number of new directory entries to be displayed.

This feature has been added to Dashboard Standard and Dashboard Pro.

Pro dashboard buyers: Please contact me with your data (Order-ID, Name & email) to get the update.

Installation

If you already have BmuS installed, check whether all other files (not updated) in your installation match the versions in the archive. See above.

If so, overwrite the old version of bmus.sh, bmus_dashboard.sh or bmus_dashboard_pro.sh, with the new versions.

Important: Don’t overwrite an existing bmus.conf. Instead just add following lines right after DASHBOARD_LINE_LOGS="500" and change version number to v.24.7.

# How many new dirs should be integrated into the dashboard
DASHBOARD_LINE_NEW_DIRS="300"

2025-12-09

Updated file:
bmus.sh (v. 25.1)
bmus_dashboard.sh (v. 24.7)
bmus_dashboard_pro.sh (v. 25.0)
language.lang (25.1)

Not updated:
bmus_conf (v.24.6)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Update
Three more tiles have been added to the Pro Dashboard.

AVG Duration (30 Days)
Success Rate (30 Days)
Max Size (30 Days)

Pro dashboard buyers: Please contact me with your data (Order-ID, Name & email) to get the update.

Installation

2025-12-08 – II

Updated file:
bmus_dashboard_pro.sh (v. 24.9)
language.lang (25)

Not updated:
bmus.sh (v. 25)
bmus_conf (v.24.6)
bmus_dashboard.sh (v. 24.6)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Fix & Update
The “Backup Type Distribution over Time” graph has been removed due to redundancy. In most cases, it showed the same data as “Backup Efficiency (New Files & Directories)”.

Instead, two new graphs have been added:

Seconds per File
Average File Size (New Files)

These two graphs are performance indicators for changes. If nothing changes on your system (pure deduplication), these graphs will show a “zero line.”

Pro dashboard buyers: Please contact me with your data (Order-ID, Name & email) to get the update.

Installation

If you already have BmuS installed, check whether all other files in your installation match the versions in the archive. See above.

If so, overwrite the old version of bmus_dashboard_pro.sh, language.lang with the new one.

Users of the standard dashboard do not have to, but can update.

2025-12-08 – I

Updated file:
bmus.sh (v. 25)
bmus_dashboard.sh (v. 24.6)
bmus_dashboard_pro.sh (v. 24.8)
language.lang (24.9)

Not updated:
bmus_conf (v.24.6)
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)

Update
A tile “Saved (Dedup)” has been added to the Pro Dashboard that shows how much data has been saved through deduplication in the current backup run.

Pro dashboard buyers: Please contact me with your data (Order-ID, Name & email) to get the update.

Installation

If you already have BmuS installed, check whether all other files in your installation match the versions in the archive. See above.

If so, overwrite the old version of bmus.sh, bmus_dashboard.sh, bmus_dashboard_pro.sh, language.lang with the new one.

Users of the standard dashboard do not have to, but can update.

2025-12-07

Updated file:
bmus.sh (v. 24.9)
bmus_conf (v.24.6)
language.lang (24.8)
bmus_dashboard_pro.sh (v. 24.7)

Not updated:
bmus_encryption.sh (v.24.3)
.bmus_credentials (v.23.1)
bmus_dashboard.sh (v. 24.5)

Update
The dashboard pro has been supplemented with a graph that logs and records the progress of RAM, CPU, and I/O wait over the duration of the backup.

Pro dashboard buyers: Please contact me with your data (Order-ID, Name & email) to get the update.

Installation

If you already have BmuS installed, check whether all other files in your installation match the versions in the archive. See above.

If so, overwrite the old version of bmus.sh, bmus_dashboard_pro.sh, language.lang with the new one. Do not overwrite bmus_conf, since your settings will be gone. Instead find and copy the whole section “=== [ Resource Monitoring Config ] ===” to your existing config. Update the version number to 24.6, so you know this file has been updated.

Users of the standard dashboard do not have to, but can update.

2025-12-05

Updated file:

bmus_dashboard_pro.sh (v. 24.5 -> v. 24.6)

Not updated:
bmus.sh (v. 24.8)
bmus_encryption.sh (v.24.3)
bmus_conf (v.24.5)
.bmus_credentials (v.23.1)
language.lang (24.7)
bmus_dashboard.sh (v. 24.5)

Fix
The graphs (1) Backup type distribution over time and (2) Deduplication efficiency over time have been changed from linear to logarithmic.

(1) If a backup recorded many changes on one day (e.g., 200 changed files) and only two changes on the next, these graphs could not be seen on the grid.
(2) A low deduplication efficiency of, for example, 0.7% resulted in the graph always remaining close to the x-line. The graph is now zoomed and draws a noticeable and comparable graph even at low deduplication efficiency.

Pro dashboard buyers: Please contact me with your data (Order-ID, Name & email) to get the update.

Installation

If you already have BmuS installed, check whether all other files in your installation match the versions in the archive. See above.

If so, overwrite only the old version of bmus_dashboard.sh or bmus_dashboard_pro.sh with the new one.

2025-12-04

Updated file:
bmus_dashboard.sh (v. 24.3 -> v. 24.5)
bmus_dashboard_pro.sh (v. 24.3 -> v. 24.5) (not in archive)

Not updated:
bmus.sh (v. 24.8)
bmus_encryption.sh (v.24.3)
bmus_conf (v.24.5)
.bmus_credentials (v.23.1)
language.lang (24.7)

Update
Added “Light Mode” to the dashboard. Users can now switch between dark and light mode.

Download archive: https://www.back-me-up-scotty.com/download/bmus.zip
(Note: Standard Dashboard included. Pro-Dashboard is not.)

Pro dashboard buyers: Please contact me with your data (Order-ID, Name & email) to get the update.

Installation

If you already have BmuS installed, check whether all other files in your installation match the versions in the archive. See above.

If so, overwrite only the old version of bmus_dashboard.sh or bmus_dashboard_pro.sh with the new one.

2025-12-03

Updated file:
bmus.sh (v. 24.7 -> v. 24.8)

Not updated:
bmus_encryption.sh (v.24.3)
bmus_dashboard.sh (v.24.3)
bmus_dashboard_pro.sh (v.24.3) (not in archive)
bmus_conf (v.24.5)
.bmus_credentials (v.23.1)
language.lang (24.7)

Fixed Issue #1
The retention logic has been changed. Under certain circumstances, old folders and files were not deleted if they had been changed in the meantime by the NAS or by another external system. BmuS was checking how old the file was based on the file age, not based on the folder name (e.g. 2025-11-11). However, if the timestamp of the last change to a file or folder has changed, BmuS concludes that the file should not be deleted (depending on the settings for deletion BACKUP_AGE_DAYS and ENCRYPTED_BACKUP_AGE_DAYS).

BmuS now checks the folder name.

Important: The new retention logic only works for encrypted (BACKUP_ENCRYPTION="1") files if READABLE_NAMES=1 is used. If this is not the case (BACKUP_ENCRYPTION="1", READABLE_NAMES=0), BmuS falls back on the file date or modification date. This can then lead to folders not being deleted and cannot be solved technically in any other way, because BmuS will not be able to read the folder name (e.g. 2025-11-11) anymore.

Fixed Issue #2
Deleted files and folders were not counted correctly and recorded in the dashboard.

Installation

Download archive: https://www.back-me-up-scotty.com/download/bmus.zip
If you already have BmuS installed, check whether all other files in your installation match the versions in the archive. See above.
If so, overwrite only the old version of bmus.sh with the new one.
Change the path to the location of your bmus.conf.

Download

2026-02-03

Update

2026-01-26

Update

Docker Security Improvements

2026-01-20

Fix

2026-01-19 II

Updates

2026-01-19

Updates

2026-01-17

Updates

Smart Retention Strategy (GFS)

Cloud Persistence & Initialization Logic Overhaul

Dashboard pro update

Native installation

Docker installation

2026-01-12

1. Robust Interrupt Handling (CTRL+C Safety)

2. Local Backup Safety Mechanism

3. Encryption Stability Improvements

4. Enhanced Cleanup Logic

2026-01-11

2026-01-01

2025-12-31

2025-12-29 – II

2025-12-29 – I

2025-12-25

2025-12-23

2025-12-17

2025-12-15

2025-12-13

2025-12-12

2025-12-11

2025-12-10

2025-12-09

2025-12-08 – II

2025-12-08 – I

2025-12-07

2025-12-05

2025-12-04

2025-12-03

Next

Searching in