Simplifying The OMV Configuration Backup and Restore Process

    • Kai wrote:

      Does the USB 3.0 stick, when mounted in a rear panel 3.0 slot, still access RAM for the purpose of being able to put OMV4 into a Wake On LAN scenario?
      depends on the sleep mode. suspend to ram would but suspend to disk would write the contents of ram to your usb stick (not good for life). The usb version doesn't make a different. If you are going to suspend your OMV system, I would first look at arm devices because you are really concerned about energy. If they can't do what you want, don't use a usb stick on an amd64 system. Use an ssd or hard drive.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I was kind of expecting that kind of a reply. Thus the downside for USB OMV OS. Currently, all is on 120GB SSD
      Thanks, Kai :thumbup:

      MY OMV OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 4.1.13-amd64 Linux Debian running virtual via VirtualBox v5.2.22. (Techno Dad Life OMV virtual installation videos as installation guide.) OMV OS on an 8GB virtual drive with 3 each 16GB data drives. Non RAID. Backup - Two sets of identical backups using GoodSync 2-way syncing onto 2 external drives (very nice EASY backup solution).


      My offering to the tech world: The great thing about being a NOOB is - You'll always be a NOOB - because every day you'll learn something that you didn't know an hour earlier, and sometimes - many times over, all in the same day. Someday you may grow old but you'll never be too old or too smart to learn something NOO. That said . . . pay it forward.
    • Kai wrote:

      Thus the downside for USB OMV OS
      If you need usb, you could use a usb-to-sata adapter. It would probably be cheaper than finding a usb stick that could handle the writes. Or you could just not sleep your NAS since it seems to cause more problems than a lot of other things.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      If you need usb, you could use a usb-to-sata adapter. It would probably be cheaper than finding a usb stick that could handle the writes. Or you could just not sleep your NAS since it seems to cause more problems than a lot of other things.
      This particular question about USB was part of my decision process on whether or not to go in depth on the backup situation per the original inquiry of this thread. I think I had probably just better learn about backup and restoring via Linux and OMV and go from there. That would allow me to have all functions available within OMV. In your last sentence - are you implying that OMV4 simply does not sleep well or function with WOL well or were you providing that sentence to the USB OMV4 OS scenario solely?
      Thanks, Kai :thumbup:

      MY OMV OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 4.1.13-amd64 Linux Debian running virtual via VirtualBox v5.2.22. (Techno Dad Life OMV virtual installation videos as installation guide.) OMV OS on an 8GB virtual drive with 3 each 16GB data drives. Non RAID. Backup - Two sets of identical backups using GoodSync 2-way syncing onto 2 external drives (very nice EASY backup solution).


      My offering to the tech world: The great thing about being a NOOB is - You'll always be a NOOB - because every day you'll learn something that you didn't know an hour earlier, and sometimes - many times over, all in the same day. Someday you may grow old but you'll never be too old or too smart to learn something NOO. That said . . . pay it forward.
    • Kai wrote:

      are you implying that OMV4 simply does not sleep well or function with WOL well or were you providing that sentence to the USB OMV4 OS scenario solely?
      I have no experience with sleeping OMV 4 since I don't use it and most of my OMV installs are VMs. But I have read many posts where systems don't sleep correctly or wake up. I would guess it is due to the bios incompatiblity with linux of most desktop boards since manufacturer generally only care about Windows and you don't put servers to sleep in the business world. So, none of this is really about OMV but more Linux in general. Sleep works very well on my Dell XPS13 laptop but it is 100% supported on Linux by Dell.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      I have no experience with sleeping OMV 4 since I don't use it and most of my OMV installs are VMs. But I have read many posts where systems don't sleep correctly or wake up. I would guess it is due to the bios incompatiblity with linux of most desktop boards since manufacturer generally only care about Windows and you don't put servers to sleep in the business world. So, none of this is really about OMV but more Linux in general. Sleep works very well on my Dell XPS13 laptop but it is 100% supported on Linux by Dell.
      Understood.
      Thanks, Kai :thumbup:

      MY OMV OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 4.1.13-amd64 Linux Debian running virtual via VirtualBox v5.2.22. (Techno Dad Life OMV virtual installation videos as installation guide.) OMV OS on an 8GB virtual drive with 3 each 16GB data drives. Non RAID. Backup - Two sets of identical backups using GoodSync 2-way syncing onto 2 external drives (very nice EASY backup solution).


      My offering to the tech world: The great thing about being a NOOB is - You'll always be a NOOB - because every day you'll learn something that you didn't know an hour earlier, and sometimes - many times over, all in the same day. Someday you may grow old but you'll never be too old or too smart to learn something NOO. That said . . . pay it forward.

      Post by flmaxey ().

      This post was deleted by the author themselves ().
    • Kai wrote:

      Does the USB 3.0 stick, when mounted in a rear panel 3.0 slot, still access RAM for the purpose of being able to put OMV4 into a Wake On LAN scenario?
      OMV will boot from a rear panel USB socket (were it won't be broken off). There's only one exception that I know of, where booting from USB had to be from a specific socket (in the back), and that particular hardware and BIOS was very old.

      WOL is more of a function of the power supply and motherboard, keeping the Ethernet interface running while the PC is shut down. This is a BIOS function - USB had nothing to do with this. (Note: In some BIOS versions, WOL must be enabled in BIOS.) If the "magic packet" is received at the Ethernet interface, the boot process is triggered much as it is with the front panel switch. Thereafter, it doesn't matter if the boot device is a CD/DVD, a USB drive (of any type) , or a hard drive.

      I'm currently waking up an OMV backup server, from my main server, twice a month. (Both are booted from a USB thumbdrive, BTW.) The backup server does it's thing and shuts down at midnight. In this case, no configuration change was required on the backup device, other than config'ing OMV on the main server to wake it up.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 4.1.17, ThinkServer TS140, 12GB ECC, 16GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.17, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk

      The post was edited 1 time, last by flmaxey: edits ().

    • flmaxey wrote:

      WOL is more of a function of the power supply and motherboard, keeping the Ethernet interface running while the PC is shut down. This is a BIOS function - USB had nothing to do with this. (Note: In some BIOS versions, WOL must be enabled in BIOS.) If the "magic packet" is received at the Ethernet interface, the boot process is triggered much as it is with the front panel switch. Thereafter, it doesn't matter if the boot device is a CD/DVD, a USB drive (of any type) , or a hard drive.
      But waking up a system with WOL requires the system to be sleeping first. The reason why I said don't use usb was if the system was suspend-to-disk which would wear out a usb stick quickly if the system slept a lot.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      But waking up a system with WOL requires the system to be sleeping first
      WOL support doesn't require the OS to be in a sleep mode. It requires BIOS and motherboard support.

      The vast majority of current systems that support WOL, and that's most of them, are in a type of "low power mode" even when they're shut down. Modern PC's are never really off, with 5 volts continually powering some components. This is what makes the front momentary contact (logic) switch work, while the NIC is powered. (It's been a long time since a front panel PC switch was an actual AC breaker.)

      My understanding of "sleep mode" and "hybernate" are low powered states where memory is preserved, as it is, while suspending the CPU and peripheral functions. "Suspend to disk", with the entire state of ram and the system written to disk, would be hard on a USB drive. But, outside of VM's, I can't see where that would be useful for a server running on physical hardware.

      Does OMV support "Suspend to disk" in the GUI? Is that what the " = Standy By" menu option does?
      _________________________________________________

      In any case, after I use the shutdown command on my backup server; the wakeonlan command and the servers Mac address can remotely start it. I'm doing this from scheduled tasks.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 4.1.17, ThinkServer TS140, 12GB ECC, 16GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.17, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk

      The post was edited 1 time, last by flmaxey: edit ().

    • flmaxey wrote:

      WOL support doesn't require the OS to be in a sleep mode. It requires BIOS and motherboard support.
      When I say sleeping, that can mean suspend to ram, suspend to disk, or powered off. They are just C states. It also requires ethernet adapter support.

      flmaxey wrote:

      Does OMV support "Suspend to disk" in the GUI? Is that what the " = Standy By" menu option does?
      I don't remember which state "Standy By" uses but the autoshutdown plugin allow you to select. It has an option to power off, hibernate (suspend to disk), suspend (suspend to ram), and suspend-hybrid (suspend to both disk and ram).
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      It also requires ethernet adapter support.
      True. (An add-on wired adapter didn't come to mind. :) ) But, if a Mobo supports WOL, the integrated NIC supports it.

      I've been doing automated shutdowns and WOL in scheduled tasks.
      I need to look at those plugins.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 4.1.17, ThinkServer TS140, 12GB ECC, 16GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.17, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk

      The post was edited 1 time, last by flmaxey ().

    • Wired ethernet is all I ever run here even for TV's, printers, etc.. Only devices wireless are cell phones and tablets.
      Thanks, Kai :thumbup:

      MY OMV OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 4.1.13-amd64 Linux Debian running virtual via VirtualBox v5.2.22. (Techno Dad Life OMV virtual installation videos as installation guide.) OMV OS on an 8GB virtual drive with 3 each 16GB data drives. Non RAID. Backup - Two sets of identical backups using GoodSync 2-way syncing onto 2 external drives (very nice EASY backup solution).


      My offering to the tech world: The great thing about being a NOOB is - You'll always be a NOOB - because every day you'll learn something that you didn't know an hour earlier, and sometimes - many times over, all in the same day. Someday you may grow old but you'll never be too old or too smart to learn something NOO. That said . . . pay it forward.
    • ryecoaaron wrote:

      But waking up a system with WOL requires the system to be sleeping first. The reason why I said don't use usb was if the system was suspend-to-disk which would wear out a usb stick quickly if the system slept a lot.
      So, as ryecoaaron and flmaxey have discussed back and forth - is the issue of wearing out a usb of concern? And, what would be the advised state for suspend . . . suspend-to-disk, -ram, -hybrid? -and- if possible please add for what reason in choice.
      Thanks, Kai :thumbup:

      MY OMV OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 4.1.13-amd64 Linux Debian running virtual via VirtualBox v5.2.22. (Techno Dad Life OMV virtual installation videos as installation guide.) OMV OS on an 8GB virtual drive with 3 each 16GB data drives. Non RAID. Backup - Two sets of identical backups using GoodSync 2-way syncing onto 2 external drives (very nice EASY backup solution).


      My offering to the tech world: The great thing about being a NOOB is - You'll always be a NOOB - because every day you'll learn something that you didn't know an hour earlier, and sometimes - many times over, all in the same day. Someday you may grow old but you'll never be too old or too smart to learn something NOO. That said . . . pay it forward.

      The post was edited 1 time, last by Kai ().

    • Kai wrote:

      So, as ryecoaaron and flmaxey have discussed back and forth - is the issue of wearing out a usb of concern? And, what would be the advised state for suspend . . . suspend-to-disk, -ram, -hybrid? -and- if possible please add for what reason in choice.
      suspend-to-disk and suspend-hybrid are definitely going to add a lot of writes to your disk. suspend-to-ram seems dangerous especially if you don't have a UPS. Personally, I wouldn't suspend the server at all. If it is still using too much power after sleeping the disks, get a more power efficient system.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      suspend-to-disk and suspend-hybrid are definitely going to add a lot of writes to your disk. suspend-to-ram seems dangerous especially if you don't have a UPS. Personally, I wouldn't suspend the server at all. If it is still using too much power after sleeping the disks, get a more power efficient system.
      Actually, not suspending at all is exactly where my line of thought has been heading. I'm running 65W APU, 2HDD, 1 SSD, no monitor, and a couple of fans; That's it. Plus, the network has nothing going on 10 hours every 24 hour period. The OMV4 OS is never asked to do anything over and above very minimal read/write. It's not as if the system is 'hard at work' every single day and night.
      Thanks, Kai :thumbup:

      MY OMV OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 4.1.13-amd64 Linux Debian running virtual via VirtualBox v5.2.22. (Techno Dad Life OMV virtual installation videos as installation guide.) OMV OS on an 8GB virtual drive with 3 each 16GB data drives. Non RAID. Backup - Two sets of identical backups using GoodSync 2-way syncing onto 2 external drives (very nice EASY backup solution).


      My offering to the tech world: The great thing about being a NOOB is - You'll always be a NOOB - because every day you'll learn something that you didn't know an hour earlier, and sometimes - many times over, all in the same day. Someday you may grow old but you'll never be too old or too smart to learn something NOO. That said . . . pay it forward.
    • Well . . . I didn't get very far.

      I am using my OMV4 virtual machine setup to learn and perform a backup and restore within OMV4. I am using this guide by tekkb. I didn't get past step 3. NO Clonezilla tab showing. So . . . where do I come up with the Clonezilla tab?

      By the way . . . I would assume there is nothing wrong/prohibitive with performing a system backup and restore within a Virtual Box OMV4 machine, correct???

      Thanks, Kai :thumbup:

      MY OMV OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 4.1.13-amd64 Linux Debian running virtual via VirtualBox v5.2.22. (Techno Dad Life OMV virtual installation videos as installation guide.) OMV OS on an 8GB virtual drive with 3 each 16GB data drives. Non RAID. Backup - Two sets of identical backups using GoodSync 2-way syncing onto 2 external drives (very nice EASY backup solution).


      My offering to the tech world: The great thing about being a NOOB is - You'll always be a NOOB - because every day you'll learn something that you didn't know an hour earlier, and sometimes - many times over, all in the same day. Someday you may grow old but you'll never be too old or too smart to learn something NOO. That said . . . pay it forward.
    • Kai wrote:

      I am using this guide by tekkb. I didn't get past step 3. NO Clonezilla tab showing. So . . . where do I come up with the Clonezilla tab?
      The guide is 3.5 years old. A lot has changed. I moved the clonezilla stuff to the kernel tab in omv-extras instead of the backup plugin itself.

      Kai wrote:

      I would assume there is nothing wrong/prohibitive with performing a system backup and restore within a Virtual Box OMV4 machine, correct???
      Nope.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      The guide is 3.5 years old. A lot has changed. I moved the clonezilla stuff to the kernel tab in omv-extras instead of the backup plugin itself.
      That said . . . is there a better option for step by step? Just trying to get the learning process moving in the right direction here.
      Thanks, Kai :thumbup:

      MY OMV OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 4.1.13-amd64 Linux Debian running virtual via VirtualBox v5.2.22. (Techno Dad Life OMV virtual installation videos as installation guide.) OMV OS on an 8GB virtual drive with 3 each 16GB data drives. Non RAID. Backup - Two sets of identical backups using GoodSync 2-way syncing onto 2 external drives (very nice EASY backup solution).


      My offering to the tech world: The great thing about being a NOOB is - You'll always be a NOOB - because every day you'll learn something that you didn't know an hour earlier, and sometimes - many times over, all in the same day. Someday you may grow old but you'll never be too old or too smart to learn something NOO. That said . . . pay it forward.
    • Kai wrote:

      That said . . . is there a better option for step by step? Just trying to get the learning process moving in the right direction here.
      The only difference is you install and set boot in the kernel tab of omv-extras instead of the clonezilla tab in the backup plugin. Some of the pics might be slightly different.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!