I am re-evaluating my backups strategies and taking an insight of NS’s procedures. For that I’ve been searching the forum and Docs, and find some details a bit fuzzy.
The scenario I will most likely be in is this: Having recent config backups of a server and wanting to restore them in a different one (either because the original is un-reparable or because I take the oportunity for a version upgrade).
With that in mind, I have these questions based on the referenced Docs:
Config backup contents.
Does the “configuration backup” include every module’s settings and it’s non-user data?
I mean the “little things”, like this:
- for OpenVPN the server settings and users access,
- for Sogo the preferences set by the users while excluding the mailboxes contents (we use it only as a shared calendar)
- the ftp accounts…
I am under the impression that restoring to a fresh system that does not have the same modules already installed can become a bit troublesome… Does the backup generate a list of modules that I could use to “prepare” a new server for a smotth restoration? What is expected to happen if a module is not available in a newer NS version?
About the product upgrade procedure.
Each file under /etc/e-smith/templates-custom/ must be manually checked for compatibility with version 7. 
Do not reboot the machine before executing the restore-data procedure. 
In this context, I assume that “manually check” basically means “be ready to having to edit the config files in unpredictable ways as the situation requires it”, am I right?
If no “data” is being restored that warning can be ignored, right?