[Opensim-users] Working with the new ROBUST Changes

[Master_Mirage]

Karen Palen wrote:
> 
> The MySql master/slave is NOT designed as a backup and you could well end
> up
> with serious problems (AKA SCREWED!)
> 
> MySql has a very rich backup facility because backup/restore is a really
> hard problem and you only get to find out what is missing when it is too
> late.
> 
> DO NOT skimp on backups! Ask me how i know ... :-( :-(
> 
> Karen
> 
> On Fri, Mar 5, 2010 at 7:46 AM, Master_Mirage <mirage123 at verizon.net>
> wrote:
> 
>>
>> As far as the Mysql stuff, i allready use master/slave mysql replication
>> so
>> that when things like this comeup i have a seperate mysql instance to
>> test
>> with. The replicator is an exact clone of all the production grids data
>> and
>> still isolated at the same time. IAR/OAR wount be nessary in my case as
>> it
>> would be using the same data anyway and as a clone theres no big deal if
>> it
>> all goes wrong in testing.
>> I brushed on the subject in other posts and this is yet another reasion
>> why
>> someome might consider master/slave replication.
>>
> 
> _______________________________________________
> Opensim-users mailing list
> Opensim-users at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-users
> 
> 
Well Mysql devs dont agree but thats passed the point anyway. I know its not
for the timid and most wount need it. Its just im dealing with db's (sp
assests) in excess of 23gigs (blobs). I spent alot of time understanding it
and ask there team alot of questions. But thats passed the point of this
thread and i have had no problems in 6mos with swapping clones (checksums
are exact). 
For most ppl you are correct and is the best way to be shure.

-- 
View this message in context: http://n2.nabble.com/Working-with-the-new-ROBUST-Changes-tp4678667p4686622.html
Sent from the opensim-users mailing list archive at Nabble.com.