[BlueOnyx:08090] Re: CMU

[Uwe Spreckelmeyer]

Hi Chuck,

 

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. 

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.

 

When you disable Mysql for new site17, site3_db of site3 will be destroyed.

 

You don´t have a chance to change the db_name within the GUI.

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.

 

Uwe

 

 

 

 

 

 

 

 

 

 

  _____  

Von: blueonyx-bounces at mail.blueonyx.it
[mailto:blueonyx-bounces at mail.blueonyx.it] Im Auftrag von Chuck Tetlow
Gesendet: Freitag, 12. August 2011 17:24
An: BlueOnyx General Mailing List
Betreff: [BlueOnyx:08089] Re: CMU

 

>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. 

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 newdatabasename".  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. 


Chuck 


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. 



---------- Original Message ----------- 
From: "Uwe Spreckelmeyer" <us at itss24.com> 
To: "'BlueOnyx General Mailing List'" <blueonyx at blueonyx.it> 
Sent: Fri, 12 Aug 2011 10:58:30 +0200 
Subject: [BlueOnyx:08086]  CMU 

> When you cmu-export a site -i.e. site3 - and cmu - import it to another 
> Server it will become i.e. site17. The sites database name is still
site3_db 
> on the new server even though this db is already in use by site3 of this 
> server. 
> 
> What can be done to prevent destruction of site3_db on the new server
using 
> the GUI  (Websettings of site, MySQL user and database, enable/disable). 
> Is it possible to disable Mysql for a site without destroying the db by
the 
> GUI? 
> 
> Any hint? 
> 
> Uwe Spreckelmeyer 
> 
> _______________________________________________ 
> Blueonyx mailing list 
> Blueonyx at mail.blueonyx.it 
> http://mail.blueonyx.it/mailman/listinfo/blueonyx 
------- End of Original Message ------- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20110812/2440c16e/attachment.html>