[asterisk-users] Write to multiple databases as redundancy scheme

2007-06-08 Thread rjcarvalho

Hi,

Can Asterisk write to multiple MySQL databases in different machines,  
at the same time, as a backup scheme?

If it does, where can that be configured? In res_mysql.conf file?

Does anyone ever made it?

Regards,
Ricardo.


___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] Write to multiple databases as redundancy scheme

2007-06-08 Thread Bobby Crawford
MySQL has its own ways of doing this kind of thing.  Take a look at the
documentation http://dev.mysql.com/doc/refman/5.0/en/replication.html  on
MySQL's website related to replication.

 

Bobby

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, June 08, 2007 11:45 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] Write to multiple databases as redundancy scheme

 

Hi,

Can Asterisk write to multiple MySQL databases in different machines, at the
same time, as a backup scheme?
If it does, where can that be configured? In res_mysql.conf file?

Does anyone ever made it?

Regards,
Ricardo. 

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Write to multiple databases as redundancy scheme

2007-06-08 Thread Chris Mason (Lists)
It would be better to let MySQL handle that - use the built-in 
replication facilities. It's easy to setup.


--
Chris Mason
(264) 497-5670 Fax: (264) 497-8463
Int:  (305) 704-7249 Fax: (815)301-9759 UK 44.207.183.0271
Cell: 264-235-5670
Yahoo IM: [EMAIL PROTECTED] 



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Write to multiple databases as redundancy scheme

2007-06-08 Thread Bryan Laird
Why would you do this why put the overhead inside asterisk when  
mysql has perfectly good replication mechanisms built in?



On Jun 8, 2007, at 12:44 PM, [EMAIL PROTECTED] wrote:


Hi,

Can Asterisk write to multiple MySQL databases in different  
machines, at the same time, as a backup scheme?

If it does, where can that be configured? In res_mysql.conf file?

Does anyone ever made it?

Regards,
Ricardo.
___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Bryan Laird, Sr. Manager CM Operations
   -+-
Cablemodems are the gateway to the Internet.
The Internet is a gateway to some things that are  better left un-seen.


___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Write to multiple databases as redundancy scheme

2007-06-08 Thread Doug Lytle

[EMAIL PROTECTED] wrote:

Hi,

Can Asterisk write to multiple MySQL databases in different machines, 
at the same time, as a backup scheme?

If it does, where can that be configured? In res_mysql.conf file?


Not that I'm aware of, but you can setup MySQL to mirror the data to a 
slave database.


Doug


--

Ben Franklin quote:

Those who would give up Essential Liberty to purchase a little Temporary Safety, 
deserve neither Liberty nor Safety.


___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Write to multiple databases as redundancy scheme

2007-06-08 Thread Anthony Francis

Justin Moore wrote:

On 6/8/07, Chris Mason (Lists) [EMAIL PROTECTED] wrote:

It would be better to let MySQL handle that - use the built-in
replication facilities. It's easy to setup.


That's a great idea for backup purposes, but if the OP is wanting true
redundancy, that won't help much. What happens then when the primary
box fails? CDR not written to the primary can't be replicated...


This is when you would use a mysql cluster and a VIP.
___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Write to multiple databases as redundancy scheme

2007-06-08 Thread Justin Moore

On 6/8/07, Chris Mason (Lists) [EMAIL PROTECTED] wrote:

It would be better to let MySQL handle that - use the built-in
replication facilities. It's easy to setup.


That's a great idea for backup purposes, but if the OP is wanting true
redundancy, that won't help much. What happens then when the primary
box fails? CDR not written to the primary can't be replicated...

--
Justin Moore
aka wantmoore
---
www.wantmoore.com
___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


RE: [asterisk-users] Write to multiple databases as redundancy scheme

2007-06-08 Thread Watkins, Bradley
UltraMonkey (www.ultramonkey.com) and MySQL Cluster
(http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster.html)

It works a charm.

- Brad 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Justin Moore
 Sent: Friday, June 08, 2007 2:13 PM
 To: [EMAIL PROTECTED]; Asterisk Users Mailing List - 
 Non-Commercial Discussion
 Subject: Re: [asterisk-users] Write to multiple databases as 
 redundancy scheme
 
 On 6/8/07, Chris Mason (Lists) [EMAIL PROTECTED] wrote:
  It would be better to let MySQL handle that - use the built-in
  replication facilities. It's easy to setup.
 
 That's a great idea for backup purposes, but if the OP is wanting true
 redundancy, that won't help much. What happens then when the primary
 box fails? CDR not written to the primary can't be replicated...
 
 -- 
 Justin Moore
 aka wantmoore
 ---
 www.wantmoore.com
 ___
 --Bandwidth and Colocation provided by Easynews.com --
 
 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
 
 

The contents of this e-mail are intended for the named addressee only. It 
contains information that may be confidential. Unless you are the named 
addressee or an authorized designee, you may not copy or use it, or disclose it 
to anyone else. If you received it in error please notify us immediately and 
then destroy it. 
___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Write to multiple databases as redundancy scheme

2007-06-08 Thread David Gomillion

On 6/8/07, Justin Moore [EMAIL PROTECTED] wrote:


On 6/8/07, Chris Mason (Lists) [EMAIL PROTECTED] wrote:
 It would be better to let MySQL handle that - use the built-in
 replication facilities. It's easy to setup.

That's a great idea for backup purposes, but if the OP is wanting true
redundancy, that won't help much. What happens then when the primary
box fails? CDR not written to the primary can't be replicated...



If it's only for the unlikely event that a DB server is unavailable, why not
have it log the CDR in text and in MySQL? If the DB server is unavailable,
the records could be parsed from the text file and the database updated.

Of course, if you had to do this more than once or twice, it would get a bit
annoying, I'm sure. But then again, write the script to do it, and use it to
populate the other databases? Dunno, just thinking out loud here.

I've written a few parsers, and the format appears to be easy to parse. It
really wouldn't be too big of a deal. The hardest part will be kicking it
off (I'd use cron), parsing the file (my personal preference would be perl
or PHP), updating the database, and making sure you don't insert duplicates.


I think I would use the UniqueID as they key, and then just use INSERT
statements. You may need an IGNORE in it to allow it to keep going, even
when there are duplicates. It's been a while since I wrote something to
update a DB where I was unsure of the data hygiene.
___
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users