On Mon, 12 Nov 2007, Michael Tiernan wrote:
The issue I believe that I was remembering was something more along
the lines of a uniquely linux quirk where "dump" did not permit
correct restores. Hell, this could've been a 2.2 kernel issue and long
I do remember an issue with dump/restore just not working properly in the
2.2 timeframe, and I have heard that it has been long resolved, but I have
not used dump/restore since the 2.0 timeframe, so I can't personally vouch
for it. In the 2.0 days, I was very happy with it, though, even if I did
occasionally get bitten by the your-filesystem-must-be-quiesced behavior.
My take on backup in general is that it's a task that's easy to get wrong
because very few people take the time to verify their backups regularly,
and because not everybody understands the limitations caused by concurrent
access (e.g., you can't backup a running DB without software that groks
its internals). My experience has been that if you understand backup, and
you have a well thought out procedure, most tools can be made to do a
effective job.
Dave
_______________________________________________
bblisa mailing list
[email protected]
http://www.bblisa.org/mailman/listinfo/bblisa
