<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<font size="2">Then go to the command-line and dump the database to a file before turning it off for that site. The command is simple:
<br />mysqldump --opt --flush-logs <span style="font-style: italic;">databasename</span> -u root -p > <span style="font-style: italic;">dumpfilename</span>
<br />
<br />Provide the MySQL database server root password and its done. So you can always dump the databases before working with the sites, to be sure the data isn't lost. In fact, it would be a good idea to dump every database on each server before starting any work. That way, you can restore them if you accidentally push the wrong button.
<br />
<br />
<br />Wait a second. In re-reading your e-mail, I'm puzzled. How could two sites show the same database name? I assume that means you had a site on the new server that was already assigned "site3_db". Then you cmuImported a new site that had been assigned that same name on another server. Is that right?
<br />
<br />That's why we don't use database names based on the site number assigned by the server. We use database names that match the site name - so a database for the site www.cnn.com would also be named www.cnn.com. That way - there is never a database name conflict.
<br />
<br />
<br />In your case, here's how I would suggest you do it:
<br />1) Backup the "site3_db" on the old server before cmuExporting the site. Use the above dump command and send it to a filename.
<br />2) <span style="font-weight: bold; text-decoration: underline;">Before</span> cmuExporting the site off the OLD server - TURN OFF MySQL database in the GUI. While that may delete the database on the old box - you've got a dump of it to a file.
<br />3) Copy that database dump file and the cmuExport to the new server.
<br />4) cmuImport the site on the new server.
<br />5) Turn ON database support for the newly imported site on the new server. When you turn on MySQL for the new site - you can give it any database name you wish (like site17_db or www.domain.tld).
<br />6) Now simply import that database dump from the old server to the new database - and you're set!
<br />
<br />This is why I don't like using the GUI for the MySQL, or for much else. Do it from the command-line and you don't run into these problems!! The only thing I really like the GUI for is MailWatch.
<br />
<br />I know, I know - not everyone is comfortable at the CL.
<br />
<br />
<br />
<br />Chuck
<br />
<br />
<br />
<br />
<br /><b>---------- Original Message
-----------</b>
<br />
From: "Uwe Spreckelmeyer" <us@itss24.com>
<br />
To: "'BlueOnyx General Mailing List'"
<blueonyx@mail.blueonyx.it>
<br />
Sent: Fri, 12 Aug 2011 18:16:14 +0200
<br />
Subject: [BlueOnyx:08090] Re: CMU
<br />
<br />> <font size="2" face="Arial" color="navy"><span style="font-size: 10pt; font-family: Arial; color: navy;">Hi
Chuck,<o:p /></span></font>
<br />> <font size="2" face="Arial" color="navy"><span style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;">the problem is a
bit
different. When you use the GUI to manage your sites you will see that
two
sites will have the same DB.
<o:p /></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;">For example: Old
site3
has site3_db and newly imported site3 from the other server, now site17 on
the
new server also has
site3_db.<o:p /></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;">When you disable
Mysql
for new site17, site3_db of site3 will be
destroyed.<o:p /></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;">You don´t have a
chance
to change the db_name within the
GUI.<o:p /></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;">Even if you give site17
a
new database like site17_db, anyone else who may manage the server
would
destroy site3_db by mistake when disabling mysql for
site17.<o:p /></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;">Uwe<o:p /></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"> <o:p /></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />> <font size="2" face="Arial" color="navy"><span lang="EN-GB" style="font-size: 10pt; font-family: Arial; color: navy;"><o:p>
</o:p></span></font>
<br />>
<br />> <font size="3" face="Times New Roman"><span style="font-size: 12pt;">
<hr size="2" align="center" width="100%" tabindex="-1" />
</span></font>
<br />> <b><font size="2" face="Tahoma"><span style="font-size: 10pt; font-family: Tahoma; font-weight: bold;">Von:</span></font></b><font size="2" face="Tahoma"><span style="font-size: 10pt; font-family: Tahoma;">
blueonyx-bounces@mail.blueonyx.it [mailto:blueonyx-bounces@mail.blueonyx.it]
<b><span style="font-weight: bold;">Im Auftrag von </span></b>Chuck Tetlow
<br />>
<b><span style="font-weight: bold;">Gesendet:</span></b> Freitag, 12. August
2011
17:24
<br />>
<b><span style="font-weight: bold;">An:</span></b> BlueOnyx General Mailing
List
<br />>
<b><span style="font-weight: bold;">Betreff:</span></b> [BlueOnyx:08089] Re:
CMU</span></font><o:p />
<br />> <font size="3" face="Times New Roman"><span style="font-size: 12pt;"><o:p>
</o:p></span></font>
<br />> <font size="3" face="Times New Roman"><span style="font-size: 12pt;">>From my experience using cmuExport/cmuImport - it doesn't do
a
thing for the MySQL databases. I've always had to backup/restore
those
manually, outside the CMU process. Admittedly, I haven't had to use
CMU
in the last 12 months or so. But before that - I got a LOT of
experience
with CMU.
<br />>
<br />>
So simply restore the database dump to a different database name on the
new
server. Dump the database on the old server to a file
like
"site3_db.dump". Copy that to the new server and use
something
like "cat site3_db.dump | mysql -u root -p <i><span style="font-style: italic;">newdatabasename</span></i>". Provide the root MySQL
password
and a name for that moved site's database - and you're all set. No
damage
to the current site3's database.
<br />>
<br />>
Chuck
<br />>
<br />>
P.S. - You might have to create that new database before restoring the dump
to
it. I don't remember. But that's easily done. Just create
the
empty database first - either at the command line or in phpMyAdmin.
<br />>
<br />>
</span></font><b><font size="2"><span style="font-size: 10pt; font-weight: bold;">----------
Original Message -----------</span></font></b><font size="2"><span style="font-size: 10pt;">
<br />>
From: "Uwe Spreckelmeyer" <us@itss24.com>
<br />>
To: "'BlueOnyx General Mailing List'" <blueonyx@blueonyx.it>
<br />>
Sent: Fri, 12 Aug 2011 10:58:30 +0200
<br />>
Subject: [BlueOnyx:08086] CMU
<br />>
<br />>
> When you cmu-export a site -i.e. site3 - and cmu - import it to another
<br />>
> Server it will become i.e. site17. The sites database name is
still
site3_db
<br />>
> on the new server even though this db is already in use by site3 of this
<br />>
> server.
<br />>
>
<br />>
> What can be done to prevent destruction of site3_db on the new
server
using
<br />>
> the GUI (Websettings of site, MySQL user and database,
enable/disable).
<br />>
> Is it possible to disable Mysql for a site without destroying the db
by
the
<br />>
> GUI?
<br />>
>
<br />>
> Any hint?
<br />>
>
<br />>
> Uwe Spreckelmeyer
<br />>
>
<br />>
> _______________________________________________
<br />>
> Blueonyx mailing list
<br />>
> Blueonyx@mail.blueonyx.it
<br />>
> <a target="_blank" href="http://mail.blueonyx.it/mailman/listinfo/blueonyx">http://mail.blueonyx.it/mailman/listinfo/blueonyx</a>
<br />>
<b><span style="font-weight: bold;">------- End of Original Message
-------</span></b>
</span></font><o:p />
<br /><b>------- End of Original Message
-------</b>
<br />
</font>
</BODY>
</HTML>