1 |
Am 16.04.2010 02:03, schrieb Neil Bothwick: |
2 |
> On Thu, 15 Apr 2010 14:30:04 -0700, Mark Knecht wrote: |
3 |
> |
4 |
>> I would like to back up a mounted RAID0 to a mounted RAID1. |
5 |
> |
6 |
> The RAID makes no difference, because rsync works at the filesystem level. |
7 |
> |
8 |
>> Would the following command be appropriate to backup /virdata on |
9 |
>> RAID0 to /backups on RAID1? |
10 |
>> |
11 |
>> rsync -avx /virdata/. /backups/. |
12 |
> |
13 |
> Yes, although the use of -v makes it harder to see any errors that may |
14 |
> occur. |
15 |
> |
16 |
|
17 |
You should also consider using --delete to cleanse your backup space |
18 |
from deleted or renamed files. |
19 |
|
20 |
>> It appears that maybe the -a option wouldn't copy the links? |
21 |
> |
22 |
> It does. |
23 |
> |
24 |
>> Also, how does rsync handle the backup if the RAID0 directory is |
25 |
>> active and changing? Will it keep working until there are no |
26 |
>> differences? Or does it read once and copy? |
27 |
> |
28 |
> It reads once, and will generally produce an error if a file has changed |
29 |
> between scanning and copying. Running rsync repeatedly until it returns |
30 |
> a 0 status may be worth considering. |
31 |
> |
32 |
> |
33 |
|
34 |
If you have an LVM on top of your RAID, you can also use LVM snapshots |
35 |
for this. Of course, if a larger write action is going on, you still get |
36 |
a half baked file. |
37 |
|
38 |
Hope this helps, |
39 |
Florian Philipp |