I didn't know that I get a message when the backup failed, even if this option is not checked. Thanks for that hint.
But wouldn't it also be useful to have a tabular overview of the last backups?
I think it's not that hard to create, but sure, its a nice to have.
I would like to avoid circumstances, where backup files were generated, but empty (no error message sent) and where backup files were corrupted during transfer. I had both situations over the last while.
Thahts why I ended in the following backup strategy:
1) Backup every night for 7 days in seperate folder
This is already possible.
Anyways, the backup transfer throught ftp went not very well for me. Irregular abortions, ending in corrupted backups.
Direct backup in a cifs mounted folder went not very well, either. This was very slow, and lasted for too long. This may be down to my infrastructure, but this isn't changeable for me, so far.
So I end up in storing the backup in a local folder, which is okay for now.
2) rsync to remote backup
Every night, after the backup runs, I rsync the changed folders to a seperate backup-space, cifs mounted (which strangely runs faster than through direct backup in the mounted folder)
3) Get clarification:
Overview over all stored backups on the backup-space with md5sums of all files, compared with the local ones, to ensure the backup is not corrupted.
I know, this all could be done through shell scripts, but it would nice to have an overview in the Directadmin, too.
For me, backups are crucial, that is why I like to be secured twice.