Discussion Locked

Upgrade exchange 5.0 to didn?t work out

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We tried to do an upgrade from 5.0 to 5.5. We have 200 mailboxes on the current server and we tried to do the fault-tolerant upgrade. The first time the upgrade stopped at around 14% of the updat of the priv.edb. We started to empty the biggest mailboxes but it didn?t helped. Upgrade stopped earlier. I tried to 'fix' the priv.edb but nothing changed. We did a roll back and are again running 5.0. Anyone have an idea what we should do? We?re thinking of installing a 5.5 server and moving the mailboxes. Good idea?

5 replies

by tony.colgrove

Installing a new 5.5 box and moving the users is not a bad idea. You will lose the single instance storage of the existing mailboxes, but you start with a new clean compact database.
One issue you might be running into is database size. Just because you cleaned some of the big mailboxes out, does decrease your database size. The message become "White Space" in the database and allow for the area to be overwritten. To actually shrink the priv.edb you need to use edbutil (Ex5.0) and defrag the database offline.
But again, I would recommend starting with a clean new server and moving the users, if you have the available hardware.

by mckaytech

I agree with Tony's answer above but there is one thing you might want to check first and that is to make sure you have enough space to do the upgrade. The fault tolerant upgrade requires free space of about 110% of the combined size of the priv.edb, pub.edb and dir.edb databases (I use 125% for safety) because it stores an unchanged copy of the databases as well as the new ones (that's how it has the fault-tolerant ability to roll back a failed upgrade).

If you don't currently have the space, you can have all your users delete as much e-mail as they can and then run an off-line defrag using edbutil.exe (edbutil /d)and then see if you have enough space.

On the other hand, I just completed v5.0 to v5.5 upgrades of a dozen servers. Ten of them ran just fine with the fault-tolerant upgrade but for the two that didn't, I built new v5.5 servers, joined them to the same site and then used the Move Mailbox utility to move the mailboxes to the new server. The key thing to watch if you do this is to make sure you also take care of re-homing any public folders, re-designating the server that holds the routing tables, etc. MS has a TechNet article "Removing the First Server from a Site" that lists the gotchas for this process.

But I would just about bet that the upgrade process is choking from inadequate drive space and the easiest fix would be to provide the additional space needed.

paul

This discussion is closed to new replies.