Failover upgrade v 20

[Martin N.]

Hello guys,

we are running primary instance + passive one (failover) both on prem. First of all I ve upgraded primary one, there has been some pain, but at the end it was successfull. Now I am trying to upgrade passive one (3 attempts already made), but still cant go through. First of all, our passive is now completely out of order (failover disabled), there is also a licence issue, most probably due to the fact that primary one is already running ver. 20. So first attempt was the usual one, direct upgrade from management console, but it failed due to uknow reason. Second one was to setup new instance, restore the backup taken from primary one, but once there was the restoration process in place, especially licence activation, it took licence/FQDN from the primary one, so it crashed the primary one. Third attempt was to setup completely clean instance, reactivate licence (same issue once I restored it from backup) and obviously not possible to restore it from backup and restore failover role. So I am a bit curious on whats the best approach to upgrade passive instance generally?

We do have enterprise licence of course.

Many thanks in advance for your help!

 

[Alphabetic]

Should be a simple case of reinstall from fresh using the "install" feature from customer.3cx.com.

When it activates, the DNS will change to the IP of the slave. However, If you restart system services on primary then the DNS will update back.

 

[Martin N.]

I ve followed this approach again and after restoration of backup on passive instance (fresh installation) then none of the links directing to webclient/console is not working, FQDN was jumping between those two instances so I had to reboot main one 3 times and passive completely switch off. I wanted to open a ticket with the support, I had 2 or 3 tickets available like month ago, and now they are all gone...

 

[Alphabetic]

You need to ensure that when passive mode is enabled the services on it have stopped and you restart services/license refresh on main to update dns. not sure why youre having such a time getting it to work.

 

[Martin N.]

The point is that I cannot enable passive mode once I am not able to get in the webclient/management console itself after upgrade, or is there any cmdlet I can enable it directly on debian? After upgrade I was checking it and all services were up and running, but again not possible to access webclient/management console.

 

[Alphabetic]

Can you send over a screenshot?

 

[Martin N.]

Not sure what do you mean? Basically I followed the instruction after successfull upgrade, so like use links:

https://*FQDN*:443
https://*externalIP*:443
https://*internalIP*:443
https://*FQDN*:5001
https://*externalIP*:5001
https://*internalIP*:5001
https://*FQDN*:5001/#/login
https://*externalIP*:5001/#/login
https://*internalIP*:5001/#/login

Non of these above were working.