DB migration

C

casorohi

Member
Hi Guys
one of our client is moving their database from one datacenter to another.
The application runs 24X7 on linux and management wants minimum down time for this migration. We are using Progress V9.1d. DB size around 150GB
Please advice/list me the migration method with minimum down time.
Thanks
 
A great deal depends on your circumstances and requirements. But unless you are experienced at this sort of thing (or willing to spend a lot of time gaining experience) the biggest factor is probably bringing in an experienced consultant (see signature line).

Having said that... Bravepoint has a product "Pro Dump & Load" which requires just 2 short outages (5 or 10 minutes each, one at the start, the other at the end) which will migrate a db in the background. It may, however, take a considerable amount of elapsed time. And I believe that it requires that each table being migrated have a unique (and possibly monotonically ascending, but I may have that wrong) index.

Or, you could elect to do a highly parallel dump & load. Not having seen your system I'm just guessing but, in my experience, 150GB might take roughly 8 hours if you have decent hardware.
 
Given that the application is wanted 24x7, are you currently using some form of replication? If not, why not? No time like the present to start. Set it up so that the replicate is at the new datacenter and you should have minimal cutover time.
 
Silly me. I assumed that anyone using an ancient, obsolete and unsupported release like 9.1D would, of course, be upgrading. If it is a like to like migration then, yes, replication would solve the problem quite neatly.

With version 9 that means "log based replication" (ai files) unless you are some sort of glutton for punishment and want to try to get Fathom Replication for v9 running.

Log based replication is pretty darned easy. Especially if you already have after-imaging up and running. If you don't have AI up and running you should stop what you're doing and fix that problem now.
 
Thanks for suggestion, one more help, could you please tell me where I got the document/pdf for Fathom Replication for v9.
Thanks
 
You really don't want to waste any time on Fathom Replication for v9. All you need for this project is after-imaging. Just configure it and enable ai (which you should do anyway and which you would have to do even if you ignore my advice regarding Fathom Replication), restore a backup on your new server (which you also have to do even if you ignore my advice re: Fathom Replication), roll forward the ai files as they occur and then when you are ready to migrate, shutdown the old system, transfer the last after-image file, roll it forward and start the new system. Total outage shouldn't be more than a few minutes.

If you are not already running after-imaging you need to be. Regardless. OE Replication (also known as Fathom Replication) is built on top of and requires after-imaging to be running first. You must do this.

To have an important database that does not use after-imaging is irresponsible and fool hardy. If you don't know how to setup and manage after-imaging get some help. If you do know how to do it then a migration such as you describe is very easy.
 
You must log in or register to reply here.
Back
Top