public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Reinstall
Date: Sun, 19 Jun 2022 18:32:55 +0100	[thread overview]
Message-ID: <9002850.rMLUfLXkoz@lenovo.localdomain> (raw)
In-Reply-To: <t8nm0q$111u$1@ciao.gmane.io>

[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]

On Sunday, 19 June 2022 18:22:34 BST Grant Edwards wrote:
> On 2022-06-19, Francisco Ares <frares@gmail.com> wrote:
> > Just for the sake of preventing a future failure, besides personal
> > files (minimum and obvious) the "world" file and the binary packages,
> > built along with the package installation, what else should I backup
> > so that I would be able to quickly restore the same full working
> > Gentoo in a new hardware without having to work from stage3 up? The
> > portage tree is one of those items, for sure. But what else?
> 
> Make a backup copy of everything under /etc.
> 
> I used to try to backup individual /etc/... files that I would need,
> but I always forgot something.
> 
> --
> Grant

Yes, besides /var/lib/portage/world and /etc/ you may also want to back up 
your /boot and kernel config, assuming the hardware (MoBo & peripherals) is the 
same (same drivers).  I wouldn't bother backing up portage, a resync will 
download it afresh.  You might want to save /distfiles if you're on a slow 
Internet link, but it has to be a copy of the current versions, otherwise the 
latest version of each package source will have to be downloaded anyway.

If you're running databases you'll also want to keep a backup of the 
respective /var/lib/*sql directory and if you're running a webserver /var/www/
* - but you would be aware of the need to keep a fresh backup of all this data 
anyway.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-06-19 17:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  9:57 [gentoo-user] Reinstall Francisco Ares
2022-05-11 11:06 ` Michael
2022-05-11 12:26 ` David Palao
2022-05-11 16:45   ` Laurence Perkins
2022-05-11 18:34     ` Neil Bothwick
2022-05-11 20:34       ` Laurence Perkins
2022-05-11 20:51       ` Wols Lists
2022-06-19 16:23         ` Francisco Ares
2022-06-19 17:22           ` [gentoo-user] Reinstall Grant Edwards
2022-06-19 17:32             ` Michael [this message]
2022-06-19 18:26               ` Francisco Ares
2022-06-20  5:01                 ` Bill Kenworthy
2022-06-19 18:08             ` Francisco Ares
2022-06-20 17:28           ` [gentoo-user] Reinstall Laurence Perkins
2022-05-11 14:32 ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9002850.rMLUfLXkoz@lenovo.localdomain \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox