restoring an old database onto new controller.

[x-man]

It looks like I may have to swap out an old MXe (was a 20 user small business unit when they stopped the 3100) controller to a new CX. The old one is running V8 om 3300ICP and of course the new one will come with Mivoice 7 (or 6 depending on Mitel stock levels).

My question is; is there any way I can restore the old database backup on to the new controller or will it all have to be keyed in by hand. I can't upgrade the old controller to 4.0 first for various reasons. Not least the customer wont spring for the new memory just to take the controller out of use.

Alternatively is it possible to export the forme then import them or has the database structure altered too much?

[sarond]

I think you can restore from 8 to MCD 4.0
You have nothing to lose, I would install MCD4.0SP4 (or the latest 4.0) on the new controller. Try to restore the database to it and then upgrade to MCD 6/7

[x-man]

Ah, good idea. As you say worth a try.

[lundah]

Yes, you should be able to load MCD 4.0SP4 on the new controller, restore the DB, do the migration steps, then upgrade to MCD 7.

Might want to export all your forms just in case. If it's a small system, might be quicker/easier just to start fresh and import all your data from the exports (except then you'll lose all your embedded VM recordings).

[x-man]

Its only small 30 users but quite complicated due to key assignments and hunt groups. There are 30 hunt groups programmed. I think I'll go the mcd 4 route as it can play happily to itself whilst I do other more important things.

Thanks.

[lundah]

Migration takes no time at all for a standalone, the 2 upgrades will take longer than anything else (assuming you do it right).

[x-man]

Aye, done a few migrations but never tried this....

[x-man]

Hmm, slight problem due to me not providing all the information....I need to leave the old controller working whilst I do this so maybe it won't work because the new controller won';t be licenced for users till the upgrade is done....so although I could load the mcd 4 and restore the database it won't be licenced with the AMC unless I also buy new user licences? is that correct? The old system has no SWA...

But if I get SWA back on the old system will it work then as the sysID will be different. So I could get a new controller and licence it and build it as per your suggestions but what about the licence issue? Or am I just being thick?

[sarond]

mmm.. No SWA no upgrade. The licensing belongs to the ARID not the sysID. Even if you were to clear the sysID and re-license with new controller you won't be able to upgrade.

You will need to get SWA applied to the existing record, clear the sysID in the AMC and license your new controller otherwise you will be stuck your current version.

[x-man]

Yup, Mitel licencing sucks. means in effect the customer has to buy new licences .

I really need to do this with the old controller working till the new one is ready but I can't do that as far as I can see unless I buy new licences. Unless I put V8 on the new controller (which there is some debate about it working with SATA) restore database, clear sys ID relicence  upgrade to 4 and then to MCD7.(assuming SWA applied). A lot of downtime I think.

[sarond]

No need to take off air for long if you have SWA.

- Apply SWA to exisitng App Record
- Clear sysID in the AMC
- Backup V8 system
- Load MCD4.0SP4 on new controller
- License new controller with original ARID
- Restore V8 system to new CX
- Migrate DB
- Upgrade to MCD6/7

Give or take a few steps but should be all that is needed. The only additional cost should be to get SWA up to date which will most likely involve a penalty fee as well

[ccitechpatrick]

I agree with sarond. I have had to do this before and that is basically the steps I took. When you clear your sys ID in the AMC, your current state won't stop working. You can then license your new system, load you V8 backup to 4.0SP4 then upgrade to 6/7.


Sent from my iPhone using Tapatalk

[LoopyLou]

Migrate DB means convert to the new database format.