Fr0gg3r - MaartenS
Technical User
Hi,
It appears I'm missing some knowledge on the upgrade processes.
I've read through the documentation of the processes:
Physical SE / Appl Server:
What we basically are doing is installing a new image on a physical server.
But there is no mention of the proces of putting the current config of the server back in place?
If I'm installing a new ISO on a physical server, I'd be overwriting the OS that is currently installed. How does the new OS get the correct settings and the IPO configuration?
Same counts for an upgrade in VMWare. put the new disk in place, but no mention of putting the IPO config on the new disk.
I doubt that the automatic upgrade proces "installing a new disk or installing a new ISO" contains a migration thing that automatically puts the old IPO config on the new server.
Any suggestions?
There is no mention of putting an IPO backup back in the new OS..
Or am I just looking over that info?
thank you.
Most likely our way of migrating to R12 will be the same as our migrations from pre R11.0.FP4(centos6) to +R11.0FP4 (centos7).
We've done this multiple times without any problems.
I still believe that this is the best way to upgrade between different OS's:
- deploy a new OVA
- setup a new system with the same ip's and domain name etc ... but in temporary vlan)
- upload licenses
- Save old IPO config to pc
- Upload it to the new server. (same for VMPRO configuration and wave files)
- Upload certificates
- compare 46xxsettings files from both servers.
- Turn off the lan port of old server (you can keep the server running in case you need to go back to the old server.
- Change vlan of new server to operational voice vlan.
- phones will connect immediatly to the new server.
- siptrunks/sbc will connect to new server immediatly.
-> no downtime
-> Takes half time when comparing to first upgrading to latest R11.1, then upgrade to R12.
This also prevents you from having to setup a temporary server where you can backup your full ipo config to to be able to put it back in the new server.
It appears I'm missing some knowledge on the upgrade processes.
I've read through the documentation of the processes:
Physical SE / Appl Server:
What we basically are doing is installing a new image on a physical server.
But there is no mention of the proces of putting the current config of the server back in place?
If I'm installing a new ISO on a physical server, I'd be overwriting the OS that is currently installed. How does the new OS get the correct settings and the IPO configuration?
Same counts for an upgrade in VMWare. put the new disk in place, but no mention of putting the IPO config on the new disk.
I doubt that the automatic upgrade proces "installing a new disk or installing a new ISO" contains a migration thing that automatically puts the old IPO config on the new server.
Any suggestions?
There is no mention of putting an IPO backup back in the new OS..
Or am I just looking over that info?
thank you.
Most likely our way of migrating to R12 will be the same as our migrations from pre R11.0.FP4(centos6) to +R11.0FP4 (centos7).
We've done this multiple times without any problems.
I still believe that this is the best way to upgrade between different OS's:
- deploy a new OVA
- setup a new system with the same ip's and domain name etc ... but in temporary vlan)
- upload licenses
- Save old IPO config to pc
- Upload it to the new server. (same for VMPRO configuration and wave files)
- Upload certificates
- compare 46xxsettings files from both servers.
- Turn off the lan port of old server (you can keep the server running in case you need to go back to the old server.
- Change vlan of new server to operational voice vlan.
- phones will connect immediatly to the new server.
- siptrunks/sbc will connect to new server immediatly.
-> no downtime
-> Takes half time when comparing to first upgrading to latest R11.1, then upgrade to R12.
This also prevents you from having to setup a temporary server where you can backup your full ipo config to to be able to put it back in the new server.