IP Office Migrating from Metal server to Virtual server

[NYSTECH]

Customer is going to migrate from Avaya 630 server to a Virtual server. I am trying to see what is best practice to do this. How has anyone done this?

I was thinking of spinning up the New Virtual server with the current release on the 630. Which is 11.1.3. 2
Do a full backup from 7071 on the 630 server.
Restore that to the new virtual sever running 11.1.3.2. Would I have issue with the restore if the IP addresses are different on the 2 servers? Or any issue going to a virtual sever from Hard metal server?)
Then upgrade virtual sever to 12.0.0.0.0 bld56

Or can I just spin up Virtual sever with 12.0 and do a restore from metal server at 11.1.3.2

And gotchas or steps to take for either scenarios?

 

[SihDEK]

Customer is going to migrate from Avaya 630 server to a Virtual server. I am trying to see what is best practice to do this. How has anyone done this?

I was thinking of spinning up the New Virtual server with the current release on the 630. Which is 11.1.3. 2
Do a full backup from 7071 on the 630 server.
Restore that to the new virtual sever running 11.1.3.2. Would I have issue with the restore if the IP addresses are different on the 2 servers? Or any issue going to a virtual sever from Hard metal server?)
Then upgrade virtual sever to 12.0.0.0.0 bld56

Or can I just spin up Virtual sever with 12.0 and do a restore from metal server at 11.1.3.2

And gotchas or steps to take for either scenarios?

We migrated a few days ago our ipoffice v 11.1.3 to a new virtual platform on vxrail in ipo v11.1.3.2. I do not recommend version 12.0 at this time. To start, we have 2 VMs installed because we have a primary and a secondary one. Ova in 11.1.3. I put a virtual network isolated from production but I kept the same IP addresses of production. I preferred to work on this isolated virtual environment to test Ipocc Xmedius and ACR connexions. With manager on my production I exported the configuration from by recording the configuration to file. primary and secondary ipo configuration and the two Gateways) I then imported into the virtual environment. I tested and validated everything. On the day of migration, I just stopped the physical servers and put the virtual servers on the network of the production.

 

[Swiney52]

I upgraded from a physical server to a virtual server on an earlier version of 11.1 and didn’t have any major issues. We did the upgrade after hours so we were able to remove the existing server from the network before brining the new server online with the same IP address.
I’m not sure what all issues would arise if you change the IP address but there would definitely be some things to work through. I think it would be better to keep the IP address the same if possible.
Either way I would not upgrade to 12 at this time. There are a lot of pretty serious bugs with IP routes and some other things. I currently have two tickets open with Avaya for issues on 12. Until they get this sorted out I’m not going past the latest version of 11.1

 

[NYSTECH]

When you did upgrade, did you do a backup form the Web Page then restore it from the Web Page?

 

[Swiney52]

When you did upgrade, did you do a backup form the Web Page then restore it from the Web Page?

It's been a couple years since I did the upgrade. I used the web backup but I also made sure I had backups of the configs from manager as well as separate VMpro backups just in case the web backup didn't work I could restore everything individually

 

[biv343]

When I did this in the past, I had the customer spin up a new server and ignited it with a temporary IP. I saved the IPO config and ran a full backup of voicemail. When we swapped, the customer unplugged the network cable from the physical server, I sent the config to the new virtual server, restarted, made sure the IP was correct, rehost the licenses, restored voicemail and done. The 'roll back' plan was to kill the virtual server and reconnect the physical server cable. Didn't need to roll back though.

This was a couple years ago in the 11.0.4 days. If I remember correctly, downtime was about 20-30 minutes.