Hello, At Sunday 11 November 2012 23:54:39 DaB. wrote: > Remember that there is a trick where you dump the user-databases with > the binlog enabled (and noting its position), leaving the database > writable. You then transfer and import the dump. Finally you make it > readonly, copy the changes from the binlog (which will be much smaller > and thus results in a shorter read-only interval) and point the dns to > the other server.
AFAIK this would need a complete LOCK of all tables during the dumping (to get a consistent state) which would be the same as switching the server read-only. Also somebody would have to write a program that read the bin-log and filter out all non-user-database-entries (enwp, commons and heartbeat in this case). The 3rd disadvantage would be that you would have to wait for the dump to complete before you can start the import, The only advantage I see it that sql-s1-user would be writable between the end of the dump and the time I awake in the morning. Sincerely, DaB. -- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Toolserver-l mailing list ([email protected]) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
