Bug #73517 | scheduled Backup | ||
---|---|---|---|
Submitted: | 8 Aug 2014 23:20 | Modified: | 10 Aug 2014 19:28 |
Reporter: | Jassim Rahma | Email Updates: | |
Status: | Open | Impact on me: | |
Category: | MySQL Server | Severity: | S4 (Feature request) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any |
[8 Aug 2014 23:20]
Jassim Rahma
[9 Aug 2014 8:32]
Hartmut Holzgraefe
What's the problem with starting the backup tool of your choice with your operating systems scheduling system of choice (cron, ...)? remember that there is not *THE* backup solution but that there are several, depending on what kind of backup you want (logic, physical, with or without point-in-time recovery, ...) and sometimes also depending on what storage engine you use, like with MySQL Cluster where actual data isn't even stored in the MySQL server process(es) itself but managed by a different set of "data node" processes/machines)
[10 Aug 2014 19:28]
Jassim Rahma
then it won't be managed or shown in the administration portal. Having it within MySQL administration will allow the user to keep a track of it