Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include all relevant user-created and user-customizable dom0 files in backups #1635

Open
2 of 5 tasks
rootkovska opened this issue Jan 15, 2016 · 7 comments
Open
2 of 5 tasks
Labels
C: core P: major Priority: major. Between "default" and "critical" in severity. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@rootkovska
Copy link
Member

rootkovska commented Jan 15, 2016

Examples:

@rootkovska rootkovska added T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. C: core P: major Priority: major. Between "default" and "critical" in severity. labels Jan 15, 2016
@rootkovska rootkovska changed the title Backup & restore: incl. net topology, qrexec policies Backup & restore: incl. net topology, qrexec policies, guid.conf Jan 15, 2016
@marmarek
Copy link
Member

Net topology is already included (if not, please give concrete example). Others - yes, should be.

@andrewdavidwong
Copy link
Member

Might be nice also to include:

  • /etc/default/grub
  • /etc/crontab
  • /etc/crypttab
  • /etc/fstab

@marmarek
Copy link
Member

@axon-qubes I'm not sure about those files - those are highly specific to particular installation, if you restore the backup on fresh installation, replacing those files most likely will break the system (at least because of different UUIDs)
Maybe /etc/crontab worth including.

@andrewdavidwong
Copy link
Member

Right, I was mainly thinking to include them in the backup but not automatically restore. But you make a good point. Perhaps it's better to leave it up to users to cp them to dom0's home before backing up.

@andrewdavidwong
Copy link
Member

Maybe /etc/crontab worth including.

Actually, I just checked, and my /etc/crontab has no entries, even though I have entries which show up when I do crontab -l (and they are working). So, backing up /etc/crontab would not be very useful (at least in my case).

@marmarek marmarek added this to the Release 4.0 milestone Jun 21, 2016
@andrewdavidwong andrewdavidwong added T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. and removed T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Jan 30, 2020
@marmot1791
Copy link

Since this is marked as a duplicate of the feature request I raised, I'd like to propose that backup of dom0 should include:

  • /etc/qubes
  • /etc/qubes-rpc

and that these files should be restored to ~/restore/etc/qubes and ~/restore/etc/qubes-rpc respectively. Later maybe other files from dom0 could be included by default or a preference setting to do so could be implemented.

I would also appreciate others' input as to what documentation should accompany this. In particular, do we expect that a user can copy ~/restore/etc/qubes and ~/restore/etc/qubes-rpc into a new install's /etc/qubes and /etc/qubes-rpc without issues? Is that true only for the same release or also across point releases (e.g. R4.0 -> R4.1).

I would like to implement this and provide some pull requests, and it seems like consensus on the solution will make them more likely to be accepted.

@andrewdavidwong
Copy link
Member

Generalizing this issue to reflect developments in Qubes OS since it was first opened.

@andrewdavidwong andrewdavidwong changed the title Backup & restore: incl. net topology, qrexec policies, guid.conf Include all user-customizable dom0 files in backups Aug 7, 2022
@andrewdavidwong andrewdavidwong changed the title Include all user-customizable dom0 files in backups Include all relevant user-created and user-customizable dom0 files in backups Aug 7, 2022
@andrewdavidwong andrewdavidwong removed this from the Release 4.2 milestone Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: core P: major Priority: major. Between "default" and "critical" in severity. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Development

No branches or pull requests

4 participants