1 |
On 24/06/2014 19:32, meino.cramer@×××.de wrote: |
2 |
> Alan McKinnon <alan.mckinnon@×××××.com> [14-06-24 19:12]: |
3 |
>> On 24/06/2014 16:43, meino.cramer@×××.de wrote: |
4 |
>>> Hi, |
5 |
>>> |
6 |
>>> I bought two identical external harddrives, USB 3.0, with 1 TByte each |
7 |
>>> (no SSD - the good ole mechanical ones...;). |
8 |
>>> |
9 |
>>> The intended use is for backup of longer files. The drives will |
10 |
>>> contain the same contents. |
11 |
>>> |
12 |
>>> Currently there are still "clean metal" (no partitioning, no fs). |
13 |
>>> |
14 |
>>> Data integrity and recoverability (Uhhh...that words looks wrong...) in |
15 |
>>> case of an desaster is more important than speed. |
16 |
>>> |
17 |
>>> What is the recommended way of partitioning ? |
18 |
>>> What filesystem to choose? |
19 |
>>> |
20 |
>>> |
21 |
>>> Thank you very much in advance for any help! |
22 |
>>> Best regards, |
23 |
>>> mcc |
24 |
>>> |
25 |
>>> |
26 |
>>> PS: Running vanilla kernel 3.15.1.... |
27 |
>> |
28 |
>> You haven't given much in the way of detail, so I assume you have |
29 |
>> regular needs, nothing fancy, and it's all a bunch of files right? |
30 |
>> |
31 |
>> In that case, partitioning and filesystem type are largely irrelevant as |
32 |
>> long as you don't have corruption. With one caveat: |
33 |
>> |
34 |
>> You must always make sure the source drive is intact and ok. If not, and |
35 |
>> you back it up anyway, then you are already toast (you will overwrite |
36 |
>> your last backup with new faulty data). |
37 |
>> |
38 |
>> There's several approaches to how to do the transfer: |
39 |
>> |
40 |
>> If you have say a general fileserver with lots of files that don't |
41 |
>> change much or often, just rsync everything in one go. There is no |
42 |
>> optimization you can do that will perform much faster than rsync. |
43 |
>> |
44 |
>> If you have a big busy filesystem that changes often and lots, then use |
45 |
>> lvm (or anything that can make snapshots) and rsync that. |
46 |
>> |
47 |
>> If you have a huge database where everything is changing all the time, |
48 |
>> don't do filesystem copies, use the tools provided by the db vendor. I |
49 |
>> doubt this is your need as you would have said so, but it's worth |
50 |
>> mentioning. |
51 |
>> |
52 |
>> |
53 |
>> -- |
54 |
>> Alan McKinnon |
55 |
>> alan.mckinnon@×××××.com |
56 |
>> |
57 |
>> |
58 |
> |
59 |
> Hi Alan, |
60 |
> |
61 |
> thanks for your reply! :) |
62 |
> |
63 |
> Yes...your are right. I have a lot static (=not changing) data on my |
64 |
> harddisk...mostly things like video tutorials (blender), videos of |
65 |
> birds I filmed, dokuments and such... |
66 |
> |
67 |
> They are eating up the space on my systems harddisk. |
68 |
> |
69 |
> Do I decided to put them on a extern hd and an identical copy on |
70 |
> another identical external harddisk. |
71 |
> |
72 |
> Its mainly a task of updateing the data on the external drives with |
73 |
> that what is new (and static and big and falls under what I described |
74 |
> above) on my systems harddisk. |
75 |
> |
76 |
> I will check rsync for that! |
77 |
|
78 |
|
79 |
That changes things just a little bit - I thought your two drives were |
80 |
going to be one for live and one for backup. Do you intend to move these |
81 |
files off your main drive onto the identical externals, or just copy the |
82 |
files? |
83 |
|
84 |
I would have those two external drives using different filesystems, just |
85 |
in case as they are your only copy and external drives are fragile in |
86 |
use and in storage. Exact fs type doesn't really matter - ext4 and xfs, |
87 |
or ext* and btrfs, it's all good. |
88 |
|
89 |
Just do make sure you don't use rsync with --delete for this :-) |
90 |
|
91 |
|
92 |
|
93 |
-- |
94 |
Alan McKinnon |
95 |
alan.mckinnon@×××××.com |