Are there any mysqldump options required when doing a backup? https://linux.die.net/man/1/mysqldump
Gzip and mysqldump are required for backup tool to work in UseResponse properly.
Please learn more details How to Backup & Restore UseResponse?
I had reviewed the link and understood the requirements prior to my question. The linked page merely states "Creating sql dump of your database using console or popular DB management tools like Adminer, phpMyAdmin." but it does not provide any specifics on the mysqldump options (see also the provided manpage link to mysqldump). Are there any mysqldump options that are needed when doing a backup?
You should have mysqldump installed on your server. That's the primary option to make backups.
Once your server meets this requirement, the backup will be done automatically on a daily basis.
I started a backup but do not see it after 5 minutes. mysql-client, which includes mysqldump, is installed on the system. Why do I not see the backup, where are the settings to change the frequency, and what is the path that it is saved to?
With our built-in backup tool, your database will be copied automatically in /work folder in .sql format on a daily basis.
Do you have the latest 5.2.3 version of UseResponse?
I have 5.1.4. Will it work on this version. From a DevOps and operational perspective, we would prefer to upgrade quarterly unless there is a way to programmatically convert the existing database. Is there a way to do this? Otherwise, we have to manually update UR prior to incorporating into our workflow because of potential database changes.
Our devops workflow is as follows: build and push docker container with UR to private docker registry -> initialize new instance of container and restore from exiting backup. If the new docker container is a newer version that the backup database schema, I'm not sure how to directly convert the database if there are any changes from the existing to the newer version. Any thoughts?
I don't know why do you store docker and database on one server, but in your case you will need to do the following:
There shouldn't be any issues when you update MYSQL version, as we never had issues with db schema on newer versions of MYSQL, because we try to support newest versions of MYSQL from release to release.
Let us know if you have more questions.
Stas, I don't understand your first comment because docker is merely a technology to support the UR service and separately, the database service which contains the UR database. The concern though is, for example, the version 5.1.4 is backed up and a new version is released, e.g., 5.1.5. The new version requires that the UR service container be built with 5.1.5 code. This container is then push to a private docker registry. The UR container and the database container are then reinitialized and the backup is restored automatically upon initialization (by placing the backup in the folder '/docker-entrypoint-initdb.d'. See also https://hub.docker.com/_/mysql. However, if the backup was created from veresion 5.1.4, then the concern is that any database schema changes between 5.1.4 and 5.1.5 may break the application because there wasn't a manual update done.
The only alternative that I see is to do many steps manually. That is, manually upload the new code to the 5.1.4 container, update UR to 5.1.5, perform the backup, then rebuild the container with 5.1.5, push the 5.1.5 container, and reinitialize a new instance using the 5.1.5 backup.
If there is mysql code that will apply any changes outside a manual update process, it will simplify the process and can be placed in '/docker-entrypoint-init.d' on the database container and will automatically update the backup created in a previous version to the current version.
Please let me know your thoughts.
The procedures on manual update are correct that you've described.
We don't have external mysql code. All updates are done using our update script where all mysql instructions are stored.
How long does a backup usually take? I manually made a backup vi the UI but the /work/backup directory does not update with a backup. There is another backup in the folder so it worked at some point. # of backups is set to 5. I removed the previous back and re-attempted to backup but nothing happened. Also, is there a log to verify the backup?
Let's organize a TeamViewer session to identify why backups are not created in your system.
Please let us know to email@example.com if you are available for the session.
Hi Lisa, My system/routers is not set up for team viewer and I prefer not to use that method because of security concerns. Instead, are there logs and where are they?
Please switch on errors displaying in configs/config.php, go to Administration - Backup, open XHR Network tab in the browser console, click Options at the bottom right of the Backup page, select Make Backup option and provide us server response from the browser console. Make sure to send the data to firstname.lastname@example.org as now we are talking inside the public topic.
Please let us know if everything is clear.
Replies have been locked on this page!