Can you take the configuration file for a IP500v2 release 7 and import directly into a IPO Server release 9.1. Is it also possible to take a backup of Voice mail Pro mailboxes and caller applications in IP500 v2 release 7 and restore to the Server Edition Voice mail Pro. Unable to find migration instructions from a IP500v2 to IPO server
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Migrating IP500v2 release 7 to a IPO Server edition release 9.1 1
- Thread starter shroud
- Start date
It may be possible.
If so I would strongly discourage it.
looking at the age of the system I would expect there to be a lot of unused legacy "Cruft" in the config and I suspect many areas where improvements could be made because enhancements added to the IPO features.
copying VM Pro callflows & greetings should bot be a problem but I would not bother with mailboxes (simply instruct users to make sure they have listened to all messages prior to the change over & maby keep the old VM Pro server on hand for a few weeks in-case someone forgets).
This is an ideal opportunity to clean up the system & should be grasped with both hands.
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
If so I would strongly discourage it.
looking at the age of the system I would expect there to be a lot of unused legacy "Cruft" in the config and I suspect many areas where improvements could be made because enhancements added to the IPO features.
copying VM Pro callflows & greetings should bot be a problem but I would not bother with mailboxes (simply instruct users to make sure they have listened to all messages prior to the change over & maby keep the old VM Pro server on hand for a few weeks in-case someone forgets).
This is an ideal opportunity to clean up the system & should be grasped with both hands.
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
-
1
- #3
I have to agree that this is a good time for some house cleaning.
When migrating from Windows based VM (assuming this is what you have in place now), we always backup/restore to the same release then do an in place upgrade on the new machine. I have tried backing up a Windows based deployment on a lower release and moving directly to a higher Linux release and it never works. This is a little tougher since Server Edition didn't exist in R7 for your situation.
My theory-craft here says you would have to spin up an application server on R7, restore the backup to it, upgrade it to 9.1, pull a backup from it, and import into the SE. I may be overthinking that one a bit but it sounds like the most solid way to make sure all greetings, names, etc all stayed active.
Or do as IPGuru said, and pitch is as a good time for house cleaning. (recommended)
When migrating from Windows based VM (assuming this is what you have in place now), we always backup/restore to the same release then do an in place upgrade on the new machine. I have tried backing up a Windows based deployment on a lower release and moving directly to a higher Linux release and it never works. This is a little tougher since Server Edition didn't exist in R7 for your situation.
My theory-craft here says you would have to spin up an application server on R7, restore the backup to it, upgrade it to 9.1, pull a backup from it, and import into the SE. I may be overthinking that one a bit but it sounds like the most solid way to make sure all greetings, names, etc all stayed active.
Or do as IPGuru said, and pitch is as a good time for house cleaning. (recommended)
Greybeard191
Technical User
completely agree with jhengel's theory-craft... this is the most fool proof way forward.
GB
GB
- Thread starter
- #5
- Status
Similar threads
- Question
- Locked
- Question