Restoring previous backup newer than PBX version

Status
Not open for further replies.

bgrattan

Customer
Joined
Mar 10, 2020
Messages
5
Reaction score
2
Good evening all,

Due to some unusual network inefficiencies, I am moving my 3CX instance to a different server. I logged into my account and downloaded the latest version (V18 Windows). After installation and the option to upload previous backup, we are met with the following error and are unable to move forward:

The backup version 18.0.2.314 is newer than the PBX version 18.0.2.307. You can restore this backup only with PBX version 18.0.2.314 or newer.

I have scoured the threads and looked all over the downloads, but am at an impasse as I cannot find a newer version to restore my backup to.

Any help is greatly appreciated.

Brian G.
 
Sadly this is the same version as I downloaded earlier today. Currently trying to force an update a bogus install to get to the promise land.
 
Try to install the new PBX without backup and upgrade to the new version, than restore your backup. 314 is the actual version.
 
  • Like
Reactions: ChrisC_3CX
What @bitn2 said should work, just make sure that, if the backup file has license key information in it that you use the same license key when deploying the new machine.
 
Thanks for the quick responses. I had figured that out and was going to follow up with a response. Awesome community thanks for the help!!
 
  • Like
Reactions: ChrisC_3CX
Our pleasure! So just to confirm everything is up and running now?
 
Our pleasure! So just to confirm everything is up and running now?
We are having a similar issue. So create a new PBX, using the existing license key. Then perform the update. Then restore the backup. Is that correct?
 
We are having a similar issue. So create a new PBX, using the existing license key. Then perform the update. Then restore the backup. Is that correct?
If the problem is that the backup version is newer than the installation version and we're talking about the same v18 versions then yes. Do not uninstall/delete the old machine unless you've confirmed everything is running well with the new one. Just make sure the old one has no internet connection or is turned off so it does not affect the License activation or FQDN DNS records.

If your scenario is different it might be best you provide more info so that we can first evaluate the situation a bit more.
 
  • Like
Reactions: AWS2P
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,083
Members
164,901
Latest member
Silent_Guru