Hi !

That sounds about right. Be careful though that the guix installation
image often is widely out of date. It may therefore take quite long to
install your system, if it works at all (if will fail if you use
packages that were not defined when the installer was created, or if you
use channels).

You'd need to guix pull at some point to get a guix that can understand
your configuration.

Be careful also to how your current configuration references your
current boot disk, if you change disks, you may need to change that part
of the configuration as well. My advice would be to give a label to your
current disk, and apply the same label to the new disk, and then use
that in your operating-system declaration.

Those are minor issues that you can forget unless you absolutely need to
be up and running less than one or two hours after a full disk failure.
Otherwise you can deal with them when the day comes.

If however you can not handle any long downtime, then I strongly suggest
you address those two points and run a exercise just to make sure it
works and that your backups are actually operational.

Cheers,

Edouard.

Laurence Rochfort <laurence.rochf...@gmail.com> writes:

> Hello all,
>
> I have my whole system declaratively configured using config.scm and
> home-configuration.scm stored in my home directory. My entire home
> folder is backed up by btrbk every hour to an external location.
>
> Am I correct in thinking that to restore from a failed disk it is sufficient 
> to:
>
> - Boot guix installer
> - Partition disk
> - Provide existing config.scm to installer "guix system init"
> - Reboot into new system
> - Restore home folder from backup
> - Run "guix home reconfigure"
>
>
> Regards,
> Laurence

Reply via email to