VM Pro migration w/in SCN

[wingnutkev]

Has anyone ever had to relocate a VM Pro server to another node within a Small Community Network?

I have a customer who planned on expanding a site a relocating their HQ when we installed the system so we made this site our main site hub. Now they have had some problems, things haven't gone as planned and the planned HQ has been tabled. The site has power issues so we need to relocate the VM Pro server to the current actual HQ.

I plan on moving the system SD with all the license over to the current HQ and re configuring the SCN to point to this as the new hub.

Will a back up and restore put everything back once the VM system has been configured on the new IPO? I think this will work since the accounts and everything else stays the same.

 

[Gunnaro]

I take it for granted that the chassis you are moving to is a 500V2 too.

On what Release are the systems?

Are you moving SIP-trunk/ISDN/POTS too?

If there are licenses on the "Current HQ" SD card that you need in the future, they won't be transferred to the "Swap" SD card.
(Unless you get Avaya to recycle them and hand in the old SD card, no guarantee that they will).

When you move the VMPro, update the new IP address for it on all IPO's in your SCN.
If they use it for more than voicemail, i.e. call flows, that must be taken care of while moving the server.

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

 

[wingnutkev]

There are 4 IPO 500 V2s on the SCN, 7.0(36)

The licensing on both HQ are similar enough other than the VM licenses and the number of voice networking channels. As far as licenses I was just planning on exchanging them, swapping SD cards and moving the licenses to the respective units.

Both units have a PRI for service and are licensed the same in that respect, there are no POTS or SIP trunks involved.

 

[Gunnaro]

Then, I think it safe to say you can move


Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

 

[punchtool]

Wingnutkev quick question I'm wandering if you resolved the issue with one of your old threads.

Exchange UMS issue
thread940-1704109

 

[wingnutkev]

We did stop experiencing the issue as often after an upgrade. I don't recall what release made a difference. One site is on 9 now the other still running 8.1.x

 

[punchtool]

I have 3 sites on 9 with UMS and once they listen to a new message here is what happens. You see it in visual voice as an old message and 5 hrs ahead as the time stamp when trying to listen to it. The phone just beeps but you go into *17 and listen to it or use email.

 

[wingnutkev]

I would suggest you make a new thread. I had opened a call with Avaya at the time but I do not recall what happened with it. I have since changed positions and do not work on either system any more.

Does it sync back up if you restart the VM service. I seem to remember it works fine for a while until the VM and Exchange loose connectivity. Once the connection is interrupted, I think I had to restart VMPro service to get things to sync back up.

 

[intrigrant]

Back to the original question: you can move the VM Pro to any SCN node but you must update all the other nodes vm setting regarding the location were VMPro resides.
I've done this a several times and it gave no problem.

 

[wingnutkev]

Yeah the move went well, we had no issues. Thanks for the reply.