Ok, I'm going to be honest here: I messed up... big time...
Here's the deal: last tuesday I wanted to upgrade my MOSS server to SP2 with
post SP2 updates. I created back-ups of both the front-end as well as the
databases. I installed SP2 and all was well, no problems there.
Now today I decided to install Projects Server 2007 onto the same front-end
machine. I ran an installation with SP2 updates slipstreamed, somehting which
I shouldn't have done. It appeared that such an update doesn't work, I read
somewhere you can't install with SP2 slipstreamed. So now I had a working
SharePoint environment, but a non working Project server. So I uninstalled
Project Server, and that's where everything went wrong.
Removing Project Server also cleared my entire C:\inetpub\wwwroot\wss
directory, along with all sites and settings in IIS: everything was gone. I
only back-up all databases on the back-end server, but didn't make new images
of both machines.
So now I'm running a partition restore on the front-end machine to restore
all sites and settings again. Maybe I was a little freaked out, I didn't
think about running the configuration wizard after uninstalling, but I'm not
sure whether that would fix this or not (I would be suprised if it would).
It'll take another half hour, and then I'll be stuck with a pre-SP2
installed front-end machine connected to SP2 update databases.... not too
sure about that either. Offcourse I can reinstall SP2 on the front-end
machine, but I don't know if that update is going to succeed when the
databases are already updated.
Worst case scenario: I can't upgrade to SP2 any longer. Then I'll restore
the tuesday back-up of the databases too. I can then upgrade the entire
installation to SP2 again and restore the SP2 databases from todays back-up
again, I guess that should work for sure.
As for this post: if anyone has any comments / pointers for me which could
help, please feel free to post them :) And please don't point in the
usefullness of making daily images / back-ups, I'm well aware of that now.