Start a Backup

It is recommended to start BmuS as sudo to ensure that root files can also be backed up if desired.

A normal backup is started with the following command (it is assumed that BmuS is in the home directory).

sudo bash /home/user/bmus.sh

or

sudo bash ./bmus.sh

It is also possible to call BmuS with an alternative configuration file that has been stored next to the main configuration. This is pretty nice if you create a cron job and want to run different configurations at different times/days.

sudo CONFIG_FILE=/home/user/bmus2.conf /home/user/bmus.sh

DRY RUN

If you first want to test whether BmuS works without backing up, you can start it in dry run mode, i.e. a simulation run.

sudo bash /home/user/bmus.sh –dry-run

or

sudo bash /home/user/bmus.sh -n

What is simulated

• ✅ NAS mount/umount
• ✅ File copy (rsync –dry-run)
• ✅ Old backup deletion
• ✅ MySQL dump
• ✅ Dashboard generation
• ✅ Mail dispatch

What will NOT be changed:

• ❌ No files written to NAS
• ❌ No history entries added
• ❌ No emails sent
• ❌ No directories created

HELP

Help can be accessed using the following command.

sudo bash /home/user/bmus.sh –help

Docker commands

If you are using the Docker version, the program files are locked in the container, which means you can no longer simply call it with sudo bash bmus.sh.

There are two ways to solve this problem.