omv-backup improvement

  • A few words about the backup plugin.

    It works as intended.

    I find that the backup file names lack a unique identifier for the backup method.

    For example, when backing up with fsarchiver, it is hard to find the corresponding files on the backup media with a regular expression.

    For example:

    -rw-r--r-- 1 root user 928 Oct 18 00:04 backup-omv-2023-10-18_00-00-01.packages

    -rw-r--r-- 1 root user 512 Oct 18 00:04 backup-omv-2023-10-18_00-00-01.grubparts

    -rw-r--r-- 1 root user 446 18 Oct 00:04 backup-omv-2023-10-18_00-00-01.grub

    -rw-r--r-- 1 root user 4851331251 18 Oct 00:04 backup-omv-2023-10-18_00-00-01.fsa

    -rw-r--r-- 1 root user 208 18 Oct 00:04 backup-omv-2023-10-18_00-00-01.fdisk

    -rw-r--r-- 1 root user 998 18 Oct 00:04 backup-omv-2023-10-18_00-00-01.blkid


    Better would be

    backup-omv-fsarch-2023-10-18_00-00-01*

    or backup-omv-borg-2023-10-18_00-00-01*

    and so on, this would make a selection much easier.

    don't it?

    edit: Title changed

  • Wh1sper

    Changed the title of the thread from “omv-backup” to “omv-backup improvement”.
    • Official Post

    All backup methods create the exact same .packages, .grub, .grubparts, .fdisk, and .blkid files. So, there is no reason to mark what backup method was used for those files.


    The other directory/files are already marked. fsarchiver is the only backup method that creates a .fsa file. borg creates a borgbackup subdirectory. dd creates a .dd.gz file. ddfull creates .ddfull.gz file. rsync will be obvious since it is a copy of the directory and file structure of the OS disk.

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Thanks for the clarification.

    My thought was that I can backup from it to a USB disk and then have the bundle of files created with the same tool.

    I have since looked at the backup script and it is clearer to me how it works.

  • ryecoaaron

    Added the Label resolved
    • Official Post

    Are you changing the backup method from time to time?

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    will the fsarchiver method test and choose it, because it is amazingly :thumbup: fast and encrypted

    borg is fast and encrypted as well but also adds block deduplication to potentially save even more space. It will really save a lot of space when you have more than one backup. The restore isn't quite as easy. ddfull is the easiest to restore though.

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I know borgbackup and using it for my server.

    Just discovered fsarchiver and want to give it a try.

    And yes a fulldd might be also valid once a week should be enough

    so I'll see how it works

    Thank you for inspiration

  • One last thing.

    I have the NAS with a used

    HP Proliant Microserver Gen8 server.

    This has the peculiarity only from a USB slot can be booted.

    So the system disk is sdd1 and the USB stick is sdf1.

    There is the target of grup-install

    the fsarchiver will probably not recognize this and after a restore of sdd1 a subsequent grub-install will probably be necessary, I guess.

    It would be perfect if an image would be created also from sdf1, it is also very small.

    But I will have to tinker with that or write a readme for it.

    • Official Post

    the fsarchiver will probably not recognize this and after a restore of sdd1 a subsequent grub-install will probably be necessary, I guess.

    It would be perfect if an image would be created also from sdf1, it is also very small.

    But I will have to tinker with that or write a readme for it.

    fsarchiver doesn't backup the boot sector. That is where the grub backup that the plugin is doing. But it is difficult to detect the correct grub setup especially if it exists on more than one drive. The good news is that you don't necessarily have to backup the grub config. If you were restoring a system to new disk, you would restore your fsarchive and then boot a Debian netinst disk to the grub repair part to re-setup grub.

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

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