Any system to full settings import / export on the way ?

I know this is a often asked feature, but be sure that it would have been already implemented if it would be simple. You all should also know that i hate to implement immature implementations in OMV. I do the complete project in my spare time, so i can only say that features are done when they are done.

Zitat von gderf

I've been with OMV since V2 and this feature has been frequently asked for, and most certainly been asked for well before ever I got here.

Back during the first beta releases of OMV, this "feature" was there. I could be wrong, but I don't think it even made it to the 1.0 release before it was removed.

From what I can remember of my personal experience, the configuration backup seemed to work well. It was the restoration that was a problem. It frequently wrecked things, didn't work properly, etc. and often I ended up purging/reinstalling OMV and starting over anyway which basically destroyed the intent. I tested it multiple times and it never once worked properly. I'm assuming most had a similar experience as votdev pulled it. The feature works well in some other NAS operating systems, but unfortunately hasn't translated well to OMV. That was when imaging your OS drive became the recommended backup procedure.

As I've said many times, I've never backed up my OS drive, and never will. Since I've migrated almost everything to docker, doing clean installs is easy and probably faster than the image/restore process. When I clean installed 6 on Thursday.. it was 50min from booting the installer USB, to all my services, shares, jobs, etc. being back to normal. Probably would have been quicker but for 2 things.. For some reason the Debian servers were really slow during the initial install... and I cried for at least 10min because I couldn't use drive labels anymore (j/k). Now admittedly, before docker, those clean installs were a total PITA, and generally took me at least 2-3hrs.

Zitat von gderf

My dd OMV system drive backup images (16GB USB 3.0 stick) are done on cron so how slow or fast this is doesn't matter to me, but it's under seven minutes.

A restore to bare metal using a proper USB 3.0 stick takes under fifteen minutes but I don't recall the exact figure.

I wonder if I was doing something wrong, because when I tried to image my SSD, it was taking over an hour. I never tried to restore it.

Obviously backing up/restoring doesn't matter if I'm clean installing a new version, but I can see where it is useful to some in lieu of reinstalling.. just not for me.

Zitat von gderf

What did you use to image? I use this:

Code

now=$(date +"%Y.%m.%d.%H.%M.%S")
file="omv-6-$now.img"
dd if=/dev/disk/by-id/usb-PNY_USB_3.0_FD_070B67D5A4B2D178-0:0 of=$file bs=1M status=progress

Prior to switching to a USB stick I used a 16GB 2.5 inch Samsung SSD in a USB case. That was considerably faster but all these times are so small to begin with they don't enter into the choice.

I used dd, but it's been so long if I told you what I did I'd probably be lying as it's been at least 5-6yrs ago. I wonder if by chance I didn't image my whole 64gig SSD, and that's why it was taking so long, vs just my root partition..

Zitat von mes mariusz

Image is not the same as import export. If you have possibility to export all settings you are able just to install new OMV release from scratch and import all of your settings (e.g. more than 50 users, their passwords, their privileges, groups, their privileges, names for shared folders, steup for /etc/fstab and many many more).

OS image is usable until it works or is possible to be upgraded to a new release (illusuin of beeing save)
With exported settings you could start your NAS even from the scratch if necessery (beeing save).

Of couse in every moment I could use e.g. the Clonezilla to make OMV image.

But this is not regarding the question asked in this thread

We know that, your question has been asked and answered. There's not much more to discuss about it.

Zitat von gderf

Using dd to image the rootfs partition won't copy the boot track, so the restored image will not boot.

There's a way to also use dd to grab that piece separately but I don't know what it is, never needed to do that. May also be a way to easily take that non-bootable rootfs partition restoration and clobber in a boot track.

Hmm, I don't know about any of that, but I've always liked the idea of clobbering something..

Zitat von gderf

There's a way to also use dd to grab that piece separately but I don't know what it is, never needed to do that. May also be a way to easily take that non-bootable rootfs partition restoration and clobber in a boot track.

https://github.com/OpenMediaVa…r/usr/sbin/omv-backup#L98

To fix, just dd the partition table and boot record back to the device before dd'ing the partition.