upgrading a huge vb 2.2.0 to VB3

[por4x4]

I have a very large VB 2.2.0 forum with several custom hacks (subscription stuff, etc) that I am planning on upgrading to VB3 in the near future. The forum is 26,000+ members, and has 1.6 million+ posts... I understand I need to upgrade to the latest 2.x version before going to VB3. I just wanted to know from others with LARGE boards what kind of headaches they encountered when upgrading. I am not looking forward to this!

[Zachery]

you need to upgrade to at least 2.2.9 so this will save you some trouble.

how big is your database?

the biggest headache is the upgrade from 2.2.X+ to beta 3 as it has the most step's after that it gets much ezier

[por4x4]

Yikes, I just noticed that it says not to post VB questions here... Sorry. :(

[por4x4]

how big is your database?


It's 5.5 GIGS.

[Zachery]

It's 5.5 GIGS.
well damn...


i can refer you to vbulletin.com search for large and upgrade you should find the topic there

[por4x4]

I was going to post my question there, but for some damn reason my account won't allow me to post over there. I've got an email in to VB about it, but I figured I'd ask here in the meantime... Thanks anyhow. ;)

[Serge]

Maybe with that big of a board you should wait. I figuare RC3 will be rolling out shortly and then Gold which hopefully will allow you to upgrade direct from 2.2.9 to the gold version so you will maybe have one big headache but after its over thats it.

[Logician]

I have upgraded a very large 2.2.6 board with 3 GB database and a lot of custom hacks to VB3 RC2 (custom hacks are not yet recoded for vb3 so upgraded board uses just default vb3 for now).

It took around 12 hours to complete the whole job and backing up the database is NOT included in this duration. It was around 100 steps excluding 2.2.6 -> 2.3.2 upgrade. Certain steps literally took hours to complete.

I had some problems in some steps and they failed to end peacefully. I believe this is because DB process was taking too long. I took control in these sections and applied some hacks manually to complete them. But in the end all board is successfully upgraded into VB3 RC2.

I have some notes about this upgrade and problematic steps but I'm in the office at the moment and my notes are not with me so I can not tell which steps required manual intervention.

[filburt1]

I have upgraded a very large 2.2.6 board with 3 GB database and a lot of custom hacks to VB3 RC2 (custom hacks are not yet recoded for vb3 so upgraded board uses just default vb3 for now).

It took around 12 hours to complete the whole job and backing up the database is NOT included in this duration. It was around 100 steps excluding 2.2.6 -> 2.3.2 upgrade. Certain steps literally took hours to complete.

I had some problems in some steps and they failed to end peacefully. I believe this is because DB process was taking too long. I took control in these sections and applied some hacks manually to complete them. But in the end all board is successfully upgraded into VB3 RC2.

I have some notes about this upgrade and problematic steps but I'm in the office at the moment and my notes are not with me so I can not tell which steps required manual intervention.
Thankfully, Steve says that the developers have already either started or are considering writing a shell script in addition to/as a replacement of the web-based installation script. It would help quite a bit, particurally for browser timeouts, crashes, etc.

[sabret00the]

Thankfully, Steve says that the developers have already either started or are considering writing a shell script in addition to/as a replacement of the web-based installation script. It would help quite a bit, particurally for browser timeouts, crashes, etc.that's amazing news, would love that, can't wait, hopefully it'll be out by the time i upgrade my live board :cool: