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