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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Voicemail Pro Backup/Restore 5

Status
Not open for further replies.

telfire

Vendor
Dec 18, 2008
119
US
Does anyone know if an immediate backup done using VM Pro client on a R11.0.4.5 physical App Svr can be restored on a virtual R11.1.2 App Svr? Is it supported? If not, has anyone still done it and it works? Thanks in advance.

APSS-Midmarket
ACIS-Midmarket
ACSS-Midmarket
ACDS-Midmarket
 
Other than installing 11.1.2 on a system (I would wait as Avaya has been pulling service and feature packs like they never have before), there should be no issue with this. Simply do the immediate backup then put it in /opt/vmpro/Backup/Scheduled/OtherBackups. Once it's there you should be able to restore it from Platform View.

 
Does not work it does not give you an OK option once the backup file is selected.
Mike
 
You may want to try some different browsers. I have found various issues with web manager that were solved by using a different browser.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
It could be a linux permission issue. I am still working on doing a successful migration in a sand box. The production one I did was a pure failure in comparison to a Widows migration.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
when in doubt with Avaya always try the Internet Explorer

They still sell things you can only program from IE

But budbyrd is correct it could be a Linux permission.
Check the owner of the file and maybe match it whatever else you have (owner vmpro etc)

Joe
FHandw, ACSS (SME)

"Dew knot truss yore Spell Cheque
 
I am trying to migrate a R11.0.4 to a R11.1 app server. Once I select my back up it just does a site and spin. I verified that vmpro is the owner of the file, so I have ruled out the linux permission issue.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
Did it at lease give you the option for OKing the restore? I didn't even get the OK button.
Mike
 
It gave me the choice of which back up to use. I pick it. Then it just gives me a spinning circle. I pulled the short straw to try to figure out how to make this work. [banghead] I am thinking I may try to do a sync from this app server to the windows server in a fallback server situation to get a copy.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
That is what I have seen on 3 different App server installs. Avaya screwed something up on this.
Mike
 
Just done a migration from Windows to Application Server on 11.0. I too have never managed to do a backup/restore as part of the migration but this time I think I have managed to get it working.

In the IP Office Knowledgebase Link, one of the steps before doing the backup is to "suspend" the VM server:


Log in to Voicemail Pro server using Voicemail Pro client.

You can then use the "File> Voicemail Shutdown > Suspend" to display the number of voicemail sessions that are active. You can stop any new sessions or end the
sessions before to take a backup.



This seems to be the key, I used this method and for good measure stopped the VM service on the Application server before doing the import through the Web Console.

I checked all the directories, and the Accounts, Greetings, WAV files & etc. had all been brought in! The only thing not imported was the VM password and the email server SMTP settings which I updated manually.

Started the VM service, changed the VM IP on the system, and it all worked as before.




“Some humans would do anything to see if it was possible to do it.
If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH'.
The paint wouldn't even have time to dry.”

Terry Pratchet
 
I have managed to backup a windows VM Pro and migrate it to an app server R11.0. Took some doing. I couldn't get it to restore from an R11.0 to R11.1. I could see the back up but it wouldn't load. I am thinking now that I have it at R11.0 I should be able to upgrade to R11.1. I had some onsite work to do this morning so I haven't been able to get that far, but I will let you. If I have time I will type up a complete FAQ. You have to get into linux and rewrite a file... It wasn't as easy as the docs make it sound.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
I have successfully migrated a Windows R11.0 VM Pro to R11.1 App server. There may be an easier way to do this, but as of yet I haven't found it. I am currently writing a 'How To' for our other techs and will post it as an FAQ once I have followed my own instruction set and verified I got all the steps right.

If anyone has managed to get this to work with the Avaya instructions, let me know. I would be interested in how you got it to work.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
This is how I've done it a few times and it seems to have done the trick although I do realize this is not a "full" back up and restore, but it covers off the majority of what's important:
1. Use VM Pro Client to back up the data base (.mdb file) to my PC
2. Go into the Windows server - Program Files (x86) - Avaya - IP Office - VoiceMail Pro - VM - and copy the audio files in the Greetings, WAVS and Names folders to my PC in folders of the same name to keep things straight
3. Access the Linux command line on the App Server to change the write permissions of the Greetings, WAVS and Names folders - /opt/vmpro vmpro]# chmod 777 for each of the 3 folders
4. Use WINScP to copy the .wav files that were copied in Step 2 into the appropriate folders on the App Server. The Greetings, WAVS, and Names folders are write protected so Step 3 is necessary to allow Step 4 to work.
5. Use VM Pro Client to restore the .mdb file to the App Server
6. Give the App Server the same IP address as the Windows server or adjust the VM Pro address in Manager accordingly.

VM to Email settings will still have to 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 I have laid out above, but for the majority of our customers this has sufficed.

 
Nortel4Ever.
That works, but it doesn't hold the greeting choices or message new/old/saved setting files. It also doesn't translate well as some files are saved as opus files... not wavs. That was what I ran up against on my half assed upgrades. I wanted and achieved a real migration. It saves all the settings. Once I get my sand box test done and know if it really works all the way, I will share the FAQ. I also had issues with the Avaya Hyper-V install, but they have more to do with my ignorance. The 777 is cool but to change up the root access to do it right is better and is reversible and doesn't leave your system vulnerable.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
budbyrd,
Like I said, my solution is not perfect but it gets the job done for most of my customers. I'm interested to see what you come up with and if it will be any quicker or easier than my procedure. Thanks for your feedback.

 
@Nortel4Ever. I am almost done with my 'How To' FAQ. I would love some volunteers to help me make sure my docs work. I am using a decommissioned PC with Win 7 Pro from our IT department. I did the free W10 upgrade to get the Hyper-V services. Right now I am verifying my Hyper-V install docs for R11.0 and R11.1. If I have the time tomorrow I should have it complete and tested. But like everything else when writing this sort of doc, I assume things that the reader may not know. It would be nice to have a critique. The Avaya docs suck. I have condensed the Hyper-v app server ignition instructions from 111 pages to about 3.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top