disk clone plugin

1st Official Post

    Hello!

    Why, after successfully cloning a disk and clicking the close button, does the system write: Do I want to discard the changes? However, there is no window for saving changes.

    Thanks for the help!

    • Official Post
    Quote from solio4wd

    Why, after successfully cloning a disk and clicking the close button, does the system write: Do I want to discard the changes? However, there is no window for saving changes.

    Because you changed settings on the form and then the plugin is navigating away from the form which will lose those changes. I will look at it but it can safely be ignored.

    omv 7.7.7-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.2 | compose 7.5.1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.1


    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 1

    I can't find any documentation for the disk cloning plugin. I ask this question because everywhere they write that it is not good to clone with the dd command from a working system disk. They write that the databases may be damaged and so on. From my point of view, the plugin for cloning the entire system disk is very necessary, since it solves the problem of a system backup. FSarchiver is complex. All other backup methods save only shared folders. Why make backups of shared folders if it’s easier to place all shared folders on RAID (mdadm or snapraid). Maybe you should stop all containers with a command, and then use the system disk cloning plugin? PLEASE explain how to work with this plugin correctly.

    • Official Post
    Quote from solio4wd

    I can't find any documentation for the disk cloning plugin

    It literally just clones one disk to another with dd. That's it.

    Quote from solio4wd

    I ask this question because everywhere they write that it is not good to clone with the dd command from a working system disk.

    While it can clone the system disk, that is not its purpose. It is not a good idea to clone the system to another disk because then you have two disks with the same filesystem uuid.


    Quote from solio4wd

    They write that the databases may be damaged and so on

    It can happen if you have a database that is very actively written to. But typically it is not that big of a risk. It is better than having no backup.

    Quote from solio4wd

    From my point of view, the plugin for cloning the entire system disk is very necessary, since it solves the problem of a system backup.

    This is exactly what the openmediavault-backup plugin is written for.

    Quote from solio4wd

    All other backup methods save only shared folders

    I don't know what you mean by that.

    Quote from solio4wd

    Why make backups of shared folders if it’s easier to place all shared folders on RAID (mdadm or snapraid).

    Raid is not backup.

    Quote from solio4wd

    Maybe you should stop all containers with a command, and then use the system disk cloning plugin?

    The compose plugin does stop the containers when running its backup.

    Quote from solio4wd

    PLEASE explain how to work with this plugin correctly.

    I think you are mixing up multiple plugins. The diskclone plugin doesn't deal with sharedfolders at all. And since the diskclone is manually run, you can manually stop containers before using it.

    omv 7.7.7-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.2 | compose 7.5.1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.1


    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!

    Thank you very much for the specific answers, literally point by point. BUT, I'm trying to use the dd plugin to clone the entire system disk to another identical disk. If the main disk breaks, then simply change the boot disk in the BIOS and the device works again. Sorry, but I'm not an expert on this topic. Alternatively, can install OMV on raid 1. But not every hardware has two NVME slots. Otherwise, you need to reinstall openmediavault. How to remember all settings? Should I backup /etc/openmediavault/config.xml? What if docker containers are installed using Yacht? However, the compose plugin backup does not work.

    Quote from solio4wd

    BUT, I'm trying to use the dd plugin to clone the entire system disk to another identical disk. If the main disk breaks, then simply change the boot disk in the BIOS and the device works again.

    Bad idea. Two "live" discs in a system with identical uuid's on them is a recepie for disaster. Debian/OMV accesses the filesystems based on uuid. with two identical live discs in the system, it does not know which drive it actually accessing. and the drives can actually get out of sync. The best approach to what you are trying to do is to not have your backup disc live. Use an external dock or enclosure that you can put the drive in to make the clone and then disconnect it. The key point being that the backup drive is not live all the time.


    If the backup drive is usb connected, you can set the bios to boot from usb first if you wish. If the system goes down, plug in the usb disc to boot from it, then clone it back to the internal, shut down, disconnect and reboot again from the internal

  • solio4wd

    Added the Label resolved

    Hello,

    I need to replace my data hard drive with another of the same brand and capacity. How can I clone my Openmediavault NAS disk identically in the best and safest way? I specify that the system is on another disk.


    Thanks for your help, I'm a beginner and don't know linux very well.

    I believe there's one important aspect/thing that should be mentioned somewhere in the official docs or FAQ about the disk clone plugin: after attaching your destination/target disk/SD (i.e. typically via USB) - if partitioned - go to storage, disk list, select it and wipe it. If not really empty, it won't show (become electable) in the clone destination. I just figured this out moments ago.

    • Official Post
    Quote from dacbarbos

    I believe there's one important aspect/thing that should be mentioned somewhere in the official docs or FAQ about the disk clone plugin: after attaching your destination/target disk/SD (i.e. typically via USB) - if partitioned - go to storage, disk list, select it and wipe it. If not really empty, it won't show (become electable) in the clone destination. I just figured this out moments ago.

    This affects many things in OMV - raid creation, filesystem creation, zfs pool creation, etc. So, it is general OMV thing not just this plugin. This is done to protect you from overwriting a disk with data on it.

    omv 7.7.7-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.2 | compose 7.5.1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.1


    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!

Register Yourself Login