1 |
On 24/06/2014 20:34, meino.cramer@×××.de wrote: |
2 |
> Alan McKinnon <alan.mckinnon@×××××.com> [14-06-24 20:00]: |
3 |
>> On 24/06/2014 19:32, meino.cramer@×××.de wrote: |
4 |
>>> Alan McKinnon <alan.mckinnon@×××××.com> [14-06-24 19:12]: |
5 |
>>>> On 24/06/2014 16:43, meino.cramer@×××.de wrote: |
6 |
>>>>> Hi, |
7 |
>>>>> |
8 |
>>>>> I bought two identical external harddrives, USB 3.0, with 1 TByte each |
9 |
>>>>> (no SSD - the good ole mechanical ones...;). |
10 |
>>>>> |
11 |
>>>>> The intended use is for backup of longer files. The drives will |
12 |
>>>>> contain the same contents. |
13 |
>>>>> |
14 |
>>>>> Currently there are still "clean metal" (no partitioning, no fs). |
15 |
>>>>> |
16 |
>>>>> Data integrity and recoverability (Uhhh...that words looks wrong...) in |
17 |
>>>>> case of an desaster is more important than speed. |
18 |
>>>>> |
19 |
>>>>> What is the recommended way of partitioning ? |
20 |
>>>>> What filesystem to choose? |
21 |
>>>>> |
22 |
>>>>> |
23 |
>>>>> Thank you very much in advance for any help! |
24 |
>>>>> Best regards, |
25 |
>>>>> mcc |
26 |
>>>>> |
27 |
>>>>> |
28 |
>>>>> PS: Running vanilla kernel 3.15.1.... |
29 |
>>>> |
30 |
>>>> You haven't given much in the way of detail, so I assume you have |
31 |
>>>> regular needs, nothing fancy, and it's all a bunch of files right? |
32 |
>>>> |
33 |
>>>> In that case, partitioning and filesystem type are largely irrelevant as |
34 |
>>>> long as you don't have corruption. With one caveat: |
35 |
>>>> |
36 |
>>>> You must always make sure the source drive is intact and ok. If not, and |
37 |
>>>> you back it up anyway, then you are already toast (you will overwrite |
38 |
>>>> your last backup with new faulty data). |
39 |
>>>> |
40 |
>>>> There's several approaches to how to do the transfer: |
41 |
>>>> |
42 |
>>>> If you have say a general fileserver with lots of files that don't |
43 |
>>>> change much or often, just rsync everything in one go. There is no |
44 |
>>>> optimization you can do that will perform much faster than rsync. |
45 |
>>>> |
46 |
>>>> If you have a big busy filesystem that changes often and lots, then use |
47 |
>>>> lvm (or anything that can make snapshots) and rsync that. |
48 |
>>>> |
49 |
>>>> If you have a huge database where everything is changing all the time, |
50 |
>>>> don't do filesystem copies, use the tools provided by the db vendor. I |
51 |
>>>> doubt this is your need as you would have said so, but it's worth |
52 |
>>>> mentioning. |
53 |
>>>> |
54 |
>>>> |
55 |
>>>> -- |
56 |
>>>> Alan McKinnon |
57 |
>>>> alan.mckinnon@×××××.com |
58 |
>>>> |
59 |
>>>> |
60 |
>>> |
61 |
>>> Hi Alan, |
62 |
>>> |
63 |
>>> thanks for your reply! :) |
64 |
>>> |
65 |
>>> Yes...your are right. I have a lot static (=not changing) data on my |
66 |
>>> harddisk...mostly things like video tutorials (blender), videos of |
67 |
>>> birds I filmed, dokuments and such... |
68 |
>>> |
69 |
>>> They are eating up the space on my systems harddisk. |
70 |
>>> |
71 |
>>> Do I decided to put them on a extern hd and an identical copy on |
72 |
>>> another identical external harddisk. |
73 |
>>> |
74 |
>>> Its mainly a task of updateing the data on the external drives with |
75 |
>>> that what is new (and static and big and falls under what I described |
76 |
>>> above) on my systems harddisk. |
77 |
>>> |
78 |
>>> I will check rsync for that! |
79 |
>> |
80 |
>> |
81 |
>> That changes things just a little bit - I thought your two drives were |
82 |
>> going to be one for live and one for backup. Do you intend to move these |
83 |
>> files off your main drive onto the identical externals, or just copy the |
84 |
>> files? |
85 |
>> |
86 |
>> I would have those two external drives using different filesystems, just |
87 |
>> in case as they are your only copy and external drives are fragile in |
88 |
>> use and in storage. Exact fs type doesn't really matter - ext4 and xfs, |
89 |
>> or ext* and btrfs, it's all good. |
90 |
>> |
91 |
>> Just do make sure you don't use rsync with --delete for this :-) |
92 |
>> |
93 |
>> |
94 |
>> |
95 |
>> -- |
96 |
>> Alan McKinnon |
97 |
>> alan.mckinnon@×××××.com |
98 |
>> |
99 |
>> |
100 |
> |
101 |
> Yes, I will delete the data from my systems drive... |
102 |
> |
103 |
> You wrote: |
104 |
> "I would have those two external drives using different filesystems" |
105 |
> |
106 |
> Different to what? Different to the fs on the system drive? Both |
107 |
> external drives use different filesystems? All three use different |
108 |
> filesystems? |
109 |
|
110 |
|
111 |
Different to each other |
112 |
|
113 |
|
114 |
> And how can this help, if the drives are fragile? (I understand |
115 |
> "fragile" as "mechanical not robust" (sorry I am no native english |
116 |
> speaker)) |
117 |
|
118 |
If one drive is say btrfs and the other say ext4 and you hit a |
119 |
corruption bug in btrfs, then you still have an uncorrupted ext4 copy |
120 |
|
121 |
> |
122 |
> I will use this "mobile disks" not really as the word "mobile" implies. They |
123 |
> will only "travel" manually between a secure place and my PC. |
124 |
> When in use, they will rest on the floor of the room (so they can not |
125 |
> be dropped) and _under_ the case of my PC (ole school big tower metal |
126 |
> case with a gap between the bottom of the case and the floor of the |
127 |
> room.) |
128 |
|
129 |
|
130 |
External drives have a much higher failure rate than internal drives. |
131 |
people don't expect them to fail or be dropped or accidentally plugged |
132 |
in in the wrong order and the wrong one to be mkfs'ed (until it does |
133 |
happen). These are real risks that you can't ignore whereas with a good |
134 |
internal drive you can often get away with it. |
135 |
|
136 |
So it only make sense to take sensible precautions that cost you very |
137 |
little, especially considering these two drives will be your only copy. |
138 |
|
139 |
|
140 |
|
141 |
-- |
142 |
Alan McKinnon |
143 |
alan.mckinnon@×××××.com |