[Spce-user] SQL Export

[Adam Clark]

Hi Daniel,

Thanks for the response.

We have since written and internal script to dump the MYSQL data. Convinced them it was safer J

I will look at the method advised as well.

Thanks once again.

Kind regards,

[sig1]

This e-mail and any attachments transmitted with it, including replies and forwarded copies subsequently transmitted, contains information which may be confidential and which may also be legally privileged. The content of this e-mail is for the exclusive use of the individual(s) or entity named above, if you are not the intended recipient, please note that any form of distribution, copying or use of this e-mail or the information in it is strictly prohibited and may be unlawful. If you have received this e-mail in error please reply to the sender at Structured Communications Ltd and then delete the e-mail immediately. Any views or opinions presented are solely those of the author, and may not necessarily represent those of Structured Communications Ltd. Structured Communications Ltd is registered in England and Wales, registered no 07667451, and its registered office is 22 London Road, Horsham, West Sussex RH12 1AY. Registered VAT number GB116507336.


From: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Daniel Grotti
Sent: 03 July 2014 16:56
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] SQL Export

Hi,
mysql port 3306 is closed from external by default.
You should enable the backutools in your config.yml in order to perform regular backups/mysqldump of your data and DB.

Daniel




On 07/02/2014 10:25 PM, Adam Clark wrote:
Evening Gents,

Just put a CE box in and deployed it to a limited number of PBXs.

My programmers want to backup this in the same way we backup our Asterisks systems and they have already built a platform for this.

They need direct access to the SQL server via 3306 (locked down to our backup platform) However 3306 is not responding to query's from an external source. Looking at the SQL config there is no BIND address to the external IP so I assume his is why this is failing.

There concern is, if we write the line in to bind the IP, is SIPWISE likely to die and be unable to contact its databases?

(I prefer dealing with our core over SQL so forgive me for asking stupid questions)

Any advise welcome. Thanks Guys



Kind regards,

[sig1]

This e-mail and any attachments transmitted with it, including replies and forwarded copies subsequently transmitted, contains information which may be confidential and which may also be legally privileged. The content of this e-mail is for the exclusive use of the individual(s) or entity named above, if you are not the intended recipient, please note that any form of distribution, copying or use of this e-mail or the information in it is strictly prohibited and may be unlawful. If you have received this e-mail in error please reply to the sender at Structured Communications Ltd and then delete the e-mail immediately. Any views or opinions presented are solely those of the author, and may not necessarily represent those of Structured Communications Ltd. Structured Communications Ltd is registered in England and Wales, registered no 07667451, and its registered office is 22 London Road, Horsham, West Sussex RH12 1AY. Registered VAT number GB116507336.






_______________________________________________

Spce-user mailing list

Spce-user at lists.sipwise.com<mailto:Spce-user at lists.sipwise.com>

http://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140703/96ffb64a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 12937 bytes
Desc: image001.png
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140703/96ffb64a/attachment-0001.png>