1 |
Thanks for the input, Anthony and Jonathan. I decided to go ahead with |
2 |
rdiff-backup, as Jonathan suggested. |
3 |
|
4 |
My first thought, was that I don't really care about previous |
5 |
increments. But, after reading the man-page for awhile, I decided that I |
6 |
wasn't really giving anything up by using rdiff-backup over rsync, so |
7 |
why not? |
8 |
|
9 |
I also followed the excludes listed in Anthony's script... thanks for |
10 |
that. One thing that wasn't in there however -- and the main reason for |
11 |
this post -- was /usr/portage. |
12 |
|
13 |
I'm in the process of doing the initial backup, and I started looking |
14 |
ahead... doing du on some of the remaining directories. I was bummed to |
15 |
discover that /usr/portage uses 1.5 gigs! (In fact, the backup's been |
16 |
going for about six hours now, and I think I might be about halfway!!) |
17 |
|
18 |
So, the question is, is there any point to including /usr/portage in the |
19 |
backup? I mean, if my server's drive crashed and I restored the backup |
20 |
onto a new drive, the first emerge sync would restore everything under |
21 |
/usr/portage, right? |
22 |
|
23 |
Then again, I'm stuck putting it in the backup now (it's mired in |
24 |
distfiles right now)... maybe I should just leave it... might make a |
25 |
full restore easier. Still, it would be useful to know, if my backup |
26 |
space started getting full, could I skip everything under /usr/portage? |
27 |
Is it *only* the portage tree under there? |
28 |
|
29 |
Thanks, |
30 |
|
31 |
Ben |
32 |
|
33 |
PS: I excluded /dev, /mnt, /proc, /sys, /tmp, /var/tmp, /var/cache/edb, |
34 |
and /var/db. |