This seems to be a file based backup/restore solution (just reading the specs, have never used this myself). FOG doesn’t do file based operations but rather backups and restores full disks and partitions. So FOG is a very different thing than UrBackup from my point of view.
I’ve not done any more work on this. The best solution is still to have permanent tunnels from site to site via a routing appliance like a Cisco router or checkpoint router or PFSense router or some other router solution.
@sabotage Put a small server at each site. The hardware can be your choosing. You could use small and low-end servers if you have the money, or you could use old desktops for it. Up to you. Then setup your main FOG Server at HQ, and install all the site’s boxes as fog storage nodes. The storage-node installation process allows you to attach it to a main fog server. Then setup the location plugin and configure all your locations. We have documentation for this in our wiki. But…
For now - you really should just setup a test FOG Server at your HQ and just try things out. Generally, newbies of FOG have lots of questions about basic stuff.
Also be aware you can do your testing with 2 systems (1 fog server, and 1 system to load virtual box on). Then with virtual box you can create as many target systems as needed. Some people develop their golden image in a virtual environment to take advantage of snapshots (moment in time backups) while they perfect their golden image. Its easy to rewind your configuration to a snapshot point then reinstalling from DVD. (for example if you forget to make a modification before you sysprep the image).
At least in older Dell firmware (unsure about newer ones), turning on UEFI would remove the PXE-on-wake option
Ah OK. thats a firmware option inside the firmware. Interesting…
I know at least in bios mode Dells had an option called PXE boot on next boot cycle. If I remember correctly with Dell’s CCTK you can tell the system boot pxe on the next system boot. That is a one shot function. You could deploy this instruction using CCTK and a FOG snapin.
just wondering if it is always something that breaks locally or if things can be affected by developers or fog employees.
We aren’t employees, FOG is supported entirely by a community of volunteers that help out at their own discretion, of their own accord. There’s no money involved besides donations - which are never expected but always appreciated. You can help out too, just by answering questions you can answer or writing tutorials or documentation, videos, etc. You’ll find that you will learn a ton just by reading the stuff that’s posted here.
As for if things are affected or not by the devs - if you re-run the fog installer, it would get the latest kernel and init in order to support the latest hardware - but no web-core changes or DB changes are made unless you actually go get the latest version of FOG. As for your OS, when you re-run the installer it makes sure it has the latest version of the packages it needs, everything else is left unchanged. Ubuntu is notorious for resetting customized configuration files during updates, which in turn cause problems - this is of course compounded because Ubuntu by default automatically updates and most people aren’t knowledgeable enough about Linux to rip out that functionality.
We do have a self-developed solution for automatically backing up and restoring
Now, what I´d need is a way to somehow “marry” the management features of FOG with these existing tools if possible.
Sure this can be done. It’s probably not too much of a quest but you’re on your own with this as we can’t and don’t want to provide special solution for company XYZ. So feel free to use whichever part of FOG you like and integrate with what you have. FOG is licensed under GPLv3 - as long as it’s
“In purely private (or internal) use—with no sales and no distribution—the software code may be modified and parts reused without requiring the source code to be released.” (quoted from wikipedia)
@FredG Sure we could go with a list of lables but what bugs me is that lables are just kind of like a sticky note. Very much volatile and therefor I don’t think it’s worth the effort to add this to FOG. I would like to come up with a more reliable / robust way of actually detecting if a partition is system or recovery or …