There is no automated way to do it that I've found but I have done it manually a few times and it seems to work well enough for most customers.
Use the VM Pro client to export the database MDB file to your desktop
Copy the wav files from the Greetings, Names, and WAVs folders
Once you get the App Server's VM application running use the VM Pro Client to import the MDB database file, this will restore all of your modules.
Use a Linux command line to change the write permissions of the Greetings, Names, and WAVs folders because they are write protected by default
Use WinScP to copy the wav files you saved over to the appropriate folders on the App Server.
Each user will have to access their mailbox settings using *17 then tell the mailbox to use the greeting that was copied from the old server. For some reason this does not happen automatically
Quick and Dirty Migration from Windows VM Pro to Linux VM Pro
1. Use VM Pro client to back up the database (.mdb file)
2. Go to Program Files (x86) – Avaya – IP Office – Voicemail Pro – VM and copy the audio files in the Greetings, WAVS and Names folders to your PC into folders of the same name to keep things straight.
3. If you want to save everyone’s stored messages then copy the contents of the Accounts folder into an Accounts folder on your PC.
4. Access the Linux command line on the App Server to change the write permissions of the Greetings, WAVS, Accounts and Names folders - /opt/vmpro vmpro]# chmod 777 for each of the 4 folders
5. Use WINScP to copy the .wav files that were copied in Step 2 into the appropriate folders on the App Server (Accounts folder optional). These folders are write protected so Step 4 is necessary to allow Step 5 to work.
6. Use the VM Pro Client to restore the .mdb file to the App Server
7. Give the App Server the same IP address as the Windows server or adjust the VM Pro address in Manager accordingly
8. VM to Email settings will still have to be manually configured on the App Server, and if you have a more advanced VM Pro with Group Announcements, campaigns etc., there will be more work to do than what is documented above.
Quick and Dirty Migration from Pre 11.1 UC Module and App Server to Post 11.1
Instead of upgrading UCM or App Server to 11.0.4.4 prior to upgrading to 11.1 save time and frustration by upgrading the UCM or App Server directly to 11.1. This will wipe everything on the older version and provide a new platform to restore your settings to.
1. Use VM Pro Client to back up the database (.mdb file)
2. Create folders named Greetings, Wavs and Names on your PC to copy .wav files into.
3. If you want to save everyone’s stored messages then copy the contents of the Accounts folder to an Accounts folder on your PC.
4. Use WINScP to connect to the UCM or App Server and navigate to /opt/vmpro
5. Copy the .wav files from the Greetings, Names, Wavs folders to the same named folders on your PC (Accounts folder optional)
6. Upgrade the UCM or App Server to 11.1
7. If upgrading an App Server perform a standard start-up and ignition of the VM application
8. Access the Linux command line on the UCM or App Server to change the write permissions of the Greetings, Wavs, Accounts and Names folders. From the Command:
Command: login
login: Administrator
Password: (Administrator password)
[Administrator@xxxVoicemail ~]$ /opt/Avaya/clish
Application Server
WARNING: Authorised Access Only
Welcome Administrator it is (time and date)
Admin
Please enter password: Administrator
Admin> root
Password: (root password)
[root@xxxVoicemail ~]# cd /opt
[root@xxxVoicemail opt]# cd vmpro
[root@xxxVoicemail vmpro]# chmod 777 Names
[root@xxxVoicemail vmpro]# chmod 777 Greetings
[root@xxxVoicemail vmpro]# chmod 777 Wavs
[root@xxxVoicemail vmpro]# chmod 777 Accounts (optional)
exit 4 times to get back to Command:
9. Use WINScp to copy the .wav files that were copied in Step 5 into the appropriate folders on the UCM or App Server. Accounts folder optional
10. Use the VM Pro Client to restore the .mdb file to the UCM or App Server
11. VM to Email settings will still have to be manually configured if required. If you have a more advanced VM Pro with Group Announcements, campaigns etc., there will be more work to do than what is documented above
