Failover and Backup

Status
Not open for further replies.

rc179

Silver Partner
Basic Certified
Joined
May 1, 2020
Messages
97
Reaction score
11
I've been looking at the Fail-over capability. This seems to essentially a scheduled backup, a scheduled resore, and an availability monitor. That all fine. But if I want to keep a separate backup, maybe to a different location, I can't. Am I correct in this?

I can see wanting to have a full backup, including Licensing Key information, but a Fail-over backup specifically does not include this.

A somewhat separate question would be, what if I configure the backup for fail-over (no licensing info) with a 10 rotation. Will the scheduled restore on the secondary system correctly use the newest backup?
 
if you want a failover system, you are better off getting enterprise license which allows you to run two servers using the same license key and have failover as per info in the 3cx docs

this way each server can have the same license key and fqdn , when you switch over there will be no configuration chaanges required for the phones as you will use the fqdn and not ip address
 
Last edited:
if you want a failover system, you are better off getting enterprise license which allows you to run two servers using the same license key and have failover as per info in the 3cx docs

this way each server can have the same license key and fqdn , when you switch over there will be no configuration chaanges required for the phones as you will use the fqdn and not ip address
I'm aware of this, when I said backup, I'm referring to the backup process, where you select what you want to backup. Fail-over specifically wants this to NOT include licensing information.

This is the meaning of backup throughout my post.
 
You can run failover using two versions of Pro license, so I am guessing if you do not include license and fqdn you can restore to the backup server.
 
You can run failover using two versions of Pro license, so I am guessing if you do not include license and fqdn you can restore the backup server.
I don't think you understand the question or maybe the failover process/config

To create a failover pair you build 2 systems and apply the same license to both. You restart the services on the Primary after the Secondary is set up so it willo be what is registered and will have the FQDN pointed to it.

You configure a scheduled backup of the primary to a mutually accessible storage location.
You configure a scheduled restore of the secondary using the backup of the primary as a source.
You configure Failover on both systems with the Primary as Active and the secondary as Passive (this is you monitoring).

All this is very straight forward.

The first question was to verify what I believe is the case, that you cannot have an additional backup process to the same or different location. This would allow for routine archive backups to use if the worst case happened and you lose both the primary and secondary. In that case you would want the licensing information included in the backup, which is not allowed when the backup is used for failover.

The second question was to establish that the scheduled resort on the secondary would know to use the latest backup if you were retaining multiple iterations of the backup.
 
Hi Rc179,

you are right. There is no other 3CX included option using the automated backup. But you can use a Windows Taskmanager or cron job with rsync on linux to save the backup folder to a different location.

Restore will always use the latest backup named "3CXScheduledBackup.zip" in the folder.
Take care that the main and backup system are using the same path (the early V16) 3CX changed the path to the path of my master pbx after the first restore.

BR
 
Hmmm it seems I'll also have to put each system into it's own folder, with our asterisk systems the backup file name was specific to the system so they all went in the same folder. With the filename being the same accross all 3CX I need to make sure they are in different folders.

Thanks
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,948
Messages
589,880
Members
164,841
Latest member
erre