Re: [Moosefs-users] Backup strategies

[Atom P. <ap...@di...>]

I've been thinking about this for a while and I think occam's razor (the 
simplest ideas is the best) might provide some guidance.

MooseFS is fault-tolerant; so you can mitigate "hardware failure".
MooseFS provides a trash space, so you can mitigate "accidental 
deletion" events.
MooseFS provides snapshots, so you can mitigate "corruption" events.

The remaining scenario, "somebody stashes a nuclear warhead in the 
locker room", requires off-site backup. If "rack awareness" was able to 
guarantee chucks in multiple locations, then that would mitigate this 
event. Since it can't I'm going to be sending data off-site using a 
large LTO5 tape library managed by Bacula on a server that also runs 
mfsmount of the entire system.

On 04/03/2012 12:56 PM, Steve Thompson wrote:
> OK, so now you have a nice and shiny and absolutely massive MooseFS file
> system. How do you back it up?
>
> I am using Bacula and divide the MFS file system into separate areas (eg
> directories beginning with a, those beginning with b, and so on) and use
> several different chunkservers to run the backup jobs, on the theory that
> at least some of the data is local to the backup process. But this still
> leaves the vast majority of data to travel the network twice (a planned
> dedicated storage network has not yet been implemented). This results in
> pretty bad backup performance and high network load. Any clever ideas?
>
> Steve

-- 
--
Perfection is just a word I use occasionally with mustard.
--Atom Powers--
Director of IT
DigiPen Institute of Technology
+1 (425) 895-4443