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
Hi Scott,
I'm trying to install the new 5107R distro on XenServer and am getting
a base SL install instead. It seems the install scripts for BlueOnyx
do not run but I'm not sure.
Anyone have a similar experience?
When booting off the CD, the Linux kernel on the CD is called with the
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
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
Then go to the command-line and dump the database to a file before turning it
off for that site. The command is simple:
mysqldump --opt --flush-logs databasename -u root -p dumpfilename
Provide the MySQL database server root password and its done. So you can
always dump the databases before
Yes I agreeI am not yet embracing the GUI for MySQL because of issues
similar to this. However, having said that, there are still some challenges
over all with CMU. For example, if you have made custom modifications to
the siteXX.include this does not copy over. I would like to see that the
On Aug 11, 2011, at 9:19 PM, Michael Stauber wrote:
I just rolled up a new 5107R ISO image:
http://devel.blueonyx.it/pub/BlueOnyx/ISO/BlueOnyx-5107R-SL-6.1-20110811.iso
I'd need some testers for it to check for the following:
- Does it install on boxes with disks 1TB?
- Does it
