V18 Upgrade Failure

[Matt_Olan]

I attempted to upgrade my 3CX instance to V18 last week but it failed. My 3CX instance is running on Debian 9. It appeared to be the Debian OS upgrade that hung up \ failed

I was thinking for attempt 2 that I would manually do the Debian 9 to 10 upgrade then run the 3CX upgrade once complete.
Does anyone know if this should work or would this cause problems with 3CX if I manually upgraded Debian first?

Thanks

 

[Agathocles Prodromou]

Hi,

Do not attempt to upgrade Debian manually. When it failed, did you receive an email with the upgrade log attached?

Upon failure, did your system automatically revert to V16?

 

[Matt_Olan]

no I did not get an email. I let it run for over 2 hours before I restored the entire VM from backup as it was completely non responsive

 

[cobaltit]

If it's virtualized and you have a backup, stop wasting time trying to 'fix' the upgrade. Make a 3CX backup, copy it off the VM, shutdown the VM, make a new VM from the 3CX ISO and restore your backup

 

[Matt_Olan]

If it's virtualized and you have a backup, stop wasting time trying to 'fix' the upgrade. Make a 3CX backup, copy it off the VM, shutdown the VM, make a new VM from the 3CX ISO and restore your backup

That is Plan B right now. It is virtualized on Azure. but it has an Azure reservation attached. I am not 100% sure what happens with the reservation if I do that.

 

[Agathocles Prodromou]

As cobaltit correctly said, the way to go is start fresh. Take a full backup of 3CX, use the 3CX Debian 10 ISO on a new VM and restore your backup. Don't forget to shutdown your old (Debian 9) instance before you restore on the new machine.

 

[Matt_Olan]

As cobaltit correctly said, the way to go is start fresh. Take a full backup of 3CX, use the 3CX Debian 10 ISO on a new VM and restore your backup. Don't forget to shutdown your old (Debian 9) instance before you restore on the new machine.

Ok, Thanks I figured that, but do you know anything about the Azure Reservations side and how to correctly handle that?

 

[Agathocles Prodromou]

Unfortunately I cannot provide a definite answer about that but the following pages should give you all the information you need:

• https://docs.microsoft.com/en-us/az...ervations#flexibility-with-azure-reservations
• https://docs.microsoft.com/en-us/az...ations/exchange-and-refund-azure-reservations

If not, then I suggest to clarify this with an MS representative.

 

[Evolute IT]

Ok, Thanks I figured that, but do you know anything about the Azure Reservations side and how to correctly handle that?

The way it seems to work (I read the docs posted by @agp), is like AWS. The reservation is tied to your account, not the VM. So you can spin a new one, configure it, and then delete the old one. Just make sure it's the same VM type. The reservation would then apply to the new VM instead.

 

[RCT-CP]

Microsoft CSP here. I can confirm @ConceptsWeb 's answer. It's not tied to the individual VM. Think of them like entitlements for your Azure tenant. When I order a VM reservation for a customer I don't connect it to a specific VM, just associate it with their tenant/domain. So long as the VM size is the same, it won't care.