omvbackup has changed output directory and filepath pattern without user intervention (seemingly after update)

1st Official Post

    For years omvbackup has reliably backed up with the method fsarchiver into my share called "Shared" and there into the subdirectory "omvbackup" (hardcoded behavior), with a backup set of 8 files having a fixed naming pattern backup-omv-YYYY-MM-DD_hh-mm-dd.ext , with most files being very tiny (a few KB most), the .fsa file containing the main backup data (ca 1.2 GB). So something like this:


    Code
    ls -l /srv/dev-disk-by-uuid-YOUR-UID-HERE/Shared/omvbackup/

-rw-rw-r--+ 1 root users  258 30.06.2024 00:07:47 backup-omv-2024-06-30_00-00-02.blkid
-rw-rw-r--+ 1 root users  379 30.06.2024 00:07:47 backup-omv-2024-06-30_00-00-02.fdisk
-rw-r--r--+ 1 root users 1.2G 30.06.2024 00:07:47 backup-omv-2024-06-30_00-00-02.fsa
-rw-rw-r--+ 1 root users  446 30.06.2024 00:07:47 backup-omv-2024-06-30_00-00-02.grub
-rw-rw-r--+ 1 root users  512 30.06.2024 00:07:47 backup-omv-2024-06-30_00-00-02.grubparts
-rw-rw-r--+ 1 root users 1.4K 30.06.2024 00:07:47 backup-omv-2024-06-30_00-00-02.packages
-rw-rw-r--+ 1 root users  149 30.06.2024 00:07:47 backup-omv-2024-06-30_00-00-02.sfdisk
-rw-rw-r--+ 1 root users 329K 30.06.2024 00:00:03 backup-omv-2024-06-30_00-00-02_u-boot.tar.bz


    But as I noted today somewhen in the recent 1-3 months the output pattern changed to: path/to/share/-YYYY-MM-DD_hh-mm-dd.ext with the ./omvbackup/backup-omv portion missing in the filepath pattern, and most alarming, the .fsa file missing entirely, concretely looking like this:



    I went to http://my-nas.local/#/system/backup/settings and re-configured it by changing the "keep" parameter from 45 to 40 and saved.


    Then I run it manually by using the "Backup" button, and could observe the failure again. No .fsa file and the filename pattern wrong:



    Environment:

    • omvbackup 7.1.4
    • OMV 7 on Armbian 24.5.1 Bookworm with Linux 6.6.31-current-odroidxu4
    • Odroid HC2

    Odroid HC2 - Armbian 24 Bookworm - OMV7

    • Official Post

    Cannot confirm this behavior. Just performed a backup and got the expected result. According to the changelog the version 7.1.4 was released on 2024-04-17. So no changes since your backup from June above.

    How can I invoke that plugin via SSH so that I can get the full log? So that I can share with you for proper analysis.


    Because after ** CONNECTION LOST ** in the web browser shell window showing the plugin progress, I get an error popup which contains the lines, that I saw in the web browser's shell output anyhow, even cut off even a bit earlier.

    Odroid HC2 - Armbian 24 Bookworm - OMV7

    And if omvbackup has not changed in the timeframe that I noted the screwup to start to occur, then probably something in my system, which omvbackup calls during its procedures, may have failed since then. I recall that the last update attempt at /#system/updatemgmt/updates has failed. Haven't had time to investigate yet. So probably that was the root cause.

    Odroid HC2 - Armbian 24 Bookworm - OMV7

    • Official Post

    You can try if removing and reinstalling the plugin solves the issue.


    Quote from porg

    How can I invoke that plugin via SSH so that I can get the full log?

    Logs are stored in /var/log/omv-backup.log

    I have not done anything in the meantime. But now that I know the log location, below is mine.


    Everything works, only the "FSArchiver backup" seems to fail.


    Possibly the file names starting with -YYYY-MM-DD_hh-mm-dd.ext without the prefix backup-omv- are a consequence of the backup failure due to a lack or error handling in your routines.

    Odroid HC2 - Armbian 24 Bookworm - OMV7

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login