MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Migrating from 32 to 64 bit

  Date: Sep 03    Category: MOSS    Views: 1193

We want to migrate our current MOSS 2007 32 bit instance, to a 64 bit server.
Here is the configuration:

Current: Windows 2003 R2 32 bit, SQL Server 2005 32 bit MOSS 2007 32 bit,
single server farm.

New: Windows 2003 R2 64 bit, SQL Server 2005 64 bit, MOSS 2007 64 bit, single
server farm.

I have searched the group and other sites, but I can only find advice on
migrating to Win 2008. Can anybody point me to where I can find some
information on the best approach and instructions on how to do it.



6 Answers Found

Answer #1    Answered On: Sep 03    

We recently did a partial migration. We are on the 32bit version of MOSS
2007, but are using a 64bit version of SQL server 2005. We left the
MOSS portion alone because we are in the midst of testing SP2010 and
didn't want to upgrade twice. As far as the SQL 2005 upgrade, what we
did was to create a new 64bit Windows server and install the 64bit SQL
2005. We then did a backup of the database(s), made them read only while
we moved them to the new server and once completely moved, we repointed
our SharePoint site collections to the new database (only takes a
minute), took the old database offline. We did this for 15 site
collections without any issues and I think we only got one call that
someone couldn't access their site.

Answer #2    Answered On: Sep 03    

We are facing the same situation with coming from MOSS 2007 32 bit to MOSS 2010
64 bit.
This last December I signed up for and attended a three day presentation on
"SharePoint 2010 Overview for IT Professionals" from SQLSoft+.
Course Number: MS-50353

What Liz has described seems to be the preferred method for migrating from
32-bit MOSS 2007 to 64-bit MOSS 2010.
You use the database detach/attach method to migrate. There is some planning
that should be looked at beforehand too.

When we did this in the lab it seem to work just great with very little trouble.

So essentially if you can afford to bring up a blank MOSS 2010 server
You can make a copy of the existing content database on MOSS 2007, place it in
read only mode on the originating server,
then bring that copy over to the new MOSS 2010 environment with the
detach/attach method.
Once you attach that database into MOSS 2010 environment the database gets
updated for the 64-bit environment and you are good to go.

Just my two cents worth. I have not done this yet but probably will before this
year is out.

Answer #3    Answered On: Sep 03    

if I am reading this
correctly, you have a single server solution. That means MOSS and SQL on the
same box.

If this is the case, this is going to be a little more challenging for you since
you can not upgrade from 32bit to 64bit on the OS and applications side right on
the same box. There is no upgrade option.

There are several options that you have. You can convert your single server
solution into a 2 server solution or you can build a totally separate single
server solution and then perform a DB attach method.

I performed this same scenario for a client with the only difference was that
they had a medium build farm, which made it easier since I was able to upgrade
by sections.

If you choose to build a separate farm, there are little things that you have to
take into considerations.

Answer #4    Answered On: Sep 03    

Just for clarification, I have a single server with both MOSS and SQL and I want
to move to a different server (beefier)where I already have Windows 2003 and SQL
2005, both 64bit.

Answer #5    Answered On: Sep 03    

Was out on a trip. So this is actually a good deal.
If you configured that new server the same way as your other server, then you
can do a DB attached to the new environment.
You should communicate an outage to your users while you perform the migration.

Answer #6    Answered On: Sep 03    

We also did the same and it was working.

Didn't find what you were looking for? Find more on Migrating from 32 to 64 bit Or get search suggestion and latest updates.