9) Now log in to your WordPress site and make sure it is still working just draft a post if it dont save then reset permissions if this dont work log in to Cpanel and do a repair on the DB some times you have to do this 3 times to get the site working again
10) Remove old DB
rm -rf /var/lib/mysql/blogline_db1234
11) Also remove the tar file in /backupdrive/mysql/blogline_db1234.tar.gz
rm -rf /backupdrive/mysql/blogline_db1234.tar.gz
Now this set up works for moving WordPress but it dont work for Multi DB any ideas and toughts would be welcom
9) Now log in to your WordPress site and make sure it is still working just draft a post if it dont save then reset permissions if this dont work log in to Cpanel and do a repair on the DB some times you have to do this 3 times to get the site working again
10) Remove old DB
rm -rf /var/lib/mysql/blogline_db1234
11) Also remove the tar file in /backupdrive/mysql/blogline_db1234.tar.gz
rm -rf /backupdrive/mysql/blogline_db1234.tar.gz
Now this set up works for moving WordPress but it dont work for Multi DB any ideas and toughts would be welcom
9603 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Sales & Support Pro
—
19th January 2012 (4 months ago)
#
No idea I'm afraid. All I can think is that simply moving the DB files is missing out some processing that MySQL would do to recognise the database properly...
According to Wordpress: http://codex.wordpress.org/Moving_WordPress#Moving_WordPress_Multisite (due to the SOPA protests you may need to scroll to the bottom of the page and click "Continue to wordpress.org") this can still be done, but will require modifying the databases themselves to reference the new location(s) on the server. As such, before making any attempts to move the databases you would want to create backups of them. It may honestly be easier/better to only move the single DB sites and leave the multi DB sites in-tact.
1162 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Member par excellence
—
25th January 2012 (3 months ago)
#
@Phil After a lot of reading up on DBs it looks like the way MultiDB works it has ref to the location of the dbs on the server so i was given a idea by the server admin at Softlayer
Again this is only a idea i have not tested it so i wont know if it will work
While you cannot actually increase the size of /var you can move the contents of the directory elsewhere and then create a sybolic link from the new location to /var/lib/mysql/. This will cause mysql to follow the link to the new directory; This can be anywhere you like including a second drive!
As with anything else you will want to ensure you have backups of the databases before you move them.
This will require that _everything_ is moved out of /var/lib/mysql.
I can say i did this on my last server moving the hole /var/lib/mysql to a lets call it a back up drive and then just added the sim link in the /var/lib/mysql and it did work on the old server so i think SoftLayers idea will work on the new server, The only problem is to move the hole dir over to a new drive will have a lot of customers unhappy as the server will be down for a wile :(
Again i am just posting my findings here so i can help any one else out there
Responses (5)
Sales & Support Pro — 18th January 2012 (4 months ago) #
Hiya!
Is there any reason why you're not just using mysqldump?
Thanks,
Phil
Member par excellence — 18th January 2012 (4 months ago) #
@Phil mysqldump i did not see the point as i was only trying to move the DB from one drive to a norther
Any thoughts why this not worked for multi db ?
Sales & Support Pro — 19th January 2012 (4 months ago) #
No idea I'm afraid. All I can think is that simply moving the DB files is missing out some processing that MySQL would do to recognise the database properly...
Member par excellence — 19th January 2012 (4 months ago) #
@Phil Just a update from Soft Layer
Employee Response - 2012-Jan-18 17:24 (GMT+0200) [Update 6]
According to Wordpress: http://codex.wordpress.org/Moving_WordPress#Moving_WordPress_Multisite (due to the SOPA protests you may need to scroll to the bottom of the page and click "Continue to wordpress.org") this can still be done, but will require modifying the databases themselves to reference the new location(s) on the server. As such, before making any attempts to move the databases you would want to create backups of them. It may honestly be easier/better to only move the single DB sites and leave the multi DB sites in-tact.
Please let me know if you have any questions.
Thank you for choosing Softlayer,
William B
Customer Technical Support
http://www.softlayer.com
Member par excellence — 25th January 2012 (3 months ago) #
@Phil After a lot of reading up on DBs it looks like the way MultiDB works it has ref to the location of the dbs on the server so i was given a idea by the server admin at Softlayer
Again this is only a idea i have not tested it so i wont know if it will work
Employee Response - 2012-Jan-18 18:45 (GMT+0200) [Update 8]
While you cannot actually increase the size of /var you can move the contents of the directory elsewhere and then create a sybolic link from the new location to /var/lib/mysql/. This will cause mysql to follow the link to the new directory; This can be anywhere you like including a second drive!
For example:
mv -v /var/lib/mysql/* /some/new/directory/
ln -s /some/new/directory/ /var/lib/mysql/
As with anything else you will want to ensure you have backups of the databases before you move them.
This will require that _everything_ is moved out of /var/lib/mysql.
I can say i did this on my last server moving the hole /var/lib/mysql to a lets call it a back up drive and then just added the sim link in the /var/lib/mysql and it did work on the old server so i think SoftLayers idea will work on the new server, The only problem is to move the hole dir over to a new drive will have a lot of customers unhappy as the server will be down for a wile :(
Again i am just posting my findings here so i can help any one else out there
Become a member