Manually Move/Restore Embedded Voicemail

[bluewhite4]

I have a customer who later this summer will be transitioning to a newer MXe, as well as replacing their ~200 digital phones with IP phones.

To try and make the transition as seamless as possible, we would like to rebuild their configuration in a lab, without using a backup of their current state.

To that end, on the day of install/cut, they would like us to restore their voicemail so that saved messages are still available to them.  They're not worried about MWI lights at all, just greetings and messages.

Since the dial plan/extension numbers will not be changing, is it possible to ftp the entire /vmail folder from the old to the new controller?

I've never really messed too much in /vmail other than when directed to by Mitel, so I'm unsure of the relationship between the folder structure and database.

I'm assuming I'd also need to do an iPVM_Stop on both systems prior to the move.


If anyone has any insight into this, I'd appreciate it.

[lundah]

Theoretically it should be possible, since the backup/restore procedure handles the entire /vmail partition separate from the call control DB, but I have no idea how you'd go about doing it. If you have a lab system, you could try copying the /vmail/temp/db/backup/vmail folder from "backup a" to "backup b" and see if you can restore the "b" backup successfully. I've never tried this but based on the file structure of everything I think it would be worth an attempt if you have the resources to experiment on.

[johnp]

There is a KB artical on backing up and restoring vmail

[bluewhite4]

There is a KB artical on backing up and restoring vmail

Really? I will have to go look for that. Thank you!

[johnp]

Yes depending on software version, the entry point may be different

[johnp]

My thought would be to change all the digital vm boxes to transfer only, then after the change resore them as extension

[bluewhite4]

My thought would be to change all the digital vm boxes to transfer only, then after the change resore them as extension

My only problem with that is that we plan to build the replacement system in our lab over days/weeks before the cut. Not only are the digital phones being replaced by IP, but all the 2000 per cabinet analogs will be replaced by ASU II's. To try and save time we want to try and make the ASU 25-pair cables "match" the 2000 ones. So we can just swap amphenol's on the blocks themselves and not have to touch all the cross-connects.

So I would imagine that the time to completion would cause the two voicemail versions to have become potentially vastly different.

[johnp]

I think I know your premise. On the date of the move, disacciate the vm boxes, make a backup of vm and restore to new system. Reeboot and associate.

[bluewhite4]

I think I know your premise. On the date of the move, disacciate the vm boxes, make a backup of vm and restore to new system. Reeboot and associate.

Exactly my hope of what to do.

[johnp]

I would think as long as you know the extensions that are changing, you should be good. Not for the faint hearted :-)

[johnp]

Make sure you do the reboot after the restore.

[bluewhite4]

Found the KB article. Actually looks simpler than I thought.

Thanks!

[ralph]

What's the KB number?

Ralph

[bluewhite4]

What's the KB number?

Ralph

05­5191­00033


Sent from my iPhone using Tapatalk