Replication migration from x32 to x64

Question

Post reply

Replication migration from x32 to x64

Viewing 5 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

noeld SSC Guru Points: 96590 More actions · Answer 1

Jay the renaming of the servers is a tough one for replicated scenarios.

If you can take the old db offline while the new come online you "could" potentially getaway with it.

There is really nothing to worry about restoring an x32 2005 db into an x64 2005 db. The file format does not change!

I have never tried your migration scenario so I can not tell if restoring master, msdb and probably distribution db too onto the new hardware could cause problems. IF the server name is the same and the disks layout are the same I see no problem but in all honesty I would try to test such a thing at least on a VM with one publication.

* Noel

Jay Kusch SSC Veteran Points: 296 More actions · Answer 2

Thanks for the info.

We are absolutely testing this before the real project is cut loose.

Just trying to get any info from others who may have tried this process in the past.

I will keep everyone posted as we progress.

Jay Kusch SSC Veteran Points: 296 More actions · Answer 3

BOL to the rescue again (once you hit on the right combination of words - lol).

We are going to be able to execute this process leveraging Replication and Mirroring.

The mirrored DBs will exist on the x64 server while the primary DBs will remain on the x32.

When ready, we should be able to failover and drop the mirror.

Here is a link that descibes the process:

http://msdn.microsoft.com/en-us/library/ms151799.aspx

noeld SSC Guru Points: 96590 More actions · Answer 4

Jay Kusch (4/6/2009)
BOL to the rescue again (once you hit on the right combination of words - lol).
We are going to be able to execute this process leveraging Replication and Mirroring.
The mirrored DBs will exist on the x64 server while the primary DBs will remain on the x32.
When ready, we should be able to failover and drop the mirror.
Here is a link that descibes the process:
http://msdn.microsoft.com/en-us/library/ms151799.aspx

You should know that it is mandatory that the distribution DB is on a separated Server and that the "new" server *cannot* have the same server name.

If the new server that you are migrating to, can have a totally different name then this or log shipping or peer-to-peer migrations can serve your purpose.

Good Luck

* Noel

Jay Kusch SSC Veteran Points: 296 More actions · Answer 5

Thanks Noel.

That is exactly the configuration we have (albiet we have not created the new x64 server yet and a different name will not be an issue since we are using CNames for all of our SQL servers instances and assocaited DBs).

Once we are ready, we will "switch" the publication server to execute from the x64 box and switch the CName pointing currently at the x32 server to the new x64 server as well. Should be pretty transparent to all of our users and apps.

Thanks for the info!