MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Changing sharepoint server names

  Asked By: Alec    Date: Apr 17    Category: MOSS    Views: 973

We are in the process of upgrading our MOSS 2007 to SQL 2005 and
additionally installing the neverfail sharepoint solution. We are doing
the upgrade on what will be the DR server then switch the DR server to
production so as to minimize the downtime impact on the users and have a
readily backout plan if the upgrade and all fails to function as it
should. For DNS entiries and shortcuts, when we are ready to do the
switch with the servers we need to rename the DR server to the
production server name. My dba will be on hand to switch the name
within SQL but I know I will have to do some configuration within
central admin also. Has anyone ever switched server names? Also I am
doing the main backup and restore ahead of time for time constraints and
will do a differential backup for the changes - will I be able to
restore the differential from a sql 2000 configuration to the SQL 2005
configuration or will I have to bring production server down and
restore it to the DR server before I even attempt to do the upgrade of



2 Answers Found

Answer #1    Answered By: Megan Martin     Answered On: Apr 17

First, SharePoint upgrades are scary enough without the complications
that you describe. I'd highly recommend moving to SQL server  2005 before
you upgrade. In fact, I'd also apply any OS or database SPs, run the
prep tools multiple times, run the tool (I can't remember the name) that
removes orphans and gets unghosted pages ready to move, etc.

Second, it sounds like you are not planning an InPlace or Gradual
upgrade but rather a database migration upgrade, so the entire Config
database with all the new server names/roles will already be in your new
environment. So, you really aren't changing  server names, you are moving
content databases. Changing domain/server names  is very difficult (may
not be possible without involving Custom Support Services), but
upgrading content databases from v2 to v3 is definitely doable. Just be
sure that you have your v3 environment completely ready; practically any
custom configuration above a Site Collection (like included Managed
Paths and Web Applications), any custom DLLs, custom site/list
definitions, custom images, in fact custom anything on the file system
must be recreated on v3 target.

Answer #2    Answered By: Donta Kirkland     Answered On: Apr 17

yes it is scary but what is life without a little excitement.

Didn't find what you were looking for? Find more on Changing sharepoint server names Or get search suggestion and latest updates.