backup_and_restore.sh script not actually backing up

Skittluier

Hi all!

I’m using the backup_and_restore.sh script to back up everything my Mailcow server has. (to be precise, I’ve used: ./backup_and_restore.sh backup all)

Now, after the backup process has completed, everything looks fine… until I go to the backup folder, where I find nothing.

What could be the cause of this? I’ve checked the Mailcow log but found nothing of use at the moment.

chriss

Did you try running it from the /opt/mailcow-dockerized directory as ./helper-scripts/backup_and_restore.sh backup all?
Or as the full path to the script /opt/mailcow-dockerized/helper-scripts/backup_and_restore.sh backup all?

Did you edit the script?

Do you run the script as root or using sudo? - Either should work, but unlikely to work as a regular user.

Did you export MAILCOW_BACKUP_LOCATION="/your/backup/destination" before running the script?

Are you checking the correct destination directory?

Incorrect permissions on the destination directory?

Insufficient space on the destination filesystem?

Which log are you consulting? Perhaps you can share it?

SebS

chriss

Incorrect permissions on the destination directory?

In addition to that: Last time I checked there was a bug in the backup script that demanded nonsensical permissions on the target destination. It wasn’t enough when only the executing user owned it.
IIRC incorrect (or “incorrect”) permissions terminate the script with an according message, though.

Skittluier

chriss

SebS

Thanks for your swift answers!

Did you try running it from the /opt/mailcow-dockerized directory as ./helper-scripts/backup_and_restore.sh backup all?
Or as the full path to the script /opt/mailcow-dockerized/helper-scripts/backup_and_restore.sh backup all?

I have just tried it, but unfortunately that didn’t work.

Did you edit the script?

Nope.

Do you run the script as root or using sudo? - Either should work, but unlikely to work as a regular user.

Yes, I ran it as root.

Did you export MAILCOW_BACKUP_LOCATION=“/your/backup/destination” before running the script?

No, I didn’t, but I did tell the script where the backup should be when being asked for it.

Are you checking the correct destination directory?

Yup!

Incorrect permissions on the destination directory?

I’ve created the directory as root and am executing the script as root. I guess that’s fine?

Insufficient space on the destination filesystem?

Nah.

Which log are you consulting? Perhaps you can share it?

I’m executing docker compose logs. This mostly shared the unbound-mailcow logs.

In addition to that: Last time I checked there was a bug in the backup script that demanded nonsensical permissions on the target destination. It wasn’t enough when only the executing user owned it.
IIRC incorrect (or “incorrect”) permissions terminate the script with an according message, though.

I’ll try this soon and will let you know how it went!

DocFraggle

Maybe share the complete output, from the beginning of running the script

Skittluier

Hey guys,

So I’ve been nosing a little more in the documentation and the .env file, and I see that the backup/restore directory Mailcow is asking for in their backup/restore script doesn’t really have any effect. It’s the MAILCOW_BACKUP_LOCATION key in the .env file that’s relevant to that script, which is my /tmp/ folder. (https://docs.mailcow.email/backup_restore/b_n_r-backup/#backup-path)

I’ve checked that folder, and all the manual backups I’m performing are being saved there.

So luckily, I’ve got a backup of Mailcow and now can continue. Thanks for all the support here! <3