Sync 2 Vici VULTR and DIGITAL OCEAN

[xodiacx]

Hi Guys

How can I sync two vicidial servers from two different cloud provider, VULTR and DIGITAL OCEAN.

Thanks

[ed123]

what you mean by sync the two servers? more details pls?

[xodiacx]

Hi ed123

Let's say that Vici is hosted in VULTR and will be the primary server, now if VULTR cloud provider is down due to unforeseen situation we want to be able still make outgoing and receive incoming calls from DIGITAL OCEAN backup server. Maybe like a FAIL OVER setup at the same time the data is sync between the two servers.

THanks

[xodiacx]

up up up up up

[ambiorixg12]

I dont think there is an existing tool on vicidial to sync servers, but you should take a look to the script /usr/share/astguiclient/ADMIN_backup.pl and use it to back the production server a backup server and using DNS as floating IP

[xodiacx]

Hi @ambiorixg12

can you please explain it further?

THanks

[williamconley]

up up up up up

Don't try to "up" in phpBB. Your post shows activity (your "up" attempt) and gets ignored. It looks like you're getting answered but actually you're just talking to yourself. Kinda the opposite of what you want. Can cause your post to be ignored for a while since someone is obviously helping you. Case in point: Sorry I'm late. lol.

Vicidial has a method to sync the db by setting up a "reporting" server. But that server is a Slave server and not capable of operating automatically as the new DB without some changes. However, it would keep the database synced. Alternately, you CAN perform the same basic DB sync by using the generic mysql slave server tools that Kumba uses to set up the reporting server during installation of the reporting servers. Just a question of how you prefer to do it.

Note that there are some errors distinct to the Vicidial system you'll need to have mysql ignore. For instance, after a reboot, the memory tables will be empty. If you ever reboot the slave server (which is a good idea, daily), those memory tables will be empty. If the DB server didn't reboot during that same period, it will have entries in the memory tables. If the primary DB attempts to modify (instead of delete or insert) one of those entries ... the missing entry will cause a sync error and sync will stop until you resolve the issue. Kumba's method if installation seems to be quite good at handling this sort of thing.

Oh: An added benefit is that you CAN use the server in question for reporting, which removes load from the running server for those reports. Handy.

During this entire process remember one very important fact: Vicidial's DB, Web and Dialer servers must ALL be in the same physical location to work as a cluster. Once you have switched to the DB at a different location, you must also switch to a dialer/web at that location. Or expect serious disruption and instability.