Mailing List ecs-isp@2rosenthals.com Archived Message #523

From: "Massimo S." <ecs-isp@2rosenthals.com> Full Headers
Undecoded message
Subject: Re: [eCS-ISP] mysql upgrade 5.1.73 -> 5.6.51
Date: Tue, 8 Aug 2023 23:34:23 +0200
To: eCS ISP Mailing List <ecs-isp@2rosenthals.com>



Il 08/08/2023 19:47, Steven Levine ha scritto:
In <list-7601707@2rosenthals.com>, on 08/08/23
    at 09:07 AM, "Massimo S." <ecs-isp@2rosenthals.com> said:


Hi,

is there any other way?

There are always other ways.  Some are more or less work than others.
Some are more or less error prone than others.

i don't have perl running on the VM
i'm not testing 5.6.51 on the VM db machine, that only runs mysql

You can always create a temporary VM just to do the upgrade and then copy
the files to the production machine once you are satisfied they are
production ready.  This is how most of us work to avoid unexpectedly
taking down a production machine.

i'm trying mysql 5.6.51 on the 2ndary mx where i've low load and no mysql installed/running
so it's already on another VM

the 5.1.73 DB machine dump all DBs each night during bkups

That's like saying Tuesday occurs once a week.  It does not tell mean
anything I don't already know.  Now, if you told us you never backed up
the DBs, that would be unexpected.

How are you dumping the DB, using what mysql commands?

Steven

mysqldump -u myuser -pmypwd --opt --all-databases -r x:\BKUP\db\backup_alldb.sql

i also do a zip of the entire \mysql (with mysql not running of course)
since i've VMs on 4th gen NVMe storage all these bkups take just some seconds

massimo

Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster