Hi!
We are in the phase of moving from development to production and we have realized, while configuring the backup system, that the process usually takes up to 20 minutes to backup a node in snapshot mode.
Said time is a problem because leaves the MySQL service inoperative during 20-minutes period.
Each node (a total of 3) consists of two virtual machines (one scheduled @03:30 a.m and the other @04:00 a.m) without the qemu agent enabled, with ubuntu 20.04, one with mysql server (mysql Ver 14.14 Distrib 5.7.39, for Linux (x86_64)) from ubuntu repo and the other VM with a docker containers, and two volumes, one where the backups related to that node are stored and another that is the volume shared between all the virtual machines, together with the volumes that are created by default.
Is this normal? Are we misconfiguring the backup system? We believe that a 20-minute downtime for our service is excessive.
We are in the phase of moving from development to production and we have realized, while configuring the backup system, that the process usually takes up to 20 minutes to backup a node in snapshot mode.
Said time is a problem because leaves the MySQL service inoperative during 20-minutes period.
Each node (a total of 3) consists of two virtual machines (one scheduled @03:30 a.m and the other @04:00 a.m) without the qemu agent enabled, with ubuntu 20.04, one with mysql server (mysql Ver 14.14 Distrib 5.7.39, for Linux (x86_64)) from ubuntu repo and the other VM with a docker containers, and two volumes, one where the backups related to that node are stored and another that is the volume shared between all the virtual machines, together with the volumes that are created by default.
Is this normal? Are we misconfiguring the backup system? We believe that a 20-minute downtime for our service is excessive.
Last edited: