[google-cloud-sql-discuss] Reduce migration downtime

Hello group!

I've been doing some research and seems it's absolutely impossible to migrate to 2nd generation without a dump, nor to setup 2nd generation MySQLs as slave of external masters or 1st Gen master...

Seems like quite a high barrier for migration;  Is there some hack/workaround/undocumented voodoo spell we can cast to avoid the dump and reload? Without being able to setup replication that means massive downtimes, and in all honesty: is pretty surprising to find a hopefully-more-advanced 2nd generation product which does not provide any low-downtime migration path (even when it could imply more machines or more complexity... *some* way would be great).

I hope am missing something and that in fact setting up 2nd generation as a slave of 1st generation would be possible?

Thanks in advance,

Markus

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/96e586c9-f5c3-46d9-8e9e-33d1e69241e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.