Backup/restore - do I need to have all licenses current?

Commercial Products and Partners Sangoma
1

I am trying to upgrade freepbx 14 to 16 by taking a backup on the old 14 pbx and restoring it on a new 16. I plan to use the same deployment id.

  • Do I need to have all licenses current? I have 25 year licenses but module updates expired a year back?
  • I am wondering if I need to purchase module updates/maintenance for those licenses for this to work correctly. I keep reading to update all modules before taking backup and I can’t do that with the expired updates.
  • How about the restore procedure? Does that need licenses with current date?

Thanks.

2
  • Do I need to have all licenses current? I have 25 year licenses but module updates expired a year back?

No. Licenses can be updated after the migration on the new server.

As mentioned above, you do not need to update all modules before the migration.

  • How about the restore procedure? Does that need licenses with current date?

Once you restore everything, you can then migrate the deployment ID, and all licenses should carry over. As for the expiration dates on the new server, it should also update (it did with my migration).

Disclaimer: We went from a waaaay lower version to 15, and the above answers were from my migration. I assume it would still apply to your situation since i’m sure there are plenty of migrations from older expired licenses to a newer version.

3

Generally you don’t need current maintenance on commercial modules for a backup or a restore. If you’re using modules behind on updates tho, its possible you might run into an old bug that affects the backup or restore process.

4

It seems some people try a restore on the new PBX without commercial module licenses.

So, they do the following:

  • Install Freepbx 16 on New VM
  • Activate it with a new deployment ID.
  • Don’t purchase new commercial modules or move the old deployment id.
  • Restore the backup from freepbx 14.
  • Then move the old deployment ID to the new VM which has the commercial module licenses.

Will restore work successfully? I have read some people complaining about some commercial modules failing if restore is done without the commercial module licenses especially for Zulu/Sangoma softphones (After restore to new home, can't install Zulu or Sangoma Connect - #15 by GSnover).

I have the following licenses in my system. I would like guidance on whether I can do the restore without commercial licenses in my new VM and then move the old deployment id or should I just purchase a temporary one year license for commercial modules for the new VM, do the backup/restore, test and then move the old deployment ID which has 25 year licenses to the new VM. I can’t have down time with this client of ours.

But, then I have 200 user softphone license. I really don’t want to purchase a new softphone license or other expensive licenses like restapps again just for the upgrade. But, if it needs a new license for successful upgrade without downtime, I may choose to do it.

Call Recording Report Expiration Date 2045-12-16 (Free Updates until 2021-12-16)
Conferences Pro Expiration Date 2045-12-16 (Free Updates until 2021-12-16)
Endpoint Manager Expiration Date 2045-01-03 (Free Updates until 2021-01-03)
Extension Routing Expiration Date 2045-12-16 (Free Updates until 2021-12-16)
Paging Pro Expiration Date 2045-12-16 (Free Updates until 2021-12-16)
Rest Apps Expiration Date 2045-01-03 (Free Updates until 2021-01-03)
Sys Admin Expiration Date 2045-12-16
Voicemail Reports Expiration Date 2045-12-16 (Free Updates until 2021-12-16)
Fax Pro Expiration Date 2045-12-16 (Free Updates until 2021-12-16)
Park Pro Expiration Date 2045-12-16 (Free Updates until 2021-12-16)
Zulu Expiration Date 2023-01-20 (Free Updates until 2022-01-20)
Zulu Users 200

5

How many commercial module licenses did you have on your PBX? I am skeptical of whether the restore will work without licenses for all commercial modules. I have more than 10 licenses which are listed in the above thread.

I am hoping for inputs from more people who have tried upgrades with multiple commercial module licenses.

6

The most important thing is that the module needs to be installed on the server you are restoring to. It does not need to be licensed, but as long as it is installed, all of the bits should restore.

7

This is everything i had migrated over.

Registered Modules

Appointment Reminders

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Caller ID Management

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Call Recording Report

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Conferences Pro

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Endpoint Manager

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

EPM for UCP

Expiration Date 2041-04-13

Extension Routing

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Outbound Call Limit

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Paging Pro

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

QXact Reports

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Rest API

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Rest Apps

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Sys Admin

Expiration Date 2041-04-13

VM-Notify

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Voicemail Reports

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Web Call Back

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Broadcast

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Fax Pro

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

XMPP

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Pinset Pro

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Park Pro

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

VQ Plus

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

Class of Service

Expiration Date 2041-04-13 (Updates and support until 2017-04-13)

8

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.