I was going through upgrade process of mysql server. It is mentioned that to upgrade from 4.1 to 5.5 we need to upgrade step by step like first to 5.0,5.1 ...5.4 and then 5.5.
I have some questions :
What if we directly upgrade from 4.1 to 5.5. What might get effected? functionality or problem related to upgrading
Chances to loose data ? Even though I'll take backup using 'mysqldump --all-data-base' option.
Lets say, I have two database. I'll take only two database backup. I'll install latest version of mysql 5.7 and load two database back. What are chances to loose data or get corrupted ?
I'm curious to know this. If anybody tried? Because I need to do upgrade in live server.
Is there any step by step document which tells exact steps to upgrade from 4.1 to 5.5 in linux server
Major new features added to MySQL 5.0 and 5.1 that may not work/won't work in 4.x can be located here:
MySQL 5.0 - http://dev.mysql.com/doc/refman/5.0/en/mysql-nutshell.html
MySQL 5.1 - http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html
Related
I need to update an old forum made in phpBB from version 3.0.11 to the new / stable version 3.2.2.
It is the first time that I put my hand at phpBB.
Making an update step by step is complicated: move from 3.0.11 to 3.0.14 ... from 3.0.14 to 3.1.x ... and from 3.1.x to 3.2.2.
So I thought: can I make a clean install of 3.2.2 and import everything I need (posts / forum / users / ALLINEED)?
Do you know any plugins that do this? maybe phpBB itself does it? Or maybe I just need to export the tables from mysql?
can you advise me something?
thank you
There is no plugin to do it, but there is a process to upgrade from 3.0 to 3.2. Your forum will be as clean as a fresh install.
The more secured solution is to begin by upgrading from 3.0.11 to 3.0.14 for security reasons.
When you can stop your forum during one or two hours, stop it and upgrade directly from 3.0 to 3.2. You don’t need to upgrade to 3.1 then to 3.2.
All explanations are provided in upgrade documentation from 3.0 to 3.2
Do not forget any step! After step3, I advise you to restore the 3.0.11 forum on a local machine or another server to be sure that your backup files are not corrupted. (Yes, it could happen during a download.)
I did it a lot of time. It works fine. One hour to do it cautiously and slowly (+ download and upload time).
Why is 3.0.* ok but 3.2 version has to specifically be 3.2.6? Is 3.2.1 ok?
Any version is fine when doing a fresh install with parse-server but from parse.com you will not be able to move to 3.2. Seems that migration tool wont allow it.
I moved to 3.0 and from there did backup/restore to 3.2.
However i would always strongly suggest that one in general runs the latest version if you can.
I do know that all test on mongodb 3.2.6 are passing including geo queries.
I have a production mongoDB 2.0 server running on a single machine. I need to upgrade it to the latest version. Would it be possible to just restore the dump from old server into the new server? Or would I have to do it one upgrade at a time?
No, in the general case, absolutely not. Best practice is to upgrade through each major version, following the upgrade instructions in each set of release notes. You can do this without downtime if you are running a replica set, at least from 2.4 -> 3.0 (I'm not as familiar with 2.0 and 2.2 since they are ancient).
In my old server, Postgresql 9.1 is installed and it contains a large scale of data. Now, I have got a new server and installed the latest version of Postgresql which is 9.2. I want to migrate the whole data from the old server to the new server. I looked at Postgresql documentation and there is a command to upgrade but it seems to explain upgrading in the same server. How could I approach for this matter?
I would be very careful about changing both hardware and major versions of PostgreSQL at the same time. If something goes wrong, it will greatly complicate figuring out what the problem is.
I do this as a two step process, first restore the database to the new server as the same version, then run pg_upgrade. That means you have to have both versions of the software installed on the new server simultaneously.
Dump the database with pg_dump and load it at the new server with psql. I think pg_upgrade is better as an in place procedure.
Is there a list anywhere or best practice instructions for update firebird databases from one version to another (in my case 2.1.3 to 2.5.2)?
I have seen backup and restore mentioned. I have updated from 1.5 to 2.1 in the past but that just worked i.e. I just installed the new firebird version, however I aware that this was probably just luck.
Regards
The Firebird 2.5.2 release notes has a section on compatibility issues that you need to be aware of when upgrading. Also the Firebird install directory contains additional info on upgrading in misc/upgrade/metadata/metadata_charset.txt. If your database has the incorrect metadata charset things might break (but AFAIK they would have been broken under Firebird 2.1 as well).
Technically you can upgrade to 2.5 without a backup and restore cycle on your database, but that means the On Disk Structure (ODS) of the database isn't upgraded to ODS 11.2, which could mean that you can't actually use some of the new features (or: performance improvements) introduced with the newer version. This could be worse if you are actually still on ODS 10.1 from Firebird 1.5.