How to do a painless server Transfer?

[Mike2902]

Im just a novice so Is my logic here correct.

I had vbulleting installed on my current server by my current host. I will be leaving them in about 3 weeks for a new host. But the new host doesnt offer the vbulletin install.

Is this how I would do it.

Open account at new host. Pay vbulletin.com to install Vbulletin on my new server. Download my whole Public_html folder from my current host (2 gigs) to my hard drive. Upload the whole folder to my new public_html folder of my new host. Then when im about to switch servers, shut down my board. Do a backup to my local drive. And then do a restore to my new server and the board should be current right before shut down? Is this correct? Then of course switch DNS at godaddy

[Floris]

This is what I do.

I make sure my vBulletin is upgraded to the latest stable. And that I have run optimize and repair on my databases.

Then I create a new database on the new host and allow the IP of the old host to remote connect to it.

Then I close my old host forum, export the database and files. And transfer them over to the new host.

Then I import the backed up database into the new hosts's new empty database that I created earlier.

Then I upload the files and update includes/config.php to match the new database.

And then I test if the site works. Yay, works! Then I open the site on the new host.

And update the config.php file on the OLD host to point to the remote database on the new host.

Now the DNS settings can be changed.

If your members are getting the old domain/ip they will use the old files, but remote connect to the IP of the new host and still get the 'new' database.

If your members are getting the new domain/ip, they will use the new files, and the local database of course, and also get the 'new' stuff.

I consider the transfer completed, and delete the old database from the old host.

And 72 hours later I remove the old files from the old host and close that account.

This allows you to keep your forum online, but 'closed' for a short period of time.
And this allows you to have users who's DNS don't propagate within minutes, up to 72 hours to get to the new host. They won't even notice the downtime.

Mind you: If you use APC or other things, and the old/new host don't mix well. Turn this off temporary until the transfer is completed 100%

A trick: edit your HOSTS file (windows and mac and linux has this) to point the IP to the HOST that you need and flush your dns. This way if your ISP hasn't updated yet, you as admin at least can 'cheat' and go to the right IP for the host. PReventing some issues.

Simpler: Close the old board. export the data, import the data on the new host. And open it. Close the old host account. And for users who it doesn't work, it will work later (up to 72 hours on average).

[Mike2902]

This is what I do.

I make sure my vBulletin is upgraded to the latest stable. And that I have run optimize and repair on my databases.

Then I create a new database on the new host and allow the IP of the old host to remote connect to it.

Then I close my old host forum, export the database and files. And transfer them over to the new host.

Then I import the backed up database into the new hosts's new empty database that I created earlier.

Then I upload the files and update includes/config.php to match the new database.

And then I test if the site works. Yay, works! Then I open the site on the new host.

And update the config.php file on the OLD host to point to the remote database on the new host.

Now the DNS settings can be changed.

If your members are getting the old domain/ip they will use the old files, but remote connect to the IP of the new host and still get the 'new' database.

If your members are getting the new domain/ip, they will use the new files, and the local database of course, and also get the 'new' stuff.

I consider the transfer completed, and delete the old database from the old host.

And 72 hours later I remove the old files from the old host and close that account.

This allows you to keep your forum online, but 'closed' for a short period of time.
And this allows you to have users who's DNS don't propagate within minutes, up to 72 hours to get to the new host. They won't even notice the downtime.

Mind you: If you use APC or other things, and the old/new host don't mix well. Turn this off temporary until the transfer is completed 100%

A trick: edit your HOSTS file (windows and mac and linux has this) to point the IP to the HOST that you need and flush your dns. This way if your ISP hasn't updated yet, you as admin at least can 'cheat' and go to the right IP for the host. PReventing some issues.

Simpler: Close the old board. export the data, import the data on the new host. And open it. Close the old host account. And for users who it doesn't work, it will work later (up to 72 hours on average).

Great answer...I think I like the simple answer best, which is what I think my logic was close too.

[RobbieZ]

Then I create a new database on the new host and allow the IP of the old host to remote connect to it.

I have created a new database (basically a fresh install right?)

[Floris]

No, don't fresh install vb
just create a new database, not a new vbulletin.

[RobbieZ]

Aah Ok. So how do I do that?

[Floris]

You can ask your hosting provider on how to add another new empty database with a user and password to that user and GRANT ALL permissions, for you to use with php software.

if your host comes with cpanel, you can go to the mysql manager and manage it from there.

[RobbieZ]

Thanks Floris, I will get onto that now

[RobbieZ]

Ok so on my Cpanel>My SQL database I already have a database.

Should I create a new one? And call it anything I want?