1 |
>> 2. Some of the files I back up only allow root to read. I can run |
2 |
>> rsync as root on each system, but I don't allow root logins. This |
3 |
>> means in order to rsync the second "sync" system with the first "sync" |
4 |
>> system, I must run the rsync command from the first "sync" system. |
5 |
>> This means I have to run rsyncd on the second "sync" system in |
6 |
>> addition to the first "sync" system. I'd rather only run one instance |
7 |
>> of rsyncd. Can anyone think of another option? |
8 |
> |
9 |
> Allow root logins only with a key, set up a specific user on the backup |
10 |
> server to run the backup tasks and add that users key to the |
11 |
> authorized_users file on the machine to be backed up. |
12 |
> |
13 |
>> 3. The rsync process always completes with "rsync error: some |
14 |
>> files/attrs were not transferred". How can I get more information |
15 |
>> about which files this pertains to? |
16 |
> |
17 |
> Run rsync with the verbose option and direct stdout and stderr to files. |
18 |
> |
19 |
>> 5. If I end up with filesystem corruption on the SRC system, will that |
20 |
>> corruption transfer over to the DST system during an rsync, or will |
21 |
>> the transfer just fail? |
22 |
> |
23 |
> If data is corrupted, that will be backed up. If the filesystem |
24 |
> corruption causes read errors, rsync will bail out. |
25 |
> |
26 |
>> 6. Can I run rsyncd on a system facing the internet without fear? |
27 |
> |
28 |
> Yes, as long as the rsync ports are closed in your router. |
29 |
> |
30 |
> Instead of all this, I'd recommend BackupPC. It handles all of your |
31 |
> issues and more and is efficient at backing up multiple machines. You |
32 |
> could run one BackupPC server and then rsync its store to the backup |
33 |
> backup server. The latest version in portage is old, get the 3.x ebuild |
34 |
> from bgo. |
35 |
|
36 |
BackupPC does look pretty good. Would anyone recommend I *don't* can |
37 |
this whole thing and set up BackupPC instead? |
38 |
|
39 |
- Grant |