Re: SharePoint Upgrade Help Needed

Tech-Archive recommends: Fix windows errors by optimizing your registry

Yes, your outline is how I would approach it.

On Apr 29, 12:42 pm, mscs...@xxxxxxxxx wrote:
Hi all,

I amhaving a single server implementation of SPS 2003 SP3, Sql
2000....everything in one box.

I am moving to new hardware, which will be a full fledge server farm
with web servers, application servers and sql servers all separated.

I do not want to use database migration technique, since ultimately it
would be an in place upgrade, and if some sites are not properly
upgraded, there is no going back...yea I understand that I will have
the original environment intact as a back up....but how would I deal
with a site which is not properly upgraded in the new environment,
given there is no going back option. (Am I right, wrong, there is a
work around, anything).

So, currently, I plan to run the gradual upgrade on my current single
server implementation. Once upgraded, I intend to move everything from
it to the new full fledge farm implementation. (Later, we will retire
this server). (Is this approach correct, incorrect, your suggestions)

Now can I do anything of the following and which is correct, best, or
anything that you suggest:

Backup the whole portal (on my single server implementation) and
restore it to the new farm. And Im done. New farm will have two web
servers, two app servers and sql cluster. The new farm is configured
independently of the old single server implementation. (I wonder if
this is even possible?)

OR, I should use attach/detach to move the sql server components to
new Sql cluster. And then move the web server components to new web
servers. And then configure the app servers. And all that is done
manually. (Am I actually talking about database migration technique
but doing it after the upgrade?)

Portal currently in use is not highly customized, may be a few
frontpage customizations. 500 to 800 users. No custom webparts. One
main level portal. 150 to 200 sites. 50+- subsites.

Please note that doing the gradual upgrade on the current server is
what I HAVE to do, officially.

Anything totally different that you wanna suggest is most welcome.

Best regards,
Rehman

.

Relevant Pages

  • RE: MSDE to SQL Server
    ... I understand that you want to upgrade MSDE instances ... We can upgrade the instance SHAREPOINT to SQL and it is not recommended ... Business Server 2003 ...
    (microsoft.public.windows.server.sbs)
  • Problem upgrading named instance in SQL 2000
    ... I have installed SQL 2000 Server on my machine with Default Instance ... After selecting the Database Engine ... Reason: Your upgrade is blocked. ...
    (microsoft.public.sqlserver.clients)
  • Re: New Hardware, moving
    ... resources to NodeB and repeat the upgrade. ... Senior Database Administrator ... Microsoft SQL Server MVP ... SQL 2000 and Windows 2003 support up to four node clusters. ...
    (microsoft.public.sqlserver.clustering)
  • Re: MSSQL on XP-Pro
    ... These old versions of SQL Server should run on XP. ... There are two ways to upgrade. ... upgrade when you run the 7.0 install. ...
    (microsoft.public.sqlserver.setup)
  • Re: upgrading from SQL 7.0 to SQL2000
    ... I like the idea of doing a fresh install of SQL> 2000. ... > 2) install SQL 7.0 on a separate machine which is a test server. ... > 3) Restore the databases from my production server on to my test server> running SQL 7.0. ... While the upgrade should work just fine I like to start>> fresh if possible. ...
    (microsoft.public.sqlserver.setup)