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

Backup & restore: incl. net topology, qrexec policies, guid.conf #1635

Open
rootkovska opened this Issue Jan 15, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@rootkovska
Member

rootkovska commented Jan 15, 2016

No description provided.

@rootkovska rootkovska changed the title from Backup & restore: incl. net topology, qrexec policies to Backup & restore: incl. net topology, qrexec policies, guid.conf Jan 15, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 15, 2016

Member

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

Member

marmarek commented Jan 15, 2016

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

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 16, 2016

Member

Might be nice also to include:

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

andrewdavidwong commented Jan 16, 2016

Might be nice also to include:

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

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 16, 2016

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.

Member

marmarek commented Jan 16, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 16, 2016

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.

Member

andrewdavidwong commented Jan 16, 2016

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

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 16, 2016

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).

Member

andrewdavidwong commented Jan 16, 2016

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment