Re: [Devil-Linux-discuss] DL and Motion

[Dominic R. <dl...@ed...>]

Yes mirroring is not backup, they are not alternatives, IMO you need 
both. Raid1 is mirroring but only protects against disk failure, like 
you I have this with DL but I wanted a *system* mirror too. I also want 
(and have) backup using rdiff-backup via sshfs.

A PC caught fire in our office earlier this week (failed power supply 
unit) - fortunately people were around to deal with it so no harm done, 
but we could have lost all our onsite data (and other stuff of course). 
I'm glad we have offsite backup...

Coffee harvesting sounds like hard work,  hope it goes well!

Dominic


On 03/08/2011 05:26, jazz wrote:
> one issue with mirroring compare to backup, is with backup you conserve
> everything once created, with mirroring if someone/something deletes all
> files, your mirror will also be empty....
> ..what is needed is a type of nas drive(network attached system)as
> writethrough system,every file you write to the fileserver will also go
> there but only readable by root so the nas drive will be invisible for
> other users
> (but yeah that's not possible/ impractical for databases)
>
> it keeps me thinking and thinking.... if there was no windows pc connected
> to the network it could all be more easy to get things implemented ..
>
> hard times...
> best regards
> Gudy
>
> during October i will be busy harvesting our coffee ,100% natural no
> pesticides used during the year, 4 trees /day /person all handwork :)
>
> On Sat, 30 Jul 2011 18:16:17 +0700, Dominic Raferd
> <dl...@ed...>  wrote:
>
>> Gudy, I can't speak for bacula, but what about backing up from your DL
>> server to another machine over ssh?
>>
>>      * rsync: this is good for simple backup and it might also be
>>        possible with DL to use some of the scripts built around rsync
>>        such as rsnapshot
>>      * rdiff-backup: sadly this is not supported directly by DL (which
>>        lacks the required librsync library), however it is possible to
>>        run it on a remote machine (on the same LAN) which first mounts
>>        the source directory (located on your DL server) using sshfs
>>        (which in turn requires fuse). I use this for our daily backup
>>        from DL to a Ubuntu-based backup server. rdiff-backup (and its
>>        derivatives, including my TimeDicer) provide a full backup history
>>        so you can recover previous file versions and deleted files, and
>>        it does so in a space-efficient manner. (It is also, like rsync,
>>        bandwidth-efficient if it can be run on both source and
>>        destination machines, but obviously that wouldn't be the case
>> here.)
>>
>> I'm assuming that it is only data that you need to backup, because one
>> of the beauties of DL is that backing up the configuration is simple
>> with save-config.
>>
>> I have recently been trying to tackle the situation of a DL server
>> failure when no tech wizard is around to fix the problem. I created a
>> similarly-configured DL server on the same LAN, with a different name
>> and IP address, and then wrote a couple of scripts one of which
>> regularly mirrors the main DL server data to this standby machine, and
>> the second of which can be used by a non-techie in emergency to switch
>> this mirror to being the primary. I would be interested to know how
>> others approach this problem?
>>
>> Dominic
>>
>> On 28/07/11 03:49, jazz wrote:
>>> I have looked at bacula a few months ago,also on the website and they
>>> all
>>> talk about tape drives
>>> Tapes are quite useless here in vietnam, as molds loves tapes(and
>>> floppies)and even cd's because of the high humidity
>>> the only solution is a hdd (but not an usb hdd as those regularly hang
>>> resulting in empty files( directory is updated with right filesize, but
>>> inside the file is only crap))
>>> the 4 sata on my mb are in use for the raid 1, (2 spare now but soon
>>> have
>>> to add 2 more hd) and ide drives are not available in shops anymore
>>> its a real dilemma to get the fileserver backed up.I have no real
>>> solution
>>> now.
>