3CX - Backup Options

[Alan Figgins]

Hi All,

I have a client that wants to run backups from the command line (separate from the ones scheduled in 3CX itself).

This is a very standard setup on the current 3CX Debian ISO.

We have tested and given them the commands to do this from the Debian Command Line:

cd /var/lib/3cxpbx/Instance1/Bin/

sudo -u phonesystem /usr/sbin/3CXBackupCmd --file=YYYYMMDD-HHMM-3CX_Backup_All.zip --options=ALL --log=/tmp/YYYYMMDD-HHMM-3CX_Backup_All.log

The client is happy to be able to backup 3CX like the above, but they also require the ability to periodically create an image of the server.

Their preference is to use either dd or ddrescue.

Their thinking is that, if the server 'dies' then they would replace the hardware, restore the dd image, then restore the 3CX backup, all without requiring any access to the 3CX console (they are very comfortable running servers, but prefer not to have to get into any specific applications - such as 3CX - if they can avoid it).

Once that is done, they would reboot, and the phone system should be up and running (minus any config changes and, for example, voicemails that were left after the backup was last run, so max of 24 hours of 'loss' or whatever period the backups are run).

That's all sounding fine to me, but do they need to take the Debian server down, and boot from a 'live disk' to run the dd backup? I assume so, but maybe I am wrong? If so, then the phone system would need to be down for some time (maybe hours - not sure) while the image is created.

Now, that might be okay if they are only imaging once every few months (say), but I just wanted to check, and also ask what others here do in this respect?

Thanks,

Alan.

 

[JohnS_3CX]

It would require shutting down the OS to avoid data loss.

You should also look into VM Snapshots along with regular disk backups, if you deploy the instance on a virtualized server.

 

[Alan Figgins]

Hi John,

That was what I thought (they presumably already know this too).

VM snapshots seem to have a bad reputation in some quarters, and this is not a virtualised server in any case - at least for now, so not an option at this point.

What do you do?

Alan.

 

[BrenttG]

If its a physical server, there is no good image solution that will not require bringing it down, as using dd will copy all the disk data however it will not capture it in the moment, so as it is copying, if a bit of data moves or changes, you will end up with data loss or corruption.

It sounds like your client does not understand this about dd.

next best option to everything listed here might just be something like this:
https://pbxmonitor.net/backup.php

 

[Alan Figgins]

Hi BrenttG,

I'm pretty sure they already know they would need to bring the server down to run an image.

It is my concern, rather than theirs, that this will mean the phone system being down for a period, maybe a few hours, while they do this.

Rather than the above options, I am considering implementing a failover server - that way they can take down one, back it up, and the other will pick up within a few minutes.

This seems like a better option than anything else I have see so far, and if (maybe a big if!) I can virtualise both 3CX servers on pre-existing virtual hosts they already have, then it will be a pretty low cost solution too, with only the marginal cost of an enterprise license if I am understanding correctly?


Alan.

 

[YiannisH_3CX]

Hello @Alan Figgins

A failover server would be the best option for your scenario as you can automatically backup one server and restore it to the failover server.
It will also be on a different server so the need for extra backups might be negated. Of course you can never have too many backups

 

[Alan Figgins]

Thanks for your suggestions guys.

As per my post above, and YiannisH_3CX's endoresement, I think we'll go with a failover server.

Alan.