Timeline for Mysql v5.1/RHEL6 dump to MariaDB v10.3/RHEL7 restore process
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 1, 2021 at 13:26 | comment | added | user2723901 | Thanks, danblack! | |
| Jun 29, 2021 at 9:55 | comment | added | danblack | mysql_upgrade is idpotent, running subsequent times is harmess. As you are probably migrating subsequent (all) database in a logical mysqldump form then mysql_update isn't required as its written around ensuring in place update is correct. | |
| Jun 28, 2021 at 13:21 | comment | added | user2723901 | Thanks; I'm in a large corporate environment with controlled access to available repos; RHEL8 not available yet. RHEL7 is at least much later than RHEL6. Since we will be moving one DB at a time over months, can you run the update process on a per DB basis? | |
| Jun 26, 2021 at 0:04 | history | answered | danblack | CC BY-SA 4.0 |