Publisher migration

Hi,
I have a Merge replication setup to replicate from server A (Florida) to
server B (Spain).
We bought a new server and want to replace server A by server N in Florida.
Is there a guideline on how to do this? (appart from the
"starting-from-scratch" approach).
Also, i would like to do it little by little; first I want to have N to be a
subscriber of A; eventually I would like to change it to be the publisher.
Thanks for your help... Jos Araujo.
Jos,
I cannot say how to do it little by little, from what I know it is boring
and painful. If you want to do it at once - it is quite simple, I did it and
it worked just fine. Just make two servers with similar directory structure,
copy database files to a second server, give it the name of the first server
and you're done. Here are the details:
1. Install SQL Server on the server N, with all the upgrades that you have
on the server A, so that the versions of SQL Servers on both computers are
exactly the same.
2. Make sure the default data files directory as well as startup parameters
on both servers are exactly the same. (Enterprise Manager - SQL Server
Properties - General tab - Startup Parameters, and Database Settings tab -
Default Data directory).
3. Stop SQL Servers on both computers A and N. Just in case you can save
files from the database folder on N - move them to another folder. Now copy
all the files from server A database folder to the corresponding folder on
the server N.
4. Disconnect both computers A and N from the network
5. Rename computer N to match computer A, reboot and make sure all the
databases are online. At this point if something goes wrong and you need
your server running right away, you can simply reconnect server A to the
network and start SQL Server there; in this case you will later have to
continue from step 2. Obviously, now you cannot have both computers running
on the same network, because they have the same name. Of course, you can
rename A too.
6. Replace A with N on the network, now you are ready to go. Hopefully
everything will work fine...
To play it safe you can try it first in your local environment, and also you
can disable all but one test subscription, replace the server, make sure
your test subscription can synchronize, and finally enable all the remaining
subscriptions. Personally, I think that the second suggestion is an
overkill, but it's your decision.
Good luck,
Igor
"Jose Araujo" <josea@.mcrinc.com> wrote in message
news:uF75UWEEFHA.3244@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I have a Merge replication setup to replicate from server A (Florida) to
> server B (Spain).
> We bought a new server and want to replace server A by server N in
> Florida.
> Is there a guideline on how to do this? (appart from the
> "starting-from-scratch" approach).
> Also, i would like to do it little by little; first I want to have N to be
> a
> subscriber of A; eventually I would like to change it to be the publisher.
> Thanks for your help... Jos Araujo.
>
|||Thanks a lot!
Jos.
"Igor Rass" <irass{nospam}@.optonline.net> wrote in message
news:OmXuuy4EFHA.3416@.TK2MSFTNGP09.phx.gbl...
> Jos,
> I cannot say how to do it little by little, from what I know it is boring
> and painful. If you want to do it at once - it is quite simple, I did it
and
> it worked just fine. Just make two servers with similar directory
structure,
> copy database files to a second server, give it the name of the first
server
> and you're done. Here are the details:
> 1. Install SQL Server on the server N, with all the upgrades that you have
> on the server A, so that the versions of SQL Servers on both computers are
> exactly the same.
> 2. Make sure the default data files directory as well as startup
parameters
> on both servers are exactly the same. (Enterprise Manager - SQL Server
> Properties - General tab - Startup Parameters, and Database Settings tab -
> Default Data directory).
> 3. Stop SQL Servers on both computers A and N. Just in case you can save
> files from the database folder on N - move them to another folder. Now
copy
> all the files from server A database folder to the corresponding folder on
> the server N.
> 4. Disconnect both computers A and N from the network
> 5. Rename computer N to match computer A, reboot and make sure all the
> databases are online. At this point if something goes wrong and you need
> your server running right away, you can simply reconnect server A to the
> network and start SQL Server there; in this case you will later have to
> continue from step 2. Obviously, now you cannot have both computers
running
> on the same network, because they have the same name. Of course, you can
> rename A too.
> 6. Replace A with N on the network, now you are ready to go. Hopefully
> everything will work fine...
> To play it safe you can try it first in your local environment, and also
you
> can disable all but one test subscription, replace the server, make sure
> your test subscription can synchronize, and finally enable all the
remaining[vbcol=seagreen]
> subscriptions. Personally, I think that the second suggestion is an
> overkill, but it's your decision.
> Good luck,
> Igor
> "Jose Araujo" <josea@.mcrinc.com> wrote in message
> news:uF75UWEEFHA.3244@.TK2MSFTNGP15.phx.gbl...
be[vbcol=seagreen]
publisher.
>