MySQL Backup solution for non-technical user

Is there a simple browser-based MySQL backup solution for
non-technical users. The server is running Red Hat Enterprise Linux.
The main features needed are:
1) Automatic scheduled off-site backups (via SSH or FTP)
2) Backup multiple databases and all their tables
3) Single-table recovery via GUI (the user simply chooses which
database and which table to recover)
4) FOSS-license a big plus, but other licenses considered

I have ruled out cron/mysqldump for the GUI (browser-based) recovery
requirement.I found phpMyBackupPro which looks like a possible
solution, and I'd really appreciate other MySQL users' input on the
topic.

Thank you!

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: MySQL Backup solution for non-technical user

On 5/10/2011 3:55 PM, Dotan Cohen wrote:
> Is there a simple browser-based MySQL backup solution for
> non-technical users. The server is running Red Hat Enterprise Linux.
> The main features needed are:
> 1) Automatic scheduled off-site backups (via SSH or FTP)
> 2) Backup multiple databases and all their tables
> 3) Single-table recovery via GUI (the user simply chooses which
> database and which table to recover)
> 4) FOSS-license a big plus, but other licenses considered
>
> I have ruled out cron/mysqldump for the GUI (browser-based) recovery
> requirement.I found phpMyBackupPro which looks like a possible
> solution, and I'd really appreciate other MySQL users' input on the
> topic.



Check out Zmanda: http://zmanda.com/zrm-mysql-enterprise.html


Michael Heaney
JCVI


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: MySQL Backup solution for non-technical user

Zmanda ZRM backup, although the fancy webinterface is only available in the commercial version. Backups are stored on the host that runs the server, and of course it serves multiple MySQL machines.

Webinterface is annoyingly slow, though :-)


----- Original Message -----
> From: "Michael Heaney"
> To: mysql@lists.mysql.com
> Sent: Tuesday, 10 May, 2011 9:58:43 PM
> Subject: Re: MySQL Backup solution for non-technical user
>
> Check out Zmanda: http://zmanda.com/zrm-mysql-enterprise.html
>
>
> Michael Heaney
> JCVI
>

--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: MySQL Backup solution for non-technical user

On Tue, May 10, 2011 at 22:58, Michael Heaney wrote:
> Check out Zmanda: http://zmanda.com/zrm-mysql-enterprise.html
>
> Michael Heaney
> JCVI
>


On Wed, May 11, 2011 at 10:00, Johan De Meersman wrote:
> Zmanda ZRM backup, although the fancy webinterface is only available in the commercial version.
> Backups are stored on the host that runs the server, and of course it serves multiple MySQL machines.
>
> Webinterface is annoyingly slow, though :-)
>

Thanks, I passed the suggestion on. Might be what he is looking for.

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: MySQL Backup solution for non-technical user

Hi everybody!


Dotan Cohen wrote:
> Is there a simple browser-based MySQL backup solution for
> non-technical users. [[...]]
> The main features needed are:
> 1) Automatic scheduled off-site backups (via SSH or FTP)

Off-site = good (for reliability purposes).

> 2) Backup multiple databases and all their tables

Definitely a "must have".

> 3) Single-table recovery via GUI (the user simply chooses which
> database and which table to recover)

If your backup/recovery tool has this feature and your users ever go
that route, you (your DBA / your authorities) must be aware that this
will break any dependencies between that recovered table and all other,
un-recovered ones.

Example:
Assume a new entry is added to the "customer" table, then (at least) one
"order" is entered for this customer.
Before, during, or after that, some garbage change is done to the
"customer" table, it is detected, and someone decides "let's recover the
customer table from the last good backup".
This will get rid of the garbage, but will also make the orders for new
customer be pointing to nowhere.

IOW:
As soon as you have relationships crossing table boundaries, a
single-table recovery is a very risky operation, and it will violate any
"referential integrity" constraints involving that table.

> [[...]]


Regards,
Joerg

--
Joerg Bruehe, MySQL Build Team, joerg.bruehe@oracle.com
ORACLE Deutschland B.V. & Co. KG, Komturstrasse 18a, D-12099 Berlin
Geschaeftsfuehrer: Juergen Kunz, Marcel v.d. Molen, Alexander v.d. Ven
Amtsgericht Muenchen: HRA 95603

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: MySQL Backup solution for non-technical user

On Fri, May 13, 2011 at 10:21, Joerg Bruehe wrote:
> Hi everybody!
>
>
> Dotan Cohen wrote:
>> Is there a simple browser-based MySQL backup solution for
>> non-technical users. [[...]]
>> The main features needed are:
>> 1) Automatic scheduled off-site backups (via SSH or FTP)
>
> Off-site = good (for reliability purposes).
>
>> 2) Backup multiple databases and all their tables
>
> Definitely a "must have".
>
>> 3) Single-table recovery via GUI (the user simply chooses which
>> database and which table to recover)
>
> If your backup/recovery tool has this feature and your users ever go
> that route, you (your DBA / your authorities) must be aware that this
> will break any dependencies between that recovered table and all other,
> un-recovered ones.
>
> Example:
> Assume a new entry is added to the "customer" table, then (at least) one
> "order" is entered for this customer.
> Before, during, or after that, some garbage change is done to the
> "customer" table, it is detected, and someone decides "let's recover the
> customer table from the last good backup".
> This will get rid of the garbage, but will also make the orders for new
> customer be pointing to nowhere.
>
> IOW:
> As soon as you have relationships crossing table boundaries, a
> single-table recovery is a very risky operation, and it will violate any
> "referential integrity" constraints involving that table.
>
>> [[...]]
>
>
> Regards,
> Joerg

Thanks Joerg for that insight. In fact, this is a very simple
installation with no joins but I will keep that in mind for the
future. Terrific point.


--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org