Help with upgrade plan

[Wilfred1]

I have v3.8 installed with around 5,000 users, 15,000 threads and 100,000 posts.

I also have vbAdvanced CMPS, 11 instances of vbDynamics and vbAdvanced Links.

Also Photoplog, vbTube and many mods from vb.org

What I thought was the best way to upgrade was:
- wait for v4 compliant updates are available on all the mods and apps
- develop a completely new site on a spare development domain with the db on the same server as the live db
- delete all the test entries on the development domain
- close live site down
- move all live site files to another spare domain for backup
- move development domain files to live domain
- use impex to import the data from old live site db to development db which then becomes the live db
- manually move the data for the addons like vbAdvanced etc from old live db to new db

Is this the best way to do it or is there a better way when you have so many addons - thanks for your help in this emerging nightmare

[Lynne]

Do NOT, I repeat, DO NOT use Impex for an upgrade! You should never ever EVER use Impex for upgrading. And, besides that, right now Impex can not import to vB4 - at the least, you will lose all your attachments.

There are several threads about upgrade strategies over on vb.com. You might want to go take a look at them.

[Wilfred1]

Thanks Lynne - it isn't an upgrade as such as I would simply be using impex as a tool to move the data from my backup 3.8 db to a brand new clean install of v4

[Lynne]

But you will be losing some of that data by doing it the way you are talking about.

[Wilfred1]

Thanks Lynne - I won't even consider impex now so a big thanks.

This is going to be a big mess, my site has over 500 tables in the db and I can see me having bits of data left here and there not to mention the down time I will have which isn't good in a competitive environment.

I will have to create the entire site in a test environment then when going live do all the upgrades again and manually copy and paste every setting, every template change, every graphic, every css change, etc etc etc and that will be not only for vb but for every addon, every 3rd party app, every mod etc - and users won't be happy.

Not everyone just has a website of a vb forum, but like me vb is just a component yet integral backbone of an "entire website" that has been built up as a complete solution having everything integrated using a lot of vb functionality.

[Lynne]

I don't know what you mean about copying every template change or css change, etc. Just export your modified style from your test site and after you do the upgrade on your live site, you import the style and viola! You have your new templates/css/colors all installed. I've done that for every one of my upgrades.

[Carnage]

Heres what i suggest you do (and is what i'm doing for my board on a MUCH MUCH bigger scale (1.2million posts 100k threads 30k members)

For your live board
1. remove any products, styles and other superfluous stuff from your installation. For me this involved removing some test skins; uninstalling a few disabled products; cleaning some old db tables out of the database and removing old files from the install directory. (the check for suspect file versions helped with the last one)
2. Make announcements to your staff and members about the upgrade to vb4

For your test (1) board:
1. Create a test board, on this install a CLEAN copy of vbulletin 4.
2. Find versions of all the plugins/products you wish to keep and install them on this board (ensure they work)
3. Convert your templates and styles on this new board .
4. You basically need to make this board identical in functionality to your main board.
5. Invite staff and some select members over to this test install to ensure its working correctly.

For test board (2):
1. Make a copy of your database and file system from your live board. (it may be necessary to take the board offline while you do this)
2. DOUBLE CHECK that this is a copy and its pointing to a different database.
3. Perform a test upgrade to vb4 on this test copy.
4. Import styles and products that you tested on test board (1).
5. Invite staff + select members to try and break this test board as well.

Repeat the above as many times as needed until your test (2) board is upgraded successfully.

On your live board:
1. Shut down board
2. Make a new database and file system backup.
3. Upgrade to vb4
4. import products and styles from the working test board (2)
5. Reopen your board.

After its back up, remove your two test boards.

[Wilfred1]

Brilliant Carnage - if you were around here I would buy you a drink - thanks mate!

[wacodep]

Thanks Lynne - it isn't an upgrade as such as I would simply be using impex as a tool to move the data from my backup 3.8 db to a brand new clean install of v4This has been discussed ad naseum over at vbulletin.com. Impex has not and is not designed to do this, nor is it supported when used for a version upgrade of vBulletin.

[Wilfred1]

Impex is out of the plan - I just thought it may be a way to just transfer the data - that is all.

My plan now using Live, Test1 and Test2 sites is:
Install v4 clean on Test1
Install vb4 clean on Test2
Develop vb4 on Test1 adding the mods, changing templates, changing styles etc
As each one is tested and working ok add it to Test2 (gives me a clean install with the final results of testing on Test1)
Create a folder structure on PC so the files of any new mods etc can be added to a default folder structure which will make it quicker to upload when going live
Once finished delete everything in Test1 and copy everything on Test2 to Test1
Invite staff and power users to test the site in Test1
Make any changes to Test1 and test again - if ok make the same changes to Test2
When everything ok delete Test1 again and copy Live to Test1
Export from Test2 Styles and Products
Disable addons in config file on Test1 and perform upgrade
Import Styles and Products
Upgrade existing addons
Upload files from PC folder structure for new addons
Get staff and power users to test Test1
Loop from #8 until good to go (updating Test2 when necessary)
Backup Live files and db
Perform quick #8 to #15 on Live
Delete Test1
Delete Test2 after Live is all running smoothlyI think this is the way to go however I am not sure about the existing addons like vbDynanics, vbAdvanced, vbTube, existing mods etc that I have got their updating sequence right in the above.

Thanks for your help

[SonicGT]

Heres what i suggest you do (and is what i'm doing for my board on a MUCH MUCH bigger scale (1.2million posts 100k threads 30k members)

For your live board
1. remove any products, styles and other superfluous stuff from your installation. For me this involved removing some test skins; uninstalling a few disabled products; cleaning some old db tables out of the database and removing old files from the install directory. (the check for suspect file versions helped with the last one)
2. Make announcements to your staff and members about the upgrade to vb4

For your test (1) board:
1. Create a test board, on this install a CLEAN copy of vbulletin 4.
2. Find versions of all the plugins/products you wish to keep and install them on this board (ensure they work)
3. Convert your templates and styles on this new board .
4. You basically need to make this board identical in functionality to your main board.
5. Invite staff and some select members over to this test install to ensure its working correctly.

For test board (2):
1. Make a copy of your database and file system from your live board. (it may be necessary to take the board offline while you do this)
2. DOUBLE CHECK that this is a copy and its pointing to a different database.
3. Perform a test upgrade to vb4 on this test copy.
4. Import styles and products that you tested on test board (1).
5. Invite staff + select members to try and break this test board as well.

Repeat the above as many times as needed until your test (2) board is upgraded successfully.

On your live board:
1. Shut down board
2. Make a new database and file system backup.
3. Upgrade to vb4
4. import products and styles from the working test board (2)
5. Reopen your board.

After its back up, remove your two test boards.


This is the exact strategy I'm using for my site. I'm coming up on step 2 of doing the test upgrade myself, still waiting on a few mods before I do though.