snacktime wrote:
Anyone have any tips for minimizing downtime when upgrading? So far we have done upgrades during scheduled downtimes. Now we are getting to the point where the time required for a standard dump/restore is just too long. What have others done when downtime is critical? The only solution we have been able to come up with is to migrate the data on a per user basis to a new database server. Each user is a merchant, and the data in the database is order data. Migrating one merchant at a time will keep the downtime per merchant limited to just the time it takes to migrate the data for that merchant, which is acceptable.
AFAIK it has always been the case that you should expect to have to dump out your databases and reload them for version upgrades.
Is anybody over at the dev team considering what an onerous burden this is? Is anyone considering doing away with it?
begin:vcard fn:Kenneth Downs n:Downs;Kenneth email;internet:ken@xxxxxxxxxx tel;work:631-689-7200 tel;fax:631-689-0527 tel;cell:631-379-0010 x-mozilla-html:FALSE version:2.1 end:vcard
