Investigate issues related to permissions for backup system

In the process of designing a backup system for the persistent volume we should take into account that all files are not owned by the “amnesia” user. This might lead to a security vs UX trade-offs:

• Do we want the backup tool to run as “root” or as “amnesia”?
• Does this have impact on the UX?
• Does this prevent us from using certain tools that have a good integration in the desktop?
• Is it reasonable not to back up files owned as “root”? For example, loosing the data of the APT features might be considered as ok but maybe not others. Is it ok to loose the NM data? Current folders owned by root in persistence:
  • apt
  • cups-configuration
  • nm-system-connections
• Is it reasonable to grant at least read permissions to “amnesia” on some files owned by “root”? How would restoring these files work then?

Related issues

• Related to #9888 (closed)
• Blocks #9889 (closed)

Original created by @sajolida on 10145 (Redmine)