1 |
Nigel, |
2 |
|
3 |
I'm still very new to how backup software works, but Box Backup sounds |
4 |
very similar to rsnapshot. That's a backup program that uses rsync over |
5 |
ssh to make incremental backups of remote filesystems (or pieces |
6 |
thereof). It has the same hourly, daily, weekly, monthly backup points |
7 |
that it sounds like Box Backup has. And, it's in portage. |
8 |
|
9 |
Not that I'm trying to talk you out of Box Backup, I'd just rather use |
10 |
something in portage if it's close enough in features. It's only |
11 |
partially a matter of the simplicity of install for me... portage also |
12 |
(generally) keeps up with security holes so that I don't have to |
13 |
remember to check up on my apps outside of portage. |
14 |
|
15 |
Now -- as information that clarifies my needs and also as another |
16 |
question of strategy -- I will be backing up a single, remote, rented |
17 |
webserver with whatever package I wind up using. I don't have and can't |
18 |
afford another server to back up to (though a mirror server would be |
19 |
nice some day). So, I'm figuring on pulling my snapshots down to my |
20 |
local gentoo box. |
21 |
|
22 |
Even though we have at least a dozen live sites on our server, we're not |
23 |
using much space on it... about 5 gig total. I looked and I have about |
24 |
50 gigs available just in my /home partition. So, I'm thinking that I |
25 |
should just backup the server's whole drive. The question is, is this |
26 |
worth the trouble... if the server's hard drive crashed, would I be able |
27 |
to restore my whole setup from the backup to a new harddrive and have a |
28 |
working system again? |
29 |
|
30 |
Hmmm, now that I take another look at the rsnapshot man page, that seems |
31 |
to be one way in which Box Backup is better than rsnapshot... there's no |
32 |
mention of recovery at all. It seems it's intended to just take |
33 |
snapshots of your system and it's up to you to figure out what to do |
34 |
with the snapshot if you need it. |
35 |
|
36 |
Well, in any case... my needs are fairly simple... don't really need the |
37 |
encyption or to allow anyone other than myself to make backups. |
38 |
|
39 |
Any and all comments appreciated. |
40 |
|
41 |
Ben |
42 |
|
43 |
Nigel Marsh wrote: |
44 |
> On Friday 22 Oct 2004 15:15, Jose Gonzalez Gomez wrote: |
45 |
> |
46 |
>>Nigel Marsh wrote: |
47 |
>> |
48 |
>>>Jose, |
49 |
>>> |
50 |
>>>[...] |
51 |
>>>As to reverting to a given date. The short answer (unusual for me ;)) is |
52 |
>>>No... The longer answer is, according the developments on the mailing |
53 |
>>>list it will do soon. |
54 |
>> |
55 |
>> Well, I had that feeling. The final question: let's say that |
56 |
>>somebody deletes a bunch of files that shouldn't be deleted. You told |
57 |
>>that the backup system informs of changes every hour or so, so I assume |
58 |
>>those files will also be deleted on the backed up system, am I wrong? If |
59 |
>>this is the case, and you notice the problem a few hours later, is there |
60 |
>>any way to recover those files? That's why I was asking about recovering |
61 |
>>the state for a given date/time. |
62 |
> |
63 |
> |
64 |
> No, they will be kept on the backup server and be marked as having been |
65 |
> deleted on the client. When the allocated space is filled up on the backup |
66 |
> server then the oldest deleted files will be deleted from the server first. |
67 |
> So the time a deleted file remains on the server is down to allocated drive |
68 |
> space and is analogous to tape. When you run out of tape space, you either |
69 |
> add more storage or you start rotating backup media. |
70 |
> |
71 |
> Also old versions of files are kept so that you can jump back say 3 weeks to |
72 |
> an old version of a file. |
73 |
> |
74 |
> If you needed to know more about the internals of it then the mailing list, |
75 |
> which is a low volume with the odd flurry of activity, would be your best |
76 |
> bet. Questions are generally answered pretty quickly. |
77 |
> |
78 |
> |
79 |
>>>On the server side, you have no access to this data. You need to keep a |
80 |
>>>client key safe to rebuild a totally dead client so that it can restore |
81 |
>>>and start again where you left off. |
82 |
>>> |
83 |
>>> |
84 |
>>>Sorry, got carried away and probably went way over what was needed to |
85 |
>>>answer your question. Must be this new coffee I'm drinking. ;) |
86 |
>> |
87 |
>> Not at all. Your answer has been very informative, and will help me |
88 |
>>a lot in making my mind in my final decission about backup software. |
89 |
>>Thanks a lot for your kindly response... and tell us about that new |
90 |
>>coffee, I think it may help us on overnight system failures ;o) |
91 |
> |
92 |
> |
93 |
> I don't know, it is in a silver unnamed bag and I got 10kg cheap from a car |
94 |
> boot sale. :) |
95 |
> |
96 |
> It's very good though. |
97 |
> |
98 |
> |
99 |
>>>Nige |
100 |
>> |
101 |
>> Best regards |
102 |
>> Jose |
103 |
> |
104 |
> |
105 |
> Nige |
106 |
> |