1 |
Am 29.04.2010 02:38, schrieb Iain Buchanan: |
2 |
> Hi & thanks, |
3 |
> |
4 |
> On Wed, 2010-04-28 at 17:31 +0200, Florian Philipp wrote: |
5 |
[...] |
6 |
> |
7 |
>> If you can live with just one big partition as a backup (probably with |
8 |
>> separate /boot), you should replace fstab and grub.conf on the backup |
9 |
>> medium and blacklist them from the files which you want to back up. |
10 |
> |
11 |
> why wouldn't I backup fstab and grub.conf as well? If my internal disk |
12 |
> dies, I assume I'll swap them over, meaning grub and fstab will have to |
13 |
> be the same. |
14 |
|
15 |
I think you misunderstood me or I didn't explain it correctly. I try it |
16 |
again: |
17 |
|
18 |
You probably have a lot of partitions on your internal disk; one for /, |
19 |
/usr and /home, for example. My reasoning was that it is probably easier |
20 |
to have just one big partition on your backup medium instead of many |
21 |
small ones. If you would then swap your backup medium in, with exactly |
22 |
the same fstab as in your original installation, your system would try |
23 |
to mount partitions which are simply not there. Therefore you need a |
24 |
different fstab and most likely also another grub.conf. |
25 |
|
26 |
> |
27 |
>> Concerning the backup tool, I would use `rsync --delete` plus all |
28 |
>> relevant switches for permissions, times, acls, etc. If you use another |
29 |
>> tool, just make sure it doesn't put some metadata onto the backup medium |
30 |
>> and that it can delete files which no longer exist on the original medium. |
31 |
> |
32 |
> I was thinking of rsync, but I didn't want to do it in an hourly cron |
33 |
> fashion, I was hoping for some "gamin" alteration-triggered idea. |
34 |
> |
35 |
|
36 |
Ah, I see what you mean. I've never worked with the file alteration |
37 |
monitor (FAM) but once evaluated inotify for some administrative |
38 |
purposes. AFAIK they are not scalable good enough to work on a system |
39 |
wide basis. For example, I think the default limit of observable files |
40 |
with inotify is 8192. |
41 |
|
42 |
>> With regard to your requirement to just 'pull the cord' without |
43 |
>> umounting it: |
44 |
> |
45 |
> I wasn't thinking of pulling the chord without unmounting, I was |
46 |
> thinking of the machine dying, hence leaving the disk in a non-shutdown |
47 |
> state. |
48 |
> |
49 |
|
50 |
Okay, I thought you meant the unreliable power at those "weird |
51 |
locations" you were talking about. Such a black-out or brown-out is |
52 |
basically the same as pulling the cord. |
53 |
|
54 |
> thanks for the tips :) rsync will at least get me going quickly. |
55 |
> Yesterday I tried iotop to with dd - some slowness but otherwise quite |
56 |
> nice. |
57 |
> |
58 |
|
59 |
To reduce the performance impact, you can also use the ionice command. |
60 |
|
61 |
Hope this helps, |
62 |
Florian Philipp |