Upgrading to new server

[FZ1OA]

I am running VB 2.3.0 on a dedicated server. We have out grown this server and I am currently in the process of moving the site to a new server. I would like to install a fresh copy of VB 3.5 on the new server and import the 2.3 db as opposed to installing 2.xx on the new server and then upgrading to 3.5. My question is can I do this and if I can could someone be kind enough to point me to a HOWTO on this type of migration?

TIA
Steve

[organik81]

- Make a full backup file
- Create a new account in the new server with the same username and password like the old server.
- Move and restore the full backup file into the new server.
- Create a new database and install default vB 3.5.0
- Integrate the ImpEx transferr script into the new 3.5.0 forum.
- Transfer the data (users, forums, threads, posts etc..) from vB 2.3.0 into the new vB 3.5.0 using ImpEx..

http://www.vbulletin.com/docs/html/impex

[Marco van Herwaarden]

No need to use ImpEx afaik. From the vB3.5 readme:

Upgrading from vBulletin 2 to vBulletin 3

The vBulletin 2 to vBulletin 3 upgrade script will upgrade your vBulletin 2 installation to vBulletin 3. You will not lose any data. Your vB2 styles will not be usable in vB3, but they will not be deleted, they will be kept in the database for your reference.
To upgrade, to vBulletin 3 your existing installation must be running at least vBulletin 2.2.9 or higher.
If you want to upgrade your forums to vBulletin 3 Release Candidate 1, you should first close your board via the vBulletin 2 admin control panel, and then make a complete back-up your database using the following command from the system command line:
mysqldump --opt -uusername -p databasename > databasename.sql(Where username is your MySQL username and databasename is the name of your database)
When your database backup is complete you should back up your existing vBulletin 2 PHP files and images, just in case you want to revert back to vBulletin 2 for whatever reason.
Before you proceed, you should run the Database Conflict Detection Script to make sure that the upgrade script will not fail due to any differences from the default vBulletin 2 installation in your database. If any conflicts are detected, you should resolve them before proceeding with the upgrade.
Next, unzip the vBulletin zip file you downloaded from the members' area to your hard disk and then open the upload/includes folder. In this you will find config.php.new. You should rename this to config.php and then open it in a text editor.
The config.php file is commented throughout, so you should be able to work out what values to enter for the variables yourself. When you have finished, save the file back into the upload/includes/ folder as config.php.
Next, you should delete all vBulletin 2 files, including PHP, CSS and style files, along with any images. You should then upload the contents of the 'upload' folder to your server.
When the upload is complete, point your browser at http://www.domain.com/forum/install/upgrade.php where www.domain.com/forum/ is the URL of your vBulletin files.
Please note that we have found that due to the large number of pages that the upgrade script loads, and the speed at which it loads them, certain browser plug-ins can cause the browser to crash out for various reasons. The Google Toolbar is one such plug-in, and we have seen browsers crashing due to the amount of browsing statistics being sent back to Google. If you have plug-ins of this kind installed, turn them off while running the upgrade script.
Running upgrade.php will automatically load the correct upgrade script and present you with a message, which you should read carefully. When you have finished reading, click the 'Next Step' button at the bottom of the page to start the upgrade process. When each page has completed its processing, it will either give you a 'Next Step' button to click, or automatically load the next page, depending on the type of job the page in question is doing.
Some steps will take quite a while to run, especially on large boards with large numbers of posts/threads. Please be patient and allow the script to complete.
If your browser crashes during the upgrade, or if you are on dial-up and your connection is dropped (etc.) then to restart the upgrade script simply point your browser at install/upgrade.php again and it will work out where you got to in the process and restart the process at the appropriate step.
For the most part, you do not need to do anything except click the 'Next Step' buttons to keep the upgrade script running. However, there are a few steps where the script will require your input to continue. One of these is the step where the script asks you to tell it which of your usergroups you use for 'Banned' users. It is important to select these carefully in order to make the enhanced vBulletin 3 banning system work. Additionally, towards the end of the upgrade, as the cookie and user format is converted from vB2 format to vB3 format, you maybe be required to log-in again a few times. This is the expected behavior.
Note: There are several upgrade scripts that need to be run. You do not need to determine which you need to run; they will be determined automatically. Simply click "next step" or "proceed" until you are redirected to your admin control panel.
When the scripts are complete, it will tell you to delete some files, and then redirect you to the Admin Control Panel. You should log in to this and proceed to the Import and Maintenance section of the control panel, where you should run the Rebuild Search Index and Rebuild Statistics controls. Both of these functions will take a quite a long time to run on larger boards.
For a complete description of how to upgrade from a previous version of vBulletin 3 to the latest version, see the upgrade section and specifically the upgrading from vBulletin 2 section of the vBulletin 3 Manual.

Steps to take:
- Backup database and restore on new host
- Install latest vB2, and upgrade to it. (since you're running 2.3.0 this is probably not needed, try without this step first)
- Remove all files again
- Upload 3.5 and edit config file
- Run upgrade

[organik81]

No need to use ImpEx afaik. From the vB3.5 readme:

Just only my choise.. I like ImpEx..

[Marco van Herwaarden]

I also like using ImpEx, but only if it is needed: Migrating from other systems or cleaning a hacked vB database.

For a 'simple' upgrade, the upgrade scripts have been invented.

[FZ1OA]

Thanks Guys

I was trying not to install VB2xx on the new server but I guess that is the best way to do it.

Steve