Restoring an old backup Restoring an old backup
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Restoring an old backup

Started by Hercules24, November 21, 2006, 02:00:54 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

Hercules24

November 21, 2006, 02:00:54 AM Last Edit: November 24, 2006, 05:48:35 AM by GauGau
Hi, I wonder if I ever have to reinstall a huge picture gallery that first started as CPG_133, but has been updated to 1410 I will get in trouble.
I remember once switching hosts when I had 133, and because back then 135 was already released, I had to manually install 133 first with the new host, then run a back up, and then upgrade to 135.
But since 141 there have been a lot of changes in the number of dbase tables, I wonder if it's still possible to get a backup working.
CPG 1.4.10 runs perfect now, but all my dbase tables are still named cpg133_albums etc.
So will I be able to get this back up restored if for what reason I have to start on a different server?
Thanks for the advice.

Joachim Müller

#1
November 21, 2006, 05:26:36 AM
There's no limit to the size of the database - you can backup and restore any size of database. The only issue you might run into is some tools like phpMyAdmin running into timeouts when backing up or restoring huge databases. To circumvent this, either use the shell if you have access to it. If you don't have it, use mySqlDumper.

Hercules24

#2
November 21, 2006, 03:21:48 PM
Thanks Gaugau, I ment that will a newly installed CPG1410 "understand" an backup restore where the tables have the prefix 133?
I remember back then I would get like 13 empty tables with 135 prefix and after running a backup also 13 filled tables with prefix 133 but the new CPG only "saw" the empty 135 tables because it was looking for tables with the 135 prefix instead of 133.

Joachim Müller

#3
November 21, 2006, 05:47:55 PM
No, it will not "understand". Edit the dump with a text editor, replacing the prefix.

Hercules24

#4
November 23, 2006, 12:19:35 AM
Ok thanks Gaugau, I don't no much about technicalities, but I think I can use PHP designer 2005 as an editor.
There's like 200 times "133 references" like cpg133_albums, cpg133_banned, cpg133_bridge etc.
In what exactly should I change the prefix when using this backup in a freshly installed 1.4.10 and maybe in a future 1.4.11?

Nibbler

#5
November 23, 2006, 12:45:40 AM
The prefix in the database has to match the prefix in include/config.inc.php. Change one or the other. That's all there is to it.

Hercules24

#6
November 24, 2006, 12:13:37 AM
Thanks Nibbler,
It's a lot easier to change only 1 prefix in the config.inc.php.
This way it's even possible to change the Mysql dbase name I see.
Problem solved!
Print
Go Up Pages1
User actions