This is somewhat academic I think, but it's an idea a colleague and I dreamt up the other day.
We're currently migrating from 11.2.1 to 11.5 on a new server (moving 32bit to 64bit Progress, and also windows versions) and our migration is planned for this weekend. It's going to take a while due to the length of time it takes to do backups and restores of the DB to reseed replication on new machines etc.
So how about this for a strategy:
That should take about 30 minutes in theory, meaning we could migrate overnight! Would this work?
> Apply the AI files from production to the new server as they are archived (this will replicate will it not?)
Progress versions should be the same on source and target. Successful replication is not guaranteed if the versions are different (including the bitness of Progress). Can you migrate to 32-bit Progress 11.2.1 on new server changing Progress version only at last moment?
Source and target will both be the same version - I'm talking about taking the AI files from current production and applying them to new production meaning that on migration day all we need to do is to change some settings on the new server.
So I guess the question is, can I take the AI files from 11.2.1 32 bit and apply them to 11.5 64 bit?
Ø So I guess the question is, can I take the AI files from 11.2.1 32 bit and apply them to 11.5 64 bit?
Source and target will both be the same version - I'm talking about taking the AI files from current production and applying them to new production meaning that on migration day all we need to do is to change some settings on the new server.
So I guess the question is, can I take the AI files from 11.2.1 32 bit and apply them to 11.5 64 bit?
Flag this post as spam/abuse.
I'll give it a whirl then. If it fails then nothing is lost! If it works then I've just bought my weekend back ;)
You can always install both versions and use 11.2.1 for the AI apply and then switch to 11.5. I would test it.
I have used AI applies between minor version differences in the past without issues... but never for production roll overs. I only used it for test/qa instances when we were planning upgrades.
I'll give it a whirl then. If it fails then nothing is lost! If it works then I've just bought my weekend back ;)
Flag this post as spam/abuse.
The SAN is part of the new infrastructure so isn't in current production. The current production box is all direct attached storage.
The new server and DR will be completely new. So I'd set up the new system to replicate to the new DR by applying a recent backup of production. That would then replicate to the new DR box. Then I'd take the AI files from current production to apply to new production, meaning that new production would basically be up to date with current live. So when we turn off current live we already have the up to date database ready to do with replication running meaning we don't have to take backups and restore them before we can migrate.
The SAN is part of the new infrastructure so isn't in current production. The current production box is all direct attached storage.
The new server and DR will be completely new. So I'd set up the new system to replicate to the new DR by applying a recent backup of production. That would then replicate to the new DR box. Then I'd take the AI files from current production to apply to new production, meaning that new production would basically be up to date with current live. So when we turn off current live we already have the up to date database ready to do with replication running meaning we don't have to take backups and restore them before we can migrate.
Flag this post as spam/abuse.
Yes that sounds like you've understood me.
Reply by James PalmerYes that sounds like you've understood me.
Stop receiving emails on this subject.Flag this post as spam/abuse.
-- Tom Bascom 603 396 4886 tom@greenfieldtech.com[/collapse]
Just make the new box a secondary replication target with the existing version of OE. Managing two versions on the new box will be much simpler and quicker than manually doing anything.
Oooh yes Tom there's a thought! :D