By wellsy on

I have now succeeded in doing this once....after much frustrating problems ( http://drupal.org/node/40646 ) and ( http://drupal.org/node/40219 )

After succeeding and making some good ground on adding new functionality to my 4.6.3 live site after testing here. That database was very successfully nuked by the update.php included with 4.7.0 beta1 and was then useless for the 4.6.3 testarea. It was eventually deleted from the server. That little hitch has cost me bigtime in absolute wasted time.

In my continuing attempts to try to setup a test area to both:-
run 4.6.3 for new feature testing
run 4.7.0 betaX for bug testing

I have tried to do this again twice now with two successive failures with a database that is around 11.2mb. It seems to me that even attempting to move a 4.6.3 site is fraught with problems. The site just does not work with a new database.

Visit http://www.orchidauction.biz/interactive/ where you will see problems exist obviously

Warning: mysql_connect(): Access denied for user '17Dec2005'@'192.168.50.2' (using password: YES) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive/includes/database.mysql.inc on line 31
Access denied for user '17Dec2005'@'192.168.50.2' (using password: YES)

I have searched these forums and have not yet found a useful solution.

So. Can anyone outline a method which is reliable to first move the working 4.6.3 installation to a new server.
I propose that two databases be created simultaneously on the new server.

One to try to update to 4.7.0 betaX
The other to continue testing of new features for my live site under 4.6.3

It seems to me that at this point in time this community needs this functionality very badly to enable testing the new beta releases.

If you read here http://drupal.org/node/40383 (point 6 of Dries Tips)
That is what I am trying to do......well I am wasting a lot of time trying to do that without any useful results at this stage.

⋅ Categories: Drupal 4.6.x

Comments

jbrauer’s picture

jbrauer commented

What I've typically done on 4.6 is to create a copy of the database on the same server so I end up with drupal and drupaltest as two databases. Using mysql there are a few ways I've done it - primarily with phpMyAdmin or Navicat (the latter is extremely worth the investment to anyone doing anything more than a single site on a single server).

Once I have the second database setup I'll make a new site in the sites folder. Again, a copy of the site. With a few tweaks to apache I now have www.example.com and test.example.com in the same code-base running against two databases. With that all working a copy of the code into separate directories (again a copy) and change the DocumentRoot for test in Apache and we're off to the races.

Then I can either upgrade over the top of test and see how things go, or create a third copy of everything and point to it from a fresh code install.

The main problem I've seen with this from time to time (with 20-60MB databases) is a difference in text encoding that sometimes munges quotes and apostrophes.

With errors like the one here I often will change the values in the settings.php file, even if I'm sure they are right, to make sure that the error changes along with it. More than once I've gotten balled up thinking I was using test.example.com but was instead using default etc. By seeing the user name change in the error I can be certain I'm looking at the right files.

--

wellsy’s picture

wellsy commented

would you mind detailing how to go about duplicating the database on the same server using phpMyAdmin.

Also is that possible across the net to another server?

Thanks in advance!

wellsy

orchidsonline.com.au

jbrauer’s picture

jbrauer commented

With PhpMyAdmin you can go into the table, choose Operations, and then have the option of moving or copying the table into another database. This is a long and slow process. Or you can export the database as a SQL file and re-import it into your new database (depending upon the size of databases this can be difficult if your server limits the size of submitted forms).

For moving across servers I highly recommend Navicat. Here's a brief blurb on it. It is simply a divine tool for managing MySQL databases. The 30-Day demo should let you see what it can do in terms of moving your databases.

------------------
Adding Understanding

--

wellsy’s picture

wellsy commented

I started another post and the solution with BigDump worked awesomely well ( http://drupal.org/node/42977 ) for me.

EDIT: I recommend the use of BigDump solution to all who may be reading this.

Not just after a big meal either.

wellsy

orchidsonline.com.au